Today I was performing an upgrade of VMware ESXi 5.0 running Dell custom image to 5.1 Dell custom image using VMware Update Manager.
The upgrade seemed to run as usual, but after some time I wondered why the host did not come back up after the automatic reboot.
I went to the console and saw the following error message:
Could not obtain module order from esx image db : Error (see log for more info)
File path of/etc/vmware/oem.xml is claimed by Multiple overlay VIBs: set([‘Dell_bootbank_dell-configuration-vib_5.1-0’, ‘Dell_bootbank_Dell-Configuration-VIB_5.0-0’])
File path of/etc/vmware/support is claimed by Multiple overlay VIBs: set([‘Dell_bootbank_dell-configuration-vib_5.1-0’, ‘Dell_bootbank_Dell-Configuration-VIB_5.0-0’])
Looking up the error in the Dell VMware vSphere 5.0 On Dell PowerEdge Systems release notes some interesting information was revealed.
Apparently there are issues when upgrading from a Dell custom version of ESXi 5.0 to a Dell custom version of ESXi 5.1.
The solution as recommended by Dell is to put the host into maintance mode, logon to the host by SSH, execute the following two commands and reboot:
esxcli software vib remove –n Dell-Configuration-VIB
esxcli software vib remove –n Dell-License-VIB
After the host completed the reboot, I scanned using VMware Update Manager and, as expected, status for my upgrade baseline changed to incompatible. Please see my previous post on how to resolve this.
I then proceeded to remediate using the Dell custom ESXi 5.1 upgrade baseline. At the end I had to go to the console and press ENTER to complete the upgrade.
As always, if this helped you please leave a comment 🙂
Incoming search terms:
- dell esx upgrade failed is claimed by multiple overlay