My dl380 gen9 server list of Firmwares removed from ILo by itself and server not oning

[Beginner1]

1. My dl380 gen9 server tries to boot but goes off. When I accessed the ILo to see what's happening I discovered that the list of Firmwares in the system information > firmware information, have all disappeared (removed without any action taken to remove them) apart from the ILo firmware which is left in the firmware list. Also I checked the IML and I saw messages like; 1 server critical fault (Service information: Input Power Loss, Power Supply, Power Supply 1 (03)). 1 server critical fault (Service information: Input Power Loss, System Board, AUX/Main EFUSE Regulator 1 (10h)). 56 Critical temperature threshold exceeded. What can I do to resolve this issue?

[support_s]

System recommended content:

1. Setup Overview for the HPE ProLiant DL380 Gen9 Server

2. ProLiant DL380 Gen9 Server Maintenance and Service Guide

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

Thank you for being a HPE valuable community member.

[BPSingh]

Greetings!

Power AC power cycle and check for the issue. 
Swap the power supply and check if the error follows the power supply or remains with the slot. 
Test with one power supply at a time 

[Beginner1]

I have been told by HP Engineer to replace system board but what surprises me is how system board gets faulty by itself. I didn't do any action to make it faulty. I shut it down myself and unplugged the whole cables before going out only to come back days after to use it and it's not oning anymore. 

[Beginner1]

I have been told by HP Engineer to replace system board but what surprises me is how system board gets faulty by itself. I didn't do any action to make it faulty. I shut it down myself and unplugged the whole cables before going out only to come back days after to use it and it's not oning anymore. The BIOS backup is empty, I suspected that the BIOS in the board died and it cannot be repaired. 

[BPSingh]

If you have already completed the steps outlined above, you can test the server in minimal configuration to help pinpoint the issue. Alternatively, if iLO is configured, you can collect the AHS logs and open a support ticket to further isolate the issue based on the logs.

[support_s]

Hello,

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

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

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