Resolving a system firmware boot failure
Learn how to identify the service action that is needed to resolve a failure while booting your system firmware.
- Does the baseboard management controller (BMC) respond to commands and are you able to access
the BMC web interface? Note: To determine whether the BMC responds to commands, run the following ipmitool command:
ipmitool -I lanplus -U <username> -P <password> -H <bmc ip or bmc hostname> chassis statusIf Then Yes: Continue with step 3. No: Continue with the next step. - Complete the following actions, one at a time, until the problem is resolved:
- Reset the BMC remotely by entering the following
command:
ipmitool -I lanplus -U <username> -P <password> -H <bmc ip or bmc hostname> mc reset cold - Disconnect the power cords from the system for 30 seconds. Reconnect the power cords, wait 5 minutes, and then go to step 1.
- Update the BMC firmware by using the pUpdate command with the block transfer (BT) option. For instructions, see Resolving a BMC access problem.
- Replace the system backplane. To identify the physical location and the removal and replacement procedure, see 7063-CR1 locations.
- Reset the BMC remotely by entering the following
command:
- After you pressed the power button, did the system turn on but fail to display the Petitboot
menu?
If Then Yes: Continue with the next step. No: This ends the procedure. - Complete the following actions, one at a time, until the problem is resolved:
- Disconnect the power cords from the system for 30 seconds. Reconnect the power cords, wait 5 minutes, and then go to step 3.
- Update the PNOR firmware. For instructions, see Getting fixes.
- Replace the system backplane. To identify the physical location and the removal and replacement procedure, see 7063-CR1 locations.
Parent topic: Beginning troubleshooting and problem analysis