Recho
Contributor
Contributor

Install VMware ESXi 5.5.0 issue on HP ProLiant DL380p Gen8

Hello

Are there any experts who have experience on installing ESXi 5.5.0 on HP ProLiant DL380p Gen8 Server?

We got the stuck at loading lsi_mr3.v00, the installation process cannot be continue...

We are using the bootable USB to install it. seems not the USB issue as we've tried several USBs and got the same issue.

We have also applied the HP_Service_Pack_for_Proliant_2013.09.0-0_744345-001_spp_2013.09.0-SPP2013090.2013_0830.30.iso to update the server fireware but still failed as before.

We are using both the VMware-ESXi-5.5.0-1331820-HP-5.71.3-Sep2013.iso and VMware-EXSIVMvisor-Installer-5.5.0-1331820.x86_64.iso to make the bootable USB, both have the same issue

Could you please help us with that?

Screenshot attached.

Thanks

Recho

27 Replies
admin
Immortal
Immortal

@Recho, Welcome to the community..!!!

Its looks like a hardware/firmware issue.
Did you checked your hardware and hardware drivers are supported and listed in HCL .. ?

Could you try to downgrade your firmware to the below version of what it had earlier, and then try booting again .?

~dGeorgey

0 Kudos
Recho
Contributor
Contributor

Thanks dGeorgey for your help

Actually I've tried old version fireware, it didn't work for me. I've also tried 5.1 version. It worked for me.

I am guessing that the loading lsi_mr3 looks like a lsi manager related code but not sure what lsi is?

Thanks

Recho

0 Kudos
admin
Immortal
Immortal

lsi_mr3 is MegaRAID SAS Invader Controller driver which is a new addition in 5.5, which was not there in 5.1 that why 5.1 installation went successful.


~dGeorgey

0 Kudos
admin
Immortal
Immortal

Otherway which you can try is;

Build the iso with latest driver available in lsi  http://www.lsi.com/products/raid-controllers/pages/megaraid-sas-9260-4i.aspx#tab/tab3   and flash existing one and apply latest firmware on the raid controller before booting.

This should fix your issue.

~dGeorgey

0 Kudos
Recho
Contributor
Contributor

Thanks dGeorgey. that maybe the point

Seems we just used the default RAID1 of the server and we have no such controller in the server configuration.

Do u have option to pass such controller driver loading during installation?

Thanks

Recho

0 Kudos
vlho
Hot Shot
Hot Shot

Hi Recho,

try delete --- /lsi_mr3.v00 in boot.cfg on USB flash...

0 Kudos
admin
Immortal
Immortal

Like vlho said, deleting it will make your ESXi alive.

There is a similar issue reported on some other thread. http://homeservershow.com/forums/index.php?/topic/6189-issues-installing-esxi-on-a-hp-n40l-microserv...--

There also the fix was to delete it. Smiley Happy

~dGeorgey

0 Kudos
Recho
Contributor
Contributor

Thank you both

Yes, it is passing but stopped at another followed step

Do I need to modify another configuration file?

Thanks

Recho

IMAG0380.jpg

0 Kudos
admin
Immortal
Immortal

Please try this,

Remove the follwoing from boot.cfg:

 

Delete -> LSI_MR3.V00

Make a copy of   LSI_MSGP.V00 and name it LSI_MR3.V00

Then you get to the install.

~dGeorgey

amusonda
Contributor
Contributor

The Fix mentioned above does work, but I think the real problem begins with not using HP's custom ESXi images.

Customize VMware ESXi Images for HP ProLiant Servers


-Abner

TechMirtra
Contributor
Contributor

The same issue happens with HP Proliant DL320e Gen8 in both ESXi 5.5 standard Image and ESXi 5.5 HP Custom Image.

The fix indicated by dGeorgey works, deleting  LSI_MR3.V00 and making a copy of   LSI_MSGP.V00 and name it LSI_MR3.V00

However it appears a new problem during the installation, the ESXi 5.5 standard image doesn't detect the logical volumes created in the SmartArray B120i, it only detects the physical disks. This is why it is recommended to download ESXi 5.5 HP Custom image to skip this problem

0 Kudos
Kilted_scot
Contributor
Contributor

I have the same problem as Recho. However my problem occurs on a Dell PowerEdge 1900.

(I don't care about supportability since this is a lab)  :smileyconfused:

I tried all of the solutions mentioned in this thread, and although they solved the first hand before installation started, they didn't solve the missing /tardisk/LSI.... error.

I was also installing from a USB flash drive.

The solution for me was to burn a DVD and install from that.

I didn't make any modification to the ISO that I burned, and the installation went smoothly.

Hope this helps.

djet
Enthusiast
Enthusiast

Same for me, only CD installation worked with no modifications and no errors.

srobakhiptsg
Contributor
Contributor

Actually it DOES happen with the HP custom image as well.  Ran into this today on a G8 380 with a P420i controller.  Using this image:  VMware-ESXi-5.5.0-1331820-HP-5.71.3-Sep2013.  Trying the del/rename fix above now. Fingers crossed. What a PITA.

0 Kudos
amusonda
Contributor
Contributor

Yeah, I had to burn to Disc as well.

0 Kudos
LordMethose
Contributor
Contributor

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.

MikeFF53212
Contributor
Contributor

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.

0 Kudos
handi2002
Contributor
Contributor

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.

Freed0mFighter
Contributor
Contributor

I can confirm using Rufus to create the bootable USB stick works.