RAID Controller not detected from Intelligent Provisioning

[Patric Falinder]

I just got a new ProLiant DL360 Gen10 Plus which I'm trying to install. I started with booting upp the SPP image to update all the firwmare etc. and updated Intelligent Provisioning to the latest.

After this I tried to install Windows on it thgouhg Intelligent Provisioning but I got an error right away saying "there is no Smart Array SR controller on this server."

When I enter Intelligent Storage Configuration I also get an error saying no controllers found.

Entering Smart Storage Administrator I get the same thing.

I managed to create a RAID 1 when clicking F9 during boot and enter some storage menu there and after that I can click Continue on the installation through IP and it seems to install.

Am I missing something here? I have three "identical" servers which I bought little over a year ago and I see that the controllers are different.

The old ones have HPE Smart Array P408i-a SR Gen10 and the new one has HPE MR416i-a Gen10+

Obvisouly there is something different here in how you manage it.
I'm running these as Hyper V hosts so I only need to RAID the disks which the OS is installed on, then the other data is on a SAN.

So can I just ignore this or is there something wrong/new that I need to fix?

[thutchings]

Hello,

The first screenshot you provided gives you the answer why it is not detected. The "there is no Smart Array SR controller on this server" is indicating that it can't find a supported controller. You do not have an SR controller. You have an MR controller. 

The method you used to configure the raid 1 through F9 should work though. You should be able to get the MRSA configuration utility available with newer versions of Intelligent Provisioning (IP). This feature shows as being added in version 3.85 of IP:
https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_b8785977f6404a4382d2bea3f1&tab=Enhancements

Regards

[TVVJ]

Hello,

You may refer to section "Creating a logical drive" of the HPE MR Gen10 Plus Controller User Guide for more information.

Regards,

[msobers22]

Hello,

The MR416i cannot be configured using SSA. You must configure the controller in System Utilities. 

1. Access System Utilities by pressing F9 during POST
2. From the System Utilities screen, select System Configuration > HPE MR416i-a Gen10+
3. Select Main Menu 
4. Configuration Management > Create Logical Drive
5. Select RAID Level
6. Select Drives > Apply Changes > Ok
7. Name the Logical Drive > Save Configuration 
8. Check the Confirm box > Click on Yes - Ok

Hope this helps

[kesarswet]

So long story short, I've got two HPE Proliant DL380 Gen10 servers where I'm trying to configure 3 Samsung SAS SSDs each and 1 HPE SATA disk. In one of the servers, everything works fine. I've configured arrays as I want to. On the other, I can't even get the disks to be recognised on SSA (Smart Storage Administrator). I've compared the disks and the System ROM firmware, iLO firmware and the Intelligent provisioning firmware and they're all the same, but none of this have helped. Any ideas are welcome.

[Sunitha_Mod]

Hello @Patric Falinder,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

[alwaysasking]

Wasted alot of time on brand new server, getting Raid setup as MR416i in my opinion is a supply chain solution to smart array shortage which was rushed and lacking in supporting software and tools. 

I could find no way to create an online spare using System Utilities. 

I updated Intelligent Provisioning with this version IP386.2023_0525.6.iso

This gave me access to an MR Storage administrator but the MR416i and SSDs were no longer visible (in System Utilites or MRSA)  and boot was extremely slow during Post as it struggled to get this MR416i device ready. 

to resolve this i downloaded ilorest tools to a pc

ran this command

ilorest flashfwpkg <file_name.fwpkg> --url <iLO5_IP_Address> -u <iLO5_username> -p <iLO5_password>

with this firmware 52.24.3-4948 for the MR416i (available here https://internal.support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_790e478d39324d7784032688fa&tab=Installation+Instructions)

Now MR416i visible , MR Storage Administrator allows creation of online spare. 

Hopefully I can save someone some wasted hours!!

[BOB2334]

@alwaysasking How did you access the MR storage administrator?  I don't know how to verify if it is even installed.  Can you access at bootup or did you access it via web interface?  I am not sure what the link/port is if accessing via the web interface.  I do see storecli is loaded, and I can see most settings, but the gui would be much easier.  This is a RedHat box by the way.

[DavidCa]

Yes....I have suffered the same and was resolved installing on the server the last SPP and the last version of the Intelligent Provision

[alwaysasking]

you access the MR storage admin via Intelligent Provisiong (F10 at boot), then Perform Maintenance and select MR Storage Administrator

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002729en_us&docLocale=en_US&page=GUID-20B22515-5ECC-4CAB-B049-AF29A3DCC340.html

[robytlk]

Ho anche io lo stesso problema.
Il mio Intelligent Provisioning vede MR416. Ho potuto configurare gli array correttamente. I dischi sono riconosciuti e hanno fatto l'inizializzazione.
Quando però avvio il setup di windows server, i dischi non sono riconosciuti. Ho anche creato il file ISO di windows con i driver Megasas35, ma non si avvia ugualmente, con il messaggio "drive.volumes is undefined"

Avete una soluzione, per favore ?

--------------------------------------------------------------------------------------------

I also have the same problem.
My Intelligent Provisioning sees MR416. I was able to configure the arrays correctly. The disks are recognized and initialized.
However, when I start the Windows Server setup, the disks are not recognized. I also created the Windows ISO file with the Megasas35 driver, but it still doesn't boot, with the message "drive.volumes is undefined"

Do you have a solution, please?

[TVVJ]

Hello,

You may require the driver for the array controller. You may download it from the HPE MegaRAID (MR) controller software download page and see if it helps:

HPE MR Gen10 Plus Controllers.

Regards,

[Moderator edit: Updated the link]

[robytlk]

@TVVJ Grazie per la tua risposta.

Avevo già incluso il driver della MegaRAID nella ISO di Windows 2022. Infatti se faccio avviare direttamente windows dal boot su USB i dischi si visualizzano.

Non sono visti se utilizzo "Rapid Setup" di Intelligent Provisioning, quindi penso che sia questo software che non ha il driver aggiornato.

Come posso aggiornare i drive di Intelligent Provvisioning, per favore ?

Grazie e saluti

Google Translated: 

Thank you for your answer.

I had already included the MegaRAID driver in the Windows 2022 ISO. In fact, if I start Windows directly from the USB boot, the disks are displayed.

They are not seen if I use Intelligent Provisioning's "Rapid Setup", so I think it is this software that does not have the updated driver.

How can I upgrade Intelligent Provisioning drives, please?

Thank you and greetings

[TVVJ]

Hello,

If the server is a Gen11 server, then download and install "Intelligent Provisioning Recovery Media for Gen11".

If the server is a Gen10 server, then download and install "Intelligent Provisioning Recovery Media for Gen10 and Gen10 Plus".

Regards,

[robytlk · Accepted solution]

Thank you for your answer
I had already tried to update using a USB stick, but it didn't work.

I burned a DVD with the intelligent provisioning ISO and it finally updated
Now recognizes MD416 controller from I.P.

thanks everyone for the help

best regards

[Sunitha_Mod]

Hello @robytlk,

That's Awesome! 

We are extremely glad to know you were able to find the solution and we appreciate you for keeping us posted. 

[robytlk]

Another small intelligent provisioning bug

1) Performed the update as mentioned above
2) Prepare the USB stick with the Windows 2022 ISO downloaded from the Microsoft website
3) Started I.P - launched "Rapid setup"
4) The discs are recognized
5) Windows installation starts
6) Windows installation crashes due to "the origin of the ISO image is not recognised)

Installed Windows without I.P - Completed successfully.

P.S.

I suggest correcting I.P. or modify the installation procedure guides because they don't work that way

Best regards

[mizogmo]

@robytlk hi friend

I have the same problem, after update 
The above methods did not work

my server hp dl380 g10

and p408i-a controller

plz help me thanks

[robytlk]

Ho riscontrato i seguenti bug, non so se risolvono per te

1) scarica l'aggiornamento di I.P. dai link indicati sopra nel post

2) crea un DVD fisico (BUG-1 con la USB non funziona) e esegui l'aggiornamento (avviando da F11 boot menù il DVD) - i tuoi dischi saranno visibili

3) crea la USB (o DVD doppia faccia) con il S.O. Windows Server

4) (BUG-2 Installare Windows da I.P. non funziona) - All'avvio del server premi F11 per il menù di boot e seleziona l'unità con il windows - installa windows

5) scarica SPP dai link di HPE e prepara una USB con la ISO

6) lancia  "launch_sum.bat" come amministratore da windows per aggiornare driver e software

Questa procedura ha funzionato per me

Regards

Google Translated: 

I encountered the following bugs, I don't know if they fix it for you

1) download the I.P. update. from the links indicated above in the post

2) create a physical DVD (BUG-1 with USB does not work) and run the update (booting the DVD from the F11 boot menu) - your disks will be visible

3) create the USB (or double-sided DVD) with the OS. Windows Server

4) (BUG-2 Installing Windows from I.P. doesn't work) - When the server starts, press F11 for the boot menu and select the drive with windows - install windows

5) download SPP from the HPE links and prepare a USB with the ISO

6) launch "launch_sum.bat" as administrator from windows to update drivers and software

This procedure worked for me

[mcmtech]

Just wanted to tag on to this in case anyone else missed it. 52.26.3.5487 (b) is not compatible with ESX 7 which game me the same error as you  saw.