Troubleshooting Your System
8-4 AlphaServer 1000A Rackmount Owner’s Guide
Interpreting Error Beep Codes
Table 8–2 describes error beep codes you may encounter while using your system. For
example, if the serial read only memory (SROM) code could not find any good memory,
you would a 1-3-3 beep code (one beep, a pause, a burst of three beeps, a pause, and
another burst of three beeps).
Table 8–2: Error Beep Codes
Beep
Code
Meaning
Action
1-1-2
A ROM data path error was
detected while loading ARC/SRM
console code.
Refer to the section, "Using the Fail-
Safe Loader."
1-1-4
The SROM code could not read the
Flash ROM headers, or there was a
checksum failure.
Refer to the section, "Using the Fail-
Safe Loader."
1-2-1
TOY NVRAM failure.
Call your service representative.
1-3-3
The SROM code could not find at
least 2 MB of good memory, or
there was no memory available.
Verify that the memory modules are
properly seated.
Replace faulty memory modules.
If replacement does not solve the
problem, call your service
representative.
3-1-2
The J1 jumper on the CPU card
was set incorrectly or the on-board
SCSI controller failed.
Check that the J1 jumper is set at bank
1. (SeeFigure 9-8) If the jumper is
not the problem, call your service
representative.
3-3-1
Generic system failure.
Call your service representative.
3-3-2
The J1 jumper on the CPU card
was set incorrectly or the PCI-to-
PCI controller failed.
Check that the J1 is set at bank 1.
(See Figure 9-8). If the jumper is not
the problem, Call your service
representative.
3-3-3
Internal Qlogic controller failure.
Call your service representative.
Reading the Console Event Log
The system maintains a console event log consisting of status messages received during
startup testing. If problems occur during startup, standard error messages may be
embedded in the console event log. To display the console event log, use the
cat el
command or, to display the log screen by screen, use the
more el
command.
