Leigh Kalbli
asked on
vm powere on fails with lock message
After an ESX host iSCSI became disconnect to our SAN's because of a Cisco switch issue, several VM's fail to power on. The error message is as follows.
Failed to lock the file
Cannot open the disk '/vmfs/volumes/5661e6ad-b2
Failed to power on scsi0:1.
Failed to add disk scsi0:1.
The referenced disk is a second disk on the VM. If i remote it, the VM powers on fine. If i try to add it back after booting up, same error.
I have also created a new VM from scratch with same specs and then added the OS disk and the above disk partition and get the same errors.
Failed to lock the file
Cannot open the disk '/vmfs/volumes/5661e6ad-b2
Failed to power on scsi0:1.
Failed to add disk scsi0:1.
The referenced disk is a second disk on the VM. If i remote it, the VM powers on fine. If i try to add it back after booting up, same error.
I have also created a new VM from scratch with same specs and then added the OS disk and the above disk partition and get the same errors.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Okay, so we need to check if the VM has a snapshot, can you screenshot the VM Folder and upload here, and also screenshot the disk settings/properties in the VM Settings.
ASKER
Attached are the screen grabs. Now what freaks me out is that i have never seen the two disks at 0. I have never seen that before.
ASKER
I think i may see it but should the .vmx.lck file be deleted?
Okay, no snapshots present.
this VM is not started on any other host ?
remove the lck file if possible
this VM is not started on any other host ?
remove the lck file if possible
ASKER
It is not powered on any other host at this time. I am deleting the file now and will post results.
ASKER
Delete file
pool-01-vol-06 (Ohio NSIGHT Customers)
Cannot delete file [pool-01-vol-06 (Ohio
NSIGHT Customers)] oh03.domain.com
/FB2 - Hebron.vmx.lck
pool-01-vol-06 (Ohio NSIGHT Customers)
Cannot delete file [pool-01-vol-06 (Ohio
NSIGHT Customers)] oh03.domain.com
/FB2 - Hebron.vmx.lck
I suspected as much, you will need to find the process and/or host which has the file locked
see here
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051
see here
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051
ASKER
Thanks. I just actually came across this post and one you mentioned https://www.experts-exchange.com/questions/28418425/Remove-lock-from-vmware-disk.html
I will follow up.
I will follow up.
sometimes, it's quick just to use the original VMX file, and VMDK to get the VM started!
in a different folder!
in a different folder!
ASKER
What exactly do you mean?
Create a new folder.
Move the VMX files to it, add the VMX file to the inventory, and then add the virtual disks!
Move the VMX files to it, add the VMX file to the inventory, and then add the virtual disks!
I see your descriptor file is messed up, therefore the disk size is showing zero.
You may require to refresh the configuration - or re-register the VM.
run command
vim-cmd vmsvc/getallvms | grep -i VMNAME -C5
once you get the vmid.
run below command.
vim-cmd vmsvc/reload vmid.
Regards,
Ajay Chanana
You may require to refresh the configuration - or re-register the VM.
run command
vim-cmd vmsvc/getallvms | grep -i VMNAME -C5
once you get the vmid.
run below command.
vim-cmd vmsvc/reload vmid.
Regards,
Ajay Chanana
ASKER
Andrew,
I attemted moving the vmx and then adding the vmdk files and still have the same issue.
I attemted moving the vmx and then adding the vmdk files and still have the same issue.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.