Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 6-1
Dimensions for the Maxtor Atlas 10K V Hard Disk Drives.. 3-3 Drive Packing Assembly... 3-5 Jumper Locations on the 68-Pin Wide SCSI Drive PCB.. 3-7 Pin Locations on SCA-2 Connector... 3-11 J1 Interface Connector Configurations... 3-15 Mounting Dimensions Maxtor Atlas 10K V Drives.. 3-23 Mounting Screw Clearance for Maxtor Atlas 10K V Drive.. 3-24 Lengthwise Airflow Cooling... 3-25 Crosswise Airflow Cooling... 3-26 ST and DT CLocking... 6-11

List of Tables

Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 4-1 Table 4-2 Table 4-3 Table 4-4 Table 4-5 Table 4-6 Table 4-7 Table 4-8 Table 4-9 Table 5-1 Table 5-2 Table 5-3 Table 5-4 Table 5-5 Table 5-6 Table 5-7 Table 5-8 Table 5-9 Table 5-10 Table 5-11 Table 5-12 Table 5-13 Table 5-14 Table 5-15 Table 5-16 Table 5-17 Table 5-18 Table 5-19 Table 5-20 Table 5-21
SCSI ID Selection on Option Connector (68-Pin SCSI Connector Drives). 3-8 SCSI ID Pin Assignments (SCA-2 Connector Versions of the Disk Drive). 3-12 Spin Up on Power On Options... 3-13 68-Pin Wide LVD Pin Assignments... 3-16 80-Pin SCA-2 LVD Pin Assignments... 3-17 68-Pin Wide Single-Ended Pin Assignments... 3-19 80-Pin SCA-2 Single-Ended Pin Assignments.. 3-20 Specifications.... 4-1 Formatted Capacity... 4-3 Timing Specifications for Maxtor Atlas 10K V.. 4-4 Power Reset Limits1... 4-5 Power Dissipation in Various Modes (Low-Profile Drives). 4-6 Acoustical CharacteristicsSound Power per ISO 7779.. 4-7 Environmental Specifications... 4-8 Shock and Vibration Specifications.. 4-10 Error Rates... 4-11 Supported SCSI Commands.. 5-1 Typical (6-Byte) Command Descriptor Block-Data Format.. 5-4 Command Descriptor Block-Field Descriptions.. 5-4 Typical (6-Byte) Command Descriptor Block - Data Format.. 5-5 Command Descriptor Block Control Field-Field Descriptions. 5-6 Status Codes... 5-7 Length Fields... 5-11 DATA-Phase Command Contents.. 5-11 CHANGE DEFINITION Command Descriptor Block-Data Format. 5-14 CHANGE DEFINITION-Field Descriptions.. 5-14 FORMAT UNIT Command Descriptor Block-Data Format.. 5-16 FORMAT UNIT Command-Field Descriptions.. 5-16 FORMAT UNIT Command Supported Options.. 5-17 FORMAT UNIT Parameter List-Data Format.. 5-17.FORMAT UNIT Defect List Header-Data Format.. 5-18 FORMAT UNIT Defect List Header-Field Descriptions. 5-18 FORMAT UNIT Defect Descriptor-Block Format.. 5-19 FORMAT UNIT Defect Descriptor- Physical Sector and Bytes From Index Format... 5-19 FORMAT UNIT Initialization Pattern Descriptor-Data Format.. 5-19 FORMAT UNIT Initialization Pattern Descriptor-Field Descriptions. 5-20 FORMAT UNIT Initialization Pattern Type.. 5-20
Table 5-22 Table 5-23 Table 5-24 Table 5-25 Table 5-26 Table 5-27 Table 5-28 Table 5-29 Table 5-30 Table 5-31 Table 5-32 Table 5-33 Table 5-34 Table 5-37 Table 5-38 Table 5-39 Table 5-40 Table 5-41 Table 5-42 Table 5-43 Table 5-44 Table 5-45 Table 5-46 Table 5-47 Table 5-48 Table 5-49 Table 5-50 Table 5-51 Table 5-52 Table 5-53 Table 5-54 Table 5-55 Table 5-56 Table 5-57 Table 5-58 Table 5-59 Table 5-60 Table 5-61 Table 5-62 Table 5-63 Table 5-64 Table 5-65 Table 5-66 Table 5-67 Table 5-68 Table 5-69

Figure 3-2 shows the packing assembly for a single Maxtor Atlas 10K V hard disk drive. Shipping containers for 25-pack are available for multiple drive shipments.
Figure 3-2 Drive Packing Assembly

3.4 3.4.1

HARDWARE OPTIONS Configuration Jumpers and Connections
This section includes setup and configuration information for Maxtor Atlas 10K V drives. These disk drives include The 16-bit multimode Ultra320 SCSI, wide version with 68-pin SCSI connector, The 16-bit multimode Ultra320 SCSI, version with SCA-2 80-pin connector. Specific individual settings for each drive type are described in Sections 3.5.1 through 3.5.4.
CAUTION: Before you begin, review the Safety, ESD, and Handling precautions described at the beginning of this manual to avoid personal injury or damage to equipment.
Jumper Options on the 68-Pin Wide PCB
This section describes how to configure the jumpers on Maxtor Atlas 10K V disks with 68-pin SCSI interface connectors. The following features are jumperselectable: SCSI ID (0), (1), (2), (3) SCSI Bus Device Identification Delay Spin Single-Ended, Disable LVD Busy Out (Remote LED) Write Protect Stagger Spin Note: The disk drive does not support on-board SCSI termination. Note: The configuration of a Maxtor Atlas 10K V hard disk drive depends on the host system in which it is to be installed. Figure 3-3 shows the printed circuit board (PCB) assemblies for 68-pin SCSI configurations, indicating the jumpers that control some of these options.

4-Pin Power Connector

12-Pin Option Connector

68-pin SCSI Connector

Figure 3-3 Jumper Locations on the 68-Pin Wide SCSI Drive PCB

Table 3-1

SCSI ID Selection on Option Connector (68-Pin SCSI Connector Drives) Jumper Location J3 Option Header
Pin Pair 7/8 Pin Pair 5/6 Pin Pair 3/4 Pin Pair 1/2

SCSI ID

Note: 0 = No Jumper, 1 = Jumper Installed Configure the drive for remote (external) SCSI ID selection by removing the SCSI ID jumpers (if present) from the referenced SCSI ID pins. Then connect the leads from the external selection switch to the referenced pins. Observe the following guidelines while doing so: ID bit 0, at Pin 8, is the Least Significant Bit. SCSI ID bits 0, 1, 2, and 3 (pins 8, 6, 4, and 2, respectively) are active LOW signals. That is, the bit is a 1 if the corresponding remote switch is closed to ground or jumper installed. Use pins 1, 3, 5 and 7 as the associated ground returns for ID bits 3, 2, 1, and 0, respectively.

1. The minus sign next to a signal indicates active low.
2. The conductor number refers to the conductor position when using 0.635 mm (0.025 inch) centerline flat ribbon cable. Other cable types may be used to implement equivalent contact assignments.

Maxtor Atlas 10K V 3-19

80-Pin SCA-2 Single-Ended SCSI Connector

Table 3-7

80-Pin SCA-2 Single-Ended Pin Assignments
CABLE CONDUCTOR NUMBER NOT APPLICABLE 80-PIN CONNECTOR CONTACT AND SIGNAL NAME 12V GROUND 12V GROUND 12V GROUND MATED 1 OPT 3.3V CHARGE GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND GROUND MATED 2 5V GROUND 5V GROUND ACTIVE LED OUT DLYD_START SCSI ID (1) SCSI ID (3) 79 80
80-PIN CONNECTOR CONTACT AND SIGNAL NAME 12V CHARGE 12V 12V 12 V OPT 3.3 VOLTS OPT 3.3 VOLTS DB (11) DB (10) DB (9) DB (8) I/O REQ C/D SEL MSG RST ACK BSY ATN DB (P0) DB (7) DB (6) DB (5) DB (4) DB (3) DB (2) DB (1) DB (0) DB (P1) DB (15) DB (14) DB (13) DB (12) 5V 5V 5V CHARGE SPINDLE SYNC RMT START SCSI ID (0) SCSI ID (2) 39 40
DRIVE MOUNTING AND INSTALLATION
Drive mounting orientation, clearance, and ventilation requirements are described in the following subsections.

Orientation

The mounting holes on the Maxtor Atlas 10K V hard disk drive allow the drive to be mounted in any orientation. Figure 3-6 shows the location of the three mounting holes on each side of the drive. The drives also can be mounted using the four mounting hole locations on the PCB side. All dimensions are in millimeters. For mounting, #6-32 UNC screws are recommended.
Figure 3-6 Mounting Dimensions Maxtor Atlas 10K V Drives

Maxtor Atlas 10K V 3-21

Mounting Screw Clearance
The printed-circuit board assembly (PCBA) is very close to the mounting holes. Figure 3-7 specifies the clearance between the screws in the mounting holes and the PCBA. Do not use mounting screws longer than the maximum lengths specified in Figure 3-7. The specified screw length allows full use of the mounting-hole threads, while avoiding damaging or placing unwanted stress on the PCBA. Clearance from the drive to any other surface (except mounting surfaces) must be a minimum of 1.25 mm (0.05 inches).
Figure 3-7 Mounting Screw Clearance for Maxtor Atlas 10K V Drive
CAUTION: The PCB is very close to the mounting holes. Do not exceed the specified length for the mounting screws. The specified screw length allows full use of the mounting-hole threads, while avoiding damaging or placing unwanted stress on the PCB. Figure 3-7 specifies the minimum clearance between the PCB and the screws in the mounting holes. The maximum torque applied to the screws must not exceed 8.6 inch-pounds.

FmtData

CmpLst
Five Forms of FORMAT UNIT Commands
Five different forms of the FORMAT UNIT command are supported through different combinations of the Format Data bit, Complete List bit, and the information in the Defect List Length field. (Refer to FORMAT UNIT Defect Header List for a description of the Defect List Length field.) The different command forms give the initiator control over the contents of the Grown Defect List. Table 5-13 describes the contents of the Grown Defect List after FORMAT UNIT command execution.
Table 5-13 FORMAT UNIT Command Supported Options Defect List Length

N/A 0 0

FmtDat
Contents of Grown Defect List after FORMAT UNIT Command Execution
All sectors found to be bad, but not listed in the Primary Defect List or Grown Defect List, are added to the Grown Defect List. Same as above. The existing Grown Defect List is discarded. A new Grown Defect List is generated, containing All sectors found to be bad, but not listed in the Primary Defect List. The Grown Defect List contains: Original Grown Defect List All sectors found to be bad, but not listed in the Primary Defect List. A list of sectors supplied by the initiator. These sectors are passed in defect descriptors in the data-out buffer transfer that occurs as part of the FORMAT UNIT command. Same as the case above, except that the current Grown Defect List is discarded before formatting begins.
FORMAT UNIT Parameter List
The FORMAT UNIT Parameter List (Table 5-14) consists of a Defect List Header (Table 5-15) followed by one or more Defect Descriptors. Descriptors are either four bytes or eight bytes in length.
Table 5-14 FORMAT UNIT Parameter List-Data Format Bit Byte
Defect List Header Initialization Pattern Descriptor (if any) Defect Descriptors (if any)

5.8.2.1

FORMAT UNIT Defect List Header
The FORMAT UNIT Defect List Header (Table 5-15) provides several optional format control bits to give the initiator more control over the defect lists. Table 5-16 provides descriptions of the data fields in the Defect List Header
Table 5-15.FORMAT UNIT Defect List Header-Data Format Bit Byte

2-3 FOV DPRY DCRT

5.12.12.2

Saved Training Configuration Values Subpage (Sub Page 2 of Mode Page 19)
The saved training configuration values subpage is used to report the SCSI device's saved training configuration values. These vendor specific values are maintained by the SCSI device when the retain training information option is enabled. The fields are listed in Table 5-76; however the content of the fields is vendor specific. Only values for the current I_T nexus are reported.
Table 5-76 Saved Training Configuration Subpage (02h) Bit Byte
MSB MSB MSB MSB MSB MSB MSB MSB MSB MSB MSB MSB MSB

MSB MSB

LSB LSB

DB(0) Value

DB(15) Value P_ORCA Value P1 Value BSY Value SEL Value RST Value REQ Value ACK Value ATN Value C/D Value I/O Value MSG Value Reserved
LSB LSB LSB LSB LSB LSB LSB LSB LSB LSB LSB LSB LSB

5.12.12.3

Negotiated Settings Subpage (Sub Page 3 of Mode Page 19)
The negotiated settings subpage, shown in Table 5-77, is used to report the negotiated settings of a target for the current I_T nexus.
Table 5-77 Negotiated Settings Subpage (03h) Bit Byte

Reserved Reserved

Transfer Period Factor Req/Ack Offset Transfer Width Exponent Protocol Option Bits Transceiver Mode Reserved Vendor Specific SENT_ PCOMP_EN RECEIVED PCOMP_EN
The Transfer Period Factor field indicates the negotiated transfer period factor for the current I_T nexus.
Table 5-78 Transceiver Period Factor Code
0-9 0x0A 0x0B 0x0C0x18 0x190x31 0x320xFF
Transceiver Period Factor
Reserved TP=6.25ns Fast - 160 (U320) TP=12.5ns Fast - 80 (U160) TP=25ns Fast - 40 (Ultra2) TP=30.3 ns Fast - 40 Fast - 20 Fast - 10 Fast - 5
The Req/Ack Offset field indicates the negotiated REQ/ACK offset for the current I_T nexus. The Transfer Width Exponent field indicates the negotiated transfer width exponent for the current I_T nexus. The Protocol Options Bits field contain the negotiated protocol options for the current I_T nexus.
The TRANSCEIVER MODE field specifies the current bus mode of the target as defined in Table 5-79.
Table 5-79 Transceiver Mode Code

00b 01b 10b 11b

Transceiver Mode
Unknown (device not capable of reporting bus mode) Single-ended Low-Voltage Differential High-Voltage Differential
The SENT PCOMP_EN bit contains the value of the PCOMP_EN bit sent by the target for the current I_T nexus. The RECEIVED PCOMP_EN bit contains the value of the PCOMP_EN bit received by the target for the current I_T nexus.

5.12.12.4

Report Transfer Capabilities Subpage - (Sub Page 4 of Mode Page 19)

6h 7h Bh Ch Fh

MODE SELECT (10) Command (55h)
The MODE SELECT (10) command allows the initiator to modify certain mode pages and thereby control some of the drives operational characteristics. Refer to MODE SELECT (6) for additional descriptions. See Table 5-85 for the data format of the MODE SELECT (10) Command Descriptor Block. See MODE SELECT (6), Table 5-88, for descriptions of the fields. See Table 5-86 for the Mode Parameter Header (10 Byte) Data Format and Table 5-87 for the Mode Parameter Block Descriptor Data Format. See Table 5-48 for mode parameter block field descriptions.
Table 5-85 MODE SELECT (10) Command Descriptor Block-Data Format Bit Byte

2-6 7-Reserved

PF Reserved

Operation Code (55h)

Parameter List Length Control
Table 5-86 Mode Parameter Header (10-Byte)-Data Format Bit Byte

0-3 4-5 6-7 (LSB)

Mode Data Length Medium Type Device-Specific Parameter Reserved Block Descriptor Length
Table 5-87 Mode Parameter Block Descriptor-Data Format Bit Byte

0-5-7 (LSB)

Number of Blocks Density Code Block Length
Table 5-88 Mode Parameter Block Descriptor-Field Descriptions Data Field
The value in this field specifies the number of logical blocks on the disk to which the density code and block length fields apply. A value of 0 in this field indicates that all of the remaining logical blocks on the disk have the medium characteristics specified. The Density Code field is unique for each device type. Direct access devices value is zero. The value in this field specifies the length in bytes of each logical block described by the block descriptor.
MODE SENSE (6) Command (1Ah)
The MODE SENSE (6) command allows the initiator to read the drive's sector descriptor and mode pages. The MODE SENSE Command Descriptor Sector is shown in Table 5-89 and the data fields are described in Table 5-90. The Mode Parameter Header is shown in Table 5-91 and the data fields are described in Table 5-92.
Table 5-89 MODE SENSE (6) Command Descriptor Block-Data Format Bit Byte

PC Reserved

DBD Page Code

Operation Code (1Ah)

Sub Page Code Allocation Length Control
Table 5-90 MODE SENSE Command-Field Descriptions Data Field

Reservation Key

Service Action Reservation Key
Table 5-118 illustrates which fields are set by the application client and interpreted by the device server for each Service and Scope value.
Table 5-118 Device Server Interpretation of Service and Scope Value Parameters Service Action
Register Reserve Reserve Reserved Release Release Release Clear Clear Pre-empt Pre-empt Pre-empt Pre-empt & Clear Pre-empt & Clear Pre-empt & Clear

Allowed Scope

Ignored LU Extent Element LU Extent Element Ignored Ignored LU Extent Element LU Extent Element
Ignored Valid Valid Valid Valid Valid Valid Ignored Ignored Valid Valid Valid Valid Valid Valid
Valid Ignored Ignored Ignored Ignored Ignored Ignored Ignored Ignored Valid Valid Valid Valid Valid Valid
Element or Element Parameters
Ignored Ignored Extent Valid Ignored Ignored Extent Valid Element Valid Ignored Ignored Ignored Extent Valid Element Valid Ignored Extent Valid Element Valid

READ (6) Command (08h)

The READ (6) command requests that data be transferred from the drive to the initiator. The amount of data transferred is specified by the transfer length field. The starting point is specified by the logical sector address. The data format and field descriptions are shown in Table 5-119 and Table 5-120 respectively.
Table 5-119 READ (6) Command-Data Format Byte
Operation Code (08h) Logical Block Address Logical Block Address (continued) Transfer Length Control
Table 5-120 READ (6) Command-Field Descriptions Field
Logical Block Address Transfer Length
Specifies the logical block address where the read operation will begin. Specifies the number of contiguous logical blocks of data to transfer. A transfer length of 0 indicates that 256 logical blocks will be transferred. Any other value indicates the number of logical blocks that will be transferred.

READ (10) Command (28h)

The READ (10) command requests that data be transferred from the drive to the initiator. The amount of data transferred is specified by the transfer length field. The starting point is specified by the logical sector address. The data format and field descriptions are shown in Table 5-121 and Table 5-122 respectively.

Table 5-150 RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block-Data Format Bit Byte
Operation Code (1Ch) Page Code Value Allocation Length Control
Table 5-151 RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block-Field Descriptions Field
Specifies the number of bytes of diagnostic-page results the drive is allowed to send to the initiator. A CHECK CONDITION is not returned if this value truncates the information available.

5.27.1

Supported Diagnostics Pages Page (00h)
Table 5-152 shows the format of the Supported Diagnostics Pages page.
Table 5-152 Supported Diagnostics Pages Page-Data Format Bit Byte
Page Code (00h) Page Length (0002h) Supported Diagnostics Pages Page (00h) Translate Address Page (40h)
To obtain the Supported Diagnostics Pages list, the initiator must: 1. Send a Supported Diagnostics Page to the drive with a SEND DIAGNOSTICS command (the Page Length in the Supported Diagnostics page must be 0). 2. Send a RECEIVE DIAGNOSTIC RESULTS command to the drive. The listing of Supported Diagnostic Pages is returned by the drive.

5.27.2

Translate Address Page (40h)
The Translate Address Page allows the initiator to translate a logical sector address, physical address, or physical bytes for an index address into any one of the other formats. The address to be translated is passed to the drive with the SEND DIAGNOSTIC command, and the results are returned to the initiator by the RECEIVE DIAGNOSTIC RESULTS command. Table 5-153 shows the format of the Translate Address Page that is returned in response to a RECEIVE DIAGNOSTIC RESULTS command, and Table 5-154 contains a description of the data fields. Multiple translated addresses are returned if the logical sector size is greater than 512 bytes (more than one physical data sector).
Table 5-153 Translate Address Page-Data Format Byte
2-5 6-10 - 13 yy+2 y+3 y+4 y+7 RAREA ALTSEC
Operation Code (40h) Page Length (2 + (8 x n)) (where n = number of sectors / LBA) Reserved ALTTRK Reserved Supplied Format = 000b (LBA) Translate Format = 101b (Physical Sector)
Translated Address (Cylinder Number)1 Translated Address (Head Number)1 Translated Address (Sector Number or Bytes From Index)1 Translated Address (Cylinder Number) Where y = ((n-1) x 8) + 6 Translated Address (Head Number) Translated Address (Sector Number or Bytes From Index)

0x5D 0x5D 0x5D 0x27 0x81 0x81 0x81 0x81
0x07 Data Protect 0x09 Vendor Specific

0x0B Aborted Cmd

0x00 0x0E 0x1B 0x25 0x3F 0x43 0x45 0x47 0x47 0x47 0x47 0x47 0x48 0x49 0x4B 0x4B 0x4B 0x4B 0x4E 0x84 0x00 0x01 0x00 0x00 0x0F 0x00 0x00 0x00 0x01 0x02 0x03 0x04 0x00 0x00 0x02 0x03 0x04 0x05 0x00 0x00 0x00 Aborted.
Abort: IU too short (data frame with length = 0) Abort: Synchronous transfers timeout Aborted with invalid LUN Aborted: Echo buffer overwritten Abort: Message reject error Abort: Reselection failed Abort: Bus parity error Abort: pCRC error detected Abort: Bus parity error during ST data phase Abort: Information Unit CRC error Abort: Async Protection error Abort: Initiator detected error Aborted with invalid Message Abort: Too much write data received Abort: ACK/NAK timeout Abort: NAK received Abort: Data offset error Overlapped commands attempted Aborted b/c of internal TO in DER for cur cmd Data miscompare error
Table 5-173 Sense-Key Specific Field Contents Sense Key
ILLEGAL REQUEST NOT READY RECOVERED ERROR MEDIUM ERROR
Field pointer bytes (Table 5-174) Progress Indication (Table 5-176) Retry count (Table 5-178) Retry count (Table 5-178)

Initiator Interpretation

Illegal field's offset (in the Command Descriptor Block or data-out buffer transfer parameters). Indicates progress of FORMAT UNIT Command. Number of retries for I/O operation Number of retries for I/O operation
The data format of the Field Pointer bytes associated with the ILLEGAL REQUEST sense key is shown in Table 5-174; the description of the data is in Table 5-175.
Table 5-174 ILLEGAL REQUEST Sense Key Field Pointer Bytes\Data Format Bit Byte

SKSV = 1

Bit Pointer

16 - 17

Field Pointer
Table 5-175 ILLEGAL REQUEST Sense Key Field Pointer Bytes\Field Descriptions Field

SKSV C/D

Sense-Key Specific Valid Command/Data. When the value in this field is 1, the Field Pointer identifies the first byte in error in the Command Descriptor Block. When 0, the Field Pointer identifies the first byte in error in the data parameters sent by the initiator in the data-out buffer transfer.
BPV Bit Pointer Field Pointer
Bit Pointer Valid. The drive does not support Bit-level resolution; the bit value must be 0. The drive does not support Bit-level resolution; the bit value must be 0. Indicates the first byte in error in either the Command Descriptor Block or in the data parameters sent by the initiator.

The data format of the Progress Indication bytes associated with the NOT READY sense key is shown in Table 5-176; the description of the data is contained in Table 5-177.
Table 5-176 NOT READY Sense Key - Progress Indication Bytes\Data Format Bit Byte

Progress Indication

Table 5-177 NOT READY Sense Key - Progress Indication Bytes\Field Descriptions Field
SKSV Progress Indication Sense-Key Specific Valid Indication of percent complete for the FORMAT UNIT command. The returned value is the numerator of a fraction that has 65536 (10000h) as the denominator (Progress Indication/10000h = percent complete).
The data format of the Retry Count bytes associated with the MEDIUM ERROR or RECOVERED ERROR sense key is shown in Table 5-178; the description of the data is contained in Table 5-179.
Table 5-178 MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry Count-Data Format Bit Byte

Retry Count

Table 5-179 MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry Count
-Field Descriptions Field
SKSV Retry Count Sense-Key Specific Valid The number of times an I/O operation was retried
RESERVE (6) Command (16h)
The RESERVE and the RELEASE commands are used for contention resolution in multiple-initiator systems. The RESERVE command is used to reserve a logical unit. The data format and the field descriptions are described in Table 5-180 and Table 5181 respectively.
Table 5-180 RESERVE (6) Command Descriptor Block-Data Format Bit Byte
Operation Code (16h) Reservation Identification Extent List Length Control
Table 5-181 RESERVE (6) Command-Field Descriptions Field

3rd Pty

When set to 1, it indicates that the Third Party Device ID field is valid. Required and used only when the 3rdPty bit is set, in which case this field specifies the SCSI ID (0 through 7 only) of the initiator to be granted the reservation of the logical unit. The drive preserves the reservation until one of the following occurs:
It is superseded by another valid RESERVE command from the initiator. It is released by the same initiator It is released by a TARGET RESET message from any initiator. It is released by a hard reset condition. The drive ignores any attempt to release the reservation made by any other initiator. For example, if ID7 sends ID2 a Third Party reservation on behalf of ID6 (the target at ID2 gets reserved for the initiator ID6), then only ID7 can release the target at ID2 (using a Third Party release). ID6 cannot release the reservation even though the reservation was made on its behalf.
Extent Reservation Identification Extent List Length
The drive supports reservations only on entire logical units. The value must be 0. Any value in this field is ignored by the drive. Any value in this field is ignored by the drive.
The drive returns RESERVATION CONFLICT status if the unit is already reserved for another initiator. Once the reservation is honored, any command from another initiator (except INQUIRY or REQUEST SENSE) is rejected with RESERVATION CONFLICT status.

Maxtor Atlas 10K V 6-11

6.14.7
Transmitter Pre-Compensation with Cutback
This is an open-loop method of compensating for some of the signal loss that is most severe on the first part of a signals transition.

6.14.8

Free Running Clock (FRC)
FRC is used to improve integrity of the clock signal by removing inter-symbol interference (ISI). By having a clock running at a constant neutralized. The free running clock is restricted for use with DT information unit transfers at 320 megabytes per second.

6.14.9

Skew Compensation
Skew compensation of data signals relative to the clock signal; an Ultra320 SCSI device can establish skew compensation simultaneously for each of the received transitions on the data lines so that they occur at the correct time relative to the clock.

6.14.10

Information Unit Transfers
IUT (or IU Transfers, also known as packetized transfers) is a method to encapsulate non-data information (like commands sent from the initiator to the target and status sent from the target to the initiator) into packets and transfer those packets at the maximum negotiated data rate of up to 320 megabytes per second. A method to transfer packets for a number of I/O processes without an intervening physical disconnection. A method to minimize overhead by eliminating several bus phase changes per I/O process.
HOT PLUGGING/REMOVAL AND INSERTION OF SCSI DEVICES
The Maxtor Atlas 10K V SCA low voltage differential (LVD) disk drives are designed for use in Hot Swap applications within a properly designed and configured SCSI system. With care, system integrators can design storage arrays and/or SCSI buses using Maxtor Atlas 10K V disk drives that are Hot Swap Case 4" tolerant. Case 4 is defined as follows: Devices are powered and the bus may have active I/O processes ongoing, but the device being removed or inserted must be idle (no ongoing I/O processes during the insertion/removal). Ground connections to the drive must be made and maintained for 1 millisecond before, during, and 1 millisecond after the insertion/ removal. The SCA-2 connector used on the Maxtor Atlas 10K V disk drive meets this requirement. Device circuitry connected to bus pins must remain glitch free during power up or power down. Note: In a multimode environment, any insertion or removal that changes the bus mode causes a transceiver mode change reset event.

6-12 Maxtor Atlas 10K V

6.15.1

System Considerations

It is not possible for the suppliers of various system components (e.g., targets, initiators, backplanes, terminators) to guarantee that a system can operate under Hot Swap Case 4" conditions. Therefore, the system integrator bears the responsibility for ensuring that the system can meet Hot Swap Case 4" operational criteria. There are two metrics key to ensuring Hot Swap Case 4" tolerance: 1. When a drive is being hot inserted into an active bus, a smaller capacitance on the SCSI bus pins create a smaller (that is, a lesser charge) transient spike on the bus. 2. When the drive is the closest drive to the connector at which another drive is being hot inserted, it is desirable that the input receivers ignore short low amplitude transients (usually via a low pass filter). LVD SCSI devices may require more stringent system design to tolerate transients that occur during Case 4 insertion or removal. System integrators should consider the following when designing their backplanes or buses: 1. Larger connector-to-connector spacing causes the transients associated with hot swapping to be attenuated dramatically before reaching an operating drive. 2. Larger SCSI signal-trace capacitance (that is, lower impedance) is preferable for minimizing transient spikes, but can cause other bus problems unrelated to hot swapping. Draft standard SCSI-3 SCSI SPI-2 (SCSI Parallel Interface), Revision 18, Section 6.6.2 illustrates the trade-offs between trace capacitance and drive-todrive spacing. 3. The universe of drives needs to be homogeneous. A 15 pF drive hot-inserted into a rack of 15 pF drives presents no difficulty. A 30 pF drive inserted into a rack of 10 pF drives with very close connector spacing, however, is more likely to cause problems.

FALSE Refers to the logical-zero (or negated) state of a binary number. See also, signal negation. FAST SCSI The SCSI protocol that governs fast synchronous transfer. See also Synchronous Transfer. FCI Flux Changes per Inch. The number of magnetic field patterns that can be stored on a given area of disk surface, used as a measure of data density. (See also BPI.) FIELD A logically related group of one or more physically contiguous bits. FILE SERVER A computer that provides network stations with controlled access to shareable resources. The network operating system is loaded on the file server, and most shareable devices (disk subsystems, printers) are attached to it. The file server controls system security and monitors station-to-station communications. A dedicated file server can be used only as a file server while it is on the network. A non dedicated file server can be used simultaneously as a file server and a workstation. FIRMWARE Permanent instructions and data programmed directly into the circuitry of read-only memory for controlling the operation of the computer. Distinct from software, which can be altered by programmers. FLUX DENSITY The number of magnetic field patterns that can be stored in a given length of disk surface. The number is usually stated as flux changes per inch (FCI), with typical values in the thousands. (See also FCI.) FLYING HEIGHT The distance between the read/write head and the disk surface, made up of a cushion of air that keeps the two objects from touching. Smaller flying heights permit denser data storage but require more precise mechanical designs. Also known as fly height. FORMAT To write a magnetic track pattern onto a disk surface, specifying the locations of the tracks and sectors. This information must exist on a disk before it can store data.
FORMATTED CAPACITY The amount of room left to store data on a disk after writing sector headers, boundary definitions, and timing information during a format operation. The size of a Maxtor drive is always expressed in formatted capacity, accurately reflecting the usable space required. FORM FACTOR The industry standard that defines the physical, external dimensions of a particular device. For example, most Maxtor hard disk drives use a 3 1/2-inch form factor. FULL HEIGHT Term used to describe a disk that occupies the vertical space (3.250 inches) of a full sized 5.25-inch drive. See also half height, low profile.
GIGABYTE (GB) 1 billion bytes. The total accessible capacity varies depending on the operating environment. Glist Abbreviation. When the drive encounters a defective sector during regular use, it adds the address of the sector to the Grown Defect List (Glist). See also Plist. GUIDE RAILS Plastic strips attached to the sides of a hard disk drive in an IBM PC/AT or compatible computer so that the drive easily slides into place.

QUEUE A prioritized list or set of processes. A queue may be a FIFO (first-in, first-out), LIFO (last-in, first -out) or a random-access entity. QUEUE TAG The value associated with an I/O process that uniquely identifies it from other queued I/O processes in the logical unit from the same initiator. QUEUED I/O PROCESS An I/O process that is in the command queue.
REMOVABLE DISK Generally said of disk drives where the disk itself is meant to be removed, and in particular of hard disks using disks mounted in cartridges. Their advantage is that multiple disks can be used to increase the amount of stored material, and that once removed, the disk can be stored away to prevent unauthorized use. RLL Abbreviation for Run Length Limited. An advanced method used to encode (or compress) data for storage on a disk. RLL encoding stores almost 50 percent more data than MFM (Modified Frequency Modulation). RLL code improves MFM code by encoding data bits in groups rather than singly. Many encoding schemes are possible. The best achieve optimum values of code rates, clocking, power spectrum, error propagation and encoding complexity. A number pair (e.g., 1,7) is usually stated with RLL references. It refers to the minimum number of 0;s(1) and the maximum number of 0's (7) that can separate data 1's stored on the disk. ROM Read-Only Memory. Integrated circuit memory chip containing programs that can be accessed and read but can not be modified. ROTARY ACTUATOR The rotary actuator replaces the stepper motor used in the past by many hard disk manufacturers. The rotary actuator is perfectly balanced and rotates around a single pivot point. It allows closedloop feedback positioning of the heads, which is more accurate than stepper motors. ROTATIONAL LATENCY The delay between when the controller starts looking for a specific block of data on a track and when that block rotates around to where it can be read by the read/write head. On average, it is half of the time needed for a full rotation (about 8 ms.). SCA-2 An improved Single Connector Attachment that incorporates two electrostatic discharge (ESD) pins on either end of the connector to improve safety when making a connection. SCSI Small Computer System Interface. An interface designed for Apple Macintosh systems and UNIX workstations. SCSI-1 The first small computer system interface standard. SCSI-2 An enhanced small computer system interface as defined and published by ANSI in standard X3.131-1994. One of the major features of SCSI-2 is integrating the controller into the peripheral device, making the device independent of the initiator. SCSI-3 A new set of related ANSI standards are currently under development by the X3T10 committee. The old SCSI-2 standard has been divided into a new set of standards for SCSI-3. Some of these [working draft] standards are: SAM (SCSI Architecture Model) for the architecture; SBC (SCSI Block Commands) for the disk drive specific command set. SPC (SCSI Primary Commands) for the primary command set; and SIP (SCSI Interlocked Protocol) for the protocol layer; SPI (SCSI Parallel Interface) for the physical layer; Layering the standards documents in this manner allows substitution of parts of the structure as new technology arrives. SCSI ADDRESS The unique address assigned to a SCSI bus device. Normally, the address is assigned and set during system installation with priority being a consideration. A SCSI address is a value of 0 to 7 (or 0 to 15 for wide SCSI).

Atlas 10K V SAS

ENTERPRISE

Serial Attached SCSI HARD DRIVE 73GB 147GB 300GB
Highest Capacity Enterprise SAS Hard Disk Drive for Mainstream HighBandwidth Applications Capacity, Availability, Scalability, Flexibility, Reliability, Adaptability and PerformanceThe Atlas 10K V SAS Advantage The Maxtor Atlas 10K V SAS delivers the industrys highest capacity point Serial Attached SCSI (SAS) drive with a 16MB cache, as fast as 4.0 msec seek time and 89MB/sec sustained data transfer rate, providing an optimal combination for use on mainstream enterprise solutions.
SAS technology brings together the best features of other Enterprise interfaces to deliver: Higher System Availability Dual port provides two data paths to each disk drive increasing the drives availability Multi-initiator capability enables multiple hosts to access a drive simultaneously Point-to-point connectivity for better fault isolation Scalability More than 16,000 devices per SAS domain Scalable bandwidth via wide ports, i.e. up to 24 Gb/s peak bandwidth with 4 SAS links configured as a wide port with full duplex End User Flexibility Configuration flexibility allow end-users to mix and match SAS and SATA drives to fit their specific application SAS back-planes can accommodate dual port / high performance SAS drives and/ or high capacity / lower cost SATA drives Performance Up to 128 queue depth support for improved IOPS performance Full duplex capability allow drives to send and receive data for two different IO operations simultaneously Point-to-point connectivity eliminates the bottleneck inherent with a shared/arbitrated bus Scalable bandwidth via wide ports Rate matching supports 1.5Gbs SATA and 3.0Gbs SAS drives for optimal performance SCSI Investment Protection Employs the SCSI command set to maintain compatibility with existing SCSI infrastructures
10,000 RPM ENTERPRISECLASS HARD DRIVE CAPACITY AND PERFORMANCE
Industrys highest capacity SAS HDD 3Gb/s Serial Attached SCSI (SAS) Maximum sustained data rate up to 89MB/s Seek times as fast as 4.0ms Double the capacity of 15K RPM drives (per platter) Full duplex capability 16MB Cache
Atlas 10K V SAS Hard Drives Deliver: MaxAdapt Features Adaptive Bias Estimation (ABE) Maintains consistent performance by adjusting the bias applied to the actuator Virtual Cache Lines (VCL)Allows dynamic assignment of cache segments Rotational Vibration Compensation (RVC)Monitors and corrects for external vibration Reliability 1,400,000 hours MTTF State-of-the-art manufacturing processes Multiple temperature tests Improved SMART and self-diagnostics Atlas 10K V SAS Best-Fit: Large Enterprise NAS/SAN Servers Mainstream NAS/SAN Workstations Direct Attached JBOD Storage Direct Attached RAID Storage

EXTRAORDINARY VALUE

MaxAdapt Features
Ease of integration SCSI investment protection

SUPERIOR RELIABILITY

Designed for 1.4 million hours MTTF 24 x 7 dependability Dual port accessibility Proven Atlas family platform SMART features RoHS compliant
SPECIFICATIONS 73.5 Formatted Capacity (GB) Bytes per Sector Interface Number of Heads Number of Disks Performance Specifications Seek Time Average Read/Write (ms) Track-to-Track Read/Write (ms) Full Stroke Read/Write (ms) Spindle Speed (RPM) Average Rotational Latency (ms) Transfer Rate Maximum Sustained (MB/sec) SAS Interface Bandwidth (MB/s) Cache (MBytes) Reliability Specifications Contact Start Stop (CSS) Data Error Rate per Bits Read Recoverable Nonrecoverable Seek MTTF Limited warranty (years) ORDER INFORMATION RoHS Model Number 8J073S0 8J147S0 8J300S0 Capacity 73.5GB 147.1GB 300GB <10 per 1012 <1 per 1015 <10 per 108 1.4 million hours 5 Physical Dimensions Width max (inches/mm) Length max (inches/mm) Height max (inches/mm) Weight max (lb/kg) 4.0/101.6 5.787/147.0 1.028/26.1 1.8/0.82 50,Power Specifications Voltage Requirements Idle Power (W) 5V +/- 5% 9.01 12V +/- 5% 12.4 9.78 4.0/4.5 4.2/4.7 0.3/0.5 11.0/12.0 10,4.4/4.1 73.5 147.1 147.1 512, 516, 518, 520, 522, 524 SAS Environmental Specifications Operating Temperature (C) Maximum Case Temperature (C) Non-Condensing Humidity (%) Shock 2 ms (G) R/W Rotational Shock (rad/sec2) Vibration 5-500 Hz (G) Rotational Vibration (rad/sec2) Altitude (feet) Acoustics, Idle (bels) Non-Operating Temperature (C) Non-Condensing Humidity (%) Shock 2 msec (G) Rotational Shock Altitude (feet) (rad/sec2) Vibration 5-500 Hz (G) -40 to to 25,-1,000 to 40,000 3.to 5 to 95 63/30 7,000 1.-1,000 to 10,000 3.6 3.8 73.5 147.1 300

For support or information, call us at 1-800-2Maxtor or visit us at www.maxtor.com
All Maxtor products are backed by our leading service and support staff. Service includes: Advance replacement in two business days 24-hour on-line troubleshooting tools and email Telephone support representatives available Monday-Friday during business hours (except holidays) To speak with a Maxtor product support representative in the U.S. and Canada, call 1-800-2MAXTOR, Mon.-Fri. from 7 a.m. to 4 p.m. (PST). In Europe, call +Mon.-Thur. from 8:30 a.m. to 5 p.m. (GMT) and Fri. 8:30 a.m. to 4 p.m. (GMT). In Australia, call 759 109. In Japan, call 543, and in Singapore, call 481 6788.
For purposes of measuring drive capacity, a gigabyte (GB) means 1,000,000,000 bytes. Total accessible capacity varies depending on operating environment. Seek times are at nominal conditions and include settling. Specifications subject to change without notice. * MTTF refers to the estimated mean time to failure based upon a statistical sample. 2005 Maxtor Corporation. Maxtor, Atlas, MaxAdapt, What drives you and the Maxtor stylized logo are registered trademarks of Maxtor Corporation. Maxtor Corporation, 500 McCarthy Boulevard, Milpitas, CA, 95035. DS-Atlas10KVSAS-4/05-CL.