Error: "Cannot open the disk '/vmfs/volumes/vsan:xxx-xxxx/xxxx-xxxx-xxxx-xxxx-xxxxx/VM.vmdk' or one of the snapshot disks it depends on." is noticed when the user try to power on the VM with shared vmdk after cross vCenter migration.

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• The VMs with shared VMDK fail to power on after the user did an XVMotion of the VMs.
  
  
• When powering on, the user gets the following error.

"Cannot open the disk '/vmfs/volumes/vsan:xxx-xxxx/xxxx-xxxx-xxxx-xxxx-xxxxx/VM.vmdk' or one of the snapshot disks it depends on."

Environment

VMware vSAN 7.0.x

VMware vSAN 8.0.x

Cause

This issue may occur due to one of these reasons:

• Could not open/create change tracking file
• I/O error accessing change tracking file
• Failed to lock the file
• The file already exists
• Insufficient permission to access file
• Input/output error
• Cannot allocate memory

 

Resolution

• Please check the KB for more details: Cannot open the disk '/vmfs/volumes/datastore_dir/vm_dir/vm.vmdk' or one of the snapshot disks it depends on
  
  
• If the issue is still not resolved after checking the above KB resolution. The user can clone the VM and then try to power on the VM. As part of the cloning, the new configuration file is generated, and the stale information is not carried with the cloned VM. Post-cloning, the VM should be able to power on without any issues.

• If the issue still persist, please contact Broadcom Support.