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

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

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

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

Predictive Suspected M

Description

fg e nt

Name L

Maintenance Components F o g

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

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

consisting of the controller serial number followed

Error! No text of specified style in document.

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

260/0x104

261/0x105

262/0x106

263/0x107 264/0x108

265/0x109

266/0x10a 267/0x10b

268/0x10c

269/0x10d 270/0x10e

271/0x10f

272/0x110

Logged?

accompanying

No Quorum For Disk Set Attachment

No Quorum Due To Broadcast Failure

No Address Table Y Ignore - Operator

No Disk Drives Found During Initialization Insufficient Space During Rebuild

Rebuild Started Y Ignore - See

Rebuild Complete Y Ignore None N ebuild has completed successfully. This message

Insufficient Space To Start Rebuild

Rebuild Failed Y Ignore - See

Cancel Rebuild Complete Y Ignore - Operator

Disk Drive Table Overflow Y Ignore - Operator

Duplicate Disk Drive Identifier Y Single

Disk Drive Installed Y Ignore - Operator

Y Ignore - Operator

Y Ignore - See

Y Ignore - Operator

Y Ignore - See

errors

activity or

accompanying

errors

accompanying

errors

activity or

accompanying

errors

activity

accompanying

errors.

accompanying

errors.

accompanying

errors

accompanying

errors

or Host Activity

activity

Occurrance

Activity

None N During startup (with VS relat ed NVRAM invalid)

None N During startup no disks were present so a new

None N here is insufficient disk space for migrating data.

None N ebuild has been started either automatically or by

None N here is insu fficient disk space for rebuild to execute.

None N ebuild has failed to complete due to multiple disk

None N ebuild cancellation has completed. This message

None N The controller is capable of retaining information

Controller or Erroneous Operator Activity

None N This error code indicates the system state change

Mfg Fail?

Since volume set partitioning is not allowed the

system cannot attach to this VS.

we were unable to find a VS with a quorum of its

members present.

we were unable to invalidate the NVRAM image on

a quorum of the members of the VS we tried to

attach to.

we were unable to to find a VS present that had a

valid shutdown image on any of the members

present.

volume set with no members was created.

This is a controllererror, although the subsystem

may still support some I/Os without adding disks.his

message follows the message, if the error

isdiscovered during rebuild.

command. Unless there wasa reset during rebuild, at

least two more messages follow this , ,, ,, or . The

messageindicates that a format subsystem was

issued through the front panel or byhost command,

eliminating the need for a rebuild. If there was a

resetduring rebuild, you will see the message

repeated.

follows the message.

This message followsthe message and may follow

the REBUILD message.

failures or a controllerfailure. Previous messages in

the log should indic ate whether or not thereha v e

been multiple disk failures. This message follows

the message.

always follows the message.

about 16 drives. Since only 12 can be inserted at a

time the remaining 4 would have to be missing

drives on which the controller still depends. If the

total number of missing drives and present drives

ever exceeds this limit, the TOO_M ANY_DRIVES

condition is logged. At this point the controller

cannot recognise any additio nal ins erted drives. The

system always reports data unavailable before this

condition is reached.

N As part of its stamp, each drive indicates its logical

position in the volume set to which it is attached.

This error is logged when ever the controller

encounters two drives which claim to be in the same

position of the same volume set. The most likely

source of this error is the erroneous assignment of

duplicate volume set ID’s. This would generally

originate with incorrect controller serial nu mber

assignment, and/or loss of NVRAM. This error

would also occur if a user made an image copy of a

drive.

consisting of a hot plug insertion. This event occurs

regardless of the disposition of the drive toward the

volume set. The device number of the drive added

appears in this change record. A device number

Event

event extended info area. After all entries currently

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

273/0x111

274/0x112

275/0x113

276/0x114

277/0x115

278/0x116

279/0x117

280/0x118

281/0x119

282/0x11a

283/0x11b

284/0x11c

285/0x11d

Logged?

Disk Drive Added To Disk Set Y Ingore - Operator

activity

Disk Drive Removed Y Ignore unless no

Operator activity

Disk Drive Deleted From Disk Set

Y Ignore - Operator

activity or

assocaited errors

Logical Unit Created Y Ignore - Operator

or host activity

Logical Unit Deleted Y Ignore - Operator

or Host activity

Logical Unit Modified Y Ignore - Host

Activity

Disk Set Attached Y Ignore - Operator

activity

Reset To Clear VSC7130 interrupt

Unable To Recreate Memory

Y Ignore - unless

repeated

Y Ignore None N This error code indicates that the system

Error

Memory Error Not Recovered

Y > 1 in 6 mo. SIMM,

With Redundancy

Memory Error Recovered With Redundancy

Y Ignore - See

accompanying

errors

Uncorrectable Memory Error Y > 1 in 6 months

per controller

Correctable Memory Error Y See correctable

rate assocaited

with usage page

Mfg Fail?

by a 0 indicates that the device number has not yet

been assi gned.

None N This error code indicates the system state change

consisting of the addition of a new volume set

member. This occurs only when a drive that was

not previously a member becomes a member. It

does NOT occur then down, failed, or missing

drives are returned to good standing. The device

number of the drive added appears in this change

record.

Disk Drive, Back End SCIS Bus, Controller

N This error code indicates the system state change

consisting of a hot plug removal. This event occurs

for volume set members only. The device number

of the drive removed appears in this change record.

A device number consisting of the controller serial

number followed by a 0 indicates that the device

number has not yet been assigned.

None N This error code indicates the system state change

consisting of the deletion of a new volume set

member. This occurs only when a drive that was

previously a member becomes a non-member. The

drive may or may not be present in the subsystem at

the time. The device number of the drive added

appears in this change record.

None N This error code indicates the system state change

consisting of the creation of a new SCSI LUN. This

change occurs only if LUN creation succeeds.

None N This error code indicates the system state change

consisting of the deletion of an existing SCSI LUN.

This change occurs only if LUN deletion succeeds.

None N This error code indicates the system state change

that occurs when an existing LUN is modified. This

change occurs only if LUN modification succeeds.

None N This error code indicates the system state change

consisting of attachment to a new volume set has

occurred. This occurs after every format subsystem

and whenever a power on or reset occurs while the

controller is not attached to a volume set. In some

cases the currently attached volume set may be

empty.

VSC7130 - on controller

Y This error code indicates that VSC7130 interrupt

could not be cleared. The controller was reset in an

effort to clear the interrupt.

experienced a memory error and was unable to

recreate the failed memory accesses. An excessive

number of un-reproducible memory errors will

result in a controller failure.

Y This error code indicates that the system Controller, Backplane

experienced a unrecoverable error that could not be recovered via redundant memory. This will cause information loss if the error occurs in non-redundant NVRAM memory.

None N This error code indicates that the system

experienced a unrecoverable error that could be recovered via redundant memory or a controller

reset Controller, SDRAM, midplane

Y This error code indicates that the system

experienced a uncorrect able shared-memory error.

The two word queue entry found in the shared-

memory controller error queue will be placed in the

event extended info area. After all entries currently

in the queue have been processed, the subsystem

will undergo a short reset at which time an attempt

will be made to correct the error using the mirrored

copy of memory (if available). SDRAM, controller, midplane

Y This error code indicates that the system

experienced a correctable shared-memory error.

The two word queue entry found in the shared-

memory controller error queue will be placed in the

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

286/0x11e

287/0x11f

288/0x120 289/0x121

290/0x122

291/0x123

292/0x124

293/0x125

294/0x126

295/0x127

296/0x128

297/0x129

Logged?

Memory Compare Error Y Ingore - See

Controller Data Bus Microprocessor Access Parity Error Internal Data Bus Error Y > 1 in 6 months Controller,

Volume Set Full Reset Y Ignore - see

Warm Boot IO Expander Fault Y Ignore if

Disk Set Detached Y Ignore -

Microprocessor Software Fault Y > 1 in 1 month Controller N This is an error detected by the processor which

Microprocessor Hardware Fault

Disk Interface Event Y Ignore, unless

Insufficient RAM For Image Upload

Disk Interface Queueing Disabled

Disk Disconnects Disabled Y Immediate

accompanying

errors

Y > 1 in 6 months Controller N This event code indicates that the a reset was

accompanying

errors

recovered by

power cycle

Operator/Host

activity

Y > 1 in 1 month Controller N This is an error detected by the processor which

occurring frequently

Y Ignore - Operator

error or

accompanying

errors

Y Immediate

Performance

Problem -

Unsupported

Disk

Performance

SDRAM, controller, midplane

SIMM None N This error code indicates that an inconsistancy was

Controller Y This error code indicates that the IO Expander

None N This is a system change event posted to the log

Disk, controller, disk interface None N This is an error detected by the startupSystem when

Disk N An attached disk could not be configured for

Disk N This event indicates that the firmware could not

Mfg Fail?

in the queue have been processed, the subsystem

will undergo a short reset at which time the

correctable error will be permanently corrected.

Y This error code indicates that the system

experienced a compare error between the redundant

shared memory copies. The two word queue entry

found in the shared-memory controller error queue

will be placed in the event extended info area. After

all entries currently in the queue have been

processed, the subsystem will undergo a short reset,

at which time an attempt will be made to sync the

two copies of mem ory (if available) to see if the

error was transient. If the error is permanent, n on-

volatile memory must be invalidated. Single

miscompare c an be recovered by selecting one of

the two versions of the data and syncing both sides

to that version.

initiated due to excessive errors on the

microprocessor local bus.

N This error code indicates that the system

experienced a parity error during a DMA Operation.

detected in one of the volume set clusters seed

values, fsb or rbtables. The migration bypassed this

cluster. This could be the result of a r6 restore

consistency posting temporary data to the cluster,

the data in the cluster will remain bad until the data

is reposted by the cache. In the mean time all reads

for data will be satisfied by the cache. After the

cache repost the data may then be successfully

migrated.

containing the warm boot bit did not power-on in

the correct default condition or that attempts to set

the warm boot bit in the IO Expander failed.

when shutdown has completed sucessfully; i.e., the

volume set is no longer attacheddevice number field

in log record is volume set number (system change

event)

caused the processor to vector to the software fault

isr. The controller always resets following this log

entry. This error is caused by illegal instruction

fetches, divide by zero, or other illegal processor

activity.

caused the processor to vector to the hardware fault

isr. The controller always resets following this log

entry. This error occurs when the microprocessor

attempts an illegal interrupt vector.

N An error occurred on the disk interface. These may

occur during disk hotplug. More detailed status is

available in the event expanded information.

the current RAM config is not large enough to hold

the NV image stored on disk. Sin ce we do not

support shrinking RAM, this fails the upload

process and causes a new VS to be created. System

state is NO_MAPS.

command queueing. Command queueing and

disconnects are disabled for this interface.

configure the drive to disable disconnects during

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

298/0x12a

299/0x12b

300/0x12c

301/0x12d

302/0x12e

303/0x12f

304/0x130

305/0x131 306/0x132

307/0x133

308/0x134

309/0x135 310/0x136 311/0x137

312/0x138

313/0x139

Logged?

Problem -

Unsupported

Disk

Mfg Fail?

data transfer phase. This will cause disconnects to

be disabled for the entire on the interface, thus

causing degraded drive performance. This event

may also indicate that the firmware could not enable

queueing on this drive, which also causes

disconnects to be disabled on the interface. The

reported FRU is the slot number. (S ee the "Disk

Interface Queu ing Disabled" event.)

Disk Reassign Completed Y See disk drive

vendor’s reassign

rate spec.

Disk N This event indicates that the array firmware

successfully completed a data reassignment

(sparing) operation. The reported FRU is the slot

number. This is informational only, not an error

condition.

Disk Reassign Cancelled Y Ignore None N This event indicates that a data-reassign (sparing)

operation was cancelled by the array firmware. The

most likely reason is that the firmware detected that

the disk was reset and in need of reconfiguration.

The reported FRU is the slot number. This is

informationa l only, not an error.

No Error On Disk Media After Medium Error

Y Ingore unless

medium error

recurs

Disk Drive N This event indicates that the PDD’s media test has

determined that media for which a drive had

reported a MEDIUM ERROR is actually OK. The

data st or ed at the a ffected LBA may or may not

have been recovered. The reported FRU is the slot

number.

Incompatible RAM Image Revision

Y Ignore - Operator

Error

None N Th is event indicates that t he NVRAM image stored

on the volume set when it was shutdown is not

compatible with the current version of firmware.

The image cannot be uploaded and the resulting

system state is NO_MAPS for this volume set.

Controller Presence Detect Faulted Off

Y Single

Occurrance

Controller, Midplane

Y he presence detect bit for the other controller is not

working. This controller does not "see" another

controller in the enclosure, yet it can communicate

successfully with the Trifid on the other controller.

This error is logged only onc e per power on.

No Interrupts From Other Controller

Y Single

Occurrance

Controller, Backplane

N he "other controller" interrupt seems to be broken.

The timer interrupt fired multiple times with new

communication messages but no "other controller"

interrupt s were present. This error is logged only

once per power on.

Disk Interface Disconnect Y Ignore - Disk

compatibility

problem

Disk Downed Y Ignore - Operator

or Host activity

Data Unavailable Y Ignore - See

accompanying

errors

Disk Drive N An attached disk unexpectedly disconnected during

a disk data transfer. This is informational, not an

error. None N A device was successfully transitioned to the down

state in response to user request. None N The data unavailable condition was triggered. This

is due to multiple failed, down, or missing drive(s).

The condition persists as a warning until less than 2

drives and down, failed, or missing.

Insufficient Optimal Space For Rebuild

Y Ingore - See

accompanying

errors

None N here is insu fficient disk space for rebuild to execute.

This may be due tothe mix of disk sizes on the

subsystem. This message follows the message and

may follow the REBUILD message.

Rebuild Restarted Y Ignore None N ebuild has been automatically restarted due to disk

failure or removal. Th ismessage follows the

message.

Rebuild Executing Y N.A. None N ab Instrumentation Only. Rebuild Preempted Y N.A. None N ab Instrumentation Only. Cancel Rebuild Started Y Ingore - Operator

or Host activity

None N ebuild has been cancelled either automatically or by

command. The subsystemautomatically cancels

rebuild if it needs to restart rebuild due to a

diskaddition, a LUN deletion, or a LUN format.

This message follows the message and may be

followed by another message.

Rebuild IO Priority Changed Y Ignore - Host

activity

None N host command has changed rebuild I/O priority

relative to host I/Os. Thismessage follows the

message.

Non-Member Drive Removed Y Ignore - Operator

activity

None N This error code indicates the system state change

consisting of a hot plug removal. This event occurs

for drives t hat are not volume set members when

they are removed. The device number field is not

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

314/0x13a

315/0x13b

316/0x13c

317/0x13d

318/0x13e

319/0x13f

320/0x140

321/0x141

322/0x142

323/0x143

324/0x144

325/0x145

326/0x146 327/0x147

328/0x148

Logged?

Drive Missing At Power On Y Ignore unless no

RAM Image Upload Failed Y Single

Old Cache Configuration Used Y Ignore - See

Incompatible RAM Image Content

Disk Interface Underrun Event Y Single

Disk Interface Overrun Event Y Si ngle

Disk Interface Timeout Event Y > 2 occurrances

Controller ECC Miscorrection Y Single

Controller Data Bus Microprocessor Access Error

Incompatible Address Table In RAM Image

Non-Volatile Memory Initialized

Battery Failed Discharge Test Y Single

Fan Failed Y Single

Power Supply Failed Y Single

Power Down Due To Fan Y Single Fans, N This error code indicates that the Background

Operator activity

Occurrance

errors associated

with shut down

Y Ignore - Operator

error

Occurrance not

with other entries

Occurrance not

with other entries

per hot plug

insert or removal

Occurrance

Y Single

Occurrance

Y Ignore - Operator

error

Y Ignore unless no

operator activity

Occurrance

Disk Drive, Controller, Back End FC Link

Disk Drives, Controller, Back End FC Link None N Write data found in the uploaded NVRAM image

None N This is an error detected by the startupSystem when

Disk, controller, disk interface Disk, controller, disk interface Disk, controller, disk interface SIMM, Controller

Controller N This error code indic ates that the system

None N This error occurs when NVRAM (SIMM(S)) is

SDRAM DIMM, Controller

Battery N This error code indicates that a battery has failed the

Fan, Controller, Backplane Power Supply, Controller, Backplane

Mfg Fail?

used.

N This error code indicates that a drive was discovered

to be missing during a power on or reset. This event

occurs for volume set m em bers only. The device

number of the drive removed appears in this change

record. A device number consisting of the

controller serial number followed by a 0 indicates

that the device number has not yet been assigned.

N The subsystem was unable to upload a usable disk

copy of NVRAM during startup. System state is

NO_MAPS.

blocked a requested transition to a new cache

configuration; the previous configuration is being

used. To get to the new configuration, get cache

flushed and do another upload.

the current RAM config is not compatible with the

RAM config of the NVRAM disk image. This is

similar to except that not enough physical RAM

space is not the problem but rather a different

mapping of NVRAM in the disk image that cannot

be supported by the current config (i.e., the image

supports 8G drives but the current config does not).

A new VS is created. System state is NO_MAPS.

To use the disk image the current config must be

updated to the disk config.

N An attached device sent/received less data than

expected.

N An attached disk sent/received more data than

expected.

N A command to an attached disk did not complete

within the allotted time.

N This error code indicates that the system

experienced a correctable error which was mostlikly

misscorrected.

experienced a uP access error without the needed

other qualifiers. Microprocessor access errors

should only occur in conjunction with correctable or

uncorrectable memory errors, or with parity errors.

If no other condition is present this event is reported

to indicate the malfunction.

removed, forcing the Time Stamp Table to shrink,

or the image to be reloaded has an invalid size.

Once NVRAM is added and the Table is expanded,

it cannot shrink.

N This message is logged when NV-SDRAM is found

to be invalid at boot and must be initialized. This

should not cause concern if memory was purposely

invalidated or a new board or new memory has just

been installed.

long discharge test. This test occurs following

power on and every 30 days thereafter. The test

takes about 36 hours to complete. Replace

Batteries.

N This error code indicates that a fan has failed.

N This error code indicates that a power supply has

failed.

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

329/0x149

330/0x14a

331/0x14b

332/0x14c

333/0x14d

334/0x14e

335/0x14f

336/0x150

337/0x151

338/0x152

339/0x153

340/0x154

341/0x155

342/0x156

343/0x157 344/0x158

Logged?

Failure Occurrance Controller,

Backplane

Mfg Fail?

Manager (BGM) has discovered that there are not

enough good fans to cool the system. The BGM is

shuttingThe NVRAM is not posted to disk, so it is

critical to repair the system quickly.

Fan Missing At Initialization Y Ignore - See

accompanying

errors.

None N This error code indicates that the BGM has started

timing that a fan is missing from the enclosure. The

total length of time a fan has been missing will be

checked periodically and if it exceeds

TIME_FAN_MISSING_ALLOWED_BGM

(approx. 10 minutes) the BGM will shut off the

power supply.

Power Down Due To Missing Fan

Y Single

Occurrance

Fan, Controller, Backplane

N This error code indicates that the BGM is shutting

off the power supply because a fan has been missing

from the enclosure for too long (approx. 10

minutes).

Replace Battery Y Single

Occurrance

Battery, Controller

N This error code indicates that the batteries have

failed a discharge test or have dropped below an

acceptable voltage level. Both batteries should be

replaced.

Cache Shrink Attempted After Shutdown Warning

Y Ignore - see

errors during

None N Attempting to shrink write cache with valid writes

still in cache.

shutdown

Controller Failed Y Ignore if

recovered with

reset

Controller N This error code indicates that a controller was

discovered to be bad during the poweron process

This can be caused by the controller having

difficulty in establishing communication. Ignore if

recovered by power cycle or reset.

SIMM Failed Y Single

Occurrance

Extended Drive Insertion Event Y Ignore unless no

operator activity

SIMM, Controller Disk Drive, Controller, Back End FC Link

N This error code indicates that a SIMM was

discovered to be bad during the poweron process.

N A backend SCSI channel was held reset longer than

the time allowed for a drive hotplug. Probably

caused by a partially inserted drive module, a failing

drive, a failing controller, or a bent pin on a

connector.

Disk Interface State Event Y Single

Occurrance not

with other entries Uncorrectable ECC Error During Initialization

Y > 1 in 6 months

if no operator

activity

Controller, disk, disk interface SIMM, Controller

N The disk i nterface controller and/or software state

information was incorrect for observed interface activity.

N This error code indicates that the system

experienced a unrecoverable error - The batteries have been fully discha rged . - The batteries were disconnected from the memory - New SDRAM memory was added All other occurance is a true

memory error Correctable ECC Error During Initialization

Y > 1 in 6 months

if no operator

activity

SIMM, Controller

N This error code indicates that the system

experienced a correctable memory - The batt eri es

have been fully discha rged . - The batteries were

disconnected from the memory - New SDRAM

memory was added All other occurance is a true

memory error Inter-controller data p ath error Y > 1 in 6 mo. Controller,

midplane

Y Failure in the test of data movement between

controllers over the high -speed bus. This controller

has been placed in isolation mode. Inter-controller address decode error

Y > 1 in 6 mo. Controller,

midplane

Y Failure in the test which exercises all address bits

while moving data between controllers over the

high-speed bus. This controller has been placed in

isolation mode. Inter-controller mirror error Y > 1 in 6 mo. Controller,

midplane

Y Failure in the test which performs mirrored writes

and reads of data between controllers over the high-

speed bus. This controller has been placed in

isolation mode. If this is a transient error, reset or

power cycle will recover, otherwise hardware has

failed. controller signature mismatch Y probably caused

by user action

Controller, Backplane

N Controller doesn’t match signature in midplane

EEPROM. The user has probably inserted a

controller with a vali d image from another

enclosure. This controller is in isolation mode. controller firmware mismatch Y probably caused

by user action

Controller N Firmware on controllers is not identical. Th is

controller is in isolation mode. remote memory config error Y Controller N The remote con troller reports that it was u nable to

configure its memory. The local controller is in

isolation mode.

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

345/0x159

346/0x15a

347/0x15b

348/0x15c

349/0x15d

350/0x15e

351/0x15f

352/0x160

353/0x161 354/0x162

355/0x163

Logged?

Bus A TWSI communication failure

Data Loss Detector entry Y Indicates

Member Disk Drive Added Back Into Disk Set

Frontend Fibre Channel ABTS Event

Cache Version Mismatch In RAM Image

RAM Version Mismatch Y N.A. None N The upload routine was unable to upload part of the

Disk Format Version Mismatch Y N.A. None N The NVRAM format of the disks does not match the

ShutDown Due To Power Supply Failure

Recovery from battery backed RAM Loss Started Recovery from Battery Backed RAM Loss complete

Redundancy corrected Y Suspect data if

Y Controller,

multiple failure

causing data loss

Y Ignore - Operator

or host activity

Y Ignore None N This error code indicates that the Host sent a Fibre

Y See errors

associated with

shut down

Y Single

Occurrance

Y Single

Occurrance

Y Ignore None N This error code i ndicates that recovery from a

followed by error

code 93 (0x5d)

battery, power supply, midplane

Disk drive(s) N This error code indicates that the data loss detector

None N This error code is a system change event indicating

None N A firmware download has a new version of the

Power Supplies, Controller, Backplane

Controller N This error code indicates that recovery from a

Disk Drive, Back End FC Link, Controller

Mfg Fail?

Y Eith er local controller or remote controller SRAM

on two-wire serial bus A could not be accessed for

controller sync. Bus B SRAM will be used instead

(if Bus B SRAMs are also inaccessible, both

controllers will reset and and try again; finally one

controller will be disabled and the system will

continue in single controller mode)

module was called because of multiple failures. A

data loss has occurred.

that a member of a volume set that was either down,

failed, or m issing has been returned to t he

unrestricted use (aka ready) state. This can occur

via the add physical drive command, or via hot plug

insertion of the drive.

Channel ABTS (Abort Sequence) BLS frame to the

abort an IO. The array will log this event for

informational and debug purposes only. It does not

necessarily indicate a problem with the array.

cacheVersionNumber. This is OK if there are no

writes stuck in cache but it causes upload to fail

with this error code if there are writes stuck in

cache. To fix this it is necessary to revert to the old

version of firmware and solve whatever problem

was causing writes to be stuck in cache (probably

one or more disks have failed).

disk NVRAM image because the current firmware

does not support that use of RAM. (Most likely an

older version of firmware is trying to upload a disk

image posted by some other firmware version.)

format used by the controller. This event is logged

when an icicle controller attempts to use disks

previously shutdown by an Ice controller or visa-

versa. The controller cannot use an NVRAM image

in the incorrect forma t.

N This error code indicates that the Background

Manager (BGM) has discovered that there are not

enough good power supplies to run the system. The

BGM is shutting down the subsystem to minimize

system operation with inadequate power.The

NVRAM is posted to disk.

battery backed RAM loss has been initiated.

battery backed RAM loss completed with at least

partial succ ess. Maps were recovered. Multiple

failures may or may not have occurred. Occurrance

of multiple failures are reported in the log between

the RECOV_STARTED and R ECOV_DONE

events.

N This error code indicates that the parity scan which

executes during recovery from RAM loss found an

instance of incorrect redundant data. Data which

was being updated when RAM was lost may

produce this error in single failure scenarios. This

error can also result from multiple failure

conditions. Firmware differentiates the two

scenarios by placing a limit on the number of these

conditions which can occur before recovery is

terminated due to multiple component failures. If

this error is followed by error 93 (0x5d) then the

contents of data blocks reported in this error should

be considered suspect. The block address of the

Event

In a dual controller envi

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

356/0x164

357/0x165

358/0x166

359/0x167

360/0x168 361/0x169

362/0x16a

363/0x16b

364/0x16c

365/0x16d

366/0x16e

367/0x16f

368/0x170

369/0x171

370/0x172

371/0x173

Logged?

Mfg Fail?

error appears in the first 4 bytes of the controller

serial number field of this log record. The LUN

appears in the fi fth byte of the controller serial

number, and the length of the affected area in 512

byte blocks appears in the last 3 bytes. The FRU

field reports the FRU of the drive corrected. Local Controller Failed DRAM Address Decode Test

Y Ignore if

recovered by

reset or power on

DRAM SIMM, Controller

N This error code indicates that the DRAM SIMM on

the local controller failed the DRAM address decode

test during the poweron process. Specifically, the

DRAM SIMM on the primary controller failed the

decode test. Remote Controller Failed DRAM Address Decode Test

Y Ignore if

recovered by

reset or power on

DRAM SIMM, Controller

N This error code indicates that the DRAM SIMM on

the remote controller failed th e DR AM a ddress

decode test during the poweron process.

Specifically, the DRAM SIMM on the secondary

controller failed the dec ode test. Controller Failed Background ROM checksum test

Y Ignore if

recovered by

reset or power on

ROM, Controller

N This error code indicates that the ROM on the local

controller failed the ROM checksum test done in the

background during idle time. The firmware stored

in the ROM is corrupted. Scrub policy detected error Y Ignore - should

be preceded by

Drive errors

Disk drive N This error code indicates th at an error was returned

to the Scrub policy by a device read. It is logged to

provide information about the cause of the error.

Additional information about the error from the

device should precede t his entry. New controller firmware was downloaded Mode Parameters changed Y Ignore - Operator

Y Ignore - Operator

activity

None N New controller firmware was successfully installed

in all controllers present in the subsystem.

None N A mode select command was processed and it

changed one or more changeable mode parameters

in the subsystem. Shared memory recovered error

Y Ignore; other

errors will follow

if significant

Controller N This error code indi cates that some non -fatal error

appeared in the s hared-memor y erro r queue. The

two words of this queue entry will be placed in the

log entry extended info area. Shared-memory controller error

Y Ignore if

recovered by

reset or power

cycle

Controller N This error code indi cates that some fatal error

appeared in the shared-memory controller error

queue. The two words of this error entry will be

placed in the event extended info area. After all

entries in the queue have been processed, the

subsystem will undergo a short reset. Shared-mem or y c hecksum error

Y > 1 in 6 mo. Controller,

SDRAM, midplane, disks

N This error code indicates that a fatal checksum error

appeared in the shared-memory controller error

queue. The two words of this queue entry will be

placed in the event extended info area. After all

entries currently in the queue have been processed,

the subsystem will undergo a reset. Flash failure resulting from command sent to flash

Y N.A. Y This error code results i f we get an error during the

programming, erasing or reading flash. So if we get

any error when commanding flash to perform a task

that we interpret as Flash not responding correctly,

we will log this error. DRAM Checksum failure during download

Y N.A. N If during the download sequence of events we fail

the checksum performed in DRAM this error will

result. This event occurs before we try to copy to

FLASH. Flash Checksum failure during download

Y N.A. Y If after copying the download image into the flash

part(s) the checksum of the image fails this error

will result. Download Semaphore request failed

Y N.A. N Only one download command from the host can be

executed at a time. If a host request for download

occurrs while one is already active the redunant

requests will get this error. Download image failed validation

Y N.A. N The download image sent from the host is validated

by the Download Sequncer as to it validity. If the

data received does not appear to be firmware image

then this error will result. Family Image compar e failed Y N.A. N If the firmwar e image to be downloaded has a

different family image value then the current l y

running image and this is a online download, then

this error will result. Download failed on slave Y N.A. Y

ronment the command to

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

ErrEnR1. The sixth byte is ErrDR1. The ninth byte

Error! No text of specified style in document.

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

372/0x174

373/0x175 374/0x176

375/0x177

376/0x178

377/0x179

378/0x17a

379/0x17b

380/0x17c

Logged?

controller download is sent to one of the controllers. This

Download failed on the master controller

Unused error code N N.A. N This error code value is unused. TWSI Event Y ignore, unless

TWSI Bus Failure Y Y This error code indicates that one of the two-wire

Frontend Fibre Channel Event Y Ignore None N This error code indicates that the Front End Fibre

Frontend Services Event Y Ignore None N This error code indicates that a Front End Services

Recovered Dual Comm Failure Y N This error code indicates that a controller was reset

Reflection ECC single-bit error overflow

processor MCP or TEA machine check error

Y N.A. Y In a dual controller environment the command to

occurring

frequently

Y Processor

Y Processor, proc

Controller, power-supply, battery, midplane

DRAM

memory bus component

Mfg Fail?

controller becomes the mas ter of the download

process. The other controller becomes the

secondary controller (or the controler that just

executes the download and reports back to the

master.) This error will result if an error oc curs on

the secondary controller.

download is sent to one of the controllers. This

controller becomes the mas ter of the download

process. The other controller becomes the

secondary controller. If it is a single controller

environmen t then the download p r ocess see the

single controller as the ma ster controller for the

download regardless of the slot it exists in. If the

download fails on this controller this error will

result.

N This error code indicates that a transaction on one of

the two-wire serial buses did not complete

successfully. The bus, target device, and fail code

will be placed in the extended info area. The bus,

controller slot, device address, and fail code will

also be placed in the enclosureID, slot, component,

and subcomponent fields of the CompID structure

respectively.

serial buses has failed. This log entry should always

be preceded by several entries. The bus that failed

will be identified in the extended info of the log

entry.

Channel port had an event that it has logged.

Specific information about the event is placed in the

extended info area of the log.

(FES) event has occurred and has been logged.

Specific information about the event is placed in the

extended info area of the log.

due to a dual-controller communication failure (one

in which the two controllers failed to sync) and that

the controllers successfully synced after the reset.

The comm failure would result from either a

transient hardware failure in the shared-memory

controller, TWSI, or TSWI SRAM or from a

situation where the controllers were not resetting

within two seconds of each other.

Y This error code indicates that the number of single-

bit ecc errors found in processor memory has

exceeded the threshold. This threshold is half the

number set up in the ECC Single-Bit Trigger

reset and reload processor memory in hopes of

correcting any soft memory errors. If errors are

occurring so fast that the count in ECC Single-Bit

Trigger reg is exceeded before a periodic scan can

discover and log this overflow, a Machine Check

will result. The first byte of extended info is the

ECC Single-Bit Counter register and the second

byte is the ECC Single-Bit Trigger register.

Y This error code indicates that a processor MCP or

TEA fault resulted in a machine check. Information

was dumped into nvsram when the error occured

and this log entry was generated during the next

successful reset. The first four bytes of extended

info is the 60x PC I Error Addr. The fi fth byte is

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

381/0x17d

382/0x17e

383/0x17f

384/0x180

385/0x181

386/0x182

387/0x183

388/0x184

389/0x185

390/0x186

391/0x187

392/0x188

393/0x189 394/0x18a

395/0x18b 396/0x18c

397/0x18d 398/0x18e

399/0x18f

400/0x190

401/0x191

402/0x192 403/0x193

404/0x194

Logged?

Mfg Fail?

is ErrEnR2. The tenth byte is ErrDR2. LCC Instal led Y Ignore - Operato r

Activity

LCC, Back End FC Port, Controller

N This error code indicates the system state change

consisting of an LCC hot plug insertion. The device

number of the drive added appears in this change

record. A device number consisting of the

controller serial number followed by a 0 indicates

that the device number has not yet been assigned. LCC Removed Y Ignore unless no

Operator activity

LCC, Back End FC Port, Controller

N This error code indicates the system state change

consisting of an LCC hot plug removal. The device

number of the lcc removed appears in this change

record. A device number consisting of the

controller serial number followed by a 0 indicates

that the device number has not yet been assigned. DDM failed image disks Y Ignore unless no

Operator activity

disk drives N This error code indicates the system could find a

usable image disk to reload NVRAM from at system

start up. Battery charger firmware downloader status

Y battery charger N This event is used to report status related to the

battery charger firmware download proc ess. See the

extended event info field for the actual status. Failure in TWSI Driver module Y Controller,

battery, power supply,

Y 2C_DRIVER_FAILURE This error indicates that an

attempt to communicate with a two-wire serial

device has failed, possibly after multiple retries.

midplane

VSC7130 chip failed Y VSC7130

Signal Detect / Port Bypass Control chip

Y The VSC7130 chip used for FC signal detect and

port-bypass control has suffered a hardware failure.

There is a VSC7130 for the host port and one for the

JBOD port. This will result in the controller being

failed. See extended information for which 7130

failed. Internal drive inserted Y Disk internal to

the controller

N An internal disk has been inserted into the

enclosure.

enclosure

Internal drive removed Y Disk internal to

the controller

N An internal disk has been removed from the

enclosure.

enclosure Internal drive requesting port bypass

Y Disk internal to

the controller

N An internal disk is requested that its FC port be

bypassed.

enclosure Internal drive has stopped requesting port bypass

Y Disk internal to

the controller

N An internal disk has stopped requesting that its FC

port be bypassed.

enclosure Internal drive is indicating a fault

Y Disk internal to

the controller

N An internal disk is indicating that it is faulted.

enclosure Internal drive is no longer indicating a fault

Y Disk internal to

the controller

N An internal disk is no longer indicating that it is

faulted.

enclosure No GBIC Installed Y GBIC port N No GBIC is installed on this controller GBIC of type MOD DEF 4

Y GBIC port N A GBIC has been inserted on thi s controller Installed GBIC of type Mod Def 4

Y GBIC port N A GBIC has been removed from this controller Removed GBIC Transmit Fault Y GBIC port N The GBIC is indicating a transmit fault GBIC no longer indicating

Y GBIC port N The GBIC is no longer indicating a transmit fault Transmit Fault GBIC Receive Signal Lost Y GBIC port N The GBIC is indicating that the no receive signal is

present GBIC no longer indicating Receive Signal Lost Non-Mod Def 4 GBIC Installed

Y GBIC port N The GBIC is no longer indicating that the no receive

signal is present

Y GBIC port Y A non-Module Definition 4 type GBIC has been

installed. This GBIC type is not supported and will

be disabled. This GBIC will also be marked as

failed. Non-Mod Def 4 GBIC Removed

Y GBIC port N A non-Module Definition 4 type GBIC has been

installed. This GBIC type is not supported but will

be used anyway. GBIC EEPROM has failed Y GBIC Y Unable to communicate with the EEPROM on the

GBIC. The EEPROM must be failed. JBOD FC Signal Detected Y JBOD Port N An FC signal is now detected on the JBOD port. JBOD FC Signal Lost Y JBOD Port N An FC signal i s no longer detected on the JBOD

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

The NVRAM battery charger has been switched to

Error! No text of specified style in document.

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

405/0x195 406/0x196 407/0x197

408/0x198 409/0x199 410/0x19a 411/0x19b 412/0x19c

413/0x19d

414/0x19e

415/0x19f

416/0x1a0

417/0x1a1

418/0x1a2

419/0x1a3

420/0x1a4 421/0x1a5 422/0x1a6 423/0x1a7 424/0x1a8 425/0x1a9 426/0x1aa

427/0x1ab 428/0x1ac 429/0x1ad 430/0x1ae

431/0x1af 432/0x1b0 433/0x1b1 434/0x1b2 435/0x1b3

Logged?

Host FC Signal Detected Y Host Port N An FC signal is now detected on the Host port. Host FC Signal Lost Y JBOD Port N An FC signal is no longer detected on the Host port. Bypassing JBOD FC Port Y JBOD Port N The JBOD FC port has been bypassed from the FC

Including JBOD FC Port Y JBOD Port N The JBOD FC port has been included in the FC

Bypassing internal disk FC Port Including internal disk FC Port Y Internal Disk N The disk port specified in the event extended

Bypassing Host FC Port Y Host Port N The Host FC port has been bypassed from the FC

Including Host FC Port Y Host Port N The Host FC port has been included in the FC loop. VSC055 Initialization Failed Y VSC055 IO

VSC055 Cache Load Failed Y VSC055 IO

VSC055 Write Failed Y VSC055 IO

VSC055 Read Failed Y VSC055 IO

VSC055 Cache Flush Failed Y VSC055 IO

VSC055 Interrupt Clear Failed Y VSC055 IO

Power supply was inserted Y Power Supply N The power supply has been inserted into the

Power supply status is GOOD Y Power Supply N The power supply has changed from a failure state

Battery manufacture date obtained Battery manufacturer name obtained Battery device name obtained Y NVRAM

Charger update function called Y NVRAM

Charger current limit set Y NVRAM

NVRAM charger reset Y NVRAM

NVRAM battery charging enabled NVRAM battery charging disabled NVRAM battery backing up memory enabled NVRAM battery backing up memory disabled NVRAM battery reconditioning is being started NVRAM battery reconditioning is being stopped Battery Manager update function call NVRAM battery charger in Y NVRAM N

Y Internal Disk N The disk port specified in the event extended

Expander Chip

Y NVRAM

battery

Y NVRAM

battery

battery charger

Y NVRAM

battery charger

Y NVRAM

battery charger

Y NVRAM

battery charger

Y NVRAM

battery charger

Y NVRAM

battery charger

Y NVRAM

battery charger

Y NVRAM

battery

Mfg Fail?

port.

loop.

information has been bypassed from the FC loop.

information has been included in the FC loop.

loop.

Y An attempt to initialize the VSC055 indicated in the

event extended information has failed. The controller will be failed.

Y An attempt to load a cache of data fromt the

VSC055 indicated in the e v ent extended infor m atio n has failed. The controller will be failed.

Y An attempt to write to the VSC055 indicated in the

event extended information has failed. The controller will be failed.

Y An attempt to read from the VSC055 indicated in

the event extended information has failed. The controller will be failed.

Y An attempt to read from the VSC055 indicated in

the event extended information has failed. The controller will be failed.

Y An attempt to flush cache data to the VSC055

indicated in the event extended information has failed. The controller will be failed.

Y An attempt to clear an interrupt on the VSC055

indicated in the event extended information has failed. The controller will be failed.

enclosure.

to a good state.

N The manfacture date from the battery has been read

and stored internally

N The manufacturer name from the battery has been

read and stored internally

N The device name from the battery has been read and

stored internally

N The charger’s update function has been called f o r the

first time after power on or a system reset

N The NVRAM battery charger circuit has been

limited to supply a max value of current to the battery while charging

N The NVRAM battery cha rger was reset

N The NVRAM battery charger ha s been enabled to

charge the batteries

N The NVRAM battery charger has been disabled

from charging the batteries

N The NVRAM battery has been enabled to backup

memory in case of a power loss

N The NVRAM battery has been disabled from

backing up memory in case of power loss

N The NVRAM battery charger has been iss ued a

command to start the reconditioning of a battery.

N The NVRAM battery charger has been iss ued a

command to stop the reconditioning of a battery.

N The battery manage r update f unction has been called

for the first time after power on or reset

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

436/0x1b4

437/0x1b5 438/0x1b6 439/0x1b7 440/0x1b8 441/0x1b9 442/0x1ba 443/0x1bb

444/0x1bc

445/0x1bd 446/0x1be

447/0x1bf

448/0x1c0

449/0x1c1

450/0x1c2

451/0x1c3 452/0x1c4 453/0x1c5 454/0x1c6 455/0x1c7

456/0x1c8

457/0x1c9

458/0x1ca

459/0x1cb

Logged?

Mfg Fail?

download mode battery charger download mode to update the charger firmware TWSI bus is busy Y Ignore, unless

occurring

Controller N The two-wire serial bus local to t he controlle is

busy.

frequently

NVRAM battery not present Y NVRAM

battery

NVRAM battery failed Y NVRAM

battery NVRAM battery not responding NVRAM battery reconditioning stopped NVRAM battery reconditioning started

Y NVRAM

battery

Y NVRAM

battery charger

Y NVRAM

battery charger Array switched to secure mode Y NVRAM

battery Array out of secure mode Y NVRAM

battery

N The NVRAM battery charger does not detect the

presence of NVRAM battery

Y The NVRAM battery charger has declared the

NVRAM battery as failed

Y The NVRAM battery is not responding to two-wire

serial bus commands

N The NVRAM battery charger has aborted the

reconditioning of a battery

N The NVRAM battery charger has successfully

started reconditioning of a battery.

N The array has been switched to secure mode due to

the condition of the batteries

N The array has been switched out of secure mode

since the condition of the batteries do not warrant it

anymore Turning on LED due to battery failure

Y Battery amber

Y The amber LED that indicates battery failure has

LED

been turned on due to a battery failure condition.

When this log entry is unaccompanied by the log

entry, it indicates that the battery management

firmware module was unable to communicate with

the NVRAM battery. Possible two-wire serial bus

communication error. Battery has reached end of life Y NVRAM

battery NVRAM battery status is LOW

Y NVRAM

battery

Y The NVRAM battery internal status indicates that

the battery has reached the end of life condition

N The status of NVRAM battery is low. This means

that the battery charge is less than a specified

threshold va lue NVRAM battery status is GOOD

Y NVRAM

battery

N The status of NVRAM battery is good. This means

that the battery charge is equal or higher than a

specified threshold value NVRAM battery status is UNKNOWN

Y NVRAM

battery

N The status of the NVRAM battery is unknown. This

may be due to the firmware not being able to

communicate with the battery TWSI bus has been requested by another module

Unable to communicate with the NVRAM battery charger

Y Ignore, unless

occurring

frequently

Y Controller,

Controller, battery, power supply

N The battery management firmware has received a

Y The battery management firmware module is unable

battery

request from another firmware module to use t he

two-wire serial bus

to communicate with the NVRAM battery charger.

Possible two-wire serial bus communication error NVRAM battery reconditioning done NVRAM battery reconditioning status

Y NVRAM

battery charger

Y NVRAM

battery

N The NVRAM battery charger has successfully

reconditioned a battery

N The state of the controller and batt eries that are

checked before a decision is taken on reconditioning EEPROM status is good Y N The eeprom can b e communica ted with an d has

valid contents. EEPROM status is "not present"

Y N Communication with the eeprom has failed. The

module assumes that no hardware is present. EEPROM status is "failed" Y Y The TWSI bus may have failed, the read after a

write resulted in inconsistent data, or the crc

checksums in a device and it’s mirror (if available)

are not correct. EEPROM status is "unknown" Y N This can is caused when an TWSI bus command

fails. The eeprom is marked as unknown until a

retry is done or the TWSI bus reports a hard failure. Invalid state in state machine Y Y This is caused by an invalid state in an eeprom state

machine. If this error is found, there is a bug in the

firmware which must be fixed. TWSI Request Failure Y Controller,

battery, power supply,

Y The two-wire serial bus module would not allow the

read or write request. This is usually due to a bus

failure.

midplane

TWSI Read Failure Y Controller,

battery, power supply, midplane

Y The two-wire serial bus module retried the read and

was either not able to get a response from the

device, the transaction failed, or the bus failed. In

the case of a bus failure, the bus was good at the

time the read request was made. Now it has failed.

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

460/0x1cc

461/0x1cd

462/0x1ce

463/0x1cf 464/0x1d0 465/0x1d1

466/0x1d2 467/0x1d3 468/0x1d4

469/0x1d5

470/0x1d6 471/0x1d7 472/0x1d8

473/0x1d9

474/0x1da 475/0x1db 476/0x1dc

477/0x1dd 478/0x1de

479/0x1df 480/0x1e0

Logged?

TWSI Write Failure Y Controller,

TWSI transmit Failure Y Controller,

EEPROM now present Y N The eeprom was marked as not present because of

EEPROM new status Y N The status (GOOD, NOT_PRESENT, FAILED,

EEPROM Selftest Passed Y Mi dplane N The eeprom selftest was able to verify that the

EEPROM Selftest Failed Y Midplane Y The selftes t of the mir r o red eeproms detected the

EEPROM Read Failed Y Midplane Y The firmware was not able to read correctly from

EEPROM Write Failed Y Midplane Y The firmware was not able to read correctly from

EEPROM not mirrored Y M idplane Y The firmware was not able to read or write correctly

EEPROM can not get wwn Y Midplane Y During a request for a new lun WWN, the firmware

Firmware clone complete Y N.A. N Cloning of firmware to the ot her controller has

Firmware clone failed. Y Controller or

VSC7130_INT_DISABLE_EH Y VSC7130

LCC_DEVICE_STATE_INV ALID_EH

LCC_EVENT_EH Y LCC/ESD N Status of elements as well as information on the

LCC_DATA_LENGTH_ERR OR_EH LCC_NOT_SUPPORTED_ER ROR_EH

LCC_RETRIES_EXCEEDED _EH LCC_ELEMENT_EXCEEDE D_MAX_EH

LCC_STORAGE_EXCEEDE D_EH LCC_JEM_DELETE_DONE_ Y LCC/E SD N Topology Manager requ est ed a delete of a JEM.

Y LCC/ESD N Happens when a JEM is no longer allowed to send

Y LCC/ESD N The amount of data sent by the LCC was not what

Y LCC/ESD N Data that was received from the LCC was not

Y LCC/ESD N The retries for an I/O have been exceeded.

Y LCC/ESD N The number of elements ,for a specific element type,

Y LCC/ESD N Exceeded element or status storage space.

midplane

battery, powersupply, midplane

battery, power supply, midplane

N.A. N Cloning of firmware to the other controller has

Signal Detect / Port Bypass Control chip

Mfg Fail?

Y The two-wire serial bus module retried the write and

was either not able to get a response from the device, the transaction failed, or the bus failed. In the case of a bus failure, the bus was good at the time the read request was made. Now it has failed.

Y The two-wire serial bus module retried the transmit

and was either not able to get a response from the device, the transaction failed, or the bus failed. In the case of a bus failure, the bus was good at the time the read request was made. Now it has failed.

"no hardware" status from the TWSI module. Upon further attempts to communicate, the device is now responding.

CRITICAL) has changed.

midplane eeproms are mirrored.

data was not identical between the pair. An attempt to fix this inconsistancy failed.

either of the mirrored midplane eeproms.

from one of th e mirrored midplane eeproms. The system is no longer fully redundant.

was not able to read from either of the midplane eeproms. This is can be due to a variety of TWSI failures or the eeprom failing. The eeprom can only create 2,000 trillion (2 quadrillion) LUN’s. If this limit has been exceeded, the mi dplane must be replaced.

completed.

failed.

Y We’ve exceeded the maximu m number of retries in

attempting to clear a VSC7130 signal detect interrupt. The interrupt is being disabled to allow other TWS devices sharing the interrupt line to be able to generate interrupts. When this condition exists, the controller will not be able to respond to JBOD cable insertion and removal instantaneously, instead it will take up to five seconds to recognize the state change. This condition generally indicates bad FC conditions or a problem with the 7130.

requests to an LCC its retries are zeroed. The current outstanding I/O may complete but no additional I/O will be started.

LCC.

was expected or calculated.

supported. e.g. LCC F/W not supported or a NEW element type is not supported by the array F/W.

exceeded the maximum allowed. (e.g. Disk element type reports 60 drives in a single JBOD)

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

481/0x1e1

482/0x1e2

483/0x1e3

484/0x1e4

485/0x1e5 486/0x1e6

487/0x1e7

488/0x1e8

489/0x1e9 490/0x1ea 491/0x1eb 492/0x1ec

493/0x1ed

494/0x1ee

495/0x1ef

496/0x1f0

497/0x1f1

498/0x1f2

499/0x1f3

500/0x1f4

501/0x1f5

Logged?

Mfg Fail?

EH The JEM object has completed its deletion. LCC_JEM_DELETE_PENDI NG_EH

Y LCC/ESD N Topology Manager requested a delete of a JEM

when the JEM has an outstanding I/O. The deletion is pending on the completion/failure of the outstanding I/O. Any qued I/O would be aborted.

TWSI bus retry Y Ignore, unless

occurring

frequently.

Controller, midplane, power supply,

N A transaction on the two-wire serial bus failed and

was retried.

battery

Keyswit ch error Y Keyswitch

circuitry

Y This error code indicates that a controller was

removed from the system without generating a park interrupt to the remaining controller when intercontroller communication was enabled. The operating state of the loggin g controller is placed in the extended info area. If the removed controller was in use, the remaining controller will go through a short reset after logging this error.

Power-on reset Y controller N This event code indicates that a controller went

through a power-on reset. This is a normal power-on condition.

Hot plug reset Y controller N This event code indicates that a controller reset was

initiated due to a controller insertion or removal.

Heartbeat timeout reset Y controller N This event code indicates that a controller reset was

initiated due to a controller heartbeat timeout. One of the controllers in the system failed to check-in with the controller heartbeat checking module.

software fault reset Y c ontroller N This event code indicates that the firmware

performed an illegal action which resulted in a software fault and reset.

hardware fault reset Y controller N This event code indicates that t he hardware

performed an illegal action which resulted in a hardware fault and reset. This could mean that the hardware ge ne r ated an unrecognized interr upt vector or that the shared-memory controller detected an internal error.

abterm reset Y controller N This event code indicates that the controller reset

due to an abnormal termination in the firmware.

front panel reset Y controller N This event code indicates that the controller reset

due to a request through the front panel.

host reset Y controller N This event code indicates that the controller reset

due to a request from the host.

firmware download reset Y controller N Th is event code indicates that the controller reset

due to the completion of a successful firmware download.

controller failover reset Y replace the failed

controller

controller Y This event code indicates that the controller reset

due to the failure of the other controller in the enclosure.

memory error reset Y con troller N This event code indicates that the controller reset

due to a memory error.

dual controller comm failure Y Ignore unless a

dual controller

system is in a

communication

controller Y This event code indicates that the controller reset

due to a dual controller communication failure. If the controllers are able to communicate after the reset, this error can be ignored .

failure state

Controller Removed Y controller N This event code indicates that the controller was

removed from the enclosure with the power on. This is a normal entry for a controller that was hot-

removed previously. reset requested by other controller

Y controller N This event code indicates that the controller reset

due to a reset request from the other controller. Shared-memory error reset Y controller N This event code indicates that the cont roller reset i n

order to recover from an error detected in shared

memory. Controller reset Y controller N This event code i ndicates that the controller reset for

an unknown reason. Current mode parameters were saved

Y controller N This event code indicates that the current mode

parameters were saved to the saved mode

parameters without changing them. Unsupported mode parameter region revision

Y controller N An access to the mode parameter region of the

chassis NV memory found data with a format

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

502/0x1f6

503/0x1f7 504/0x1f8

505/0x1f9

506/0x1fa

507/0x1fb 508/0x1fc

509/0x1fd

510/0x1fe

511/0x1ff

512/0x200

513/0x201

514/0x202

515/0x203 516/0x204 517/0x205 518/0x206 519/0x207

Logged?

Enclosure NV memory contains an invalid mode parameter

Enclosure Power Switch Pressed Event Log uploaded Y controller N The event log data prior to this entry has been

Event Log upload complete Y controller N The event log data prior to this entry and following

Power Supply EEPROM Failed Y Power Supply Y Unable to communicate with the power supply

Temperature Sensor Failed Y Controller Y A write/r ead to/from the Temperature sensor failed. format subsystem reset Y controller N This event code indicates that the controller reset

Miscompare during midplane EEPROM selftest

FC Signal Detect Interrupt Y VSC7130 PBC

Dual-controller clock sync error

Event Log copy from NVSRAM start

Event Log copy from NVSRAM complete

Power supply failure Y Power Supply Y Indicates the output voltages supplied by the power

Cannot communicate with the power supply expander The power supply eeprom had an error The power supply blower had an error The over voltage error bit is set Y Power Supply Y The over voltage error bit is set in the power supply

The over current error bit is set Y Power Supply Y The over current error bit is set in the power supply

Y controller N During an upload of enclosure-specific mode

Y enclosure N The enclosure power switch has been pressed.

Y midplane Y This event code indicates that the data on the two

/ Dual Repeater Chip

Y controller N An interrupt from the sha red-memory controller

Y controller N Following this entry, events are being added to the

Y controller N The addition of entries from NVSRAM to the

Y Power Supply Y The communication with the power supply expander

Y Power Supply Y The EEPROM update function returned an error

Y Power Supply Y The Blower update function returned an error

Mfg Fail?

revision that is unsupported by this firmware.

parameters from enclosure NV memory, an invali d

value was found. A default value for this parameter

is being substituted.

uploaded from an image copy (due to invalid

NVRAM). There has been an unknown amount of

elapsed time after uploaded log entries that is not

accounted for in the current system time. Following

this entry and p rior to the LOG_UPLOAD_DONE

entry are any events logged prior to the upload .

Times for those events will not be consistent with

any other log entries, but will be internally

consistent.

the entry have occurred prior to the upload of the

event log image. These entries have been r ecorded

with a system time that is not consistent with the

uploaded entries, or the time in this entry and those

following it.

EEPROM. It is assumed to be failed. The power

supply must be replaced.

due to a format subsystem command.

eeproms at a given location was different. This

problem is usually fixed if the firmware can write to

the eeproms .

N An interrupt on one of the VSC7130 port-bypass

control / signal detect chips has occurred. See the

extended information for details.

reported the controller clocks were more than 1 tick

out of sync with each other.

log from NVSRAM entries that were written when

the log memory was not available. The time and

sequence numbers for these entries may not be

valid. Some normal entries may be interleaved with

these entries. The completion of the additions will

be noted by a corresponding event log system event.

controller log has been completed. The time and

sequence numbers for those entries may not be

valid. Some normal entries may be interleaved with

those entries. The start of the additions should have

been noted by a corresponding event log system

event.

supply have dropped below or raised above their

normal operating ranges. This can be ignored if seen

after a sudden power loss, or when unplugging,

plugging in, removing, or inserting power supplies.

was not successful

expander

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

520/0x208 521/0x209 522/0x20a

523/0x20b

524/0x20c 525/0x20d 526/0x20e

527/0x20f

528/0x210

529/0x211

530/0x212

531/0x213

532/0x214 533/0x215

534/0x216

535/0x217

536/0x218

537/0x219

538/0x21a

539/0x21b

540/0x21c

541/0x21d

The over temperature error b it is set The under voltage error bit is set

Logged?

Y Power Supply Y The over current error bit is set in the power supply

Y Power Supply Y The under voltage error bit is set in the power

Mfg Fail?

expander

supply expander Dram text area cksum error Y Co ntroller Y The DRAM Text area chec ksum does not matc h the

checksum calculated during initialization. A bgm

timer polls to check t he CKSUM once every ho ur. Software address warning Y Controller N This warning indicates that there is switch conflict

in the JBOD enclosures . Two or more enclosure

switches are set to the same address. LCC switch address warning Y Controller N This warning indicates that there is an LCC switch

mismatch within a JBOD enclosures. Power supply not present Y Power Supply Y This warning indicates that the power supply is not

present Map Disk Event Y Controller N This error code indicates that the Topology Manager

MAP DISK code had an event that it has logged.

The defined events are REDUNDANT MAP

DISKS, MAP_DISK_REDUNDANCY_LOSS, and

NO_MAP_DISKS. Battery NVRAM backup command Unsupported host po rt be hav ior table revision

Y NVRAM

battery charger

N The command sent to enable or disable the batteries

from backing up the NVRAM has failed.

Y Ignore None N The host port behavior table that was read from

chassis NV memory contains an unsupported

revision value. The RAM-based table will be

initialized as empty. Host Port Behavior table was initialized as empty

Y None N The host port behavior table was initialized as

empty due to a failure to read the contents from

chassis NV storage. Firmware download failed Y Ignore. These

should be

detected by the

download utility.

AutoFormat Event Occured Y Ignore unless no

Operator activity

none N A firmware download operation failed. The details

of the failure are included in the event unique

section of the event and other events logged in

conjunction with this one.

Disk Drive, Back End FC Link

N An AutoFormat event was logged, th is is caused

either by a backend format of an internal drive

beginning or completin g. Look as the associated

data for drive and status. Power supply is not connected to an AC source Some non-critical midplane eeprom data was not rest ored.

Y Power Supply Y This warning indicates that the power supply is not

connected to an AC source.

Y Midplane

EEPROM

N This warning indicates that some non-critical

eeprom data was not restored during the automatic

restore process. The user should be able to replace

this data by hand. (Licenses, mode parms, Host port

behavior, etc. Automatic midplane repair failed.

Y Midplane

Y This warning indicates the automatic midplane

EEPROM

eeprom repair process has failed because of bad

NVSRAM data. The repair can not be done. Temp sensor exceeded warnin g temperature.

Y Controller

Y The temperature sensor has exceeded the

Temp Sensor

recommended temperature for asserting an over-

temp warning. Temp sensor exceeded shutdown temperature.

Y Controller

Y The temperature sensor has exceeded the

Temp Sensor

recommended temperature for issuing a controller

shutdown. Temp sensor is now in range. Y Controller

Temp Sensor

N The temperature sensor had exceeded the

recommended temperature for asserting a warn ing.

The temperature has now come back down within

range. There is 3 degrees C of hysteresis. Disk interface online. Y Ignore Disk interface N A disk interface has come online and is functional.

This occurs normally during reset or reconfiguration

(hotplug). Disk interface device discovered.

Y Ignore Disk interface N A device has been discovered on a disk interface

during reset or reconfiguration (hotplug). This is

normal. Disk interface device logout Y Ignore Disk Interface N The login to a d evice on a disk interface has been

closed. This occurs normally during reconfiguration

(hotplug). Disk interface error count has incremented

Y Ignore, unless

occurring

frequently

Disk interface N The count of link-level errors on a disk interface has

incremented. This can occur under normal

circumstances (especially with disk hotplug), so it

does not indicate a problem unless it occurs

frequently.

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

542/0x21e

543/0x21f

544/0x220

545/0x221

546/0x222

547/0x223 548/0x224

549/0x225

550/0x226 551/0x227

552/0x228

553/0x229 554/0x22a

555/0x22b

556/0x22c

557/0x22d

558/0x22e

559/0x22f

560/0x230 561/0x231

562/0x232

Logged?

Disk interface is down Y Disk interface,

Lost flash log entry Y Ignore Controller flash

Backend channel hardware failure

Maintenance reset Y Ignore. These

Disk dropped for map data Y Failing disk Disk N An error has occurred accessing the map data index

Using spare map disk index region Event log structure cor r upted Y controller N The Event log structure in NVRAM was determined

Front End FC Link Up Event Y controller N The Front End Fibre Channel port is now up. The

Front End SCSI Queue Full defected Decoder lock exclusive lock grant timed out.

Decoder lock request was deferred.

Decoder deferred lock request was granted. Decoder deferred lock was released.

Disk interface CheckCondition error

Power Switch Failed Y Ignore Midplane N The power switch’s redundant switch outputs are

Map disk dropped Y Ignore Disk Y The Dump Disk Manager has decided to drop a map

Map disk added Y Ignore Disk Y The Dump Disk Manager has added a map disk. Map disk reduplex complete Y Ignore Disk N The Dump Disk Manager has finished reduplexing

Map disk removed Y Ignore Disk N The Dump Disk Manager has removed a map disk. Backend Disk Initialization Failure

Backend Invalid BlockSize Disk

disk or controller

Y Failing controller Backend

occur

periodically.

Y Failing disk Disk N An error in the primary map disk index data and the

Y controller N The Front End Fibre Channel port has reached a

Y Ignore. Lab

only.

Y Ignore. Lab

only.

Y Ignore. Lab

only.

Y Ignore. Lab

only.

Y Ignore Disk, LCC,

Y Ignore Backend Disk N One of the backend disks was set to an "Init Failed"

Disk interface N A disk interface has been down for longer than the

log

channel

controller N This reset is performed periodically to scrub ECC

none N The cross controller lock module failed to grant the

none N The cross controller lock module deferred a request

none N The cross controller lock module granted a lock

none N The sequencer released a decoder lock that was

Disk interface

Mfg Fail?

time allowed for normal recovery. Array function

will continue without use of this channel. This can

be caused by a bad connection to disks (internal or

external), or by a failind disk or controller.

N This event code should only appear in the flash logs.

It indicates that a log entry was lost because the

flash log queue was full when a new event arrived to

be logged. This is expected to be a normal

occurrence, but is logged to show that some

information has been lost.

N An error has occurred which indicates that the disk

interface electronics is failing. It is also possible

that this error could be caused by failing

interconnect hardware.

errors from NV memory.

region of a map disk and the disk will no longer be

used to store map data.

spare copy of the data is being used.

to be corrupt. The event log has been reset and any

contents have been lost.

topology that was acquired is in the extended log

information.

SCSI QUEUE FULL condition.

decoder’s lock in exclusive mode, within the

allowed period, after an ob tain request was deferred.

This may indicate a deadlock in the system or that

the system is too busy.

to obtain the decoder’s lock. This is normal for

exclusive acquisition but not for shared acquisition.

request that had previously been deferred.

originally deferred when it was requested from the

cross controller lock module.

N A command sent to a device on a disk interface has

returned a Check Condition status. This can occur

under normal circumstances, so it does not indicate

a problem unless it occurs frequently, or if the Sense

Data indicates a problem.

inconsistent. To repair this problem, the midplane

must be replaced.

disk due to a disk failure or hotplug event. This

should normally result in a Map Disk Redudancy

Loss warning or No Map Disks warning.

the map disks. This process begins after a disk is

inserted and is being set up as the second map disk.

state. This could indicate a significant problem with

the disk, or simply that it needs to be formatted.

state because it has an invalid blockS iz e. This could

mean the disk failed a previous format (0-block

size) or came new from the factory (512-block size).

Event

Number

(dec/hex)

Event Name

Predictive

Maintenance

Implication

Suspected Components

Description

563/0x233

564/0x234 565/0x235 566/0x236

567/0x237 568/0x238

569/0x239 570/0x23a 571/0x23b

572/0x23c 573/0x23d

574/0x23e

575/0x23f

576/0x240

577/0x241

578/0x242

579/0x243

580/0x244 581/0x245 582/0x246

583/0x247

584/0x248

Logged?

PDM Add Y Ignore Disk N A PDM has been added for the specified device.

Disk Redundant Path Found Y Disk N A redundant path to an already known drive has

Disk Redundant Path Lost Y Disk N A redundant path to an already known drive has

State Changing Start Y N The state changing bit has been asserted. State Changing End Y N The state changing bit has been deasserted. Disk Driver Created Y N A PDD (proxy and real) h as been instanti ated for a

Disk Driver Deleted Y N A PDD (proxy and rea l) has been destroyed for a

Hot Plug Even t Y N A generic hot plug event occurred. See the event

New Device Found Y N A new device was discovered by CFMhot. Old Device Lost Y N A device CFMhot already knew about has

Warning Indicator Activated Y N One of the warning indicators has been actviated.

Warning Indicator Deactivated Y N One of the warning indicators has been deactviated.

PDM Label Table Mismatch Y N A PDM, during instantiation, came up with different

Uploaded mode parms were defaulted

Start multi disk loss scan Y Ignore. should

Multi disk loss detected Y Ignore. should

Exit multi disk loss reset Y Ignore. should

Policy generated relocation error Insufficent space for policy relocation Frontend Fibre Channel Hung Port Event

DDM Disk Change Event Y Ignore None N This error is being used to indicate (in the extended

Repair of corrupted eeprom done.

Y NA None Y The midplane EEPROM mode parameters region

controller N A backend scan was started to detect a multiple disk be other prior failure events

controller N A multiple disk loss was detected. Raid 5 DP writes be other prior failure events

controller N This controller is exiting from the excessive disk be other prior failure events

Y NA None Y A policy sponsored data relocation failed.

Y NA None Y There is not enough space to perform a policy

Y Ignore None N This error code indicates that the Front End Fibre

Y Ignore Controller

EEPROM

Mfg Fail?

The actual blockSize is output i n the verbose log eventInfo.

This could mean that a previously downed drive is being re-added, or that a PDM was added for a newly added drive.

been discovered.

been lost.

disk.

unique description for more information.

disappeared.

Check the extended event information for more information.

basic information. One possible cause is downloading unsupported mech FW that doesn’t conform to the required capacity point for drive category.

contains a revision that is older than the revision expected by current firmware. As a result, some mode parameters were set to their default values since there was no saved value present in the EEPROM.

loss condition because of a raid 5 DP write failure. If a multiple disk loss is detected, raid 5 DP writes will not be allowed to proceed. Another log entry will indicate if the condition is detected. No additional entry will be made otherwise.

will not be processed until this condition is cleared.

missing condition. Enough of the missing disks have been restored to attempt normal operations.

HP StorageWorks 7100 Appendix

Specifications and Main Features

Frequently Asked Questions

User Manual