A quick one this: After recovering from a hung VMware Workstation host, I was booting up the virtual machines and on one of them, I saw the following error:
Failed to lock the file.
Cannot open the disk <disk name> or one of the snapshot disks it depends on.
Module DiskEarly power on failed.
Failed to start the virtual machine.
This was unusual as I knew the disk was indeed there and there weren’t any snapshots of the machine in question. So, I went to the folder for that virtual machine and saw these extra files that I wasn’t expecting:
These “lck” folders are created when locks are placed on vmdk and vmem files when the machine is in the running state. As the machine wasn’t running, these folders shouldn’t have been there. Also, the vmem file shouldn’t be there if the machine is off.
Resolution was simple: Just delete these file and folders. Once done, the machine powered on just fine.
Hope this helps!
Thanks a lot for the solution. It saved my one day work of setting up complete development environment.
Great Sir, thank you!
i have to delete all those .lck files???
You saved my day! Greetings from germany
Thanks you saved 6 months of development and work
Wow! Glad to be of assistance! ☺️
Thanks a lot for this simple but effective way of solution, back working.
Good man
Thank you! Had a power failure last night and believe that caused the lock. Happy to find your simple solution. It saved me from using my backup image of the HD.
Thanks
Thanks for this quick and easy fix to my issue!
very nice
Awesome Brother…Gr8 explanation… Hatsoff
easy solution and it touched!!
Thank you very much.
I could not have figured out this simple resolution.
Gracias por el aporte me funciono muy bien saludos
Thank you very much
Thank you very much for saving my skin
Thank you very much
Nice. Short and sweet and works.
THANK YOU!!!!!
Thanks Very Mach…..