ProLiant Servers (ML,DL,SL)

Re: Starting drivers. Please wait, this may ... take HOURS!!!

 
kira12
Frequent Advisor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

Hello Bigbag,

i solve it with using a H440 instead of the P440ar. After change the Controller an update the BIOS to 2.80 it works and it swap back to V4 CPU and the

P440ar...

best regards ré

SomeWhoCallMeTi
Visitor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

Following for updates.
I'm getting the same thing on my DL360 g9. "Starting drivers, please wait" takes about 15-30 minutes, then moves to Power and Thermal Calibration, where it sits for another 30-60 minutes depending on its mood.
I have updated iLo, and not seen any improvement. I have tried to update the P440ar, but the update fails. I don't have warranty coverage any longer, so I can't download a BIOS update. I have also run the latest NIC software updates.
I plan reboots to occur in the dead of night so nobody notices. It works, but isn't helpful for my beauty sleep.
SomeWhoCallMeTi
Visitor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

Update...

After downloading the smart array controller software update (cp032801), and the array flash update (cp039995), I have had a significant improvement in boot time. It's back to a normal 4 minutes or so. The flash update will NOT run without installing the array controller software update first. 

JB-LH
Occasional Advisor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

I, too, have a server that does this. Though, it's in production, so I can't do any troubleshooting at the moment.

However, one of the reader comments at the link posted by "opoplawski" on January 23rd, 2020, caught my eye.

https://www.running-system.com/hpe-starting-drivers-please-wait-bios-p89-v2-40-spp-201704

"Solution was to change the storage option in the Bios from the default “Scan all targets” to “Scan Configured Targets only” prior to the update."

I'd be interested in knowing if this worked for anybody.

Thanks!

AxelThirud
Occasional Visitor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

Storage options was already set to "Scan configured targets only" on one of our servers with this problem

Looking at the boot options, there was a "VMWare ESXI" entry as the first boot option. I put the SD Card there instead (where my esxi is installed) and the server booted normally. (this setting can also be set through ILO before restarting the server)

Of course, there could be some error in the bios where the "Scan configured targets only" wasn't saved properly and that this was corrected when the bios settings where saved again after changing BIOS options....

JB-LH
Occasional Advisor

Re: Starting drivers. Please wait, this may ... take HOURS!!!

Thanks for commenting, AxelThirud. I haven't had a chance to check my server yet, since it's still in production.