Portal Home > Knowledgebase > VMware Knowledge Base > UCS Blade loses configuration after reboot in VMware ESXi 5.0.x

UCS Blade loses configuration after reboot in VMware ESXi 5.0.x


  • UCS Blades booting from FCoE/iSCSI SAN revert to a previous state after reboot.
  • The ESXi 5.0 Bootbank points to /tmp and/or no altbootbank exists.
  • You are unable to install VMware Tools in virtual machines.
  • You are unable to patch/update ESXi 5.0.
  • A task fails with:

    The host returns esxupdate error code: 15. The package manager transaction is not successful.
    Could not install patches on

  • In the esxupdate.log, you see messages similar to:

    esxupdate: ERROR: InstallationError: ('Current bootbank /bootbank is not verified and most likely a serious problem was encountered during boot, it is not safe to continue altbootbank install. bootstate is 2, expected value is 0.')

    esxupdate: HostImage: DEBUG: Live image has been updated but /altbootbank image has not.  This means a reboot is not safe.

    esxupdate: HostImage: INFO: Installer was not initiated - reason: altbootbank is invalid: Error in loading boot.cfg from bootbank /bootbank: Error parsing bootbank boot.cfg file /bootbank/boot.cfg: [Errno 2] No such file or directory: '/bootbank/boot.cfg'


The FCoE device discovery may take longer than expected, and when the restore-bootbank jumpstart plug-in starts, the bootbank partition on the FCoE LUN is still not available.


This is a known issue in VMware ESXi 5.0.x. A resolution for this issue is being evaluated for inclusion in a future release.

If you are experiencing this issue, open a Support Request.
To work around this issue, reinstall from local storage.

Based on VMware KB 2031315

Also Read