iLO 5 Self-Test Error on MicroServer Gen10 Plus

[NeoMod]

Recently, this message has been showing at start-up on a HPE Proliant MicroServer Gen 10 Plus:

Embedded: iLO 5 embedded health Device - Operation Failed

iLO 5 has detected a self-test error. For details, consult the iLO 5 Server and iLO 5 Diagnostics page.

Upon entering the "System Health Summary" I can see that everything is marked as "Healthy" except for the last point:

[Operation Failed ] Embedded: iLO 5 embedded health Device.

Entering the sub-menu at BIOS level doesn't provide any more info, referencing the iLO Diagnostic Page for more information.

Accessing the iLO Web Interface the warning pre-login text states:

"iLO Self-Test reports a problem with: EEPROM. View details on Diagnostics page"

And upon reaching the Diagnostics page the only error is inside the "iLO Self-Test" page is the following:

EEPROM Device or content issue: status 0x6 rw_csum rw_rev

I tried searching for the code "status 0x6 rw_csum rw_rev" but to no avail. Closest documented occurrence I could find is regarding the integrated SD Card Module in some Gen8/Gen9 servers, but the Microserver doesn't have any integrated reader.

I tried:

- Replacihng the power supply "brick"
- Replacing the iLO Enablement Module
- Booting without the iLO Enablment Module (error persists)
- Replacing the CMOS Battery
- Power-cycling the server (two days off-line with no battery)
- Resetting iLO
- Resetting BIOS
- Upgrading the system with the latest available SPP and iLO FW (no errors, all updates successful)
- Ran a full system test from Intelligent Provisioning: no issues detected
- Ran a full memory check: no issues. Even swapped both DDR modules.
- Checked cables, connectors, screws, etc. nothing out of the ordinary, everything is properly seated.

The server has been operating for a few days now, following all the above procedures; however, the error persists, and I can't identify anything out of order. Seems to me that the error could be self-contained to the iLO Chip and not impacting the operations.

Altough I would like more info, especially if possible, on the error code, which itself seems not very well documented. (or maybe I just missed it and it needs some Google-fu special power to emerge...)
Any help would be greatly appreciated!

[yesheswini_s]

Hello @NeoMod ,

Please try resetting iLO by using the procedure provided in this link.

Refer to this advisory, which discuss a similar issue.    iLO Self Test Error

Try to update SPP to latest version and run the self-test also please check all the firmware are up-to-date

Thanks,

Yesheswini S

[NeoMod]

@yesheswini_s,

Thank you for the kind response.

I had already performed the suggested steps, but out of due diligence, I followed the suggested procedure.

• I issued a new “iLO RESET” this time using the BIOS path (instead of using the iLO WEB GUI). The operation completed successfully, but the error remains.
• I’ve read the linked advisory, but I've already updated the iLO Firmware to the latest version (v. 3.14, June 16, 2025). I tried pushing the update one more time, overwriting the existing package: the update completed successfully, but the error remains.
  1. I also tried downgrading to the previous version, just in case: the operation was successful, but the error remains.
• I had already applied the latest service pack( SPP 2025.05.00.00 but I tried again: update succesfull, but the problemi remains.

I decided also to try the “Restore default manufacturing settings” procedure, which also reverted the iLO version back to default. Surprisingly, this resolved the issue, or well, this proved that the problem wasn’t really about a damaged component.

With iLO v. 2.11 there is no error reported.

I then tried to progressively update the iLO until the error appeared again, but it seems everything above 2.11 will cause the issue to reappear.

[Thaufique_Mod]

Hello @NeoMod 

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

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