Seagate SCSI Interface Product Manual page 207

Table of Contents

Advertisement

SCSI Interface Product Manual, Rev. J
cal block. For example, if the Sense Key is Medium Error, it is the Logical Block Address of the failure
block.
[9]
Additional Sense Length—Specifies additional sense bytes are to follow. This is limited to a maximum of
10 (decimal) additional bytes. If the Allocation Length of the command descriptor block is too small to
transfer all of the additional sense bytes, the Additional Sense Length is not adjusted to reflect the trunca-
tion.
[10] Additional Sense Code and Additional Sense Code Qualifier—Provides additional clarification of errors
whenever Sense Key is valid. Error code definitions are in Table 157. If the condition is not reportable by
the drive, the Additional Sense Code and Additional Sense Code Qualifier are set to No Additional Sense
Information (Code 0000).
[11] Defined for Seagate internal use only.
[12] The Sense Key Specific Valid (SKSV) bit and Sense Key Specific bytes are described below.
The additional sense bytes field may contain command specific data, peripheral device specific data, or
vendor specific data that further defines the nature of the Check Condition status.
The Sense Key Specific field is defined by this specification when the value of the SKSV bit is one. The
definition of this field is determined by the value of the Sense Key field. This field is reserved for sense
keys not described in Table 156.
If the Sense Key field is set to Illegal Request (5H) and the SKSV bit is set to one, the Sense Key Specific
field is defined as shown in Table 153. These fields point to illegal parameters in command descriptor
blocks and data parameters sent by the initiator in the Data Out phase.
Table 153: Field Pointer Bytes
Bit
7
Byte
15
SKSV
16
(MSB)
17
A Command Data (C/D) bit of one indicates that the illegal parameter is in the command descriptor block.
A C/D bit of zero indicates that the illegal parameter is in the data parameters sent by the initiator during
the Data Out phase.
A Bit Pointer Valid (BPV) bit of zero indicates that the value in the bit pointer field is not valid. A BPV bit of
one indicates that the bit pointer field specifies the bit of the byte designated by the field pointer that is in
error. When a multiple-bit field is in error, the bit pointer field shall point to the most-significant (left-most)
bit of the field.
The Field Pointer field indicates the byte of the command descriptor block or of the parameter data that
was in error. Bytes are numbered starting from zero, as shown in the tables describing the commands and
parameters. When a multiple-byte field is in error, the pointer shall point to the most-significant (left-most)
byte of the field.
Note. Bytes identified as being in error are not necessarily the place that has to be changed to correct
the problem.
If the sense key is Recovered Error (1h), Hardware Error (4h), or Medium Error (3h), and if the SKSV bit is
one, the Sense Key Specific field is defined as shown in Table 154. These fields identify the actual number
of retries used in attempting to recover from the error condition.
Table 154:
Actual Retry Count Bytes
Bit
7
Byte
15
SKSV
16
(MSB)
17
6
5
C/D
Reserved
6
5
4
3
BPV
Field Pointer
4
3
Reserved
Actual Retry Count
2
1
Bit Pointer
(LSB)
2
1
(LSB)
193
0
0

Advertisement

Table of Contents
loading

Table of Contents