Hello,
When I worked with my virtual machine (windows 10) the electricity went out.
Now I want to start a virtual machine but I have an error:
module disk power on failed
Please see the attached file.
Thanks
Welcome to the Community,
with VMware Workstation closed, check whether the VM's folder contains files, or sub-directories with a .lck (lock) extension, and delete them.
If this doesn't help, run dir *.* from the command line to list all of the VM's files, and post the command's output in your next reply.
André
Welcome to the Community,
with VMware Workstation closed, check whether the VM's folder contains files, or sub-directories with a .lck (lock) extension, and delete them.
If this doesn't help, run dir *.* from the command line to list all of the VM's files, and post the command's output in your next reply.
André
Thank you,
I deleted two folders with .lck extension and My problem was solved.
What are these folders?
Why are they created?
Thanks
They are used a locking mechanism in VMware Workstation.
How exactly this works is something that only the developers know. At least I'm not aware of a public documentation about this.
André
Hi there, I know this post is a little older, but I'm running into the same problem. I've tried deleting the .lck folder as well as running Restoro to try and fix the problem, no luck on either option. I'm wondering if there's anything else I can do or whether I'm gonna have to completely redo my project within the next 2 days. Thanks in advance
Hi there, I'm also facing the same problem. Any help on this problem would be welcome. Thank you.
@flegma9 You've provided few details other than the error message. There's more than one thing that could cause this. Please attach the vmware.log file from your virtual machine as well as a listing of all the files in the virtual machine's folder so we can get a better idea of what's going on.
That worked for me too. I had two folders inside the VM with the same error, both with the .lck extension. Once deleted after exiting VMware Workstation; problem solved. The cause was power fail of the host environment.
