HP StorageWorks 7100 Appendix

Appendix A. Disk Array Controller Log

The array controller continually monitors all components of the disk array, and logs any information that may be of helpful in
evaluating the performance and operation of the array. All aspects of array operation are logged, including:

• changes to the operating status of the array

• changes to the configuration of the array

• performance data

• port er ror statistics

Table 1 lists all event codes that can appear in the controller log event pages. The table also includes events that are not
logged, but can still generate SCSI sense data. Appropriate corrective action is included for all events that require it. Many
events are informational and require no action on the part of the user. The Suspected Component column lists the hardware
components potentially implicated by the event code.

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con

e disk dr ive returned a status of

Error! No text of specified style in document.

Table 1. Controller Log Event Code Descriptions

Event

Number

(dec/hex)

0/0x0
1/0x01
2/0x02

3/0x03
4/0x04
5/0x05

6/0x06

7/0x07
8/0x08
9/0x09

10/0x0a
11/0x0b
12/0x0c

13/0xd

14/0x0e

15/0x0f

16/0x10

17/0x11

18/0x12

19/0x13
20/0x14

21/0x15

22/0x16

23/0x17

Event
Name

No Sense N N.A. None N No sense data is available.
Undefined N N.A. None N Undefined event code.
Unsupported LUN Capacity N N.A. None N An attempt was made to create a LUN with an

Parameter List Length Error N N.A. None Y The length of the para met er li st was incorrect for the

Invalid Field In Parameter List N N.A. None Y One or more of the fields in the parameter list

No Physical Device Present N N.A. None Y A command attempted to access a device (disk or

Invalid Opcode N N.A. None Y The opcode in the command that was received is not

Invalid Bit In CDB N N.A. None Y One or more fields in the CDB contained an illegal

Logical Block Address Out Of
Range
Not Ready N N.A. None N The array is not ready to process the command that

Undefined N N.A. None N Undefined event code.
Power On Unit Attention N N.A. None N The array just completed a reset operation.
Hardware Error Unit Attention N N.A. None Y The most recent reset operat ion detected a hardware

Commands Cleared Unit
Attention

Mode Parameters Changed
Unit Attention

Unconfigured LUN N N.A. None N The LUN to which the command was sent is

Invalid Target LUN N N.A. None N The subsystem does not support the LUN that was

Invalid Source LUN N N.A. None N The subsystem does not support the LUN that was

Not Enough Space Y Ignore None Y A write command had to move data in order to find

Command Illegal In Current
State
Becoming Ready N N.A. None N The subsystem is not ready to process the command

Recovered With Low Level
Retries

Recovered By Disk Drive Y See information

Disk Drive Media Error Y See informa tion Disk Dri ve N Th

Predictive

Maintenance

Implication

Logged?

N N.A. None Y The LBA specified in the command was out of

N N.A. None N Another originator sent commands to the array that

N N.A. None N Another initiator sent commands to the array that

N N.A. None N The current subsystem state precludes processing of

Y Ignore Disk,

provided by

drive vendor

Suspected
Components

controller, disk
interface

Disk Driv e N The d isk driv e r eturned a status of

Description

Mfg Fail?

unsupported capacity. The capacity was either zero
or was greater than the maximum LUN capacity
supported by the subsystem.

command and it’s parameters.

contained an invalid value.

enclosure controller) that is not currently present in
the subsystem.

supported by the subsystem. This error could be
due to the LUN Security configuration.

or unsupported value.

range for the LUN that it was sent to.

was received. Furthermore, the array will not
become ready until an initializing command is
received and successfully processed.

error during a selftest operation.

resulted in commands being cleared for the current
originator.

resulted in shared mode parameters being changed
for the current initiator.

currently not configured for use.

specified in the most recent command. The LUN is
the target of the requested action.

specified in the most recent command. The LUN is
the source of the requested action.

enough space to complete. Errors were encountered
during this process which precluded the controller
from providing enough space for the write. This
would generally result from multiple failing or
missing drives. This failure can also result from
faulty space management logic in the controller.

the requested command.

that was received. However, it is in the process of
becoming ready and will be able to process that
command soon.

N On a previous attempt(s), the drive failed the I/O.

The PDD retried th e I/O and the drive returned good
status. PDD stands for Physical Device Driver.
Specifically this error indicates that the RAID
implementation was not involved in the retries.

CHECK_CONDITION, RECOVERED_ERROR.

Event

A state conflict was detected in an attempt to down

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

24/0x18

25/0x19

26/0x1a

27/0x1b
28/0x1c

29/0x1d

30/0x1e

31/0x1f

32/0x20

33/0x21

34/0x22

35/0x23

36/0x24

Logged?

provided by

drive vendor

Mfg Fail?

CHECK_CONDITION, MEDIA_ERROR. The
PDD’s retries are exhausted. The PDD may or may
not have attempted a REASSIGN BLOCKS
command.

Disk Drive Hardware Error Y See informa tion

provided by

drive vendor

Disk Driv e N The d isk driv e r eturned a status of

CHECK_CONDITION, HARDWARE_ERROR.
The PDD’s retries are exhausted or the the I/O is not

retryable.
Disk Drive Reset By Related
Hot Plug

N N.A. None N A device sharing the same backend bus as this drive

was either inserted or removed causing a bus reset.

The ID returned status of HOT_RESET_ID for this

I/O. The PDD could not retry this I/O either

because it is not retryable, or its retries were

exhausted.
Disk Drive Reset Itself Y Ingore if

accompanied by

hot plug.

Disk Driv e N The d isk driv e r eturned a status of

CHECK_CONDITION, UNIT_ATTENTION,

PWR_ON_RESET. The PDD could not retry this

I/O. If there wasn’t already a reconfiguration in

progress when the PDD got the callback for this I/O,

the PDD used the JCB for this I/O to reconfigure the

drive; the UNIT ATTENTION condition has

already been cleared. Recommend that the client

retry the I/O.
Disk Drive Reset by Pass
Through
Disk IO Failed Due To Drive
Removal

Y Ignore None N A passThruReset occurred. The PDD could not

retry this I/O.

N N.A. None N Subsequent to a hot removal, the PDD’s destroy

method was invoked. I/Os in the PDD’s waiting

queue are flushed with this status. Active I/Os

which complete with good status, after the destroy

method is invoked, but which executed during a

device configuration, will also be returned with this

status. (Active I/Os which comp lete with good

status status and not concurrent with device

configuration will be returned with good st atus.)
Disk Drive Failed Initialization Y N.A. None Y A disk drive failed the reconfiguration attempt

(TUR, inquiry, mode sense, mode select, read

capacity). The PDD attempted a device

reconfiguration after the device was reset during the

normal course of operation (i.e. not during a hotplug

of this drive, but possibly during a hotplug of

another drive). If the device reconfiguration fails,

the PDD flushes all non-passthru I/Os from its

waiting queue with this status. The I/O whose JCB

was used for the config is also returned with this

status. If there was active I/Os concurrent with the

config, it is also returned with this status.
Disk I/O Failed Due To
Related Hot Plug

Y Ignore. None N The I/O executed concurrently with a device

reconfiguration. The state of the drive was

unknown (danger of write cache being enabled.)

The I/O was not retryable or the PDD’s retries are

exhausted. The I/O should be retried by the client.
Unexpected Disk Drive Error Y Single

Occurrance

Unless Excluded

For Drive Type

Disk Drive N The drive returned CHECK CONDITION status

with meaningless sense data, or sense data not

otherwise handled by the PDD’s error recovery

algorithms. The PDD’s retries are exhausted or the

I/O is not retryable.
Invalid SLRC transition N N.A. None N An attempt was made to change the SLRC mode

parameter from a value of AutoRAID to RAID1

while LUNs were configured in the subsystem. This

transition cannot be made unless no LUNs are

configured.
Disk Drive Miscompare on
Write And Verify

Y Single

Occurrance

Disk Drive,
Controller, Disk
Interface

N The disk drive returned a MISCOMPARE error

status. The PDD’s retries are exhausted or the I/O is

not retryable.
Disk Drive State Conflict Y Ignore None N The PDM was in the wrong state for read, write or

pass thru. down, missing or initialization failed.

missing.
Disk Drive Data Out Of Sync
After Access

Y Ingore - See

accomapnying

None N Data being read or written on a device through the

PDM was out of sync after the access was complete.

errors

Illegal Drive State For Down N N.A. None N

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con
Error! No text of specified style in document.

Event

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

37/0x25

38/0x26

39/0x27

40/0x28

41/0x29

42/0x2a
43/0x2b

44/0x2c

45/0x2d

46/0x2e

47/0x2f

48/0x30

49/0x31

50/0x32

Logged?

Command a PDM. This covers conflicts in both the device

Recovered With RAID 5
Retries

Recovered With RAID 5
Redundancy

Unavailable Dat a Detected By
RAID 5

Send Diagnostic Self Test
Failure

Invalid Pass Through N N.A. None Y The host attempted an execute pass thru command

Pass Through Reset Failed Y Ignore None N Passthru reset resulted in a bad status.
Recovered With RAID 1
Redundancy

Invalid RG ID N N.A. None N A command that specifies an Redundancy Group ID

Shutdown Failed N N.A. None N CFM could not shutdown the subsystem because no

Not Enough Space Y Ignore - See

Disk Drive Removed During
Add Physical Drive

Cancel Rebuild With Auto­Rebuild Enabled

Disk Drive Stamp Write Failed Y Single

Disk Drive State Changed
During Add Physical Drive

Y Ignore - See

accompanying

errors

Y Ignore - See

accompanying

errors

Y See

Accompanying

Errors

N Single

Occurrance

Y Ignore - See

Accompanying

Errors

accompanying

errors

N N.A. None N A drive disappeared from the subsystem through hot

N N.A. None Y A rebuild operation was cancelled by the host while

Occurrance - See

accompanying

errors

N N.A. None N During the add physical drive command the drive is

None N Retries were used by the R5 module in the

None N Redundancy was used by the R5 module in the

None N R5 detected that the devices necessary for a read or

Controller Y Send Diagnostic Self test failure The current system

None N Redundancy was used by the R1 module in the

None Y A write command had to move data in order to find

Disk Drive,
Controller, Disk
Interface

Mfg Fail?

state in the PDM label and the sync stat e of the data

effected by the down.

successful completion of a read or write. This error

code has been replaced by 96&97, but has been left

in the table so that log readers built from this file

will be able to read old fi rmware.

successful completion of a read or write. This error

code has been replaced by 98&99, but has been left

in the table so that log readers built from this file

will be able to read old fi rmware.

write were not available for access before the access

was attempted. This can apply to an initial attempt

to read or write or to a retry.

state and warnings indicate that the self test should

return bad status.

without a valid Set Pass Thru Mode command

preceding it.

successful completion of a read or write. This error

code has been replaced by 100&101, but has been

left in the table so that log r eaders built from this fil e

will be able to read old fi rmware.

specified one that is invalid for the current

subsystem configuration.

volume set memb er s were present (a ll members

missing)

enough space to complete. Errors were encountered

during this process which precluded the controller

from providing enough space for the write. This

would generally result from multiple failing or

missing drives. This failure can also result from

faulty space management logic in the controller.

plug removal while an add physical drive command

was in progress against the drive.

auto-rebuild was enabled. Since auto-rebuild is

enabled, rebuild would only start up again after the

cancel, r endering it ineffective. Therefore the

controller rejects cancel rebuild commands while

auto-rebuild is enabled.

N In order to make a drive a member of a volume set it

must have a stamp written onto it by the controller.

This error indicates that the writing or updating of

the stamp failed during an add physical drive

command, causing the command to fail.

reconfigured for ICE access. If the reconfiguration

process su cceeds when it previously failed, then the

disposition of the drive must be reassessed by the

controller. This is processed as an independent hot

plug event which may cause the host to reconsider

whether or not to add the drive to the volume set.

Therefore the add physical drive command fails if

this condition is encounte r e d. The drive state sho ul d

be reassessed then the add command reattempted if

appropria te.this err is intentionally not logged (in

general, all * hdwr errs a r e logged)

Event

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

51/0x33

52/0x34

53/0x35

54/0x36

55/0x37

56/0x38

57/0x39

58/0x3a

59/0x3b
60/0x3c

61/0x3d

62/0x3e

63/0x3f

64/0x40

65/0x41

66/0x42

67/0x43

68/0x44
69/0x45

Offline firmware download
with disk size derating

Logged?

N Ignore None N An offline con troller firmware download was

Mfg Fail?

attempted while disk size derating was in effect.

Derating of the disks causes the shutdown portion of

the offline download to post the shutdown image at

the wrong location on the disk, and, as a result, the

subsystem boots to a No Maps state after the

download. To prevent this error, remove the disk

derating and try the download again.
Concurrent downloads
attempted

Y Ignore - Host

Problem

None Y A host attempted to start a controller firmware

download operation while another was already in

progress.
Feature capability exceeded N Ignore - Host

Porblem

None N A host request was found to require more capability

than current feature l ice nsing has enabled. This may

be a request for an operation that is not enabled in a

currently licensed feature.
Incompatible Image family N Ignore - Normal

for some cases of

firmware

None N The firmware image that was sent is of a family that

is incompatible with the currently executing

firmware. As a result, the download c annot be

performed online.
Configuration change occurred
during discover subsystem

N Ignore - should

be handled by

host

None Y A configuration change or component hot plug was

detected during the execution of the Discover

Subsystem command. As a result, the response that

was built may not reflect the current configuration.
Download Image Checksum
Failure

Y Ignore - Likely

image

None Y The firmware image that was sent contained defects

such that the checksum verification failed.

distribution

problem
Unavailable Dat a Detected By
RAID1 Read

Y Ignore - See

accompanying

errors

None N R1 detected that the devices necessary for a read

were not available for access before the access was
attempted. This can apply to an initial attempt to

read or to a retry.
Unavailable Dat a Detected By
RAID1 Write

Y Ignore - See

accompanying

errors

None N R1 detected that the devices necessary for a write

were not available for access before the access was

attempted. This can apply to an initial attempt to

write or to a retry.
Disk Interface Error Y N.A. None Y An error occurred on a disk interface command.
Unsupported feature N Ignore. Device

Management

None Y An attempt was made to install a license for a

feature that this product does not support.

error
LUN specified exceeds
maximum

N N.A. None Y An 8-byte hierarchic LUN reference specified a

LUN value that exceeds the maximum specified by
the LUN creation limit mode parameter.

Reassign Failed Y Single

Occurrance

Reassign Out Of Resources Y Single

Occurrance

Disk Drive Y The PDD’s attempts to reassign a bad block failed

due to device errors.

Disk Drive Y The PDD was unable to complete a Reassign Blocks

command because the sparing buffer is too small.

Optimal Space Error In RAID 5 Y Ingore None N R5 detected that space allocated for an "optimal

only" migrating write (i.e. rebuild policy) was no
longer optimal after the write had completed. The
write completed in degraded mode but the client
module requires an optimal completion as indicated
by the optimal only allocation hint.

Optimal Space Error In RAID 1 Y Ignore None N R1 detected that space allocated for an "optimal

only" migrating write (i.e. rebuild policy) was no
longer optimal after the write had completed. The
write completed in degraded mode but the client
module requires an optimal completion as indicated
by the optimal only allocation hint.

No Shutdown Image Posted N N.A. None Y CFM could not shutdown subsystem because no

volume set members was successfully posted with

the NVRAM image.
Bad Disk Drive State Du ring
Add Physical Drive

N N.A. None N A drive was in the initialization failed state after the

spin up attempt during an add physical drive

command. The drive is failing initialization, so

information on the nature of the failure should

appear in the log.
Disk Interface Data Underrun Y N.A. None N A backend device sent/received less data than

expected.
Disk Interface Data Overrun Y N.A. None N A backend device sent/received more data than

expected.

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con
Error! No text of specified style in document.

Event

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

70/0x46
71/0x47
72/0x48

73/0x49

74/0x4a

75/0x4b

76/0x4c

77/0x4d

78/0x4e

79/0x4f

80/0x50
81/0x51

82/0x52

83/0x53
84/0x54

85/0x55

86/0x56
87/0x57

88/0x58

Logged?

Disk Interface Command
Timeout
Disk Interface Hot Plug N N.A. None N A command was aborted by a disk hotplug or by

Host Write Collision With
Failed Cache Post

Disk Drive Defect List Error Y Single

Disk Drive Format Error Y Single

Invalid/unsupported hierarchic
LUN reference

Disk Interface State Error Y N.A. None N The backend disk interface hard ware or software

Write Sequence In Cache
Broken By Host Abort

Silent Disk Drive Error
Recovery

Check Condition From Disk
Drive With No Sense

Disk Drive Failed Start Unit
Command
Unexpected Disk Drive Status Y Single

Insufficient resources for LUN
operation.

Microcode C hanged Unit
Attention
Create LUN can’t get LUN
WWN seed

Recovered By Disk Drive On
Retry

Not ready, manual intervention
required
Data loss detected Y N.A. None Y An otherwise successful read op failed due to data

Insufficient memory resources N N.A. None N There is not enough memory installed in the

Y N.A. None Y A backend device did not complete a command

Y ignore - see

accompanying

errors

Occurrance

Occurrance

N Ignore - Host

LUN addressing

problem

N N.A. None N A part of a write cache stream was aborted by the

N N.A. None N On a previous attempt(s), the drive failed the I/O.

Y Single

Occurrence

Y Single

Occurrence

Occurrance,

possible

compatibility

problem

N N.A. None N There is insufficient physical disk storage capacity

N N.A. None N New controller microcode was just installed.

Y None allowed None Y The create LUN operation cannot be completed

Y See drive vendor

recommendation

N N.A. None Y The command is not possible in current subsystem

None N A write launched from cache but ended with a non-

Disk Driv e N The d isk driv e r eturned a status of

Disk Driv e N The d isk driv e r eturned a status of

None Y The host specified an 8-byte hierarchic LUN

Disk Drive N The disk drive returned a check condition with no

Disk Drive N The disk drive returned bad status for a start unit

Disk Drive,
Controller, Disk
Interface

Disk Drive N On a previous attempt(s), the drive failed the I/O.

Mfg Fail?

within the allotted time.

error error recovery for some other command.

SUCCESS status; this caused cache to mark the

write cache entry as RETRY which means it is stuck

in cache. A flush is required by a new FUA write.

One of the pages from the flush is stuck in cache

and the response is to fail the new write.

CHECK_CONDITION, HARDWARE_ERROR, .

The PDD’s retries are exhausted or the I/O is not

retryable. The drive may n eed to be form atted.

CHECK_CONDITION, MEDIA_ERROR,

FORMAT CORRUPTED/FAILED. May be cause

for immediate failure. The PDD did not attempt to

send a REASSIGN BLOCKS command. The drive

may need to be formatted.

reference that contained either an unsupported

address mode or made use of hierarchy levels that

the subsystem does not support.

state information was incorrect for observed

activity.

host. The failed write was forced because the

operation could not be completed. The host should

retry the operation.

(Usually due to hot plug.) The PDD retried the I/O

and the drive returned good status. We do not log a

recovered error because the original error was not

logged. We report GOOD statu s to the host.

sense data. The PDD’s retries are exhausted or the

I/O is not retryable.

command. The PDD’s retries are exhausted.

N The disk drive returned a status of SCSI_BUSY,

RESERVATION_CONFLICT, or some

undecodable status. The PDD’s retries are

exhausted or the I/O is not retryable.

present for the LUN operation that was requested.

More disks must be added to the subsystem before

the operation can be successful.

because the memory device that holds the seed for

the LUN WWN has either failed or cannot return the

requested data. LUN WWNs cannot be made

unique without this data.

The PDD retried the I/O and the disk drive returned

a status of CHECK_C ONDITION,

RECOVERED_ERROR

state.

loss recorded in at least 1 of the disk blks read This

is a rev2 error; the error is defined but not u s ed in

rev1 firmware.

Event

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

89/0x59
90/0x5a

91/0x5b

92/0x5c

93/0x5d

94/0x5e

95/0x5f

96/0x60

97/0x61

98/0x62

99/0x63

100/0x64

101/0x65

102/0x66

Logged?

Mfg Fail?

for LUN operation. controllers to complete the requested LUN

operation. More memory must be installed before

the requested operation can be completed

successfully.
Undefined N N.A. None N Undefined event code.
Host Read Collision With
Failed Cache Post

Y ignore - see

accompanying

errors

None N A host write was flushed from cache but ended with

a non-SUCCESS status; this caused cache to mark

the write cache entry as RETRY which means it is

stuck in cache. A new host read partially hits the

same address which normally causes the write to

flush but the write is stuck in cache. The r esponse is

to fail the read.
Ambiguous Volume Set
Reference

Y ignore - operator

error

None Y A volume set ID referenced in a recover command

was ambiguous. If a null (wild card) volume set

was used in a recover command t hen this error

means that the controller found drives from multiple

volume sets present. If a non-null volume set uas

used then this error means that the contoller is

already attached to a volume set other than the one

referenced in the recover command.
Recovery From RAM Loss
Failed

Y Single

Occurrance

Disk Drive,
Disk Interface,
Controller,
Operator

Y This error indicates that the controller was unable to

recover an NVRAM image from any disk in the

volume set. This could be because none of the disks

present have images, or the disks that did have

images were removed, or failed before the images

could be fully uploaded into the controller.
Multiple Failures Suspected
During Recovery

Y ignore - see

accompanying

errors

None Y Conditions detected during recovery indicate that at

least one failure or hot plug event occurred in

addition to the loss of NVRAM that prompted the

recovery. This implies that data integrity is likely to

have been compromised in ways that are not

detectable outside of the occurrance of this log entry

or sense data report. It is likely that the controller

does not have sufficient information to determine

the extent of the damage.
Volume Set Missing During
Recovery

Y ignore - operator

error

None Y The volume set referenced in a recover command is

not present in the subsystem. If a NULL volume set

was referenced then this error ind icates that no

members of any volume set were presen t. This error

can also result from imcompatible stamp versions
RAM Configuration Mismatch
During Recovery

Y Single

Occurrance

Controller
SIMM, operator
error

Y An attempt was made to recover an image after

RAM loss but the image would not fit in the non-

failing memory available on the controller. Either

the SIMM configuration has been modified, or one

or more SIMMs have failed. Recovery may be

possible using the another controller as the primary.
Read Recovered With RAID 5
Retries

Y Ignore - See

accompanying

None N Retries were used by the R5 module in the

successful completion of a read.

errors
Write Recovered With RAID 5
Retries

Y Ignore - See

accompanying

None N Retries were used by the R5 module in the

successful completion of a write.

errors
Read Recovered With RAID 5
Redundancy

Y Ignore - See

accompanying

None N Redundancy was used by the R5 module in the

successful completion of a read.

errors
Write Recovered With RAID 5
Redundancy

Y Ignore - See

accompanying

None N Redundancy was used by the R5 module in the

successful completion of a write.

errors
Read Recovered With RAID 1
Redundancy

Y Ignore - See

Accompanying

None N Redundancy was used by the R1 module in the

successful completion of a read.

Errors
Write Recovered With RAID 1
Redundancy

Y Ignore - See

Accompanying

None N Redundancy was used by the R1 module in the

successful completion of a write.

Errors
Disk drive reported a SMART
event

Y Signals internal

drive errors

threshold

exceeded,

Disk Dri v e Y The d isk dri v e reported a SMART event. The event

is logged and the common sense data is updated for
all regular read/write and passthru commands. The
precedence for SMART event data i n the comm o n
area is low, so that other errors that occur during the
same I/O are reported back to the host. A SMART
event does n ot affect t he I/O except that it do es

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con
Error! No text of specified style in document.

Event

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

103/0x67

104/0x68

105/0x69

106/0x6a

107/0x6b

108/0x6c

109/0x6d

110/0x6e

111/0x6f

112/0x70

113/0x71

114/0x72

115/0x73
116/0x74

117/0x75

118/0x76

119/0x77

120/0x78

121/0x79

Logged?

JM Write Recovered With
Retries

Force Unit Access Failed with
no Sense Data

Host DATA-OUT FCP-DL and
CDB transfer lengths not equal

Host Block command
attempted with FCP-DL NOT a
block size
LUN Security prevents the
requested operation

An unsupported operation was
attempted on a snapshot LUN

flush of storage ob ject failed Y disallow

Parameter Value Invalid N None N Parameter Value Invalid
Host is not authorized to read
from a LUN

Host can not be authenticated
to access LUN Security map

Limit to Maximum number of
Principals is reached

Host is not authorized to write
to a LUN

Feature is not licensed N Ignore - Host

Hot plug or LIP occured during
processing of passthrough

Unexpected JBOD Error Y Unknown JBOD ESD N The JBOD ESD returned CHECK CONDITION

Recovered By Enclos ure
Service Device (ESD)

PassThru request Failed Y Ignore - Should

JBOD ESD IO Failed Due To
ESD Removal

Mode Select command failed
due to NV memory write
failure

Y Ignore - See

Accompanying

Errors

Y Ignore - See

accompanying

errors

Y Ignore - Host

Protocol

Incompatibility

Y Ignore - Host

Protocol

Incompatibility

N Ignore - Host

LUN addressing

problem

Y Ignore - Incorrect

host behavior

snapshot

Y Ignore - Host

doesn’t have

permission to

access LUN

Y Ignore - Provide

correct password

Y Ignore - Remove

unwanted

associations from

Security map

Y Ignore - Host

doesn’t have

permission to

access LUN

Porblem

Y Ignore - should

be handled by

host

Y See information

provided by

JBOD vendor

be handled by

host

N N.A. None N Subsequent to a hot removal, the ESD’s (JEM/ JBOD

Y No ne of these are

allowed

None N Retries were used by the JM module in the

Cache N A forced unit access write command failed. The

None Y A Host DATA-OUT phase attempted to use an

None Y The Host attempted to perform a block oriented

None Y The Host attempted to perform an operation on a

None Y The Host attempted to perform a command, on a

None Y in preparation for a snapshot of a particular storage

None Y The Host attempted to perform an operation on

None N The Host failed the authentication for access to

None N The LUN Security Utility cannot be allowed to add

None Y The Host attempted to perform an operation on a

None Y A host request was found to use a feature without

None N The host Pass through request was not successfull.

JBOD ESD N The disk drive returned a status of

JBOD ESD N The requested comma nd (valid or NotValid) has

Midplane Y An attempt to write new mode parameter data to the

Mfg Fail?

count as one try of the I/O.

successful completion of a write.

component returning the bad return code may not
have provided val id se ns e data to notify the host that
an error has occurred. Cache will fill in va lid sense
data to alert the host to the write failure.

FCP-DL parameter that does NOT exactly match the
targets desired data transfer length.

command but the FCP-DL parameter was not a
multiple of a SCSI block size.

LUN that LUN security, in the current
configuration, prohibits.

snapshot LUN, that required an operation that is
unsupported for snapshots.

object, the system will attempt to flush all writes for
the storage object from the cache to the back-end
disks. If, for any reason the flush does not complete
successfully, the snap must not be allowed to
proceed.

LUN without having an appropriate access
permission.

LUN Security map because the password that it
presented is incorrect.

any more associations for new Principals since the
maximum limit for Principals set in the firmware is
reached.

LUN without having an appropriate access
permission.

having purchased its license.

This could be due to a LIP or Hot Reset of the
device.

status with sense information not handled by the
JBOD error recovery algorithms. The JBOD retries
are exhausted or the I/O is not retryable.

CHECK_CONDITION, RECOVERED_ERROR

Failed to be sent to the requested JBOD ESD due to
the fact that there is no valid Path for
communication to the desired device at the current
time.

Enclosure Ma nager) destroy method was invoked.
I/O’s in the JEM’s waiting queue are flushed with
this status.

chassis NV memory failed. As a result, none of the
mode parameter changes are being recorded. If the
chassis NV memory problems persist, the mode

Event

the volume set the NVRAM st amp were not p r esent.

Number

(dec/hex)

Event
Name

Predictive

Maintenance

Implication

Suspected
Components

Description

122/0x7a

123/0x7b

124/0x7c
125/0x7d
126/0x7e

127/0x7f

128/0x80

129/0x81
130/0x82
131/0x83

132/0x84

133/0x85

134/0x86

135/0x87

Event

Number

(dec/hex)

256/0x100

257/0x101

258/0x102

259/0x103

Logged?

Mfg Fail?

parameters stored there will prob ably revert to their

default values.
Hardware error prevents
successful command
completion
Host Port Behavior Table
overflow

Y No ne of these are

allowed

Y No ne of these are

allowed

Unknown Y The command failed because a required access to

hardware failed and was either not retried or was

retried unsuccessfully.

Unknown Y An attempt was made to add a new entry to the host

port behavior table but no unused entry was

available. An existing entry must be deleted to

make room for the new entry.
Sequencer error injection error N These only occur

in internal testing
Test mode is required for this
command
Subsystem LUN configuration

N Th ese only occur

in internal testing

N Ignore None N This error is used to report a Unit Attention for LUN
changed UA
Mode parameters were restored

N Ignore None N This error is used to report a Unit Attention for the
from defaults UA

Unknown Y This error is used for a variety of purposes when

injecting errors in sequencer module tests.

Unknown Y The command that was received is only allowed

when the test mode flag in the personality is true.

Inventory changed.

case where mode parameters were restored from

defaults.
Limit to supported number of
Principals has been reached

Y Ignore - Remove

unwanted

associations from

None Y The LUN Security Utility cannot add any more

associations for new Principals because the

supported limit for Principals has been reached.

Security map
Disk Interface Error - no
logging

N N.A. None N A command to a backend device failed in an

expected manner, so that logging is not required.

Disk Interface Error Y N.A. None N A command to a backend device failed with sense

data indicating an unexpected error.
Disk Interface Command
Failed

Y N.A. None N A command to a backend device failed due to an

error that does not include sense data from the

device.
Host is not authorized to access
LUN

Y Ignore - Host

doesn’t have

permission to

None Y LUN Security Authoriztion failed - Host attempted

to perform an operation on a LUN without having

an appropriate access permission.

access LUN
Cannot identify a FRU in
phatom enclosure with id 0xff

Y Ignore - Cannot

identify FRU in

phantom

None N Phantom enclosure is a collection of disks with no

physical slot mapping. Ideally there should not be
any disk in phatom enclosure

enclosure
Journal Manager B uffer Write
Failed

Y N.A. Journal

Manager

Y A Journal Manager Buffer Write has failed.

Resilient map updates have not been posted to disk.

FUA write failures may result from this condition
Journal Manager Stage Write
Failed

Y N.A. Journal

Manager

Y A Journal Manager Stage Write has failed. Resilient

map updates have not been posted to disk. FUA

write failures may result from this condition
Event E

v

Predictive Suspected M

Description

fg
e
nt

Name L

Maintenance Components F
o
g

ai

l?
g
e
d
?

Implication
Access Time Count Error Y Ignore. None N The frequency distribution table used to locate

recently modified blocks was found to be
inconsistent. This is indicative of a firmware

problem. This problem is self correcting.
Disk Drive Placed In Failed
State

Y Single

Occurrance

Disk Drive,
Controller,

N The firmware made a decision to automatically fail

a disk device due to its accumulated error history.

Back End FC
Link

NVRAM Image Out Of Date Y Ignore - Operator

activity

None N During startup a disk stamp newer than the

NVRAM committed stamp copy was found. This

indicates the volume set attached successfully to a

different controller and this VS related NVRAM is

not valid.
No Quorum For Disk Set
Access

Y Ignore - Operator

activity or

None N During startup a quorum of the drives belonging to