Troubleshooting Your System
AlphaServer 1000 Rackmount Owner's Guide 8-3
System Diagnostics
This section describes three sources of error information that can help you diagnose and
troubleshoot system problems. Beep codes are audible error codes emitted by the system
for specific problems. The console event log is a record of startup status messages which
may contain helpful diagnostic information. Console command displays, such as the
test
command display, are another source of diagnostic information.
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-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."
3-3-1
Generic system failure.
Call your service representative.
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.
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.
