IBM Support

Diagnostic error codes - IBM eServer xSeries 345

Troubleshooting


Problem

IBM eServer xSeries 345 diagnostic error codes.

Resolving The Problem

Notes:

  1. In the following error codes, if xxx is 000, 195, or 197, do not replace a FRU. The descriptions for these error codes are described in the following list:

    000 The test passed.
    195 The Esc key was pressed to abort the test.
    197 This is a warning error and may not indicate a hardware failure.

    For all error codes, replace the replaceable unit (FRU or CRU) or take the action indicated.

  2. See IBM eServer xSeries 345 - System parts listing to determine which components are replaceable by the customer (CRUs), and which components should be replaced by an IBM field service technician (FRUs).
Error code/Symptom FRU/Action
001-XXX-001
(Failed core tests)

System board
001-250-000
(Failed system board ECC)

System board
001-250-001
(Failed system board ECC)

System board
005-XXX-000
(Failed video test)

System board
011-XXX-000
(Failed COM1 serial port test)

System board
011-XXX-001
(Failed COM2 serial port test)

System board
014-XXX-000
(Failed parallel port test)

System board
015-XXX-001
(USB interface not found, board damaged)

System board
015-XXX-015
(Failed USB external loopback test)
  1. Make sure the parallel port is not disabled.
  2. Run the USB external loopback test again.
  3. System board
015-XXX-198
(USB device connected during USB test)
  1. Remove USB devices from USB1 and USB
  2. Run the USB external loopback test again.
  3. System board
020-XXX-000
(Failed PCI interface test)

System board
020-XXX-001
(Failed hot-swap slot 1 PCI latch test)
  1. PCI hot-swap latch assembly
  2. System board
020-XXX-002
(Failed hot-swap slot 2 PCI latch test)
  1. PCI hot-swap latch assembly
  2. System board
020-XXX-003
(Failed hot-swap slot 3 PCI latch test)
  1. PCI hot-swap latch assembly
  2. System board
020-XXX-004
(Failed hot-swap slot 4 PCI latch test)
  1. PCI hot-swap latch assembly
  2. System board
030-XXX-000
(Failed internal SCSI interface test)

System board
035-XXX-099
(No adapters were found.)		 If adapter is installed re-check connection.
035-XXX-S99
(Failed RAID test on PCI slot S. S = number of failing PCI slot. Check System Error Log before replacing a FRU.)
  1. Adapter
  2. SCSI backplane
  3. Cable
035-XXX-SNN
(Check System Error Log before replacing a FRU. s = number of failing PCI slot, nn = SCSI ID of failing fixed disk.)

Hard disk drive with SCSI ID nn on RAID adapter in PCI slot s.
035-253-S99
(RAID adapter initialization failure)
  1. ServeRAID adapter in slot s is not configured properly. Obtain the basic and extended configuration status, and see the ServeRAID Hardware Maintenance Manual for more information.
  2. Cable
  3. SCSI backplane
  4. Adapter
075-XXX-000
(Failed power supply test)

Power supply
089-XXX-001
(Failed microprocessor test)
  1. VRM 1 for microprocessor 1
  2. Microprocessor 1
089-XXX-002
(Failed optional microprocessor test)
  1. VRM 2 for optional microprocessor 2
  2. Optional microprocessor 2
166-198-000
System Management: Aborted (Unable to communicate with ASM. It may be busy. Run the test again.)
  1. Run the diagnostic test again.
  2. Correct other error conditions and retry. These include other failed system-management tests and items logged in the system-error log of the optional Remote Supervisor Adapter.
  3. Disconnect all server and option power cords from the server, wait 30 seconds, reconnect, and retry.
  4. Remote Supervisor Adapter, if installed
  5. System board
166-201-001
System Management: Failed (I2C bus error(s) See SERVPROC and DIAGS entries in event log.)
  1. If installed, reseat the I2C cable between the Remote Supervisor Adapter (in PCI slot 5/J5 on the PCI riser card) and system management connector on the PCI riser card.
  2. Reseat memory DIMMs.
  3. Memory DIMMs
  4. System board
166-201-002
System Management: Failed (I2C bus error(s) See SERVPROC and DIAGS entries in event log.)
  1. Reseat I2C cable between the operator information panel and the system board (J22).
  2. Diagnostics panel
  3. System board
166-201-003
System Management: Failed (I2C bus error(s) See SERVPROC and DIAGS entries in event log.)
  1. Reseat cables between the system board and the power supply or power cage assembly.
  2. Power cage assembly
  3. System board
166-201-004
System Management: Failed (I2C bus error(s) See SERVPROC and DIAGS entries in event log.)
  1. Hard disk drive backplane
  2. System board
166-201-005
System Management: Failed (I2C bus error(s) See SERVPROC and DIAGS entries in event log.)
  1. Reseat Memory DIMMs.
  2. Reseat microprocessors.
  3. Memory DIMMs
  4. Microprocessors
  5. System board
166-250-000
System Management: Failed (I2C cable is disconnected. Reconnect I2C cable between Remote Supervisor Adapter and system board.)
  1. If installed, reseat the I2C cable between the Remote Supervisor Adapter (in PCI slot 5/J5 on the PCI riser card) and system-management connector on the PCI riser card.
  2. I2C cables
  3. Advanced System Management adapter
  4. System board
166-260-000
System Management: Failed (Restart ASM Error. After restarting, ASM communication was lost. Unplug and cold boot to reset ASM.)
  1. Disconnect all server and option power cords from the server, wait 30 seconds, reconnect, and retry.
  2. Reseat the Remote Supervisor Adapter in PCI slot 5/J5 on the PCI riser card.
  3. Remote Supervisor Adapter
166-342-000
System Management: Failed (ASM adapter BIST indicate failed tests.)
  1. Ensure the latest firmware levels for Remote Supervisor Adapter and BIOS.
  2. Disconnect all server and option power cords from server, wait 30 seconds, reconnect, and retry.
  3. Remote Supervisor Adapter
166-400-000
System Management: Failed (ISMP self test result failed tests: x where x = Flash, RAM, or ROM.)
  1. Reflash or update firmware for ISMP.
  2. System board
180-XXX-000
(Diagnostics LED failure)		 Run diagnostics panel LED test for the failing LED.
180-XXX-001
(Failed front LED panel test)
  1. Operator information panel
  2. System board
180-XXX-002
(Failed diagnostics LED panel test)
  1. Diagnostics panel
  2. System board
180-361-003
(Failed fan LED test)
  1. Fan(s)
  2. System board
180-XXX-003
(Failed system board LED test)

System board
180-XXX-005
(Failed SCSI backplane LED test)
  1. SCSI backplane
  2. SCSI backplane cable
  3. System board
201-XXX-0NN
(Failed memory test.)
  1. DIMM Location slots 1-6 where nn = DIMM location.
    NOTE: nn 1=DIMM 1; 2=DIMM 2; 3=DIMM 3; 4=DIMM
  2. System board
201-XXX-999
(Multiple DIMM failure, see error text)
  1. See error text for failing DIMMs.
  2. System board
202-XXX-001
(Failed system cache test)
  1. VRM 1
  2. Microprocessor 1
202-XXX-002
(Failed system cache test)
  1. VRM 2
  2. Microprocessor 2
206-XXX-000
(Failed diskette drive test)
  1. Rerun the test with a different diskette
  2. Cable
  3. Diskette drive
  4. System board
215-XXX-000
(Failed IDE CD-ROM drive test)
  1. Rerun the test with a different CD-ROM.
  2. CD-ROM drive cables
  3. CD-ROM drive
  4. System board
217-198-XXX
(Could not establish drive parameters)
  1. Check cable and termination.
  2. SCSI backplane
  3. Hard disk
217-XXX-000
(Failed BIOS hard disk test)
NOTE: If RAID is configured, the hard disk number refers to the RAID logical array.

Hard disk 1
217-XXX-001
(Failed BIOS hard disk test)
NOTE: If RAID is configured, the hard disk number refers to the RAID logical array.

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.

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.

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.

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

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 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)		 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)

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

 

 

 

Document Location

Worldwide

Operating System

Older System x:All operating systems listed

[{"Type":"HW","Business Unit":{"code":"BU016","label":"Multiple Vendor Support"},"Product":{"code":"HW19S","label":"Older System x->xSeries 345"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 January 2019

UID

ibm1MIGR-53292

Page Feedback