Page 1 ........... . Ultra160 .
Page 3 ..........Ultra160 .
Page 4 Seagate reserves the right to change, without notice, product offerings or specifications. No part of this publication may be reproduced in any form without written permission of Seagate Technology LLC.
Page 5 Seagate Applications Engineers. Seagate Applications Engineers will try to obtain a value for the particular desired specification that is as close to permanent as is possible at the time...
Page 7: Table Of Contents
SCSI Interface Product Manual, Rev. B Table of Contents Interface requirements ............1 How to use this interface manual .
Page 8 SCSI Interface Product Manual, Rev. B 2.5.37 Receive skew compensation ......... .26 2.5.38 Receiver amplitude time skew .
Page 9 SCSI Interface Product Manual, Rev. B 2.12.10 Message restrictions ..........43 2.12.11 Negotiation message sequences .
Page 10 viii SCSI Interface Product Manual, Rev. B 3.8.2 STATUS phase exception condition handling ......67 MESSAGE phase .
Page 11 SCSI Interface Product Manual, Rev. B 4.4.2 ACA (AUTO CONTINGENT ALLEGIANCE)......92 4.4.3 HEAD OF QUEUE .
Page 12 SCSI Interface Product Manual, Rev. B 7.6.4 Sense data............129 7.6.4.1 Asynchronous Event Reporting .
Page 13 SCSI Interface Product Manual, Rev. B 8.10.2 MODE SELECT page descriptors ........194 8.11 MODE SELECT (10) command (55h) .
Page 14 SCSI Interface Product Manual, Rev. B 8.34.3 Third Party Release ..........279 8.35 RELEASE (10) command (57h) .
Page 15 SCSI Interface Product Manual, Rev. B xiii 9.2.3 Self-test modes........... 329 9.2.3.1 Foreground mode .
Page 16 SCSI Interface Product Manual, Rev. B...
Page 17: List Of Figures
SCSI Interface Product Manual, Rev. B List of Figures Figure 1. Functional scope of SCSI standards..........1 Figure 2.
Page 18 SCSI Interface Product Manual, Rev. B...
Page 19: Interface Requirements
Seagate products. The features described in this manual are typically referred to as “Ultra160 SCSI” or “Ultra320 SCSI” features. Each individual drive’s Product Manual, Volume 1, for the various SCSI interface products contains additional and more detailed information on protocol, features supported, timing, and electrical/mechanical aspects of how the SCSI interface is implemented by that product.
Page 20: Applicable Standards
SCSI Interface Specifications listed in Section 1.1.2. The drives covered by this product manual are classified as “Intelligent” peripherals. The Seagate SCSI interface described herein consists of a 9 or 18 bit bidirectional data bus (includes bits for parity checking and enabling CRC protection), plus 9 control signals. The SCSI interface supports multiple ini-...
Page 21: Glossary
SCSI Interface Product Manual, Rev. B Note. In this revision, some new terminology is introduced as taken from the ANSI specifications. In many instances, the broader scope terms such as “initiator” and “target” are not used, but rather the more specific terms “Application Client”...
Page 22 SCSI Interface Product Manual, Rev. B client—An object that requests a service from a server. command—A request describing a unit of work to be performed by a device server. command descriptor block—A structure used to communicate a command from an application client to a device server.
Page 23 SCSI Interface Product Manual, Rev. B enabled (task state)—The state of a task that may complete at any time. Alternatively, the state of a task that is waiting to receive the next command in a series of linked commands. ended command—A command that has completed or aborted. exception condition—Any event that causes a SCSI device to enter an auto contingent allegiance or contin- gent allegiance condition.
Page 24 SCSI Interface Product Manual, Rev. B iuCRC protection—The use of CRC to detect DT DATA PHASE data transmission errors during parallel trans- fers. Contains CRC information covering all bytes transmitted in a SPI information unit. layer—A subdivision of the architecture constituted by subsystems of the same rank. linked CDB—A CDB with the link bit in the control byte set to one.
Page 25 SCSI Interface Product Manual, Rev. B peer entities—Entities within the same (protocol) layer. pending task—A task that is not a current task. physical interconnect—A single physical pathway for the transfer of information between SCSI devices in a domain. physical reconnect—The act of resuming a nexus to continue a task. A SCSI target port initiates a physical reconnect when conditions are appropriate for the physical bus to transfer data associated with a nexus between a SCSI initiator port and a SCSI target port.
Page 26 SCSI Interface Product Manual, Rev. B SCSI I/O system—An I/O system, consisting of two or more SCSI devices, a SCSI interconnect and a SCSI protocol, which collectively interact to perform SCSI I/O operations. SCSI protocol layer—The protocol and services used by a SCSI application layer to transport data represent- ing a SCSI application protocol transaction.
Page 27: Keywords
SCSI Interface Product Manual, Rev. B task management request—A request submitted by an application client, invoking a task management func- tion to be executed by a task manager. task management response—The response returned to an application client by a task manager on comple- tion of a task management request.
Page 28: Physical Interface Characteristics
SCSI Interface Product Manual, Rev. B shall—A keyword indicating a mandatory requirement. Designers are required to implement all such manda- tory requirements to ensure interoperability with other standard conformant products. should—A keyword indicating flexibility of choice with a strongly preferred alternative. Equivalent to the phrase “it is recommended.”...
Page 29: Summary Of Scsi Commands And Messages
SCSI Interface Product Manual, Rev. B Summary of SCSI commands and messages Following is an alphabetical table listing the SCSI commands described in this manual. Details are given in Section 8.0. Command name Hex code Device type Page number CHANGE DEFINITION COMPARE COPY COPY AND VERIFY...
Page 30 SCSI Interface Product Manual, Rev. B Command name Hex code Device type Page number VERIFY Direct access WRITE 6 Direct access WRITE 10 Direct access WRITE AND VERIFY Direct access WRITE BUFFER WRITE LONG Direct access WRITE SAME XD READ Direct access XD WRITE Direct access...
Page 31: Scsi Bus
Section 1.1.2. Communication on the SCSI Bus is allowed between only two SCSI devices at a time. Seagate drives support systems with a maximum of 16 SCSI devices including the host computer(s) connected to the SCSI bus. Each SCSI device has a SCSI ID bit assigned as shown in Table 1.
Page 32: Scsi Bus Signals Overview
Paragraphs 3.1.5.2 and 3.5.3.2 of the Ultra2 SCSI Interface Product Manual, Volume 2, part num- ber 77738479. This Ultra160/Ultra320 SCSI Interface Product Manual, Volume 2, discusses SCSI-3 protocol (now called only “SCSI”). There are now different ways of latching data from the REQ and ACK signals, depending on whether ST DATA phases, DT DATA phases, or paced transfers are being used for information transfers.
Page 33 SCSI Interface Product Manual, Rev. B P_CRCA (Parity/CRC Available)—A signal identifying either parity or CRC available based on bus phase and negotiated settings. During the SELECTION PHASE, RESELECTION PHASE, ST DATA PHASE, COMMAND PHASE, MESSAGE PHASE, and STATUS PHASE, this signal is referred to as DB(P_CRCA) and is sourced by the SCSI device port driving the Data Bus.
Page 34: Drive Select
SCSI Interface Product Manual, Rev. B DB(7–0) (8-bit data bus)—Each data bit that forms the 8-bit data bus. Bit significance and priority during arbi- tration are shown in Table 1. DB(15–0) (16-bit data bus)—16 data bit signals that form the 16-bit Data Bus. Bit significance and priority dur- ing arbitration are shown in Table 1.
Page 35: Or-Tied Signals
SCSI Interface Product Manual, Rev. B Figure 3. Voltage and current definitions Figure 4 defines the signaling sense of the voltages appearing on the – signal and + signal lines as follows: a. The – signal terminal of the driver shall be negative with respect to the + signal terminal for an asserted state.
Page 36 SCSI Interface Product Manual, Rev. B 16 data bit (P) cable 8 data bit (A) cable C/D, I/O, DB(15-8), SCSI bus phase MSG, REQ ACK, ATN DB(7-0) P_CRCA DB(P1) COMMAND Targ None Targ Init Init Init None ST DATA IN Targ None Targ...
Page 37: Scsi Bus Timing
SCSI Interface Product Manual, Rev. B SCSI bus timing Unless otherwise indicated, the delay time measurements for each SCSI device, defined in paragraphs 2.5.1 through 2.5.58 shall be calculated from signal conditions existing at that SCSI device’s own SCSI bus connec- tion.
Page 38 SCSI Interface Product Manual, Rev. B Timing values for negotiated transfer rate [1] Timing description Reference Type Asynch Fast-5 Fast-10 Fast-20 Fast-40 REQ(ACK) period Section 2.5.39 nom N/A 200 ns 100 ns 50 ns 25 ns Transmit assertion period [2] Section 2.5.53 min 80 ns 30 ns...
Page 39 SCSI Interface Product Manual, Rev. B Timing values for negotiated transfer rate [1] Timing description Reference Type Fast-10 Fast-20 Fast-40 Fast-80 Fast-160 Transmit hold time [2] [3] Section 2.5.54 min 38.4 ns 19.2 ns 9.6 ns 4.8 ns 4.77 ns Transmit ISI compensation Section 2.5.55 max 1.0 ns...
Page 40 SCSI Interface Product Manual, Rev. B Table 9: SCSI Fast-160 timing budget template Item Fast-160 Comments REQ(ACK) period 12.5 ns From Table 7 Transfer period 6.25 ns REQ(ACK) period / 2 Ideal Setup/Hold 3.125 ns REQ(ACK) period / 4 Non-compensatable (Early to Late) Worst-case total of + and –...
Page 41: Arbitration Delay
SCSI Interface Product Manual, Rev. B 2.5.1 Arbitration delay The minimum time a SCSI device shall wait from asserting BSY for arbitration until the data bus can be exam- ined to see if arbitration has been won (see Section 3.1.2). There is no maximum time. 2.5.2 ATN transmit setup time When information unit transfers are not being used, the ATN transmit setup time is the minimum time provided...
Page 42: Cable Skew Delay
SCSI Interface Product Manual, Rev. B 2.5.8 Cable skew delay The maximum difference in propagation time allowed between any two SCSI bus signals when measured between any two SCSI devices excluding any signal distortion skew delays. 2.5.9 Chip noise in receiver The maximum transition to transition time shift due to the internal physics of the receiving SCSI device circuitry.
Page 43: Pcrc Transmit Hold Time
SCSI Interface Product Manual, Rev. B 2.5.18 pCRC transmit hold time The minimum time provided by the transmitter between the transition of the REQ signal and the transition of the P_CRCA signal during data group transfers. 2.5.19 pCRC transmit setup time The minimum time provided by the transmitter between the transition of the P_CRCA signal and the transition of the REQ signal during data group transfers.
Page 44: Receive Internal Hold Time
SCSI Interface Product Manual, Rev. B negation) of the REQ signal or the ACK signals and the changing of the data bus, DB(P_CRCA), and/or DB(P1) signals. 2.5.30 Receive internal hold time The minimum time provided for hold time in the receive data detector after allowance for timing errors and tim- ing compensation from all sources measured from the worst-case bit (i.e., data or parity) to the compensated offset strobe.
Page 45: Reset Delay
SCSI Interface Product Manual, Rev. B aging the time between edges during long (i.e., greater than 512 bytes) all zeros or all ones data transfers and by ignoring the first and last 10 transitions. In DT DATA phases, the negotiated transfer period for data is half that of the REQ(ACK) period since data is qualified on both the assertion and negation edges of the REQ or ACK signal.
Page 46: System Deskew Delay
SCSI Interface Product Manual, Rev. B 2.5.49 System deskew delay The minimum time that a SCSI device should wait after receiving a SCSI signal to ensure that asynchronous transfers at the same time are valid. The system deskew delay shall not be applied to the synchronous trans- fers or paced transfers.
Page 47: Transmit Req Negation Period With P_Crca Transitioning
SCSI Interface Product Manual, Rev. B 2.5.60 Transmit REQ negation period with P_CRCA transitioning The minimum time that a SCSI target port shall negate the REQ signal while transitioning P_CRCA during data group transfers. Specified to provide the increased receive REQ negation period, subject to loss on the inter- connect.
Page 48 SCSI Interface Product Manual, Rev. B Figure 8 shows an example of transfers with a negotiated transfer period of 6.25 ns at the receiving SCSI device’s connector. There is no difference as to when data is latched on paced transfers, however, the relation- ship between the data and REQ or ACK is required to be adjusted in the SCSI devices receiver to match the synchronous transfers DT Data shown in Figure 5.
Page 49: Figure 5. St Latching Data Vs. Dt Latching Data
SCSI Interface Product Manual, Rev. B REQ or ACK ST Data (synchronous or asynchronous transfers) DT Data (synchronous transfers) DT Data (paced transfers) DT & ST DT & ST Clock Clock Clock Clock Figure 5. ST latching data vs. DT latching data <----- transfer period = 25 ns ----->...
Page 50: Paced Transfer On A Scsi Bus
SCSI Interface Product Manual, Rev. B transfer period = 25 ns 25 ns 25 ns 25 ns REQ or ACK DT Data Clock Clock Clock Clock Example: A negotiated transfer period of 25 ns equates to a transfer rate of 40 megatransfers per second. Figure 7.
Page 51: Data Transfer Modes
SCSI Interface Product Manual, Rev. B During paced transfers, the clock signal (i.e., REQ or ACK) transitions at the negotiated transfer period. Data is qualified by the clock signal and the phase of the P1 signal. Receiver skew compensation is vendor specific and, therefore, not defined in this manual. SCSI Device SCSI Device Signal...
Page 52: Data Group Transfers
SCSI Interface Product Manual, Rev. B • Information unit transfers. Information units encapsulate all nexus, task management, task attribute, com- mand, data, and error protection. Usually these are called “SPI information units.” Sections 2.11.1 and 2.11.2 contain a brief description of how packetized information transfer and CRC protec- tion fit into the SCSI I/O system operation.
Page 53: Negotiation
SCSI Interface Product Manual, Rev. B transfer agreement between two SCSI devices (i.e., the RD_STRM bit set to one). A SCSI target port is not required to use read streaming even if streaming support is enabled. A SCSI target port, while streaming data, may give an indication that the stream of SPI data stream information nits are about to end while still sending the current SPI data stream information unit.
Page 54: Negotiable Fields
SCSI Interface Product Manual, Rev. B A port may originate negotiation even if its negotiation required flag is false (e.g., to change the settings, as part of integrity checking procedures, or, for a SCSI initiator port, after a SCSI target port has originated nego- tiation).
Page 55: Transfer Agreements
SCSI Interface Product Manual, Rev. B When negotiating, the responding port shall respond with values that are a subset of the values in the originat- ing message as indicated in Table 11 (e.g., if the originating message requests a REQ/ACK offset of 10h, the responding message has a REQ/ACK offset field set to 10h or lower).
Page 56: Transfer Period Factor
SCSI Interface Product Manual, Rev. B 2.12.5 Transfer period factor The Transfer Period Factor field selects the transfer period and determines which transfer rate’s timing values in Tables 5, 6, 7, and 8 shall be honored, provided that REQ/ACK OFFSET is greater than 00h. The field values are defined in Table 13.
Page 57: Transfer Width Exponent
SCSI Interface Product Manual, Rev. B For DT synchronous transfers the REQ/ACK offset is the number of REQ transitions that may be sent by the SCSI target port in advance of the number of ACK transitions received from the SCSI initiator port. For paced transfers in DT DATA IN phase the REQ/ACK offset is the number of data valid state REQ assertions that may be sent by the SCSI target port in advance of ACK assertions received from the SCSI initiator port.
Page 58: Protocol Options
SCSI Interface Product Manual, Rev. B 2.12.8 Protocol options The protocol options fields affect the protocol used between the ports. The SCSI target port uses the protocol options bits to indicate to the SCSI initiator port if it agrees to enable the requested protocol options. Except for the PCOMP_EN bit, the SCSI target port shall not enable any protocol options that were not enabled in the negotiation message received from the SCSI initiator port.
Page 59: Dt_Req
SCSI Interface Product Manual, Rev. B Table 18 describes the bus phases resulting from IU_REQ changes. Table 18: Bus phases resulting from IU_REQ changes Modified Initial IU_REQ BUS phase following IU_REQ value Causes MESSAGE phases a. PPR negotiation keeping IU_REQ set to zero; COMMAND, DATA, STATUS, b.
Page 60: Wr_Flow
SCSI Interface Product Manual, Rev. B 2.12.8.5 WR_FLOW The SCSI initiator port shall set WR_FLOW to one to indicate that the SCSI target port should enable write flow control during write streaming. In response, the SCSI target port shall set WR_FLOW to one if it is capable of write flow control and zero if it is not.
Page 61: Negotiable Field Combinations
SCSI Interface Product Manual, Rev. B 2.12.9 Negotiable field combinations Not all combinations of the negotiable fields are valid. Only the combinations defined in Table 19 shall be allowed. All other combinations of the listed fields are reserved. Table 19: Valid negotiable field combinations Protocol options Transfer...
Page 62: Negotiation Message Sequences
SCSI Interface Product Manual, Rev. B WDTR and SDTR may be originated by either SCSI target ports or SCSI initiator ports. Since WDTR resets all the values that SDTR sets, it shall be sent first if both are needed. SCSI target ports capable of wide transfer agreements shall originate negotiation with WDTR followed with SDTR.
Page 63: Logical Characteristics
SCSI Interface Product Manual, Rev. B Logical characteristics The operations of the SCSI bus as described in this section are supported by the drive as specified in each individual drive’s Product Manual, Volume 1. The drive always functions as the target unless otherwise stated. SCSI bus phases overview The drive responds to the following phases: BUS FREE phase...
Page 64: Expected Bus Free Phases
SCSI Interface Product Manual, Rev. B m. after a PPR (Parallel Protocol Request) negotiation in response to a selection using attention condition when information unit transfers are enabled (see Section 4.3.12); or n. after any successful negotiation that causes information unit transfers to be enabled or disabled. The target uses an unexpected bus free to inform the initiator of a protocol error.
Page 65: Qas Protocol
SCSI Interface Product Manual, Rev. B 1. If no higher priority SCSI ID bit is true on the Data Bus [DB(7) is the highest], the SCSI device has won the arbitration and the SCSI device shall assert the SEL signal. 2.
Page 66: Qas Phase Overview
SCSI Interface Product Manual, Rev. B 3.1.2.3 QAS phase overview For targets with information unit transfers and QAS enabled to indicate it wants to release the bus, the following procedure is used: 1. The target shall change to a MESSAGE IN phase, issue a single QAS Request (55h) message, and then wait for ACK to be true.
Page 67: Selection Phase
SCSI Interface Product Manual, Rev. B 6. After the QAS arbitration delay in step 4, SCSI devices with arbitration fairness enabled that are not arbi- trating shall start sampling the Data Bus to determine the SCSI devices that are attempting arbitration, the SCSI device that won, and the SCSI devices that lost.
Page 68: Selection Using Attention Condition Timeout Procedure
SCSI Interface Product Manual, Rev. B a PPR (Parallel Protocol Request) negotiation (see Section 4.3.12 in this manual). On completion of the PPR negotiation, the target shall proceed to a BUS FREE phase. If the first message received by the target during the MESSAGE OUT phase is not a task management message or a PPR message, the target shall change to a MESSAGE IN phase and issue a MESSAGE REJECT message followed by a WDTR message with TRANS- FER WIDTH EXPONENT field set to 00h.
Page 69: Selection Without Using Attention Condition Time-Out Procedure
SCSI Interface Product Manual, Rev. B 3.2.1.2.2 Selection without using attention condition time-out procedure Two optional selection time-out procedures are specified for clearing the SCSI bus if the initiator waits a mini- mum of one selection time-out delay and there has been no BSY signal response from the target: a.
Page 70: Physical Reconnection Timeout Procedure
SCSI Interface Product Manual, Rev. B only after both the BSY and SEL signals are continuously false for a minimum of one bus settle delay. For more information on glitches, see ANSI SPI-4, T10/1365D. 3.3.3 Physical reconnection timeout procedure Two optional physical reconnection timeout procedures are specified for clearing the SCSI bus during a RESE- LECTION phase if the target waits a minimum of one selection timeout delay and there has been no BSY sig- nal response from the initiator: •...
Page 71: Asynchronous Transfer
SCSI Interface Product Manual, Rev. B Table 20: Information transfer phases Signal MSG I/O Phase Direction of transfer Comment ST DATA OUT Initiator to target ST DATA Phase ST DATA IN Initiator from target DATA phase DT DATA OUT Initiator to target DT DATA phase DT DATA IN...
Page 72: Synchronous Transfer
SCSI Interface Product Manual, Rev. B 0,P_CRCA) or DB(15-0,P_CRCA,P1) signals and shall negate the REQ signal. After the REQ signal is false, the initiator shall then negate the ACK signal. After the ACK signal is false, the target may continue the transfer by driving the DB(7-0,P_CRCA) or DB(15-0,P_CRCA,P1) signals and asserting the REQ signal as described above.
Page 73: Information Unit Transfer
SCSI Interface Product Manual, Rev. B During DT data transfers, data shall be clocked on both the assertion and negation of the REQ and ACK signal lines. References to REQ/ACK transitions in this section refer to either an assertion or a negation of the REQ or ACK signal.
Page 74: Data Group Data Field Transfer
SCSI Interface Product Manual, Rev. B Detected Error message (see Section 4.3.5) or an ABORT TASK message to the target. These messages notify the target that the SPI status information unit was invalid and the message received from the initiator was a SCSI initiator port Detected Error message.
Page 75 SCSI Interface Product Manual, Rev. B If the I/O signal is true (i.e., transfer to the initiator), to transfer the data field, the target: 1. shall drive the DB(15-0) signals to their values and shall negate the P_CRCA signal; 2. shall wait at least the longer of one pCRC transmit setup time from the negation of P_CRCA or one trans- mit setup time from DB(15-0) being driven with valid data;...
Page 76 SCSI Interface Product Manual, Rev. B 11. hold the DB(15-0) signals for a minimum of one transmit hold time and hold the REQ signal asserted for a minimum of one transmit assertion period; 12. drive the DB(15-0) signals to their pCRC values; 13.
Page 77 SCSI Interface Product Manual, Rev. B Pad field data and pCRC field data are transferred using the same negotiated transfer period as the data field data. The target may continue to send REQs, up to the negotiated offset, for the next data group. The target shall not transition REQ with P_CRCA asserted until the initiator has responded with all ACK transitions for the previous data group.
Page 78: Paced Transfer
SCSI Interface Product Manual, Rev. B If the target does not retry transferring the information transfer or it exhausts its retry limit, the target shall go into a STATUS phase and send a CHECK CONDITION status with a sense key set to Aborted Command and an additional sense code set to SCSI Parity Error for the task associated with the pCRC error.
Page 79: Dt Data In Phase Training Pattern
SCSI Interface Product Manual, Rev. B training pattern to achieve deskewing. The transmitting SCSI device shall not make an intentional shift in rela- tive timing between the data bus signals and the REQ or ACK signal during the DT data phase. Note.
Page 80: Dt Data Out Phase Training Pattern
SCSI Interface Product Manual, Rev. B 4. negate ACK signal; 5. wait the equivalent of 32 transfer periods (e.g., 200 ns at Fast-160); 6. set precompensation to negotiated state; and 7. assert and negate ACK signal at the negotiated transfer period 32 time, (e.g., (2 x 6.25 ns) x 32 = 400 ns at Fast-160.
Page 81: P1 Data Valid/Invalid State Transitions
SCSI Interface Product Manual, Rev. B 3. keep the P1, DB(15-0), and ACK signals negated for the equivalent of 8 additional transfer periods; 4. simultaneously assert and negate PA and DB(15-0) signals at twice the negotiated transfer period (i.e., simultaneously repeat a 1100b bit pattern 12 times on each signal) while asserting and negating ACK at the negotiated transfer period 24 times (e.g., (2 x 6.25) x 24 = 300 ns at Fast-160);...
Page 82: Starting Pacing Transfers At End Of Training Pattern
SCSI Interface Product Manual, Rev. B 3.5.3.2.1 Starting pacing transfers at end of training pattern See Section 3.5.3.1 for the description of starting a data valid state after a training pattern. 3.5.3.2.2 Starting pacing transfers with no training pattern Before starting the DT DATA IN phase, the SCSI target port shall wait at least two system deskew delays after the SEL signal is negated before the first assertion of the REQ signal.
Page 83: Deskewing
SCSI Interface Product Manual, Rev. B • shall drive the DB(15-0) signals to their values simultaneous with the next REQ signal negation; and • shall hold the DB(15-0) signals valid for a minimum of one transmit hold time. If the I/O signal is true (i.e., transfer to the SCSI initiator port), to receive SPI information units the SCSI initiator port shall: •...
Page 84: Command Phase
SCSI Interface Product Manual, Rev. B Table 21: Wide SCSI byte order SCSI bus Data Transfer transfer number 15..8 7..0 width 8-bit 16-bit Note. When transferring consecutive bytes W, X, Y, and Z across the buses, they are transferred as shown above.
Page 85: Dt Data Out Phase
SCSI Interface Product Manual, Rev. B 3.7.3 DT DATA OUT phase The DT DATA OUT phase allows the SCSI target port to request that data be sent from the SCSI initiator device to the SCSI target device using DT data transfers. The target shall assert the MSG signal and negate the C/D and I/O signals during the REQ/ACK handshakes of this phase.
Page 86: Message In Phase Exception Condition Handling
SCSI Interface Product Manual, Rev. B 3.9.2.1 MESSAGE IN phase exception condition handling If the SCSI initiator port detects a parity error on any message byte it receives, the SCSI initiator port shall cre- ate an attention condition. When the SCSI target port switches to a MESSAGE OUT phase, the SCSI initiator port shall send a MESSAGE PARITY ERROR message (see Section 4.3.7) to the SCSI target port.
Page 87: Scsi Bus Phase Sequences
SCSI Interface Product Manual, Rev. B DB(P_CRCA), and/or DB(P1) no sooner than one system deskew delay after the detection of the negation of the I/O signal. e. The DB(P_CRCA) signal direction may switch direction while the Data Bus and/or DB(P1) does not (e.g., changing from COMMAND phase to DT DATA OUT phase).
Page 88: Phase Sequences For Selection Without Using Attention Condition With Information Unit Transfers Disabled
SCSI Interface Product Manual, Rev. B 3.11.3 Phase sequences for selection without using attention condition with information unit transfers disabled The allowable sequences for either physical reconnection or selection using attention condition while an infor- mation unit transfer agreement is not in effect shall be as shown in Figure 12. The normal progression for selection without using attention condition (see Section 3.2.1.1.2) is: 1.
Page 89: Phase Sequences For Physical Reconnection Or Selection Without Using Attention Condition With Information Unit Transfers Enabled
SCSI Interface Product Manual, Rev. B 3.11.4 Phase sequences for physical reconnection or selection without using attention condition with information unit transfers enabled The sequences for physical reconnection or selection without using attention condition while an information unit transfer agreement is in effect shall be as shown in Figure 13. The normal progression for selection without using attention condition (see Section 3.2.1.1.3) if QAS is dis- abled is: 1.
Page 90: Phase Sequences For Physical Selection Using Attention Condition With Information Unit Transfers Enabled
SCSI Interface Product Manual, Rev. B 3.11.5 Phase sequences for physical selection using attention condition with information unit transfers enabled The sequences for a selection with attention condition while an information unit transfer agreement is in effect shall be as shown in Figure 14. The normal progression for selection using attention condition (see Section 3.2.1.1.3) if QAS is disabled is: 1.
Page 91: Dt Data Bus Protection Using Crc
SCSI Interface Product Manual, Rev. B For ST DATA phases, the DB(P_CRCA) signal shall indicate odd parity for DB(7-0). If 8-bit transfers are enabled, the DB(P1) signal shall not be checked. If 16-bit data transfers are enabled, the DB(P1) signal shall indicate odd parity for DB(15-8).
Page 92 SCSI Interface Product Manual, Rev. B...
Page 93: Message System Specification
SCSI Interface Product Manual, Rev. B Message system specification SCSI protocol messages allow communication between a SCSI initiator port and a SCSI target port for the pur- pose of link management. The link management messages used for this purpose are defined within this stan- dard and their use is confined to this standard.
Page 94: One-Byte Messages
SCSI Interface Product Manual, Rev. B Message code Message format One-byte message 56–7Fh Reserved 80h–FFh One-byte message (IDENTIFY) 4.2.1 One-byte messages One-byte messages consist of a single byte transferred during a MESSAGE phase. The byte’s message code determines the message to be performed as defined in Tables 26, 39, and 44. The IDENTIFY message is a one-byte code, but its format is different.
Page 95: Link Control Messages
SCSI Interface Product Manual, Rev. B by the particular drive. In the tables, the message code values are given a direction specification (In-Out). Detailed descriptions follow the tables. Messages other than those supported by a drive are answered by the drive with a MESSAGE REJECT message.
Page 96: Disconnect
SCSI Interface Product Manual, Rev. B 4.3.2 DISCONNECT The DISCONNECT message is sent from a SCSI target port to inform an initiator that the target plans to do a physical disconnect by releasing the BSY signal, and that a later physical reconnect is going to be required in order to complete the current task.
Page 97: Ignore Wide Residue
SCSI Interface Product Manual, Rev. B may change the DISCPRIV bit, but shall not attempt to switch to another task. (See the DTDC field of the phys- ical disconnect/reconnect mode page in Section 8.12.4 for additional controls over physical disconnection.) An implied RESTORE POINTERS message shall be performed by the initiator following successful identifica- tion of the nexus during the MESSAGE IN phase of a physical reconnection or a successful receipt of a SPI L_Q information unit.
Page 98: Linked Command Complete
SCSI Interface Product Manual, Rev. B 4.3.6 LINKED COMMAND COMPLETE The LINKED COMMAND COMPLETE message is sent from a target to an initiator to indicate that a linkied command has completed and that status has been sent. The initiator shall then set the pointers to the initial state for the next linked command.
Page 99: Modify Bidirectional Data Pointer
SCSI Interface Product Manual, Rev. B Table 30: MODIFY DATA POINTER message format Byte EXTENDED MESSAGE (01 EXTENDED MESSAGE LENGTH (05 MODIFY DATA POINTER (00 (MSB) ARGUMENT (LSB) 4.3.10 MODIFY BIDIRECTIONAL DATA POINTER The MODIFY BIDIRECTIONAL DATA POINTER message (see Table 31) is sent from the target to the initiator and requests that the signed data-out argument be added using two’s complement arithmetic to the value of the current data-out pointer and signed data-in argument be added using two’s complement arithmetic to the value of the current data-in pointer.
Page 100: Parallel Protocol Request
SCSI Interface Product Manual, Rev. B 4.3.12 PARALLEL PROTOCOL REQUEST PARALLEL PROTOCOL REQUEST messages (see Table 32) are used to negotiate a synchronous data trans- fer agreement, a wide data transfer agreement, and set the protocol options between two SCSI devices. Table 32: PARALLEL PROTOCOL REQUEST message format Byte...
Page 101 SCSI Interface Product Manual, Rev. B The REQ/ACK OFFSET value is chosen to prevent overflow conditions in the port’s receive buffer and offset counter. The REQ/ACK OFFSET values and which timing values shall be selected are defined below. Value Description Timing values Specifies asynchronouse transfer agreement.
Page 102 SCSI Interface Product Manual, Rev. B A PARALLEL PROTOCOL REQUEST message exchange shall be initiated by an initiator whenever a previ- ously arranged parallel protocol agreement may have become invalid. The agreement becomes invalid after any condition that may leave the parallel protocol agreement in an indeterminate state such as: a.
Page 103: Parallel Protocol Request
SCSI Interface Product Manual, Rev. B Table 34: PARALLEL PROTOCOL REQUEST messages implied agreement Target’s Parallel Protocol Request response Implied agreement Non-zero REQ/ACK OFFSET Synchronous transfer (i.e., each SCSI device transmits data with a period equal to or greater than and a REQ/ACK OFFSET equal to or less than the negotiated values received in the target’s PPR message).
Page 104: Qas Request
SCSI Interface Product Manual, Rev. B If during the PARALLEL PROTOCOL REQUEST message the initiator creates an attention condition and the first message of the MESSAGE OUT phase is either a MESSAGE PARITY ERROR or MESSAGE REJECT message, the data transfers shall be considered to be negated by both SCSI devices. In this case, both SCSI devices shall use the eight-bit asynchronous data transfer mode with all the protocol options bits set zero to indicate ST DATA IN and ST DATA OUT phases for data transfers between the two SCSI devices.
Page 105 SCSI Interface Product Manual, Rev. B The REQ/ACK OFFSET field contains the maximum number of REQ assertions allowed to be outstanding before a corresponding ACK assertion is received at the target. The size of a data transfer may be 1 or 2 bytes depending on what values, if any, have been previously negotiated through an exchange of WIDE DATA TRANSFER REQUEST messages or PPR messages.
Page 106: Target Initiated Sdtr Negotiation
SCSI Interface Product Manual, Rev. B Responding SCSI device Parallel Protocol Request response Implied agreement Parity error (on responding Asynchronous transfer message) Unexpected bus free (as a result of Asynchronous transfer the responding message) No response Asynchronous transfer If there is an unrecoverable parity error on the initial SDTR message (see sections 3.12.2 and 3.12.3), the initi- ating SCSI device shall retain its previous data transfer mode.
Page 107: Task Complete
SCSI Interface Product Manual, Rev. B 4.3.17 TASK COMPLETE The TASK COMPLETE message is sent from a target to an initiator to indicate that a task has completed and that valid status has been sent to the initiator when information unit transfers are disabled. After successfully sending this message, the target shall go to the Bus Free phase by releasing the BSY signal.
Page 108: Target Initiated Wdtr Negotiation
SCSI Interface Product Manual, Rev. B If a SCSI device implements both wide data transfer option and synchronous data transfer option and uses the SDTR and WDTR messages, then it shall negotiate the wide data transfer agreement prior to negotiating the synchronous data transfer agreement.
Page 109: Initiator Initiated Wide Data Transfer Request (Wdtr) Negotiation
SCSI Interface Product Manual, Rev. B and both SCSI devices shall go to eight-bit data transfer mode for data transfers between the two SCSI devices. Any prior synchronous data transfer agreement shall remain intact. 4.3.18.2 Initiator initiated Wide Data Transfer Request (WDTR) negotiation If the initiator recognizes that WDTR negotiation is required, it creates an attention condition and sends a WDTR message to begin the negotiating process.
Page 110: Aca (Auto Contingent Allegiance)
SCSI Interface Product Manual, Rev. B If a target does not implement tagged queuing and a queue tag message is received, the target shall switch to a Message In phase with a MESSAGE REJECT message and accept the task as if it were untagged, provided there are no outstanding untagged tasks from that initiator.
Page 111: Head Of Queue
SCSI Interface Product Manual, Rev. B 4.4.3 HEAD OF QUEUE See Table 41 for the format of the Head of Queue message. Table 41: Head of Queue message format Byte MESSAGE CODE (21h) TAG (00h-FFh) The Head of Queue message specifies that the task shall be placed in the task set as a Head of Queue task. The rules used by the device server to handle Head of Queue tasks within a task set are defined in Section 7.0 of this manual and in the SCSI Architecture Model-2 standard.
Page 112: Task Management Messages
SCSI Interface Product Manual, Rev. B Task management messages Table 44 lists the codes used for messages that manage tasks. Details about these task management mes- sages is given in subsections following the table. 4.5.1 Task management message codes Table 44: Task management message codes Support IU Transfers...
Page 113: Abort Task Set
SCSI Interface Product Manual, Rev. B 4.5.3 ABORT TASK SET The ABORT TASK SET message is defined in the SCSI Architecture Model-2 standard. In addition to the requirements in the SCSI Architecture Model-2 standard the target shall go to the BUS FREE phase following the successful receipt of the ABORT TASK SET message.
Page 114 SCSI Interface Product Manual, Rev. B...
Page 115: Miscellaneous Scsi Bus Characteristics
SCSI Interface Product Manual, Rev. B Miscellaneous SCSI bus characteristics Asynchronous conditions can occur on the SCSI bus that cause a SCSI device to perform certain actions that may alter the phase sequence of an I/O process. Furthermore, SCSI devices may not all be powered on at the same time.
Page 116: Bus Reset Condition
SCSI Interface Product Manual, Rev. B f. If SPI (SCSI Parallel Interface) information unit transfers are disabled and an attention condition is detected during a RESELECTION phase, the SCSI target port shall enter MESSAGE OUT phase after the SCSI tar- get has sent its IDENTIFY message for that RESELECTION phase.
Page 117: Target Reset Event
SCSI Interface Product Manual, Rev. B 5.4.3 Target reset event When a SCSI device successfully receives a SCSI target port Reset message, it shall cause a reset event. In response to a SCSI target port reset event, the SCSI target shall create a unit attention condition for all SCSI initiator ports.
Page 118: Command Processing Considerations And Exception Conditions
SCSI Interface Product Manual, Rev. B 5.5.3 Saved pointers Saved pointers point to initiator storage locations where command, status and data information are stored for a task that was saved at some point in the past. There is one set of saved pointers for the current task for each target on the interface bus that is currently active (whether or not it is currently connected to the initiator).
Page 119: Incorrect Initiator Connection
SCSI Interface Product Manual, Rev. B per SCSI device basis or as a system wide option. In any case, a SCSI device conducts a survey with INQUIRY commands to be sure that the SCSI devices on the SCSI bus are appropriate destinations for SEND commands with an AER bit of one.
Page 120 SCSI Interface Product Manual, Rev. B...
Page 121: Spi Information Units
SCSI Interface Product Manual, Rev. B SPI information units An information unit transfer transfers data in SPI information units. The order in which SPI information units are transferred within an information unit transfer follows a prescribed sequence. When information unit transfers are enabled, only SPI information units shall be transferred within the DT DATA OUT phase and DT DATA IN phase.
Page 122: Figure 15. Spi Information Unit Sequence During Initial Connection
SCSI Interface Product Manual, Rev. B SELECTION DT DATA OUT SPI L_Q (always Init to Targ) (logical connect) Attention SPI COMMAND Condition (always Init to Targ) (logical disconnect) DT DATA IN MESSAGE MESSAGE FREE (to SPI L_Q/DATA [3] (physical (QAS or WDTR) disconnect) SPI L_Q/STATUS [4]) See Table 48 for the format of the SPI L_Q information unit.
Page 123: Figure 16. Spi Information Unit Sequence During Data Type Transfers
SCSI Interface Product Manual, Rev. B DT DATA IN DT DATA OUT RESELECTION (from SPI STATUS (from SPI COMMAND or SPI DATA) or SPI DATA) DT DATA IN SPI L_Q (always Targ to Init) (logical reconnect) (data pointer restored) Attention DT DATA OUT Condition DT DATA IN...
Page 124: Figure 17. Spi Information Unit Sequence During Data Stream Type Transfers
SCSI Interface Product Manual, Rev. B DT DATA IN DT DATA OUT RESELECTION (from SPI STATUS (from SPI COMMAND or SPI DATA) or SPI DATA) DT DATA IN SPI L_Q (always Targ to Init) (logical reconnect) (data pointer restored) Attention DT DATA IN Condition DT DATA OUT...
Page 125: Spi Information Units
SCSI Interface Product Manual, Rev. B RESELECTION DT DATA OUT DT DATA IN (from SPI DATA (from SPI DATA) or SPI COMMAND) DT DATA IN SPI L_Q (always Targ to Init) (logical reconnect) (data pointer Data restored) Length Attention Condition SPI STATUS (always Targ to Init) (logical disconnect)
Page 126 SCSI Interface Product Manual, Rev. B status information unit shall be reported for the task management function. If the Task Management Flags field is not a supported value, then the task manager shall terminate the task with a Good status and the packetized failure code shall be set to task management function not supported.
Page 127: Spi L_Q Information Unit
The Write Data (WRDATA) bit and Read Data (RDDATA) bit are defined in SCSI protocol standards T10/ 1144D (FCP-2), sections 9.1, 9.1.16, and 9.1.17. They are also discussed in the Seagate Fibre Channel Interface Manual, part number 77767496. These two bits are used by drives in a Fibre Channel I/O sys- tem and shall be ignored by this section.
Page 128 SCSI Interface Product Manual, Rev. B Table 48: SPI L_Q information unit Byte Type [1] Reserved Tag [2] Logical Unit Number [3] Reserved Data Length [4] BIDI Direction [5] Reserved Reserved iuCRC Interval [6] iuCRC [7] The Type field is defined in Table 49. If a SCSI initiator port receives a type code that is not defined in Table 49, that initiator shall follow the procedures defined in Section 3.5.2.2.1.1.
Page 129 SCSI Interface Product Manual, Rev. B Table 49: SPI L_Q information unit type Codes Type Description Last Sent by a SCSI initiator port device to indicate a SPI command information unit shall follow this command SPI L_Q information unit. Indicates the initiator device shall not send any more SPI command information units during the current connection.
Page 130 SCSI Interface Product Manual, Rev. B Table 50: BIDI Direction Codes Description A unidirectional command or a type code other than data or data stream (see Table 49). A bidirectional command transferring data from the SCSI initiator device to the SCSI target device.
Page 131: Spi Data Information Unit
SCSI Interface Product Manual, Rev. B 6.2.3 SPI data information unit The SPI data information unit (see Table 51) contains data. The detection of a BUS FREE phase following a SPI data information unit by a SCSI initiator port shall be equivalent to the initiator receiving a DISCONNECT message.
Page 132 SCSI Interface Product Manual, Rev. B The detection of a BUS FREE phase following a SPI data stream information unit by a SCSI initiator shall be equivalent to the initiator port receiving a DISCONNECT message. The detection of a QAS REQUEST message following a SPI data stream information nit by a SCSI initiator shall be equivalent to the initiator receiving a DISCONNECT message.
Page 133: Spi Status Information Unit
SCSI Interface Product Manual, Rev. B 6.2.5 SPI status information unit The SPI status information unit (see Table 53) contains the completion status of the task indicated by the pre- ceding SPI L_Q information unit. The target shall consider the SPI status information unit transmission to be successful when there is no attention condition on the transfer of the information unit.
Page 134 SCSI Interface Product Manual, Rev. B The Packetized Failures field (see Table 54) contains information describing the packetized failures detected during the execution of a task. The Packetized Failures field shall contain valid information if the target detects any of the conditions described by the packetized failure code (see Table 55). Table 54: Packetized Failures field Byte...
Page 135: Scsi Commands
For all commands, if there is an invalid parameter in the Command Descriptor Block, the drive shall terminate the command without altering the medium. The format description for the Command Descriptor Block as supported by Seagate drives is shown in tables 56, 57, 58, 59, and 60.
Page 136: Fixed And Variable Length Command Descriptor Block Formats
SCSI Interface Product Manual, Rev. B 7.2.1 Fixed and variable length Command Descriptor Block formats For all commands, if there is an invalid parameter in the command descriptor block, the device server termi- nates the command without altering the medium. Table 56 shows the typical format of a 6-byte CDB.
Page 137 SCSI Interface Product Manual, Rev. B Table 58: Typical CDB for 12-byte commands Byte Operation Code [1] Reserved Service Action (if required) [2] (MSB) Logical Block Address (if required) [3] (LSB) (MSB) Transfer Length (If required) [4] Parameter List Length (if required) [5] Allocation Length (if required) [6] (LSB) Reserved...
Page 138 SCSI Interface Product Manual, Rev. B Table 60: Typical variable length CDB Byte Operation Code (7Fh) [1] Control [7] Reserved Reserved Reserved Encryption Identification [8] Reserved Additional CDB Length (n–7) [9] (MSB) Service Action [2] (LSB) Service Action specific fields [10] Notes for Tables 56, 57, 58, 59, and 60.
Page 139 SCSI Interface Product Manual, Rev. B The Transfer Length of the commands that are used to send a list of parameters to a drive is called the Parameter List Length. The Parameter List Length specifies the number of bytes sent during the DATA OUT phase.
Page 140 SCSI Interface Product Manual, Rev. B Obsolete bit. Bit 0 provides an obsolete way to request interrupts between linked commands. If bit 0 is equal to one, device servers not implementing the obsolete capability (Link bit was formerly in this bit position and Flag bit was in bit 1 position) terminate the command with CHECK CONDITION sta- tus and the sense key shall be set to ILLEGAL REQUEST.
Page 141: Status
SCSI Interface Product Manual, Rev. B Status A Status byte shall be sent from the target to the initiator during the STATUS phase at the termination of each command as specified in Tables 62 and 63 unless the command is cleared by one of the following conditions: 1.
Page 142: Status Precedence
SCSI Interface Product Manual, Rev. B Intermediate–Condition Met. This status is returned whenever the operation requested by a linked command is satisfied (see the PREFETCH commands in ANSI SCSI Block Commands-2, T10/1417D), unless the com- mand is terminated with Check Condition, Reservation Conflict, Task Set Full, Busy status. If Intermediate or Intermediate-Condition Met status is not returned, the series of linked commands is terminated and the task is ended.
Page 143: Command Examples
SCSI Interface Product Manual, Rev. B Command examples 7.4.1 Single command example A typical operation on the SCSI bus is likely to include a single Read command to a peripheral device such as the drive. This operation is described in detail starting with a request from the initiator. This example assumes that no linked commands and no malfunctions or errors occur and is illustrated in Figure 19.
Page 144: Disconnect Example
SCSI Interface Product Manual, Rev. B 7.4.2 Disconnect example In the single command example, the length of time necessary to obtain the data may require a time consuming physical seek. In order to improve system throughput, the drive may disconnect from the initiator, freeing the SCSI bus to allow other requests to be sent to other SCSI devices.
Page 145: Timing Examples
SCSI Interface Product Manual, Rev. B Timing examples Times (T00 through T35) necessary to define performance are listed in the individual drive’s Product Manual, Volume 1, in the “Disc drive SCSI timing” section. For timing waveforms to define these times, refer to the SCSI Parallel Interface-4 specification (SPI-4).
Page 146: Clearing An Auto Contingent Allegiance Condition
SCSI Interface Product Manual, Rev. B or CA condition shall be completed with a status of ACA Active (if NACA=1 in the new command’s CDB Control byte, see Section 7.2.1, note [7], Table 61) or Busy (if NACA=0). If TST=001b, tasks created by one initiator shall not be rejected based on an ACA or CA condition in effect for another initiator.
Page 147: Sense Data
SCSI Interface Product Manual, Rev. B command with CHECK CONDITION status. Sense data shall be set to the values specified for the REQUEST SENSE command in item b below; b. The target supports the logical unit, but the peripheral device is not currently attached to the target. In response to an INQUIRY command the target shall return the INQUIRY data with the peripheral qualifier set to the value required in the SPC-2 standard.
Page 148: Unexpected Reselection Phase
SCSI Interface Product Manual, Rev. B An error condition or unit attention condition shall be reported to a specific initiator once per occurrence of the event causing it. The logical unit may choose to use an asynchronous event report or to return CHECK CONDI- TION status on a subsequent command, but not both.
Page 149: Target Hard Reset
The version or level of microcode has changed. m. The logical unit inventory has been changed (not generally applicable to Seagate disc drives); or n. A change in the condition of a synchronized spindle occurred (not generally applicable to Seagate disc drives).
Page 150: Queued Tasks (Formerly "Queued I/O Processes")
SCSI Interface Product Manual, Rev. B 4. Return the device’s operating mode to the appropriate initial conditions, similar to those conditions that would be found following device power-on. The Mode Select conditions (see SCSI Primary Commands-2 SPC-2, T10/1236D) shall be restored to their saved values if saved values have been established. Mode Select conditions for which no saved values have been established shall be returned to their default values;...
Page 151: Parameter Rounding
SCSI Interface Product Manual, Rev. B regardless of initiator, are executed before that command with the Ordered Task Queue Tag message. All com- mands received with a Simple Task Queue Tag message after a command received with an Ordered Task Queue Tag message, regardless of initiator, are executed after that command with the Ordered Task Queue Tag message.
Page 152: Incorrect Initiator Connection
In some vendor-specific cases, it may also be necessary to perform other commands including Mode Sense and READ CAPACITY. The more recent Seagate drives do not support the Change Operating Definition command (see individual drive’s Product Manual, Volume 1). Each logical unit begins at a particular operating definition. If the logical unit supports the CHANGE DEFINI- TION command, the present operating definition can be changed to any other operating definition supported by the logical unit.
Page 153: Command Descriptions
Two types of commands are supported by the drive: commands for all devices; and commands for direct access devices. The individual Product Manuals for each Seagate model drive list the Commands and param- eter pages that the particular drive supports. Some commands are not supported by any Seagate devices.
Page 154 SCSI Interface Product Manual, Rev. B Table 64. Commands sorted by command name (continued) Command type Length Command Direct operation access Command name code devices devices bytes bytes bytes Variable Reference RECEIVE DIAGNOSTIC 8.32 (see page 273) RESULTS REGENERATE 8.33 (see page 277) RELEASE (6) 8.34 (see page 279) RELEASE (10)
Page 155 SCSI Interface Product Manual, Rev. B Table 65. Commands sorted by operation code Command type Length Command Direct operation access code Command name devices devices bytes bytes bytes Variable Reference TEST UNIT READY 8.53 (see page 311) REZERO UNIT 8.41 (see page 299) REQUEST SENSE 8.38 (see page 285) FORMAT UNIT...
Page 156 SCSI Interface Product Manual, Rev. B Table 65. Commands sorted by operation code (continued) Command type Length Command Direct operation access code Command name devices devices bytes bytes bytes Variable Reference WRITE LONG 8.59 (see page 321) CHANGE DEFINITION 8.1 (see page 139) WRITE SAME 8.60 (see page 322) LOG SELECT...
Page 157: Change Definition Command (40H)
SCSI Interface Product Manual, Rev. B CHANGE DEFINITION command (40h) Note. The CHANGE DEFINITION command is an obsolete command implemented only by SCSI-1/SCSI-2 devices. The CHANGE DEFINITION command (Table 66) modifies the operating definition of the drive with respect to commands from all initiators.
Page 158: Compare Command (39H)
SCSI Interface Product Manual, Rev. B Use of the Control byte by the drive is a customer unique option. See Table 61, “CONTROL field,” in Sec- tion 7.2.1. The operating definition is modified after successful completion of the command. The drive shall consider the command successfully completed when it detects the assertion of the ACK signal for the COMMAND COM- PLETE message.
Page 159: Format Unit Command (04H)
SCSI Interface Product Manual, Rev. B FORMAT UNIT command (04h) The FORMAT UNIT command (Table 68) ensures that the medium is formatted so all of the user addressable data blocks can be accessed. There is no guarantee that the medium has or has not been altered. In addition, the medium may be certified and control structures may be created for the management of the medium and defects.
Page 160: Format Unit Parameter Definition
Primary Defect (P type) flawed sectors are identified at the time of shipment in a list of defects (permanent flaws) supplied by Seagate and stored on the disc in an area that is not directly accessible by the user. (This list may be referred to as an ETF List.) This defect list is not modified or changed by the drive (or ini- tiator) after shipment.
Page 161 SCSI Interface Product Manual, Rev. B Table 69: FORMAT UNIT parameter definition (format variations) CDB-Byte (see Table 68) DATA LIST Defect List Format Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Comments Default format: No DATA OUT phase occurs. Drive reallocates all sectors in the P list plus any sector which fails the Format Verify phase (C type flaws).
Page 162: Format Unit Parameter List
Disable Primary (DPRY). If one, flaws in the drive P list are not reallocated during formatting. This means existing reallocations of the P list are canceled and no new reallocations made during formatting. The P list is retained. Some Seagate drives do not support a DPRY bit of one. See individual drive’s Product Manual, Volume 1.
Page 163: Initialization Pattern Descriptor
SCSI Interface Product Manual, Rev. B The initialization pattern type field indicates the type of pattern the target shall use to initialize each logical block within the initiator accessible portion of the medium (Table 74). All bytes within a logical block shall be written with the initialization pattern.
Page 164: Defect List Formats
This section describes the format of the defect list that follows the Defect List Header described in Table 71. Three formats are possible: • Block format (Seagate drives do not support the block format, except as a customer special) • Bytes from Index format (see Table 76) •...
Page 165 SCSI Interface Product Manual, Rev. B The Defect Descriptors shall be in ascending order. The drive may return CHECK CONDITION if the defect descriptors are not in ascending order. For determining ascending order, the CYLINDER NUMBER OF DEFECT is considered the most significant part of the address and the DEFECT BYTES FROM INDEX is con- sidered the least significant part of the address.
Page 166: Inquiry Command (12H)
SCSI Interface Product Manual, Rev. B INQUIRY command (12h) The INQUIRY command requests that information regarding parameters of the target and a component logical unit be sent to the application client. Options allow the application client to request additional information about the target and logical unit or information about SCSI commands supported by the device server (see Section 8.6.3).
Page 167 SCSI Interface Product Manual, Rev. B If an INQUIRY command is received from a SCSI initiator port with a pending unit attention condition (i.e., before the device server reports CHECK CONDITION status), the device server shall perform the INQUIRY command and shall not clear the UNIT ATTENTION condition (see SAM-2, T10/1157D). The INQUIRY data should be returned even though the device server is not ready for other commands.
Page 168: Drive Standard Inquiry Data
SCSI Interface Product Manual, Rev. B 8.6.1 Drive standard INQUIRY data The drive standard INQUIRY data contains 36 required bytes, followed by a number of bytes of drive specific data that is drive dependent (see individual drive’s Product Manual, Volume 1). The standard INQUIRY data is given in Table 79.
Page 169 SCSI Interface Product Manual, Rev. B The PERIPHERAL QUALIFIER and PERIPHERAL DEVICE TYPE fields identify the device currently con- nected to the logical unit. If the target is not capable of supporting a device on this logical unit, the device server shall set this field to 7Fh (PERIPHERAL QUALIFIER set to 011b and PERIPHERAL DEVICE TYPE set to 1Fh).
Page 170 SCSI Interface Product Manual, Rev. B Table 82: ANSI-approved version Code Description The device does not claim conformance to any standard The device complies to ANSI X3.131:1994 (SCSI-2) The device complies to ANSI X3.131:199 The device complies to ANSI T10/1236 The device complies to ISO/IEC 9316-1995 The device complies to ISO/IEC 9316-1995 and to ANSI X3.131:1994 (SCSI-2) The device complies to ISO/IEC 9316-1995 and to ANSI X3.131:1997...
Page 171 SCSI Interface Product Manual, Rev. B device supports, for this logical unit, the basic task management model defined by ANSI document SCSI Architecture Model-2 (SAM-2), T10/1157. [11] An Enclosure Services (ENCSERV) bit of one indicates that the device contains an embedded enclosure services component.
Page 172 [34] IUS. Information Unit Supported. [35] Copyright Notice field. This field contains 48 bytes of ASCII data “Copyright (c) XXXX Seagate All rights reserved,” where “XXXX” indicated the current year. [36] VERSION DESCRIPTOR 2 through 8 (bytes 60-71). The VERSION DESCRIPTOR fields provide for iden- tifying up to eight standards to which the device claims conformance.
Page 173: Scsi Parallel Interface (Spi) Specific Inquiry Data
This section describes the vital product data page structure and the vital product data pages that are applicable to Seagate devices. These pages are optionally returned by the INQUIRY command and contain specific prod- uct information about the drive. The vital product data includes vendor identification, product identification, unit serial numbers, device operating definitions, manufacturing data, field replaceable unit information, and other vendor-specific information.
Page 174: Command Support Data
SCSI Interface Product Manual, Rev. B Note. The device server should have the ability to execute the INQUIRY command even when an error occurs that prohibits normal command execution. In such a case, CHECK CONDITION status should be returned for commands other than INQUIRY or REQUEST SENSE. The sense data returned may contain the field replaceable unit code.
Page 175 SCSI Interface Product Manual, Rev. B Table 88 defines the values and meanings of the SUPPORT field. Table 88: Support values and meanings Support Description 000b Data about the requested SCSI operation is not currently available. 001b The device server does not support the tested SCSI operation code. All data after byte 1 is undefined.
Page 176: Vital Product Data Parameters
SCSI Interface Product Manual, Rev. B 8.6.5 Vital product data parameters This section describes the optional vital product data page structure and the vital product data pages (see Table 89) that are applicable to all SCSI devices. These pages are optionally returned by the INQUIRY com- mand and contain vendor-specific product information about a SCSI target port or logical unit.
Page 177: Ascii Information Page
SCSI Interface Product Manual, Rev. B The PAGE LENGTH field specifies the length of the following page data. If the ALLOCATION LENGTH is less than the length of the data to be returned, the page length shall not be adjusted to reflect the trunca- tion.
Page 178: Device Identification Page
SCSI Interface Product Manual, Rev. B 8.6.5.3 Device Identification page The Device Identification page (see Table 92) provides the means to retrieve zero or more identification descriptors applying to the logical unit. Logical units may have more than one identification descriptor (e.g., if several types or associations of identifier are supported).
Page 179 SCSI Interface Product Manual, Rev. B Each IDENTIFICATION DESCRIPTOR (see Table 93) contains information identifying the logical unit, physical device, or access path used by the command and returned parameter data. Table 93. Identification Descriptor Byte Reserved CODE SET [a] Reserved Association [b] Identifier Type [c]...
Page 180 SCSI Interface Product Manual, Rev. B [c] The Identifier Type field specifies the format and assignment authority for the identifier, as described in tables 96 and 97. Table 96: Identifier Type Value Description No assignment authority was used and consequently there is no guarantee that the identifier is glo- bally unique (i.e., the identifier is vendor-specific).
Page 181: Supported Vital Product Data
1 see Table 96). 4. Byte 42 is the beginning of the Identification Descriptor for the EUI-64 identifier (Identifier type 2, see Table 96). 5. For Seagate devices, this will say “Seagate.” 8.6.5.4 Supported Vital Product Data pages This section contains a list of the vital product data page codes supported by the target or logical unit (see Table 99).
Page 182: Unit Serial Number Page
SCSI Interface Product Manual, Rev. B 8.6.5.5 Unit Serial Number page This page provides a product serial number for the target or logical unit. See Table 100 following. Table 100: Unit Serial Number page (80h) Byte PERIPHERAL QUALIFIER [1] PERIPHERAL DEVICE TYPE [1] PAGE CODE (80h) Reserved PAGE LENGTH [2]...
Page 183 SCSI Interface Product Manual, Rev. B The PAGE LENGTH field specifies the length of the product firmware numbers. If the ALLOCATION LENGTH is too small to transfer all of the page, the page length shall not be adjusted to reflect the trunca- tion.
Page 184 SCSI Interface Product Manual, Rev. B Table 102: Firmware Numbers page (C0h) (Applies to model families [5][9] other than those covered by Table 101) Byte PERIPHERAL QUALI- PERIPHERAL DEVICE TYPE [1] FIER [1] PAGE CODE (C0h) [2] PAGE LENGTH [3] SCSI FIRMWARE RELEASE NUMBER [4] SERVO FIRMWARE RELEASE NUMBER [4] SAP BLOCK POINT NUMBERS (MAJOR/MINOR) [4]...
Page 185: Date Code Page (C1H)
SCSI Interface Product Manual, Rev. B Servo Adaptive Parameters (SAP) are created independently from the servo firmware. Thus, they have their own release information. The SAP Firmware Release Number field contains ASCII data. The SAP MANUFACTURING KEY field contains a binary code used by manufacturing to identify the SAP. The high order word of the SERVO FIRMWARE PRODUCT FAMILY and PRODUCT FAMILY MEMBER IDs field contains a binary code which corresponds to the Servo Firmware Family ID.
Page 186: Jumper Settings Page (C2H)
SCSI Interface Product Manual, Rev. B 8.6.8 Jumper Settings page (C2h) Table 104: Jumper Settings page (C2h) Byte PERIPHERAL QUALIFIER [1] PERIPHERAL DEVICE TYPE [1] PAGE CODE (C2h) [2] PAGE LENGTH (02h) [3] DS [4] MS [5] WP [6] PE [7] DRIVE ID [8] TERM Reserved...
Page 187 SCSI Interface Product Manual, Rev. B The Drive ID is shown below in the table. Bit 3 is the most significant bit and bit 0 is the least significant bit. Bit 3 Bit 2 Bit 1 Bit 0 Drive ID Terminator Enable (TE).
Page 188: Device Behavior Page (C3H)
SCSI Interface Product Manual, Rev. B 8.6.9 Device Behavior page (C3h) The Device Behavior page (Table 105) will be used by the regression tests to determine what behavior should be expected from a particular firmware package. Table 105: Device Behavior page (C3h) Byte PERIPHERAL QUALIFIER [1] PERIPHERAL DEVICE TYPE [1]...
Page 189: Log Select Command (4Ch)
SCSI Interface Product Manual, Rev. B LOG SELECT command (4Ch) The LOG SELECT command provides a means for an application client to manage statistical information main- tained by the device about the device or its logical units. This information is logged within the drive and can be sent to the initiator in response to a LOG SENSE command from the initiator.
Page 190 SCSI Interface Product Manual, Rev. B that parameters shall not be saved. Log Parameters are also saved after each thermal calibration if the TSD bit in the Log Parameter pages (see Table 111) is zero. It is not an error to set the SP bit to one and to set the DS bit of a LOG PARAMETER to one. In this case, the parameter value for that LOG PARAMETER is not saved.
Page 191: Log Sense Command (4Dh)
SCSI Interface Product Manual, Rev. B LOG SENSE command (4Dh) The LOG SENSE command provides a means for a SCSI initiator port to retrieve statistical information main- tained by the drive about the drive operation. It is a complementary command to the LOG SELECT command. This information is stored in logs (counters) in the drive and is sent to the initiator in the DATA IN phase of the LOG SENSE command.
Page 192 SCSI Interface Product Manual, Rev. B Table 109 (PAGE CODE 00h) returns the list of log pages that the drive supports. Table 109: Supported Log pages Byte Reserved PAGE CODE (00h) Reserved (MSB) PAGE LENGTH (n–3) [a] (LSB) SUPPORTED PAGE LIST [b] [a] The PAGE LENGTH field specifies the length in bytes of the following SUPPORTED PAGE LIST.
Page 193 SCSI Interface Product Manual, Rev. B The LOG SENSE command and its DATA IN phase use the format of Table 110. Explanations pertaining to the table apply generally to both LOG SELECT and LOG SENSE commands, with differences noted. However, only one log page at a time is returned with each LOG SENSE command (see Section 8.9).
Page 194 SCSI Interface Product Manual, Rev. B Disable Update (DU). For the LOG SELECT command, this applies only to the cumulative LOG PARAME- TER values (indicated by 01 in the PC field of the LOG SELECT and LOG SENSE command descriptor block).
Page 195 SCSI Interface Product Manual, Rev. B Data counters are associated with one or more events. The data counter is updated whenever one of these events occurs by incrementing the counter value, provided the DU bit is zero. See note [2] for this table.
Page 196 SCSI Interface Product Manual, Rev. B The page code assignments for the log pages are listed in Table 113. Detailed descriptions follow the table. Table 113: Log Page codes Page Code Description Section Page Application Client page 8.9.1 Buffer Over-run/Under-run page 8.9.2 Cache Statistics page 8.9.3...
Page 197: Application Client Page (0Fh)
SCSI Interface Product Manual, Rev. B 8.9.1 Application Client page (0Fh) The Application Client page (Table 114) provides a place for application clients to store system information. The page code for the application client page is 0Fh. Table 114. Application Client page Byte PAGE CODE (0Fh) [1] Reserved...
Page 198: Buffer Over-Run/Under-Run Page (01H)
SCSI Interface Product Manual, Rev. B [d] The state of the LOG PARAMETER control bits ([4] through[10]) for parameters 0000h through 0FFFh is specified in Table 116. Table 116: Parameter control bits for general usage parameters (0000h through 0FFFh) Value Description Value provided by applications client Device server supports saving of parameter...
Page 199: Cache Statistics Page (37H)
SCSI Interface Product Manual, Rev. B The CAUSE field indicates the reason that the over-run occurred. Table 119: Cause field definition Cause Description Undefined Bus busy Transfer rate to slow 3h - Fh Reserved The TYPE field indicates whether the counter records under-runs or over-runs. A value of zero specifies a buffer under-run condition and a value of one specifies a buffer over-run condition.
Page 200: Error Counter
SCSI Interface Product Manual, Rev. B 8.9.4 Error Counter pages (Write, Read, Read Reverse, and Verify, 02h, 03h, 04h, and 05h) This clause defines the optional error counter pages for write errors (page code 02h), read errors (page code 03h), read reverse errors (page code 04h) and verify errors (page code 05h). The log page format is defined near the beginning of 8.9.1.
Page 201: Factory Log Page (3Eh)
SCSI Interface Product Manual, Rev. B 8.9.5 Factory Log page (3Eh) Log page code 3Eh specifies factory status parameters. Table 122: Factory Log page (3Eh) Byte PARAMETER CODE [1] [2] PARAMETER CODE 0000h–Power-on Time. This parameter code represents the number of drive power- on minutes.
Page 202 SCSI Interface Product Manual, Rev. B first self-test log parameter; results from the second most recent self-test shall be reported in the second self- test log parameter; etc. If fewer than twenty self-tests have occurred, the unused self-test log parameter entries shall be zero filled.
Page 203 SCSI Interface Product Manual, Rev. B [b] The values of the LOG PARAMETER control bits [2] through [8] for self-test results log parameters is specified in Table 126. Table 126: Parameter control bits for self-test results log parameters Value Description Value provided by device server Device server supports saving of parameter Device server manages saving of parameter...
Page 204: Start-Stop Cycle Counter Page (0Eh)
SCSI Interface Product Manual, Rev. B [i] The SENSE KEY, ADDITIONAL SENSE CODE, and ADDITIONAL SENSE CODE QUALIFIER fields may contain a hierarchy of additional information relating to error or exception conditions that occurred during the self-test represented in the same format used by the sense data (see REQUEST SENSE command).
Page 205 SCSI Interface Product Manual, Rev. B The state of the PARAMETER CONTROL bits for parameter 0001h is specified in Table 129. Table 129: Parameter control bits for date of manufacture parameters (0001h) Value Description Value provided by device server Device server does not support saving of parameter Device server manages saving of parameter No threshold comparison is made on this value ignored when ETC is 0...
Page 206: Supported Log Pages (00H)
SCSI Interface Product Manual, Rev. B storage devices, a single start-stop cycle is defined as an operational cycle that begins with the disk spin- dle at rest, continues while the disk accelerates to its normal operational rotational rate, continues during the entire period the disk is rotating, continues as the disk decelerates toward a resting state, and ends when the disk is no longer rotating.
Page 207: Temperature Page (0Dh)
SCSI Interface Product Manual, Rev. B 8.9.12 Temperature page (0Dh) This clause defines the optional temperature log page (page code 0Dh). A device that implements the temper- ature page shall implement parameter 0000h. Parameter 0001h is optional and may be either omitted or set to a value indicating that the parameter is not defined.
Page 208 SCSI Interface Product Manual, Rev. B manufacturer of the device. The reference temperature may change for vendor-specific reasons. The state of the parameter control bits for parameter 0001h is specified in Table 134 also.
Page 209: Mode Select (6) Command (15H)
SCSI Interface Product Manual, Rev. B 8.10 MODE SELECT (6) command (15h) The MODE SELECT (6) command (Table 135) provides a means for the initiator to specify medium, logical unit, or peripheral device parameters to the drive. The drive also implements the MODE SENSE command (see Section 8.12.1).
Page 210 SCSI Interface Product Manual, Rev. B command. (The host shall not be penalized by values not changeable by the host which have a SCSI target port “ripple change” as a result of this MODE SELECT.) b. If the initiator attempts to send an unsupported value or a nonzero value to a reserved field in the MODE SELECT header, block descriptor, or any page header.
Page 211 SCSI Interface Product Manual, Rev. B Table 136: MODE SELECT parameter list Byte Reserved MEDIUM TYPE [1] Reserved BLOCK DESCRIPTOR LENGTH (either 0 or 8 decimal) [2] Block Descriptor DENSITY CODE or NUMBER OF BLOCKS (MSB) [3] [4] NUMBER OF BLOCKS (MSB) [3] [4] NUMBER OF BLOCKS [4] NUMBER OF BLOCKS (LSB) [4] BLOCK LENGTH (MSB) [5]...
Page 212: Mode Select
SCSI Interface Product Manual, Rev. B 8.10.2 MODE SELECT page descriptors The rest of the MODE SELECT parameters are organized into pages that group the parameters by function. The parameter definitions are the same as those described in the MODE SENSE command (Section 8.12) and are not repeated here.
Page 213: Mode Select (10) Command (55H)
SCSI Interface Product Manual, Rev. B 8.11 MODE SELECT (10) command (55h) The MODE SELECT (10) command provides a means for the initiator to send a list of drive operating mode parameters to the drive. Initiators should issue MODE SENSE prior to MODE SELECT to determine supported pages, page lengths, and other parameters.
Page 214 SCSI Interface Product Manual, Rev. B d. If the initiator attempts to send a value for a changeable parameter that is outside the range supported by the target and rounding is not implemented for that parameter (see note [7] of Table 145). e.
Page 215 SCSI Interface Product Manual, Rev. B b. If the drive supports capacity programming (see note [4]), byte 0 is useable as MSB part of the number in bytes 1, 2, and 3. For drives whose capacity does not require the use of byte 0, byte 0 will always be 00h.
Page 216: Mode Sense (6) Command (1Ah)
A Disable Block Descriptors (DBD) bit of zero indicates that the drive may return zero or more block descriptors in the returned MODE SENSE data, at the drive’s discretion. Seagate SCSI-2 products return one block descriptor if the DBD bit is zero. A DBD bit of one specifies that the drive shall not return any block descriptors in the returned MODE SENSE data.
Page 217 SCSI Interface Product Manual, Rev. B Page Codes that may be supported by the drive are summarized here (see individual drive’s Product Man- ual, Volume 1): Page Code Description REUNIT ATTENTION Page parameters (returned last of the pages) Error Recovery parameters Disconnect/Reconnect Control parameters Format parameters Rigid Drive Geometry parameters...
Page 218 SCSI Interface Product Manual, Rev. B Table 143: MODE SENSE Data Byte SENSE DATA LENGTH [1] MEDIUM TYPE [2] DPO-FUA WP [3] Reserved Reserved BLOCK DESCRIPTOR LENGTH (8 decimal) [4] Block Descriptor Data DENSITY CODE (MSB) [5] [6] NUMBER OF BLOCKS (MSB) [6] NUMBER OF BLOCKS [6] NUMBER OF BLOCKS (LSB) [6] Reserved...
Page 219: Mode Sense Page Descriptor Header
SCSI Interface Product Manual, Rev. B the Format command. The usual valid values are 256 through 4096. Some drive products can format down to 180 bytes per sector. Some products can only format an even numbered value of bytes per sector (180-4096).
Page 220: Reunit Attention Parameters Page (00H)
SCSI Interface Product Manual, Rev. B 8.12.2 REUNIT ATTENTION Parameters page (00h) The REUNIT ATTENTION Parameters page is the last page to be reported by the drive. Table 145: REUNIT ATTENTION Parameters page (00h) Byte PS [12] PAGE CODE (00h) PAGE LENGTH (in bytes) [1] INQUIRY UNIT...
Page 221 Caching Page (08h) Length from 12h to 0Ah. [10] These bits are reserved for future compatibility with Seagate host adapters. Though they presently may be changeable, (see note [9]) these bits do not control anything, unless the individual drive’s Product Manual, Volume 1, indicates that they do and defines their use in the MODE SENSE Data section.
Page 222: Error Recovery Page (01H)
SCSI Interface Product Manual, Rev. B 8.12.3 Error Recovery page (01h) The drive Error Recovery page implementation is defined in Table 146. This table summarizes the function, the default value, and changeability status for each byte/bit. Table 146: Error Recovery page (01h) Byte Page Descriptor Header PS [1]...
Page 223 SCSI Interface Product Manual, Rev. B from the medium). The valid data is placed in the reallocated block. This function doesn’t apply to the FORMAT UNIT command. When set to zero, the drive shall not perform automatic reallocation but shall create CHECK CONDITION status with sense key of Medium Error instead.
Page 224 SCSI Interface Product Manual, Rev. B [16] The RECOVERY TIME LIMIT field (bytes 10 and 11) specifies the maximum time in milliseconds that the host allows the drive to spend in error recovery efforts during the execution of a command. The READ and WRITE RETRY count can also be set to limit the amount of time the drive spends in error recovery of indi- vidual LBAs.
Page 225: Disconnect/Reconnect Control Page (02H)
SCSI Interface Product Manual, Rev. B 8.12.4 Disconnect/Reconnect Control page (02h) The Disconnect/Reconnect mode page provides the applications client the means to tune the performance of the SCSI parallel interface. The Disconnect/Reconnect page implementation is defined in Table 147. This table summarizes the function and defines the default value and changeable status.
Page 226 The sense key shall be set to ILLEGAL REQUEST and the additional sense code set to Illegal Field In Parameter List. Not all Seagate drive models implement this field. See individual drive’s Product Manual, Volume 1, which indicates if a particular drive implements the DTDC function.
Page 227 CONNECT message sequence may want to use the Disconnect Immediate feature. However, not all Seagate drive models implement this feature. See individual drive’s Product Manual, Volume 1. [13] The Fair Arbitration field indicates whether the target should use fair or unfair arbitration when requesting an interconnect tenancy.
Page 228: Format Parameters Page (03H)
SCSI Interface Product Manual, Rev. B 8.12.5 Format Parameters page (03h) The Format Parameters page implementation is defined in Table 148. This table summarizes the function and defines the default or changeability status for each bit. The actual implementation of reserving spare areas for defect management takes place during the FORMAT UNIT command.
Page 229 SCSI Interface Product Manual, Rev. B The only time this page of parameters may be sent is immediately before sending a FORMAT UNIT com- mand to the drive. The Current parameters for this page are updated immediately but any changes between these Current parameters and the existing media format are not in effect until after the FORMAT UNIT command is completed.
Page 230: Rigid Drive Geometry Parameters Page (04H)
SCSI Interface Product Manual, Rev. B 8.12.6 Rigid Drive Geometry Parameters page (04h) The Rigid Drive Geometry Parameters page implementation is defined in Table 149. This table summarizes the function and defines the default value Table 149. Rigid Drive Geometry Parameters page (04h) Byte Page Descriptor Header PS [1]...
Page 231 SCSI Interface Product Manual, Rev. B Table 149. Rigid Drive Geometry Parameters page (04h) (continued) Byte (MSB) MEDIUM ROTATION RATE [7] (LSB) Changeable [8] Default Reserved Changeable [8] Default Reserved Changeable [8] The Parameter Savable (PS) bit of 1 indicates that page 04 parameter data is savable and is saved when a Format Function is performed.
Page 232: Verify Error Recovery Page (07H)
SCSI Interface Product Manual, Rev. B 8.12.7 Verify Error Recovery page (07h) The Verify Error Recovery page (Table 150) specifies the error recovery parameters the target shall use during the VERIFY command and the verify operation of the WRITE AND VERIFY command. Table 150: Verify Error Recovery page (07h) Byte...
Page 233 SCSI Interface Product Manual, Rev. B The Parameter Savable (PS) bit is used only with the MODE SENSE command. This bit is reserved with the MODE SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor-specific location.
Page 234: Caching Parameters Page (08H)
See individual drive’s Product Manual, Volume 1, section showing changeable values. When the Initiator Control (IC) enable bit is set to one, adaptive read look-ahead (ARLA) is disabled. When IC is set to zero, ARLA is enabled. Since Seagate drives covered by this manual never organize the...
Page 235 The Size Enable (SIZE) bit, when set to one, indicates that the Cache Segment Size is to be used to con- trol caching segmentation. When SIZE equals zero, the Initiator requests that the Number of Cache Seg- ments is to be used to control caching segmentation. For Seagate drives covered by this manual, SIZE is always zero.
Page 236 SCSI Interface Product Manual, Rev. B [17] The Force Sequential Write (FSW) bit, when set to one, indicates that multiple block writes are to be trans- ferred over the SCSI bus and written to the media in an ascending, sequential, logical block order. When the FSW bit equals zero, the target is allowed to reorder the sequence of writing addressed logical blocks in order to achieve a faster command completion.
Page 237: Control Mode Page (0Ah)
SCSI Interface Product Manual, Rev. B 8.12.9 Control Mode page (0Ah) The MODE SENSE/MODE SELECT Control Mode page (Table 152) provides controls over several SCSI fea- tures which are applicable to all device types such as tagged queuing, extended contingent allegiance, asyn- chronous event notification, and error logging.
Page 238 SCSI Interface Product Manual, Rev. B A Task Set Type (TST) field specifies the type of task set (see Table 153). If the device maintains mode pages per initiator, the TST field, if changeable, shall reflect in all initiator pages the state selected by the most recent MODE SELECT.
Page 239 SCSI Interface Product Manual, Rev. B additional sense code to Write Protected. When SWP is one and the device model defines a write protect (WP) bit in the DEVICE-SPECIFIC PARAMETER field in the mode parameter header (see Table 143), the WP bit shall be set to one for subsequent MODE SENSE commands.
Page 240: Notch Page (0Ch)
SCSI Interface Product Manual, Rev. B 8.12.10 Notch page (0Ch) The Notch page (Table 156) contains parameters for direct access devices that implement a variable number of blocks per cylinder and support this page. Each section of the drive with a different number of blocks per cylin- der is referred to as a notch.
Page 241 SCSI Interface Product Manual, Rev. B ber of notches. An active notch value of zero indicates that this and subsequent MODE SELECT and MODE SENSE commands refer to the parameters that apply across all notches. The STARTING BOUNDARY field indicates the beginning of the active notch or, if the active notch is zero, the beginning boundary of the drive.
Page 242: Power Condition Page (0Dh Or 1Ah)
SCSI Interface Product Manual, Rev. B 8.12.11 Power Condition page (0Dh or 1Ah [5]) The Power Condition page provides the initiator the means to control the length of time a logical unit will delay before changing its power requirements. There is no notification to the initiator that a logical unit has entered into one of the power conditions.
Page 243: Xor Control Mode Page (10H)
SCSI Interface Product Manual, Rev. B 8.12.12 Xor Control Mode page (10h) The Xor Control Mode page (Table 158) provides the initiator with the means to obtain or modify certain Xor operating parameters of the target. Table 158: Xor Control Mode page (10h) Byte Reserved PAGE CODE (10h)
Page 244 SCSI Interface Product Manual, Rev. B See individual drive’s Product Manual, Volume 1, MODE SENSE Data section, for a table showing codes that indicate which of these bits are changeable by the host using the MODE SELECT command.
Page 245: Port Control Mode Page (19H)
SCSI Interface Product Manual, Rev. B 8.12.13 Port control mode page (19h) The Port Control Mode page contains the parameters that affect SCSI target port operation options. The page shall be implemented by LUN 0 of all SPI SCSI target devices. The page shall not be implemented by logical units other than LUN 0.
Page 246: Margin Control Subpage
SCSI Interface Product Manual, Rev. B Table 160: Port Control Mode page long format (19h) Byte PS [1] Long (1) PAGE CODE (19h) SUBPAGE CODE [2] (MSB) PAGE LENGTH (n – 3) (LSB) Reserved Reserved PROTOCOL IDENTIFIER = 1h PROTOCOL SPECIFIC MODE PARAMETERS The Parameter Savable (PS) bit of 0 indicates that the page 19h parameter data is not savable in non-vol- atile memory.
Page 247 SCSI Interface Product Manual, Rev. B The margin control fields contain two’s complement values as shown in the table below. Value Parameter values Binary Decimal 0111b Maximum setting 0110b 0101b 0100b 0011b 0010b 0001b 000b Recommended default value 111b 1110b 1101b 1100b 1011b...
Page 248: Saved Training Configuration Values Subpage
SCSI Interface Product Manual, Rev. B The DRIVER SLEW RATE field indicates the relative difference between the assertion and negation mag- nitudes divided by the rise or fall time. A larger value indicates a faster slew rate. 8.12.13.2 Saved training configuration values subpage The saved training configuration values subpage is used to report the SCSI device’s saved training configura- tion values.
Page 249: Negotiated Settings Subpage
SCSI Interface Product Manual, Rev. B 8.12.13.3 Negotiated settings subpage The negotiated setting subpage is used to report the negotiated settings of a SCSI target port for the current I_T nexus. Table 163: Negotiated settings subpage Byte TRANSFER PERIOD FACTOR [1] Reserved REQ/ACK OFFSET [2] TRANSFER WIDTH EXPONENT [3]...
Page 250 SCSI Interface Product Manual, Rev. B Table 164: Report transfer capabilities subpage Byte MINIMUM TRANSFER PERIOD FACTOR [1] Reserved MAXIMUM REQ/ACK OFFEST [2] MAXIMUM TRANSFER WIDTH EXPONENT [3] PROTOCOL OPTIONS BITS SUPPORTED [4] Reserved Reserved Reserved The MINIMUM TRANSFER PERIOD FACTOR field shall be set to the smallest value of the transfer period factor supported by the SCSI target port.
Page 251: Informational Exceptions Control Page (1Ch)
SCSI Interface Product Manual, Rev. B 8.12.14 Informational Exceptions Control page (1Ch) The Informational Exceptions Control page (Table 165) defines the methods used by the target to control the reporting and the operations of specific informational exception conditions. This page shall only apply to infor- mational exceptions that report an additional sense code of Failure Prediction Threshold Exceeded to the application client.
Page 252 Maintaining the INTERVAL TIMER and REPORT COUNT after power cycles and/or resets by the target shall be vendor-specific. [Seagate: A predicted failure is preserved through resets and power cycles. The count of how many informational exception conditions that were reported by the target to any initiator is cleared by a reset of power cycle.]...
Page 253 SCSI Interface Product Manual, Rev. B Table 166: Format of Method of Reporting Informational Exceptions (MRIE) field MRIE Description No reporting of informational exception condition. This method instructs the target to not report information exception conditions. Asynchronous event reporting. This method instructs the target to report informational exception conditions by using the rules for asynchronous event reporting as described in the SCSI Architec- ture Model and the relevant Protocol Standard.
Page 254: Mode Sense (10) Command (5Ah)
A Disable Block Descriptors (DBD) bit of zero indicates that the drive may return zero or more block descriptors in the returned MODE SENSE data, at the drive’s discretion. Seagate SCSI-2 products return one block descriptor if the DBD bit is zero. A DBD bit of one specifies that the drive shall not return any block descriptors in the returned MODE SENSE data.
Page 255 SCSI Interface Product Manual, Rev. B The PAGE CODE allows the initiator to select one or all of the pages of Mode parameters supported by the target. Page codes that may be supported by the drive are summarized here (see individual drive’s Product Manual, Volume 1): Page Code Description...
Page 256 SCSI Interface Product Manual, Rev. B Table 169: MODE SENSE Parameter List Byte SENSE DATA LENGTH [1] MEDIUM TYPE [2] DPO-FUA WP [3] Reserved Reserved Reserved BLOCK DESCRIPTOR LENGTH (8 decimal) [4] Block Descriptor Data DENSITY CODE [5] [6] NUMBER OF BLOCKS (MSB) [6] NUMBER OF BLOCKS [6] NUMBER OF BLOCKS (LSB) [6] Reserved...
Page 257: Move Medium Command (A7H)
SCSI Interface Product Manual, Rev. B block descriptor. A NUMBER OF BLOCKS field value of zero indicates that all of the remaining logical blocks of the logical unit have the medium characteristics specified by the block descriptor. b. For drives that have capacity programming capability, these bytes do not report back the drive capacity on some models.
Page 258: Persistent Reserve In Command (5Eh)
SCSI Interface Product Manual, Rev. B 8.15 PERSISTENT RESERVE IN command (5Eh) The PERSISTENT RESERVE IN command (see Table 170) is used to obtain information about persistent res- ervations and reservation keys that are active within a device server. This command is used in conjunction with the PERSISTENT RESERVE OUT command (see Section 8.16).
Page 259: Persistent Reserve In Parameter Data For Read Keys
SCSI Interface Product Manual, Rev. B Table 171: PERSISTENT RESERVE IN Service Action codes Code Name Description Read Keys Reads all registered Reservation Keys. The Read Keys service action requests that the device server return a parameter list contain- ing a header and a complete list of all reservation keys currently reg- istered with the device server.
Page 260: Persistent Reserve In Parameter Data For Read Reservations
SCSI Interface Product Manual, Rev. B The ADDITIONAL LENGTH field contains a count of the number of bytes in the Reservation Key List. If the ALLOCATION LENGTH specified by the PERSISTENT RESERVE IN command is not sufficient to contain the entire parameter list, then only the bytes from 0 to the maximum allowed ALLOCATION LENGTH shall be sent to the application client.
Page 261 SCSI Interface Product Manual, Rev. B Table 174: PERSISTENT RESERVE IN Read Reservations Descriptor Byte (MSB) RESERVATION KEY [1] (LSB) (MSB) SCOPE-SPECIFIC ADDRESS [2] (LSB) Reserved SCOPE [3] TYPE [4] OBSOLETE [2] If a persistent reservation is present in the logical unit that does contain elements, there shall be a Reser- vation descriptor in the list of parameter data returned by the device server in response to the PERSIS- TENT RESERVE IN command with a Read Reservation service action for the Logical Unit persistent reservation that is held, if any, and each element persistent reservation that may be held.
Page 262 SCSI Interface Product Manual, Rev. B Table 176: Persistent Reservation Type Codes Code Name Description Read Reads Shared: Any application client on any initiator may execute commands Shared that perform transfers from the storage medium or cache of the logical unit to the initiator.
Page 263: Persistent Reserve Out Command (5Fh)
SCSI Interface Product Manual, Rev. B 8.16 PERSISTENT RESERVE OUT command (5Fh) The PERSISTENT RESERVE OUT command (see Table 177) is used to reserve a logical unit for the exclusive or shared use of a particular initiator. The command shall be used in conjunction with the PERSISTENT RESERVE IN command and shall not be used with the Reserve and Release commands.
Page 264: Persistent Reserve Out Parameter List
SCSI Interface Product Manual, Rev. B Table 178: PERSISTENT RESERVE OUT Service Action codes Code Name Description Register The PERSISTENT RESERVE OUT command executing a Register service action registers a reservation key with a device server. See T10/1157-D, Sec- tion 5.3, for details. Reserve The PERSISTENT RESERVE OUT command performing a Reserve service action creates a persistent reservation having a specified scope and type.
Page 265 SCSI Interface Product Manual, Rev. B The SERVICE ACTION RESERVATION KEY field contains information needed for three service actions; the Register, Preempt, and Preempt and Clear service actions. For the Register service action, the SER- VICE ACTION RESERVATION KEY field contains the new reservation key to be registered. For the Pre- empt and Preempt and Clear service actions, the SERVICE ACTION RESERVATION KEY field contains the reservation key of the persistent reservations that are being preempted.
Page 266: Prefetch Command (34H)
SCSI Interface Product Manual, Rev. B 8.17 PREFETCH command (34h) The PREFETCH command (Table 181) requests that the drive read and transfer the specified logical blocks to the drive's cache memory. No data shall be transferred to the initiator. Table 181: PREFETCH command (34h) Byte OPERATION CODE (34h)
Page 267: Read Command (08H)
SCSI Interface Product Manual, Rev. B 8.19 Read command (08h) The Read command (Table 182) requests that the drive transfer data to the initiator. Table 182: Read command (08h) Byte LOGICAL BLOCK ADDRESS (MSB) [2] LOGICAL UNIT NUMBER [1] LOGICAL BLOCK ADDRESS LOGICAL BLOCK ADDRESS (LSB) TRANSFER LENGTH [3] CONTROL [4]...
Page 268 SCSI Interface Product Manual, Rev. B If any of the following conditions occur, this command shall be terminated with a CHECK CONDITION status, and if extended sense is implemented, the Sense Key shall be set as indicated in the following table. This table does not provide an exhaustive enumeration of all conditions that may cause the CHECK CONDITION status.
Page 269: Read 10 Command (28H)
SCSI Interface Product Manual, Rev. B 8.20 READ 10 command (28h) The READ 10 command (formerly called the READ EXTENDED command) requests that the target transfer data to the initiator. This command is implemented with the drive specific parameters shown in Table 183. This command operates the same as the READ command (see Section 8.19) except that in the CDB for this command a four byte LOGICAL BLOCK ADDRESS and a two byte Transfer Length may be specified.
Page 270 SCSI Interface Product Manual, Rev. B The TRANSFER LENGTH specifies the number of contiguous logical blocks of data that shall be trans- ferred. A TRANSFER LENGTH of zero indicates that no logical blocks shall be transferred. This condition shall not be considered an error. Any other value indicates the number of logical blocks that shall be trans- ferred.
Page 271: Read 12 Command (A8H)
SCSI Interface Product Manual, Rev. B 8.21 Read 12 command (A8h) The Read 12 command requests that the target transfer data to the initiator. Table 184: Read 12 command (A8h) Byte DPO [2] FUA [3] RELADR [4] LOGICAL UNIT NUMBER [1] LOGICAL BLOCK ADDRESS (MSB) [5] LOGICAL BLOCK ADDRESS [5] LOGICAL BLOCK ADDRESS [5]...
Page 272 SCSI Interface Product Manual, Rev. B If any of the following conditions occur, this command shall return a CHECK CONDITION status and the Sense Key shall be set as indicated. This table does not provide an exhaustive enumeration of all conditions that may cause the CHECK CONDITION status.
Page 273: Read 16 Command (28H)
SCSI Interface Product Manual, Rev. B 8.22 READ 16 command (28h) The READ 16 command requests that the target transfer data to the initiator. Table 185: READ 16 command (28h) Byte DPO [2] FUA [3] RELADR [4] LOGICAL UNIT NUMBER [1] LOGICAL BLOCK ADDRESS (MSB) [5] LOGICAL BLOCK ADDRESS [5] LOGICAL BLOCK ADDRESS [5]...
Page 274 SCSI Interface Product Manual, Rev. B The TRANSFER LENGTH specifies the number of contiguous logical blocks of data that shall be trans- ferred. A TRANSFER LENGTH of zero indicates that no logical blocks shall be transferred. This condition shall not be considered an error. Any other value indicates the number of logical blocks that shall be trans- ferred.
Page 275: Read Buffer Command (3Ch)
SCSI Interface Product Manual, Rev. B 8.23 READ BUFFER command (3Ch) The READ BUFFER command is used in conjunction with the WRITE BUFFER command as a diagnostic func- tion for testing drive memory and the SCSI bus integrity. This command shall not alter the medium. Command format is shown in Table 186.
Page 276: Read Combined Descriptor Header And Data Mode (0000B)
SCSI Interface Product Manual, Rev. B 8.23.1 Read Combined Descriptor Header and Data mode (0000b) In this mode, a four byte READ BUFFER header followed by the data bytes are returned to the initiator during the DATA IN phase. The BUFFER ID and the BUFFER OFFSET fields are not used by drives supported by this manual, and must be zero (see Table 187).
Page 277: Read Data From Echo Buffer Mode (1010B)
SCSI Interface Product Manual, Rev. B The value contained in the buffer field of subsequent WRITE BUFFER and READ BUFFER commands should be a multiple of 2 offset boundary as shown in Table 189. Table 189: Buffer Offset Boundary Offset Offset Boundary Boundary Buffer Offsets...
Page 278: Read Capacity Command (25H)
SCSI Interface Product Manual, Rev. B 8.24 READ CAPACITY command (25h) The READ CAPACITY command (Table 191) provides a means for the initiator to request the capacity of the drive information. Table 191: READ CAPACITY command (25h) Byte RELADR [2] LOGICAL UNIT NUMBER [1] LOGICAL BLOCK ADDRESS (MSB) [2] LOGICAL BLOCK ADDRESS [2]...
Page 279 SCSI Interface Product Manual, Rev. B In response to the READ CAPACITY command, the drive returns 8 bytes of READ CAPACITY Data to the host. The contents of the 8 bytes are listed in Table 192. Table 192: READ CAPACITY Data Byte Description LOGICAL BLOCK ADDRESS (MSB)
Page 280: Read Defect Data (10) Command (37H)
SCSI Interface Product Manual, Rev. B 8.25 READ DEFECT DATA (10) command (37h) The READ DEFECT DATA (10) command requests that the target transfer the medium defect data to the initia- tor. If the drive is unable to access any medium defect data, it terminates the command with CHECK CONDI- TION status.
Page 281 SCSI Interface Product Manual, Rev. B This command is intended to be used only with the FORMAT UNIT command (Section 8.5). The initiator should not interpret or act upon this list except to resend this list as defect data in a FORMAT UNIT command. It is not possible to relate actual physical locations to logical block addresses given in connection with other com- mands.
Page 282: Read Defect Data (12) Command (B7H)
SCSI Interface Product Manual, Rev. B 8.26 READ DEFECT DATA (12) command (B7h) The READ DEFECT DATA (12) command (see Table 195) requests that the device server transfer the medium defect data to the application client. If the logical unit is reserved, a reservation conflict shall occur when a READ DEFECT DATA (12) command is received from a SCSI initiator port other then the one holding a logical unit reservation.
Page 283: Read Element Status Command (B4H)
SCSI Interface Product Manual, Rev. B IN phase when the ALLOCATION LENGTH bytes have been transferred or when all available defect data has been transferred to the initiator, whichever is less. See Table 61, “CONTROL field,” in Section 7.2.1. The READ DEFECT DATA (12) list header (see Table 196) contains an eight byte header, followed by zero or more defect descriptors.
Page 284: Read Extended Command
SCSI Interface Product Manual, Rev. B 8.28 READ EXTENDED command Refer to the READ 10 command on page 251. 8.29 READ LONG command (3Eh) The READ LONG command (Table 197) requests that the target transfers data to the initiator. The data passed during the READ LONG command shall include the data bytes, followed by the ECC bytes of the single LOGI- CAL BLOCK ADDRESSed by the command.
Page 285 SCSI Interface Product Manual, Rev. B contain the difference (residue) of the requested length minus the actual length in bytes. (Negative values are indicated by two’s complement notation.) See Table 61, “CONTROL field,” in Section 7.2.1.
Page 286: Reassign Blocks Command (07H)
SCSI Interface Product Manual, Rev. B 8.30 REASSIGN BLOCKS command (07h) The REASSIGN BLOCKS command (Table 198) requests the target to reassign the defective logical blocks to an area on the logical unit reserved for this purpose. After sending the REASSIGN BLOCKS command, the initiator transfers a defect list that contains the LOGI- CAL BLOCK ADDRESSes to be reassigned.
Page 287: Reassign Blocks Defect List
SCSI Interface Product Manual, Rev. B 8.30.1 REASSIGN BLOCKS defect list The REASSIGN BLOCKS defect list (Table 199) contains a four byte header followed by one or more Defect Descriptors. The length of each Defect Descriptor is four bytes. Table 199: REASSIGN BLOCKS defect list Byte Defect List Header...
Page 288: Rebuild Command (81H)
SCSI Interface Product Manual, Rev. B 8.31 REBUILD command (81h) The REBUILD command (Table 200) requests that the target write to the medium the Xor data generated from the specified source devices. The target, acting as a temporary initiator, issues Read commands to retrieve the specified data from the source device.
Page 289: Rebuild And Regenerate Parameter Data
SCSI Interface Product Manual, Rev. B The PORT CONTROL field is defined in Table 201. If the PORT CONTROL field has a value of 01b and the target is not a multiple port device the command shall be terminated with a CHECK CONDITION sta- tus.
Page 290 SCSI Interface Product Manual, Rev. B The SOURCE DESCRIPTORS identify the source device target identifiers and starting LOGICAL BLOCK ADDRESSes on those devices for the REGENERATE or REBUILD operation. See Table 203 for the source descriptor format. The PAD field contains invalid data and shall be ignored. Note.
Page 291: Receive Diagnostic Results Command (1Ch)
SCSI Interface Product Manual, Rev. B 8.32 RECEIVE DIAGNOSTIC RESULTS command (1Ch) The RECEIVE DIAGNOSTIC RESULTS command requests analysis data be sent to the initiator after comple- tion of a SEND DIAGNOSTIC command. The drive supports the optional Page format, wherein the initiator sends additional pages after a SEND DIAGNOSTIC command.
Page 292 The ERROR CODE is a two byte value that provides information designating which part of a diagnostic operation has failed. The byte 7 error code is vendor unique and defined in note [4]. Usually, Seagate drives support only some subset of the list given in note [4].
Page 293: Supported Diagnostic
SCSI Interface Product Manual, Rev. B 8.32.1 Supported Diagnostic Pages If the SEND DIAGNOSTICs command requests the Supported Diagnostics Pages list (PF bit = 1), the drive returns data in the format shown in Table 206 after receiving the RECEIVE DIAGNOSTIC RESULTS com- mand.
Page 294 SCSI Interface Product Manual, Rev. B address. An RAREA bit of zero indicates that no part of the translated address falls within a reserved area of the medium. Table 208: Address Field LOGICAL BLOCK ADDRESS Format Byte (MSB) LOGICAL BLOCK ADDRESS (LSB) Table 209: Address Field Physical Sector Address Format...
Page 295: Regenerate Command (82H)
SCSI Interface Product Manual, Rev. B 8.33 REGENERATE command (82h) The REGENERATE command (see Table 210) requests that the target write to the buffer the Xor data gener- ated from its own medium and the specified source devices. The target, acting as a temporary initiator, issues Read commands to retrieve the specified data.
Page 296 SCSI Interface Product Manual, Rev. B The REGENERATE LENGTH field indicates the length in logical blocks of the resulting Xor data. It also specifies the length in logical blocks that is transferred from each of the specified sources. The parameter data for the REGENERATE command is defined in Table 202. This parameter data describes the other devices that will be sources for the regenerate operation.
Page 297: Release (6) Command (17H)
SCSI Interface Product Manual, Rev. B 8.34 RELEASE (6) command (17h) The RELEASE (6) command (Table 212) is used to release previously reserved drives. It is not an error for a SCSI initiator port to attempt to release a reservation that is not currently active. In this case, the drive returns GOOD status without altering any other reservation.
Page 298: Release (10) Command (57H)
SCSI Interface Product Manual, Rev. B 8.35 RELEASE (10) command (57h) The Reserve and Release commands provide the basic mechanism for contention resolution in multiple-initia- tor systems. The RELEASE (10) command (Table 213) is used to release a previously reserved logical unit or, if the extent release option is implemented, to release previously reserved extents within a logical unit.
Page 299: Report Device Identifier Command (A3)
SCSI Interface Product Manual, Rev. B 8.36 REPORT DEVICE IDENTIFIER command (A3) The REPORT DEVICE IDENTIFIER command (see Table 214) requests that the device server send device identification information to the application client. This command is optional for all device types, except for SCC-2 devices, and devices that set the SCCS bit in their Standard INQUIRY data (see Section 8.6.1).
Page 300 SCSI Interface Product Manual, Rev. B reflect the truncation. The identifier length shall initially equal zero, and shall be changed only by a successful SET DEVICE IDENTIFIER command (see Section 8.48). [b] The IDENTIFIER field shall contain a vendor-specific value. The value reported shall be the last value written by a successful SET DEVICE IDENTIFIER command.
Page 301: Report Luns Command (A0H)
SCSI Interface Product Manual, Rev. B 8.37 REPORT LUNS command (A0h) The REPORT LUNS command (see Table 216) requests that the peripheral device LOGICAL UNIT NUMBERs of known logical units in the target be sent to the application client. The REPORT LUNS command shall return information about only those logical units to which commands may be sent.
Page 302 SCSI Interface Product Manual, Rev. B The device server shall report the LOGICAL UNIT NUMBERs of configured logical units using the format shown in Table 217. Table 217: REPORT LUNS parameter list format Byte (MSB) LUN LIST LENGTH (n-7) [1] (LSB) (MSB) Reserved...
Page 303: Request Sense Command (03H)
SCSI Interface Product Manual, Rev. B 8.38 REQUEST SENSE command (03h) The REQUEST SENSE command (Table 218) requests that the device server transfer sense data to the appli- cation client in the format shown in Table 219. If any nonfatal error occurs during execution of REQUEST SENSE, the drive shall return sense data with GOOD status.
Page 304 The SEGMENT NUMBER field contains the number of the current segment descriptor if the REQUEST SENSE command is in response to a COPY, COMPARE, or COPY AND VERIFY command. Up to 256 segments are supported, beginning with segment zero. Seagate disc drives do not currently implement any of the copy commands.
Page 305 SCSI Interface Product Manual, Rev. B Additional sense codes provide further detail describing the sense key. Additional sense code qualifiers add further detail to the additional sense code. The additional sense code and additional sense code qual- ifier may be used by application clients where sophisticated error recovery procedures require detailed information describing the error and exception conditions.
Page 306: Sense Key Specific Field
SCSI Interface Product Manual, Rev. B [15] 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. [16] Bytes 18-n are not presently used. 8.38.1 Sense Key Specific field The SENSE KEY SPECIFIC field as defined by this manual when the value of the Sense Key Specific Valid...
Page 307: Current Errors
SCSI Interface Product Manual, Rev. B Note. This field relates to the retry count fields specified within the error recovery parameters page of the MODE SELECT command (see Table 146). If the sense key is NOT READY and the SKSV bit is one, the SENSE KEY SPECIFIC field shall be defined as shown in Table 220.
Page 308: Deferred Errors
SCSI Interface Product Manual, Rev. B 8.38.1.2 Deferred errors Error code 70h (current error) indicates that the Check Condition or Command Terminated status returned is the result of an error or exception condition on the command that returned the Check Condition or Command Terminated status or an unexpected bus free condition.
Page 309: Sense Key And Sense Code Descriptions
SCSI Interface Product Manual, Rev. B 8.38.2 Sense Key and Sense Code descriptions Table 224 lists the Sense Keys in the extended sense data format that are used by the drive. Table 224: Applicable Drive Sense Keys Sense Description No Sense—Indicates there is no specific Sense Key information to be reported for the drive. This would be the case for a successful command or when the ILI bit is one.
Page 310: Additional Sense And Additional Sense Qualifier Codes
Table 225 lists the Additional Sense (ASC) and Additional Sense Qualifier (ASCQ) codes. Code values are in hexadecimal. ANSI standard SPC-2 lists a more complete table in error description alphabetical order. This Table 225 list adequately covers all Seagate drives, however. Note.
Page 311 Synchronous Data Transfer Error Defect List Not Found Primary Defect List Not Found Grown Defect List Not Found Seagate Unique Diagnostic Code Miscompare During Verify Operation Number of Defects Overflows the Allocated Space That The Read Defect Command Can Handle...
Page 312 SCSI Interface Product Manual, Rev. B Table 225: Error codes for ASC and ASCQ bytes (Table 219 bytes 12 and 13 of Sense Data) (continued) ASCQ (byte 12) (byte 13) Description Invalid Field Parameter—TMS Firmware Tag Invalid Field Parameter—Check Sum Invalid Field Parameter—Firmware Tag Write Protected Power On, Reset, Or Bus Device Reset Occurred...
Page 313 SCSI Interface Product Manual, Rev. B Table 225: Error codes for ASC and ASCQ bytes (Table 219 bytes 12 and 13 of Sense Data) (continued) ASCQ (byte 12) (byte 13) Description Power-On Or Self-Test Failure Message Error Internal Target Failure Select/Reselection Failure SCSI Parity Error Initiator Detected Error Message Received...
Page 314: Reserve (6) Command (16H)
SCSI Interface Product Manual, Rev. B 8.39 RESERVE (6) command (16h) The Reserve and Release commands provide the basic mechanism for contention resolution in multiple initia- tor systems. The third party reservation allows one initiator to reserve the drive for some other SCSI device that can act as a SCSI initiator port.
Page 315: Third Party Reservation
SCSI Interface Product Manual, Rev. B 8.39.3 Third Party Reservation The third party reservation option for the Reserve command allows a SCSI initiator port to reserve a logical unit for another SCSI device. If the drive supports third party reserve command, the drive also implements the third party release option (see Section 8.34.3).
Page 316: Reserve (10) Command (56H)
SCSI Interface Product Manual, Rev. B 8.40 RESERVE (10) command (56h) The Reserve and Release commands provide the basic mechanism for contention resolution in multiple-initia- tor systems. The RESERVE (10) command (Table 228) is used to reserve a logical unit or, if the extent reserva- tion option is implemented, extents within a logical unit.
Page 317: Rezero Unit Command (01H)
SCSI Interface Product Manual, Rev. B 8.41 REZERO UNIT command (01h) The REZERO UNIT command (Table 229) requests that the drive set its LOGICAL BLOCK ADDRESS to zero and return the drive read/write heads to the track (or cylinder) containing logical block zero. This command is intended for systems which disable retries and the initiator performs error recovery.
Page 318: Seek Command (0Bh)
SCSI Interface Product Manual, Rev. B 8.45 SEEK command (0Bh) The SEEK command (Table 230) requests that the drive seek to the specified LOGICAL BLOCK ADDRESS. For systems which support disconnection, the drive disconnects when a valid SEEK command is received. The use of this command is infrequent since all commands involving data transfer to/from the drive media contain implied seek addresses.
Page 319: Seek Extended Command (2Bh)
SCSI Interface Product Manual, Rev. B 8.46 SEEK EXTENDED command (2Bh) The SEEK EXTENDED command requests that the drive seek to the specified LOGICAL BLOCK ADDRESS. This command is implemented with the drive specific parameters listed in Table 231. Table 231: SEEK EXTENDED command (2Bh) Byte LOGICAL UNIT NUMBER [1]...
Page 320: Send Diagnostic Command (1Dh)
SCSI Interface Product Manual, Rev. B 8.47 SEND DIAGNOSTIC command (1Dh) The SEND DIAGNOSTIC command (see Table 232) requests the device server to perform diagnostic operations on the target, on the logical unit, or on both. Targets that support this command shall implement, at a minimum, the default self-test feature (the SelfTest bit equal to one and a PARAMETER LIST LENGTH of zero).
Page 321 SCSI Interface Product Manual, Rev. B SPC-2, T10/1236D, for the definition of diagnostic pages. A PF bit of zero indicates that all SEND DIAG- NOSTIC parameters are vendor-specific. A SELF TEST bit of one directs the device server to complete the target’s default self-test. If the self-test successfully passes, the command shall be terminated with Good status;...
Page 322: Supported Diagnostic Page-Send Diagnostic
SCSI Interface Product Manual, Rev. B 8.47.1 Supported Diagnostic page—SEND DIAGNOSTIC The Supported Diagnostic page (Table 234) instructs the drive to make available the list of all supported diag- nostic pages to be returned by a subsequent RECEIVE DIAGNOSTIC RESULTS command. The definition of this page for the SEND DIAGNOSTIC command includes only the first four bytes (Receive Diagnostic version given in Table 206).
Page 323 SCSI Interface Product Manual, Rev. B The ADDRESS TO TRANSLATE field contains a single address the initiator is requesting the drive to translate. The format of this field is defined by the SUPPLIED FORMAT field. The supported formats are shown in Table 208 and Table 209. For systems which support disconnection, the drive will disconnect while executing this command.
Page 324: Set Device Identifier Command (A4H)
SCSI Interface Product Manual, Rev. B 8.48 SET DEVICE IDENTIFIER command (A4h) The SET DEVICE IDENTIFIER command (see Table 236) requests that the device identifier information in the logical unit be set to the value received in the SET DEVICE IDENTIFIER parameter list. This command is optional for all device types.
Page 325: Set Limits Command (33H)
SCSI Interface Product Manual, Rev. B The SET DEVICE IDENTIFIER parameter list (see Table 237) contains the identifier to be set by the addressed logical unit. Table 237. SET DEVICE IDENTIFIER parameter list Byte IDENTIFIER [1] The IDENTIFIER field shall be a vendor-specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands.
Page 326: Start/Stop Unit Command (1Bh)
SCSI Interface Product Manual, Rev. B 8.50 START/STOP UNIT command (1Bh) The START/STOP UNIT command requests that the target enable the logical unit for further operations (start) or stop spindle rotation (stop). The drive is able to execute the following commands when the drive spindle is not rotating, or in a simulated stopped condition: TEST UNIT READY REQUEST SENSE...
Page 327: Synchronize Cache 10 Command (35H)
SCSI Interface Product Manual, Rev. B 8.51 SYNCHRONIZE CACHE 10 command (35h) The SYNCHRONIZE CACHE 10 command (Table 239) ensures that logical blocks in the cache memory, within the specified range, have their most recent data value recorded on the physical medium. If a more recent data value for a logical block within the specified range exists in the cache memory than on the physical medium, then the logical block from the cache memory shall be written to the physical medium.
Page 328: Synchronize Cache 16 Command (91H)
SCSI Interface Product Manual, Rev. B 8.52 SYNCHRONIZE CACHE 16 command (91h) The SYNCHRONIZE CACHE 16 command (Table 239) ensures that logical blocks in the cache memory, within the specified range, have their most recent data value recorded on the physical medium. If a more recent data value for a logical block within the specified range exists in the cache memory than on the physical medium, then the logical block from the cache memory shall be written to the physical medium.
Page 329: Test Unit Ready Command (00H)
SCSI Interface Product Manual, Rev. B 8.53 TEST UNIT READY command (00h) The TEST UNIT READY command provides a means to verify the logical unit is ready. This is not a request for a self-test. If the logical unit (drive) can accept an appropriate medium access command without returning CHECK CONDITION status, the drive returns a GOOD status.
Page 330: Verify Command (2Fh)
SCSI Interface Product Manual, Rev. B 8.54 VERIFY command (2Fh) The VERIFY command requests that the target verify the data written on the medium. This command is imple- mented with the drive specific parameters listed in Table 242. The drive disconnects while this command is being executed if the initiator supports disconnect/reconnect.
Page 331: Write Command (0Ah)
SCSI Interface Product Manual, Rev. B 8.55 Write command (0Ah) The Write command (Table 243) requests that the drive write, to the medium, the data transferred by the initia- tor. Table 243: Write command (0Ah) Byte LOGICAL BLOCK ADDRESS (MSB) [2] LOGICAL UNIT NUMBER [1] LOGICAL BLOCK ADDRESS LOGICAL BLOCK ADDRESS (LSB)
Page 332: Write 10 Command (2Ah)
SCSI Interface Product Manual, Rev. B 8.56 WRITE 10 command (2Ah) The WRITE 10 command requests that the drive write to the medium the data transferred by the initiator. This command is implemented with the drive specific parameters listed in Table 244. Refer also to individual drive’s Product Manual, Volume 1, Write Caching section, for information on Write Cache Control.
Page 333 SCSI Interface Product Manual, Rev. B If any of the following conditions occur, this command shall be terminated with a CHECK CONDITION status and the Sense Key shall be set as indicated in the following table. This table does not provide an exhaustive enumeration of all conditions that may cause the CHECK CONDITION status.
Page 334: Write And Verify Command (2Eh)
SCSI Interface Product Manual, Rev. B 8.57 WRITE AND VERIFY command (2Eh) The WRITE AND VERIFY command requests that the target write the data transferred from the initiator to the medium and then verify that the data is correctly written. The data is only transferred once from the initiator to the drive.
Page 335: Write Buffer Command (3Bh)
SCSI Interface Product Manual, Rev. B 8.58 WRITE BUFFER command (3Bh) The WRITE BUFFER command may be used in conjunction with the READ BUFFER command as a diagnos- tic function for testing the drive’s data buffer memory and the SCSI bus integrity. When used in a diagnostic mode, the medium shall not be accessed during the execution of this command.
Page 336: Combined Header And Data Mode (0000B)
SCSI Interface Product Manual, Rev. B 8.58.1 Combined header and data mode (0000b) In this mode, data to be transferred is preceded by a four-byte header. The four-byte header consists of all reserved bytes. The Buffer ID and the Buffer Offset fields shall be zero. The PARAMETER LIST LENGTH field specifies the maximum number of bytes that shall be transferred from the Data Out Buffer.
Page 337: Download Microcode With Offsets (0110B)
SCSI Interface Product Manual, Rev. B shall generate a unit attention condition (see SAM-2) for all initiators except the one that issued the WRITE BUFFER command. When reporting the unit attention condition, the device server shall set the additional sense code to Microcode Has Been Changed. 8.58.6 Download microcode with offsets (0110b) In this mode, the application client may split the transfer of the vendor-specific microcode or control information...
Page 338: Write Data To Echo Buffer (1010B)
SCSI Interface Product Manual, Rev. B and save operation. In this mode, the Data Out Buffer contains vendor-specific, self-describing microcode or control information. Since the downloaded microcode or control information may be sent using several commands, when the logi- cal unit detects the last download microcode with offsets and save mode WRITE BUFFER command has been received, the device server shall perform any logical unit required verification of the complete set of down- loaded microcode or control information prior to returning Good status for the last command.
Page 339: Write Long Command (3Fh)
SCSI Interface Product Manual, Rev. B 8.59 WRITE LONG command (3Fh) The WRITE LONG command (Table 247) requests that the target write to the medium the data transferred by the initiator. The data passed during the WRITE LONG command shall include the data bytes and all ECC bytes to be written to the single LOGICAL BLOCK ADDRESSed in the command.
Page 340: Write Same Command (41H)
SCSI Interface Product Manual, Rev. B 8.60 WRITE SAME command (41h) The WRITE SAME command (Table 248) requests that the target write the single block of data transferred by the initiator to the medium multiple times. Table 248: WRITE SAME command (41h) Byte OPERATION CODE (41h) LOGICAL UNIT NUMBER [1]...
Page 341: Xdread Command (52H)
REGENERATE 8.33 Not all Seagate devices support the Xor commands. Where used by a particular model Seagate device, the individual drive’s Product Manual, Volume 1, for that model device specifies that the Xor commands are sup- ported by the devices addressed by the Product Manual.
Page 342 SCSI Interface Product Manual, Rev. B tions are needed for a typical update write sequence: a read transfer from the device containing protected data, a write transfer to the device containing protected data, a read transfer from the device containing check data, and a write transfer to the device containing check data.
Page 343: Xdwrite Command (50H)
SCSI Interface Product Manual, Rev. B 8.62 XDWRITE command (50h) The XDWRITE command (see Table 251) requests that the target Xor the data transferred to it with the data on the medium. The resulting Xor data is stored in the target's buffer. The disposition of the data transferred from the initiator is controlled by the disable write bit.
Page 344: Xdwrite Extended Command (80H)
SCSI Interface Product Manual, Rev. B 8.63 XDWRITE EXTENDED command (80h) The XDWRITE EXTENDED command (see Table 252) requests that the target Xor the data transferred to it with the data on the medium (see Note [6]). The disposition of the data transferred from the initiator is con- trolled by the Disable Write bit.
Page 345 SCSI Interface Product Manual, Rev. B Table 253: PORT CONTROL field Value Description The target transfers the data using the same port that received the command. The target transfers the data using a different port than that which received the command. The target transfers the data using one port of the target’s choice.
Page 346: Xpwrite Command (51H)
SCSI Interface Product Manual, Rev. B 8.64 XPWRITE command (51h) The XPWRITE command (see Table 254) requests that the target Xor the data transferred to it with the data on the medium and then writes the Xor data to the medium. For additional information about Xor commands, see Section 8.61.1.
Page 347: Drive Features
Not all Seagate drives support this mode. While performing a self-test in the foreground mode, the device server shall respond to all commands except INQUIRY, REPORT LUNS, and REQUEST SENSE with a CHECK CONDITION status, a sense key of Not Ready and an additional sense code of Logical Unit Not Ready, Self-Test In Progress.
Page 348: Background Mode
SCSI Interface Product Manual, Rev. B If a device server is performing a self-test in the foreground mode and a test segment error occurs during the test, the device server shall update the Self-test results log page (see Section 8.9.9) and report CHECK CON- DITION status with a sense key of Hardware Error and an additional sense code of Logical Unit Failed Self- Test.
Page 349: Alternate Error Detection For The Asynchronous Information Phases (Aip)-Command, Message, And Status
SCSI Interface Product Manual, Rev. B While executing a self-test unless an error has occurred, a device server shall respond to a REQUEST SENSE command by returning a sense key of Not Ready and an additional sense code of Logical Unit Not Ready, Self- Test In Progress with the sense key specific bytes set for progress indication.
Page 350: Covered Signals
SCSI Interface Product Manual, Rev. B 9.3.2.1 Covered signals Table 257 defines the signals to be covered by the protection code and their bit locations in the 21-bit code word. When a SCSI device receives an information byte, it also latches the state of the other SCSI signals and values noted in Table 257.
Page 351: Code Description
SCSI Interface Product Manual, Rev. B 9.3.2.2 Code description The protection code (see Table 258) is a cyclic binary BCH code. Table 258: Protection code Maximum data Number of Minimum distance Code bits allowed redundant bits of the code (21,15,4) The BCH protection code is a cyclic code with a generator polynomial of x 6 + x 5 + x 2 + 1.
Page 352: Enabling Protection Code Checking
SCSI Interface Product Manual, Rev. B 9.3.3.2 Enabling protection code checking A SCSI device enables protection code checking for an I_T nexus when it detects that valid protection code data is being transmitted on the upper byte of the SCSI bus. The frequency that a SCSI device will try to enable protection code checking and the number of valid protection code bytes required is vendor-specific.
Page 353: Case 3-Current I/O Processes Not Allowed During Insertion Or Removal
SCSI Interface Product Manual, Rev. B c. The system shall be designed such that the SCSI device being removed shall maintain its power ground and logic ground prior to, during, and for at least 1 ms after the disconnection of any device connector con- tact from the SCSI bus.
Page 354: Spi-3 To Scsi-2 Terminology Mapping
SCSI Interface Product Manual, Rev. B g. Initiation or resumption of I/O processes for a newly inserted or removed SCSI device is vendor-specific but shall not occur sooner than 200 milliseconds after the completion of the insertion or removal event. h.
Page 355 SCSI Interface Product Manual, Rev. B Index Diagnostic Data Bytes 274 Drive Standard Inquiry Data 152 Persistent Reserve In parameter data 241, 242 Numerics Standard Inquiry Data format 150 additional parameter 291 10 byte commands 135, 137 additional sense 291 12 byte commands 135, 137 data 245, 283 3rd Party.
Page 356 SCSI Interface Product Manual, Rev. B Alternate Sectors per Zone receive setup time 23 Format Parameters page 210, 211 SCSI bus signal 14 Alternate Track transmit setup time 23 Translate Address page—Receive Diagnostic attention condition 97 275, 276 attribute 127 Alternate Tracks per Volume auto contingent allegiance 3, 5, 121, 127, 129 Format Parameters page 210, 211...
Page 357 SCSI Interface Product Manual, Rev. B BPV. see Bit Pointer Valid Byte Check BQue. see Basic Queuing Verify command 312 BSY. see Busy Write and Verify command 316 buffer 325 Byte Transfer Length Buffer Capacity Read Long command 266 Echo Buffer Descriptor mode 259 Write Buffer command 317 Read Buffer Descriptor mode 258, 259 Write Long command 321...
Page 358 SCSI Interface Product Manual, Rev. B chip noise in receiver 24 16-byte commands 119 Clear 6-byte commands 118 Service Action code 246 control field 121 clear ACA message 95 format 118 clear ACA task management function 128 linked 6 clear queue 130, 313 typical variable length 120 clear queue message 249 Command Descriptor Block Size...
Page 359 SCSI Interface Product Manual, Rev. B contiguous logical blocks 312, 314 control byte 127, 128 contingent allegiance 4 control field 121 contingent allegiance (NACA=0) 130 control mode page 4, 127, 132, 133, 176, 177, contingent allegiance condition 5, 128 194, 199, 203, 219, 227, 237 Control descriptor 201 Change Definition command 139, 140...
Page 360 SCSI Interface Product Manual, Rev. B D type defect 142 data 142, 264 Data growth 142 SPI data information unit 113 primary 142 SPI data stream information unit 114 defect data descriptor 263 data 5 defect data header 263 failed 290 Defect Descriptor 146 subset 290 Reassign Blocks defect list 269...
Page 361 SCSI Interface Product Manual, Rev. B device behavior page 170 Defect List header 144 device failure 291 Disable Queuing Device Identification page 160 Control Mode page 219, 220 Device Offline Disable Read-Ahead Send Diagnostic command 302, 303 Caching Parameters page 216, 218 device server 3, 4, 240, 242, 244, 245, 246, 247, disable retries 299 Disable Save...
Page 362 SCSI Interface Product Manual, Rev. B drive counter 176 Enable Threshold Comparison drive failure 233 Log Parameter 175, 176 Drive ID Enable Vital Product Data Jumper Settings page 168 Inquiry command 148 Drive ID table enable vital product data 155 Jumper Settings page 169 Enable Warning drive nominal rotation rate 213...
Page 363 SCSI Interface Product Manual, Rev. B error handling parameter 290 error log 290 factory log page 183 error logging 219 factory/field maintenance 273 error recovery 205, 215, 266 failed block 270 flag 215 failed data 290 error recovery page 204, 266 failed function 290 descriptor 201 failure prediction threshold exceeded 233...
Page 364 SCSI Interface Product Manual, Rev. B Force Unit Access glossary 3 Caching Parameters page 218 GLTSD. see Global Logging Target Save Disable Read 12 command 253 good status 123, 191, 198, 236, 248, 270, 277, Read 16 command 255 279, 280, 290, 311, 314, 325, 326 Read Extended command 251 growth defect 142 Rebuild command 270...
Page 365 SCSI Interface Product Manual, Rev. B identify message 78, 117 information unit transfer 5, 34 Idle informational exception condition 235 Power Condition page 224 informational exceptions control page 194, 199, Idle Condition Timer 233, 237 Power Condition page 224 descriptor 201 ignore wide residue message 79 initial connection 5 IL bit 202...
Page 366 SCSI Interface Product Manual, Rev. B internal data buffer 313 Drive Standard Inquiry Data 153 internal error recovery procedure 313 Standard Inquiry Data format 150 internal Xor operation 324 linked command 5, 6, 125, 132 intersymbol interference 5, 6 complete 121 Interval Timer List Parameter Informational Exceptions Control page 233, 234...
Page 367 SCSI Interface Product Manual, Rev. B defective 269 address 283 format 276 Logical Unit Number List Logical Block Cache Segment Size Report LUNs parameter list format 284 Caching Parameters page 216, 218 Logical Unit Number List Length Logical Block Data Report LUNs parameter list format 284 Write Same command 322 logical unit persistent reservation 243...
Page 368 SCSI Interface Product Manual, Rev. B medium error 144, 205, 250, 252, 254, 256, 262, mode select parameter list 191, 193 269, 288 mode select parameters 130 medium error sense key 291 mode select savable parameters 145 Medium Rotation Rate mode select/mode sense page 193 Rigid Drive Geometry Parameters page 213 mode sense 121...
Page 369 SCSI Interface Product Manual, Rev. B Multiplication Factor Rigid Drive Geometry Parameters page 212, Caching Parameters page 216, 217 Number of Heads Rigid Drive Geometry Parameters page 212, NACA. see Normal Auto Contingent Allegiance Number of Interleaves ND. see Notched Drive Device Behavior page 170 negated edge 4 Number of Source Descriptors...
Page 370 SCSI Interface Product Manual, Rev. B Notch page 222 Port Control Mode page 227, 228 P bit 262, 263, 264, 265 Power Condition page 224 P List Rigid Drive Geometry Parameters page 212 Read Defect Data (12) command 264 Self-test Results Log page 184 Read Defect Data (12) list header 265 Start-stop Cycle Counter page 186 P list 264...
Page 371 SCSI Interface Product Manual, Rev. B Power Condition page 224 parameter list Rigid Drive Geometry Parameters page 212 Persistent Reserve Out 246 Self-test Results Log page 184 Parameter List Length Start-stop Cycle Counter page 186 Log Select command 171, 172 Supported Diagnostic page 304 Mode Select (10) command 195 Supported Diagnostic Pages 275...
Page 372 SCSI Interface Product Manual, Rev. B pCRC Receive hold time 24 physical interface pCRC Receive setup time 24 characteristics 10 pCRC Transmit hold time 25 physical medium 309, 310 pCRC Transmit setup time 25 physical reconnect 7 PE. see Parity Enable physical reconnection 7 peer entities 7 Physical Sector...
Page 373 SCSI Interface Product Manual, Rev. B Standard Inquiry Data format 150 queue tag value 133 Product Revision Level queued task 132 Drive Standard Inquiry Data 150, 154 Quick Arbitrate Supported Product Serial Number SPI-specific standard Inquiry bits 155 Unit Serial Number page 164 Standard Inquiry Data format 150 Progress Indication quick arbitration and selection 7...
Page 374 SCSI Interface Product Manual, Rev. B Read Retry Count reference model 7 Error Recovery page 204, 205 Reference Temperature Read Shared Temperature page 189 Persistent Reservation 244 regenerate 324 read transfer 324 Regenerate command 277, 278, 323 read/write heads 213 Regenerate Length read-write error recovery page 266 Regenerate command 277, 278...
Page 375 SCSI Interface Product Manual, Rev. B confirmation transaction 7 reset delay 27 response transaction 7 reset event 98 SCSI bus signal 14 reset hold time 27 Request Sense 25 reset to selection 27 request sense 121, 202, 203, 308 residual skew error 27 Request Sense command 27, 117, 129, 131, 171, response 7 266, 285, 290, 296, 321...
Page 376 SCSI Interface Product Manual, Rev. B SAP Block Point Numbers (major/minor) 166 SCSI device 7 SAP. see Servo Adaptive Parameters identifier 7 savable parameter 191 insertion 334 Save removal 334 Change Definition command 139 reservations 131 Save Control SCSI Firmware Release Number Change Definition command 139 Firmware Numbers page 164, 165, 166 save data pointer message 86, 126...
Page 377 SCSI Interface Product Manual, Rev. B selection phase 5 server 8 selection time-out delay 27 service 8 Self Seek delivery failure 8 Unit Attention Parameters page 202, 203 delivery port 8 self-monitoring analysis and reporting technology delivery subsystem 8 233, 329 delivery transaction 8 measurement 183 Service Action...
Page 378 SCSI Interface Product Manual, Rev. B single command example 125, 126 ST LVD phases 29 single initiator 14 stable error correction code syndrome 182 single target 14 standard inquiry data 202 single transition 8 format 283 single-ended 14 Standard Inquiry Data format 150 data signals 29 Standby Fast-10 26...
Page 379 SCSI Interface Product Manual, Rev. B Supported Log page 174 target save disable 172 Supported Log pages 188 target-resident entity 6 Supported Vital Product Data pages 163 task 6, 8, 127, 128, 258 Supported Vital Product Data pages 163 abort event 8 SURF address 8, 128 Format Parameters page 210...
Page 380 Prefetch command 248 Read 12 command 253 Read 16 command 255, 256 UAAERP. see Unit Attention AER Permission Read command 249 Ultra160 1 Read Extended command 251, 252 Ultra320 1 Write 10 command 314 unchangeable parameter 203 Write and Verify command 316...
Page 381 SCSI Interface Product Manual, Rev. B unconfirmed protocol service 9 Drive Standard Inquiry Data 154 unexpected bus free 123 Standard Inquiry Data format 150 condition 290 Vendor Specific Unit Attention ASCII Information page 159 Unit Attention Parameters page 202 Defect List header 144, 145 unit attention 202, 250, 252, 254, 256, 315 Drive Standard Inquiry Data 153 Unit Attention AER Permission...
Page 382 SCSI Interface Product Manual, Rev. B SPI-specific standard Inquiry bits 155 XPWrite target 327 Standard Inquiry Data format 150, 153 Wide Bus 32 Drive Standard Inquiry Data 153 Year of Manufacture wide data transfer request 202 Start-stop Cycle Counter page 186 wide data transfer request message 89 Wide SCSI Address 16 SPI-specific standard Inquiry bits 155...
Page 384 Seagate Technology LLC 920 Disc Drive, Scotts Valley, California 95066-4544, USA Publication Number: 75789509, Rev. B, Printed in USA...

This manual is also suitable for:

Ultra320

Seagate Ultra160 Product Manual

1 Interface Requirements

2 SCSI Bus

3 Logical Characteristics

4 Message System Specification

5 Miscellaneous SCSI Bus Characteristics

6 SPI Information Units

7 SCSI Commands

Quick Links

Related Manuals for Seagate Ultra160

Summary of Contents for Seagate Ultra160