- #HP SMART ARRAY P410I CONTROLLER DRIVER LINUX INSTALL#
- #HP SMART ARRAY P410I CONTROLLER DRIVER LINUX DRIVERS#
It is very important to use this exact order of the files ! Copy back and rename the smx.deb file to hp-smx-provider-500.02.10.13.44-434156.vib. On the Linux console (Putty) walk to the folder with the 3 files and type in the folling command:Īr -r smx.deb descriptor.xml sig.pkcs7 hp-smx-provider tmp) for example with a tool like WinSCP. vib archiv to a folder inside the Linux disk (eg. This can be done on a Linux or Mac OX (with Toolbox) System. The following lines have to be deleted:Īfter that we have to pack the. Inside this archiv is a descriptor.xml file which has to be modified to avoid the "BIOS vendor." error. This file can be extracted with 7Zip, which recognizes it as a Debian Archiv (deb). This is the Smart Array provider and the only file we need. Because of this we can extract the hp offilne bundle zip archiv and move the hp-smx-provider-500.02.10.13.44-434156.vib out of it. The VIB files are now complete installers based on Debian. In the ESXi 4.x Version this was not that problem because you only have to edit the vmware.xml file inside the metadata.zip archiv (delete the unused vib sections and the hwPlatform lines) but with ESXi 5 we have a new format for the offline bundles and VIB files. Because of this HP blocks the installation with the hint "BIOS vendor HP ist required but host BIOS vendor is.". Ilo drivers) which may be problematic on non HP hardware (PSOD).
#HP SMART ARRAY P410I CONTROLLER DRIVER LINUX DRIVERS#
The CIM providres are only available as part of the " HP ESXi Offline Bundle for VMware ESXi 5.0" which contains also other HP specific drivers (eg.
#HP SMART ARRAY P410I CONTROLLER DRIVER LINUX INSTALL#
As a result there was not health status from the P410i controller any more which is not acceptable for a production server.īecause the Smart Array controllers were also sold separatly we could not imagine that there might be a problem to install CIM providers for this controller, but this was wrong. For this task we could only use the standard VSphere 5 installation ISO and not the HP version of it. For the upgrade to VSphere 5 of our existing HP Prolient servers we wanted to use newer Supermicro Units but stay with the Hp Smart Array P410i controllers and disks we had before.