Hello, what is your server model and Coudl you gşve us more information about your issue?
in generic, I can suggest below steps:
Do you happen to know what caused the improper shutdown? The most common cause for the UEFI0116 error is a disk drive issue. Could you check if any of the hard drives have amber lights?
Before trying any other troubleshooting steps, I would recommend performing a flea power drain. This involves shutting down the system, disconnecting power and network cables, and then holding in the power button for 20 seconds without any cords connected. After the flea power drain, let the system sit for 3 minutes to allow the DRAC (Dell Remote Access Controller) to reset without any power plugged in. Then, plug in the network cable and power cord, but wait for 2 minutes before powering on to give the DRAC time to initialize. After performing these steps, check if the system boots up normally.
If you are able to access the F2 BIOS setup after performing the flea power drain, it is possible that the boot mode might have changed to BIOS. In that case, changing the boot mode to UEFI in the BIOS setup could help.
If you have already performed the flea power drain and the issue persists, I would recommend taking the server to its minimum configuration for troubleshooting. This means removing everything from the server except for the system board, one power supply unit (and the PIB if applicable), the control panel with cable, one processor (CPU) in socket CPU1, and one memory module (DIMM) installed in socket A1. Power on the server in this minimal configuration and see if it clears the post. If it does, power down and then individually add the removed devices until the issue reappears, identifying the cause.
DELL-Erman O
Moderator
Moderator
•
2.2K Posts
0
April 3rd, 2024 11:21
Hello, what is your server model and Coudl you gşve us more information about your issue?
in generic, I can suggest below steps:
Do you happen to know what caused the improper shutdown? The most common cause for the UEFI0116 error is a disk drive issue. Could you check if any of the hard drives have amber lights?
Before trying any other troubleshooting steps, I would recommend performing a flea power drain. This involves shutting down the system, disconnecting power and network cables, and then holding in the power button for 20 seconds without any cords connected. After the flea power drain, let the system sit for 3 minutes to allow the DRAC (Dell Remote Access Controller) to reset without any power plugged in. Then, plug in the network cable and power cord, but wait for 2 minutes before powering on to give the DRAC time to initialize. After performing these steps, check if the system boots up normally.
If you are able to access the F2 BIOS setup after performing the flea power drain, it is possible that the boot mode might have changed to BIOS. In that case, changing the boot mode to UEFI in the BIOS setup could help.
If you have already performed the flea power drain and the issue persists, I would recommend taking the server to its minimum configuration for troubleshooting. This means removing everything from the server except for the system board, one power supply unit (and the PIB if applicable), the control panel with cable, one processor (CPU) in socket CPU1, and one memory module (DIMM) installed in socket A1. Power on the server in this minimal configuration and see if it clears the post. If it does, power down and then individually add the removed devices until the issue reappears, identifying the cause.
Hope that helps!
Praveen.Singh
3 Apprentice
3 Apprentice
•
406 Posts
0
April 24th, 2024 20:40
What I usually recommend to people it to disable, then re-enable the Lifecycle controller, which can be done through command line.
That will disable the controller. You can then run:
To turn it back on. There is a third state, 2, which corresponds to recovery mode.
Praveen.Singh
3 Apprentice
3 Apprentice
•
406 Posts
0
April 24th, 2024 20:41
Check this
https://www.dell.com/community/en/conversations/poweredge-hddscsiraid/rac0501-uefi0116-system-does-not-boot-up/647f9529f4ccf8a8de7a33ac