inaccessible virtual objects on vSAN cluster.

Products

• VMware vSAN

Issue/Introduction

Inaccessible virtual objects on vSAN cluster showing under vSAN cluster > Monitor > Virtual Objects:

On verification, you may see that these inaccessible objects do not belong to any of the active VMs running in the vSAN cluster.

We can look at the object state and match the vmdk path UUID to the group UUID of the object from the below commands.

esxcli vsan debug object list --health=inaccessible - To get the list of only the inaccessible objects

Match this with the path of the hard disk under Edit Settings:

We can see in the above images that the path UUID does not match with the group UUID of the inaccessible objects.

Environment

vSphere vSAN 7.x

vSphere vSAN 8.x

Cause

vSAN objects become inaccessible when there are not enough Active components due to the lose of Fault Doamins that exceeds the storage policy's Failures to Tolerate to keep the object accessible.

• This can happen if hosts are in vSAN Decom/ESXi maintenance mode
• Failed disks/disk groups
• Network partition
• vSAN cluster shutdown/restart is in an inconsistent state
• VM restored from backup and stale components remains in the vSAN datastore.

Resolution

After verifying all the objects, we can suggest removing the inaccessible objects if they are not needed anymore.

Kindly open a Broadcom Support ticket for further assistance in removing the unwanted objects.