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

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• 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 hostname
  
  
• 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 <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> 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'

Environment

VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.0

Cause

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.

Resolution

This issue is resolved in ESXi 5.0 Update 2 and ESXi 5.1.

ESXi 5.0 Update 2 is available to download from VMware Downloads. For more information, see the VMware ESXi 5.0 Update 2 Release Notes.

ESXi 5.1 is available to download from VMware Downloads. For more information, see the VMware ESXi 5.1 Release Notes.

Additional Information

UCSブレードサーバ上のESXi5.0.xを再起動すると、構成情報が消失する