Restore Vmdk Descriptor File !new! -

Disaster Recovery: How to Manually Restore a Corrupt or Missing VMDK Descriptor File

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

vi WindowsServer.vmdk Here is a standard template for a monolithic sparse or monolithic flat disk. You must change the values in brackets. restore vmdk descriptor file

Run this command against the flat file:

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" Disaster Recovery: How to Manually Restore a Corrupt

Don't panic. You don't need backups of the entire VM to fix this. You just need to rebuild a 1KB text file.

You check the datastore, and everything looks fine—your large flat VMDK (usually named vmname-flat.vmdk ) is sitting right there, taking up 100GB. But its tiny sibling, the descriptor file ( vmname.vmdk ), is missing or corrupted. Run this command against the flat file: ddb

Have you recovered a VM using this method? Let me know in the comments below!