Ado74
Contributor
Contributor

Help fixing "The specified virtual disk needs repair (0x3e86)"

Hi

I ran the recover space command to on my VM as it was using 120GB of 180GB allocated. As this was taking I while I cancelled it as I had work to do. my mac froze and restarted. Since then i cannot start up the vm. I get the error he specified virtual disk needs repair (0x3e86). I have tried sudo /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -R to repair but it just gives me same error message. Looking at logs I see

localized/Windows 7 x64.vmwarevm/Virtual Disk.vmdk] Grain #2535785 @324621568 is orphaned.

2018-07-11T17:12:15.439Z| vmx| I125: DISKLIB-SPARSECHK: [/Users/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Virtual Disk.vmdk] 254817 orphan(s) detected

2018-07-11T17:12:15.439Z| vmx| I125: This is bug 1683.

2018-07-11T17:12:15.461Z| vmx| I125: DISK: Opening disks took 5449 ms.

2018-07-11T17:12:15.461Z| vmx| I125: Module 'Disk' power on failed.

2018-07-11T17:12:15.461Z| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0

2018-07-11T17:12:15.467Z| vmx| I125: <<< file Throttled >>>

Ive tried to attached the support info but zip file is too large, what bits are required?

Can this be repaired/documents recovered. I dont have an up to date back up--yea I know....

Cheers

A

0 Kudos
4 Replies
daphnissov
Immortal
Immortal

You've canceled an important disk move operation which was a big no-no. As a result, you probably have data corruption. You're already aware not having a backup was your big mistake, but at this point other than opening a support request there may not be a solution.

0 Kudos
dlhotka
Champion
Champion

There are a handful of people in the forum who can help repair disks - Wila posted some information in a recent thread about the ones to look for.

0 Kudos
continuum
Immortal
Immortal

Unfortunately at the moment the easiest approach to this problem is this nasty workaround:
1. copy the VMDK file in question to a Windows machine that has Starwind V2V converter installed
2. try to read the VMDK with the V2V converter
3. if possible convert the VMDK to another format / or create a new VMDK with it
4. copy back to your Fusion host

5. cross fingers
Plan B: try to install an older version of vdiskmanager - last known good one is from Fusion 3.1
see
VMware Knowledge Base

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
Ado74
Contributor
Contributor

thanks for the replys. Ive a new windows laptop, I will try copying over to that and I will report back.

0 Kudos