Use this information to diagnose and solve POST error codes for the blade server.
The following table describes the POST error codes that appear in the IMM system event log and suggested actions to correct the detected problems.
Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
See Parts listing - BladeCenter HX5 to determine which components are customer replaceable units (CRU) and which components are field replaceable units (FRU).
If an action step is preceded by "(Trained service technician only)," that step must be performed only by a Trained service technician.
Error code
Description
Action
0010002
Microprocessor not supported.
(Trained service technician) Complete the following steps:
Check the system event log for any memory errors that might be related to the specified DIMM and resolve those errors.
Note
If the system event log is full, new events will not be posted to the log. You can clear the system event log through the Setup Utility (see Using the Setup utility). Select System Event Logs and then select Clear System Event Log.
Save the settings and exit from the Setup utility.
0051003
Uncorrectable runtime DIMM error
Refer to TIP H21455 for minimum code level.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
Swap one of the DIMMs with a DIMM of the same size and type from another channel (see Installing a DIMM - BladeCenter HX5. For example, if a problem occurs on DIMM 1 and DIMM 4, swap DIMM 1 with a similar DIMM in slot 9.
Enable all affected DIMMs using the Setup utility.
If the failure remains on the original DIMM slots, replace the DIMM that was not moved. If the failure follows the DIMM that was moved, replace the DIMM that was swapped.
If you receive this error code for a blade server configuration that includes an IBM MAX5 expansion blade, multiple DIMMs might have been disabled. After you replace the mismatched DIMM, make sure that all DIMMs have been enabled using the Setup utility (see Using the Setup utility) or using the Advanced Settings Utility (see Using the Advanced Settings Utility (ASU)).
Turn off the blade server. Then turn on the blade server and immediately turn it off (before POST completes) four times, using either the power button on the front of the blade server or the advanced management module web interface.
Note
Make sure that you turn off the blade server immediately after starting it. Turning on the blade server and immediately turning it off four times will cause UEFI to be start using default settings the next time the server is started.
If the problem is resolved, run the Setup utility, select Load Default Settings, and save the settings to recover the server firmware.
Remove the battery and reinstall the battery to clear CMOS memory and NVRAM. The real time clock will also be reset.
Remove all DIMM pairs and make sure that a pair of DIMMs that are known to be operational are installed in DIMM connectors 1 and 4). Then, restart the blade server.
If the problem is resolved, continue adding DIMM pairs back to the system (see Installing a DIMM - BladeCenter HX5), restarting the blade server each time a DIMM pair is added.
Note
If the blade server fails to start after adding a DIMM pair, replace one of the DIMMs with a DIMM of the same size and type (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5). If the issue is resolved, continue to add additional DIMM pairs. If the problem remains, replace the second DIMM of the pair with the original removed DIMM. If the problem remains, continue to Step 6.
Turn off the blade server. Then turn on the blade server and immediately turn it off (before POST completes) four times, using either the power button on the front of the blade server or the advanced management module web interface.
Note
Make sure that you turn off the blade server immediately after starting it. Turning on the blade server and immediately turning it off four times will cause UEFI to be start using default settings the next time the server is started.
If the problem is resolved, run the Setup utility, select Load Default Settings, and save the settings to recover the server firmware.
Remove the battery and reinstall the battery to clear CMOS memory and NVRAM. The real time clock will also be reset.
Remove all DIMM pairs and make sure that a pair of DIMMs that are known to be operational are installed in DIMM connectors 1 and 4). Then, restart the blade server.
If the problem is resolved, continue adding DIMM pairs back to the system (see Installing a DIMM - BladeCenter HX5), restarting the blade server each time a DIMM pair is added.
Note
If the blade server fails to start after adding a DIMM pair, replace one of the DIMMs with a DIMM of the same size and type (see Removing a DIMM - BladeCenter HX5 and Installing a DIMM - BladeCenter HX5). If the issue is resolved, continue to add additional DIMM pairs. If the problem remains, replace the second DIMM of the pair with the original removed DIMM. If the problem remains, continue to Step 6.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different memory channel or microprocessor (see Installing a DIMM - BladeCenter HX5 for memory population sequence).
If the error still occurs on the same DIMM, replace the affected DIMM (as indicated by the error LEDs on the system board or the event logs).
Check the system event log for any memory errors that might be related to specified DIMM pair and resolve those errors.
Note
If the system event log is full, new events will not be posted to the log. You can clear the system event log through the Setup Utility (see Using the Setup utility). Select System Event Logs and then select Clear System Event Log.
Remove the specified DIMM pair and replace the DIMM pair with an identical pair of known good DIMMs, and then restart the server. Repeat as necessary. If the failures continue, go to step 5.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different memory channel or microprocessor (see Installing a DIMM - BladeCenter HX5 for memory population sequence).
Enable all affected DIMMs using the Setup utility.
If the failure remains on the original DIMM slots, replace the DIMM that was not moved. If the failure follows the DIMM that was moved, replace the DIMM that was swapped.
Check the system event log for any memory errors that might be related to the specified DIMM and resolve those errors.
Note
If the system event log is full, new events will not be posted to the log. You can clear the system event log through the Setup Utility (see Using the Setup utility). Select System Event Logs and then select Clear System Event Log.
Remove the specified DIMM pair and replace the DIMM pair with an identical pair of known good DIMMs, and then restart the server. Repeat as necessary. If the failures continue, go to step 5.
Turn off the blade server. Then turn on the blade server and immediately turn it off (before POST completes) four times, using either the power button on the front of the blade server or the advanced management module web interface.
Note
Make sure that you turn off the blade server immediately after starting it. Turning on the blade server and immediately turning it off four times will cause UEFI to be start using default settings.
Remove the battery and reinstall the battery to clear CMOS memory and NVRAM. The real time clock will also be reset.
Remove any recently installed hardware.
Update the server firmware through the advanced management module web interface.
2018002
Option ROM resource allocation failure.
Informational message that some devices might not be initialized.
Run the Setup utility (see Using the Setup utility). Select Start Options from the menu and modify the boot sequence so that you change the load order of the optional-device ROM code.
Run the Setup utility (see Using the Setup utility) and disable unused resource to make more space available:
Select Start Options
Select Planar Ethernet (PXE/DHCP) to disable the integrated Ethernet controller ROM.
Select Advanced Functions, followed by PCI Bus Control, and then PCI ROM Control Execution to disable the ROM of the adapters in the PCI slots.
Select Devices and I/O Ports to disable any of the integrated devices.
Replace the following components one at a time in the order shown, restarting the server each time:
Recover the server firmware to the latest level. Run the Setup utility, select Load Default Settings, and save the settings to recover the server firmware.
Undo any recent configuration changes, or clear CMOS memory to restore the settings to the default values.
Remove any recently installed hardware.
3038003
Firmware corrupted.
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Restart the server until you see F1 Setup or the Boot Device selection.
Undo any recent system changes, such as new settings or newly installed devices.
Check the advanced management module event log for any power related issues and resolve them. You can access the event log through the advanced management module web interface. For more information see the Advanced Management Module Installation and User's Guide. the ../com.ibm.bladecenter.advmgtmod.doc/adv_man_mod_printable_doc.html.
Remove all hardware that is not listed on the ServerProven website.
Run the Setup utility (see Using the Setup utility). Select Load Default Settings and save the settings. Then, restart the blade server.
3108007
System configuration restored to default settings
Information only. This is message is usually associated with the CMOS battery clear event.
3138002
Boot configuration error
Run the Setup utility and remove any recent changes made to the settings (see Using the Setup utility).
Run the Setup utility (see Using the Setup utility). Select Load Default Settings and save the settings.
Core Root of Trust Measurement (CRTM) update failed
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818002
Core Root of Trust Measurement (CRTM) update aborted
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818003
Core Root of Trust Measurement (CRTM) flash lock failed
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818004
Core Root of Trust Measurement (CRTM) system error
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818005
Current Bank Core Root of Trust Measurement (CRTM) capsule signature invalid
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818006
Opposite bank CRTM capsule signature invalid
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3818007
CRTM update capsule signature invalid
Revert to a previous version of the firmware for the blade server.
If the blade server will not start, switch to the backup UEFI image. Set switch 7 to the on position. See System-board switches for the location of switch 7.
Set switch 7 to the off position. See System-board switches for the location of switch 7.
3828004
AEM power capping disabled
Check the settings and the event logs.
Make sure that the Active Energy Manager feature is enabled in the Setup utility. Select System Settings > Power > Active Energy Manager > Capping Enabled.