Table of Contents
Advertisement
Chapter 3. Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with your server.
If you cannot locate and correct the problem using the information in this section,
see Appendix A, "Getting help and technical assistance", on page 121 for more
information.
General checkout
The server diagnostic programs are stored in upgradeable read-only memory
(ROM) on the system board. These programs are the primary method of testing the
major components of the server: the system board, Ethernet controller, video
controller, RAM, keyboard, mouse (pointing device), diskette drive, serial ports, and
hard disk drives. You can also use the diagnostic programs to test some external
devices. See "Diagnostic programs and error messages" on page 24.
If you cannot determine whether a problem is caused by the hardware or by the
software, you can run the diagnostic programs to confirm that the hardware is
working properly.
When you run the diagnostic programs, a single problem might cause several error
messages. When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages
might not occur the next time you run the test.
A failed system might be part of a shared DASD cluster (two or more systems
sharing one or more external storage devices). Before you run diagnostics, verify
that the failing system is not part of a shared DASD cluster.
A system might be part of a cluster if:
v The system is identified as part of a cluster.
v One or more external storage units are attached to the system and at least one
v One or more systems are located near the failing system.
If the failing system is suspected to be part of a shared DASD cluster, you can run
all diagnostic tests except the diagnostic tests that test the storage unit (DASD
residing in the storage unit) or the storage adapter attached to the storage unit.
Notes:
1. For systems that are part of a shared DASD cluster, run one test at a time in
2. If multiple error codes are displayed, diagnose the first error code that is
3. If the computer stops with a POST error, go to "POST error codes" on page 99.
4. If the computer stops and no error is displayed, go to "Undetermined problems"
5. For safety information, see "Safety information" on page 123.
6. For intermittent problems, check the error log.
© Copyright IBM Corp. 2002
of the attached storage units is also attached to another system or unidentifiable
source.
looped mode. Do not run all tests in looped mode, because this could enable
the DASD diagnostic tests.
displayed.
on page 112.
21
Advertisement
Table of Contents
Troubleshooting
