Marvel RAID fails after Firmware Update - MicroserverGen10 boot fail!

[Carsten76]

We have a Proliant Microserver Gen10 that no longer starts. I loaded an apparently incompatible firmware for the Marvel RAID 88SE9230 (via the Marvell MSU Tool under Windows). After a "successful" update, a restart was required. Since then it only boots into the BIOS message "Press DEL or F2 to enter Setup.../Press F11 to enter Boot Menu". No matter what I choose, it doesn't get any further (not even into the BIOS or UEFI...). I had previously backed up the old firmware. But since I can no longer get into the RAID tool via UEFI, I can no longer restore them. Is there a way to save or disable the Marvell controller? If it can be deactivated, I could install an alternative controller.

TIA

[support_s]

System recommended content:

1. HPE ProLiant MicroServer Gen10 Troubleshooting Guide | Accessing the Marvell BIOS Utility under UEFI boot mode

2. Advisory: HPE ProLiant MicroServer Gen10 - BIOS Update to Version A330 (ZA10A330) Is Required to Access the Integrated Marvell BIOS Utility (MBU) and Configure Drive Arrays

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Carsten76]

I cant access UEFI Boot Mode, because the Post hangs on "Entering Boot Menu...".
Same problem when i try to get in to BIOS. It hangs on "Entering setup...".

The installed Bios Version is A360 (ZA10A360).

I made a BIOS Reset, but same problem.

[ksram]

Hi Carsten76,

Good day1

Thank you for the Post.

Can you try removing the Card (if its removable) and then try to Power-On the Server.

If the Server boots, may be you will have to replace the Card (After trying Re-seat)

Thank you
RamKS

[Carsten76]

Hi RamKS,

thank you for your support.

The Raid Controller is onboard, there is no card that i can remove.

Thank you.

Carsten

[ksram · Accepted solution]

Hi,

Try clearing NVRAM

And if its Inbuilt and the Firmware is corrupted and if we dont have other options, then probably we will have to repalce the System Board.

Thank you
RamKS

[Carsten76]

Hi,

Unfortunately clearing the CMOS did not solve the problem. Replacing the mainboard is out of the question for cost reasons.

Nevertheless thanks for your support.