Seagate SCSI Interface Product Manual

page of 276

/ 276
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SCSI Interface

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Product Manual, Volume 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Summary of Contents for Seagate SCSI Interface

Page 1 ........... . SCSI Interface .
Page 3 ..........SCSI Interface .
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, Inc.
Page 5 Revision status summary sheet Revision Authority Date Signature Sheets Affected A Issue 12/18/92 D. Ashby/ 1 thru 257. J. Averyt PLD:83345 8/18/93 1 thru 4, 4.1, 5 thru 193 deleted shs 194 thru 257. (Technical changes on pages 5, 9, 10, 78, 93, 94, 104-107, 109, 136, 139-142, 144, 147, 149, 161-164, 166, 167, 181, 185 thru 193.)
Page 7: Table Of Contents
SCSI Interface Product Manual, Rev. J Table of Contents Interface requirements ............1 How to use this interface manual .
Page 8 SCSI Interface Product Manual, Rev. J 3.1.5.2 Synchronous data transfer ........22 3.1.6...
Page 9 SCSI Interface Product Manual, Rev. J 4.7.1 Untagged task queuing ..........71 4.7.2...
Page 10 SCSI Interface Product Manual, Rev. J 5.16 Persistent Reserve Out command (5Fh) ........158 5.16.1...
Page 11 Seagate Technology support services ........
Page 13: List Of Figures
SCSI Interface Product Manual, Rev. J List of Figures Figure 1. Functional scope of SCSI-3 standards ......... . . 1 Figure 2.
Page 15: Interface Requirements
For information about features not included herein that the newer drives may support, refer to the standards listed in Section 1.1.1. This specification is designed to provide a universal detailed description of the SCSI interface for those drive products whose individual drive’s Product Manual, Volume 1, do not contain the details of how the SCSI inter- face is implemented by that drive.
Page 16: Applicable Standards
Specifications listed in Section 1.1.1. 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 bus (8 data + 1 parity or 16 data + 2 parity) plus 9 control signals supporting multiple initiators, disconnect/reconnect, self-configuring host software, automatic features that relieve the host from the necessity of knowing the physical architecture of the target (logical block addressing is used), and some other miscellaneous features.
Page 17: Glossary
SCSI Interface Product Manual, Rev. J 1157-D (SAM-3) should be well understood before reading operation descriptions in any SCSI docu- ment. Although a Glossary of terms is provided herein, the definitions may not be adequate for some. The SAM-3 specification gives a more detailed understanding of some of the new SCSI terminology.
Page 18 SCSI Interface Product Manual, Rev. J confirmation—A response returned to an object, which signals the completion of a service request. confirmed protocol service—A service available at the protocol service interface, which requires confirma- tion of completion. current task—A task that is in the process of sending messages, sending status, transferring data, or transfer- ring command data to or from the initiator.
Page 19 SCSI Interface Product Manual, Rev. J initiator—A SCSI device containing application clients which originate device service and task management requests to be processed by a target SCSI device. interconnect subsystem—One or more physical interconnects which appear as a single path for the transfer of information between SCSI devices in a domain.
Page 20 SCSI Interface Product Manual, Rev. J physical interconnect—A single physical pathway for the transfer of information between SCSI devices in a domain. port—Synonymous with “service delivery port.” A single attachment to a SCSI bus from a SCSI device. procedure—An operation that can be invoked through an external calling interface.
Page 21 SCSI Interface Product Manual, Rev. J service delivery port—A device-resident interface used by the application client, device server or task man- ager to enter and retrieve requests and responses from the service delivery subsystem. Synonymous with “port.” service delivery subsystem—That part of a SCSI I/O system which transmits service requests to a logical unit or target and returns logical unit or target responses to an initiator.
Page 22: Keywords
SCSI Interface Product Manual, Rev. J unlinked command—A SCSI-3 command having the link bit set to zero in the CDB control byte. upper level protocol—An application-specific protocol executed through services provided by a lower level protocol. 1.2.2 Keywords Several keywords are used to differentiate between different levels of requirements and optionality, as follows: vendor-specific—Specification of the referenced item is determined by the device vendor.
Page 23: Summary Of Scsi Commands And Messages
SCSI Interface Product Manual, Rev. J Summary of SCSI commands and messages Following is an alphabetical table listing the SCSI commands described in this manual. Details are given in Section 5.0. Command name Hex code Device type Page number Change Definition Format Unit dir.
Page 24 SCSI Interface Product Manual, Rev. J Following is an alphabetical summary of the SCSI messages described in this manual. Details are given in Section 3.5. Message Name Hex Code Page number Abort Abort Tag Bus Device Reset Clear Queue Command Complete...
Page 25: Scsi Bus
SCSI features supported by the drive described in the particular Product Manual being referenced. Communication on the SCSI Bus is allowed between only two SCSI devices at a time. Some Seagate drives support systems with a maximum of eight SCSI devices including the host computer(s) connected to the SCSI bus.
Page 26: Scsi Bus Signals
SCSI Interface Product Manual, Rev. J SCSI bus signals There are ten control and eighteen data signals, as listed below: · BSY · C/D · MSG · DIFFSNS (Multimode) (may sometimes be designated “DIFFSENS”) · SEL · I/O · REQ ·...
Page 27: Drive Select
Drives using the 16 bit data interface can have one of sixteen ID bits selected by installing 0 to 4 jumpers in a binary coded configuration on the drive select header. Drives that support SCAM protocol (SCSI Configured Automatically) can have their drive ID assigned via the SCSI interface (see Appendix A). 2.1.2 Signal values Signals may assume true or false values.
Page 28: Arbitration Delay (2.4 Μs)
SCSI Interface Product Manual, Rev. J SCSI ID: A unique data bit (the SCSI ID) shall be driven by each actively arbitrating SCSI device: the other seven data bits shall be released (i.e., not driven) by this SCSI device. The parity bit [DB(P), DB(P1)] may be undriven or driven to the true state, but shall never be driven to the false state during this phase.
Page 29: Deskew Delay (45 Ns)
SCSI Interface Product Manual, Rev. J 2.2.9 Deskew delay (45 ns) The minimum time required for deskew of certain signals. 2.2.10 Disconnection delay (200 µs) The minimum time that a target shall wait after releasing BSY before participating in an Arbitration phase when honoring a Disconnect message from the initiator.
Page 30: Fast Hold Time (10 Ns)
SCSI Interface Product Manual, Rev. J 2.3.4 Fast hold time (10 ns) This value is the minimum time added between the assertion of REQ or ACK and the changing of the data lines to provide hold time in the initiator or target respectively, while using fast synchronous data transfers.
Page 31: Logical Characteristics
SCSI Interface Product Manual, Rev. J Logical characteristics The operations of the SCSI bus as described in Section 3.0 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.
Page 32: Selection Phase
SCSI Interface Product Manual, Rev. J The procedure for a SCSI device to obtain control of the SCSI bus is as follows: 1. The SCSI device shall first wait for the Bus Free phase to occur. The Bus Free phase is detected when BSY and SEL are simultaneously and continuously negated for a minimum of a bus settle delay.
Page 33: Single Initiator Option
See SCAM initialization description in the SCAM Product Manual, part number 77767519. Upon recog- nizing SCAM selection, a SCAM device’s SCSI interface should respond by asserting SEL and MSG itself, then interrupting the device’s processor. SCAM target devices shall recognize and respond to SCAM selection whenever the device has neither been assigned a soft ID nor confirmed its current ID since power-on or a reset condition.
Page 34: Reselection Procedure
SCSI Interface Product Manual, Rev. J Reselection can be used only in systems that have Arbitration phase implemented. The drive implements the Reselection phase if the system is capable of supporting Reselection. ATN during Selection implies that the host supports messages other than command complete.
Page 35: Information Transfer Phases
SCSI Interface Product Manual, Rev. J 3.1.5 Information transfer phases Note. The Command, Data, Status, and Message phases are grouped together as information transfer phases because they are all used to transfer data or control information via the Data Bus. The actual contents of the information is beyond the scope of this section.
Page 36: Synchronous Data Transfer
SCSI Interface Product Manual, Rev. J 3.1.5.2 Synchronous data transfer Synchronous data transfer may be used only in the data phase if previously agreed to by the initiator and target through the message system (see Synchronous Data Transfer Request message in Section 3.5.3.2). The mes- sages determine the use of synchronous mode by both SCSI devices and establish a REQ/ACK offset and a transfer period.
Page 37: Status Phase
SCSI Interface Product Manual, Rev. J 3.1.8 Status phase The Status phase allows the target to request that it send status information to the initiator. See Section 4.3 for details. The target shall assert C/D and I/O and negate the MSG signal during the REQ/ACK handshake of this phase.
Page 38: Reset Condition
SCSI Interface Product Manual, Rev. J The initiator creates the Attention condition by asserting ATN at any time except during the Arbitration or Bus Free. The initiator shall assert the ATN signal two deskew delays before negating the ACK signal for the last byte transferred in a bus phase for the attention condition to be honored before transition to a new bus phase.
Page 39: Arbitrating Systems
SCSI Interface Product Manual, Rev. J 3.3.2 Arbitrating systems For systems in which the Arbitration phase is implemented, the allowable sequences are shown in Figure 4. The normal progression is from the Bus Free phase to Arbitration, from Arbitration to Selection or Reselection, and from Selection or Reselection to one or more of the information transfer phases (Command, Data, Status, or Message).
Page 40: Current Pointers
SCSI Interface Product Manual, Rev. J The SCSI architecture provides for sets of pointers to be kept within each initiator Path Control area (see Fig- ure 6). These pointers are in sets of three pointers per set. The pointers in each set point to three storage area sections in the initiator.
Page 41: Message System Specification
The message system allows communication between an initiator and target for the purpose of interface man- agement. For Seagate drives, the Logical Unit Number (LUN) (see Section 4.2.2) has always been zero. This may not be true on all future drives.
Page 42: Messages-General
SCSI Interface Product Manual, Rev. J 3.5.2 Messages—General The messages supported by the various drives are listed in a table in the individual drive’s Product Manual, Volume 1. Table 3 lists Messages that are defined by the SCSI protocol. The message code values are given a direction specification (In-Out).
Page 43: Message Details
SCSI Interface Product Manual, Rev. J The first message sent by the initiator after the Selection phase shall be an Identify, Abort, or Bus Device Reset message. If a target receives any other message, it shall go to Bus Free phase (unexpected Bus Free).
Page 44 SCSI Interface Product Manual, Rev. J Clear Task Set (0Eh) The target shall go to the Bus Free phase following successful receipt of the Clear Task Set message. The tar- get shall perform an action equivalent to receiving a series of Abort Task Set messages from each initiator. All tasks from all initiators in the task set for the specified logical unit shall be cleared from the task set.
Page 45: Initiator Detected Error
SCSI Interface Product Manual, Rev. J Identify (80h - FFh) The Identify message (Table 4) is sent by either the initiator or the target to establish an I T L nexus. Table 4. Identify message format Byte Identify DiscPriv LUNTAR LUNTRN The Identify bit shall be set to one to specify that this is an Identify message.
Page 46: Message Parity Error
SCSI Interface Product Manual, Rev. J Message Parity Error (09h) The Message Parity Error message is sent from the initiator to the target to indicate that the last message byte it received had a parity error. In order to indicate its intentions of sending this message, the initiator shall assert the ATN signal prior to its release of the ACK signal for the REQ/ACK handshake of the message that has the parity error.
Page 47: Head Of Queue Tag
SCSI Interface Product Manual, Rev. J Check Condition status. The sense key shall be set to Aborted Task and the additional sense code shall be set to Overlapped Tasks Attempted. Only one status is returned. Note. For each logical unit on each target, each initiator has up to 256 task tags to assign to tasks. A task tag becomes available for reassignment when the task ends.
Page 48: Extended Message (01H)
SCSI Interface Product Manual, Rev. J Target Transfer Disable (13h) The Target Transfer Disable (TDD) message is sent from an initiator to a target to request that subsequent reconnections for data transfer on the task be done by the initiator instead of the target. The target may recon- nect for other purposes, but shall not enter a data phase on a target reconnection.
Page 49 SCSI Interface Product Manual, Rev. J Table 7: Synchronous Data Transfer Request message format Byte Value Description Extended message Extended message length Synchronous Data Transfer Request code Transfer period factor [1] REQ/ACK offset Notes. See tables in the individual drive’s Product Manual, Volume 1, synchronous data transfer periods sup- ported section, for a list of transfer periods supported by the drive described therein.
Page 50 SCSI Interface Product Manual, Rev. J Responding device SDTR response Implied agreement 1. Non-zero REQ/ACK offset Synchronous transfer (i.e., each device transmits data with a trans- fer period equal to or less than the values received in the other device’s SDTR message) 2.
Page 51 SCSI Interface Product Manual, Rev. J Wide Data Transfer Request message A Wide Data Transfer Request (WDTR) message (Table 9) exchange shall be initiated by a SCSI device when- ever a previously-arranged transfer width agreement may have become invalid. The agreement becomes invalid after any condition which may leave the data transfer agreement in an indeterminate state, such as: 1.
Page 52: Figure 7. Wide Scsi Byte Ordering
SCSI Interface Product Manual, Rev. J sage Parity Error or Message Reject. In this case, both devices shall go to eight-bit data transfer mode for data transfers between the two devices. For the Message Parity Error case, the implied agreement shall be rein- stated if a re-transmittal of the second of the pair of messages is successfully accomplished.
Page 53 SCSI Interface Product Manual, Rev. J If the last data byte transferred for a command does not fall on the DB(15-8,P1) signals for a 16-bit wide trans- fer, then the values of the remaining higher-numbered bits are undefined. However, parity bits for these unde- fined bytes shall be valid for whatever data is placed on the bus.
Page 54: Message Exception Conditions Handling
SCSI Interface Product Manual, Rev. J Message exception conditions handling Table 12 attempts to clarify how to handle message exception conditions. The numbers in the grid spaces of Table 12 are response code numbers that are decoded and explained in note [4].
Page 55 SCSI Interface Product Manual, Rev. J In a multi-initiator or queued environment, an initiator’s attempt to prevent disconnection (by clearing the DiscPriv bit in the initial Identify message or in a subsequent Identify message, or by rejecting a Discon- nect message) may result in the target terminating the associated command with a status of Busy.
Page 56: System
SCSI Interface Product Manual, Rev. J S.M.A.R.T. system Some drive families mentioned in Section 1.1 implement what is called in the industry the S.M.A.R.T. system. S.M.A.R.T. is an acronym for Self-Monitoring Analysis and Reporting Technology. The intent of the S.M.A.R.T.
Page 57: Scsi Commands
SCSI Interface Product Manual, Rev. J SCSI commands This section defines the SCSI command structure and describes a typical SCSI bus procedure involving a command, status return, and message interchange. The command structure defined herein provides for a contiguous set of logical blocks of data to be transferred across the interface.
Page 58: Operation Code
SCSI Interface Product Manual, Rev. J 4.2.1 Operation code The operation code (Table 13) of the Command Descriptor Block has a group code field and a command code field. The three bit group code field provides for eight groups of command codes. The five bit command code field provides for thirty two command codes in each group.
Page 59: Logical Unit Number (Lun)
SCSI Interface Product Manual, Rev. J Table 15. Typical Command Descriptor Block for ten byte commands Byte Operation Code Logical Unit No. Reserved Logical Block Address (if required) (MSB) Logical Block Address (if required) Logical Block Address (if required) Logical Block Address (if required) (LSB)
Page 60: Transfer Length
SCSI Interface Product Manual, Rev. J 4.2.5 Transfer length The Transfer Length specifies the amount of data to be transferred, usually the number of blocks. For several commands the transfer length indicates the requested number of bytes to be sent as defined in the command description.
Page 61: Status
SCSI Interface Product Manual, Rev. J 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 17 and 18 unless the command is cleared by one of the following conditions: 1.
Page 62 SCSI Interface Product Manual, Rev. J Contingent Allegiance condition exists. The normal initiator recovery action is to issue the command again at a later time. Intermediate or Intermediate–Condition Met—This status shall be returned for every command in a series of...
Page 63: Command Examples
SCSI Interface Product Manual, Rev. J Command examples 4.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 8.
Page 64: Disconnect Example
SCSI Interface Product Manual, Rev. J 4.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 65: Timing Examples
SCSI Interface Product Manual, Rev. J 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. Timing waveforms to define these times are illustrated in Tables 19 through 33.
Page 66 SCSI Interface Product Manual, Rev. J Table 20: Arbitration, Selection (with ATN), and Message Out INIT ID INIT & TARG ID 1ST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 67 SCSI Interface Product Manual, Rev. J Table 21: Identify Msg Out to Command Phase IDENT MSG 1ST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 68 SCSI Interface Product Manual, Rev. J Table 22: Command Descriptor Block Transfer 1ST BYTE 2ND BYTE LAST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK T23.6.3 (etc. to T23.6.6)** T23.10.3 (etc. to T23.10.10)*** T23.6.2* T23.10.2** * and 8-15 if applicable...
Page 69 SCSI Interface Product Manual, Rev. J Table 23: Command Phase, Status Phase, Command Completed Msg and Bus Free LAST BYTE STATUS CMD COMPL 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 70 SCSI Interface Product Manual, Rev. J Table 24: Last Command Byte, Disconnect Msg, Bus Free, and Reselect LAST BYTE DISCON ARB ID 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 71 SCSI Interface Product Manual, Rev. J Table 25: Arbitration, Reselection, and Message In TARGET ID TARG & INIT ID IDENT MSG 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 72 SCSI Interface Product Manual, Rev. J Table 26: Reselect Identify Msg, Status Phase, Command Complete Msg, and Bus Free LAST BYTE STATUS CMD COMPL 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 73 SCSI Interface Product Manual, Rev. J Table 27: Last Command Byte to Data in Phase LAST BYTE 1ST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 74 SCSI Interface Product Manual, Rev. J Table 28: Last Command Byte to Data Out Phase LAST BYTE 1ST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK T07, T08 * and 8-15 if applicable...
Page 75 SCSI Interface Product Manual, Rev. J Table 29: Reselect Identify Msg to Data in Phase IDENT MSG 1ST BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 76 SCSI Interface Product Manual, Rev. J Table 30: Data in Block Transfer 1ST BYTE LAST BYTE 2ND BYTE 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 77 SCSI Interface Product Manual, Rev. J Table 31: Data Out Block Transfer 1ST BYTE LAST BYTE 0-7* 2ND BYTE -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 78 SCSI Interface Product Manual, Rev. J Table 32: Last Data Byte, Save Pointer Msg, and Disconnect Msg LAST BYTE SAVE PTR DISCON 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 79 SCSI Interface Product Manual, Rev. J Table 33: Data in Phase, Status Phase, Command Complete Msg, and Bus Free LAST BYTE STATUS CMD COMPL 0-7* -ATN -SEL -BUSY -I/O -MSG -C/D -REQ -ACK * and 8-15 if applicable...
Page 80: Command Processing Considerations And Exception Conditions
SCSI Interface Product Manual, Rev. J Command processing considerations and exception conditions The following clauses describe some exception conditions and errors associated with command processing and the sequencing of commands. 4.6.1 Auto Contingent Allegiance or Contingent Allegiance The auto contingent allegiance (NACA=1, see Section 4.2.6) or contingent allegiance (NACA=0) condition shall exist within the task set when the logical unit completes a command by returning a Check Condition sta- tus (see Section 4.3).
Page 81: Clearing An Auto Contingent Allegiance Condition
SCSI Interface Product Manual, Rev. J siderations described in T10/1157D, clause 7, “Task Set Management.”) shall affect acceptance into the task set or rejection for a task from that initiator. 4.6.1.2 Clearing an Auto Contingent Allegiance condition If the NACA bit is set to zero in the Control byte of the faulting command, then the SCSI-2 rules for clearing contingent allegiance shall apply.
Page 82: Sense Data
SCSI Interface Product Manual, Rev. J 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 83: Autosense
SCSI Interface Product Manual, Rev. J status on a subsequent command, but not both. Notification of an error condition encountered after command completion shall be returned only to the initiator that sent the affected task or tasks. Asynchronous event reports may be used to notify devices that a system resource has become available. If a logical unit uses this method of reporting, the sense key in the AER sense data shall be set to Unit Attention.
Page 84: Target Hard Reset
SCSI Interface Product Manual, Rev. J Logical units may queue unit attention conditions. After the first unit attention condition is cleared, another unit attention condition may exist (e.g., a power on condition followed by a microcode change condition). The Unit Attention condition for a particular initiator is cleared when that initiator does one of the following: 1.
Page 85: Queued Tasks (Formerly "Queued I/O Processes")
SCSI Interface Product Manual, Rev. J Queued tasks (formerly “Queued I/O Processes”) Queuing of tasks allows a drive to accept multiple commands for execution at a later time. There are two methods for implementation of queuing, tagged and untagged. Tagged task queuing allows the drive to accept multiple commands from each initiator.
Page 86: Parameter Rounding
SCSI Interface Product Manual, Rev. J The Control Mode page specifies alternative queue management algorithms with additional rules on the order of execution of commands (see Table 96). A task received from an initiator without a task queue tag message while there are any tagged I/O commands in the command queue from that initiator is an incorrect initiator connection, unless there is a contingent alle- giance condition.
Page 87: Incorrect Initiator Connection
SCSI Interface Product Manual, Rev. J Each logical unit begins at a particular operating definition. If the logical unit supports the Change Definition command, the present operating definition can be changed to any other operating definition supported by the logical unit. The actual details of the operating definition of a logical unit are vendor-specific. If the operating definition is changed to one that does not include the Change Definition command, the target continues to accept the Change Definition command.
Page 89: Command Descriptions
SCSI Interface Product Manual, Rev. J Command descriptions Two types of commands are supported by the drive: commands for all devices; and commands for direct access devices. In each of these categories, the drive supports only Group 0, Group 1, and Group 2 com- mands.
Page 90 SCSI Interface Product Manual, Rev. J Table 34. Commands sorted by command name Command type Length Command Command name operation Reference Direct access code devices devices bytes bytes bytes Change Definition 5.1 (see page 78) Compare 5.2 (see page 79) Copy 5.3 (see page 79)
Page 91 SCSI Interface Product Manual, Rev. J Table 35. Commands sorted by operation code Command type Length Command operation Command name Reference Direct access All devices code devices bytes bytes bytes Test Unit Ready 5.47 (see page 211) Rezero Unit 5.37 (see page 203) Request Sense 5.34 (see page 191)
Page 92: Change Definition Command (40H)
SCSI Interface Product Manual, Rev. J Change Definition command (40h) The Change Definition command (Table 36) modifies the operating definition of the drive with respect to com- mands from all initiators. The drive maintains only one operating definition and it applies to all initiators in the system.
Page 93: Compare Command (39H)
SCSI Interface Product Manual, Rev. J It is permissible for a SCSI-2 device that has its definition changed to a SCSI-1 device to accept a Change Def- inition command. If the Change Definition command is not executed successfully for any reason, the operating definition shall remain the same as it was before the Change Definition command was attempted.
Page 94: Format Unit Command (04H)
SCSI Interface Product Manual, Rev. J Format Unit command (04h) The Format Unit command (Table 38) 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 95: 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 96 SCSI Interface Product Manual, Rev. J Table 39: Format Unit parameter definition (format variations) CDB-Byte (see Table 38) 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 97: 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 98: Initialization Pattern Descriptor
SCSI Interface Product Manual, Rev. J Initialization Pattern (IP). An IP bit of one indicates that an initialization pattern descriptor is included in the Format Unit parameter list immediately following the defect list header. An IP bit of zero indicates that an initialization pattern descriptor is not included and that the target uses its default initialization pattern.
Page 99: Defect List Formats
This section describes the format of the defect list that follows the Defect List Header described in Table 41. 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 46) •...
Page 100 SCSI Interface Product Manual, Rev. J The Defect Descriptors shall be in ascending order. The drive may return Check Condition if the defect descrip- tors 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 considered the least significant part of the address.
Page 101: Inquiry Command (12H)
SCSI Interface Product Manual, Rev. J Inquiry command (12h) The Inquiry command requests that information regarding parameters of the drive be sent to the initiator. An option Enable Vital Product Data (EVPD) allows the initiator to request additional information about the drive.
Page 102: Drive Standard Inquiry Data
SCSI Interface Product Manual, Rev. J 5.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 49.
Page 103 SCSI Interface Product Manual, Rev. J Table 50: ANSI-approved version Code Description The device does not claim conformance to any standard. Obsolete (formerly SCSI-1). The device complies to ANSI X3.131-1994 (SCSI-2). The device complies to ANSI X3.301-1997. The device complies to ANSI T10/1236.
Page 104 XXXXXXXX is the drive serial number. [30] The reserved area from byte 56 through byte 95 is filled with 00h. [31] The Copyright Notice field contains the 48 bytes of ASCII data “Copyright (c) 199X Seagate All rights reserved,” where “X” indicates the current year.
Page 105: Vital Product Data
SCSI Interface Product Manual, Rev. J 5.6.2 Vital Product Data pages The initiator requests the vital product data information by setting the EVPD bit to one and specifying the page code of the desired vital product data. If the drive does not implement the requested page, it shall return Check Condition status.
Page 106: Unit Serial Number Page (80H)
SCSI Interface Product Manual, Rev. J 5.6.3 Unit Serial Number page (80h) Table 54: Unit Serial Number page (80h) Byte Peripheral Qualifier [1] Peripheral Device Type [1] Page Code (80h) [2] Page Length [3] Product Serial Number [4] Board Serial Number [5] Notes.
Page 107: Device Identification Page (83H)
SCSI Interface Product Manual, Rev. J Page 81h defines the current operating definition, the default operating definition, and which operating definitions are implemented by the drive. These operating definition values are specified in the Change Definition command (see Table 36).
Page 108 SCSI Interface Product Manual, Rev. J (83h) Table 57: Device Identification page Byte Peripheral Qualifier [1] Peripheral Device Type [1] Page Code (83h) Reserved Page Length (n–3) Identification Descriptor List [2] Identification Descriptor (First) Identification Descriptor (Last) Notes. The Peripheral Qualifier field and Peripheral Device Type field value of 00h indicates a direct-access device (magnetic disc) is connected to this logical unit.
Page 109 SCSI Interface Product Manual, Rev. J The Association field specifies the entity with which the Identifier field is associated, as described in Table Table 60: Association Value Description The Identifier field is associated with the addressed physical or logical device.
Page 110: Firmware Numbers Page (C0H)
SCSI Interface Product Manual, Rev. J Table 62: Device identification page example Bytes Hexadecimal values ASCII values 00–15 00 83 00 32 02 01 00 22 58 59 5A 5F 43 6F 72 70 ...2...XYZ_Corp 16–31 53 75 70 65...
Page 111 SCSI Interface Product Manual, Rev. J Table 64: Firmware Numbers page (C0h) (Applies to model families [5][9] other than those covered by Table 63) Byte Peripheral Qualifier [1] Peripheral Device Type [1] Page Code (C0h) [2] Page Length [3] SCSI Firmware Release Number [4]...
Page 112: Date Code Page (C1H)
SCSI Interface Product Manual, Rev. J 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. The low order word of this field con- tains a binary code which corresponds to the Product Family Member ID.
Page 113: Jumper Settings Page (C2H)
SCSI Interface Product Manual, Rev. J 5.6.8 Jumper Settings page (C2h) Table 66: 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]...
Page 114 SCSI Interface Product Manual, Rev. J 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 115: Device Behavior Page (C3H)
SCSI Interface Product Manual, Rev. J 5.6.9 Device Behavior page (C3h) The Device Behavior page (Table 67) will be used by the regression tests to determine what behavior should be expected from a particular firmware package. Table 67: Device Behavior page (C3h)
Page 116: Log Select Command (4Ch)
SCSI Interface Product Manual, Rev. J Log Select command (4Ch) The Log Select command provides a means for an initiator to manage statistical information about the drive operation. 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 117 SCSI Interface Product Manual, Rev. J 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 118 SCSI Interface Product Manual, Rev. J The Log Sense command and its Data In phase also use the format of Table 70, so explanations pertaining to the table apply generally to both Log Select and Log Sense commands, with differences noted. However, only one log page is selected and returned with each Log Sense command (see Section 5.9).
Page 119 SCSI Interface Product Manual, Rev. J Table 71: Log Parameters Byte (MSB) Parameter Code [1] (LSB) DU [2] DS [3] TSD [4] ETC [5] TMC [6] Reserved LP [7] Parameter Length (n-3 bytes) [8] – – – – Parameter Value [9] –...
Page 120 SCSI Interface Product Manual, Rev. J Enable Threshold Comparison (ETC). A one indicates that a comparison to the threshold value is per- formed whenever the cumulative value is updated. A bit of zero indicates the comparison is not performed. The value of the ETC bit is the same for both the threshold and cumulative parameters.
Page 121: Write, Read, And Verify Error Counter Pages (02H, 03H, And 05H)
SCSI Interface Product Manual, Rev. J The page code assignments for the log pages are listed in Table 73. Detailed descriptions follow the table. Table 73: Log Page codes Page Code Description Section Page Error Counter page (Write) 5.8.1 Error Counter page (Read) 5.8.1...
Page 122: Non-Medium Error Page (06H)
SCSI Interface Product Manual, Rev. J Total Times Correction Algorithm Processed. This parameter code specifies the counter that counts the total number of retries, or “times the retry algorithm is invoked.” If after five attempts a counter 02h type error is recovered, then five is added to this counter. If three retries are required to get a stable ECC syndrome before a counter 01h type error is corrected, then those three retries are also counted here.
Page 123: Factory Log Page (3Eh)
SCSI Interface Product Manual, Rev. J 5.8.4 Factory Log page (3Eh) Log page code 3Eh specifies factory status parameters. Table 77: Factory Log page (3Eh) Byte Parameter Code [1] [2] Notes. Parameter Code 0000h–Power-on Time. This parameter code represents the number of drive power-on minutes.
Page 124: Log Sense Command (4Dh)
SCSI Interface Product Manual, Rev. J Log Sense command (4Dh) The Log Sense command provides a means for an initiator to retrieve statistical information maintained 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 com- mand.
Page 125 SCSI Interface Product Manual, Rev. J Table 79 (Page Code 00h) returns the list of log pages that the drive supports. This page is not defined for the Log Select command. Table 79: Supported Log pages Byte Reserved Page Code (00h)
Page 126: Mode Select (6) Command (15H)
SCSI Interface Product Manual, Rev. J 5.10 Mode Select (6) command (15h) The Mode Select (6) command (Table 80) 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 5.2.1.10).
Page 127 SCSI Interface Product Manual, Rev. J mand. (The host shall not be penalized by values not changeable by the host which have a target “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 128: Mode Select
Page Codes. Note. See individual drive’s Product Manual, Volume 1, section “SCSI Interface commands supported,” for a table showing the mode pages that a particular drive implements. The table shows the default parame- ters for pages that are implemented and shows which mode parameters are changeable by that drive...
Page 129 SCSI Interface Product Manual, Rev. J Table 83: Mode Sense page codes supported Page Code Description Unit Attention page parameters (should be sent last in a group of Mode pages) Error Recovery parameters Disconnect/Reconnect Control parameters Format parameters Rigid Drive Geometry parameters...
Page 130: Mode Select (10) Command (55H)
SCSI Interface Product Manual, Rev. J 5.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 param- eters to the drive. Initiators should issue Mode Sense prior to Mode Select to determine supported pages, page lengths, and other parameters.
Page 131 SCSI Interface Product Manual, Rev. J c. If an initiator attempts to send a page with a length not equal to the parameter length reported for that page by the Mode Sense command. 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 [5] of Table 101).
Page 132 SCSI Interface Product Manual, Rev. J ters. A Block Descriptor Length of zero indicates that no block descriptors shall be included in the param- eter list. This condition shall not be considered an error. a. For drives that do not support capacity programming, the Density Code shall be 00h to define the default density of medium.
Page 133: 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 134 SCSI Interface Product Manual, Rev. J 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 Prod-...
Page 135 SCSI Interface Product Manual, Rev. J Table 88: 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]...
Page 136: Mode Sense Page Descriptor Header
SCSI Interface Product Manual, Rev. J The Block Length, as defined after a format function, specifies the length in bytes of each logical block described by the Block Descriptor. Default is 512 if no Mode Select command is received before the For- mat command.
Page 137: Error Recovery Page (01H)
SCSI Interface Product Manual, Rev. J 5.12.2 Error Recovery page (01h) The drive Error Recovery page implementation is defined in Table 90. This table summarizes the function, the default value, and changeability status for each byte/bit. Table 90: Error Recovery page (01h)
Page 138 SCSI Interface Product Manual, Rev. J The Automatic Write Reallocation of defective data blocks Enabled (AWRE) bit, when set to one, allows the drive to automatically relocate bad blocks detected during write operations. The drive performs the automatic write reallocation only if the drive has the valid data (e.g., original data in the buffer or recovered from the medium).
Page 139 SCSI Interface Product Manual, Rev. J effort. Each level may consist of multiple error recovery steps. See individual drive’s Product Manual, Vol- ume 1, for more details on the levels of error recovery available. [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.
Page 140: Disconnect/Reconnect Control Page (02H)
SCSI Interface Product Manual, Rev. J 5.12.3 Disconnect/Reconnect Control page (02h) The Disconnect/Reconnect Page implementation is defined in Table 91. This table summarizes the function and defines the default value and changeable status. Table 91: Disconnect/Reconnect Control page (02h) Byte...
Page 141 The sense key shall be set to Illegal Request and the additional sense code set to Illegal Field In Parame- ter 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 142: Format Parameters Page (03H)
SCSI Interface Product Manual, Rev. J 5.12.4 Format Parameters page (03h) The Format Parameters page implementation is defined in Table 92. 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 143 SCSI Interface Product Manual, Rev. J Notes. 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 144: Rigid Drive Geometry Parameters Page (04H)
SCSI Interface Product Manual, Rev. J 5.12.5 Rigid Drive Geometry Parameters page (04h) The Rigid Drive Geometry Parameters page implementation is defined in Table 93. This table summarizes the function and defines the default value Table 93. Rigid Drive Geometry Parameters page (04h)
Page 145 SCSI Interface Product Manual, Rev. J Table 93. Rigid Drive Geometry Parameters page (04h) (continued) Byte (MSB) Medium Rotation Rate [7] (LSB) Changeable [8] Default Reserved Changeable [8] Default Reserved Changeable [8] Notes. 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 146: Verify Error Recovery Page (07H)
SCSI Interface Product Manual, Rev. J 5.12.6 Verify Error Recovery page (07h) The Verify Error Recovery page (Table 94) specifies the error recovery parameters the target shall use during the Verify command and the verify operation of the Write and Verify command.
Page 147 SCSI Interface Product Manual, Rev. J Notes. 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 148: Caching Parameters Page (08H)
SCSI Interface Product Manual, Rev. J 5.12.7 Caching Parameters page (08h) The Caching Parameters page for Mode Sense/Mode Select defines the parameters that affect the use of the cache (Table 95). Table 95: Caching Parameters page (08h) Byte Page Descriptor Header...
Page 149 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 cache according to size of segment, but rather by number of segments, this bit is used to enable or dis- able ARLA (in non-Seagate equipment, this might be used to designate cache size).
Page 150 SCSI Interface Product Manual, Rev. J [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 151: Control Mode Page (0Ah)
SCSI Interface Product Manual, Rev. J 5.12.8 Control Mode page (0Ah) The Mode Sense/Mode Select Control Mode page (Table 96) provides controls over several SCSI-2 features which are applicable to all device types such as tagged queuing, extended contingent allegiance, asynchro- nous event notification, and error logging.
Page 152 SCSI Interface Product Manual, Rev. J The Queue Algorithm Modifier field specifies restrictions on the algorithm used for re-ordering commands that are tagged with the Simple Queue Tag message. Table 97: Queue Algorithm Modifier Value Definition Guaranteed data integrity: Requires the device to order the actual execution sequence of the queued command such that data integrity is guaranteed at any time.
Page 153: Notch Page (0Ch)
SCSI Interface Product Manual, Rev. J 5.12.9 Notch page (0Ch) The Notch page (Table 98) 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 154 SCSI Interface Product Manual, Rev. J active notch shall be greater than or equal to 0 and less than or equal to the maximum number of notches. An active notch value of zero indicates that this and subsequent Mode Select and Mode Sense com- mands refer to the parameters that apply across all notches.
Page 155: Power Condition Page (0Dh Or 1Ah)
SCSI Interface Product Manual, Rev. J 5.12.10 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 156: Xor Control Mode Page (10H)
SCSI Interface Product Manual, Rev. J 5.12.11 Xor Control Mode page (10h) The Xor Control Mode page (Table 100) provides the initiator with the means to obtain or modify certain Xor operating parameters of the target. Table 100: Xor Control Mode page (10h)
Page 157 SCSI Interface Product Manual, Rev. J The Rebuild Delay field specifies the minimum time in milliseconds between successive Read commands during a rebuild operation. See individual drive’s Product Manual, Volume 1, Mode Sense Data section, for a table showing codes...
Page 158: Unit Attention Parameters Page (00H)
SCSI Interface Product Manual, Rev. J 5.12.12 Unit Attention Parameters page (00h) The Unit Attention Parameters page is the last page to be reported by the drive. Table 101: Unit Attention Parameters page (00h) Byte PS [10] Page Code (00h)
Page 159 Caching Page (08h) Length from 12h to 0Ah. These bits are reserved for future compatibility with Seagate host adapters. Though they presently may be changeable, (see note [7]) 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 160: Informational Exceptions Control Page (1Ch)
SCSI Interface Product Manual, Rev. J 5.12.13 Informational Exceptions Control page (1Ch) The Informational Exceptions Control page (Table 102) 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 161 The maintaining of the Interval Timer and the 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 162 SCSI Interface Product Manual, Rev. J Table 103: Format of Method of Reporting Informational Exceptions (MRIE) field Code 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-3 Archi- tectural Model and the relevant Protocol Standard.
Page 163: 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 164 SCSI Interface Product Manual, Rev. J 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 Prod-...
Page 165 SCSI Interface Product Manual, Rev. J Table 106: 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]...
Page 166: Move Medium Command (A7H)
SCSI Interface Product Manual, Rev. J A Number of Blocks 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 167: Persistent Reserve In Command (5Eh)
SCSI Interface Product Manual, Rev. J 5.15 Persistent Reserve In command (5Eh) The Persistent Reserve In command (see Table 107) is used to obtain information about persistent reserva- tions and reservation keys that are active within a device server. This command is used in conjunction with the Persistent Reserve Out command (see Section 5.16).
Page 168: Persistent Reserve In Parameter Data For Read Keys
SCSI Interface Product Manual, Rev. J Table 108: 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 169: Persistent Reserve In Parameter Data For Read Reservations
SCSI Interface Product Manual, Rev. J The Generation value allows the application client examining the generation value to verify that the config- uration of the initiators attached to a logical unit has not been modified by another application client with- out the knowledge of the examining application client.
Page 170 SCSI Interface Product Manual, Rev. J Table 111: 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] Notes. If a persistent reservation is present in the logical unit that does contain elements, there shall be a Reser-...
Page 171 SCSI Interface Product Manual, Rev. J Table 113: 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 172: Persistent Reserve Out Command (5Fh)
SCSI Interface Product Manual, Rev. J 5.16 Persistent Reserve Out command (5Fh) The Persistent Reserve Out command (see Table 114) 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 173: Persistent Reserve Out Parameter List
SCSI Interface Product Manual, Rev. J Table 115: 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, Section 5.3, for details.
Page 174 SCSI Interface Product Manual, Rev. J The Service Action Reservation Key field contains information needed for three service actions; the Reg- ister, Preempt, and Preempt and Clear service actions. For the Register service action, the Service Action Reservation key field contains the new reservation key to be registered. For the Preempt 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 175: Prefetch Command (34H)
SCSI Interface Product Manual, Rev. J 5.17 Prefetch command (34h) The Prefetch command (Table 118) 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 118:...
Page 176: Read Command (08H)
SCSI Interface Product Manual, Rev. J 5.19 Read command (08h) The Read command (Table 119) requests that the drive transfer data to the initiator. Table 119: Read command (08h) Byte Logical Block Address (MSB) [2] Logical Unit Number [1] Logical Block Address...
Page 177 SCSI Interface Product Manual, Rev. J 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 178: Read Buffer Command (3Ch)
SCSI Interface Product Manual, Rev. J 5.20 Read Buffer command (3Ch) The Read Buffer command is used in conjunction with the Write Buffer command as a diagnostic function for testing drive memory and the SCSI bus integrity. This command shall not alter the medium. Command format is shown in Table 120.
Page 179: Read Combined Descriptor Header And Data Mode (0000B)
SCSI Interface Product Manual, Rev. J 5.20.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 39).
Page 180: Read Data From Echo Buffer Mode (1010B)
SCSI Interface Product Manual, Rev. J 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 123. Table 123: Buffer Offset Boundary Offset...
Page 181: Read Capacity Command (25H)
SCSI Interface Product Manual, Rev. J 5.21 Read Capacity command (25h) The Read Capacity command (Table 125) provides a means for the initiator to request the capacity of the drive information. Table 125: Read Capacity command (25h) Byte RelAdr [2]...
Page 182 SCSI Interface Product Manual, Rev. J 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 126. Table 126: Read Capacity Data...
Page 183: Read Defect Data (10) Command (37H)
SCSI Interface Product Manual, Rev. J 5.22 Read Defect Data (10) command (37h) The Read Defect Data (10) command requests that the target transfer the medium defect data to the initiator. If the drive is unable to access any medium defect data, it terminates the command with Check Condition status.
Page 184 SCSI Interface Product Manual, Rev. J the Allocation Length bytes have been transferred or when all available defect data has been transferred to the initiator, whichever is less. See “Control byte,” paragraph 4.2.6. This command is intended to be used only with the Format Unit command (Section 5.5). The initiator should not interpret or act upon this list except to resend this list as defect data in a Format Unit command.
Page 185: Read Defect Data (12) Command (B7H)
SCSI Interface Product Manual, Rev. J 5.23 Read Defect Data (12) command (B7h) The Read Defect Data (12) command (see Table 129) 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 an initiator other then the one holding a logical unit reservation.
Page 186: Read Element Status Command (B4H)
SCSI Interface Product Manual, Rev. J Allocation Length specifies the number of bytes the initiator has allocated for the returned defect data. An Allocation Length of zero indicates that no Read Defect Data shall be transferred. Any other value indi- cates the maximum number of bytes to be transferred.
Page 187: Read Extended Command (28H)
SCSI Interface Product Manual, Rev. J 5.25 Read Extended command (28h) The Read Extended command requests that the target transfer data to the initiator. This command is imple- mented with the drive specific parameters shown in Table 131. This command operates the same as the Read command (see Section 5.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 188 SCSI Interface Product Manual, Rev. J The Logical Block Address specifies the logical block at which the read operation shall begin, if RelAdr bit is zero (see note [4]). The Transfer Length specifies the number of contiguous logical blocks of data that shall be transferred. A Transfer Length of zero indicates that no logical blocks shall be transferred.
Page 189: Read Long Command (3Eh)
SCSI Interface Product Manual, Rev. J 5.26 Read Long command (3Eh) The Read Long command (Table 132) 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 logical block addressed by the command.
Page 190: Reassign Blocks Command (07H)
SCSI Interface Product Manual, Rev. J 5.27 Reassign Blocks command (07h) The Reassign Blocks command (Table 133) 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 logical block addresses to be reassigned.
Page 191: Reassign Blocks Defect List
SCSI Interface Product Manual, Rev. J 5.27.1 Reassign Blocks defect list The Reassign Blocks defect list (Table 134) contains a four byte header followed by one or more Defect Descriptors. The length of each Defect Descriptor is four bytes. Table 134:...
Page 192: Rebuild Command (81H)
SCSI Interface Product Manual, Rev. J 5.28 Rebuild command (81h) The Rebuild command (Table 135) 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 193: Rebuild And Regenerate Parameter Data
SCSI Interface Product Manual, Rev. J The Port Control field is defined in Table 136. 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 status. The sense data shall be set to Illegal Request: Invalid Field in CDB.
Page 194 SCSI Interface Product Manual, Rev. J The Pad field contains invalid data and shall be ignored. Note. The Pad field is included to accommodate initiators which require the intermediate data to be aligned on a particular memory boundary. The Intermediate Data field contains data that shall be used in the Xor operation with the data from the specified source devices.
Page 195: Receive Diagnostic Results Command (1Ch)
SCSI Interface Product Manual, Rev. J 5.29 Receive Diagnostic Results command (1Ch) The Receive Diagnostic Results command requests analysis data be sent to the initiator after completion of a Send Diagnostic command. The drive supports the optional Page format, wherein the initiator sends additional pages after a Send Diagnostic command.
Page 196 The Error Code is a two byte value that provides information designating which part of a diagnostic opera- tion 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 197: Supported Diagnostic
SCSI Interface Product Manual, Rev. J 5.29.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 141 after receiving the Receive Diagnostic Results command. It lists all of the diagnostics pages supported by the drive.
Page 198 SCSI Interface Product Manual, Rev. J A Reserved Area (RAREA) bit of one indicates that all or part of the translated address falls within a reserved area of the medium (e.g., speed tolerance gap, alternate logical block, vendor reserved area, etc.).
Page 199: Regenerate Command (82H)
SCSI Interface Product Manual, Rev. J 5.30 Regenerate command (82h) The Regenerate command (see Table 145) requests that the target write to the buffer the Xor data generated 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 200 SCSI Interface Product Manual, Rev. J The Logical Block Address field specifies the starting logical block address for the target to read data from its own medium. This data is a source for the regenerate operation. The Regenerate Length field indicates the length in logical blocks of the resulting Xor data. It also speci- fies the length in logical blocks that is transferred from each of the specified sources.
Page 201: Release (6) Command (17H)
The drive may not support extent reservations, in which case this bit must always be zero. Since the Reserva- tion Identification byte is valid only for extent reservations, the drive ignores this byte when it does not support extent release. Check individual drive’s Product Manual, Volume 1, section “SCSI Interface commands sup- ported” for support of this command.
Page 202: Release (10) Command (57H)
If bit 4 is zero, byte 3 is zero. If bit 4 is one, byte 3 identifies the SCSI bus ID of the device that reserves the drive. Must be zero. Must be zero if not supported. Check with individual drive’s Product Manual, Volume 1, SCSI Interface commands supported section (see paragraph 5.35.1 of this volume). See “Control byte,” paragraph 4.2.6.
Page 203: Report Luns Command (A0H)
SCSI Interface Product Manual, Rev. J 5.33 Report LUNs command (A0h) The Report LUNs command (see Table 149) 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 204 SCSI Interface Product Manual, Rev. J The device server shall report the logical unit numbers of configured logical units using the format shown in Table 150. Table 150: Report LUNs parameter list format Byte (MSB) LUN List Length (n-7) [1]...
Page 205: Request Sense Command (03H)
SCSI Interface Product Manual, Rev. J 5.34 Request Sense command (03h) The Request Sense command (Table 151) requests that the drive transfer sense data to the initiator in the for- mat shown in Table 152. The sense data shall be valid for a Check Condition status returned on the prior com- mand.
Page 206: Extended Sense Data Format
SCSI Interface Product Manual, Rev. J 5.34.1 Extended Sense Data Format The drive is capable of sending 18 bytes of extended sense data, and does send 18 bytes if the Allocation Length of the Request Sense command is equal to or greater than 18 bytes (otherwise, the number of bytes specified by the Allocation Length are sent).
Page 207 SCSI Interface Product Manual, Rev. J cal block. For example, if the Sense Key is Medium Error, it is the Logical Block Address of the failure block. Additional Sense Length—Specifies additional sense bytes are to follow. This is limited to a maximum of 10 (decimal) additional bytes.
Page 208 SCSI Interface Product Manual, Rev. J The Actual Retry Count field returns implementation specific information on the actual number of retries used in attempting to recover an error or exception condition. Not all drives implement reporting actual retry count in bytes 15, 16, and 17. See individual drive’s Product Manual, Volume 1.
Page 209: Sense Keys
Hardware Error—Indicates the drive detected a non-recoverable hardware failure while performing the command or during a self-test. This includes SCSI interface parity error, controller failure, device failure, etc.
Page 210: Extended Sense, Additional Sense And Additional Sense Qualifier Codes
SCSI Interface Product Manual, Rev. J 5.34.3 Extended Sense, Additional Sense and Additional Sense Qualifier codes Table 157 lists the Extended Sense, Additional Sense and Additional Sense Qualifier codes. Note. Table 157 is for reference only, as not all drives listed on the cover of this manual support all of the codes listed.
Page 211 SCSI Interface Product Manual, Rev. J Table 157: Error codes for bytes 12 and 13 of Sense Data (values are in hexadecimal) (continued) Byte Byte Description Recovered Data Using Negative Offset Recovered Data Using Previous Logical Block ID Recovered Data Without ECC—Data Auto Reallocated...
Page 212 SCSI Interface Product Manual, Rev. J Table 157: Error codes for bytes 12 and 13 of Sense Data (values are in hexadecimal) (continued) Byte Byte Description Command Sequence Error Tagged Commands Cleared By Another Initiator Medium Format Corrupted Format Failed...
Page 213: Deferred Errors
SCSI Interface Product Manual, Rev. J 5.34.3.1 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 214: Reserve (6) Command (16H)
Interface commands supported.” Reserve Identification applies only if Extent is supported. This field must be zero if not supported. Check with individual drive’s Product Manual, Volume 1, section “SCSI Interface commands supported” (also see paragraphs 5.35.1 and 5.35.2 in this volume).
Page 215: Third Party Reservation
SCSI Interface Product Manual, Rev. J 5.35.3 Third Party Reservation The third party reservation option for the Reserve command allows an initiator 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 5.31.3).
Page 216: Reserve (10) Command (56H)
SCSI Interface Product Manual, Rev. J 5.36 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 160) is used to reserve a logical unit or, if the extent reserva- tion option is implemented, extents within a logical unit.
Page 217: Rezero Unit Command (01H)
SCSI Interface Product Manual, Rev. J 5.37 Rezero Unit command (01h) The Rezero Unit command (Table 161) 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 218: Seek Command (0Bh)
SCSI Interface Product Manual, Rev. J 5.41 Seek command (0Bh) The Seek command (Table 162) 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 219: Seek Extended Command (2Bh)
SCSI Interface Product Manual, Rev. J 5.42 Seek Extended command (2Bh) The Seek Extended command requests that the drive seek to the specified Logical Block Address. This com- mand is implemented with the drive specific parameters listed in Table 163.
Page 220: Send Diagnostic Command (1Dh)
SCSI Interface Product Manual, Rev. J 5.43 Send Diagnostic command (1Dh) The Send Diagnostic command requests that the drive perform diagnostic tests on itself or perform other op- tional operations. Table 164 shows the format of the Send Diagnostics command as implemented by the drive.
Page 221: Supported Diagnostic Page-Send Diagnostic
SCSI Interface Product Manual, Rev. J 5.43.1 Supported Diagnostic page—Send Diagnostic The Supported Diagnostic page (Table 165) 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 141).
Page 222: Set Limits Command (33H)
SCSI Interface Product Manual, Rev. J 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 143 and Table 144.
Page 223: Start/Stop Unit Command (1Bh)
Write Data Buffer Read Data Buffer The remaining commands (see individual drive’s Product Manual, Volume 1, SCSI interface commands sup- ported section, for a list of all commands supported) cannot be executed until after the drive has spindled up. If the drive receives one of these commands before it can be executed, a Check Condition status is returned (with sense key of Not Ready).
Page 224: Synchronize Cache Command (35H)
SCSI Interface Product Manual, Rev. J 5.46 Synchronize Cache command (35h) The Synchronize Cache command (Table 168) 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 225: Test Unit Ready Command (00H)
SCSI Interface Product Manual, Rev. J 5.47 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 226: Verify Command (2Fh)
SCSI Interface Product Manual, Rev. J 5.48 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 170. The drive disconnects while this command is being executed if the initiator supports disconnect/reconnect.
Page 227: Write Command (0Ah)
SCSI Interface Product Manual, Rev. J 5.49 Write command (0Ah) The Write command (Table 171) requests that the drive write, to the medium, the data transferred by the initia- tor. Table 171: Write command (0Ah) Byte Logical Block Address (MSB) [2]...
Page 228: Write And Verify Command (2Eh)
SCSI Interface Product Manual, Rev. J 5.50 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 229: Write Buffer Command (3Bh)
SCSI Interface Product Manual, Rev. J 5.51 Write Buffer command (3Bh) The Write Buffer command may be used in conjunction with the Read Buffer command as a diagnostic 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 230: Combined Header And Data Mode (0000B)
SCSI Interface Product Manual, Rev. J 5.51.1 Combined Header and Data mode (0000b) In this mode, data to be written to the drive’s data buffer is preceded by a four byte header. The Byte Transfer Length includes a four byte header and the Write Buffer data. A Transfer Length of zero indi- cates that no data transfer shall take place.
Page 231: Byte Transfer Length (Cdb Bytes 6, 7, And 8)
SCSI Interface Product Manual, Rev. J 5.51.4.2 Byte Transfer Length (CDB bytes 6, 7, and 8) The Transfer Length in bytes of the downloadable code. This value must be the exact length of the download data. A value of one signifies one byte of download data, etc.
Page 232: Write Data To Echo Buffer Mode (1010B)
SCSI Interface Product Manual, Rev. J 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 logical unit shall perform any logical unit required verification of the complete set of downloaded microcode or control information prior to returning Good status for the last command.
Page 233: Write Extended Command (2Ah)
SCSI Interface Product Manual, Rev. J 5.52 Write Extended command (2Ah) The Write Extended 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 175. Refer also to individual drive’s Product Manual, Volume 1, Write Caching section, for information on Write Cache Control.
Page 234 SCSI Interface Product Manual, Rev. J 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 enu- meration of all conditions that may cause the Check Condition status.
Page 235: Write Long Command (3Fh)
SCSI Interface Product Manual, Rev. J 5.53 Write Long command (3Fh) The Write Long command (Table 176) 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 236: Write Same Command (41H)
SCSI Interface Product Manual, Rev. J 5.54 Write Same command (41h) The Write Same command (Table 177) requests that the target write the single block of data transferred by the initiator to the medium multiple times. Table 177: Write Same command (41h)
Page 237: Xdread Command (52H)
Regenerate 5.30 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 238 SCSI Interface Product Manual, Rev. J 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 239: Xdwrite Command (50H)
SCSI Interface Product Manual, Rev. J 5.56 XDWrite command (50h) The XDWrite command (see Table 180) 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 240: Xdwrite Extended Command (80H)
SCSI Interface Product Manual, Rev. J 5.57 XDWrite Extended command (80h) The XDWrite Extended command (see Table 181) 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 controlled by the Disable Write bit.
Page 241 SCSI Interface Product Manual, Rev. J Table 182: 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.
Page 242: Xpwrite Command (51H)
SCSI Interface Product Manual, Rev. J 5.58 XPWrite command (51h) The XPWrite command (see Table 183) 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 5.55.1.
Page 243: Seagate Technology Support Services
Seagate's automated FAX delivery system. Using a touch-tone phone, you can obtain technical support information by return FAX 24 hours daily. This service is available worldwide. Presales Support Our Presales Support staff can help you determine which Seagate products are best suited for your specific application or computer system. Seagate Express You can purchase select tape products and tape accessories through Seagate Express 24 hours daily by call- ing 1-800-531-0968 or by faxing your order to: +1-972-481-4812.
Page 244 USA/Canada/Latin America Support Services Presales Support Disc: 1-877-271-3285 or +1-405-936-1210 FAX: +1-405-936-1683 Tape: 1-800-626-6637 or +1-714-641-2500 FAX: +1-714-641-2410 Technical Support (SeaFONE) 1-800-SEAGATE or +1-405-936-1234 (for specific product phone number) FAX: Disc: +1-405-936-1685; Tape: +1-405-936-1683 SeaFAX 1-800-SEAGATE SeaTDD +1-405-936-1687 SeaBOARD Disc: +1-405-936-1600; Tape: +1-405-936-1630...
Page 245 SCSI Interface Product Manual, Rev. J Africa/Middle East Support Services For presales, technical support, warranty repair and FAX services in Africa and the Middle East, dial our Euro- pean call center at +31-20-316-7222 from 8:30 a.m. to 5:00 p.m. (European central time) Monday through Fri- day, or send a FAX to +31-20-653-3513.
Page 247: Appendix Ascsi Configured Automatically (Scam)
SCAM Protocol defines all the hardware and software requirements that provide SCSI devices with a means to establish a device’s SCSI bus ID over the SCSI interface using the standard SCSI interface signals in a nontra- ditional way. The SCAM Protocol defines a level 1 protocol and a level 2 protocol. Level 1 protocol defines a hardware and software functionality that is less capable than Level 2 protocol.
Page 249 SCSI Interface Product Manual, Rev. J Index Extended Sense Data Format 192, 193 additional sense code 67, 68, 73, 83, 103, 105, 106, 110, 112, 116, 122, 127, 144, 146, Numerics 148, 169, 171, 175, 177, 196, 207, 210, 10 byte commands 76, 77...
Page 250 SCSI Interface Product Manual, Rev. J ARRE. see Automatic Read Reallocation Enabled Block Descriptor Length ASA-1 firmware 91 Mode Select (10) parameter list 117 ASA-2 firmware 91 Mode Select parameter list 113 ASCII Family Number Mode Sense (6) command 119...
Page 251 SCSI Interface Product Manual, Rev. J bus free CAP. see Caching Analysis Permitted delay 14 capacity programming 114, 118, 121, 151, 152 phase 17, 71 catastrophic failure 73 state 49, 50 CDB. see Command Descriptor Block Bus Inactivity Limit certification defect 81...
Page 252 SCSI Interface Product Manual, Rev. J unlinked 8 continue task 30 untagged 33, 72 Control command block 221 Change Definition command 78 command byte 216 Mode Select (10) command 116 command code 44 Mode Sense (10) command 149 command complete message 49, 50, 78...
Page 253 SCSI Interface Product Manual, Rev. J current operating definition 93 Device Behavior page 101 current parameter 129 Default Operating Definition current persistent reservation 154 Implemented Operating Definition page 92 current pointer 26 default operating definition 93 current reservation 201 default self test 206...
Page 254 SCSI Interface Product Manual, Rev. J Mode Sense Parameter List 151 XDWrite command 225 density code 151 XDWrite Extended command 226 deskew delay 15 XPWrite command 228 destination device 4 disable page out bit 185 detected error 41 Disable Page Out-Force Unit Access...
Page 255 SCSI Interface Product Manual, Rev. J download 216 element address 156 download microcode 218 element reservation 156, 160 download microcode and save 216 EMDP. see Enable Modify Data Pointers Download Microcode and Save mode Enable Early Recovery Write Buffer command 216...
Page 256 SCSI Interface Product Manual, Rev. J on-the-fly 107, 124, 133 error counter page 107 factory log page 109 error event factory/field maintenance 181 recoverable 108 failed block 178 error handling parameter 199 failed data 199 error log 199 failed function 199...
Page 257 SCSI Interface Product Manual, Rev. J Seek command 204 G type defect 81 Seek Extended command 205 general error category 192 Send Diagnostic command 206 general message protocol 27 Start/Stop Unit command 209 generate no sense 148 Test Unit Ready command 211...
Page 258 SCSI Interface Product Manual, Rev. J Identifier asynchronous 21 Identification Descriptor 94, 95 phase 13 Identifier Length informational exception condition 148 Identification Descriptor 94, 95 informational exceptions control page 115, 120, Identifier Type 146, 150 Identification Descriptor 94, 95 descriptor 122...
Page 259 SCSI Interface Product Manual, Rev. J internal Xor operation 224 Seek Extended command 205 international standard 216 Send Diagnostic command 206 intersymbol interference (ISI) 5 Start/Stop Unit command 209 Interval Timer Test Unit Ready command 211 Informational Exceptions Control page 146, 147...
Page 260 SCSI Interface Product Manual, Rev. J Write Extended command 219 Write Buffer command 215 Write Long command 221 Write command 213 Write Same command 222 Write Extended command 219 XDRead command 223 Write Long command 221 XDWrite command 225 Write Same command 222...
Page 261 SCSI Interface Product Manual, Rev. J media Mode Select (6) command 112 disc 49 Mode Select command 69, 72, 115, 119, 126, 129, media information 5 131, 133, 134, 139, 140, 141, 143, 144, medium access command 211 145, 147, 149, 152, 194, 195, 199...
Page 262 SCSI Interface Product Manual, Rev. J multiple initiators 2 Write Same command 222 multiple locks 210 number of blocks 151 multiple persistent reservations 154 Number of Cache Segments multiple physical addresses 176 Caching Parameters page 134, 136 multiple port device 179, 185, 226...
Page 263 SCSI Interface Product Manual, Rev. J Mode Select (10) command 116 Mode Select (6) command 112 P bit 169, 170, 171, 172 Send Diagnostic command 206 P list 171 page format P type defect 81 optional 181 packetized command structure 43...
Page 264 SCSI Interface Product Manual, Rev. J Change Definition command 78 PE. see Parity Enable Parameter Information peer entities 5 Mode Select (10) parameter list 117 peer-to-peer protocol service 5 Mode Sense Data 121 pending task 5 Parameter Length PER. see Post Error Log Parameter 105, 106 Perf.
Page 265 SCSI Interface Product Manual, Rev. J Physical Sector Unit Serial Number page 92 Defect List Header Description 170 product serial number 95 Read Defect Data (12) list header 172 Product Unique Sense Data physical sector 129 Extended Sense Data Format 192...
Page 266 SCSI Interface Product Manual, Rev. J read capacity data 168, 204 recoverable error event 108 read combined descriptor header and data 164, 165 recoverable read error 174 Read command 49, 50, 80, 143, 162, 173, 178, recovered error 124, 133, 148, 162, 163, 169,...
Page 267 SCSI Interface Product Manual, Rev. J request 6, 7 response 6 confirmation transaction 6 service 7 response transaction 6 Response Data Format SCSI bus signal 12 Drive Standard Inquiry Data 88, 89 request sense 20, 45, 46, 144, 209 restore pointers 31, 33, 41...
Page 268 SCSI Interface Product Manual, Rev. J save data pointer 33, 41 summary 9 save data pointer message 50 SCSI compliance level 72 save executable microcode 215 SCSI configured automatically. see SCAM Save Implemented SCSI device 6, 233 Implemented Operating Definition page 92, 93...
Page 269: Figure 8. Single Command Example
SCSI Interface Product Manual, Rev. J Send Diagnostic command 206 Firmware Numbers page 97 self-describing microcode 217 servo RAM release number 96 self-monitoring analysis and reporting technology Servo ROM Release Date In ASCII 42, 146 Firmware Numbers page 97 measurement 109...
Page 270 SCSI Interface Product Manual, Rev. J Power Condition page 141 synchronous data transfer request 33, 34, 35, 36, Start Start/Stop Unit command 209 message 34 Start command 211 response 36 start unit 199 synchronous negotiation 41 Start/Stop Unit command 209...
Page 271 SCSI Interface Product Manual, Rev. J task set 7, 47, 48 Format Parameters page 128, 129 faulted 4 transaction 7 full status 48 Transfer Block management 66, 67 Error Recovery page 123, 124 queue 33 Transfer Disable task state Drive Standard Inquiry Data 88, 90...
Page 272 SCSI Interface Product Manual, Rev. J Unit Attention Parameters page 144 vendor specific 8 unit attention 144, 163, 174, 220 condition 217 unit attention condition 69, 70, 73, 102, 105, 112, error recovery 67 138, 216, 217, 218 microcode 216...
Page 273 SCSI Interface Product Manual, Rev. J Caching Parameters page 134, 135 write cache enable bit 178, 185, 219, 225, 226, Write command 127, 178, 185, 213, 219, 225, 226 write data buffer 209 Write Data Only mode Write Buffer command 216...
Page 276 Seagate Technology, Inc. 920 Disc Drive, Scotts Valley, California 95066-4544, USA Publication Number: 77738479, Rev. J, Printed in USA...

Seagate SCSI Interface Product Manual

1 Interface Requirements

2 SCSI Bus

3 Logical Characteristics

4 SCSI Commands

5 Command Descriptions

6 Seagate Technology Support Services

Appendix Ascsi Configured Automatically (SCAM)

Quick Links

Related Manuals for Seagate SCSI Interface

Summary of Contents for Seagate SCSI Interface