The vSAN datastore is not visible in the vSphere Client following a host PSOD or firmware upgrade on ESXi 8.0.3.

Products

• VMware vSAN

Issue/Introduction

• vSAN datastore is not visible or mapped in vSphere Client.
• Running esxcli vsan cluster get returns: vSAN Clustering is not enabled on this host.
• Service daemons clomd and osfsd are not running.
• The host is running VMware ESXi 8.0.3 (Build 24674464).

Environment

• VMware ESXi 8.0.3 (Build 24674464)
• VMware vSAN (OSA or ESA)

Cause

The local node loses its runtime clustering membership configuration state during a crash or firmware flash sequence. This disables core orchestration services and prevents the storage layer from registering the vSAN topology.

Resolution

To restore storage accessibility, manually force the host to rejoin the existing cluster.

1. Log into a healthy host in the same cluster via SSH.

2. Retrieve the active Sub-Cluster UUID: 

         esxcli vsan cluster get | grep -i "Sub-Cluster UUID"

     3. Log into the affected host (Esxi_hostname) via SSH.

4. Run the join command using the UUID retrieved in step 2:

• For vSAN OSA: esxcli vsan cluster join -u <Sub-Cluster_UUID>

• For vSAN ESA: esxcli vsan cluster join -x -u <Sub-Cluster_UUID>

5. Verify the host state: 

         esxcli vsan cluster get 

         Confirm the Local Node State reflects AGENT or MASTER and the Sub-Cluster Member Count is correct.

6. Exit Maintenance Mode and verify datastore visibility.

Note: Fixed in release ESXi 8.0 Update 3 and higher.