VMware Communities
mromini1
Contributor
Contributor

Fusion 8.5.10: unable to start virtual machine - vmdk corrupted

Hi all, I have a big problem with a virtual machine. It does not start anymore and inside the log file I read this error:

018-08-20T09:38:12.604+01:00| vmx| I125: DISKLIB-SPARSECHK: [/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk] 61440 excess bytes at end of file

2018-08-20T09:38:12.604+01:00| vmx| I125: DISKLIB-SPARSE: "/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk" : failed to open (14😞 Disk needs repair.

2018-08-20T09:38:12.604+01:00| vmx| I125: DISKLIB-LINK : "/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk" : failed to open (The specified virtual disk needs repair). 

2018-08-20T09:38:12.604+01:00| vmx| I125: DISKLIB-CHAIN : "/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk" : failed to open (The specified virtual disk needs repair).

2018-08-20T09:38:12.604+01:00| vmx| I125: DISKLIB-LIB : Failed to open '/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk' with flags 0x1a The specified virtual disk needs repair (14).

2018-08-20T09:38:12.606+01:00| vmx| I125: DISKLIB-SPARSECHK: [/Users/m.romini/Documents/Virtual Machines.localized/VmMarior8.edpromagna.local/WmMarior8.vmwarevm/Disco virtuale.vmdk] 61440 excess bytes at end of file

I tried to fix the error with vmware-vdiskmanager -R without success.

Does anyone have any ideas? I enclose the complete log to the discussion.

0 Kudos
3 Replies
mromini1
Contributor
Contributor

Nobody has any ideas?

0 Kudos
continuum
Immortal
Immortal

The best approach is to copy the vmdk to a Windowshost and read it with V2Vconverter from Starwind.
Second best is to use an older vmware-vdiskmanager - all current versions are broken.
Third best - but probably the easiest variant is to edit the size of the VMDK - apparantly the vmdk is 120 * 512 = 61440 bytes too small.
So please read VMDK-Handbook-Basics ,
extract the embedded descriptor
and edit the line that starts with
RW <value in sectors> SPARSE "Disco virtuale.vmdk"
Add 120 to  <value in sectors> and reinject the descriptorfile.
Make sure to keep a backup of the original descriptor !
I dont know if this will work - but it is worth a try.
Ulli


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

0 Kudos
mromini1
Contributor
Contributor

Thanks for the instructions. I tried the third way without success. I still recovered the data I needed using 7zip to open the file and then I reinstalled windows from the beginning.

0 Kudos