Post Error Messages - IBM eServer 135 xSeries User Reference Manual

POST error messages

Table 12. POST error messages
POST message
062 The server failed to start on three consecutive attempts.
All caches are disabled. Repeatedly turning the server on and then off or resetting the server
might cause this problem.
Action:
If the problem persists, call for service. When the problem is corrected, be sure to enable the
caches.
101 102 106 An error occurred during the system board and microprocessor test.
Action:
114 An adapter read-only memory (ROM) error occurred.
Action:
If you cannot isolate and correct the problem, call for service.
129 An error was detected in the L1 cache of one of the microprocessors.
Action:
70
IBM xSeries 135: User's Reference
Table 11. POST beep codes
2-3-1 Screen initialization has failed.
1-2-4 RAM refresh verification has failed.
1-3-1 First 64 Kb RAM test has failed.
1-3-2 First 64 Kb RAM parity test has failed.
3-3-1 A memory size mismatch has occurred.
3-3-3 Attention: In some memory configurations, the 3-3-3 beep
code might sound during POST followed by a blank display
screen. If this occurs and the Boot Fail Count feature in the
Start Options of the Configuration/Setup Utility is set to
Enabled (its default setting), you must restart the server
three times to force the system BIOS to reset the memory
connector or bank of connectors from Disabled to Enabled.
The following tables provide information about the POST error messages that can
appear during startup.
Start the Configuration/Setup Utility program and verify that all settings are
correct. See "Using the Configuration/Setup Utility program" on page 12 for more
information. Use the Cache Control selection in the Advanced Setup menu of the
Configuration/Setup Utility program to enable the caches.
Call for service.
Remove the options. If you can start the server without the options installed,
reinstall each option one at a time and retest after each is reinstalled. When an
option fails, replace it.
1. If you just installed a microprocessor, verify that the microprocessor is installed
and seated correctly.
2. If the problem persists, call for service.
Description
Turn off the
server and then
restart the
server. If the
problem
persists, call for
service.
Reseat the
memory
modules or
install a memory
module. If the
problem
persists, call for
service.