Maxtor Atlas 10K V, Product Manual

Page: 175 / 253

Maxtor Atlas 10K V
5-117
Table 5-170
Supported Sense Keys
Sense Key Code Description
NO SENSE 0h
There is no specific sense key information to be reported for the designated logical unit.
This is the case for a successful command or a command that received CHECK CON-
DITION or COMMAND TERMINATED status because one of the following bits is set
to 1: File Mark, EOM, or ILI.
RECOV-
ERED ER-
ROR
1h
The last command completed successfully with some recovery action performed by the
drive. Details may be contained in the additional sense bytes and the Information field.
When multiple recovered errors occur during one command, the choice of which error
to report (first, last, most severe, etc.) is device specific.
NOT READY 2h
The logical unit cannot be accessed. Operator intervention may be required to correct
this condition.
MEDIUM
ERROR
3h
The command terminated with a non-recovered error condition that was probably
caused by a flaw in the medium or an error in the recorded data. This sense key can also
be returned if the drive is unable to distinguish between a flaw in the medium and a spe-
cific hardware failure (Sense Key
HARDWARE
ERROR
4h
The drive detected a non-recoverable hardware failure while performing the command
or during a self-test. The error type could be controller failure, device failure, etc.
ILLEGAL
REQUEST
5h
The drive detected an illegal parameter in the Command Descriptor Block or in the ad-
ditional parameters supplied as data for some commands. If the drive detects an invalid
parameter in the Command Descriptor Block, it terminates the program without altering
the medium. If the drive detects an invalid parameter in the additional parameters sup-
plied as data, the drive may have already altered the medium. This sense key may also
indicate that an invalid IDENTITY message was received.
UNIT
ATTENTION
6h
The drive generates this sense key whenever the drive is reset by a TARGET RESET
message, a hard reset condition, or by a power-on reset. Other conditions that generate
a UNIT ATTENTION include:
•
The mode parameters in effect for this initiator have been changed by another initia-
tor.
• The microcode has been changed.
• Tagged commands queued for this initiator were cleared by another initiator.
• INQUIRY data has been changed.
• The mode parameters in effect for the initiator have been restored from non-volatile
memory.
• Other events that require the attention of the initiator.
DATA
PROTECT
7h
A Read or Write command was attempted on a sector that is protected for this operation.
The requested operation was not performed.
VENDOR
SPECIFIC
9h This sense key is used to report specific Maxtor conditions.
ABORTED
COMMAND
Bh
The drive aborted the command. The initiator may be able to reissue the command suc-
cessfully.
MISCOM-
PARE
Eh The source data did not match the data read from the medium (i.e., a mismatch).