The command completed silently. She held her breath and typed: partedUtil get … – the table matched the healthy host.
“Partition table,” she whispered. The previous admin had left no documentation, but she knew ESXi stored its boot banks on a small FAT16 partition, then a core dump partition, then a VMFS data partition. If the GPT table got corrupted, the host would see the disk as raw. esxi repair partition table
ls /vmfs/volumes/5d2a8b2e... → all VMs were there. She restarted the VMs one by one. By 2:30 AM, services were restored. The command completed silently
She mounted it: esxcfg-volume -M 5d2a8b2e-fc0f2b10-1234-7845c4f5a9b1 The previous admin had left no documentation, but
Then she used partedUtil get /vmfs/devices/disks/mpx.vmhba0:C0:T0:L0 – it returned garbage: partitions overlapping, wrong end sectors.
She didn’t panic. ESXi has a built-in repair tool: partedUtil fix but only if you know the original partition layout. She didn’t. She did have one clue: a working identical host in the same cluster.
The command completed silently. She held her breath and typed: partedUtil get … – the table matched the healthy host.
“Partition table,” she whispered. The previous admin had left no documentation, but she knew ESXi stored its boot banks on a small FAT16 partition, then a core dump partition, then a VMFS data partition. If the GPT table got corrupted, the host would see the disk as raw.
ls /vmfs/volumes/5d2a8b2e... → all VMs were there. She restarted the VMs one by one. By 2:30 AM, services were restored.
She mounted it: esxcfg-volume -M 5d2a8b2e-fc0f2b10-1234-7845c4f5a9b1
Then she used partedUtil get /vmfs/devices/disks/mpx.vmhba0:C0:T0:L0 – it returned garbage: partitions overlapping, wrong end sectors.
She didn’t panic. ESXi has a built-in repair tool: partedUtil fix but only if you know the original partition layout. She didn’t. She did have one clue: a working identical host in the same cluster.