IBM eServer xSeries 205 Type 8480, Руководство по техническому обслуживанию и ремонту

Страница: 103 / 168

Note: See “System” on page 110 to determine which components should be replaced by a field service technician.
Error code/symptom FRU/action
217-XXX-001 (Failed BIOS hard disk test)
Note: If RAID is configured, the hard disk
number refers to the RAID logical array.
v Hard disk 2
217-XXX-002 (Failed BIOS hard disk test.)
Note: If RAID is configured, the hard disk
number refers to the RAID logical array.
v Hard disk 3
217-XXX-003 (Failed BIOS hard disk test.)
Note: If RAID is configured, the hard disk
number refers to the RAID logical array.
v
Hard disk 4.
217-XXX-004 (Failed BIOS hard disk test.)
Note: If RAID is configured, the hard disk
number refers to the RAID logical array.
v
Hard disk 5.
217-XXX-005 (Failed BIOS hard disk test.)
Note: If RAID is configured, the hard disk
number refers to the RAID logical array.
v Hard disk 6.
264-XXX-0NN (Failed tape drive test.)
1. Tape cartridge, if user executed the Read/Write Tape Drive test
(failure code of XXX = 256).
2. SCSI or power cable connected to tape drive with SCSI ID nn .
3. Tape drive with SCSI ID nn (refer to the Help and Service
Information appendix of the tape drive’s User Guide).
4. System board or SCSI controller (run SCSI controller diagnostic to
determine if the SCSI bus is functioning properly.)
264-XXX-999 (Errors on multiple tape
drives, see error text for more info.)
v See error messages/text in the PC Doctor error log for detailed
information on each individual tape drive error.
301-XXX-000 (Failed keyboard test.)
v Keyboard.
405-XXX-000 (Failed Ethernet test on
controller on the system board.)
1. Verify that Ethernet is not disabled in BIOS.
2. System board.
405-XXX-00N (Failed Ethernet test on
adapter in PCI slot n .)
1. Adapter in PCI slot n .
2. System board.
415-XXX-000 (Failed Modem test.)
1. Cable.
Note:
Ensure modem is present and attached to server.
2. Modem.
3. System board.
Error symptoms
You can use the error symptom table to find solutions to problems that have definite
symptoms.
If you cannot find the problem in the error symptom charts, go to “Starting the
diagnostic programs” on page 26 to test the server.
If you have just added new software or a new option and your server is not
working, complete the following steps before using the error symptom charts:
1. Remove the software or device that you just added.
2. Run the diagnostic tests to determine if your server is running correctly.
3. Reinstall the new software or new device.
Chapter 6. Symptom-to-FRU index
93