The server got up on the BIOS, what could happen?

Question

BIOS

I will explain the situation in more detail: there is an ETegro Hyperion RS130 G3 server. It has Zentyal OS installed. While configuring the network interfaces (via the web interface) and applying the parameters, the server stopped showing signs of life (it does not respond to pings, ssh input is not available, the session was active before). The OS interface seemed to respond when physically accessed, but it was not possible to reboot (the roofing felts hung, or something else, I don’t know). Rebooted in an emergency.
When turned on, the manufacturer's logo appears and then nothing. The Status LED on the front panel is solid orange. The documentation (21 pages) describes only two modes: solid green and flashing orange.
After a long wait, the OS has booted up, is working normally, the configs have not been lost, but the server is making a lot of noise (as if under high load / temperature).
I can not get into the BIOS / web interface for managing the server.
What can happen to him?

Answer 1

The worst scenario - he booted from the second "bank" of the bios in emergency mode. You probably won’t be able to see this from the OS on a regular basis, you either need to install the controller from the vendor, or reboot and enter the BIOS through the \ IPMI console.
There may be several reasons for this behavior, but usually (or I just met it more often) the bios overflows log and disables clearing on overflow, in such a situation, regular loading is impossible and the preloader after the timeout switches to the second "bank" (where there is usually no logging at all) , but of course different motherboard manufacturers have different behavior.