Recovery — Vmfs

First, unmount the datastore (force if necessary).

We’ve all been there. You log into vCenter, click on a datastore, and your heart sinks. Instead of the happy green "Normal" status, you see "Not Mounted" or "Corrupted." Maybe an ESXi host lost power during a SAN firmware update, or someone accidentally deleted a LUN mapping. recovery vmfs

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. First, unmount the datastore (force if necessary)

partedUtil getptbl /vmfs/devices/disks/naa.6000c29c4c5a2b1c If the output is gibberish or empty, the partition table is zeroed out. You need to know the old partition size. Usually, a VMFS datastore uses the entire LUN (Partition starting at sector 2048). Instead of the happy green "Normal" status, you

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 ).