IBM IntelliStation A Pro 6217, Руководство по обслуживанию

Страница: 61 / 188

v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v
See Chapter 3, “Parts listing, Machine Type 6217,” on page 67 to determine which components are
customer replaceable units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by (Trained service technician only), that step must be performed only by a
trained service technician.
Error code Description Action
030-XXX-00N Failed SCSI interface test.
If N=0, system board; if N>0, SCSI
adapter in slot N .
1. See the information that comes with the
adapter for instructions and test information.
2. Run the diagnostic tests.
3. Reseat the following components:
a. Failing adapter
b. (Trained service technician only) System
board
4. Replace the following components one at a
time, in the order shown, restarting the
computer each time:
a. Failing adapter
b. (Trained service technician only) System
board
089-XXX-001 Failed microprocessor test.
1. (Trained service technician only) Make sure
that the microprocessor is installed and seated
correctly.
2. If the computer does not have the latest level
of BIOS code installed, update the BIOS code
to the latest level.
3. Reseat the following components:
a. (Trained service technician only)
Microprocessor
b. (Trained service technician only) System
board
4. Replace the following components one at a
time, in the order shown, restarting the
computer each time:
a. (Trained service technician only)
Microprocessor
b. (Trained service technician only) System
board
089-XXX-002 Failed optional microprocessor test.
1. (Trained service technician only) Make sure
that microprocessor 2 is installed and seated
correctly.
2. Make sure that the BIOS code is at the latest
level.
3. (Trained service technician only) Reseat
microprocessor 2.
4. (Trained service technician only) Replace
microprocessor 2.
201-198-xxx Memory test aborted. See PC Doctor
logs.
1. Restart the server.
2. Run the diagnostic test again.
3. Reinstall the diagnostic program.
4. Refer to the error log for additional information.
Chapter 2. Diagnostics
45