unable to access file since it is locked error

[Daniel997]

Hi all,

I am trying to start a VM located on SAN storage after a failure in the storage network (iSCSI) when I get this error (the storage network failure has been repaired):

• unable to access file <unspecified filename> since it is locked.

So far I have tried the following:

• Create a new VM and attach the disks of the old VM to the new VM and I get the above error trying to start the new VM.

• Ran lsof | grep /vmfs/volumes/.../vmname/vmname.vmdk on all attached ESX boxes (no process were listed).

• Tried the steps in () however the UUID returned when using the vmkfstools -D is not found in any of the ESX boxes in our organisation (unless I'm doing something wrong here?).

• Tried running ps auxfww | grep vmname on all esx boxes (returns no results)

• Tried esxtop on all ESX boxes and there is no reference to the VM I'm trying to start.

• Tried running vmkfstools -L release VMNAME.vmdk and get this error (Command release failed Error: Inappropriate ioctl for device).

• Tried running a vcbExport however get this error (Error: Failed to open the disk: Failed to lock the file).

Is there any way of forcing the lock on this file open that I haven't tried yet?

[Daniel997]

I have managed to fix this issue by trying the vcbExport from each ESX box until I found the one that was holding the lock. I have exported the vmdk file to a new file which I have now attached to a new VM.