Several FW errors during boot, changing values in RBSU or updating FW not possible

[StephanA]

We have two Proliant DL325 Gen10, CPU AMD Epyc 7262, Bios A41 05/16/2024.
After a regular update of the Debian 12.10 installation I rebooted the backup server because of a kernel update.

The server reported it can't find an OS.
With One-Time Boot I was able to boot the Debian OS, which was working flawlessly.

The Boot Entry was missing in the System Configuration.
Trying to restore the value with F10 leads to an error dialog "Submit failed for form: ...(RBSU)", the value was not saved.
Leaving the menu with ESC after setting, a Dialog come up, asking for saving changed values.
Confirming had not produced an error message, but had not solved the problem, the Boot entry vanished again.

Afterwards following error messages started to appear during boot:
329 - Power Management Controller FW error - Unable to communicate with the FW ...
270 - iLO FW Communication Issue - Unabled to communicate with iLO FW ...
312 - HPE Smart Storage Energy Pack 1 Communication Failure ...
338 - HPE RESTful API Error - Unable to communicate with iLO FW.

Removing the power connectors to both power supplies for some hours had no effect.
I followed the instructions and tried to update firmwares.
Updating the System Bios failed instantly after starting the update.
Updating iLO was not possible, I found no menu entry for this, maybe because I disabled iLO during first installation of the server.
Enabling iLO failed also with "Submit failed for form: ...".
I found no menu entry to update the Power FW.

It seems that I can't change any value in RBSU.
Trying to reset or set to default had no effects, all changed values during first installation remained.

All the time the checkbox "Server Configuration Lock" was not set. I have not found where to set/reset the lock.

I assumed that the NVRAM got invalid, so I searched for a HW reset. I only found the clock battery, which I removed for a minute.
After reboot the clock was wrong as expected, but the problem remained.
But now I even was not able to set the clock.

How can I make the configuration/NVRAM useable again?

[StephanA · Accepted solution]

The server was 5 days disconnected from the grid.

Now the RBSU is functional again. No Firmware errors.

There was one saving error when creating the Debian boot entry, but afterwards the boot entry exists.

I have successfully corrected the boot order, date&time and other settings.

As usual the fans spin down after reboot and starting the OS.

I suppose the buffer batteries inside the server prevented the reset of  the invalid RBSU memory, 1-2 hours off the grid are insufficient to clear.

[Sunitha_Mod]

Hello @StephanA,

Perfect! 

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