Inaccessible objects referencing VMs from a different cluster.
search cancel

Inaccessible objects referencing VMs from a different cluster.

book

Article ID: 401615

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

When checking Skyline health or by command line on the ESX hosts, there's no inaccessible objects, but on monitor -  vSAN - virtual objects, we observe inaccessible objects relating to VMs that don't exist in the vSAN datastore 

Environment

VMware vSAN 7.x
VMware vSAN 8.x

Cause

When checking the virtual machines showing as inaccessible, they're running on a completely different vSAN and the VM is referencing two different vSAN datastores below. 

The virtual machine might have an ISO file attached to the VMs from the other vSAN cluster, this is the reason it's showing two datastores.  

Resolution

Detach ISO file from the virtual machines that's referencing the different vSAN datastore.

Just edit settings of the VM and detach the ISO File by selecting X or alternatively, you can select Client Device.