Failed to enter maintenance mode due to one or more candidate objects for migration being currently inaccessible

[crazych]

Hello

I have V-Sun cluster 5.5 version width 4 hosts

I need to enter one host to maintenance mode width full migration mode, but the host after 5 minutes gives an error message

Failed to enter maintenance mode due to one or more candidate objects for migration being currently inaccessible. Retry operation in a different VSAN data migration mode.

How find problem?

all VMS moved to another host

command vsan.resync_dashboard

2016-12-10 14:39:15 +0000: Querying all VMs on VSAN ...

2016-12-10 14:39:15 +0000: Querying all objects in the system from  ...

2016-12-10 14:39:15 +0000: Got all the info, computing table ...

+-----------+-----------------+---------------+

| VM/Object | Syncing objects | Bytes to sync |

+-----------+-----------------+---------------+

+-----------+-----------------+---------------+

| Total     | 0               | 0.00 GB       |

+-----------+-----------------+---------------+

Please help me

[admin]

Greetings!

On a vSAN enabled cluster, you have below options to choose from while placing a host in Maintenance Mode.

1) Ensure accessibility

2) Full data migration

3) No data migration

Which option you are selecting while placing the host in Maintenance Mode?

Can you please try with "Ensure accessibility" mode and see if the host gets placed in Maintenance Mode successfully?

You can read the difference between "Ensure accessibility" and "Full data migration" at VMware blog - Virtual SAN - Maintenance Mode Monitoring - VMware vSphere Blog‌

_________________________

Was your question answered correctly? If so, please remember to mark your question as "Correct" or "Helpful" when you get the correct answer. This helps others searching for a similar issue.

Cheers!

-Shivam

[crazych]

I need full data migration mode.

the server is in transient mode Ensure accessibility without any problem. The problem is only in full data migration.

[zdickinson]

Good morning, I think the error message is on the nose.  There are inaccessible objects on a diskgroup located on the host you're trying to put into maintenance mode.  I would contact support first.  If you don't have support...

vsan.check_state ~cluster does that show any inaccessible objects?  If so the fix will involve deleting them.  The way to do so can vary on what the objects are.  Can you post the output of the command?  Thank you, Zach.

[SureshKumarMuth]

Hi,

I would strongly recommend to raise a VMware support to resolve the issue to avoid any dataloss. There are tools available to check and clear the invalid components at the vSAN level.

Regards,

Suresh

[crazych]

This log command "vsan.check_state First/computers/V-sun/"

/localhost> vsan.check_state First/computers/V-sun/
2016-12-14 15:15:45 +0000: Step 1: Check for inaccessible VSAN objects
Detected 1 objects to be inaccessible
Detected 327ac757-92a2-269d-e303-d017c2a7afd7 on 172.16.0.12 to be inaccessible


2016-12-14 15:15:45 +0000: Step 2: Check for invalid/inaccessible VMs


2016-12-14 15:15:45 +0000: Step 3: Check for VMs for which VC/hostd/vmx are out of sync
Did not find VMs for which VC/hostd/vmx are out of sync


/localhost>

I don`t have support.

what is "327ac757-92a2-269d-e303-d017c2a7afd7"? disk id? vm id? or another object id?

[SureshKumarMuth]

Check if this article help you in finding the object type

http://www.vryan.co.uk/index.php/2015/10/20/vsan-fixing-inaccessible-objects/

Regards,

Suresh

[crazych]

There is a fix for this but not in the command set for RVC 5.5

I have 5.5 version

I don`t have licensing vCenter server 6.0