Problem running SPP 2018/03 on Gen9 Server

[gsb88]

Figured it out. Had the wrong P number bios. My dl360 Gen8 bios is P71 and I was trying P73. Got the P71 update and worked fine. All BIOS are not created equal.

[Torsten.]

In the past and even now there were/are different server lines like

ML/DL 100 - entry level

ML/DL 300 - "professional" etc ...

But there was an exception in Gen8:

No ML/DL100, but a ML/DL 300"e" and "p", were the "e" was the replacement for the ML/DL100 series.

Confusing ...

The P70 and similar in the BIOS naming is a code for the model family, here are some examples:

HP ProLiant DL380p Gen8 (P70)
HP ProLiant DL360p Gen8 (P71)
HP ProLiant ML350p Gen8 (P72)
HP ProLiant DL360e Gen8/DL380e Gen8 (P73)
HP ProLiant DL320e Gen8 v2 (P80)
HP ProLiant ML350e Gen8/ML350e Gen8 v2 (J02) 

[gsb88]

Thanks Torsten, that clears up the BIOS confusion.

[mikldk]

Just updated a HPE BL460c G9 with Windows Server 2016 with Hyper-V yesterday - running full load with 50 VM's today.

No issues so far.

I did run the HP SPP launch_sum.bat from mounted ISO inside OS.

[ahe]

Not sure what HPE changed now, but by building a new custom SPP including the freshly released 2018.03.1 hotfix supplemental bundle, it works now for me on both DL380 Gen9 and DL160 Gen9. If I exclude that supplemental bundle it still fails.

For me that makes clear that there was an issue with the first release, but that is now resolved if the hotfix supplemental bundle is included.

[wallyhall]

I had this during an out of hours upgrade the other evening.

Fortunately one of my coworkers had seen the issue before and was able to diagnose it over the phone.

For us, this has happened twice now - during the "Analyzing system" section (after upgrading the firmware etc), it can be observed that each virtual disk volume on the HP Smart Array is being scanned (the disks spin in groups, for a very long time each).  We expect it coincides with a disk firmware upgrade, and the upgrade triggers a sector scan (or something similar) which takes an absolute age.

We powered down and powered back up; the firmware was upgraded fine and no ill effect from the power cycle was observed.