Status Byte Codes - Seagate ST3285N Product Manual

32 ST3655 Family SCSI Drives Product Manual, Rev. A

3.2 Status byte codes

After the drive terminates each command, the drive sends the status byte
(shown below) to the initiator during the status phase, unless the com-
mand is terminated by one of the following methods:
• An abort message
• A bus device reset message
• A hard reset
• A catastrophic reset condition
Bytes
7 6
Reserved
0
0 0
The status byte code can be any of the following:
00 Good status. The drive has successfully completed execution of
H
a command.
02 Check condition status. The drive detected an error, an excep-
H
tion, or an abnormal condition. In response, the initiator may issue
a Request Sense command to determine the nature of the condi-
tion.
08 Busy status. The drive is busy, and is, therefore, unable to accept
H
a command from an initiator. The initiator retries the command
later. The drive returns a busy status if the initiator has not sent
the disconnect message and tries to queue a command or if the
initiator rejects the disconnect message and the queue is not
empty.
10 Intermediate status. The drive successfully completed a com-
H
mand that was one of a series of linked commands without issuing
a check condition status or reservation conflict status. (Had the
drive not returned an intermediate status, the series of linked
commands would have been terminated.)
18 Reservation conflict status. A SCSI device tried to access the
H
drive, but was unable to because the drive was already reserved
by another SCSI device.
28 Queue full status. The drive received a command, but rejected
H
it because the queue was full. The drive only uses this status if
tagged command queuing is implemented.
Bits
5 4 3 2
Status byte code
1 0
RSVD
0