To decode sense codes that are reported from Raid Manager controlled devices, such as the a1000 and the a3x00 series, users should reference the file /usr/lib/osa/raidcode.txt on their system. They may also reference the Status window in the rm6 gui to see the messages generated by the array along with the decoded explanation of any sense codes. For situations where a hardware failure has occurred, the Recovery Guru application in the Recovery window will provide assistance.

Users may reference the sense code listing below. This is a copy of the raidcode.txt file that is included with Raid Manager 6.22,REV=0.14.

=====

RAID ERROR CODE DESCRIPTIONS

This document describes the various error codes returned by the Series 3 RAID controllers. On detection of an error condition, the controller will return a status of Check Condition on the command that had the error. The host should respond with a Request Sense command. On receipt of the Request Sense, the controller will return sense data, which includes the Sense Key, FRU Code, and ASC/ASCQ information, indicating the reason for the error condition.

SENSE KEYS

The possible Sense Keys returned by the RAID controller in the sense data, on receipt of a Request Sense command are shown below. The Sense Key is returned in byte 2 (zero-referenced) of the Request Sense data. The Sense Key may be thought of as a summary code for the error. More detailed information about the error is provided by the FRU and ASC/ASCQ codes described in the next sections.

(0x00)-No Sense

The controller has no errors to report at this time.

(0x01)-Recovered Error

The controller detected the error, but was able to recover from it.

(0x02)-Not Ready

The controller is in the process of finishing initialization, and will not allow hosts access to user data until it is ready.

(0x03)-Media Error

A drive attached to the controller detected a media error on itself.

(0x04)-Hardware Error

This Sense Key is typically returned by the controller on most unrecoverable errors.

(0x05)-Illegal Request

A command was issued to the controller that is not allowed (for example, access to a non-existent logical unit).

(0x06)-Unit Attention

The controller is informing the host of an action it took to remedy an exception condition (for example, the controller marked a drive Failed, because the drive could no longer be accessed).

(0x0B)-Aborted Command

The controller could not finish the requested operation. However, in the typical scenario, it will have taken some action to ensure that the error condition would not occur again. Therefore, the next time this same command is received, the same error condition should not occur.

(0x0E)-Miscompare

A failed Verify operation, or a Verify with Parity Check operation failure will return a Sense Key of Miscompare.

FIELD REPLACEABLE UNITS (FRU) CODE DEFINITIONS

Each time an error is detected, the controller will put the Field Replaceable Unit (FRU) code of the failed component in the sense data (byte 14 (zero-referenced) in the sense data for the first error and bytes 26-33 (zero-referenced) for additional errors). To provide meaningful information for troubleshooting, the FRU codes have been grouped. The defined FRU groups are listed below.

FRU Code Description

0x01 Host Channel Group

0x02 Controller Drive Interface Group

0x03 Controller Buffer Group

0x04 Controller ASIC Group

0x05 Controller Other Group

0x06 Subsystem Group

0x07 Not Used

0x08 Sub-enclosure Group

0x09-0x0F Reserved

0x10-0xFF Drive Groups

(0x01)-Host Channel Group

This group consists of the host SCSI bus, its SCSI interface chip, and all initiators and other targets connected to the bus.

(0x02)-Controller Drive Interface Group

This group consists of the SCSI interface chips on the controller which connect to the drive buses.

(0x03)-Controller Buffer Group

This group consists of the controller logic used to implement the on-board data buffer.

(0x04)-Controller Array ASIC

This group consists of the ASICs on the controller associated with the RAID functions.

(0x05)-Controller Other Group

This group consists of all controller-related hardware not associated with another group.

(0x06)-Subsystem Group

This group consists of subsystem components that are monitored by the RAID controller, such as power supplies, fans, thermal sensors, and AC power monitors.

(0x08)-Sub-Enclosure Group

This group consists of the devices such as power supplies, environmental monitor, and other subsystem components in the sub-enclosure.

(0x10-0xFF)-Drive Group

This group consists of a drive (embedded controller, drive electronics, and Head Disk Assembly), its power supply, and the SCSI cable that connects it to the controller; or supporting sub-enclosure environmental electronics. An FRU code denoting a drive contains the channel number (1-relative) in the upper nibble, and the drive's SCSI ID in the lower nibble. For example, a drive on the third channel, SCSI ID 2 would be denoted by an FRU code of 0x32.

ADDITIONAL SENSE CODES AND QUALIFIERS

This section lists the Additional Sense Code (ASC), and Additional Sense Code Qualifier (ASCQ) values returned by the RAID controller in the sense data. The ASC and ASCQ provide detailed information about the specific error.

SCSI-2 defined codes are used whenever possible. Array specific error codes are used when necessary, and are assigned SCSI-2 vendor unique codes 0x80 to 0xFF.

The most probable Sense Keys (listed below for reference) returned for each error are also listed in the table. Sense Keys of 6 in parentheses indicate that 6 (Unit Attention) would be the nominal Sense Key reported; however, the actual value would be that set in the "Sense Key for Vendor-unique Conditions" field in the User-configurable options of the NVSRAM.

ASCs and ASCQs are normally returned in bytes 12 and 13 (zero-referenced) of the sense data. On multiple errors (defined as errors that occurred on the same command, not necessarily as errors that occurred simultaneously), there may be additional ASCs and ASCQs in the ASC/ASCQ stack, which are bytes 22-25 (zero-referenced) of the sense data. In most cases, the first error detected is stored in bytes 12 and 13 of the sense data; subsequent errors are stored in the ASC/ASCQ stack.

The following section lists all possible ASC/ASCQ combinations returned by the controller.

ASC ASCQ Sense Key

00 00 0

No Additional Sense Information

The controller has no errors to report for the requesting host and addressed logical unit combination.

ASC ASCQ Sense Key

04 01 2

Logical Unit In Process Of Becoming Ready

The controller is executing its initialization functions on the addressed logical unit. This includes drive spin-up and validation of the drive and logical unit configuration information. This error is normally returned on commands following the initial Inquiry command after a power-up/reset.

ASC ASCQ Sense Key

04 02 2

Logical Unit Not Ready, Initializing Command Required

The controller is configured to wait for a Start/Stop Unit command before spinning up the drives, but the command has not yet been received.

ASC ASCQ Sense Key

04 04 2

Logical Unit Not Ready, Format In Progress

The controller previously received a Format Unit command from an initiator, and is executing that command on this logical unit. Other commands cannot be sent to this logical unit until the Format Unit completes.

ASC ASCQ Sense Key

04 81 02

Firmware Versions Incompatible

The versions of firmware on the redundant controllers are incompatible/inconsistent. This is probably because you replaced a failed controller with a new controller that does not have the same version of firmware. Controllers with an incompatible version of firmware may cause unexpected results. Therefore, you must download new firmware as soon as possible. Use the Recovery Guru/Health Check in the Recovery Application to obtain instructions on how to download firmware to make the versions consistent.

ASC ASCQ Sense Key

0C 00 4,(6)

Unrecoverable Write Error

If this error is reported during normal operation, the controller has detected an error on a write operation to a drive, but was unable to recover from the error. The drive that failed the write operation will be marked Failed.

If this error is reported just after a power loss has occurred, it indicates that the controller has detected that its batteries have been discharged.

> If the power loss was for a reasonably long time, wait for the controller's batteries to be recharged.

> If the power loss was for a very short time, the controller's cache holdup battery logic has failed.

> If the controller has on-board batteries (such as a 3601 RAID controller), replace the controller.

> If the controller has off-board batteries, check the battery hardware to ensure that there is no malfunction.

ASC ASCQ Sense Key

0C 01 1

Write Error Recovered With Auto Reallocation

The controller recovered a write operation to a drive. Auto reallocation may or may not have been used but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action.

ASC ASCQ Sense Key

0C 80 4,(6)

Unrecovered Write Error Due To Possible Battery Discharge And Alternate Controller Failure

If this error is reported during normal operation, it indicates that the controller had to synchronize and/or purge its cache due to configuration changes (such as logical unit deletion, addition or replacement), or if requested to do so by the host system, and the cache synchronization or purge failed for some reason. The user should restore any data that would have been lost.

This error is also reported in the following situations at power-up:

> The controller noted that it had dirty data in cache, and attempted to flush it to disk, but the flush operation failed. The dirty data will be lost. The user should restore any data that would have been lost.

> If the controller had been in write-back caching mode with caching without batteries disabled and mirroring DISABLED:

> The controller has detected that the batteries are either not physically present now, or they have fully discharged. Dirty user data in this controller's cache has been lost and the user must restore the dirty data.

> If the controller has its own on-board batteries, the user should replace the controller with a good one, or if that is impossible, turn off write-back caching until the controller can be replaced.

> If the controller has off-board batteries, the user should replace the batteries in the battery pack and ensure that the battery hardware is functioning normally.

> If the controllers had been in write-back caching mode with caching without batteries disabled and mirroring ENABLED:

> The controller has detected that its batteries, as well as those of the alternate controller are not functioning. Dirty user data in the cache has been lost and the user must restore the dirty data. The user must replace the controllers' batteries.

> The controller has detected that it was newly swapped into this subsystem, and that it had dirty data in cache. The dirty data cannot be flushed to disk because it has been removed from its original subsystem. The user should ignore the error, since no data loss has occurred on this subsystem.

> The controller has detected that its batteries are not functioning, and it had dirty cached data, and the alternate controller has been replaced by another controller (and therefore the mirrored copy of the cached data has been lost). Dirty user data in this controller's cache may have been lost and the user must restore the dirty data. The user must replace the controller's batteries. If possible, the user should swap-in the original alternate controller, so that the dirty data in that controller's cache may be reclaimed and flushed to disk.

ASC ASCQ Sense Key

0C 81 4,(6)

Deferred Unrecoverable Error Due To Memory Failure

Recovery from a Data Cache error was unsuccessful. User data may have been lost.

ASC ASCQ Sense Key

11 00 3

Unrecovered Read Error

An unrecovered read operation to a drive occurred and the controller has no redundancy to recover the error. The error probably occurred in RAID 0 or Degraded RAID levels 1, 3, or 5.

ASC ASCQ Sense Key

11 8A 3

Miscorrected Data Error - Due To Failed Drive Read

A media error has occurred on a read operation during interrupted write processing.

ASC ASCQ Sense Key

18 02 1

Recovered Data - Data Auto Reallocated

The controller recovered a read operation to a drive. Auto reallocation may or may not have been used but this is the only standard ASC/ASCQ that tells the initiator that no further actions are required by the driver. The host need not take any action.

ASC ASCQ Sense Key

1A 00 5

Parameter List Length Error

A command was received by the controller that contained a parameter list and the list length in the CDB was less than the length necessary to transfer the data for the command.

ASC ASCQ Sense Key

20 00 5

Invalid Command Operation Code

The controller received a command from the initiator that it does not support.

ASC ASCQ Sense Key

21 00 5

Logical Block Address Out Of Range

The controller received a command that requested an operation at a logical block address beyond the capacity of the logical unit. This error could be in response to a request with an illegal starting address or a request that started at a valid logical block address and the number of blocks requested extended beyond the logical unit capacity. The user should check the capacity of the logical unit, and retry the command after correcting it.

ASC ASCQ Sense Key

24 00 5

Invalid Field In CDB

The controller received a command from the host with an unsupported value in one of the fields in the command block.

ASC ASCQ Sense Key

25 00 5

Logical Unit Not Supported

The addressed logical unit is currently not configured. An Add Logical Unit operation to the Logical Array Mode Page must be executed to define and configure the logical unit before it is accessible.

ASC ASCQ Sense Key

26 00 5

Invalid Field In Parameter List

The controller received a command with a parameter list that contained an error. This error is typically returned on a Mode Select if:

> an attempt was made to issue the Mode Select to a non-supported mode page.

> an attempt was made to change a changeable mode page field with a Mode Select to an unsupported value.

> an attempt was made to reconstruct a drive that is not part of any logical unit. The typical scenario in this case is the deletion of a Degraded logical unit, leaving the Failed drive marked Failed.

> a Mode Select was issued to the Logical Array Page (page 2B) for a non-supported action (the "Action To Take" field was not set to a value 0x80-0x88).

ASC ASCQ Sense Key

28 00 6

Not Ready To Ready Transition

The controller has completed its initialization operations on the logical unit and it is now ready for access. This Unit Attention is used to notify hosts that the controller is ready to allow access to logical units. This notification is particularly useful if a host has exhausted its retry count soon after reset or power up.

ASC ASCQ Sense Key

29 00 6

Power On, Reset, Or Bus Device Reset Occurred

The controller has detected one of the above conditions.

ASC ASCQ Sense Key

29 04 6

Device Internal Reset

The controller has reset itself due to an internal error condition. Commands in progress have been lost.

ASC ASCQ Sense Key

29 81 (6)

Default Configuration Has Been Created

The controller has completed the process of creating a default logical unit. There is now an accessible logical unit that did not exist previously. The host should execute its device scan to find the new logical unit.

ASC ASCQ Sense Key

29 82 (6)

Controller Firmware Synchronized

The controller firmware was successfully synchronized with the replacement controller.

ASC ASCQ Sense Key

2A 01 6

Mode Parameters Changed

The controller received a request from another initiator to change the mode parameters for the addressed logical unit. This Check Condition is to notify the current initiator that the change occurred. This error may also be reported if the Mode Select parameters changed because of a cache synchronization error during the processing of the mode recent Mode Select request. The host should execute its device scan to determine the changes on the logical unit.

ASC ASCQ Sense Key

2A 02 6

Log Parameters Changed

The controller received a request from another initiator to change the log parameters for the addressed logical unit. This Check Condition notifies the current initiator that the change occurred. The host should be aware that the other host may have cleared log parameters, such as the controller's performance statistics or its AEN log.

ASC ASCQ Sense Key

2F 00 6

Commands Cleared By Another Initiator

The controller received a Clear Queue message from another initiator. This Check Condition is to notify the current initiator that the controller cleared the current initiator's commands if it had any outstanding commands. If the host had outstanding commands, it should retry them.

ASC ASCQ Sense Key

31 01 1,4

Format Command Failed

A Format Unit command issued to a drive returned an unrecoverable error. The drive will be identified in the FRU code of the sense data. The user should replace the drive.

ASC ASCQ Sense Key

32 00 4

Out Of Alternates

A Re-assign Blocks command to a drive failed. The drive will be identified in the FRU code of the sense data. The user should replace the drive.

ASC ASCQ Sense Key

3F 01 (6)

Drive Microcode Changed

The controller successfully downloaded new microcode to the specified drive, as requested by the host. This Unit Attention is used to notify the host that the Download Drive Microcode function completed successfully.

ASC ASCQ Sense Key

3F 80 (6)

Drive Failed Due To Write Failure

The drive failed a write command to it. The user should replace the drive.

ASC ASCQ Sense Key

3F 82 (6)

Drive Failed Due To Format/Restore Failure

The (previously-failed) drive was marked Failed due to either: (1) the drive failing a Format Unit command issued to it, or (2) the reconstruction on the drive failing due to the controller being unable to restore it (for example, an error occurring on another drive required for reconstruction). If the drive was marked Failed prior to reconstruction starting on it, the user should replace it. If the drive was Failed after reconstruction had begun, the drive was marked Failed because the controller could not reconstruct it. The user should format the entire logical unit, and then restore data from the last good tape backup.

ASC ASCQ Sense Key

3F 85 (6)

Drive Failed Due To No Response

The drive failed a Read Capacity or Read command at Start Of Day. The controller was unable to read the RAID subsystem configuration information stored on it. The user should replace the drive.

ASC ASCQ Sense Key

3F 86 (6)

Drive Failed Due To Format Failure

The drive failed either a Format Unit command, or a Write operation (issued when a logical unit was formatted). The user should replace the drive.

ASC ASCQ Sense Key

3F 87 (6)

Drive User-Failed Via Mode Select

The drive was manually failed by the user. The user should replace the drive.

ASC ASCQ Sense Key

3F 89 (6)

Wrong Drive Removed/Replaced

The user hot-removed a non-Failed drive. If the controller has not marked the drive Failed yet, the user should re-insert the drive as soon as possible. If the drive has been marked Failed, the user should replace it.

ASC ASCQ Sense Key

3F 8B (6)

Drive Capacity Less Than Minimum

The drive is not large enough to support all the logical units that must be reconstructed on it. The user should replace the drive with a larger capacity drive.

ASC ASCQ Sense Key

3F 8C (6)

Drive Has Wrong Block Size

The drive's block size does not match that of the other drives in the logical unit. The user should either: (1) issue a Mode Select command to the controller directing it to first format, and then reconstruct the drive, or (2) replace this drive with another drive pre-formatted to the block size used by all of the other drives in the logical unit.

ASC ASCQ Sense Key

3F 8D (6)

Drive Failed - Controller Storage Failure

The controller was unable to access or store internal RAID subsystem configuration information on the drive. The user should replace the drive.

ASC ASCQ Sense Key

3F 8E (6)

Drive Failed - Reconstruction Failure

A drive failed due to a reconstruction failure at Start of Day (SOD).

ASC ASCQ Sense Key

3F 98 (6)

Drive Marked Offline Due To Internal Recovery Procedure

An error has occurred during interrupted write processing causing the LUN to transition to the Dead state. Drives in the drive group that did not experience the read error will transition to the Offline state (0x0B) and log this error.

ASC ASCQ Sense Key

3F BD (6)

Drive Has Incorrect Critical Parameters Set

The controller was unable to query the drive for its current critical mode page settings, or was unable to change these to the correct setting. Currently, this indicates the Qerr bit is set incorrectly on the drive specified in the FRU field of the Request Sense data.

ASC ASCQ Sense Key

3F C3 (6)

Channel Failure

The controller failed a channel, and will not access drives on this channel any more. The FRU Group Qualifier (byte 26) in the sense data will indicate the 1-relative channel number of the failed channel. This condition is typically caused by a drive ignoring SCSI protocol on one of the controller's destination channels. The controller typically fails a channel if it issued a reset on a channel, and it continued to see drives ignore the SCSI Bus Reset on this channel.

ASC ASCQ Sense Key

3F C7 (6)

Non-Media Component Failure

(1) A subsystem component other than a drive or controller has failed (for example, fan, power supply, battery) or (2) An over-temperature condition has occurred (some RAID modules contain a temperature sensor). The fans, power supplies, and battery are usually located in the controller module tray. The FRU codes will indicate the faulty component. The user should replace the component indicated.

ASC ASCQ Sense Key

3F C8 (6)

AC Power Fail

The Uninterruptible Power Source (UPS) has indicated that AC power is no longer present and the UPS has switched to standby power. While there is no immediate cause for concern, users should save their work frequently, in case the battery is suddenly depleted.

ASC ASCQ Sense Key

3F C9 (6)

Standby Power Depletion Imminent

The Uninterruptible Power Source (UPS) has indicated that its standby power source is nearing depletion. The host should take actions to stop IO activity to the controller. Normally, the controller will change from a write-back caching mode to a write-through mode. The user should not change again to write-back mode until full AC power has been restored.

ASC ASCQ Sense Key

3F CA (6)

Standby Power Source Not At Full Capacity

The Uninterruptible Power Source (UPS) has indicated that its standby power source is not at full capacity. To prevent loss of data in the event of the failure of AC power, the user should not activate write-back caching mode until full UPS power has been restored.

ASC ASCQ Sense Key

3F CB (6)

AC Power Has Been Restored

The Uninterruptible Power Source (UPS) has indicated that AC power is now being used to supply power to the controller.

ASC ASCQ Sense Key

3F D0 (6)

Write-Back Cache Battery Discharged

The controller has detected that its battery is no longer charged. If a power failure were to occur, any dirty user data in cache will be lost. To prevent the loss of any user data, the user should either: (1) replace this controller with another, or (2) turn off write-back cache.

ASC ASCQ Sense Key

3F D1 (6)

Write-Back Cache Battery Charged

The controller has detected that its battery is now fully charged, and will be capable of holding up the cache contents in the event of a power failure. The user may switch to write-back mode, if desired.

ASC ASCQ Sense Key

3F D8 (6)

Battery Reached Expiration

The controller has failed the battery because the battery has reached its expirations date. You should replace the battery as soon as possible.

ASC ASCQ Sense Key

3F D9 (6)

Battery Near Expiration

The controller has detected that the battery is nearing its expiration date. You should replace the battery as soon as possible.

ASC ASCQ Sense Key

3F E0 (6)

Logical Unit Failure

The controller has placed the logical unit in a "Dead" state. User data and/or parity can no longer be maintained to ensure availability. The most likely cause is the failure of a single drive in non-redundant configurations or a second drive in a configuration protected by one drive. The data on the logical unit is no longer accessible.

ASC ASCQ Sense Key

3F EB (6)

LUN Marked Dead Due To Media Error Failure

An error has occurred during interrupted write processing during Start of Day causing the LUN to transition to the Dead state.

ASC ASCQ Sense Key

40 NN 4,(6)

Diagnostic Failure On Component NN (0x80 - 0xFF)

The controller has detected the failure of an internal controller component. This failure may have been detected during operation as well as during an on-board diagnostic routine. The values of NN supported in this release are listed as follows:

> 80 - Processor RAM

> 81 - RAID buffer

> 82 - NVSRAM

> 83 - RAID Parity Assist (RPA) chip

> 84 - Battery-backed NVSRAM or clock failure

> 91 - Diagnostic self test failed non-data transfer components test most likely controller cache holdup battery discharge)

> 92 - Diagnostic self test failed data transfer components test

> 93 - Diagnostic self test failed drive Read/Write Buffer data turnaround test

> 94 - Diagnostic self test failed drive Inquiry access test

> 95 - Diagnostic self test failed drive Read/Write data turnaround test

> 96 - Diagnostic self test failed drive self test

In a dual controller environment, the user should place this controller offline (hold in reset) (unless the error indicates controller battery failure, in which case the user should wait for the batteries to recharge). In single controller environments, the user should not use this subsystem until the controller has been replaced.

ASC ASCQ Sense Key

43 00 4

Message Error

The controller attempted to send a message to the host, but the host responded with a Reject message.

ASC ASCQ Sense Key

44 00 4,B

Internal Target Failure

The controller has detected a hardware or software condition that does not allow the requested command to be completed. If the Sense Key is 0x04 indicating a Hardware Failure, the controller has detected what it believes is a fatal hardware or software failure and it is unlikely that just a retry of the command would be successful. If the Sense Key is 0x0B indicating an Aborted Command, the controller has detected what it believes is a temporary software failure that is likely to be recovered if retried.

ASC ASCQ Sense Key

45 00 4

Selection Time-out On A Destination Bus

A drive did not respond to selection within a selection time-out period. Possible reasons for this error include drive failure, channel failure, or the possibility of an incomplete hot-swap holding the whole channel in reset.

ASC ASCQ Sense Key

47 00 1,B

SCSI Parity Error

The controller detected a parity error on the host SCSI bus or one of the drive SCSI buses.

ASC ASCQ Sense Key

48 00 1,B

Initiator Detected Error Message Received

The controller received an Initiator Detected Error Message from the host during the operation.

ASC ASCQ Sense Key

49 00 B

Invalid Message Error

The controller received a message from the host that is not supported or was out of context when received.

ASC ASCQ Sense Key

49 80 B

Drive Reported Reservation Conflict

A drive returned a status of Reservation Conflict.

ASC ASCQ Sense Key

4B 00 1,4

Data Phase Error

The controller encountered an error while transferring data to/from the initiator or to/from one of the drives.

ASC ASCQ Sense Key

4E 00 B

Overlapped Commands Attempted

The controller received a tagged command while it had an untagged command pending from the same initiator, or it received an untagged command while it had a tagged command(s) pending from the same initiator.

ASC ASCQ Sense Key

80 02 4

Bad ASC Code detected by Error/Event Logger

ASC ASCQ Sense Key

80 03 4

Error Occurred During Data Transfer From SRM Host

ASC ASCQ Sense Key

84 00 4

Operation Cannot Be Completed With LUN In Its Current State

The requested command or Mode Select operation is not allowed with the logical unit in the state indicated in byte 76 of the sense data. Typically, the controller will return this error if:

> A Repair Parity, Write And Verify With Parity Check, or Reassign Blocks command was issued to the logical unit, but the logical unit is either in the Degraded or Reconstructing state.

> A Test Unit Ready was issued to a Dead logical unit, and the NVSRAM option that directs the controller to return a Good status in this case has not been enabled.

> A user data access command (Read or Write) was issued to a Dead logical unit.

> The user attempted to replace a logical unit, but the logical unit is currently in the Reconstructing state.

> The user attempted to add a logical unit, but the specified logical unit already exists.

> The user attempted to check available capacity for logical unit addition, but no logical unit exists on the specified set of drives.

> The user attempted to delete, modify, replace or format a non-existent logical unit.

ASC ASCQ Sense Key

84 06 4

Logical Unit Awaiting Format

A Mode Select has successfully completed to create a logical unit, but the logical unit has not been formatted.

ASC ASCQ Sense Key

85 01 4

Drive IO Request Aborted

IO issued to failed or missing drive due to recently failed removed drive. This error can occur as a result of IOs in progress at the time of a failed or removed drive.

ASC ASCQ Sense Key

87 00 4

Microcode Download Error

The controller detected an error while downloading microcode and storing it in non-volatile memory.

ASC ASCQ Sense Key

87 08 4

Microcode Download Error

Incompatible board type for the code downloaded.

ASC ASCQ Sense Key

88 0A (6)

Subsystem Monitor NVSRAM Values Configured Incorrectly

The controller detected an error in the configuration of the Subsystem Fault region of the NVSRAM. This error means that the controller either cannot turn on or turn off the desired Fault LEDs.

ASC ASCQ Sense Key

8A 00 5

Illegal Command For Drive Access

The initiator attempted to pass a command through to a drive that is not allowed. The command could have been sent in pass-through mode or by attempting to download drive microcode.

ASC ASCQ Sense Key

8A 01 5

Illegal Command For The Current RAID Level

The controller received a command that cannot be executed on the logical unit due to its RAID level configuration. Examples are parity verify or repair operations on a RAID 0 logical unit. The user should check the command being attempted, and ensure that it is being issued to a logical unit configured to an appropriate RAID level.

ASC ASCQ Sense Key

8A 10 5

Cannot Perform Modification - Non-standard Segment Size/Insufficient Resources

Could not perform the modification because either (1) some or all of the LUNs in the group have non-standard segment sizes or (2) the RAID controller doesn't have sufficient resources to perform it.

For Cause #1:

Check the segment sizes of the LUNs by using Module Profile>>LUNs. The standard segment sizes (in blocks) are: 16, 32, 64, 128, 256, and 512. If some of the LUNs in the group have non-standard segment sizes, the only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size.

For Cause #2:

If the LUNs in the group have standard segment sizes, use Options>>Modify Group/LUN>>Segment Size in Configuration and attempt to select a smaller size and retry the modification operation. If the modification operation fails again, the only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size.

ASC ASCQ Sense Key

8B 02 B,(6)

Quiescence Is In Progress Or Has Been Achieved

The addressed logical unit has been quiescent. Redundant controller mode changes or logical unit ownership transfers will be, or already are in progress.

ASC ASCQ Sense Key

8B 03 B

Quiescence Could Not Be Achieved Within The Quiescence Timeout Period

It was not possible to make the requested logical units quiescent within the specified period. The make-quiescent attempt has been aborted, and controller mode changes, or logical unit ownership transfers will not be attempted.

ASC ASCQ Sense Key

8B 04 5

Quiescence Is Not Allowed

It is not possible to make the requested logical units quiescent at this time, probably because another initiator has already requested quiescence in anticipation of a redundant controller mode change, or a logical unit ownership transfer.

ASC ASCQ Sense Key

8E 01 E,(6)

A Parity/Data Mismatch Was Detected

The controller detected inconsistent parity/data during a parity verification.

ASC ASCQ Sense Key

91 00 5

General Mode Select Error

An error was encountered while processing a Mode Select command. This error could returned for the following reasons:

> An invalid "Action To Take" value was set in the Mode Select page.

> An attempt was made to clear all drive and logical unit configurations by issuing a "CLEAR" to the Redundant Controller Mode Page, but the Mode Select was sent to the controller with the lower drive-side SCSI ID.

> The controller could not save configuration information to the drives when a logical unit was added or replaced. The user should verify that the drives' hardware is functioning correctly, or replace the drive listed in the FRU code.

> The controller could not spin up a drive that the user manually added via the "Add Drive" operation via a Mode Select to the Physical Array Page. The user should verify that the drive's hardware is functioning correctly, or replace the drive.

> The controller could not mark a failed drive Optimal, if the user wished to do so via a Mode Select to the Physical Array Page.

> The user attempted to mark failed an Optimal drive in an already-Dead LUN.

> The user attempted to mark a failed drive as Replaced, but the controller could not access the failed drive. The user should verify that the drive's hardware is functioning correctly, or replace the drive.

> The user attempted to mark a failed drive as Replaced in a logical unit that is either Dead or formatting. The user should bring the logical unit to the appropriate state before attempting the operation again.

> The user requested the controller to initiate a parity scan on all logical units, but the controller is the Passive controller. The user should retry the operation via the Active controller.

> The user requested an operation that caused the controller to synchronize and purge its cache (such as logical unit addition, deletion, or replacement, a transfer of ownership of the logical unit from one controller to another, or a change in the redundant controller mode of operation), but either the synchronize or the purge of the cache failed.

ASC ASCQ Sense Key

91 03 5

Illegal Operation For Current Drive State

A drive operation was requested through a Mode Select that cannot be executed due to the state of the drive. This error could be returned for the following reasons:

> The user attempted to mark a non-existent drive as Optimal, Failed, Non-existent or Replaced, or assign or deassign the non-existent drive as Global Hot Spare.

> The user attempted to operate on a drive on a non-supported channel or SCSI ID. For example, attempting to "Add a Drive" to channel 7 on a 5-channel RAID controller.

> The user attempted to add or replace a logical unit on a drive that is neither in an Optimal (but not Global Hot Spare) nor Spare state.

> The user attempted to reassign blocks on a non-existent drive.

> The user attempted to format a logical unit which has missing drives in it.

> The user attempted to format a logical unit which exists on a set of drives that have SubLUNs on them.

> The user attempted to mark a reconstructing drive (status of Replaced) as Optimal.

> The user attempted to mark a non-failed drive as Replaced.

> The user attempted to delete a drive, but the drive was not marked unassigned (it belongs to a logical unit).

> The user attempted to revive a logical unit that (1) is not currently marked Dead, (2) has missing drives in it, (3) has drives in it that are marked Wrong Drive Replaced, or (4) has multiple drives that are marked Failed, but not all of the failed drives are on the same channel.

> The user attempted to download drive firmware to a drive that is not owned by this controller, or the drive is either Non-existent or has been removed.

> The user attempted to mark a failed drive as Replaced, but the drive's capacity is too small to support the logical units configured on the drive group.

> The user attempted to mark a drive as Replace, Format And Reconstruct that is neither in the Failed or Replaced states.

ASC ASCQ Sense Key

91 09 5

Illegal Operation With Multiple SubLUNs Defined

An operation was requested that cannot be executed when multiple SubLUNs are defined on the drive. This error could be returned for the following reasons:

> The user attempted to add or replace a SubLUN on a drive group which is configured with logical units configured to a different RAID level.

> The user attempted to add or replace a SubLUN on a drive group which its drives are not in the same sequence as that for the other SubLUNs on them.

> The user attempted to let one controller take over the ownership of certain SubLUNs, but all SubLUNs on the affected drive group were not transferred.

ASC ASCQ Sense Key

91 33 5

Illegal Operation For Controller State

The requested Mode Select operation could not be completed due to the current state of the controller. This error could be returned for the following reasons:

> The user attempted to fail or unfail the alternate controller, but the current controller is in the Passive mode of operation.

> The user attempted to switch from Active-Passive mode of operation to Active-Active mode, but this is a single controller system.

> The user attempted to direct this controller to fail the alternate controller, but the alternate controller still owns some of the configured logical units.

ASC ASCQ Sense Key

91 36 5

Command Lock Violation

The controller received a Write Buffer Download Microcode, Send Diagnostic, or Mode Select command, but only one such command is allowed at a time and there was another such command active.

ASC ASCQ Sense Key

91 50 5

Illegal Operation For Drive Group State

An operation was requested that cannot be executed because of the current state of the drive group (such as a modification operation being performed).

ASC ASCQ Sense Key

91 51 5

Cannot Perform Modification - Insufficient Reserved Capacity

A modification operation (RAID level, segment size, capacity expansion, or defragmentation) could not be performed because there is insufficient capacity reserved on each drive for internal configuration purposes. If you want to complete this modification, the only solution is to back up the data on the drive group's LUNs, delete the LUNs, and recreate them with the desired RAID level, number of drives, and segment size.

NOTE: There may be a decrease in drive group capacity when recreating the LUNs (about 38 MB per drive), since this drive group was originally created with pre-2.05 controller firmware and release 3.X controller firmware requires more reserved capacity per drive for internal configuration purposes.

ASC ASCQ Sense Key

94 01 5

Invalid Request Due To Current LUN Ownership

The operation is not allowed because the controller does not own the logical unit. The user should change the logical unit's owner, or attempt the operation from the owning controller.

ASC ASCQ Sense Key

95 01 4

Extended Drive Insertion/Removal Signal

The controller has detected that the drive insertion/removal signal is permanently active. The user should ensure that the drives on the affected channel are properly seated.

ASC ASCQ Sense Key

95 02 (6)

Controller Removal/Replacement Detected

The controller detected the activation of the signal(s) used to indicate that the alternate controller has been removed or replaced.

ASC ASCQ Sense Key

98 01 (6)

Multiple Drive Trays With Same ID

The controller has determined that there are multiple drive trays with the same ID selected. The user should ensure that each drive tray has a unique ID setting.

ASC ASCQ Sense Key

A0 00 (6)

Write-Back Cache (With Mirroring) Could Not Be Enabled

The user requested the controller to enable write-back cache, but the controller was unable to do so because:

> A battery was charging after a power cycle. If the RAID Module was power cycled, the user should wait approximately 12 to 15 minutes. The caching should be enabled again.

> Mirroring was requested, but this controller cannot do so because: (1) its batteries are not operational, and the cache-without-batteries (CWOB) feature is disabled, or (2) its batteries are not present, and the CWOB feature is disabled, or (3) the alternate controller's batteries are either not present or not operational, and the CWOB feature is disabled. The user should replace this controller with another one, or should turn off write-back caching.

> The controller was mirroring data, and the Force Write Through on Two Minute Warning bit (FWT) is set, and it has now detected a two minute warning from the UPS. It will now transition to write-through mode until full AC power has been restored. The user should not re-enable write-back caching until full AC power is restored.

> Mirroring was requested, but the alternate controller is not ready to mirror. The user should ensure that the alternate controller is present in the RAID Module and that it is functional.

> The controller was mirroring data, and now detects that the mirrors are out of synchronization, because: (1) a mirror operation failed, or (2) the alternate controller was removed. The user should ensure that the alternate controller is present in the RAID Module and that it is functional.

ASC ASCQ Sense Key

A1 00 (6)

Write-Back Cache (With Mirroring) Could Not Be Enabled - Cache Size

Mismatch

The controller will not allow mirroring to be enabled if the alternate controller's cache size is different. The user must ensure that both controllers in the subsystem have the same cache size.

ASC ASCQ Sense Key

A4 00 (6)

Global Hot Spare Drive Smaller Than At Least One Drive In The Subsystem

A drive designated as Global Hot Spare does not have the capacity to cover all of the drives in the RAID subsystem. The user should attempt to ensure that the Global Hot Spare drive has a capacity as large as the largest capacity drive in the RAID subsystem. Note that the Global Hot Spare drive will still be used to cover any smaller capacity drives.

ASC ASCQ Sense Key

A6 00 (6)

Recovered Processor Memory Failure

The controller has detected and corrected a recoverable error in processor memory.

ASC ASCQ Sense Key

A7 00 (6)

Recovered Data Buffer Memory Error

The controller has detected and corrected a recoverable error in the data buffer memory. Sense bytes 34-36 will contain the count of errors encountered and recovered.

ASC ASCQ Sense Key

C0 00 4,(6)

The Inter-controller Communications Channel Has Failed

The controller has detected the failure of the communications link between the redundant controllers. A switch to Active-Active mode of operation will not be allowed.

ASC ASCQ Sense Key

D0 06 4

Drive IO Time-Out

The controller destination IO timer expired while waiting for a drive command to complete. This error is possible if the drive's power was suddenly turned off, or if there is an extended reset on the channel due to an incomplete drive removal/insertion. The user should check that the drive is still powered up. If there was a drive removal/insertion on this channel a few seconds ago, the user should ensure that the drive is completely seated in the subsystem.

ASC ASCQ Sense Key

D1 0A 4

Drive Reported Busy Status

A drive returned a Busy status in response to a command.

ASC ASCQ Sense Key

E0 XX 4

Destination Channel Error

If XX = 00 - 07, it indicates the Sense Key returned by the drive after a Check Condition status. If XX = 10, it indicates that a bus level error occurred. If the same error continues to be returned, the user should replace the drive.

Internal Summary

• This document was published at the Knowledge Management team's request.