We ran into this issue when a VM went down unexpectedly and it would not restart cleanly - the error was:
"Cannot open the disk '/vmfs/volumes/4cf0daa-10489d5-4e6b-00219ba51425/ttw-db-09/ttw-db-09_3.vmdk' or one of the snapshot disks it depends on."
To debug, I ssh'ed into the ESXi 4.1 box to check out the file it was referring to (it was fine and readable and touchable per KB10051) and the vmware.log which indicated the actual issue:
"Cannot open the disk '/vmfs/volumes/4cf0daa-10489d5-4e6b-00219ba51425/ttw-db-09/ttw-db-09_3.vmdk' Failed to lock the file"
None of of the related KB's helped resolve the issue.
What turned out to be the solution came from a forum posting - just creating a temp snapshot and deleting cleared the condition and allowed the VM to power on cleanly.
thanks again to the vmware community forums - truly a great 24x7 resource!
8 comments:
Great and simple solution, I was working on mac recovery software and had source code which I didn't checkin and my VM was not booting. The solution worked for me. You are really great :-)
Life saver this has just sprang my fileserver back into life after trying various other more complicated things!
Thank you...You saved my life.
You saved my life...Thank you
HI, Please detail more your solution. I don't understand "deleting cleared the condition and allowed the VM to power on cleanly."
@dungtt: create a snapshot for the VM, then delete that snapshot - then power on VM as normal.
@vExpert2013: thanks for your advice, but it didn't work with me. VM still can't power on.
hey i just removed that ....vmdk.lck file from machine folder......machine started...no issues..
Post a Comment