Once the partition is recreated, attempt the mount again:

esxcfg-volume -l # Find the volume name esxcfg-volume -U [Volume_Name] Run the repair. You must unmount the volume first, or you will crash the host.

First, unmount the datastore (force if necessary).

vmkfstools -V -r /vmfs/devices/disks/naa.6000c29c4c5a2b1c:1 If the metadata is corrupt (files show up, but VMs won't power on), you need the VMFS Offline Metadata Analyzer ( voma ).

The Virtual Machine File System (VMFS) is incredibly resilient, but it isn't invincible. The good news? You just need to know the right commands and the right order of operations.

Create a new partition (assuming a standard 1MB offset):

voma -m vmfs -f fix -d /vmfs/devices/disks/naa.6000c29c4c5a2b1c:1 voma will scan every file descriptor, fix chain corruption, and rebuild the allocation map. This tool has saved my bacon more times than I can count. Once the repair completes (or the mount succeeds), rescan again and verify the heartbeat.