To verify and validate that this was caused by the update and that the driver wasn’t actually part of my 6.5u1 installation I went to the esxupdate logs in /var/log/esxupdate.log esxupdate: 15329961: BootBankInstaller.pyc: INFO: Copying /bootbank/intelcim.v00 to /tmp/stagebootbank/intelcim.v00 In that updated driver it clearly says “ This issue is only encounter when upgrading to version 2018.09.31 (5.5.0.66-1). I did a quick search and found that there is a newer driver from HPE with the title I had the latest HPE SPP, so I applied it on the system but still, the ESXi couldn’t recognize the array controller. At this point in time and even before logging in to the system I knew something broke *YIKES* and at that point in time my wife had plans to go out with the kids and I had around 30 minutes before I start getting threats of unplugging the home-lab cabinet from power :-P. Since we were on 6.5 and not on the 6.7 GA I couldn’t use the “ esxcli software vib update” command and I had to use the “ esxcli software vib install” command instead because it complained about the esx-base image.Īfter the upgrade was done, the server booted but the system fans kept screaming.

In the lab usually I attempt different ways of upgrading the hosts, so that (1) to keep my know-how around the client fresh, (2) to make sure that things actually work as they’re expected as if I was going to do them for a customer.įor this specific server I used the offline bundle ( HPE Gen9 Plus Custom Image for ESXi 6.7 Update 2 Offline Bundle). This host was on 6.5u1 and based on the upgrade path in the interoperability matrix a single shot upgrade is supported. I’ve been busy for the past two days upgrading my home lab to 6.7 U2 and one of my servers is a ProLiant ML150 Gen9 and its RAID controller is a B140i.

Vmware esxi 6.7 u2 hpe custom image