Recently I installed three equal IBM server x 3650 machines with VMware and installed and connected two QLogic HBA’s in each server.
After installing ESX I ran into a problem with one of the machines trying to connect to the datastores. Two of the machines perfectly could see all presented luns after a rescan. One machine however, did not even see a card, no WWN’s available. At first I thought the Storage guy made some mistake in presenting the LUNs, so I called him right away, but he assured me that the faulty machine was targeted. So the investigation continued…
Some quick searches on Google did not bring me any further than pointing me at the HBA config-utility that is initialized at boot time to look if there’s something wrong with the HBA.
While rebooting the host I was looking for the QLogic banner which was not appearing, but instead of a banner I got an error message:
PCI device resource allocation error:
Next when booting into the Console screen there also turned up an error:
When I saw these errors I was not happy assuming I had an hardware issue/failure.
When I googled on the specific error message I just got a few hits, one of them (from a IBM developer site I believe) stated that there is a limited amount of memory available to load ROM bios-apps, and if you have a lot of devices like RAID controllers, HBA controllers, network controllers etc. you may reach a point to where a device ROM BIOS will not load. He also suggested to turn off unneeded ROM BIOS apps/PXE boot options.
Because I indeed have up to four nics AND a RAID controller AND two H’BA’s, I went into the BIOS and turned off the PXE boot option of the onboard nics in the BIOS:
After the PXE was disabled on the onboard nics, the system apparently had enough resources to load the Qlogic Firmware and also ESX was able to load the driver and see the presented LUNs and booted normally (as the others).
6 comments