IBM eServer 370 xSeries, User Reference Manual

Page: 145 / 218

Power-on self-test (POST) beep codes
The successful completion of POST is indicated by one beep and the appearance
of the first screen of your operating system or application program. More than one
beep indicates that POST detected an error.
Beep codes are sounded in a series of beeps. For example, a 1–2–4 beep code
sounds like one beep, a pause, two consecutive beeps, another pause, and four
more consecutive beeps.
POST beep code descriptions
The following list contains more detailed descriptions of the possible types of beeps
that your server might emit.
No beeps
If no beep occurs, have the system serviced.
Continuous beep
This indicates that your startup processor has failed, or the I/O function card,
processor daughterboard, I/O board, or speaker subsystem might contain a
failing component. If the system continues through POST with no errors,
have the system serviced. If no video appears, the startup processor has
failed; replace the startup processor.
One short beep
If one beep occurs after your server successfully completes POST (that is,
after the System POST Complete (OK) light on the information panel is
illuminated), then POST has no configuration or functional errors to report.
One beep also occurs after your server completes POST if you enter an
incorrect power-on password.
Two short beeps
This beep combination indicates that POST encountered an error. The
Configuration/Setup Utility program will display additional information; follow
the instructions displayed. See “Viewing the test log” on page 121 for
explanations of any POST error messages.
Three short beeps
This beep combination indicates a system memory error. This combination
occurs only if the video BIOS cannot display the error message. Replace
the failing DIMM.
Repeating short beeps
This beep combination indicates that your I/O function card, processor
daughterboard, or I/O board might contain a failing component; your
keyboard might be defective; or a key on the keyboard might be stuck.
Ensure that:
1. Nothing is resting on the keyboard and pressing a key.
2. No key is stuck.
3. The keyboard cable is connected correctly to the keyboard and to the
correct connector on the server.
Chapter 6. Solving problems
129