When attempting to add a fully rebuilt or repurposed ESXi host to a vSAN cluster, the operation fails with a "General system error." Specifically, the error message indicates a failure during the vSAN cluster join process, often referencing a "Sysinfo operation" or a failure to join the host in the vSAN cluster.
Symptoms can include one or multiple of the following:
esxcli vsan cluster get may still show unexpected or stale cluster configuration or membership information despite the host being "rebuilt."
vSAN (All)
Even after a full OS reinstallation, residual vSAN metadata or partition information can persist on the local disks or the ESXi configuration layer. This leftover data causes the host to report itself as still belonging to or being "vSAN enabled" or has a disk format version for the previous cluster, which conflicts with the new cluster's configuration during the join operation.
To resolve this issue, the residual vSAN configuration must be explicitly cleared from the host before it is added to the new cluster.
Verify vSAN Configuration: Connect to the ESXi host via SSH and run: esxcli vsan cluster get Note: If the output shows enabled vSAN clustering or lists a Sub-Cluster UUID, the host will need to be removed from the stale cluster
Force the host to leave its perceived vSAN cluster state: esxcli vsan cluster leave
Check for Residual Partitions (If applicable): If the issue persists, use partedUtil to inspect disks for legacy vSAN partitions that may not have been fully erased during the rebuild by checking the disk partitions through vCenter UI
navigate to the ESXi host.
Click the Configure tab.
Under Storage, click Storage Devices.
Re-attempt Cluster Join: After verifying the host is no longer in a cluster and has no vSAN partitions proceed to add the host to the new vSAN cluster via the vSphere Client.