HP StorageWorks 7100 - Virtual Array Appendix page 6

FC-SCSI Interface SpecificationDescribes the IceCube SCSI interface. Targetted as part of OEM manual.Disk Array Con
Event Event
Number Name
(dec/hex)
70/0x46 Disk Interface Command
Timeout
71/0x47 Disk Interface Hot Plug
72/0x48
Host Write Collision With
Failed Cache Post
73/0x49 Disk Drive Defect List Error
74/0x4a Disk Drive Format Error
75/0x4b Invalid/unsupported hierarchic
LUN reference
76/0x4c Disk Interface State Error
77/0x4d
Write Sequence In Cache
Broken By Host Abort
78/0x4e Silent Disk Drive Error
Recovery
79/0x4f Check Condition From Disk
Drive With No Sense
80/0x50
Disk Drive Failed Start Unit
Command
81/0x51
Unexpected Disk Drive Status
82/0x52 Insufficient resources for LUN
operation.
83/0x53 Microcode Changed Unit
Attention
84/0x54 Create LUN can't get LUN
WWN seed
85/0x55
Recovered By Disk Drive On
Retry
86/0x56
Not ready, manual intervention
required
87/0x57
Data loss detected
88/0x58
Insufficient memory resources
Predictive Suspected
Maintenance Components
Implication
Y N.A. None
N N.A. None
Y ignore - see None
accompanying
errors
Y Single Disk Drive
Occurrance
Y Single Disk Drive
Occurrance
N Ignore - Host None
LUN addressing
problem
Y N.A. None
N N.A. None
N N.A. None
Y Single Disk Drive
Occurrence
Y Single Disk Drive
Occurrence
Y Single Disk Drive,
Occurrance, Controller, Disk
possible Interface
compatibility
problem
N N.A. None
N N.A. None
Y None allowed None
Y See drive vendor Disk Drive
recommendation
N N.A. None
Y N.A. None
N N.A. None
Error! No text of specified style in document.
Description
Y A backend device did not complete a command
within the allotted time.
N A command was aborted by a disk hotplug or by
error error recovery for some other command.
N A write launched 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 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.
N The disk drive returned a status of
CHECK_CONDITION, HARDWARE_ERROR, .
The PDD's retries are exhausted or the I/O is not
retryable. The drive may need to be formatted.
N The disk drive returned a status of
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.
Y The host specified an 8-byte hierarchic LUN
reference that contained either an unsupported
address mode or made use of hierarchy levels that
the subsystem does not support.
N The backend disk interface hardware or software
state information was incorrect for observed
activity.
N A part of a write cache stream was aborted by the
host. The failed write was forced because the
operation could not be completed. The host should
retry the operation.
N On a previous attempt(s), the drive failed the I/O.
(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 status to the host.
N The disk drive returned a check condition with no
sense data. The PDD's retries are exhausted or the
I/O is not retryable.
N The disk drive returned bad status for a start unit
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.
N There is insufficient physical disk storage capacity
present for the LUN operation that was requested.
More disks must be added to the subsystem before
the operation can be successful.
N New controller microcode was just installed.
Y The create LUN operation cannot be completed
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.
N On a previous attempt(s), the drive failed the I/O.
The PDD retried the I/O and the disk drive returned
a status of CHECK_CONDITION,
RECOVERED_ERROR
Y The command is not possible in current subsystem
state.
Y An otherwise successful read op failed due to data
loss recorded in at least 1 of the disk blks read This
is a rev2 error; the error is defined but not used in
rev1 firmware.
N There is not enough memory installed in the