Maxtor Atlas 10K V Product Manual September 6, 2005 Revision 3 PN: 000001911
Maxtor © March 24,2005 Maxtor Corporation. All rights reserved. Printed in U.S.A. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein – which will be incorporated in revised editions of the publication. Maxtor may make changes or improvements in the product(s) described in this publication at any time and without notice. UL/CSA/VDE/TUV UL standard 1950 3rd Edition recognition granted under File No. E146611 CSA standard C22.
You can request Maxtor publications from your Maxtor Sales Representative or order them directly from Maxtor. Publication Number: PN: 000001911 Corporate Headquarters 500 McCarthy Blvd Milpitas, California 95035 Tel: 408-894-5000 Fax: 408-362-4740 Research and Development Center 333 South Street Shrewsbury, MA 01545 Tel: 1-800-2-MAXTOR or 1-800-262-9867 Before You Begin Thank you for your interest in Maxtor hard disk drives.
Regulatory Statements This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. Any modifications of this device - unless expressly approved by the manufacturer - can void the user’s authority to operate this equipment under Part 15 of the FCC Rules.
Table of Contents Chapter 1 ABOUT THIS MANUAL 1.1 AUDIENCE ....................................................................................................................... 1.2 MANUAL ORGANIZATION.......................................................................................... 1.3 TERMINOLOGY AND CONVENTIONS ..................................................................... 1.4 REFERENCES .....................................................................................................
3.5.2.1 80 Pin SCA-2 Mating Connectors...............................................................................3-20 3.5.3 68-Pin Wide Single-Ended SCSI Connector ............................................................3-21 3.5.4 80-Pin SCA-2 Single-Ended SCSI Connector ..........................................................3-22 3.6 DRIVE MOUNTING and installation ................................................................................. 3-26 3.6.1 Orientation ............................
5.11.2 Vital Product Data Pages .........................................................................................5-24 5.12 LOG SELECT Command (4Ch)........................................................................................ 5-32 5.13 LOG SENSE Command (4Dh) .......................................................................................... 5-33 5.13.1 LOG SENSE Command Descriptor Block ..............................................................5-34 5.13.2 LOG SENSE Log Pages ..
5.34 5.35 5.36 5.37 5.38 5.39 5.40 5.41 5.42 5.43 5.44 5.45 5.46 5.47 5.48 5.49 RESERVE (6) Command (16h) ....................................................................................... 5-124 RESERVE (10) Command (56h) ..................................................................................... 5-125 REZERO UNIT Command (01h) .................................................................................. 5-127 SEEK (6) Command (0Bh)......................................................
6.14.2 Data Read Errors .......................................................................................................6-7 6.14.3 Reallocation of Bad Blocks ........................................................................................6-8 6.15 THE ULTRA160 and ULTRA320 LOW VOLTAGE DIFFERENTIAL (LVD) SCSI INTERFACE ....................................................................................................... 6-8,6-9 6.15.1 DIFFSENS ..................................................
List of Figures 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 ........................................................
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) .
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 INQUI
Table 5-70 Table 5-71 Table 5-72 Table 5-73 Table 5-74 Table 5-75 Table 5-76 Table 5-77 Table 5-78 Table 5-79 Table 5-80 Table 5-81 Table 5-84 Table 5-85 Table 5-86 Table 5-87 Table 5-88 Table 5-89 Table 5-90 Table 5-91 Table 5-92 Table 5-93 Table 5-94 Table 5-95 Table 5-96 Table 5-97 Table 5-98 Table 5-99 Table 5-100 Table 5-101 Table 5-102 Table 5-103 Table 5-104 Table 5-105 Table 5-106 Table 5-107 Table 5-108 Table 5-109 Table 5-110 Table 5-111 Table 5-112 Table 5-113 Control Mode Page-Data Format (Page
Table 5-114 Table 5-115 Table 5-116 Table 5-117 Table 5-118 Table 5-119 Table 5-120 Table 5-121 Table 5-122 Table 5-123 Table 5-124 Table 5-125 Table 5-126 Table 5-127 Table 5-128 Table 5-129 Table 5-130 Table 5-131 Table 5-132 Table 5-133 Table 5-134 Table 5-135 Table 5-136 Table 5-137 Table 5-138 Table 5-139 Table 5-140 Table 5-141 Table 5-142 Table 5-143 Table 5-144 Table 5-145 Table 5-146 Table 5-147 Table 5-148 Table 5-149 Table 5-150 Table 5-151 Table 5-152 Table 5-153 Table 5-154 Table 5-155 PERSIST
Table 5-156 Table 5-157 Table 5-158 Table 5-159 Table 5-160 Table 5-161 Table 5-162 Table 5-163 Table 5-164 Table 5-165 Table 5-166 Table 5-167 Table 5-168 Table 5-169 Table 5-170 Table 5-171 Table 5-172 Table 5-173 Table 5-174 Table 5-175 Table 5-176 Table 5-177 Table 5-178 Table 5-179 123 Table 5-180 Table 5-181 Table 5-182 Table 5-183 Table 5-184 Table 5-185 Table 5-186 Table 5-187 Table 5-188 Table 5-189 Table 5-190 Table 5-191 Table 5-192 Table 5-193 Table 5-194 Table 5-195 Table 5-196 RELEASE (6) Com
Table 5-197 Table 5-198 Table 5-199 Table 5-200 Table 5-201 Table 5-202 Table 5-203 Table 5-204 Table 5-205 Table 5-206 Table 5-207 Table 5-208 Table 5-209 Table 5-210 Table 5-211 Table 5-212 Table 5-213 Table 5-214 Table 5-215 Table A-1 Table A-2 Table A-3 Table A-4 Table A-5 Table A-6 Table B-1 Table B-2 Table B-3 SET DEVICE IDENTIFIER Parameter List-Data Format....................... 5-132 SET DEVICE IDENTIFIER Parameter List-Field Descriptions ..............
Chapter 1 ABOUT THIS MANUAL This chapter gives an overview of the contents of this manual, including the intended audience, how the manual is organized, terminology and conventions, and references. 1.1 AUDIENCE The Maxtor Atlas 10K V Product Manual is intended for reference by original equipment manufacturers (OEMs) that are integrating the disk drive into a system or subsystem, developers, and disk drive installers.
1.3 TERMINOLOGY AND CONVENTIONS In the Glossary at the back of this manual, you can find definitions for many of the terms used in this manual.
The typographical and naming conventions used in this manual are listed below. Conventions that are unique to a specific table appear in the notes that follow that table. Typographical Conventions: • Names of Bits: Bit names are presented in initial capitals. An example is the Host Software Reset Bit. • Commands: Firmware commands are listed as all capitals. An example is MODE SELECT. • Parameters: Parameters are given as initial capitals when spelled out, and are given as all capitals when abbreviated.
Chapter 2 GENERAL DESCRIPTION This chapter summarizes the general functions and key features of the Maxtor Atlas 10K V family of hard disk drives, as well as the applicable standards and regulations. 2.1 PRODUCT OVERVIEW Maxtor Atlas 10K V hard disk drives are part of a family of high performance, 1-inch-high hard disk drives manufactured to meet the highest product quality standards. There are currently three models in the Maxtor Atlas 10K V series, with capacities of 73.5, 147.
Performance • Average seek time of 4.0 ms (1D) , 4.2 (2D) and 4.4 (4D) for reads • Average seek time of 4.5 ms (1D), 4.7 (2D), and 4.9 ms (4D) for writes • 10,000 RPM rotational speed • Average rotational latency of 3 ms • 8 MB CACHE (ECC Protected) buffer.
• MaXAdaptTM ~ Adaptive Active Filter (AAF) ~ Rotational Vibration Compensation (RVC) ~ Adaptive Bias Estimation (ABE) ~ Virtual Cache Line (VCL) • Ultra 320 Performance Enhancements ~ Double Transition (DT) Data Transfer ~ Free Running Clock (FRC) ~ Skew Compensation ~ Cyclic Redundancy Check (CRC) ~ Domain Validation ~ Information Unit (IU) Transfers ~ Transmitter Pre-Compensation with Cutback ~ Quick Arbitration and Selection (QAS) ~ Asynchronous Information Protection (AIP) ~ SCSI Bus Fairness ~ Flow
Versatility • Downloadable firmware • Plug-and-Play SCSI • SCSI-2, Ultra160 SCSI, and Ultra320 SCSI compatibility 2.3 REGULATORY COMPLIANCE STANDARDS Maxtor Corporation’s disk drive products meet all domestic and international product safety regulatory compliance requirements. Maxtor’s disk drive products conform to the following specifically marked Product Safety Standards: • Underwriters Laboratories (UL) Standard 1950 3rd Edition. This certificate is category UL recognized pertaining to all 3.
Product EMI/EMC Qualifications: Maxtor Corporation’s disk drive products meet all domestic and international electromagnetic emissions and immunity requirements. Maxtor’s disk drive products conform to the following EMI/EMC Standards • CE Mark (Europe) is a Self Declaration as per Directive 89/336, EN55022: 1998 (Emissions) and EN55024: 1998 (Immunity). • C-Tick Mark (Australia/New Zealand) is a Self Declaration as per AS/NZS3548: 1998. • BSMI Mark (Taiwan) is a Self Declaration as per CNS 13438:1998.
Chapter 3 INSTALLATION This chapter explains how to unpack, configure, mount, and connect the Maxtor Atlas 10K V hard disk drive prior to operation. It also explains how to start up and operate the drive. 3.1 SAFETY, HANDLING, & ELECTROSTATIC DISCHARGE PROTECTION 3.1.1 Safety Precautions For your safety, follow all safety procedures described here and in other sections of the manual.
• Always handle the drive carefully and gently. A drop of 1/4 inch onto a bench or desktop can damage a drive. • Do not bump, jar, or drop the drive. Use care when transporting the drive. • Always gently place the drive flat, PCB side down, on an appropriate ESD-protected work surface to avoid the drive being accidentally knocked over. • Do not pack other materials with the drive in its shielded bag. • Place the drive in the anti-static bag before placing in shipping container.
3.2 SPACE REQUIREMENTS The Maxtor Atlas 10K V hard disk drive is shipped without a faceplate and comes in the following SCSI interface configurations: • 68-pin Wide SCSI • 80-pin SCA-2 SCSI Figure 3-1 Shows The Mechanical Dimensions of the drives.
3.2.1 Shock Feet Maxtor Atlas 10K V hard disk drives are outfitted with plastic shock feet on the bottom edge of the base casting, near the corners, beneath the side mounting holes (translucent), and near the corners of the top cover next to the screws (black). The shock feet give an additional level of isolation to prevent the head and disk damage that occasionally occurs during unpacking, staging, and installation.
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.
3.4 HARDWARE OPTIONS 3.4.1 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.
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 Maxtor Atlas 10K V 3-7
Table 3-1 SCSI ID Selection on Option Connector (68-Pin SCSI Connector Drives) Jumper Location – J3 Option Header SCSI ID Pin Pair 7/8 Pin Pair 5/6 Pin Pair 3/4 Pin Pair 1/2 0 0 0 0 0 1 1 0 0 0 2 0 1 0 0 3 1 1 0 0 4 0 0 1 0 5 1 0 1 0 6 0 1 1 0 7 1 1 1 0 8 0 0 0 1 9 1 0 0 1 10 0 1 0 1 11 1 1 0 1 12 0 0 1 1 13 1 0 1 1 14 0 1 1 1 15 1 1 1 1 Note: 0 = No Jumper, 1 = Jumper Installed Configure the drive for remote (external) SC
3.4.2.2 Delay Spin (DS), Stagger Spin (SS) Maxtor Atlas 10K V drives have three Spin Up modes: Option 1 (No jumpers installed): Spin up immediately when power is applied. Verify that no jumper is installed across the Delay Spin pin pair of the J3 Option Header. Option 2 (Delay Spin jumper installed): Spin up on START STOP UNIT command: Install the jumper across pin pair 15/16 (GND/Delay Spin) on the J3 Option Header. 3.4.2.
3.4.3 SCA-2 80-Pin Connector Versions This section describes the SCA-2 (Single Connector Attachment) 80-pin connector for Maxtor Atlas 10K V drives with the following features: • SCSI ID • Spin Up • Activity LED displays Use Figure 3-4 to locate the appropriate pins for configuring the drive. Note that Figure 3-4 does not call out each of the 80 pins on the connector, but rather illustrates the layout of the pins.
3.4.3.2 SCSI ID for SCA-2 Versions Each SCSI device on the bus must have a unique SCSI ID number assigned to it. The drive can be configured for SCSI ID numbers that range from 0 through 15. Configure the SCSI ID by providing the proper open or ground signal inputs to the referenced pins of the drive’s 80-pin new version SCA-2 connector (Figure 3-4). Refer to Table 3-2 for SCSI ID pin assignments.
Table 3-2 SCSI ID Pin Assignments (SCA-2 Connector Versions of the Disk Drive) Location on SCA Connector SCSI ID ID3 - Pin 80 ID2 - Pin 40 ID1 - Pin 79 ID0 - Pin 39 0 0 0 0 0 1 0 0 0 1 2 0 0 1 0 3 0 0 1 1 4 0 1 0 0 5 0 1 0 1 6 0 1 1 0 7 0 1 1 1 8 1 0 0 0 9 1 0 0 1 10 1 0 1 0 11 1 0 1 1 12 1 1 0 0 13 1 1 0 1 14 1 1 1 0 15 1 1 1 1 Note: 0 indicates an open circuit and 1 indicates ground. 3.4.3.
Table 3-3 Spin Up on Power On Options Option STAGGER_SPIN (Pin 78) DELAY_SPIN (Pin 38) Open Open Ground Open Open Ground Ground Ground Option 1 – Spin Up When Power is Applied Option 2 – Spin Up After Delay Option 3 – Spin Up on START Command Reserved 3.4.3.4 Activity LED for SCA-2 Connector Versions The drive provides the output BUSY_OUT signal to power a user-supplied activity LED. The output indicates the drive is performing a SCSI operation.
3.5 INTERFACE CONNECTOR (J1) The configuration of J1 is different for the 68-pin and 80-pin SCSI variations. Figure 3-5 shows the various connector styles.
Maxtor Atlas 10K V 3-15
3.5.
3.5.2 80-Pin SCA-2 SCSI Connector - LVD Table 3-5 80-PIN CONNECTOR CONTACT AND SIGNAL NAME 12V CHARGE 1 12V 2 12V 80-Pin SCA-2 LVD Pin Assignments CABLE CONDUCTOR NUMBER NOT APPLICABLE 80-PIN CONNECTOR CONTACT AND SIGNAL NAME 12V GROUND 41 12V GROUND 42 3 12V GROUND 43 12 V 4 MATED 1 44 OPT 3.3 VOLTS 5 OPT 3.3V CHARGE 45 OPT 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) 3.5.2.1 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 NOT APPLICABLE +DB (2) +DB (1) +DB (0) +DB (P1) +DB (15) +DB (14) +DB (13) +DB (12) MATED 2 5V GROUND 5V GROUND ACTIVE LED OUT DLYD_START SCSI ID (1) SCSI ID (3) 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 80-Pin SCA-2 Mating Connectors The compatible 80-pin mating connectors are: • Right-angle receptacle, AMP CHAMP, .
3.5.
3.5.4 80-Pin SCA-2 Single-Ended SCSI Connector Table 3-7 80-Pin SCA-2 Single-Ended Pin Assignments 80-PIN CONNECTOR CONTACT AND SIGNAL NAME 12V CHARGE 12V 12V 12 V OPT 3.3 VOLTS OPT 3.
3.6 DRIVE MOUNTING AND INSTALLATION Drive mounting orientation, clearance, and ventilation requirements are described in the following subsections. 3.6.1 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.
3.6.2 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.
3.6.3 Mounting For the best results during performance benchmark testing, it is highly recommended that the drive be mounted firmly in a system or fixture, rather than sitting unconstrained on a tabletop. If it is necessary to do early testing of the drive while it is unconstrained, the drive should rest on a flat, smooth, semi-cushioned surface (similar to a mousepad). The drive should not be operated on a hard surface—this avoids performance degradations due to the higher incidence of recovered errors.
Above Unit Below Unit Figure 3-9 Crosswise Airflow Cooling 3-24 Maxtor Atlas 10K V
Chapter 4 SPECIFICATIONS This chapter gives a detailed description of the physical, electrical, and environmental characteristics of the Maxtor Atlas 10K V hard disk drives. 4.1 SPECIFICATION SUMMARY Table 4-1 Specifications MAXTOR ATLAS 10K V 73.5 GB MAXTOR ATLAS 10K V 147.1 GB MAXTOR ATLAS 10K V 300 GB Non-RoHS Model Numbers: 8D073J0 8D073L0 8D147J0 8D147L0 8D300J0 8D300L0 RoHS Model Numbers: 8J073J0 8J073L0 8J147J0 8J147L0 8J300J0 8J300L0 Formatted Capacity 73.5 GB 147.
DESCRIPTION Maximum effective areal density MAXTOR ATLAS 10K V 73.5 GB MAXTOR ATLAS 10K V 147.1 GB MAXTOR ATLAS 10K V 300 GB 75 Gbits/in2 75 Gbits/in2 75 Gbits/in2 Servo Mechanical Timing Specifications: Sequential Head Switch Time2 0.3 ms read 0.5 ms write 0.3 ms read 0.5 ms write 0.3 ms read 0.5 ms write Sequential Cylinder Switch Time3 0.3 ms read 0.5 ms write 0.3 ms read 0.5 ms write 0.3 ms read 0.5 ms write Random4 Average Seek (Read) 4.0 ms typical 4.2 ms typical 4.
1. Typical specifications assume 25°C ambient temperature, nominal supply voltages and no applied shock or vibration. Maximum specifications assume worst case extremes of operating temperature, humidity, and supply voltages. 2. Sequential Head Switch time is the time from the conclusion of the last sector of a track to the beginning of the first logical sector on the next track of the same cylinder. It includes sequencer overhead for write setup on head and cylinder switch. 3.
4.3 DATA TRANSFER RATES Data is transferred from the disk to the read buffer at a rate of up to 89 MB/s in bursts. Data is transferred from the read buffer to the SCSI bus at a rate of up to 6 MB/s in the asynchronous mode, or at up to 320 MB/s in the synchronous mode. For more detailed information on interface timing, refer to Chapter 6. 4.4 TIMING SPECIFICATIONS Table 4-3 illustrates the timing specifications of the Maxtor Atlas 10K V hard disk drive.
8. At power on start up error algorithms are used and may extend the time to Drive Ready to as long as 30 seconds. 4.5 POWER The Maxtor Atlas 10K V hard disk drive operates from two supply voltages: MAXTOR ATLAS 10K IV 73.5/147.1/300 GB +12 V +/-10% @ Spin up, +/- 5% While running +5 V +/- 5% Allowable ripple and noise for each voltage: 4.5.
4.5.3 Drive Power Dissipation Table 4-5 lists the drive power dissipation and the corresponding currents for the various modes of operation of the Maxtor Atlas 10K V hard disk drive. Table 4-5 Power Dissipation in Various Modes (Low-Profile Drives) TYPICAL AVERAGE CURRENT1, 4 (AMP RMS UNLESS OTHERWISE NOTED) MODE OF OPERATION +12V TYPICAL AVG. POWER5 (WATTS) +5V 73.5 GB 147.1 GB 300 GB 73.5 GB 147.1 GB 300 GB 73.5 GB 147.1 GB 300 GB Startup peak1 1.34 1.33 1.57 0.84 0.68 0.69 19.7 19.
4.6 ACOUSTICS Table 4-6 specifies the acoustical characteristics of the Maxtor Atlas 10K V hard disk drive. The acoustics is measured in an anechoic chamber with background noise <25 dBA. Table 4-6 Acoustical Characteristics—Sound Power per ISO 7779 OPERATING MODE SOUND POWER (MEAN) SOUND POWER (MEAN + 3 SIGMA) MAXTOR ATLAS 10K IV 73.5/147.1/300 GB Idle On Track 73.5 GB 147.1 GB 300 GB 3.16 3.52 3.67 3.38 3.68 3.91 Seeking Random 73.5 GB 147.1 GB 300 GB 3.60 3.87 3.96 3.72 4.04 4.19 1.
4.7 MECHANICAL The Maxtor Atlas 10K V hard disk drives have the following mechanical characteristics: Height1: Width: Depth: Weight (4-disk): 1.028 in. 4.0 in. 5.787 in. 1.8 Ib (26.1 mm) (101.6 mm) (147.0mm) (820 grams) All dimensions are exclusive of any optional faceplate. Drive mode small form factor specifications. 1. Except when shock feet are uncompressed (see of Chapter 3). 4.
4.9 ELECTROMAGNETIC CONDITIONS 4.9.1 EMI/RFI Susceptibility 3 Volts/meter 80% modulated from 80 to 1000 MHz. 4.9.2 ESD Drive must function with no data loss or component damage with air discharges of 1 to 15 KV, and contact discharges of 2 to 8 KV in both positive and negative voltages. 4.9.3 Sensitivity to Magnetic Fields The Maxtor Atlas family of drives meet 3A @ 230V / 50 Hz specification. 4.
4.11 RELIABILITY Component Life: 5 years Preventive Maintenance (PM): Not required Contact Start/Stop: 50,000 cycles at ambient, 35,000 at Environments Annualized Failure Rate (AFR) No greater than 0.58 percent Drive reliability is closely related to the temperatures the drive is exposed to. The AFR is based on an operational design temperature ambient of 86° F (30° C) 4.12 DISK ERRORS Table 4-9 provides the error rates for the Maxtor Atlas 10K V hard disk drive.
Chapter 5 SCSI Description This chapter contains an overview of SCSI command and status processing and a detailed description of the commands supported by the disk drives. The SCSI command system enables the initiator to instruct the drive to perform specific functions. In this manual, unless otherwise stated, numerical values are given in decimal. Hexadecimal numbers, such as opcodes, are always given with an “h” following, as in 5Ah except when entire data tables are in hexadecimal. 5.
5-2 Command Operation Code Category PERSISTENT RESERVATION OUT 5Fh Sequential READ (6) 08h Normal READ (10) 28h Normal READ BUFFER 3Ch Sequential READ CAPACITY 25h Immediate READ DEFECT DATA (10) 37h Sequential READ DEFECT DATA (12) B7h Sequential READ LONG 3Eh Sequential REASSIGN BLOCKS 07h Sequential RECEIVE DIAGNOSTIC RESULTS 1Ch Sequential RELEASE 17h Sequential RELEASE (10) 57h Sequential REPORT LUNS A0h Sequential REPORT DEVICE IDENTIFIER A3h Sequential RE
1. Relative Addressing is not supported by the drive. Therefore, in all I/O commands, the RelAdr bit must be 0. 2. RESERVE and RELEASE are supported, as are third-party reservations. Extent reservations are not supported. 3. The RECEIVE DIAGNOSTIC RESULTS and SEND DIAGNOSTIC DATA commands implement vendor-unique pages to test the drive during the manufacturing process. It is recommended that initiators specify only the non-page format variants of these commands (PF=0), except for page 0x40.
5.2 Command Descriptor Block An initiator communicates with the drive by sending a 6-, 10-, or 12-byte Command Descriptor Block (CDB) that contains the parameters for the specific command. The SCSI command's operation code is always the first byte in the CDB and a control field is the last byte. For some commands, the CDB is accompanied by a list of parameters sent during the data-out buffer transfer. Table 5-2 shows the format of a typical sixbyte CDB.
Field Description Logical Block Address The 6-byte READ, SEEK, and WRITE Command Descriptor Blocks contain a 21-bit Logical Block Address. The 10-, 12-, and 16- Command Descriptor Blocks contain a 32-bit Logical Block Address. Commands that require additional parameter data specify the length of the Logical Block Address that is needed. See the specific command descriptions for more detailed information.
Table 5-5 contains a description of the CDB control field. Table 5-5 Command Descriptor Block Control Field-Field Descriptions Field Vendor Specific Bits Description These bits must be 0. NACA Normal Auto-Contingent Allegiance - This bit must be zero to indicate that SCSI-2 Contingent Allegiance rules apply. Link Bit A Link bit set to one signals that the initiator requests continuation of a task (I/O Process) across two or more SCSI commands.
5.3 Status/Error Reporting SCSI message-level errors are communicated by messages that are defined specifically for that purpose. SCSI command-level errors are communicated by a status that is returned by the drive during the STATUS phase.
command is one in which the Link bit in the Command Descriptor Block is set. After successful completion of a linked command the drive sends an INTERMEDIATE status, followed by a LINKED COMMAND COMPLETE message. If the Flag bit was set in the Command Descriptor Block, the drive sends an INTERMEDIATE status, followed by a LINKED COMMAND COMPLETE (WITH FLAG) message. The drive then switches the bus to the command phase in order to receive the next command in the linked chain.
5.5 DATA Transfer Command Components Many of the SCSI commands cause data to be transferred between the initiator and the drive. The content and characteristics of this data are command-dependent. Table 5-8 lists the information transmitted for all of the commands. The “Length in CDB” column of Table 5-8 identifies the Command Descriptor Block field used by the drive to determine how much command-related data are to be transferred.
Command Length in CDB Data Out (To Drive) Data In (To Initiator) READ BUFFER Allocation --- READ CAPACITY Allocation --- READ DEFECT DATA Allocation --- • Defect List (Hdr) (4) • Defect Descriptors • Data (512) • LBA Tag (2) • EDC (2) • ECC (60) • Fill (2) READ BUFFER Header (4) Mode-zero Buffer (512) or Section of Drive’s DRAM or READ BUFFER Desc.
5.6 Command Length in CDB WRITE LONG Byte Transfer (must be 578) WRITE SAME 0 Data Out (To Drive) • Data (512) • LBA Tag (2) • EDC (2) • ECC (60) • Fill (2) Data In (To Initiator) -- Data (1 logical sector) SCSI COMMAND DESCRIPTIONS The SCSI command descriptions that follow this page contain detailed information about the SCSI commands that are supported by the drive. Each description provides a Data Format and Field Descriptions for the Command Descriptor Block for the described command.
5.7 CHANGE OPERATING DEFINITION (40h) The CHANGE DEFINITION command shown in Table 5-9 and Table 5-10 set the SCSI compliance for disk drives with parallel SCSI interfaces to one of four different levels: SCSI-1, SCSI-1/CCS, SCSI-2 or SCSI-3.
5.8 FORMAT UNIT Command (04h) The FORMAT UNIT command formats the disk's storage media into initiatoraddressable logical blocks according to initiator-defined options. This command ensures that the disk storage media is formatted so that all data sectors are accessible. Any data residing on the disk before this command is invoked is lost. This command repairs damage left by previous WRITE LONG commands. The WRITE LONG command allows the initiator to deliberately corrupt a sector's ECC or EDC.
Table 5-11 FORMAT UNIT Command Descriptor Block-Data Format Bit Byte 7 6 5 0 4 3 2 1 0 Operation Code (04h) 1 Reserved Fmt Data Cmp List 2 Vendor-Specific 3-4 Interleave 5 Control Defect List Format Table 5-12 FORMAT UNIT Command-Field Descriptions Field Description FmtData Format Data. When the Format Data value is 1, it indicates that a data-out buffer transfer occurs as part of the command execution.
5.8.1 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.
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 .
5.8.2.2 FORMAT UNIT Defect Descriptor-Block Format Each descriptor specifies a 4-byte defective sector address of the sector that contains the defect as shown in Table 5-17. Table 5-17 FORMAT UNIT Defect Descriptor-Block Format Bit Byte 7 6 5 0-3 5.8.2.3 4 3 2 1 0 Defective Block Address FORMAT UNIT Defect Descriptor — Physical Sector and Bytes From Index Format The Physical Sector defect descriptor specifies the location of a defect that is the length of a sector.
Table 5-20 FORMAT UNIT Initialization Pattern Descriptor-Field Descriptions Name Description IP Modifier The Initialization Pattern Modifier must be 0. IP Type The Initialization Pattern Type field (Table 5-21) indicates the type of pattern the drive uses to initialize each logical sector within the initiator-accessible portion of the medium. All bytes within a logical sector are written with the initialization pattern.
5.9 INQUIRY Command (12h) The INQUIRY command allows the initiator to determine the kind of SCSI devices attached to its SCSI bus. It causes a device that is attached to a SCSI bus to return information about itself. The drive identifies itself as a Direct Access Storage Device that implements the applicable interfacing protocol. The drive does not need to access its storage medium to respond to the inquiry. The INQUIRY commands are described in Table 5-22 and Table 5-23.
5.9.1 Standard Inquiry Data Page The Standard Inquiry Data Page is returned by the drive in response to the INQUIRY command if EVPD = 0. The data format is described inTable 5-24 and the fields are described in Table 5-25.
Table 5-25 Standard Inquiry Data Page-Field Descriptions Field Name Value Description Peripheral Qualifier 0 Non-zero if initiator selects an invalid logical unit. Peripheral Device 0 0 indicates that this is a Direct Access Device. ANSI Version 3 ANSI SCSI Level 3 (SCSI-3) is supported. AERC 0 Asynchronous Event Reporting is not supported. NormACA 0 Does not support setting NACA in CDB Control word. Port 0 Only used when MultiP = 1.
5.9.2 Vital Product Data Pages The Vital Product Data pages that can be returned by the drive are described in the following paragraphs in the sequence shown in Table 5-27. 5.9.2.1 Supported Vital Product Data Pages Page (00h) The Supported Vital Product Data Pages page (Table 5-26) provides a directory of the Vital Product Data Pages that are supported by the drive.Table 5-27 lists the supported pages.
5.9.2.3 Implemented Operating Definition Page (81h) The Implemented Operating Definition page reflects the current and available operation definitions as described in Table 5-30 and Table 5-31.
5.9.2.4 ASCII Implemented Operating Definition Page (82h) The ASCII Implemented Operating Definition page returns the character string's length (1Bh) in byte 4, followed by the appropriate character string (“SCSI-3, SCSI2, SCSI-1/CCS” in bytes 5 through 31 for Parallel SCSI. This is described in Table 5-32. Table 5-32 ASCII Implemented Operating Definition Page - Data Format Bit Byte 0 5.9.2.
Table 5-34 Device Identification Page - Field Description 5.9.2.6 Field Definition Code Set This field specifies the code set used for the Identifier field. Applicable values are: Value Description 0h Reserved 1h The Identifier field contains binary values 2h The Identifier field contains ASCII graphic codes (code values 20h through 7Eh) 3h – Fh Reserved Association This field specifies the entity with which the Identifier field is associated.
Table 5-36 Command Support Data Page-Field Descriptions Field Description Support The value of the Support field describes the type of support that the disk drive provides for Command Support Data. Value Description 000b Data about the requested SCSI operation code is not currently available. In this case, all data after Byte 1 is undefined. 001b The device does not support the SCSI operation code requested.
Table 5-37 Command Support Data Page Command or Operation Codes Hex Data Returned When INQUIRY is Received and CmdDt Bit =1 OpCode Command Support ANSI Version CDB Length CDB Size Usage Data 00h TEST UNIT READY 03 01 06 00E000000003 01h REZERO UNIT 03 01 06 01E000000003 03h REQUEST SENSE 03 01 06 03E00000FF03 04h FORMAT UNIT 03 01 06 04FFFFFFFF03 07h REASSIGN BLOCKS 03 01 06 070E00000003 08h READ (6) 03 01 06 08FFFFFFFF03 0Ah WRITE (6) 03 01 06 0AFFFFFFFF03 0B
Hex Data Returned When INQUIRY is Received and CmdDt Bit =1 40h CHANGE DEF. 03 01 0A 40E0017F000000000 003 41h WRITE SAME 03 01 0A 41E2FFFFFFFF00FF FF03 4Ch LOG SELECT 03 01 0A 4CE3C000000000FF FF03 4Dh LOG SENSE 03 01 0A 4DE1FF00000000FF FF03 55h MODE SELECT (10) 03 01 0A 55100000000000FFF F03 56h RESERVE (10) 03 03 0A 5610FFFF000000FF FF03 57h RELEASE (10) 03 03 0A 5710FFFF000000FF FF03 5Ah MODE SENSE (10) 03 01 0A 5AE8FF00000000FF FF03 5Eh PERSIST. RES.
5.10 LOG SELECT Command (4Ch) The drive collects and stores performance data and error summaries in counters. The LOG SELECT command is used to zero these counters. The LOG SELECT command is a complementary command to the LOG SENSE command. The format of the LOG SELECT CDB and a description of the fields follows in Table 5-38 and Table 5-39 respectively.
5.11 LOG SENSE Command (4Dh) Note: Log Sense data pages require special interpretation and also are subject to change. For assistance with the Log Sense data pages, contact your Maxtor Applications Engineer. The drive collects operational information and stores these statistics as log data. Log data are grouped by category into log pages. The LOG SENSE command allows an initiator to retrieve the stored log data. The LOG SENSE command is a complementary command to the LOG SELECT command.
5.11.1 LOG SENSE Command Descriptor Block The Command Descriptor Block for the LOG SENSE command is shown in Table 5-41. Table 5-42 contains field descriptions.
5.11.2 LOG SENSE Log Pages The log pages that are returned from the drive have a common format that is shown in Table 5-43. Each page contains a 4-byte header followed by one or more log parameters. Refer to Table 5-44. Table 5-45 contains the format for the Generic Log Parameter and Table 5-46 describes the fields.
Table 5-46 Generic Log Parameter-Field Descriptions Field Description Parameter Code A code which uniquely identifies each parameter on a given Log Page. For example, the code 8002h on the Seek Performance Summary page reports the average seek time while the same code on the Block Replacement Summary page reports the number of blocks replaced. The following pages in this manual contain the lists of applicable parameters for each Log page. DU Disable Update.
5.12 MODE SELECT (6) Command (15h) SCSI refers to the drive’s operational parameters as its mode parameters. SCSI groups the mode parameters by function into a set of data structures referred to as mode pages. The MODE SELECT (6) command allows the initiator to modify some of these mode pages and thereby control some of the drive’s operational characteristics. The Save Page (SP) option in the Command Descriptor Block makes the changes permanent.
Table 5-49 Initiator-Changeable Mode Pages Page Code Page Name Function Size In Bytes 00h Unit Attention Control Page Unit Attention reporting (enables or disables) 4 01h Read-Write Error Recovery Page Medium Access Error recovery and reporting procedures for READ and WRITE commands 12 02h Disconnect-Reconnect Page Bus behavior during data transfers 07h1 Verify Error Recovery Page Medium Access Error recovery and reporting procedures for the VERIFY command 12 08h1 Caching Page Cache pol
5.12.2 Mode Page Types The drive maintains three distinct sets of mode pages. They are the current page, the default page, and the saved page. The drive also reports a fourth set of changeable pages. The page types are defined in Table 5-50. Table 5-50 Mode Page Types Page Type Definition The current mode page set applies to all initiators and defines the drive’s mode. The SCSI-2 specification states that a drive can maintain Mode parameters on a per-initiator basis if it so chooses.
Table 5-52 Mode Parameter List-Field Descriptions Field Description Mode Parameter Header Contains information about the remainder of the parameter list and is always present (see Table 5-53 and Table 5-54). Block Descriptor Allows the initiator to set the drive’s Logical Block Size and number of Logical Block Addresses (see Table 5-55 and Table 5-56). The page code(s) of the pages that are a part of this command.
Table 5-56 Mode Parameter Block Descriptor-Field Descriptions Field Description If the number of blocks is set to zero, the device shall retain its current capacity if the block size has not changed. If the number of blocks is set to zero and the block size has changed, the device shall be set to its maximum capacity when the new block size takes effect. If the number of blocks is greater than zero and less than or equal to its maximum capacity, the device shall be set to that number of blocks.
Table 5-59 Unit Attention Condition Page (Page 0) 5.12.6 Field Default Value Description PS 1 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. The bit is reserved with the MODE SELECT command. DUA 0 Disable Unit Attention.
Table 5-61 Read-Write Error Recovery Page - Field Descriptions Field Default Value Description PS 1 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. The bit is reserved with the MODE SELECT command. AWRE 1 Automatic Write Reallocation Enable.
Field Default Value Description Recovery Time Limit 0 Specifies the maximum time, in milliseconds, that a retry is attempted on a failed sector during a read or write operation. When the value is 0, it means that there is no time limit. The minimum permissible value, however, is 100 milliseconds.
5.12.7 Disconnect–Reconnect Page (02h) The Disconnect–Reconnect Page provides the application client the means to attempt to optimize the performance of the delivery subsystem. The data format and field descriptions are described in Table 5-62 and Table 5-63.
Field Default Value EMDP 0 Fairness Arbitration 111b (Def) Description Enable MODIFY DATA POINTER. Not supported by the drive. Indicates whether or not the target should use fair or unfair (e.g., priority) arbitration when beginning the interconnect tenancy. 000b - Disables the fairness algorithm. A fixed priority scheme based on the SCSI ID assigned is used. Non-Zero - Any non-zero value enables the fairness algorithm (SCSI SPI-2 ANSI standard, Appendix B). DImm Disconnect Immediate.
Table 5-65 Verify Error Recovery Page-Field Descriptions (Page 7) Field Default Value Description PS 0 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. The bit is reserved with the MODE SELECT command. EER 0 Enable Early Recovery. Not supported by the drive. Post Error Recovery.
NOTES: Bytes 12 to 19 are returned only if the device operating definition is SCSI-3. Table 5-67 Caching Page - Field Descriptions Field Default Value Description PS 1 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. Bit reserved with MODE SELECT command.
Field Default Value Description Demand Read Retention Priority 0 This field advises the drive on the retention priority to assign data read into the cache that has also been transferred from the drive to the initiator. Demand Write Retention Priority 0 This field advises the drive on the retention priority to assign data written into the cache that has also been transferred from the cache memory to the medium.
4 EECA RAC Reserved SWP RAERP 5 Reserved 6–7 Ready AEN Holdoff Period 8–9 10 UAAER P EAERP Busy Timeout Period MSB 11 Extended Selftest Completion Time Extended Selftest Completion Time LSB NOTES: Bytes 8 to 11 are returned only if the device operating definition is SCSI-3.
Table 5-69 Control Mode Page-Field Descriptions Field Value Default Description PS 1 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. The bit is reserved with the MODE SELECT command. GLTSD 0 Global Logging Target Save Disable. If this bit = 1, the ability to save log ages to disk is disabled.
NOTES: If the Queue Algorithm Modifier specifies restricted re-ordering (0000b), commands are not allowed to execute concurrently. If this field specifies unrestricted re-ordering (0001b), concurrent I/O execution is allowed.
5.12.11 Notch and Partition Page (0Ch) The Notch and Partition page contains parameters for drives that implement a variable number of sectors per cylinder, and, support this page. Each section of the logical unit with a different number of sectors is referred to as a notch (or band). Each notch must span a set of consecutive logical blocks in the logical unit, the notches must not overlay, and no logical blocks can be excluded from the notches.
Table 5-71 Notch and Partition Page-Field Descriptions Data Field Description PS Parameters Savable. This bit is only used with the MODE SENSE command. The returned value of 0 indicates that the target is not capable of saving this page in a non-volatile vendor specific location. This bit is reserved with the MODE SELECT command. ND LPN Notched (banded) Drive. A value of 0 indicates that the drive is not notched and that all other parameters in this page are returned as 0.
5.12.12 Port Control Mode Page (19h) The port control mode page (see Table 5-72 and Table 5-73) contains those parameters that affect SPI SCSI device port operation options. The page will be implemented by LUN 0 of all SPI SCSI devices. The page will not be implemented by logical units other than LUN 0. The implementation of any bit and its associated functions is optional. The page follows the MODE SENSE/MODE SELECT rules specified by SCSI Primary Commands-2 standard.
Table 5-73 Port Control Page Long Format Bit Byte 7 6 0 PS LONG (1) 5 1 2 n 2 1 0 Page Code (19h) Page Length (n-3) LSB Page Length (n-3) 4 6 3 Subpage Code MSB 3 5 4 Reserved Reserved Protocol Identifier (1h) Protocol Specific Mode Parameters The Subpage Code field indicates which subpage is being accessed. Subpage Code values are listed in Table 5-93. If the Subpage Code field is zero, the target will return a CHECK CONDITION status.
5.12.12.1 Margin Control Subpage (Sub Page 1 of Mode Page 19) The Margin Control subpage (see Table 5-74) contains parameters that set and report margin control values for usage between the initiator/target pair on subsequent synchronous and paced transfers. A MODE SELECT command will return the current settings for the initiator/target pair. Fields that are not implemented will be reported as zero.
The Driver Strength field indicates the relative amount of driver source currently used by the driver. The Driver Strength field affects both the strong and week drivers. A larger value indicates more driver source current. The Driver Precompensation field indicates the relative difference between the weak driver and the strong driver amplitudes when precompensation is enabled. A larger value indicates a larger difference between the weak and strong amplitudes.
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.
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.
The TRANSCEIVER MODE field specifies the current bus mode of the target as defined in Table 5-79. Table 5-79 Transceiver Mode Code Transceiver Mode 00b Unknown (device not capable of reporting bus mode) 01b Single-ended 10b Low-Voltage Differential 11b 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) The report transfer capabilities subpage is used to report the transfer capabilities for the SCSI target port. The values in this subpage are not changeable via a MODE SELECT command.
5.12.13 Information Exceptions Control Page (1Ch) This page defines the methods used by the disk drive to control the reporting and operations of specific informational exception conditions. This page applies only to informational exceptions that report an additional sense code of FAILURE PREDICTION THRESHOLD EXCEEDED to the application client. Informational exception conditions occur as the result of vendor-specific events within a disk drive.
Table 5-83 Information Exceptions Control Page-Field Descriptions (Page 1Ch) Field Default Value Description PS 1 Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. This bit is reserved with the MODE SELECT command. PERF 1 Performance. This bit enables/disables performance-sensitive functions.
Table 5-84 Codes Used by the MRIE Field Field Description 0h No reporting of informational exception condition. This method instructs the disk drive not to report these conditions. 1h Asynchronous Event Reporting. This method of reporting instructs the disk drive to report informational exception conditions by using the rules for asynchronous event reporting as described in the SCSI-3 Architecture Model and the relevant Protocol Standard.
5.13 MODE SELECT (10) Command (55h) The MODE SELECT (10) command allows the initiator to modify certain mode pages and thereby control some of the drive’s 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.
Table 5-88 Mode Parameter Block Descriptor-Field Descriptions 5-64 Data Field Description Number of Blocks 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. Density Code The Density Code field is unique for each device type. Direct access devices value is zero.
5.14 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-92 Mode Parameter Header and Block Descriptor-Field Descriptions Data Field Description Mode Data Length Length of the returned data Medium Type Always zero (0) Device-Specific Parameter Bit 7 - This bit is set if the drive is write protected Bit 4 - This bit is always set to indicate that the drive supports cache memory. Zero (0) if Block Descriptor (DBD) in MODE SENSE Command Descriptor Length sector is 0. Block Descriptor If DBD is 1, then the Block Descriptor Length is eight (8).
21 - 23 Reserved Maxtor Atlas 10K V 5-67
Table 5-95 Format Device Page-Field Descriptions (Page 3) Field Description PS Parameters Savable. This bit is only used with the MODE SENSE command. This bit is reserved with the MODE SELECT command. A PS bit value of 1 indicates that the disk drive is capable of saving the page in a non-volatile vendor specific location. Tracks/Zone The number of physical tracks per cylinder. Alternate Sectors/Zone The number of spare locations within a notch.
5.14.3 Rigid Disk Geometry Page (04h) The Rigid Disk Geometry Page describes the drive geometry. The data format and field descriptions are described in Table 5-96 and Table 5-97 respectively.
Table 5-97 Rigid Disk Geometry Page-Field Descriptions (Page 4) Field Description PS Parameters Savable. This bit is only used with the MODE SENSE command. A returned value of 1 indicates that the target is capable of saving the page in a non-volatile, vendor-specific location. The bit is reserved with the MODE SELECT command. Number of Cylinders The number of physical cylinders that hold host data. Number of Heads The number of heads that can access host data.
5.15 MODE SENSE (10) COMMAND (5Ah) The MODE SENSE command allows the initiator to read the drive’s sector descriptor and mode pages. See Table 5-98 for MODE SENSE (10) Command Descriptor Block – Data Format, Table 5-99 for Mode Parameter Header (10 Byte) — Data Format, and Table 5-100 for Mode Parameter Block Descriptor – Data Format. Refer to Table 5-90,Table 592, and Table 5-101 for descriptions of the fields.
Table 5-101 Mode Parameter Header & Block Descriptor-Field Descriptions Data Field Mode Data Length Medium Type Device Specific Parameter Block Descriptor Length Density Code Number of Blocks Block Length 5-72 Description Length of the returned data. Always zero (0). Bit 7 - This bit is set if the drive is write protected. Bit 4 - This bit is always set to indicate that the drive supports cache memory. The value = 0 if no Block Descriptor is supplied; the length is 8 if a block descriptor is supplied.
5.16 PERSISTENT RESERVATION IN Command (5Eh) The PERSISTENT RESERVATION IN command is a 10-byte command used to obtain information about persistent reservations and reservations that are active within a device server. It is used in conjunction with the PERSISTENT RESERVATION OUT command.
Table 5-103 PERSISTENT RESERVATION IN Command-Field Descriptions Data Field Description Service Action Service actions that require information about persistent reservation and registrations may require enabling of nonvolatile memory within the logical unit.
Table 5-105 Read Keys Parameters-Field Descriptions Data Field Description The value in this field is a 32-bit counter in the device server that is incremented each time a PERSISTENT RESERVATION OUT command requests a Register, Clear, Pre-empt, or Pre-empt and Clear operation.
Table 5-107 Read Reservations Parameters-Field Descriptions Data Field Description The value in this field is a 32-bit counter in the device server that is incremented each time a PERSISTENT RESERVATION OUT command requests a Register, Clear, Pre-empt, or Pre-empt and Clear operation.
Table 5-109 PERSISTENT RESERVATION IN Read Reservations Descriptor-Field Descriptions Data Field Description Reservation Key The Reservation key field contains an 8-byte value that identifies the reservation key under which the persistent reservation is held.
Table 5-110 Persistent Reservation Type Codes and Their Meanings Code Name Description READS: Shared; any application client on any initiator may execute commands that perform transfers from the disk to the initiator. 0h READ Shared WRITES: Prohibited; any command from any initiator that performs a transfer from the initiator to the disk results in a reservation conflict.
Code Name Description READS: Shared; any application client on any initiator may execute commands that perform transfers from the disk to the initiator.
Table 5-111 represents graphically all possible combinations of Persistent Reservations Being Attempted when Persistent Reservations are already held for each of the types of persistent reservations.
5.17 PERSISTENT RESERVATION OUT Command (5Fh) The PERSISTENT RESERVATION OUT command is a 10-byte command used to reserve a logical unit or an extent within a logical unit for the exclusive or shared use by an initiator. The command is used in conjunction with the PERSISTENT RESERVATION IN command; it is not used with the RESERVE and RELEASE commands. Persistent reservations conflict with reservations made via the RESERVE command.
Table 5-113 PERSISTENT RESERVATION OUT Command-Field Descriptions Data Field Description Service Action Service actions that require information about persistent reservation and registrations may require enabling of nonvolatile memory within the logical unit.
Table 5-114 provides detailed descriptions of each of the PERSISTENT RESERVATION OUT command’s seven possible service actions (Service Action codes appear in bits 0 – 4 of Byte 1). Table 5-114 PERSISTENT RESERVATION OUT Command’s Service Action Descriptions Code Name Description When the command executes a Register service action, it registers a reservation key with a device server without generating a reservation.
Code Name Description A PERSISTENT RESERVATION OUT command with Release service action removes a persistent reservation held by the same initiator. The fields associated with a Release service action match fields of the active persistent reservation. Sending of a PERSISTENT RESERVATION OUT command that specifies a Release service action when no persistent reservation exists from that initiator does not result in an error.
Code Name Description A PERSISTENT RESERVATION OUT command with a successful Pre-empt service action removes all persistent reservations for all initiators that have been registered with the Service action Reservation key specified in the PERSISTENT RESERVATION OUT command’s parameter list. A persistent reservation is also established for the pre-empting initiator. Any commands from any initiator that have been accepted by the device server as nonconflicting continue their normal executions.
Code Name Description A PERSISTENT RESERVATION OUT command with a Pre-empt & Clear service action removes all persistent reservations for all initiators that have been registered with the Service action Reservation key specified in the PERSISTENT RESERVATION OUT command’s parameter list. It also establishes a persistent reservation for the pre-empting initiator.
Table 5-115 presents the definitions of the characters of the available “Type” values from the Type field of the PERSISTENT RESERVATION IN Read Reservations parameters. Each of the codes provides handling instructions for READ operations, for WRITE operations, and for subsequent attempts to establish persistent reservations (referred to as “Additional Reservations Allowed” in the table).
Code Name Description READS: Shared; any application client on any initiator may execute commands that perform transfers from the disk to the initiator. WRITES: Shared; any application client on any initiator may execute commands that perform transfers to the disk from the initiator.
(MSB) 22 – 23 Extent Length (LSB) Maxtor Atlas 10K V 5-89
Table 5-117 PERSISTENT RESERVATION OUT Parameter List-Field Descriptions Data Field Description Reservation Key This field contains an 8-byte token that is provided by the application client to the device server to identify which initiator is the source of the PERSISTENT RESERVATION OUT command. The device server verifies that the Reservation Key in the PERSISTENT RESERVATION OUT command matches the Reservation Key that is registered for the initiator from which the command is received.
Table 5-118 illustrates which fields are set by the application client and interpreted by the device server for each Service and Scope value.
5.18 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.
5.19 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.
5.20 READ BUFFER Command (3Ch) The READ BUFFER command is used in conjunction with the WRITE BUFFER command. It allows the initiator to gain access to the data storage areas within the drive's controller. In particular, these two commands are used to check the integrity of the buffer-initiator data path, independent of the media, typically for fault isolation in the event of a failure.
Table 5-124 READ BUFFER Command-Field Descriptions Field Description Mode Four modes are supported by the drive; Combined Header and Data, Data Only, Descriptor Only, and Read Data from Echo Buffer. The permissible values for Buffer ID, Buffer Offset, are as follows: Combined Header and Data – In this mode, data to be transferred is preceded by a 4-byte header that contains the buffer capacity.
5.21 READ CAPACITY Command (25h) The READ CAPACITY command reports formatted capacity and track-boundary information. The data format and field descriptions are shown in Table 5-125 and Table 5-126 respectively.
5.22 READ DEFECT DATA Command (10) (37h) The READ DEFECT DATA (10) command directs the drive to report defect information about the drive’s medium. Refer to the FORMAT UNIT command for information about defects. The data format and field descriptions are shown in Table 5-128 and Table 5-129 respectively. The data sent to the host in the command’s datain buffer transfer consists of a four-byte Defect List header (Table 5-132 and Table 5-133), followed by any Defect Descriptors (Table 5-130 and Table 5-131).
Table 5-129 READ DEFECT DATA (10) Command-Field Description Field Description When the value is 0, the returned data does not include the Primary Defect List. PList When the value is 1, the returned data includes the Primary Defect List. The defects are returned in ascending order. When the value is 0, the returned data does not include the Grown Defect List. When the value is 1, the returned data includes the Grown Defect List. The defects are returned in order of occurrence.
Table 5-131 shows the Defective Bytes From Index Format when the Defect List Format is 100b or the Physical Sector Format when the Defect List Format is 101b.
5.23 READ DEFECT DATA Command (12) (B7h) The READ DEFECT DATA (12) command directs the drive to report defect information about the drive’s medium. Refer to the FORMAT UNIT command for information about defects. The data sent to the host in the command’s data-in buffer transfer consists of a four-byte Defect List header (Table 5-138 and Table 5-139), followed by any Defect Descriptors (Table 5-136 and Table 5-137).
Table 5-136 shows the Block Format returned when the Defect List Format is 000b. Table 5-136 Defect Descriptor-Block Format Bit Byte 7 6 5 0-3 4 3 2 1 0 Defective Block Address Table 5-137 shows the Defective Bytes From Index Format when the Defect List Format is 100b or the Physical Sector Format when the Defect List Format is 101b.
5.24 READ LONG Command (3Eh) The READ LONG command is used in conjunction with the WRITE LONG command to allow the initiator to issue raw reads and writes of physical data blocks, but address them as logical blocks with an assumed sector length of 512 bytes. These two commands are used to verify the correction capability of the drive’s ECC and to create a known kind and location to verify the drive’s recovery and bad sector handling policies.
5.25 READ SKIP MASK Command (E8h) The READ SKIP MASK command allows the initiator to condition the function of the READ commands to allow only selected data to be transferred over the SCSI interface. A READ SKIP MASK command precedes a READ (10) command; the READ (10) command must be linked to the READ SKIP MASK command or the skip mask is lost and a CHECK CONDITION status is returned.
5.26 REASSIGN BLOCKS Command (07h) The REASSIGN BLOCKS Command reassigns one or more logical blocks to a spare location(s) set aside for this purpose and records the reassignments in the Grown Defect List. No command-specific Control Descriptor Block fields affect the processing performed for this command. The list of Logical Block Addresses to reassign is supplied in the REASSIGN BLOCKS Defect List passed in the command's data-out buffer transfer.
sense data. If all defects were reassigned, but some other error occurred, then FFFFFFFFh is posted in the command-specific field.
5.27 RECEIVE DIAGNOSTIC RESULTS Command (1Ch) The RECEIVE DIAGNOSTIC RESULTS command fetches the results of the last SEND DIAGNOSTIC command sent to the drive. The drives support the diagnostic pages listed in Table 5-149.
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 7 6 5 4 3 0 Page Code (00h) 1 Reserved 2 2-3 Page Length (0002h) 4 Supported Diagnostics Pages Page (00h) 5 Translate Address Page (40h) 1 0 To obtain the Supported Diagnostics Pages list, the initiator must: 1.
Table 5-153 Translate Address Page-Data Format Bit Byte 7 6 5 0 4 3 2 0 Operation Code (40h) 1 Reserved 2-3 Page Length (2 + (8 x n)) (where n = number of sectors / LBA) 4 5 1 Reserved RAREA ALTSEC ALTTRK Supplied Format = 000b (LBA) Reserved Translate Format = 101b (Physical Sector) 6-8 Translated Address (Cylinder Number)1 9 Translated Address (Head Number)1 10 - 13 Translated Address (Sector Number or Bytes From Index)1 yy+2 Translated Address (Cylinder Number) Where y = ((n-
5.28 RELEASE (6) Command (17h) The RELEASE and the RESERVE commands are used for contention resolution in multiple-initiator systems. The RELEASE command is used to release a previously reserved logical unit. The drive will not return an error if the initiator attempts to release a reservation that is not currently valid. The data format and field descriptions are shown in Table 5-155 and Table 5-156 respectively.
5.29 RELEASE (10) Command (57h) The RELEASE and the RESERVE commands are used for contention resolution in multiple-initiator systems. The RELEASE (10) command is used to release a previously reserved logical unit. The drive will not return an error if the initiator attempts to release a reservation that is not currently valid. The data format and field descriptions are shown in Table 5-157 and Table 5-158 respectively.
5.30 REPORT DEVICE IDENTIFIER Command (A3h) The REPORT DEVICE IDENTIFIER command requests that the device server send device identification to the application client. The data format and field descriptions are shown in Table 5-159 and Table 5-160 respectively.
Identifier 5-112 Maxtor Atlas 10K V The value reported in this field is a vendor-specific value and is the last value written by a successful SET DEVICE IDENTIFIER command. The value of the Identifier is changed only by a successful SET DEVICE IDENTIFIER command. The Identifier value persists through device resets, power cycles, and formatting of media.
5.31 REPORT LUNS Command (A0h) The REPORT LUNS command requests that the peripheral device logical unit numbers of known logical units in the target disk be sent to the applications client. The command only returns information about the logical units to which commands may be sent. The data format and field descriptions are shown in Table 5-163 and Table 5-164 respectively.
5.32 REQUEST SENSE Command (03h) The REQUEST SENSE command causes the drive to transfer detailed sense data to the initiator. The drive maintains sense data on an individual initiator basis. The data format and field descriptions are shown in Table 5-166 and Table 5-167 respectively.
5.32.2 Status Reporting The drive returns CHECK CONDITION status for a REQUEST SENSE command only to report errors specific to the command when: • A non-zero reserved bit is detected in the Command Descriptor Block. • A drive malfunction prevents return of the sense data. For Parallel SCSI disk drives, the drive also returns CHECK CONDITION status for a REQUEST SENSE command to report errors specific to the command when an unrecovered parity error is detected on the data bus.
Table 5-169 Sense Data Fields (Error Code 70h)-Field Descriptions Field Definition Valid The Valid bit, when set to 1, indicates that the Information field contains valid information, as defined below. When set to 0, it indicates that the contents of the Information field are not as defined below. Error Code Either 70h, indicating that current errors are to be reported, or 71h, indicating deferred errors are to be reported. Segment Number This feature is not supported and will return a zero value.
Sense Key Code NO SENSE 0h RECOVERED ERROR 1h NOT READY 2h MEDIUM ERROR 3h HARDWARE ERROR 4h ILLEGAL REQUEST 5h Table 5-170 Supported Sense Keys Description There is no specific sense key information to be reported for the designated logical unit. This is the case for a successful command or a command that received CHECK CONDITION or COMMAND TERMINATED status because one of the following bits is set to 1: File Mark, EOM, or ILI.
Table 5-171 Sense Key Information Field Contents Command Sense Key Field Contents FORMAT UNIT RECOVERED ERROR The address of the first bad sector encountered during the format operation. This sector, and all other bad sectors found during a format operation, are automatically reallocated by the drive. ILLEGAL REQUEST The first illegal defect descriptor encountered in the Defect Descriptor List.
Table 5-172 Supported Additional Sense Codes and Sense Code Qualifiers (in Hex) Sense Key 0x00 No Sense 0x01 Rec Error Sense Sense Code Qualifier 0x00 0x00 Meaning No additional sense information 0x0B 0x01 SMART overtemperature trip 0x5D 0x00 Smart triggered 0x5D 0x01 Smart triggered due to Read TA Factor 0x5D 0x02 Smart triggered due to Write Err Factor 0x5D 0x5B Smart triggered due to spin retry 0x5D 0xFF Smart test trigger 0x5E 0x00 Power State: ACTIVE 0x5E 0x01 Power State: I
Sense Key 0x01 Rec Error 5-120 Sense Sense Code Qualifier Meaning 0x17 0xA0 Possible Bump-1st - recovered 0x17 0xA1 Bump Err-2nd - recovered 0x17 0xA2 Defective Wdg-1st - recovered 0x17 0xA3 Defective Wdg-2nd - recovered 0x17 0xA4 Map'd Wdg-1st - recovered 0x17 0xA5 Map'd Wdg-2nd - recovered 0x17 0xA6 Id Err-1st - recovered 0x17 0xA7 Id Err-2nd - recovered 0x17 0xA8 Unknown Wdg Err-1st - recovered.
Sense Key 0x02 Not Ready 0x03 Medium Error Sense Sense Code Qualifier 0x04 0x00 Meaning Drive Not Ready 0x04 0x01 Drive Not Ready, in process of coming ready 0x04 0x02 Drive Not Ready, use START cmd 0x04 0x04 Drive Not Ready, formatting 0x04 0x09 Drive Not Ready, self test in progress 0x04 0x80 FileSystem Boot Area unreadable @ POR 0x04 0x82 File has not been written - can not read 0x04 0x83 Error reading diskware file 0x04 0x84 Diskware not loaded yet - issue start cmd 0x04 0x
Sense Key 0x03 Medium Error 0x04 Hdwe Error 5-122 Sense Sense Code Qualifier Meaning 0x15 0x81 Servo Write Not OK 0x15 0x82 Servo Read Not OK 0x15 0x83 Spoke address error 0x16 0x00 Data synchronization mark error 0x16 0x83 Spoke synchronization mark error 0x19 0x00 MCS is invalid 0x19 0x01 Unknown defect list 0x19 0x03 Bad grown defect list 0x19 0x80 Replacement block bad 0x19 0x81 Found two bad RBNs 0x27 0x00 Write protected 0x31 0x00 Format corrupted 0x31 0x01 F
Sense Key 0x04 Hdwe Error Sense Sense Code Qualifier 0x06 0x90 Meaning Invalid CP18 on disk 0x06 0x91 Invalid CP21 on disk 0x06 0x92 Invalid CP22 in NVR 0x06 0x93 Head polarity cal failed.
Sense Key 0x04 Hdwe Error 5-124 Sense Sense Code Qualifier Meaning 0x09 0x96 Svo: Offtrack Prediction Err-2nd.
Sense Key Sense Sense Code Qualifier Meaning 0x3E 0x03 Logical Unit failed self test 0x3E 0x04 Logical unit log update failure Maxtor Atlas 10K V 5-125
Sense Key 0x04 Hdwe Error 5-126 Sense Sense Code Qualifier 0x40 0x80 Meaning Unknown HW problem 0x40 0x82 Hardware Bug Check (check Info field) 0x40 0x83 Failed HDA test. 0x40 0x84 Failed PCB test. 0x40 0x85 EDC check failed. 0x40 0x86 Controller FIFO over/underflow error. 0x40 0x88 DIAG: Drive failed to read servowriter serial number. 0x40 0x89 DIAG: Failed XOR test.
Sense Key 0x04 Hdwe Error Sense Sense Code Qualifier Meaning 0xA0 0x00 New wrt cmd overlaps deferred write error 0xA0 0x01 New wrt cmd overlaps deferred read error 0xA0 0x02 New rd cmd overlaps deferred write error 0xA0 0x03 New rd cmd overlaps deferred read error 0xA0 0x81 Failed to load the FSBA 0xA0 0x82 a power-up servo calibration failed 0xA0 0x83 head check failed 0xA0 0x84 Loading of disk config pages from filesystem failed 0xA0 0x85 Diskware loaded, but failed validation
Sense Key 0x04 Hdwe Error 5-128 Sense Sense Code Qualifier 0xA0 0x95 Meaning Selfscan could not load results (0x31) 0xA0 0x96 Selfscan could not load Defect (0x32) 0xA0 0x97 Selfscan could not load Defect Manager files 0xA0 0x98 Selfscan could not load SuperZoneData file 0xA0 0x99 Selfscan timeout waiting for drive to come ready 0xA0 0x9A Load Selfscan overlays failed 0xA0 0x9B Selfscan overlays do not match firmware 0xA0 0x9C Failed to lock within TBD seconds0x04/0xA0/0xA0 Spin tim
Sense Key 0x04 Hdwe Error Sense Sense Code Qualifier Meaning 0xA0 0xAC Spin time-out - SETTLE 0xA0 0xAD Spin time-out - STEADY 0xA0 0xAE Spin time-out - FAULT 0xA0 0xAF Spin time-out - ETM 0xA0 0xB0 Spin time-out - ROCKSPINDLE 0xA0 0xB1 Spin time-out - ANTILOCK 0xA0 0xB2 Spin time-out - SYNC4BRAKE 0xA0 0xB3 Diablo shutdown due to high temp 0xA0 0xB4 VCM wasn’t updated in time 0xA0 0xB5 Spindle clk is missing 0xA0 0xB6 Sync-to-Index, servo went dead 0xA0 0xB7 Sync-to-Ind
Sense Key 0x05 Illegal Request 5-130 Sense Sense Code Qualifier 0x1A Meaning 0x00 Parameter list length error 0x20 0x00 Invalid command.
Sense Key 0x06 Unit Attn 0x06 Unit Attn Sense Sense Code Qualifier Meaning 0x0B 0x01 SMART overtemperature trip 0x28 0x00 Not Ready to Ready transition 0x29 0x01 Power-On-Reset occurred 0x29 0x02 SCSI bus reset occurred 0x29 0x03 Bus device reset message 0x29 0x04 Recovered from bug check 0x29 0x05 Bus mode changed to single ended 0x29 0x06 Bus mode changed to LVDS 0x29 0x86 Reset after too many ACK's 0x2A 0x01 Mode parameters were changed 0x2A 0x02 Log parameters were ch
Sense Key Sense Sense Code Qualifier 0x0B Aborted Cmd 0x00 0x0E 0x00 Meaning Aborted.
16 - 17 Field Pointer Table 5-175 ILLEGAL REQUEST Sense Key Field Pointer Bytes\Field Descriptions Field Description SKSV Sense-Key Specific Valid C/D 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 Valid.
-Field Descriptions Field 5-134 Description SKSV Sense-Key Specific Valid Retry Count The number of times an I/O operation was retried Maxtor Atlas 10K V
5.33 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.
5.34 RESERVE (10) Command (56h) 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. If RESERVE (10) is used, then RELEASE (10) is also used. The data format and the field descriptions are described in Table 5-182 and Table 5-183 respectively. The data format for the Event Descriptors is described in Table 5-184.
Table 5-184 Extent Descriptors-Data Format Bit Byte 7 6 0 5 4 3 2 Reserved 1-3 4-7 (MSB) RelAdr 1 Reservation Type Number of Blocks (MSB) 0 (LSB) Logical Block Address (LSB) The Reservation Type field defines the type of reservation in effect for the extent being reserved. Available types of reservations are shown in Table 5-185. Table 5-185 Reservation Types Reservation Type Description 00b READ shared. No write operations are permitted by any initiator to the reserved extent.
5.35 REZERO UNIT Command (01h) The REZERO UNIT command sends the heads to cylinder 0 (Logical Block Address 0). Once the heads are on the track, they are not guaranteed to stay at cylinder 0; periodic calibrations may send them to a different cylinder. If periodic calibrations have been disabled by using the MAN bit (byte 3, bit 6) of the Vendor Unique Function Control Page in the MODE SELECT command (15h), the REZERO UNIT command will cause the drive to perform the next scheduled calibration.
5.36 SEEK (6) Command (0Bh) The SEEK (6) command uses a 6-byte Command Descriptor Block to request the drive to send the drive heads to the requested Logical Block Address. The drive responds by placing the heads at the correct Logical Block Address. When the heads are at the specified Logical Block Address, they are not guaranteed to stay in that position since periodic calibrations may send them to a different cylinder. The data format is shown in Table 5-189.
5.37 SEEK (10) Command (2Bh) The SEEK (10) command uses a 10-byte Command Descriptor Block to request the drive to send the drive heads to the requested Logical Block Address. The drive responds by placing the heads at the correct Logical Block Address. When the heads are at the specified Logical Block Address, they are not guaranteed to stay in that position since periodic calibrations may send them to a different cylinder. The data format is shown in Table 5-190.
5.38 SEND DIAGNOSTIC Command (1Dh) The SEND DIAGNOSTIC command sends a diagnostic page to the drive. Refer to the RECEIVE DIAGNOSTICS RESULTS command for a description of the diagnostic pages and the use of the diagnostic commands. The Supported Diagnostic Page List (Table 5-193) and Translate Page List (Table 5-194) can be sent with this command. Table 5-191 shows the SEND DIAGNOSTIC CDB data format and Table 5-192 shows the field descriptions.
Field Description SelfTest If the PF bit is 0 and the SelfTest bit is 1, the drive runs its self-test routine. GOOD status is returned to the initiator if the self-test passes. CHECK CONDITION status is returned along with any available sense data if the self-test fails. This field is ignored if the PF bit is 1. DevOnl Any value in this field is ignored by the drive. UnitOfl Any value in this field is ignored by the drive.
5.39 SET DEVICE IDENTIFIER Command (A4h) The SET DEVICE IDENTIFIER command requests that the device identifier information in the logical unit be set to the value send via the SET DEVICE IDENTIFIER command’s parameter list. The data format and field descriptions are shown in Table 5-195 and Table 5-196 respectively. Upon successful completion of a SET DEVICE IDENTIFIER command, a Unit Attention is generated for all initiators except the one that issued the command.
5.40 START STOP UNIT Command (1Bh) The START STOP UNIT command enables or disables the logical unit for media access operations. This command gives the initiator remote control over drive spinup and spin-down. The data format and field descriptions are shown in Table 5-199 and Table 5-200 respectively. A jumper (or backplane connection) is used to select the spin-up mode. When configured for remote control of spin-up (Option 3), the drive requires a START STOP UNIT Command to spin up.
5.41 SYNCHRONIZE CACHE Command (35h) The SYNCHRONIZE CACHE command ensures that all logical blocks, within the specified range in the drive's cache memory, have their most recent data value recorded on the physical medium. If more recent data for a logical block, within the specified range, exists in the cache memory than on the physical medium, then the logical blocks from the cache memory is written to the physical medium.
5.42 TEST UNIT READY Command (00h) The TEST UNIT READY command returns GOOD status if the drive is ready to receive medium access commands (that is, READ, WRITE, VERIFY, etc.). If the drive is not ready to receive medium access commands, it returns CHECK CONDITION status with the appropriate sense keys and qualifiers. The data format is described in Table 5-203.
5.43 VERIFY Command (2Fh) The VERIFY command verifies the data on the medium for the Logical Block Address range specified. The data format and field descriptions are shown in Table 5204 and Table 5-205 respectively.
5.44 WRITE (6) Command (0Ah) The WRITE (6) command requests that the drive write initiator-supplied data to the medium. The Command Descriptor Block for the WRITE (6) command is shown in Table 5206; Table 5-207 describes the data fields.
5.45 WRITE (10) Command (2Ah) The WRITE (10) command requests that the drive write initiator-supplied data to the medium. The data format and field descriptions are shown in Table 5-208 and Table 5-209 respectively.
5.46 WRITE AND VERIFY Command (2Eh) The WRITE AND VERIFY command writes host-supplied data to the unit and verifies it was written correctly. The data format and field descriptions are shown in Table 5-210 and Table 5-211 respectively.
5.47 WRITE BUFFER Command (3Bh) The WRITE BUFFER and the READ BUFFER commands allow the initiator to gain access to the data storage areas within the drive controller. These commands are used to check the integrity of the buffer-initiator data path independent of the storage medium, typically for fault isolation. The commands can be used to verify the caching policies of the controller or other kinds of debug work. In addition, the WRITE BUFFER command supports controller microcode downloads.
Table 5-213 WRITE BUFFER Command-Field Descriptions Field Description Mode Five modes are supported by the drive; Combined Header and Data, Data Only, Download Microcode and Save, and Write Data from Echo Buffer. The permissible values for Buffer ID, Buffer Offset are as follows: Combined Header and Data – In this mode, the data to be transferred is preceded by a 4-byte header that contains reserved bytes that must be set to 0.
5.48 WRITE LONG Command (3Fh) The WRITE LONG and READ LONG commands allow the initiator to issue raw reads and writes of physical sectors addressed as logical blocks with an assumed sector length of 512 bytes. These commands are used to verify the correction capability of the drive's ECC and to create defects of a known kind and location to verify the drive's recovery and bad sector handling policies. The data format and field descriptions are shown in Table 5-214 and Table 5-215 respectively.
Table 5-216 WRITE SAME Command Descriptor Block-Data Format Bit Byte 7 6 5 4 0 3 2 1 0 Operation Code (41h) 1 Reserved 2-5 PBdata LBdta RelAdr Logical Block Address 6 Reserved 7-8 Number of Blocks 9 Control Table 5-217 WRITE SAME Field Description 5.50 Field Description PBdata Physical Block Data - Not supported. This feild must be zero.
Table 5-219 WRITE SKIP MASK Command - Field Description Field Description Logical Block Address This field specifies the first logical block of the corresponding WRITE (10) COMMAND. This allows a SEEK to begin immediately. The LBA of the following WRITE (10) command must be the same as the LBA of the Write SKIP MASK command, Skip Mask Length This field indicated the length in bytes of the skip mask. The mask is up to 64 bytes, giving a data address capability of 256K.
5-156 Maxtor Atlas 10K V
Chapter 6 FEATURE DESCRIPTIONS This chapter provides descriptions of many of the features incorporated in the Maxtor Atlas 10K V hard disk drive family. 6.1 KEY FEATURES Maxtor Atlas 10K V disk drives provide unequaled quality and performance. They are designed to improve the performance of high-end workstations, file servers, and storage systems. Among their features are the following: • 73.5, 147.
• MaxAdpat Feature Set - Rotational Vibration Compensation (RVC) - Adaptive Bias Estimation (ABE) - Virtual Cache Line (VCL) - Adaptive Active Filtration (AAF) • Advanced Ultra160 SCSI-LVD, Ultra320 SCSI-LVD, Ultra2-LVD, and Ultra-SE with 68-pin wide connector or 80-pin SCA-2 connector • Superior data integrity: •352-bit Reed-Solomon quad-burst ECC provides fast on-the-fly correction for small errors and robust software-based correction for larger errors •EDC internal protection from SCSI bus to media Note:
6.3 ZERO LATENCY READ/WRITE An average of half a revolution of latency is saved by starting to read or write as soon as a seek settles on the designated track. If reading, the initial data read is stored in a buffer (cache) until the actual starting address data block is reached and read. The starting address data is then transferred to the bus as the rest of the data is transferring from media to the buffer.
digital address data. The digital portions of the spoke data are read and used to locate the desired track, spoke, and head number. The quadrature analog signal portion is detected and used by a servo feedback control loop to precisely position the head on the track center. 6.
information about the reallocation (such as the new destination and the data in transit) is recorded. If the reallocation is interrupted, the process can automatically continue from the last checkpoint without data loss. If a block reallocation is performed on unrecoverable data (rare), a Bad Data Mark is set in the new location. Thus, there is no chance of undetected bad data being generated from a reallocation. 6.8.5 Data Verification Data can be verified in two ways.
6.12 DIAGNOSTICS The drive has extensive diagnostic capabilities, including those described below: power-on self-test, periodic self-adjustments, and host diagnostics. Maxtor uses selfdiagnostic tests and sense data tracking to manage drive errors, in addition to logical block address (LBA) revectoring. 6.12.1 Power On Self Test (POST) The disk drive performs a self-diagnostic test immediately at power up. Both the Fault LED and a Busy LED briefly illuminate during spin-up as a lamp test.
6.12.3 Host Diagnostics The Host Processor can command the drive to perform diagnostic tests and report status using RECEIVE and SEND DIAGNOSTIC RESULTS commands. Certain parameters can be sent to the drive to alter or enhance the performance of the diagnostic tests specified. 6.12.4 Log Sense Maxtor implements multiple LOG SENSE pages which logically group together parameters related to disk and subsystem activities.
allocated at the end of each band, and are reserved for grown, revectored blocks. All grown defects are reallocated to one of the spare blocks, using a “nearest neighbor” algorithm. If bad block replacement is enabled (via the AWRE and ARRE bits in the ReadWrite Error Recovery Page), blocks that are difficult to read or write may be replaced after multiple retries. If the bad block data is recoverable, the drive first verifies that the original block location is bad with multiple write tests.
6.14.1 DIFFSENS The DIFFSENS signal in the SCSI bus defines the current operating mode of the SCSI bus. A level below +.5 volts defines a single-ended bus. A level between +.7 and +1.9 volts defines an LVD bus. A level above +2.4 volts defines a High Voltage Differential (HVD) bus. Before LVD was introduced, HVD was simply called Differential SCSI. All single-ended-only devices connect the DIFFSENS signal to ground. On an LVD bus, the terminators drive the DIFFSENS signal to +1.
6.14.3 DT AND ST CLOCKING With Ultra160 and Ulra320 SCSI interfaces, Maxtor has introduced a new method of clocking data on the SCSI bus. This method, called Double Transition (DT) clocking, uses both the rising and falling edges of the REQ and ACK signals to clock data into the receiving device. This has the advantage of allowing the REQ and ACK signals to run at half the frequency that would be required under the traditional Single Transition (ST) SCSI clocking scheme for the same data rate.
6.14.4 CYCLIC REDUNDANCY CHECKING When transferring data with DT clocking on the SCSI bus, a significantly improved form of error checking, cyclic redundancy checking (CRC) is used instead of the traditional parity checking. With CRC checking, the device sending data generates a four-byte CRC character based on the contents of the bytes being transferred. The receiving device also generates a CRC character as it receives the bytes.
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 signal’s 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.
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.
6.15.2 APPLICABLE SCSI PHYSICAL DOCUMENTS If additional information is required, refer to the following documentation: • SCSI-3 SPI (SCSI Parallel Interface), revision 15, now ANSI Standard No. X3.253.1993 - Device Insertion/Removal classes • SCSI-3 Fast-20, revision 6, now ANSI Standard No. X3.277.
Appendix A QUICK REFERENCE Appendix A is a synopsis of SCSI commands, associated pages, messages, sense keys and status codes used in this manual. Note: Reserved fields in CDBs and Parameters have a value of 0; Reserved fields in states and other parameters sent to an initiator are set to 0. A.1 SCSI-2/SCSI-3 Equivalent Terminology Table A-1 contains the SCSI-3 equivalent terms for common terms used in SCSI-2 documents.
A.2 SCSI Commands and Messages Table A-2 and Table A-3 contains the SCSI-3 commands and messages and their corresponding op codes.
Table A-3 SCSI-3 Quick Reference – Messages Messages Msg.
Format Device Format Status Implemented Operating Definition Last n Error Events Medium Types Supported Non-Medium Error Counter Notch and Partition Peripheral Device Port Control Page Margin Control Subpage Saved Training Configuration Values Subpage Negotiated Setting Subpage Report Transfer Capabilities Subpage Read Error Counter Read-Write Error Recovery Rigid Disk Geometry Standard Inquiry Data Supported Diagnostic Pages Supported Log Pages Supported Vital Product Pages Translate Address Unit Attention
A.4 Sense Keys Table A-5 lists the sense keys. Table A-5 SCSI-3 Quick Reference – Sense Keys Sense Keys NO SENSE RECOVERED ERROR NOT READY MEDIUM ERROR HARDWARE ERROR ILLEGAL REQUEST UNIT ATTENTION DATA PROTECT VENDOR SPECIFIC ABORTED COMMAND MISCOMPARE A.5 Sense Code - Hex 0 1 2 3 4 5 6 7 9 B E Status Codes Table A-6 lists the status codes.
Appendix B NEGOTIATED RATE INFORMATION PAGE REFERENCE This appendix provides information about the INQUIRY command’s Negotiated Rate Information Page that is not provided in Section 5.11.2.7. Specifically, it provides the codes and meanings for the Transfer Period Factor field (byte 4) and a table that explains the allowable settings for the QAS, DT, and IU fields (bits 2, 1, and 0, respectively, of byte 7). B.
OCh Transfer period = 50 ns (Fast-20 data is latched using a transfer period of less than or equal to 96 ns and greater than or equal to 50 ns). 0Dh – 18h Transfer period = the period factor x 4 (Fast-20 data is latched using a transfer period of less than or equal to 96 ns and greater than or equal to 50 ns). 19h – 31h Transfer period = the period factor x 4 (Fast-10 data is latched using a transfer period of less than or equal to 196 ns and greater than or equal to 100 ns).
B.2 Settings for the QAS, DT, and IU fields Table C-3 provides valid bit combinations for the QAS, DT, and IU fields of the INQUIRY command’s Negotiated Rate Information Page (Section 5.11.2.7 of this manual). Only the combinations shown in the table are valid; all other combinations are reserved. Table B-3 Settings for the QAS, DT, and IU Fields of the Negotiated Rate Information Page (INQUIRY Command) QAS DT IU Description 0 0 0 Selects Single Transition phases.
GLOSSARY A ACCESS – (v) Read, write, or update information stored on a disk or other medium. (n) The operation of reading, writing, or updating stored information. ACCESS TIME – The interval between the time a request is made by the system and the time the data is available from the drive. Includes the seek time, rotational latency, and command processing overhead time. (See also seek, rotational latency, and overhead.) ACTIVE I/O PROCESS– An I/O process that is currently in execution (not queued).
Glossary BLOCK – In UNIX workstation environments, the smallest contiguous area that can be allocated for the storage of data. UNIX blocks are generally 8 Kbytes (16 sectors) in size. In DOS environments, the block is referred to as a cluster. (Note: This usage of the term block at the operating system level is different from its meaning in relation to the physical configuration of the hard drive. See sector for comparison.) BPI – Bits Per Inch.
GLOSSARY DATA SEPARATOR – The circuit that extracts data from timing information on drives that store a combined data and clock signal. DEDICATED SERVO – A positioning mechanism using a dedicated surface of the disk that contains timing and positioning information only, as compared to surfaces that are also used for data. (See also embedded servo.) DEFECT MANAGEMENT – A technique ensuring long-term data integrity.
Glossary F 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.
GLOSSARY HARD-SECTORED – The most common method of indicating the start of each sector on a disk, based on information located in the embedded servo. This method is more precise than soft-sectored techniques and results in lower overhead. (See also soft-sectored.) HEAD – The tiny electromagnetic coil and metal pole used to create and read back magnetic patterns on the disk. Also known as read/write head. HEAD CRASH – Damage to the read/write head, usually caused by sudden contact with the disk surface.
Glossary J JUMPER – A tiny box that slips over two pins on a circuit board, connecting the pins electrically. Some board manufacturers use Dual In-Line Package (DIP) switches instead of jumpers. K KILOBYTE (K) – A unit of measure consisting of 1,024 (210) bytes. L LANDING ZONE – A non-data area on the disk’s inner cylinder where the heads can rest when the power is off.
GLOSSARY MICROSECOND (µs) – One millionth of a second (.000001 sec.). MILLISECOND (ms) – One thousandth of a second (.001 sec.). MTBF – Mean Time Between Failure. Reliability rating indicating the failure rate expected of a product expressed in power on hours (POH). Since manufacturers differ in the ways they determine the MTBF, comparisons of products should always take into account the MTBF calculation method. MTTR – Mean Time To Repair.
Glossary PERIPHERAL – A device added to a system as an enhancement to the basic CPU, such as a disk drive, tape drive or printer. PHYSICAL FORMAT – The actual physical layout of cylinders, tracks, and sectors on a disk drive. PHYSICAL SECTOR –See sector, data. PLATTER – Common term referring to the hard disk. POH – Power On Hours.
GLOSSARY 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.
Glossary SCSI BUS – A multi-signal parallel bus that interconnects SCSI devices in a daisy-chain fashion. SCSI DEVICE – A host adapter or a target controller that can be attached to the SCSI bus. SCSI ID – The bit-significant representation of the SCSI address referring to one of eight (or one of sixteen) data lines. SECTOR – On a PC hard drive, the minimum segment of track length that can be assigned to store information.
GLOSSARY S.M.A.R.T. – Self-Monitoring and Analysis Reporting Technology. The continual monitoring of the drive's operating condition with reports sent to the host computer. Similar to Maxtor's EWS (Early Warning System) used in some drives. before and after each block. This method is faster than asynchronous data transfer. SOFT ERROR – A faulty data reading that does not recur if the same data is reread from the disk, or corrected by ECC. Usually caused by power fluctuations or noise spikes.
Glossary “asserted”) state of a binary number. See also, signal assertion. WINCHESTER DISKS – Former code name for an early IBM hard disk model, sometimes still used to refer to hard drives in general. U UNFORMATTED CAPACITY – The total number of bytes of data that can be put on a disk drive. Formatting the disk requires approximately 20% of this space to record servo data, addresses, boundary definitions, and timing information.
INDEX Numerics 4-pin DC power connector 3-21 512-byte sectors available 4-3 A abbreviations 1-2 acoustics 4-7 Active Notch 5-51 actuator 4-6 Adapter, 50-pin to 68-pin 2-4 Additional Sense Codes 5-109, 5-113 Additional Sense Length 5-110 Allocation Length 5-11, 5-34, 5-101, 5- 107, 5-108, 5-109 altitude2 4-8 ASCII Implemented Operating Definition 5-26 ASCII Implemented Operating Definition Page 5-26 audience definition 1-1 auto head-park method 4-2 average write 4-2 AWRE 5-15, 5-43, 5-47 Caching Page 5-4
error correction method 4-2 Error Reporting 5-7 error type 4-11 ESD 3-4 Extent List Length 5-124 F faceplate 3-3 Field Pointer Bytes 5-122 Firmware Revision 5-27 Firmware Revision Page 5-27 Flag Bit 5-6, 5-13 Format Device 5-65, 5-66 Format Device Page 5-65 FORMAT UNIT Command 5-15, 5-16, 5-17, 5-21 formatted capacity 4-1, 4-3 full stroke 4-4 G general 2-1 GList 5-95, 5-96, 5-97, 5-98 Grown Defect List 5-15, 5-17, 5-18, 5- 43, 5-95, 5-96, 5-97, 5-98, 5-100 H hard reset time 4-4 HARDWARE ERROR 5-112 hard
INDEX Medium Type 5-63, 5-65, 5-70 Mode Data Length 5-65 Mode Page Types 5-39 Mode Parameter Block Descriptor 5-40, 5-41 Mode Parameter Header 5-11, 5-39, 5- 40, 5-62, 5-64, 5-69, 5-70 Mode Parameter List 5-39 mode select 1-3 MODE SELECT (10) 5-1, 5-62 MODE SELECT (6) Command 5-37, 5- 60 MODE SENSE (10) 5-1, 5-69 Module Serial Number 5-24 mounting 3-23, 3-24 multiple drive shipments 3-5 Parameter Pointer 5-34 Parameter Pointer Control 5-34 PCBA 3-24 performance 2-2 Peripheral Device 5-23 Peripheral Qual
Reed-Solomon ECC 2-3 references 1-3 Relative Addressing 5-23, 5-90, 5-93 RELEASE Command 5-104, 5-105 reliability 2-3, 4-10 Remote Busy and Fault Displays (16-bit Drives, except SCA) 3-9 REQUEST SENSE Command 5-106, 5- 107, 5-108, 5-132 Reservation Identification 5-104, 5-105, spindle startup 4-6 Standard Inquiry Data 5-22, 5-23 Standard Inquiry Data Page 5-22 start/stop 4-10 Starting Boundary 5-51 Status Reporting 5-109 Status/Error Reporting 5-7 Supplied Format 5-103 supply voltage 4-5 Supported Additio
INDEX U Unit Attention Condition Page 5-59, 5- 60 Unit Serial Number 5-24 Unit Serial Number Page 5-24 UNIX 4-3 unrecoverable error rate 4-2 V ventilation 3-23, 3-25 ventilation requirements 3-23 Verification Length 5-136 VERIFY Command 5-136, 5-139 Verify Correction Span 5-46 Verify Error Recovery 5-45, 5-46 Verify Error Recovery Page 5-45 Verify Recovery Time Limit 5-46 Verify Retry Count 5-46 versatility 2-3 vibration 4-10 Vital Product Data 5-11, 5-21, 5-24, 5-28 Vital Product Data Pages 5-24 volt ret
