VMware Communities
keeran02
Contributor
Contributor

VMware Module Disk power on failed..

I suddenly got this error on my vmmachine. Does anyone know what kind of problem is it?

I really need to fix it. I do not have a backup yet.

pastedImage_1.png

Reply
0 Kudos
10 Replies
sjesse
Leadership
Leadership

if you go into the folder where the vmdk file in the error is, are there any files that end it --001.vmdk?

Reply
0 Kudos
keeran02
Contributor
Contributor

I do have this one

pastedImage_0.png

Reply
0 Kudos
sjesse
Leadership
Leadership

can you post  the file that ends in vmx?

Reply
0 Kudos
keeran02
Contributor
Contributor

pastedImage_0.png

Reply
0 Kudos
sjesse
Leadership
Leadership

Hats not enough, there should be a part that looks like

scsi0:0.fileName = "Windows 10 x64.vmdk"

this is the one pointing to your harddrive, if its trying to find a snapshot there would be entries near this. A very basic one I have is 67 lines long.

Reply
0 Kudos
keeran02
Contributor
Contributor

Here is the only one point with this filename thing:

pastedImage_0.png

Reply
0 Kudos
a_p_
Leadership
Leadership

"Disk needs repair" means that the .vmdk file is corrupted. Depending on what's wrong it may or may not be fixed easily.

At this point I strongly recommend that you backup all the VMs files, so there's a way back to the current state in case things will become even worse.

What's the virtual disk's provisioned size, i.e. the size that shows up in the VM's settings?

André

PS: Please attach the VM's vmware.log file to your next reply post.

Reply
0 Kudos
keeran02
Contributor
Contributor

I got the problm. somehow the iso file got deleted.

I dont have any backup of the machine so i createted new machine.

Is there any way to put the iso into that machine and the machine would work normally?

Reply
0 Kudos
a_p_
Leadership
Leadership

Sorry, but I'm having trouble to understand what you say. Can you please clarify what that deleted ISO image is related to the virtual disk's corruption!?

André

Reply
0 Kudos
peanuts01
Contributor
Contributor

Image for post

Then look at directory with same name of the virtual machine with .lck, And delete them, After that restart the virtual machine, That error should be fixed. It worked for me.