1. Attempt Object Repair (If Data Still Exists Elsewhere)
If the object is still available via its mirrored/redundant copy: You can trigger a manual repair: vsan.repair_object -force <object_path>
2. Remove the Failed Disk (If It’s Confirmed Bad)
If the disk has SMART failures, read errors, or can’t be recovered:
Place the host into maintenance mode
Use “Ensure Accessibility” if you don’t have enough free space
Or “Full data migration” if you want full rebuild (requires space)
Remove the disk group using vCenter or ESXCLI: esxcli vsan storage diskgroup remove -d <disk-uuid>
Then you can physically replace the disk and recreate the disk group.
Do not just pull the disk from the server without properly removing it from vSAN — it can destabilize the cluster.