VMware Cloud Community
vvenu
Enthusiast
Enthusiast

Enter Maintenance Mode

Has any seen this?

Enter maintenance mode stuck at 91% - Details shows as "Entering VSAN maintenance mode." I have to hard boot the server.

Build 3620759

Reply
0 Kudos
10 Replies
BoneTrader
Enthusiast
Enthusiast

can you tell us a bit more about your Setup?

Reply
0 Kudos
vvenu
Enthusiast
Enthusiast

Environment: 2 ESXi hosts running 6.0 U2 booting from local SATA HDD

These are Dell R710 servers each has 64 Gb ram using Emulex LPe12000 for storage

vCenter is also running on latest U2

Let me know if you need any other info.

Thanks

Reply
0 Kudos
bcalverthca
Contributor
Contributor

I am seeing the same problem.  I have updated to U2 successfully on 8 of 8 lab servers, and 15 of 17 QA servers, but the last 2 QA servers are both getting on the task Enter Maintenance Mode, at 91% with status Entering VSAN maintenance mode.  HP blade servers BL660c Gen 8 that are running 6.0 U1b from the HP custom image.  All VMs are cleared from the host, and we are not even using VSAN.  The hosts are boot from SAN. 

The command times out after 30 minutes as you would expect.

Reply
0 Kudos
bcalverthca
Contributor
Contributor

I can't really explain what was broken, but I restarted management agents on one of the hosts, and used the command from SSH to enter maint mode and it worked.  I didn't try to do it from the vSphere client after restarting agents.

esxcli system maintenanceMode set -e True

Reply
0 Kudos
vvenu
Enthusiast
Enthusiast

Weird thing is when you deploy a VM,  You will notice a task "Retrieve a ticket to register the virtual SAN VASA Provider" and gets completed with no errors even though VSAN is not enabled

This seems more like a BUG Smiley Happy

Reply
0 Kudos
Zimeon
Contributor
Contributor

Had the same issue weith ESXi 5.5 build 2718055 with a host getting stuck at 91% while entering maintenance mode. Operation timed out while entering VSAN maintenance mode while not having VSAN in use.

Restarting management agents and retrying entering maintenance mode solved the issue.

Reply
0 Kudos
danielmgrinnell
Enthusiast
Enthusiast

Restarting the Management Services fixed it for me

Cancel the Maintenance Mode, SSH to host Run this services.sh restart and try again should fix it.

Thanks

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

You can restart hostd and vpxa but I would not suggest go with services.sh restart. It may break things further sometimes and when you have LACP is configured, it is definitely not recommended.

https://kb.vmware.com/s/article/1003490?language=en_US

Warning: If LACP is configured on the vSAN network, do not restart management agents on ESXi hosts running vSAN.

  • Restarting the management agents may impact any tasks that are running on the ESXi host at the time of the restart.
  • Check for any storage issues before restarting the Host deamon hostd service or services.sh

Thanks,

MS

batuhandemirdal
Enthusiast
Enthusiast

Hi,

if there is no server on it, do you try to close it manually?

Reply
0 Kudos
Alvaidas
Contributor
Contributor

Make sure there is no Virtual machines on the host. If there is just migrate them to different host, this will enter the host in the maintenance mode, and error will go away.

Thanks

Reply
0 Kudos