Inaccessible Objects in VSAN

Products

• VMware vSAN

Issue/Introduction

• Inaccessible objects found showing for Unknown object type.
• Checked all VMs and their object health state shows Healthy.
• Followed the Skyline recommendation which tried to purge the inaccessible vSAN objects, but the vCenter UI wizard is did not find any VM swap objects to remove.

Environment

vSAN

Cause

An investigation with the help of Broadcom vSAN Support  was conducted to identify the inaccessible objects. It was determined that the objects were associated with a failed physical vSAN storage disk that was previously replaced.

The inaccessible objects should have been deleted when the disk was deleted but there was a unidentified health issue with all hosts communicating in the cluster at the time of the cleanup task which allowed vSAN object component UUIDs to be readded in the vSAN CMMDS library as ghost/unassociated objects. The identity data that is given to objects by vSAN was removed when disk clean up took place but the 3 components were not removed because of the non-availability of the disk at the time of the cleanup task.

Resolution

Open a case with Broadcom Support.

With the assistance of Broadcom vSAN Support Engineer the objects can be safely identified and removed. Once the objects were removed the Skyline health alarm returned to a green health state.

Additional Information

For further definitions on vSAN Inaccessible objects please see the following:

vSAN Health Service - Data Health - vSAN Object Health - inaccessible objects