Restore Vmdk Descriptor File Updated Guide

Always take a checksum (MD5) of the -flat.vmdk before editing. One wrong space in the descriptor file is fine—it will throw an error. One wrong offset? That corrupts the partition table.

ddb.adapterType = "lsilogic" ddb.geometry.cylinders = "[CYLINDERS]" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.longContentID = "b5e0dbe93277d7e7d70505c1" ddb.thinProvisioned = "0" ddb.toolsVersion = "0" ddb.uuid = "6000C299-1234-5678-9abc-def123456789" ddb.virtualHWVersion = "13" restore vmdk descriptor file

Run this command against the flat file:

Disaster Recovery: How to Manually Restore a Corrupt or Missing VMDK Descriptor File Always take a checksum (MD5) of the -flat

vi WindowsServer.vmdk Here is a standard template for a monolithic sparse or monolithic flat disk. You must change the values in brackets. That corrupts the partition table

Create a new file named exactly like the original (e.g., WindowsServer.vmdk ) using vi or nano .

# Disk DescriptorFile version=1 CID=fffffffe parentCID=ffffffff createType="monolithicFlat" RW [SIZE_IN_SECTORS] VMFS "vmname-flat.vmdk" The Disk Data Base #DDB