How to clear Detected Objects Innaccesible

[jgaleano]

Hi Guys.

We are currently having some issues in our VirtualSAN cluster, a week ago we have one host with hardware fail, so we cannot run a full migration, we changed the server with a spare one and insert it to the cluster and create te Disk Group, but that brings more problems that solutions, some VM start to fail and become innaccesible from the vcenter, and the cluster went very slow performance.

Right know we restore a lot of backups and recover most of the data but when we run the comand vsan.check_state we found the following output that prevent the hosts to enter in maintanance mode.

> vsan.check_state ~cluster

2014-11-25 14:17:16 +0000: Step 1: Check for inaccessible VSAN objects

Detected 15 objects to be inaccessible

Detected 42fe3754-208b-4217-e562-002590f94756 on ################## to be inaccessible

Detected 44bf6f54-fc65-4421-a8cf-002590f94756 on ################## to be inaccessible

Detected 0f537054-8351-9a32-1f63-002590f9c36c on ################## to be inaccessible

Detected 807e2054-7cff-cd44-ce6b-002590f94a56 on ################## to be inaccessible

Detected 90703d54-92f5-3958-9068-002590f961ec on ################## to be inaccessible

Detected b6715254-3b30-585d-d01b-002590f961ec on ################## to be inaccessible

Detected f3032a54-7abc-6272-f9a9-002590f961ec on ################## to be inaccessible

Detected d3f35254-3562-0684-28d2-002590f961ec on ################## to be inaccessible

Detected a0664254-735d-1191-7f2e-002590f94a56 on ################## to be inaccessible

Detected e6372054-93b2-3894-eb91-002590f961ec on ################## to be inaccessible

Detected 99c35c54-8cf9-2faa-752d-002590f94a56 on ################## to be inaccessible

Detected 4a8c2054-f486-75b5-b5f7-002590f94756 on ################## to be inaccessible

Detected a7392f54-c40b-51c3-ec69-002590f94756 on ################## to be inaccessible

Detected e7527054-c1a8-4ac9-0466-002590f9c36c on ################## to be inaccessible

Detected 7bde6454-c642-96f6-b13f-002590f961ec on ################## to be inaccessible

2014-11-25 14:17:17 +0000: Step 2: Check for invalid/inaccessible VMs

2014-11-25 14:17:17 +0000: Step 3: Check for VMs for which VC/hostd/vmx are out of sync

Also in the step 3 appears a bunch of VM that we had recovered by backups, but appears to keep out of sync.

We ran the command vsan.check_state -e to recover those machines and this command unregister an re register the vm but does not disappear from the list.

How we can fix this issue to recover the healt status of the VSAN cluster?

I really apreciate your help with this.

Best Regards.

[admin]

Hi,

Please go ahead and file an SR with VMware support for them to review your situation and help you out.

Thanks.

Kiran

[OITVIRT]

We are currently in the same boat and do already have an SR open on it.  Wondering if you can share the steps taken to resolve or what was your experience with support on the problem.

Thanks,

Doug

[jgaleano]

Hi OITVIRT

Well, sadly I have to tell you that the support request that we have open about this issue, has taken a long time to them to analyze the logs and still without an answer yet.

Hope support can help us with this, when they answer us I’ll update here the answer.

[philzy]

May be this could help you Re: Need to identify a VM with the Inaccessible VSAN Objects