Recover data from disk with missing vmdk parts

[bugi14]

I have a VMware disk which is saved as several 2GB .vmdk parts. A couple of these parts became corrupted, meaning that the virtual machine could no longer recognise the disk. Is there any way I could recover the data stored on the remaining parts?

Thanks,

Darren

[continuum]

Hi
create a list of all the vmdks that are still available
a cmd like this
dir /TW *.vmdk >> list-of-chunks
will do.
Also post the descriptor-vmdk.

Once we have that info we can tell you what to do next

Ulli

[bugi14]

Hi Ulli,

I've attached the descriptor file, and this is the list of chunks:

06/03/2015  15:38     2,056,257,536 Windows 8 x64-s001.vmdk

06/03/2015  15:38     2,120,155,136 Windows 8 x64-s002.vmdk

04/03/2015  19:03     2,141,978,624 Windows 8 x64-s003.vmdk

04/03/2015  19:03     2,146,697,216 Windows 8 x64-s004.vmdk

04/03/2015  19:03     1,919,352,832 Windows 8 x64-s005.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s007.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s008.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s009.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s010.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s011.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s012.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s013.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s014.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s015.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s016.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s017.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s018.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s019.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s020.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s021.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s022.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s023.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s024.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s025.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s026.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s027.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s028.vmdk

04/03/2015  19:03     2,139,488,256 Windows 8 x64-s029.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s030.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s031.vmdk

04/03/2015  19:03     2,108,555,264 Windows 8 x64-s032.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s033.vmdk

04/03/2015  19:03     2,137,849,856 Windows 8 x64-s034.vmdk

04/03/2015  19:03     1,818,624,000 Windows 8 x64-s035.vmdk

04/03/2015  19:03     1,207,042,048 Windows 8 x64-s036.vmdk

04/03/2015  19:03     1,308,295,168 Windows 8 x64-s037.vmdk

04/03/2015  19:03     1,360,396,288 Windows 8 x64-s038.vmdk

04/03/2015  19:03     2,145,976,320 Windows 8 x64-s039.vmdk

04/03/2015  19:03     2,145,583,104 Windows 8 x64-s040.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s041.vmdk

04/03/2015  19:03     2,146,762,752 Windows 8 x64-s042.vmdk

04/03/2015  19:03     2,060,255,232 Windows 8 x64-s044.vmdk

04/03/2015  19:03       619,315,200 Windows 8 x64-s045.vmdk

04/03/2015  19:03         3,997,696 Windows 8 x64-s046.vmdk

04/03/2015  19:03         8,716,288 Windows 8 x64-s047.vmdk

04/03/2015  19:03        10,616,832 Windows 8 x64-s048.vmdk

04/03/2015  19:03         5,046,272 Windows 8 x64-s049.vmdk

04/03/2015  19:03         7,733,248 Windows 8 x64-s050.vmdk

04/03/2015  19:03           131,072 Windows 8 x64-s051.vmdk

06/03/2015  15:34             2,722 Windows 8 x64.vmdk

              50 File(s) 87,434,660,514 bytes

Thanks

[a_p_]

What you may try is to replace the two missing files ("Windows 8 x64-s006.vmdk" and "Windows 8 x64-s043.vmdk") with a "blank" .vmdk file that only contains the required metadata. To get such a file, either create another VM with e.g. a 5GB split virtual disk, and use one of the 327.680 Bytes files, or use the file I attached to this post. Once all files are in place, you can try to either mount the virtual disk on the host system in read-only mode, or attach it to a helper VM as a secondary disk. In any case make sure you backup the files - unless already done - and/or create a snapshot before powering on the VM again to avoid changes in the current files.

André