How to fixed damaged VM to retrieve files?

[blaine1]

I have a VM that says it is not a VM when trying to open/upgrade using Fusion 1.5.3 (15870345) - Though the structure looks okay, it appears that the VM has some damaged or incomplete file sizes?

Is there a way to put this together so that I can recover any files?

I've attached a listing for the package contents and the descriptor for the Virtual Disk is as follows...

# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=4b71289b
parentCID=ffffffff
isNativeSnapshot="no"
createType="twoGbMaxExtentSparse"

# Extent description
RW 4192256 SPARSE "Virtual Disk-s001.vmdk"
RW 4192256 SPARSE "Virtual Disk-s002.vmdk"
RW 4192256 SPARSE "Virtual Disk-s003.vmdk"
RW 4192256 SPARSE "Virtual Disk-s004.vmdk"
RW 4192256 SPARSE "Virtual Disk-s005.vmdk"
RW 4192256 SPARSE "Virtual Disk-s006.vmdk"
RW 4192256 SPARSE "Virtual Disk-s007.vmdk"
RW 4192256 SPARSE "Virtual Disk-s008.vmdk"
RW 4192256 SPARSE "Virtual Disk-s009.vmdk"
RW 4192256 SPARSE "Virtual Disk-s010.vmdk"
RW 4192256 SPARSE "Virtual Disk-s011.vmdk"
RW 4192256 SPARSE "Virtual Disk-s012.vmdk"
RW 4192256 SPARSE "Virtual Disk-s013.vmdk"
RW 4192256 SPARSE "Virtual Disk-s014.vmdk"
RW 4192256 SPARSE "Virtual Disk-s015.vmdk"
RW 4192256 SPARSE "Virtual Disk-s016.vmdk"
RW 4192256 SPARSE "Virtual Disk-s017.vmdk"
RW 4192256 SPARSE "Virtual Disk-s018.vmdk"
RW 4192256 SPARSE "Virtual Disk-s019.vmdk"
RW 4192256 SPARSE "Virtual Disk-s020.vmdk"
RW 4192256 SPARSE "Virtual Disk-s021.vmdk"
RW 4192256 SPARSE "Virtual Disk-s022.vmdk"
RW 4192256 SPARSE "Virtual Disk-s023.vmdk"
RW 4192256 SPARSE "Virtual Disk-s024.vmdk"
RW 4192256 SPARSE "Virtual Disk-s025.vmdk"
RW 4192256 SPARSE "Virtual Disk-s026.vmdk"
RW 4192256 SPARSE "Virtual Disk-s027.vmdk"
RW 4192256 SPARSE "Virtual Disk-s028.vmdk"
RW 4192256 SPARSE "Virtual Disk-s029.vmdk"
RW 4192256 SPARSE "Virtual Disk-s030.vmdk"
RW 61440 SPARSE "Virtual Disk-s031.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "7832"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "c86e6d4023223a3f3bdd97b14b71289b"
ddb.toolsVersion = "9476"
ddb.uuid = "60 00 C2 96 dd c

Thanks in advanced for any suggestions.

Blaine 

[continuum]

Thanks for anticipating the follow up questions for a problem like this.
It saves a lot of time when the descriptor-vmdk and a filelist is already included.

> it appears that the VM has some damaged or incomplete file sizes?
Did you receive a message like "file is not a virtual disk" ?
If yes - we need the details for that message which should appear in the latest vmware.log

Without such a message you would need to use hexdump -C against all slices and report all files that do not start with KDMV

Ulli

[a_p_]

I assume that the reason for the truncated .vmdk file that you've posted is just a copy&paste issue.

From the files' time stamps it looks like the VM has either not been used for several years, or it has been restored from a backup!? Anyway, what I could think of is that the reason for the error message is the VM's suspended state, from which it cannot resume anymore due to either changed hardware, OS upgrades, or even VMware Fusion upgrades.
What should help in this case is to do "hard reset" the VM by deleting its .vmss, ansd .vmem files.

André