Yeah, I had to burn to Disc as well.
I found that if you boot the ISO from the Virtual Media mount of the iLO, it will install.
I also confirmed that the VMware-ESXi-5.5.0-1331820-HP-5.70.38-Sep2013.iso build does not have any problems booting from USB media, only the VMware-ESXi-5.5.0-1331820-HP-5.71.3-Sep2013.iso
There is about a 10 MB difference between the two ISOs.
I did confirm both SHA1 checks on each of the respective ISOs.
I called and opened a case with HP informing them of this specific problem, so perhaps they will fix it on the next build release.
I also ran into this exact issue on an HP DL360 G5 and an IBM X3400 M3 using a USB to install 5.5, 5.1 worked as well. I ran it off of CD and it installed fine. Seems this is the workaround for everyone so far.
i met the same issue on my test server. (dell)
i used ultraISO to write the ISO image into usb drive and it failed to install with lsi_mr3.v00 error message as mentiond above.
I tried the resolution above (delete and then copy rename the file) , it didn't work for dell server.
I don't have a CD rom on the server, and I found if you write the ISO using another tool (Rufus), it went through smoothly.
Hope this helps.
I can confirm using Rufus to create the bootable USB stick works.
Thanks Freed0mFigter, just want to 2nd your post (and the result from following your post) the Rufus to create the bootable USB stick works for me as well.
hi folks. Have tested UltraISO and Rufus with "VMware-VMvisor-Installer-5.5.0.update01-1623387.x86_64" and "VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014" on my HP GL360 G5 with HP P800 controller on board. Both ISOs work fine after Rufus and none after UltraISO (error messages and other bugs mentioned earlier).
Rufus might complain about old image loader and offers to download/upgrade one, so press "YES" and upgrade it otherwise the ISO won't boot.
ESXi might complain about "The Execute Disable/No Execute CPU feature is not enabled for this machine", so before installation enable that feature in BIOS under CPU options.
This issue still occurs if you try to create the bootable USB media manually, even with the newest HP custom 5.5 image (june 2014). I'm provisioning a pair of DL380G8s with the 420i controller and ran into it.
Rufus saves the day. create the USB drive with Rufus and everything works as intended. Burning CDs doesn't work for systems without that drive.
Great call on suggesting Rufus. That makes the bootable media much easier to maintain.
Thank you so much for recommending using Rufus. I encountered the same problem with a Dell Precision 490 and using Rufus saved the day!
Same issue here, with LILO... Other programs such as unetbootin doesn't work either (no boot at all !)
But yeah, fortunately, I've just tested Rufus, and it does perfectly the job !
This sollution 100% work for me. Thank you!
Original vmware iso file "VMware-VMvisor-Installer-5.5.0.update01-1623387.x86_64"
IBM System X 3650
Installation from iLO using the img file works fine for me.
We were getting false positive bad memory errors on 2 of our ESXi 5.5 blades. HP Support suggested updating the vibs with this file hp-esxi5.5uX-bundle-2.4-16.zip. After running the install and rebooting we haven't had any additional reported memory errors, but today when I rebooted the same host it is now stuck on the same "loading module ipmi_si_drv ..." screen that most of the other admins are seeing.
So I figured I would try to upgrade to the latest and greatest HP Branded ESXi 5.5 version. During the upgrade, guess what??, yup, I'm stuck on the loading module ipmi_si_drv ... screen.
I wonder why this didn't happen during the reboot after we patched the vibs?
Any suggestions? What functionality do I lose if I uninstall/delete the ipmi_si_drv module?
Since this is a Blade and the error seems to be iLo related I decided to shudown and pull the blade from the chassis. I waited 30 seconds and pushed it back in. No error on boot??? I also rebooted again to see if I would get the error. It rebooted FINE..