Hi,
We got the same boot message (screenshot below) after rebooting one hosts,
The host was rebooted as after upgrading VC to 5.5 u2d, we got a new FDM package and the package was failing with the following message:
*********************************************************************************************************************
fdm-installer: [43617873] 2015-10-23 06:56:29: Installing the VIB
fdm-installer: [43617873] 2015-10-23 06:56:38: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: Installation Result
fdm-installer: Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
fdm-installer: Reboot Required: true
fdm-installer: VIBs Installed: VMware_bootbank_vmware-fdm_5.5.0-2442329
fdm-installer: VIBs Removed: VMware_bootbank_vmware-fdm_5.5.0-1750787
fdm-installer: VIBs Skipped:
fdm-installer: [43617873] 2015-10-23 06:56:38: There is a pending reboot. Remove the vib...
*********************************************************************************************************************
Tried to reset the server again and it did boot successfully the second time. Even though the server rebooted successfully, We got the following messgae during new FDM agent install:
fdm-installer: [38599] 2015-10-28 05:05:47: Installing the VIB
fdm-installer: [38599] 2015-10-28 05:05:57: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: [InstallationError]
fdm-installer: There was an error checking file system on altbootbank, please see log for detail.
The error is documented in - VMware KB: Remediating an ESXi 5.x and 6.0 host with Update Manager fails with the error: There was an error checkin…
Following the above article i got the following output:
/vmfs/volumes/550d5b11-0aa0a2b1-8c0d-001b21ce6bc0/log # dosfsck -a -w /dev/disks/mpx.vmhba32:C0:T0:L0:5
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/disks/mpx.vmhba32:C0:T0:L0:5: 105 files, 42300/63929 clusters
This in my case there was a possible corruption in the altbootbank partition as FDM agent did install successfully after this.