VMware Communities
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

Is there a way to repair VMDK file after vdiskmanager.exe says it can not be repaired?

Hello,

I have VMDK file which is corrupted due to some controller issue on host. I'm running 12.1 Workstation on Win 8.1 x64. VMDK output below along with log.

[ADMIN]: PS > .\vmware-vdiskmanager.exe -R "D:\dalliandt2\DALIANDT2.vmdk"

The virtual disk, 'D:\daliandt2\DALLIANDT2.vmdk', is corrupted and cannot be repaired.

1 Solution

Accepted Solutions
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

OK after spending entire day trying to find a solution I found the way to fix it.

Download V2V convertor (free)  Download StarWind V2V Converter | StarWind Software

I converted by broken dynamically expanding disk to flat one and Windows booted, detected file corruption and started running repair.

View solution in original post

8 Replies
continuum
Immortal
Immortal
Jump to solution

Please attach the vdiskmanager log.
It will show us if there is any hope.
Sometimes vdiskmanager from WS 7.1 can help - but not always


________________________________________________
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
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

Here is the log

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Run the command again - it may fix one piece at a time.
It probably will be necessary to check other vdiskmanager-versions.


________________________________________________
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
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

How do I know if repairs are being done after each run of command and that I'm not wasting time running the same command all over again? I'm running latest version of Vmware Workstation, I assume I have latest version of vdiskmanager as well, what other version of vdiskmanager needs to be checked?

G

Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Compare the new vdiskmanager.log with the one from previous run.
It should have less errors - or just be smaller inside.
vdiskmanager from WS 6.5 upto 7.1 is ok - all later versions released with WS are questionable.
There also are some working versions that come with the VDDK-kit - but finding out which versions are broken is tricky


________________________________________________
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
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

File are identical in size after each run (i run vdiskmanager 10 times).

How do I find vdiskmanager from earlier versions of WS without installing and removing current one?

I found some vdiskmanager from both VDDK and some older versions for Workstation. All of the failing with below

[ADMIN]: PS > .\vdiskmanager-windows-7.0.1.exe -R D:\dal2\DAL2.vmdk

NOT_IMPLEMENTED d:/build/ob/bora-227600/bora/lib/disklib/sparseChecker.c:1279

Win32 object usage: GDI 4, USER 1

CoreDump: Writing minidump to C:\Users\g\AppData\Roaming\VMware\vdiskmanager-windows-7.0.1-8132.dmp

[ADMIN]: PS >

Reply
0 Kudos
ChanKaiShi
Enthusiast
Enthusiast
Jump to solution

OK after spending entire day trying to find a solution I found the way to fix it.

Download V2V convertor (free)  Download StarWind V2V Converter | StarWind Software

I converted by broken dynamically expanding disk to flat one and Windows booted, detected file corruption and started running repair.

AnatolyVilchins
Jump to solution

Wow! interesting workaround! Thanks for sharing!

I`ll leave it here just in case if someone would like to learn more about v2 vconverter:

https://www.starwindsoftware.com/styles-v2/pdf/starwind-free/V2V_Converter.pdf

Kind Regards, Anatoly Vilchinsky