Technical data

B.6 Status
A status byte must be sent from the target to the initiator during the Status phase at the
completion of each command.
The contents of the SCSI status byte must conform to rules of the SCSI 2 specification.
Otherwise, there are no restrictions on the use of this byte. Table B–7 lists the status bytes.
Table B–7: Status Bytes
Status Byte Description
Good The target has successfully completed the command.
Check Condition Any error, exception, or abnormal condition that causes sense data to be set must
cause a Check Condition status. The REQUEST SENSE command must be issued
following a Check Condition status, to determine the nature of the condition.
Condition Met The SEARCH DATA command returns this status whenever a search condition
is satisfied. The logical block address of the logical block that satisfies the search
may be determined with a REQUEST SENSE command. This status is also
returned by the PRE-FETCH command when there is sufficient space in the cache
memory for all of the addressed logical blocks.
Busy The target is busy. This status is returned whenever a target is unable to
process the command from an otherwise acceptable initiator (that is, there are
no conflicting reservations). The recommended initiator recovery action is to issue
the command again at a later time.
Intermediate Linked commands are not implemented.
Reservation
Conflict
This status is returned whenever a SCSI device attempts to access a logical unit or
an extent within a logical unit that is reserved with a conflicting reservation type
for another SCSI device. The recommended initiator recovery action is to issue the
command again at a later time.
Queue Full Tagged queuing is not implemented.
B–8 Small Computer System Interface (SCSI)