With the rollout of ESX6.0 Update 2 (build number 362759) VMware has bundled a new VIB for the VMware VSAN in the update.
Previously there was no VSAN VIB included the ESXi Image and if you trying to upgrade your host using esxcli with this command
esxcli software vib update -d "/vmfs/volumes/bnesx03-localstorage/ESXi-6.0.0-4192238-6.0.10.zip"
Tthe process will fail with this error message:
VIB VMware_bootbank_esx-base_6.0.0-2.34.xxxxx requires vsan << 6.0.0-2.35, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_esx-base_6.0.0-2.34.xxxxxx requires vsan >= 6.0.0-2.34, but the requirement cannot be satisfied within the ImageProfile.
I tried the good old esxcli -f command to force the update. It seemed to do the trick until I rebooted the host and it hung during in initialization process. It never moved passed the “user loaded successfully” message you see in the screenshot.
Once I rebooted the hung host it reverted back to the pre-upgrade build version
So I changed tack and used the following esxcli -n option to specifically install the VSAN health as well as the ESXi OS from the .zip file as opposed trying to update a non-existent VIB.
esxcli software vib install -n esx-base -n vsan -n vsanhealth -d "/vmfs/volumes/bnesx03-localstorage/ESXi-6.0.0-4192238-6.0.10.zip"
On reboot of the host, the hypervisor loaded without issue. I then reran the update command to finish off the upgrade and update rest of the VIBs.
esxcli software vib update -d "/vmfs/volumes/bnesx03-localstorage/ESXi-6.0.0-4192238-6.0.10.zip"
No issues were encountered after the reboot.
https://cliffcahill.com 
Hey, just wondering if you have some thoughts on this…..
I have a bunch of ESXi hosts all running on local storage and the storage is limited on each, just a couple of 100 GB remaining on each host so I don’t have the room to migrate machines around to clear out any hosts.
I need to upgrade to 6.0 U3 from 5.0.0 but weary of doing any in place upgrade while there are VMs still on it, shut down of course.
Would I be better off moving the VM files off to a NAS first? I have Veeam backups just in case.
Thanks
LikeLiked by 1 person
Have done plenty of in-place upgrades Its non distributive to the datastores and the esxi partitions are separate from VMFS volume that is mounted on your host. I would check the HCL to ensure your hardware is compatible with 6.0U3.
LikeLiked by 2 people