ESXi host loses complete or partial configuration after a reboot
book
Article ID: 306902
calendar_today
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
This article provides information about:
The ESXi boot process
The impact of an unclean shutdown or reboot
Symptoms:
ESXi host loses complete or partial configuration after a reboot
Environment
VMware vSphere ESXi
Cause
This issue can occur after an unclean shutdown or reboot.
Resolution
These steps outline the process for saving configuration settings. Interruption during the process can lead to a loss of configuration settings.
auto-backup.sh, a cronjob that is executed the first minute of every hour, saves the configuration state of the ESXi host.
All configurations modifications are primarily written to /bootbank.
In the event of VIB updates/installation the operating system related binaries and configuration files are copied over to /altbootbank.
Note: Silent VIB updates may occur. You can validate if these have occurred using Log -/var/log/esxupdate.log and the configuration file in bootbank or altbootbankboot.cfg.
Configuration files are saved in the file state.tgz.
A known good state is saved in /bootbank prior to the update.
If there have been updates/installations, on a subsequent reboot, ESXi boots off /altbootbank from the saved/modified state. This is achieved by updating boot.cfg file.
Early in the boot process, the higher value for bootstate is chosen from the two bootbanks. Later in the boot process, the symbolic link /bootbank is created to point to the bootbank the host booted from, and /altbootbankis created to point to the secondary bootbank. The two bootbanks swap their name on the first boot after an upgrade.
At the end of the boot process,the jumpstart script resets the bootstate to 0.
If the host is rebooted recursively or the reboot process is interrupted, the ESX host boots into the previous state, causing the differential configuration of bootbank and altbootbank to be lost.