Search the VMware Knowledge Base (KB)
View by Article ID

Initializing vSAN during boot takes a longer time (2149115)

  • 1 Ratings

Symptoms

  • A vSAN cluster ESXi host stops responding during a reboot.
  • On the DCUI screen you see a message similar to:

    VSAN Initializing SSD: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX Please wait...

Resolution

This is an expected behavior when rebooting a vSAN host. At this stage of the reboot, the ESXi host (vSAN) processes all log entries to generate all required metadata tables.

The time taken to complete this task will depend on the load and the number of log blocks in the write buffer before the host was rebooted.

Note: A further reboot of the host in this state should be avoided. This task can take some time to complete. In the worst case scenario, under normal load and healthy conditions when there are large amounts of data in the write buffer, it may take up to an hour (per disk group) to complete the task.

Ensure if the ESXi host is making progress:
  1. Using the DCUI console press Alt + F11.
  2. 2. If you notice similar messages then the vSAN host is making progress and does not need a hard boot:

    2017-02-02T04:53:38.287Z cpu13:33631)LSOMCommon: SSDLOGLogEnumProgress:1168: Estimated time for recovering 1542499 log blks is 185229 ms device: mpx.vmhba1:C0:T1:L0:2
    2017-02-02T04:53:38.288Z cpu26:33632)LSOMCommon: SSDLOGLogEnumProgress:1168: Estimated time for recovering 1350623 log blks is 163589 ms device: mpx.vmhba1:C0:T0:L0:2
    2017-02-02T04:54:43.366Z cpu34:33253)PLOG: PLOG_Recover:760: Doing plog recovery on SSD mpx.vmhba1:C0:T1:L0:2
    2017-02-02T04:57:18.154Z cpu28:33633)LSOMCommon: SSDLOGEnumLog:1311: PLOG: Total Time: 154787953 us, Read Time: 114793757 us, Process Time: 81268242 us, numReads: 999141
    2017-02-02T04:57:18.521Z cpu36:33255)PLOG: PLOGRecDisp:701: PLOG recovery complete 52451a31-830b-86ed-6fc5-ce32eebff076:Processed 5742172 entries, Took 155155 ms


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Notes:
  • This task may fail if there is a underlying issue with the SSD.
  • If Alt +F11 is not working then enable serial logging for the instances before going for a hard reboot. For more information on serial logging, see: Enabling serial-line logging for ESXi 5.x (1033888).

Additional Information

Long boot times may also occur if you are experiencing issues with component metadata health. For more information, see Component metadata health check fails with invalid state error (2145347).

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: