VMFS Recovery™
Recover data from damaged or formatted VMFS disks or VMDK files
TRY IT FREEVer 4.28, WinBUY NOWFrom $699
Last updated:

Recover Missed VMDK Descriptor: Full Repair and VMFS Recovery Guide

A missing or corrupted VMDK descriptor file prevents VMware from recognizing the virtual disk, leaving the VM unbootable and snapshots unusable. This issue often occurs after interrupted copies, unsafe USB removal, or manual misconfiguration.

This guide explains how to detect a missing descriptor, rebuild it manually or with recovery tools, and restore VMFS integrity. You’ll see the exact workflow: stop datastore activity, validate disk structure, repair VMDK descriptor, and recover lost VMDKs with tools like DiskInternals VMFS Recovery™. The focus is on fast restoration of VM functionality and safe extraction of critical data.

Recover Missed VMDK Descriptor: Direct Answer

A VMware virtual disk (VMDK) is not a single file but a pair of components that work together. When the descriptor is missing, the VM cannot boot even though the actual data may still be intact.

A VMDK disk consists of two parts: descriptor file + flat/sparse extent

  • The descriptor file (.vmdk) is a small text file that defines disk geometry, size, parent relationships, and snapshot chain references.
  • The flat or sparse extent file (-flat.vmdk or -s001.vmdk) contains the actual binary data of the virtual disk.

If descriptor is deleted or corrupted, the flat disk usually remains intact

  • The VM will fail to start because VMware cannot interpret the raw extent file without its descriptor.
  • However, the data inside the flat file is still present and can be recovered if the descriptor is rebuilt correctly.

Recovery requires rebuilding descriptor metadata and re‑linking snapshots

Administrators must recreate the descriptor file with accurate parameters:

  • Disk size (in sectors)
  • Geometry (cylinders, heads, sectors)
  • Disk type (thin, thick, sparse)
  • Parent snapshot references (if applicable)

Once rebuilt, the descriptor must be linked back to the snapshot chain to restore VM consistency.

Incorrect geometry or CID breaks VM boot and snapshot chain

  • Even small errors in the descriptor — such as mismatched cylinder/head/sector values or an incorrect CID (Content ID) — will prevent VMware from attaching the disk.
  • A wrong CID breaks the snapshot chain, making rollback impossible and potentially corrupting the VM state.

What Is a VMDK Descriptor File?

The VMDK descriptor file is a small but critical component of every VMware virtual disk. It acts as the metadata layer that tells VMware how to interpret the raw disk data stored in the flat extent file. Without it, the hypervisor cannot attach or boot the virtual machine.

Descriptor vs Flat Disk

Small text‑based metadata file

  • The descriptor (.vmdk) is only a few kilobytes in size.
  • It contains human‑readable parameters that define the disk’s structure and relationships.

References flat extent file

  • The descriptor points to the associated -flat.vmdk or sparse extent file, which holds the actual binary data of the virtual disk.
  • This link ensures VMware knows where the VM’s data resides.

Contains disk geometry, CID, parent CID, adapter type

  • Geometry: Cylinders, heads, and sectors that define the disk layout.
  • CID (Content ID): A unique identifier for the disk state, used to track snapshots.
  • Parent CID: Links the disk to its parent snapshot, maintaining the snapshot chain.
  • Adapter type: Specifies the virtual controller (IDE, SCSI, NVMe) used to attach the disk.

Critical Fields Inside Descriptor

ParameterPurpose
RW valueDisk size in sectors
CIDCurrent disk ID
parentCIDSnapshot relationship
createTypeDisk provisioning type
ddb.adapterTypeController type (lsilogic, pvscsi, ide)

Symptoms of a Missing or Corrupted Descriptor

When the VMDK descriptor file is missing or damaged, VMware cannot interpret the flat disk file correctly. The following errors and behaviors are the most common indicators:

“File not found” error

  • VMware reports that the .vmdk file cannot be located, even though the flat extent file still exists.

VM fails to power on

  • The virtual machine refuses to start because the hypervisor cannot attach the disk without its descriptor metadata.

Snapshot chain error

  • Active snapshots break since the descriptor contains the parent/child relationships needed to maintain the chain.

CID mismatch

  • The Content ID (CID) in the descriptor does not match the expected value, causing VMware to reject the disk or snapshot.

“Cannot open the disk” message

  • A direct error from VMware indicating the descriptor is invalid, missing, or points to the wrong extent file.

Invalid or unsupported virtual disk format

  • VMware interprets the disk as corrupted or in an unsupported format because the descriptor’s geometry or adapter type is incorrect.

Common Causes of Missed VMDK Descriptor

A missing or corrupted VMDK descriptor file usually results from human error or datastore instability. Understanding the root causes helps administrators prevent recurrence and plan safer recovery workflows.

Accidental deletion in datastore browser

  • The descriptor file is small and often mistaken for an unnecessary text file.
  • Deleting it while cleaning up snapshots or VM files leaves the flat disk orphaned.

Storage failure on VMFS

  • Hardware issues or sudden power loss can damage metadata structures.
  • Descriptor files are more vulnerable because of their small size and critical role.

Snapshot consolidation interruption

  • If consolidation is interrupted (e.g., host crash, USB removal, or manual cancel), snapshot descriptors may not update correctly.
  • This breaks the parent/child chain and leaves disks inaccessible.

Manual disk copy without descriptor

  • Copying only the -flat.vmdk file to another datastore without its descriptor results in an unusable disk.
  • VMware requires both files to interpret and attach the virtual disk.

Datastore corruption

  • VMFS corruption from unsafe device removal, failed writes, or hardware faults can damage descriptor metadata.
  • Even if the flat file remains intact, the missing descriptor prevents VMware from mounting the disk.

Manual Method to Recover Missed VMDK Descriptor

When the descriptor file is missing, recovery often requires manually recreating it. This process demands precision, as even small errors in geometry or CID values can prevent VMware from attaching the disk.

Step 1 — Identify the Flat or Delta Disk

  1. 1. Locate the -flat.vmdk (main extent file) or -delta.vmdk (snapshot extent file) in the datastore.
  2. 2. Verify the disk size from file properties or by running ls -lh in the ESXi shell.
  3. 3. Confirm which file is the active disk versus snapshot extents to avoid rebuilding the wrong descriptor.

Step 2 — Determine Disk Geometry

  1. 4. Calculate the RW sectors:

\mathrm{RW\ sectors}=\frac{\mathrm{Disk\ size\ in\ bytes}}{512}

  1. 5. Since VMware uses 512‑byte sectors, this gives the correct size entry for the descriptor.
  2. 6. Confirm the provisioning type (thin, thick, or sparse) by checking datastore properties or VM configuration.
  3. 7. Note whether the disk is standalone or part of a snapshot chain.

Step 3 — Recreate Descriptor File

  1. 8. Use a template from a similar VM or an older backup descriptor as a starting point.
  2. 9. Adjust critical fields:
  • Disk size (RW sectors)
  • Extent type (flat, sparse, delta)
  • Adapter type (e.g., lsilogic, ide, nvme)
  • CID and parentCID values to maintain snapshot chain integrity
  1. 10. Save the recreated descriptor with the same name as the missing .vmdk file.

Example snippet of a recreated descriptor file:

# Disk DescriptorFile version=1 CID=12345678 parentCID=ffffffff createType="vmfs" # Extent description RW 41943040 FLAT "disk-flat.vmdk" 0 # Disk geometry ddb.geometry.cylinders = "2610" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.adapterType = "lsilogic"

Step 4 — Validate With vmkfstools

  1. 11. Run vmkfstools -e to examine disk integrity.
  2. 12. If errors are detected, adjust geometry or CID values until VMware accepts the descriptor.
  3. 13. Use vmkfstools -x repair for minor structural inconsistencies.
  4. 14. Once validated, attach the disk back to the VM and test boot.

Recovering Snapshot Chains With Missing Descriptors

When a snapshot descriptor is missing or corrupted, VMware loses the ability to track the parent‑child relationship between disks. Recovery requires carefully rebuilding the chain and ensuring CID values match correctly.

Snapshot Dependency Structure

Base disk

  • The original -flat.vmdk file that contains the full VM data.

Delta disks

  • Snapshot files (-delta.vmdk) that store changes since the snapshot was taken.

Parent‑child linkage

  • Each delta disk references its parent via the descriptor file.
  • The chain must remain intact for VMware to merge or roll back snapshots.

CID and parentCID Matching

How mismatch breaks chain

  • Each VMDK has a CID (Content ID) that uniquely identifies its state.
  • The parentCID in a snapshot descriptor must match the CID of its parent disk.
  • If these values are mismatched, VMware cannot follow the chain, leading to errors like “Cannot open the disk” or broken consolidation.

Safe correction workflow:

  1. 1. Identify the snapshot hierarchy using datastore files and VM configuration.
  2. 2. Open each descriptor file and check the CID and parentCID values.
  3. 3. Correct mismatches by editing the descriptor so that the parentCID matches the actual CID of the parent disk.
  4. 4. Validate with vmkfstools -e to ensure VMware accepts the corrected chain.
  5. 5. Test consolidation or VM boot only after confirming the chain is consistent.
ScenarioRisk LevelRecommended Action
Base descriptor missingMediumRecreate descriptor
Delta descriptor missingHighRebuild full chain
CID mismatchMediumManual correction
VMFS corruptionCriticalUse recovery software

When Manual Repair Fails

Not every VMDK descriptor issue can be solved by hand. In some cases, the damage extends beyond missing metadata and requires specialized recovery tools.

Extent file partially corrupted

  • If the -flat.vmdk or -delta.vmdk itself is damaged, recreating the descriptor won’t restore lost data.
  • Recovery must target the binary extent file directly.

Snapshot chain incomplete

  • Missing or broken snapshot descriptors leave gaps in the parent‑child hierarchy.
  • Manual CID corrections cannot rebuild a chain when intermediate disks are gone.

Datastore metadata damaged

  • VMFS corruption can prevent VMware from recognizing files correctly.
  • Descriptor repair alone won’t fix broken VMFS structures.

Multiple disks affected

  • If several VMDKs in the same VM are missing descriptors or corrupted, manual recreation becomes impractical.
  • Automated deep‑scan recovery is often the only viable option.

VMFS Datastore Recovery After Descriptor Loss

When a VMDK descriptor file is missing, it often signals deeper issues within the VMFS datastore. Recovery must go beyond simple file recreation and address potential metadata corruption or incomplete writes.

Why Descriptor Loss Often Indicates Larger VMFS Issues

  • Metadata corruption. VMFS relies on metadata to track files; corruption here can cause descriptors to vanish or become unreadable.
  • Incomplete write operations. Interrupted transfers or unsafe device removal may leave descriptors partially written, breaking disk references.
  • RAID degradation. Underlying RAID issues can cause inconsistent blocks, leading to missing or corrupted datastore files.
  • Power outage impact. Sudden power loss during disk operations can damage both descriptors and VMFS journal entries.

Enterprise‑Grade Recovery Workflow

  1. 1. Scan VMFS datastore to detect damaged metadata and orphaned files.
  2. 2. Detect orphaned flat disks that have lost their descriptors but still contain valid data.
  3. 3. Reconstruct VMDK structure by rebuilding descriptors and restoring snapshot chains.
  4. 4. Restore VM configuration files (.vmx, .nvram, .log) to ensure the VM can boot with recovered disks.

Example: DiskInternals VMFS Recovery™

  • Performs a deep scan of damaged VMFS volumes to locate lost or corrupted files.
  • Recovers deleted VMDK descriptor files and re‑links them with flat extents.
  • Restores full virtual machines, including configuration and snapshot hierarchy.
  • Allows administrators to extract files without overwriting production storage, ensuring safe recovery before redeployment.
Tip: How to recover a VMDK from a flat file

Ready to get your data back?

How to recover a VMDK file? To start recovering your data, documents, databases, images, videos, and other files, press the FREE DOWNLOAD button below to get the latest version of DiskInternals VMFS Recovery® and begin the step-by-step recovery process. You can preview all recovered files absolutely for FREE. To check the current prices, please press the Get Prices button. If you need any assistance, please feel free to contact Technical Support. The team is here to help you restore a VM from a VMDK!

FREE DOWNLOADVer 4.28, WinBUY NOWFrom $699

Manual Repair vs Professional Recovery

MethodComplexityData SafetyBest Use Case
Manual descriptor rebuildHighMediumSingle disk issue
Snapshot chain repairVery HighMediumAdvanced admins
VMFS Recovery softwareMediumHighDatastore damage
File extraction onlyLowHighData retrieval focus

Preventing Future VMDK Descriptor Loss

Descriptor loss is often the result of human error or unstable storage conditions. By following preventive measures, administrators can greatly reduce the risk of missing or corrupted VMDK metadata.

  1. 1. Avoid manual deletion in datastore
  • Never remove small .vmdk files without confirming their role.
  • The descriptor may look insignificant but is essential for VM boot.
  1. 2. Consolidate snapshots regularly
  • Long snapshot chains increase the chance of broken descriptors.
  • Regular consolidation keeps the hierarchy clean and reduces dependency errors.
  1. 3. Monitor RAID and VMFS health
  • RAID degradation or VMFS corruption often manifests first as missing metadata.
  • Use monitoring tools to detect early signs of disk or datastore instability.
  1. 4. Keep configuration backups
  • Maintain copies of .vmx, .nvram, and descriptor files.
  • Backups allow quick restoration if a descriptor is accidentally deleted.
  1. 5. Use controlled shutdown procedures
  • Power outages or unsafe host shutdowns can corrupt VMFS metadata.
  • Always shut down ESXi hosts and VMs gracefully to protect descriptors and snapshot chains.

Related articles

FREE DOWNLOADVer 4.28, WinBUY NOWFrom $699