To recover a host for which a critical failure was detected during system boot.
search cancel

To recover a host for which a critical failure was detected during system boot.

book

Article ID: 312115

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

This article will help to find the cause of the boot failure.


Symptoms:

After bootup/upgrade the host fails to exit the maintenance mode. User can also observe:

  • Event on VC UI:
"A critical failure was detected during system boot. The host is currently not able to exit maintenance mode and run workloads. Refer to VMware KB 93107 for details."                                                       
  • Message on host UI (summary page):

"A critical failure was detected during system boot. The host cannot currently run workloads. Please refer to KB 93107 for more details."

  • Manual attempt to exit maintenance mode also fails with same error:

#esxcli system maintenanceMode set -e=0

A general system error occurred: Cannot exit maintenance mode due to failure during boot.


Environment

VMware vSphere ESXi 8.0.1
VMware vSphere ESXi 8.0.x
VMware vSphere ESXi 8.0.2

Cause

There could be different reasons for the boot failure.
Example: failed to repartition the disk while upgrading from 6.5/6.7 to 8.0U2.

Resolution

To find the cause of the boot failure login to the host and look for the relevant alert message in /var/run/log/vmkwarning.log file and follow the KB mentioned in it. The same alert message can be found on the sysAlert shell (press fn+option+f11) on ESXi DCUI.

Example: 2023-06-15T09:59:20.467Z Al(177) vmkalert: cpu0:1000079885)ALERT: An error occurred while backing up VFAT partition files before re-partitioning. This might be due to VFAT corruption, please refer to KB 91136 for steps to remediate the issue.


Workaround:

The workaround would be specific to the cause of the boot failure. Please refer to the KB specific to the failure.