esxcli storage filesystem list | grep unmounted esxcli storage filesystem mount -l "DatastoreName" When restoring from a storage snapshot to the same host that sees the original LUN:
If voma reports errors, proceed to repair. voma -m vmfs -f fix -d /dev/disks/naa.600xxxx:1 ⚠️ Warning : voma -f fix can make data unrecoverable if used incorrectly. Run only after voma -f check confirms specific recoverable errors (e.g., invalid heartbeat, orphaned inode). 3.3 Recover from Backup of VMFS Metadata If you have a metadata backup from dd : recovery vmfs datastore
1. Initial Diagnosis: Identify the Problem Before attempting recovery, determine the exact state of the datastore. esxcli storage filesystem list | grep unmounted esxcli
# Check filesystem (no repair) voma -m vmfs -f check -d /dev/disks/naa.600xxxx:1 Advanced Recovery (VMFS Metadata Repair) 3
# List available partitions partedUtil get /dev/disks/naa.600xxxx partedUtil set /dev/disks/naa.600xxxx 1 0xFB 0 104857600 Reload partition table partedUtil fix /dev/disks/naa.600xxxx 3. Advanced Recovery (VMFS Metadata Repair) 3.1 Check & Repair File System (Read-Only First) From ESXi shell (requires SSH):
# Identify the snapshot LUN esxcfg-volume -l esxcfg-volume -m <UUID_of_snapshot> 2.4 Recover a Deleted Datastore (Partition Table) If the VMFS partition table is lost but data intact: