Troubleshooting
Problem
This section lists the ServeRAID-4 controller error codes/messages, and the error procedures. ServeRAID-4 Controller error codes/messages The error codes/messages are displayed on the screen in a line of text immediately after the adapter BIOS vers
Resolving The Problem
This section lists the ServeRAID-4 controller error codes/messages, and the error procedures.
ServeRAID-4 Controller error codes/messages
The error codes/messages are displayed on the screen in a line of text immediately after the adapter BIOS version.
If POST detects changes in the controller configuration or detects a controller hardware problem, messages appear on the screen. Refer to "POST (ISPR) error procedures" further down in this document and correct the problem.
If there is no POST Error or Configuration Error message, the BIOS screen resembles the sample shown below. Note that your version may be different from the one shown.
--------------------------------------------------------------------------------------------------
__________________________________
IBM ServeRAID BIOS
Copyright IBM Corp. 1995, 2000
Ver: 3.00.12 08/14/2000
__________________________________
Press Ctrl+I to access the Mini-Configuration Program.
Initializing ServeRAID Controller 1 in Slot 1.
Power-on self-test can take up to 59 Second(s) -- test Passed.
Drive configuration can take up to 6 Minute(s) 0 Second(s) -- test Passed.
ServeRAID Firmware Version:2.82.00
No logical drives found; none are installed.
Non-Disk SCSI Devices Found: CD-ROM 0, Tape 0, Removable-media 0, Other 1.
BIOS not loaded no devices found - Installation stopped.
--------------------------------------------------------------------------------------------------
If there is a POST Error message, the BIOS screen resembles the sample shown below. Refer to "POST (ISPR) error codes" further down in this document and correct the problem. Note that your version may be different from the one shown. The characters XXXX indicate the POST (ISPR) error.
--------------------------------------------------------------------------------------------------
__________________________________
IBM ServeRAID BIOS
Copyright IBM Corp. 1995, 2000
Ver: 3.00.12 08/14/2000
__________________________________
Press Ctrl+I to access the Mini-Configuration Program.
Initializing ServeRAID Controller 1 in Slot 1.
Power-on self-test can take up to 59 Second(s) -- test Failed.
Controller is not responding properly - Run Diagnostics.
Error Code: XXXX-YY
BIOS not loaded no devices found - Installation stopped.
--------------------------------------------------------------------------------------------------
The sample BIOS screen below shows Configuration Status and/or Error information.
--------------------------------------------------------------------------------------------------
__________________________________
IBM ServeRAID BIOS
Copyright IBM Corp. 1995, 2000
Ver: 3.00.12 08/14/2000
__________________________________
Press Ctrl+I to access the Mini-Configuration Program.
Initializing ServeRAID Controller 1 in Slot 1.
Power-on self-test can take up to 59 Second(s) -- test Passed.
Drive configuration-can take up to 6 Minute(s) 0 Second(s) -- test Failed.
Controller POST and Config Error Codes: ISPR = EF10 BCS = 09 ECS = 20.
Following drives not responding (old state: new state: ch SID)
(RDY:EMP: 2:0)
The system has a configuration error due to above condition(s). Press: F4 - Retry the command F5 - Update Controller configuration to exclude NON-RESPONDING drives Warning: NON-RESPONDING drives will be set to DDD, DHS, or EMP state F10 - Exit without change
--------------------------------------------------------------------------------------------------
NOTE: Do not replace a ServeRAID-4 controller or a system board containing an imbedded ServeRAID-4 controller for ServeRAID problems unless replacing the controller is listed in the Symptom-to-FRU index .
POST (ISPR) error codes
The ISPR (Interrupt Status Port Register), BCS (Basic Configuration Status), and ECS (Extended Configuration Status) codes identify the controller state.
NOTE: Do not replace the ServeRAID-4x controller or an imbedded controller on a system board unless such a replacement is indicated in the recommended Actions in an error code list that appears in Symptom-to-FRU index.
POST (ISPR) error procedures
The ISPR Error Procedures list errors, symptoms, and the possible causes. The most probable cause is listed first. Use these procedures to help you solve ServeRAID problems when servicing the computer. A complete list of error codes is in the Symptom-to-FRU index.
NOTE: Where the ISPR Error Procedures refer to a SCSI backplane, see the Hardware Maintenance Manual for the system you are servicing.
EF10 (Default ISPR)
1. No ISPR Error Present.
9ZXX thru BZXX (SCSI bus error caused either by cables, termination, defective drives, etc.)
1. Isolate between SCSI subsystem and controller by disconnecting all SCSI cables from suspect card, and reboot.
CAUTION: Do not press F5. Doing so changes the customer's configuration.
If an ISPR error is still present, perform the following actions until the error is no longer present:
a. Reseat the controller
b. Replace the controller
NOTES:
a.Refer to the Hardware Maintenance Manual (HMM) specific to the system comprising the SCSI channel for SCSI cable details.
b.The adapter/controller detects a configuration change. Do not choose Save Changes. Instead, press F10 to bypass any options to this effect.
2. If ISPR error is EF10 after disconnecting cables:
a. Identify which channel is causing the error by the second digit (Z) of the original ISPR code as indicated in the following table:
Note: ServeRAID-4H controllers have 4 channels; ServeRAID-4L controllers have only one channel; and ServeRAID-4M controllers have 2 channels.
Table 1. SCSI identifier
|
SCSI Channel Code (z)
|
Descriptions
|
|
1
|
Channel 1 |
|
2
|
Channel 2 |
|
3
|
Channel 1 & 2 |
|
4
|
Channel 3 |
|
5
|
Channel 1 & 3 |
|
6
|
Channel 2 & 3 |
|
7
|
Channel 1, 2 & 3 |
|
8
|
Channel 4 |
|
9
|
Channel 1 & 4 |
|
A
|
Channel 2 & 4 |
|
B
|
Channel 1, 2 & 4 |
|
C
|
Channel 3 & 4 |
|
D
|
Channel 1, 3 & 4 |
|
E
|
Channel 2, 3 & 4 |
|
F
|
Channel 1, 2, 3 & 4 |
b. Confirm that the channel(s) identified from the error in step 2a is (are) the cause of the error by verifying that the error presents itself ONLY when the offending channel is reconnected.c. Check termination of identified channel.
Note: Refer to the HMM (Hardware Maintenance Manual) specific to the system comprising the SCSI channel for termination details.
d. Check for proper backplane jumper configuration.
Note: Refer to the HMM (Hardware Maintenance Manual) specific to the system comprising the SCSI channel for jumper details.
e. Check for proper cabling configuration in systems that use DASD status cables. Reconnect all cables removed in step 1 above.
f. Disconnect one drive at a time attached to the channel identified in step a above ; then, reboot to determine which drive is causing the error.
g. Replace SCSI cable.
h. Replace SCSI backplane.
FFFF or other code not listed
1. Isolate between SCSI Subsystem and controller by disconnecting all SCSI cables attached to the suspect card, and reboot.
CAUTION: Do not press F5. Doing so will change the customer's configuration.
If ISPR code is EF10 after disconnecting cables, follow the steps below until the error is eliminated:
a. Identify which channel is causing the error by reconnecting cables one at a time and rebooting until the error returns.
b. Check termination of identified channel in step 1a. Note: Refer to the HMM (Hardware Maintenance Manual) specific to the system comprising the SCSI channel for termination details.
c. Disconnect one drive at a time attached to channel identified in step 1a and reboot each time to determine which drive is causing the problem.
d. Replace SCSI Cable attached to channel identified in step 1a.
e. Replace Backplane attached to channel identified in step 1a.
2. If original ISPR code is still present after disconnecting all SCSI cables and rebooting, perform the following actions until the error is no longer present:
- Reseat the controller
- Replace the controller
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 January 2019
UID
ibm1MIGR-4R6LGQ