Troubleshooting Your System
AlphaServer 1000A Rackmount Owner’s Guide 8-3
Table 8–1: Determining Where to Look
Task or Problem
Relevant Section
To confirm that EISA cards or memory modules
are properly configured.
Option Card Problems
To run a diagnostic test of the whole system,
show its status, or terminate the testing.
System Diagnostics
No startup display appears when you turn on the
system.
System Diagnostics (Interpreting Error Beep
Codes)
Power Problems
Console Problems
Problems Detected by the Operating System
Startup tests do not complete.
Console Problems
The system cannot boot the operating system.
Boot Problems or System Diagnostics
The operating system reports errors, is hung, or
crashes.
Problems Detected by the Operating System
The system cannot access a mass storage device.
Storage devices are missing from the
show
device
display.
Storage Problems
The system indicates network problems, an EISA
card is not configured, or a PCI card is unseen by
the system.
Option Card Problems
The monitor or the terminal is not working.
Monitor and Terminal Problems
The keyboard and mouse are not working.
Keyboard and Mouse Problems
The system repeatedly shuts down after 10
seconds.
Overheating Problems
The Flash ROM is corrupted, and the system
cannot access console mode.
Using the Fail-Safe Loader
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.
