Troubleshooting
Problem
ServeRAID II Controller Error Codes/Messages Use the following ServeRAID II controller error code/message information when diagnosing ServeRAID problems.
Resolving The Problem
ServeRAID II Controller Error Codes/Messages
Use the following ServeRAID II controller error code/message information when diagnosing ServeRAID problems. The error codes/messages are displayed on the screen in a line of text immediately after the adapter BIOS version screen similar to the following appears.
Press Ctrl+I to start the MiniConfig Utility. The following message is displayed on the screen.
The interrupt status port register (IPSR) codes, basic configuration status (BCS) messages, and extended configurations status (ECS) messages identify the Controller State. The BCS and ECS codes indicate a configuration change. Configuration change information is displayed on the screen in text following the IPSR code.
Note: Do Not replace a planar (system board) for RAID problems that has an integrated on-board ServeRAID Controller if the system board is not listed as the FRU/Action in the following index. Refer to RAID adapter HMM S10L-9147-00 for recovery procedures for DDD drives.
| IPSR Error | FRU/Action |
|---|---|
| EF10 (Default ISPR) | 1. Controller is functioning properly. DO NOT replace Controller. |
| 1xxx (Microcode Checksum Error) | 1. RAID Controller. System Board, if integrated controller. |
| 2xxx thru 8xxx (Code DRAM Error) | 1. Install the download jumpers (two jumpers on J15, installed parallel to PCI slots) and Flash the Controller with the latest IBM ServeRAID BIOS/Firmware from the IBM Web site, then; remove the jumpers. 2. RAID Controller System Board, if integrated controller. |
| 9xxx thru Bxxx(hex) (SCSI bus error caused by either defective drives, termination, etc.) | 1. Note The Controller will detect a configuration change. Do not select Save Changes. Press F10 to bypass any save options. Isolate between the SCSI subsystem and the controller by disconnecting all SCSI cables and reboot. If the IPSR code still occurs, replace the planar. 2. If the IPSR code does not occur after disconnecting the cables, follow the steps below until the error is eliminated: a. Identity which channel is causing the error by the second digit of the original IPSR code: = Channel 1 ISPR = B2xx = Channel 2 ISPR = B3xx = Channel 1 and 2 b. Confirm that the channel(s) identified by the error code(s) is/are the cause of the error by verifying that the error presents itself when the offending channel is reconnected. c. Ensure that channel is properly terminated. d. Ensure that the backplane configuration jumpers settings are correct. e. Replace the failing cable. f. Replace the failing backplane. g. Disconnect one drive at a time that is attached to the failing channel, then; reboot to the system to determine which drive is causing the error. |
| EF10 (Default ISPR) | 1. N/A, controller is functioning properly. |
| EFFE (Firmware code corrupt or download jumpers are in place) | 1. Verity that the download jumpers (J15) are not in place. 2. Flash the controller firmware with the download jumpers in place ( two jumpers on J15, installed parallel to PCI slots), then remove the download jumpers. 3. RAID Controller. System Board, if integrated controller. |
| FFFF | 1. Isolate between SCSI Subsystem and Controller by disconnecting aII attached SCSI cables and reboot. IF IPSR code is NOT PRESENT 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. Verity correct termination of the failing channel. c. SCSI cable attached to the failing channel. d. Backplane attached to the failing channel. e. Disconnect one drive at a time attached to failing channel and reboot to determine which drive is causing the problem. 2. If the IPSR code remains after disconnecting aII SCSI cables then rebooting, replace system planar. |
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 January 2019
UID
ibm1DDSE-42ZJAQ