Vm fails to power on with the message "Cannot open the disk '/vmfs/volumes/b8####c0-0f####23-####-000######000/VM-NAME/VM-NAME.vmdk' or one of the snapshot disks it depends on."

Products

• VMware vSphere ESXi

Issue/Introduction

• There might have been power outage prior to the issue.
• The datastore in use is NFS 4.1.
• Around the timestamp of the failed power on task, you see in the vmkernel.log messages like in the sample below:

<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu6:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy
<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu6:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy
<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu28:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy
<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu0:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy
<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu1:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy
<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu48:2115285)NFS41: NFS41FileOpenFile:2911: Open of 0x430cf1fd87f0 with openFlags 0x2 failed: Busy

Environment

VMware ESXi 8.0.x

Cause

The error message are evidence of lock files in the NFS server.

Resolution

To resolve the locks on the NFS side, please contact your storage vendor.

 

If the VM is still not powering on after the lock issue is mitigated on the storage side, please raise a ticket with VMware by Broadcom.