Skip to main content
Solved

Cannot read disque

  • March 1, 2023
  • 5 replies
  • 449 views

Forum|alt.badge.img+5

 

I'm trying to backup Virtual machines on VMware.

All backups are ok except two vms.

I have this error

Cannot read disque [[Datastore2-Compellent] SRV-EXCHANGE/SRV-EXCHANGE-000002.vmdk] for virtual machine [SRV-EXCHANGE] on the host [esxi03.domain.local]. 
[Une ou plusieurs erreurs se sont produites lors du traitement de la demande. (ERROR_ERRORS_ENCOUNTERED.774) , Échec de ReadCurrVmdkFile (W32.774)]

I have verified the connection between the access node and vice and the ESXIs all fine.

But I noticed that commvault try to access to vmdk disk that didn't exist on the VMs.

i have tow VMDK Files for two virtual disks that called  “SRV-EXCHANGE/SRV-EXCHANGE-1-000028.vmdk and SRV-EXCHANGE/SRV-EXCHANGE-000004.vmdk” for this vm.

Someone has a solution for this

 

Best answer by NVFD411

@Elmahdi Achraf - Must be a communication issues.  Please double check the network connectivity and access via the needed ports.

5 replies

Forum|alt.badge.img+7
  • Vaulter
  • March 1, 2023

@Elmahdi Achraf - Based on the initial troubleshooting steps you provided.  It seems that the error may be with the VMDK files itself (possible corruption or discrepancies between the VMDK files and vdisk).  

As mentioned here -

To rule out corruption or fragmentation quickly have your VMware team Storage vMotion the VM having the issue.  As it migrates the VM it will clear up any issues. If the problem persist then I recommend that a case with Commvault be opened to investigate further.

 


Forum|alt.badge.img+5

we have tried the storage vmotion but the problem still persists


Forum|alt.badge.img+7
  • Vaulter
  • Answer
  • March 13, 2023

@Elmahdi Achraf - Must be a communication issues.  Please double check the network connectivity and access via the needed ports.


Forum|alt.badge.img+5

@NVFD411 ok i will chek this again.

Thank you.


Forum|alt.badge.img
  • Novice
  • April 30, 2025

We are getting following error as below for few of the vms in the cluster and its taking much more time to complete the jobs

 

Erros:

      Agent issue
    Could not read data from the virtual disk.
   - VDDK thread timeout, possible VDDK deadlock