VMware Communities
piggyz
Enthusiast
Enthusiast

Problem with a corrupted segment of a disk

Hello,

After a disk fail one of my Virtual Machines is now broken. Exactly it complain about a segment of the disk can't be found, even if it is (probably corrupted) on the new disk where I saved all the backups of my faulty disk

The message is: Unable to Open file: "arch9-000011.vmdk"

This machine have very many snapshot (circa 25). To try to solve the problem, I tried to delete some of this snapshots using the Snapshot GUI with no luck. Everytime I try to delete some snapshot, it always complain about the corrupted disk file below.

Now I do ask, considering I do not have a backup of this machine, how can I try to fix this problem considering of like 25 segments of the disk, this one is the only one corrupted (I didn't had problems to copy other segments from the old faulty disk to the new disk)? No problem if I do loose some of the snapshots, I just need the basic machine running.

Any help will be very very appreciated

Reply
0 Kudos
2 Replies
piggyz
Enthusiast
Enthusiast

I want to add that if I try to access the disk from the configuration menu of this machine, when I click on Hard Disk, the system say: "The Parent of This Virtual Disk could not be opened"

Reply
0 Kudos
continuum
Immortal
Immortal

if you really have a corrupt snapshot - then the only thing you can do is to edit the snapshotchain so that it skips this vmdk.

Lets say your chain looks like this:

base.vmdk - snap1 - snap2 - snap3 - snap18 - snap15 - snap4 - snap5 - snap11-corrupt - snap20 - snap21 - current-snapshot as listed in the vmx

After the edit you would then have a shorter chain like this

base.vmdk - snap1 - snap2 - snap3 - snap18 - snap15 - snap4 - snap5 - snap20 - snap21 - current-snapshot as listed in the vmx


NOTE: if you have created the VMs with defaults you have to edit embedded descriptorfiles - do not attempt this with a hexeditor if this is your first time.
Read http://sanbarrow.com/vmdk-howtos.html#editvmdk

first !!!!!

There may be other ways to fix this but we would need the vmware.logs and the embedded descriptorfiles to get the whole picture.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos