POST Faults

A server in standby mode cannot power on. (The power indicator is steady yellow.)

1. Collect iBMC logs, and query the CPLD register to determine whether the power supply link to the mainboard has failed.
2. If the server cannot be powered on by pressing the power button, check whether the hardware of the component where the power button is located is faulty.
3. Check whether the mainboard (with integrated CPUs) and DIMMs are installed properly.

1. Remove PCIe devices, such as NICs. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 2.
2. Retain only the minimum configuration of the server and check whether the fault is rectified. For details about the minimum configuration of each server, see Handling Faults Based on Symptoms.
   • If yes, no further action is required.
   • If no, go to 3.
3. Check whether the mainboard (with integrated CPUs) and DIMMs are faulty by replacing them and performing switching tests. If they are faulty, replace the faulty components.

A server powers off immediately when powered on.

1. Check whether the external power supply is normal, including the PDUs, PSUs, and power cables.
2. Check whether the total power of the PSUs configured for the server is less than the power required for running the server.
3. Collect iBMC logs, and query the CPLD register to determine whether the power supply link to the mainboard has failed.
   NOTE:

   After the OS is powered off, collect iBMC logs. Do not remove the AC PSU or restart the server. Otherwise, the fault information bit recorded in the CPLD register will be cleared.

4. Check the power supply unit (PSU) backplane and the mainboard.

1. Check whether the external power supply is normal, including the PDUs, PSUs, and power cables. Replace any faulty components and check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 2.
2. Replace the mainboard or PSU backplane.

The message "no signal" is displayed immediately after the server powers on.

1. Collect iBMC logs, and query the CPLD register to determine whether the power supply link to the mainboard has failed.
2. Use the iBMC CLI to enable BIOS full printing, restart the server, and save system serial port logs. After the fault recurs, collect iBMC logs and download the .bin file of the BIOS.

1. Run the ipmcset -d clearcmos command to clear the CMOS. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 2.
     NOTICE:

     Running the ipmcset -d clearcmos command will restore the BIOS defaults. Exercise caution when running this command.

2. Upgrade the iBMC, and the BIOS. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 3.
3. Remove PCIe devices, such as NICs. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 4.
4. Retain only the minimum configuration of the server and check whether the fault is rectified. For details about the minimum configuration of each server, see Handling Faults Based on Symptoms.
   • If yes, no further action is required.
   • If no, go to 5.
5. Check whether the mainboard (with integrated CPUs) and DIMMs are faulty by replacing them and performing switching tests. If they are faulty, replace the faulty components.

The server repeatedly powers on and then powers off.

1. Enable the video recording function on the iBMC WebUI.
2. Use the iBMC CLI to enable BIOS full printing, restart the server, and save system serial port logs. After the fault recurs, collect iBMC logs and download the .bin file of the BIOS.
3. Restore the default BIOS settings, and check whether the server operates properly.
   • If yes, modify the BIOS parameters in the OS side based on actual requirements.
   • If the fault persists, collect iBMC logs and download the .bin file of the BIOS. For details, see the iBMC User Guide.

The POST stops responding at a screen.

1. Capture the current screen.
2. Collect iBMC logs, and query the CPLD register to determine whether the power supply link to the mainboard has failed.
3. Use the iBMC CLI to enable full printing for the BIOS.
4. Enable the video recording function on the iBMC WebUI, restart the server, and save system serial port logs. When the fault is repeated, collect iBMC logs and download the .bin file of the BIOS.
5. Check the external USB devices, CPUs, drives, DIMMs, and PCIe devices.

RAID self-check is suspended.

1. Capture the current iBMC KVM or local KVM screen.
2. Collect iBMC logs.

1. If a RAID controller card firmware error exists, replace the RAID controller card or supercapacitor. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 2.
2. Check whether the drives, drive backplane, and SAS cables are faulty.
   • If yes, replace faulty components.
   • If no, go to 3.
3. If the RAID array is offline, import it again. Then check whether the fault is rectified.
   • If yes, no further action is required.
   • If no, go to 4.
4. If the supercapacitor runs out of power, follow the instructions shown in the displayed messages to keep the server running. After the server runs for 30 minutes, check the supercapacitor status. If the supercapacitor is abnormal, replace it.

NIC Preboot Execution Environment (PXE) has failed.

1. Check whether the NIC supports PXE.
2. Check the BIOS PXE configuration. Ensure that the NIC PXE function is enabled.
3. Check the NIC.
4. Check the PXE network environment on the service side.

Follow the handling procedure.