Maxtor 10K V User Manual

Maxtor Atlas 10K V  
Product Manual  
September 6, 2005  
Revision 3  
PN: 000001911  
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. This manual provides technical information for OEM engi-  
neers and systems integrators regarding the installation and use of Maxtor hard drives. Drive repair should be per-  
formed only at an authorized repair center. For repair information, contact the Maxtor Customer Service Center at  
800-2MAXTOR or 303-678-2045.  
CAUTION: Maxtor hard drives are precision products. Failure to follow these precautions and guidelines outlined  
here may lead to product failure, damage and invalidation of all warranties.  
1
BEFORE unpacking or handling a drive, take all proper electro-static discharge (ESD) precautions,  
including personnel and equipment grounding. Stand-alone drives are sensitive to ESD damage.  
2
3
4
BEFORE removing drives from their packing material, allow them to reach room temperature.  
During handling, NEVER drop, jar, or bump a drive.  
Once a drive is removed from the Maxtor shipping container, IMMEDIATELY secure the drive through  
its mounting holes within a chassis. Otherwise, store the drive on a padded, grounded, antistatic surface.  
5
NEVER switch DC power onto the drive by plugging an electrically live DC source cable into the  
drive's connector. NEVER connect a live bus to the drive's interface connector. (P68 only)  
Please do not remove or cover up Maxtor factory-installed drive labels. They contain information required should the  
drive ever need repair.  
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 users  
authority to operate this equipment under Part 15 of the FCC Rules. Operation is subject to the following two condi-  
tions: (1) This device may not cause harmful interference and (2) This device must accept any interference that may  
cause undesirable operation.  
This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance  
with the instructions, may cause harmful interference to radio communications. Howerver, there is no guarantee that  
interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or  
television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to  
correct the interference by one or more of the following measures:  
- Reorient or relocate the receiving antenna.  
- Increase the separation between the equipment and receiver.  
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.  
- Consult the dealer or an experienced radio/TV technician for help.  
NOTE: Additional information on the need to interconnect the device with shielded (data) cables or the need for special devices, such  
as ferrite beads on cables, is required if such means of interference suppression was used in the qualification test for the device. This  
information will vary from device to device and needs to be obtained from the EMC group or product manager.  
This Class B digital apparatus complies with Canadian ICES-003.  
Table of Contents  
Chapter 1  
ABOUT THIS MANUAL  
1.1 AUDIENCE....................................................................................................................... 1-1  
1.2 MANUAL ORGANIZATION.......................................................................................... 1-1  
1.3 TERMINOLOGY AND CONVENTIONS ..................................................................... 1-2  
1.4 REFERENCES .................................................................................................................. 1-3  
Chapter 2  
GENERAL DESCRIPTION  
2.1 PRODUCT OVERVIEW ................................................................................................. 2-1  
2.2 KEY FEATURES............................................................................................................... 2-1  
2.3 REGULATORY COMPLIANCE STANDARDS............................................................ 2-3  
2.4 HARDWARE REQUIREMENTS................................................................................... 2-4  
Chapter 3  
INSTALLATION  
3.1 SAFETY, HANDLING, & ELECTROSTATIC DISCHARGE PROTECTION............. 3-1  
3.1.1 Safety Precautions .......................................................................................................3-1  
3.1.2 Handling ....................................................................................................................3-1  
3.1.3 Electrostatic Discharge (ESD) Protection ....................................................................3-2  
3.2 SPACE REQUIREMENTS............................................................................................ ...3-4  
3.2.1 Shock Feet .................................................................................................................3-5  
3.3 UNPACKING INSTRUCTIONS ................................................................................. ...3-6  
3.4 HARDWARE OPTIONS ............................................................................................. .... 3-8  
3.4.1 Configuration Jumpers and Connections .....................................................................3-8  
3.4.2 Jumper Options on the 68-Pin Wide PCB ................................................................3-8  
3.4.2.1 Write Protection ....................................................................................................3-10  
3.4.2.2 Delay Spin (DS) Stagger SPin (SS) ..............................................................................3-11  
3.4.2.3 Single-Ended Operation _ Force SE )Disable LVD)................................................... .3-11  
3.4.2.4 Remote Busy and Fault Displays..................................................................................3-11  
3.4.3 SCA-2 80-Pin Connector Versions ...........................................................................3-12  
3.4.3.1 Termination for the 80-Pin SCA-2 Connector Versions..............................................3-12  
3.4.3.2 SCSI ID for SCA-2 Versions........................................................................................3-13  
3.4.3.3 Spin Up for the 80 Pin SCA-2 Connector Versions.....................................................3-14  
3.4.3.4 Activity LED for SCA Connector Versions.................................................................3-15  
3.5 INTERFACE CONNECTOR (J1)....................................................................................3-15  
3.5.1 68-Pin Wide SCSI Connector - LVD .......................................................................3-18  
3.5.1.1 68-Pin Wide Connector............................................................................................. .3-18  
3.5.2 80-Pin SCA-2 SCSI Connector - LVD ....................................................................3-19  
Maxtor Atlas 10K V  
i
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 ...............................................................................................................3-26  
3.6.2 Mounting Screw Clearance .......................................................................................3-27  
3.6.3 Mounting .................................................................................................................3-28  
3.6.4 Ventilation ................................................................................................................3-28  
Chapter 4  
SPECIFICATIONS  
4.1 SPECIFICATION SUMMAR ...................................................................................... 4-1,4-2  
4.2 FORMATTED CAPACITY.............................................................................................. 4-3  
4.3 DATA TRANSFER RATES ............................................................................................. 4-4  
4.4 TIMING SPECIFICATIONS ............................................................................................ 4-4  
4.5 POWER............................................................................................................................. 4-5  
4.5.1 Power Sequencing ......................................................................................................4-5  
4.5.2 Power Reset Limits ....................................................................................................4-5  
4.5.3 Drive Power Dissipation .............................................................................................4-6  
4.6 ACOUSTICS............................................................................................................ 4-7  
4.7 MECHANICAL................................................................................................................. 4-8  
4.8 ENVIRONMENTAL CONDITIONS.............................................................................. 4-8  
4.9 ELECTROMAGNETIC CONDITIONS ......................................................................... 4-9  
4.9.1 EMI/RFI Susceptibility ..............................................................................................4-9  
4.9.2 ESD ...........................................................................................................................4-9  
4.9.3 Sensitivity to Magnetic Fields ......................................................................................4-9  
4.10 SHOCK AND VIBRATION............................................................................................. 4-9  
4.11 RELIABILITY .................................................................................................................. 4-10  
4.12 DISK ERRORS................................................................................................................ 4-10  
Chapter 5  
SCSI Description  
5.1 Overview of the SCSI Command Descriptions.................................................................... 5-1  
5.2 Command Descriptor Block................................................................................................ 5-4  
5.3 Status/Error Reporting........................................................................................................ 5-7  
5.4 Auto Contingent Allegiance Condition and Contingent Allegiance Condition .................... 5-8  
5.5 Extended Contingent Allegiance Condition ........................................................................ 5-9  
5.6 Linked Commands............................................................................................................. 5-10  
5.7 DATA Transfer Command Components............................................................................ 5-11  
5.8 SCSI COMMAND DESCRIPTIONS .............................................................................. 5-13  
5.9 NEW OPERATING DEFINITION (40h) ....................................................................... 5-14  
5.10 FORMAT UNIT Command (04h).................................................................................... 5-15  
5.10.1 Five Forms of FORMAT UNIT Commands .......................................................... 5-17  
5.10.2 FORMAT UNIT Parameter List ............................................................................5-17  
5.11 INQUIRY Command (12h).............................................................................................. 5-21  
5.11.1 Standard Inquiry Data Page ......................................................................................5-22  
Maxtor Atlas 10K V ii  
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-35  
5.14 MODE SELECT (6) Command (15h)................................................................................ 5-37  
5.14.1 Initiator-Changeable Mode Pages ............................................................................5-37  
5.14.2 Mode Page Types ....................................................................................................5-39  
5.14.3 Mode Parameter List ...............................................................................................5-39  
5.14.4 Categories of Changeable Pages ...............................................................................5-41  
5.14.5 Unit Attention Condition Page (00h) ......................................................................5-41  
5.14.6 Read-Write Error Recovery Page (01h) ..................................................................5-42  
5.14.7 Disconnect–Reconnect Page (02h) ..........................................................................5-44  
5.14.8 Verify Error Recovery Page (07h) ...........................................................................5-45  
5.14.9 Caching Page (08h) .................................................................................................5-46  
5.14.10 Control Mode Page (0Ah) .....................................................................................5-48  
5.14.11 Notch and Partition Page (0Ch) .............................................................................5-50  
5.14.12 Port Control Mode Page (19h) ..............................................................................5-52  
5.14.14 Information Exceptions Control Page (1Ch) ..........................................................5-59  
5.15 MODE SELECT (10) Command (55h).............................................................................. 5-62  
5.16 MODE SENSE (6) Command (1Ah) ................................................................................. 5-64  
5.16.1 Read-Only Mode Pages ..........................................................................................5-65  
5.16.2 Format Device Page (03h) .......................................................................................5-65  
5.16.3 Rigid Disk Geometry Page (04h) .............................................................................5-67  
5.17 MODE SENSE (10) Command (5Ah) ............................................................................... 5-69  
5.18 PERSISTENT RESERVATION IN Command (5Eh)...................................................... 5-71  
5.19 PERSISTENT RESERVATION OUT Command (5Fh) ................................................. 5-79  
5.20 READ (6) Command (08h)................................................................................................ 5-89  
5.21 READ (10) Command (28h).............................................................................................. 5-90  
5.22 READ BUFFER Command (3Ch).................................................................................... 5-91  
5.23 READ CAPACITY Command (25h) ................................................................................ 5-93  
5.24 READ DEFECT DATA Command (10) (37h).................................................................. 5-94  
5.25 READ DEFECT DATA Command (12) (B7h) ................................................................. 5-97  
5.26 READ LONG Command (3Eh)........................................................................................ 5-99  
5.27 REASSIGN BLOCKS Command (07h)........................................................................... 5-100  
5.28 RECEIVE DIAGNOSTIC RESULTS Command (1Ch)................................................. 5-101  
5.28.1 Supported Diagnostics Pages Page (00h) ................................................................5-102  
5.28.2 Translate Address Page (40h) .................................................................................5-102  
5.29 RELEASE (6) Command (17h)........................................................................................ 5-104  
5.30 RELEASE (10) Command (57h)...................................................................................... 5-105  
5.31 REPORT DEVICE IDENTIFIER Command (A3h)...................................................... 5-106  
5.32 REPORT LUNS Command (A0h) ................................................................................. 5-107  
5.33 REQUEST SENSE Command (03h)............................................................................... 5-108  
5.33.1 Sense Data Availability ...........................................................................................5-108  
5.33.2 Status Reporting ....................................................................................................5-109  
5.33.3 Sense Data Format for Error Code 70h and Error Code 71h ..................................5-109  
Maxtor Atlas 10K V iii  
5.34 RESERVE (6) Command (16h)....................................................................................... 5-124  
5.35 RESERVE (10) Command (56h)..................................................................................... 5-125  
5.36 REZERO UNIT Command (01h).................................................................................. 5-127  
5.37 SEEK (6) Command (0Bh)............................................................................................... 5-128  
5.38 SEEK (10) Command (2Bh)............................................................................................. 5-129  
5.39 SEND DIAGNOSTIC Command (1Dh)......................................................................... 5-130  
5.39.1 Supported Diagnostic Page List ..............................................................................5-131  
5.39.2 Translate Address Page ...........................................................................................5-131  
5.40 SET DEVICE IDENTIFIER Command (A4h)................................................................ 5-132  
5.41 START STOP UNIT Command (1Bh) .......................................................................... 5-133  
5.42 SYNCHRONIZE CACHE Command (35h).................................................................. 5-134  
5.43 TEST UNIT READY Command (00h)........................................................................... 5-135  
5.44 VERIFY Command (2Fh)................................................................................................ 5-136  
5.45 WRITE (6) Command (0Ah)........................................................................................... 5-137  
5.46 WRITE (10) Command (2Ah)......................................................................................... 5-138  
5.47 WRITE AND VERIFY Command (2Eh) ....................................................................... 5-139  
5.48 WRITE BUFFER Command (3Bh)................................................................................ 5-140  
5.49 WRITE LONG Command (3Fh) .................................................................................... 5-142  
Chapter 6  
FEATURE DESCRIPTIONS  
6.1 KEY FEATURES......................................................................................................... 6-1,6-2  
6.2 WRITE-BACK CACHING......................................................................................... 6-2,6-3  
6.3 ZERO LATENCY READ/WRITE.................................................................................. 6-3  
6.4 DISCONNECT-RECONNECT....................................................................................... 6-3  
6.5 TRACK AND CYLINDER SKEWING ........................................................................... 6-3  
6.6 AVERAGE ACCESS TIME............................................................................................... 6-3  
6.7 EMBEDDED SERVO SYSTEM.................................................................................. 6-3,6-4  
6.8 DATA INTEGRITY AND SECURITY ........................................................................... 6-4  
6.8.1 Media Error Protection ...............................................................................................6-4  
6.8.2 Transfer Error Protection ............................................................................................6-4  
6.8.3 Addressing Error Protection ........................................................................................6-4  
6.8.4 Data Sector Reallocation Error Protection ..................................................................6-4  
6.8.5 Data Verification ........................................................................................................6-5  
6.9 TAGGED COMMAND QUEUING................................................................................. 6-5  
6.10 COMMAND REORDERING ......................................................................................... 6-5  
6.11 BANDED RECORDING ................................................................................................. 6-5  
6.12 SPECIAL FUNCTIONS.................................................................................................... 6-5  
6.13 DIAGNOSTICS................................................................................................................. 6-6  
6.13.1 Power On Self Test (POST) ......................................................................................6-6  
6.13.2 Periodic Self-Adjustments ..........................................................................................6-6  
6.13.3 Host Diagnostics ........................................................................................................6-7  
6.13.4 Log Sense ..................................................................................................................6-7  
6.14 ERROR RECOVERY ..................................................................................................... 6-7  
6.14.1 Seek Error Recovery .................................................................................................6-7  
Maxtor Atlas 10K V iv  
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 ..............................................................................................................6-10  
6.15.2 DIFFSENS SWITCHING ......................................................................................6-10  
6.15.3 DT AND ST CLOCKING .....................................................................................6-11  
6.15.4 CYCLIC REDUNDANCY CHECKING .............................................................6-12  
6.15.5 DOMAIN VALIDATION .....................................................................................6-12  
6.15.6 Adaptive Active Filter (AAF) ...................................................................................6-12  
6.15.7 Transmitter Pre-Compensation with Cutback ..........................................................6-13  
6.15.8 Free Running Clock (FRC) ....................................................................................6-13  
6.15.9 Skew Compensation ................................................................................................6-13  
6.15.10 Information Unit Transfers ....................................................................................6-13  
6.16 HOT PLUGGING/REMOVAL AND INSERTION OF SCSI DEVICES...................... 6-13  
6.16.1 System Considerations .............................................................................................6-14  
6.16.2 APPLICABLE SCSI PHYSICAL DOCUMENTS ..................................................6-15  
Appendix A  
QUICK REFERENCE  
A.1 SCSI-2/SCSI-3 Equivalent Terminology ............................................................................ A-1  
A.2 SCSI Commands and Messages............................................................................................ A-2  
A.3 SCSI Pages.......................................................................................................................... A-3  
A.4 Sense Keys .......................................................................................................................... A-5  
A.5 Status Codes........................................................................................................................ A-5  
Appendix B  
NEGOTIATED RATE INFORMATION PAGE REFERENCE  
B.1 TRANSFER PERIOD FACTOR FIELD.......................................................................... B-1  
B.2 Settings for the QAS, DT, and IU fields .............................................................................. B-2  
Maxtor Atlas 10K V  
v
List of Figures  
Figure 3-1 Dimensions for the Maxtor Atlas 10K V Hard Disk Drives ................................ 3-3  
Figure 3-2 Drive Packing Assembly .................................................................................... 3-5  
Figure 3-3 Jumper Locations on the 68-Pin Wide SCSI Drive PCB ................................... 3-7  
Figure 3-4 Pin Locations on SCA-2 Connector ................................................................ 3-11  
Figure 3-5 J1 Interface Connector Configurations............................................................. 3-15  
Figure 3-6 Mounting Dimensions Maxtor Atlas 10K V Drives.......................................... 3-23  
Figure 3-7 Mounting Screw Clearance for Maxtor Atlas 10K V Drive .............................. 3-24  
Figure 3-8 Lengthwise Airflow Cooling............................................................................ 3-25  
Figure 3-9 Crosswise Airflow Cooling.............................................................................. 3-26  
Figure 6-1 ST and DT CLocking ..................................................................................... 6-11  
Maxtor Atlas 10K V xiii  
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  
SCSI ID Selection on Option Connector (68-Pin SCSI Connector Drives). 3-8  
SCSI ID Pin Assignments (SCA-2 Connector Versions of the Disk Drive). 3-12  
Spin Up on Power On Options................................................................. 3-13  
68-Pin Wide LVD Pin Assignments........................................................... 3-16  
80-Pin SCA-2 LVD Pin Assignments ........................................................ 3-17  
68-Pin Wide Single-Ended Pin Assignments.............................................. 3-19  
80-Pin SCA-2 Single-Ended Pin Assignments ........................................... 3-20  
Specifications............................................................................................... 4-1  
Formatted Capacity ..................................................................................... 4-3  
Timing Specifications for Maxtor Atlas 10K V............................................. 4-4  
Power Reset Limits1 ................................................................................... 4-5  
Power Dissipation in Various Modes (Low-Profile Drives) .......................... 4-6  
Acoustical Characteristics—Sound Power per ISO 7779.............................. 4-7  
Environmental Specifications....................................................................... 4-8  
Shock and Vibration Specifications ............................................................ 4-10  
Error Rates................................................................................................ 4-11  
Supported SCSI Commands ........................................................................ 5-1  
Typical (6-Byte) Command Descriptor Block-Data Format......................... 5-4  
Command Descriptor Block-Field Descriptions........................................... 5-4  
Typical (6-Byte) Command Descriptor Block - Data Format....................... 5-5  
Command Descriptor Block Control Field-Field Descriptions..................... 5-6  
Status Codes................................................................................................ 5-7  
Length Fields............................................................................................. 5-11  
DATA-Phase Command Contents ............................................................ 5-11  
CHANGE DEFINITION Command Descriptor Block-Data Format ....... 5-14  
CHANGE DEFINITION-Field Descriptions ........................................... 5-14  
FORMAT UNIT Command Descriptor Block-Data Format.................... 5-16  
FORMAT UNIT Command-Field Descriptions....................................... 5-16  
FORMAT UNIT Command Supported Options...................................... 5-17  
FORMAT UNIT Parameter List-Data Format.......................................... 5-17  
.FORMAT UNIT Defect List Header-Data Format.................................. 5-18  
FORMAT UNIT Defect List Header-Field Descriptions .......................... 5-18  
FORMAT UNIT Defect Descriptor-Block Format .................................. 5-19  
FORMAT UNIT Defect Descriptor- Physical Sector and Bytes  
From Index Format................................................................................... 5-19  
FORMAT UNIT Initialization Pattern Descriptor-Data Format ............... 5-19  
FORMAT UNIT Initialization Pattern Descriptor-Field Descriptions ...... 5-20  
FORMAT UNIT Initialization Pattern Type............................................ 5-20  
Table 5-19  
Table 5-20  
Table 5-21  
Maxtor Atlas 10K V xiv  
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  
INQUIRY Command Descriptor Block-Data Format .............................. 5-21  
INQUIRY Command Descriptor Block-Field Descriptions...................... 5-21  
Standard Inquiry Data Page-Data Format................................................... 5-22  
Standard Inquiry Data Page-Field Descriptions .......................................... 5-23  
Supported Vital Product Data Pages -Data Format..................................... 5-24  
Vital Product Data-Page Codes ................................................................. 5-24  
Unit Serial Number Page-Data Format...................................................... 5-24  
Unit Serial Number Page-Field Descriptions ............................................. 5-24  
Implemented Operating Definition Page-Data Format............................... 5-25  
Implemented Operating Definition Page-Field Descriptions ...................... 5-25  
ASCII Implemented Operating Definition Page - Data Format.................. 5-26  
Device Identification Page-Data Format .................................................... 5-26  
Device Identification Page-Field Description............................................. 5-27  
Command Support Data Page-Data Format............................................... 5-28  
Command Support Data Page-Field Descriptions ...................................... 5-29  
Command Support Data Page Command or Operation Codes .................. 5-30  
LOG SELECT Command Descriptor Block-Data Format......................... 5-32  
LOG SELECT Command Descriptor Block-Field Descriptions................. 5-32  
Disk Drive Log Pages ................................................................................ 5-33  
LOG SENSE Command Descriptor Block-Data Format............................ 5-34  
LOG SENSE Command Descriptor Block-Field Descriptions ................... 5-34  
LOG SENSE Log Page Format-Data Format............................................. 5-35  
LOG SENSE Log Page Format-Field Descriptions .................................... 5-35  
Generic Log Parameter-Data Format ......................................................... 5-35  
Generic Log Parameter-Field Descriptions................................................. 5-36  
MODE SELECT (6) Command Descriptor Block-Data Format................ 5-37  
MODE SELECT (6) Command Field Descriptions................................... 5-37  
Initiator-Changeable Mode Pages.............................................................. 5-38  
Mode Page Types...................................................................................... 5-39  
Mode Parameter List-Data Format............................................................. 5-39  
Mode Parameter List-Field Descriptions .................................................... 5-40  
Mode Parameter Header (6-Byte)-Data Format......................................... 5-40  
Mode Parameter Header- Field Descriptions.............................................. 5-40  
Mode Parameter Block Descriptor-Data Format........................................ 5-40  
Mode Parameter Block Descriptor-Field Descriptions................................ 5-41  
Categories of Changeable Pages................................................................. 5-41  
Unit Attention Condition Page (Page 0).................................................... 5-41  
Unit Attention Condition Page (Page 0).................................................... 5-42  
Read-Write Error Recovery Page-(Page 1) ............................................... 5-42  
Read-Write Error Recovery Page - Field Descriptions.............................. 5-43  
Disconnect–Reconnect Page (Page 2)........................................................ 5-44  
Disconnect-Reconnect-Field Description (Page 2) .................................... 5-44  
Verify Error Recovery Page-(Page 7) ........................................................ 5-45  
Verify Error Recovery Page-Field Descriptions (Page 7)............................ 5-46  
Caching Page-(Page 8) .............................................................................. 5-46  
Caching Page-Field Descriptions ............................................................... 5-47  
Maxtor Atlas 10K V  
xv  
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  
Control Mode Page-Data Format (Page 0Ah)............................................ 5-48  
Control Mode Page-Field Descriptions...................................................... 5-49  
Notch and Partition Page-(Page 0Ch)........................................................ 5-50  
Notch and Partition Page-Field Descriptions ............................................. 5-51  
Port Control Page Short Format................................................................ 5-52  
Port Control Page Long Format ................................................................ 5-53  
Margin Control Subpage (01h).................................................................. 5-54  
Saved Training Configuration Subpage (02h)............................................. 5-55  
Negotiated Settings Subpage (03h)............................................................. 5-56  
Transceiver Mode ..................................................................................... 5-56  
Report Transfer Capabilities Subpage (4)................................................... 5-57  
Field Descriptions...................................................................................... 5-57  
Information Exceptions Control Page-(Page 1Ch)..................................... 5-59  
Information Exceptions Control Page-Field Descriptions (Page 1Ch) ........ 5-60  
Codes Used by the MRIE Field ................................................................ 5-61  
MODE SELECT (10) Command Descriptor Block-Data Format.............. 5-62  
Mode Parameter Header (10-Byte)-Data Format ....................................... 5-62  
Mode Parameter Block Descriptor-Data Format........................................ 5-62  
Mode Parameter Block Descriptor-Field Descriptions................................ 5-63  
MODE SENSE (6) Command Descriptor Block-Data Format .................. 5-64  
MODE SENSE Command-Field Descriptions .......................................... 5-64  
Mode Parameter Header (6 Byte)-Data Format.......................................... 5-64  
Mode Parameter Header and Block Descriptor-Field Descriptions............. 5-65  
Read-Only Mode Pages ............................................................................ 5-65  
Format Device Page-(Page 3) .................................................................... 5-65  
Format Device Page-Field Descriptions (Page 3)........................................ 5-66  
Rigid Disk Geometry Page-(Page 4).......................................................... 5-67  
Rigid Disk Geometry Page-Field Descriptions (Page 4)............................. 5-68  
MODE SENSE (10) Command Descriptor Block-Data Format................. 5-69  
Mode Parameter Header (10 Byte)-Data Format........................................ 5-69  
Mode Parameter Block Descriptor-Data Format........................................ 5-69  
Mode Parameter Header & Block Descriptor-Field Descriptions................ 5-70  
PERSISTENT RESERVATION IN Command Descriptor  
Block-Data Format.................................................................................... 5-71  
PERSISTENT RESERVATION IN Command-Field Descriptions......... 5-72  
Read Keys Parameters-Data Format........................................................... 5-72  
Read Keys Parameters-Field Descriptions .................................................. 5-73  
Read Reservations Parameters-Data Format .............................................. 5-73  
Read Reservations Parameters-Field Descriptions...................................... 5-74  
PERSISTENT RESERVATION IN Read Reservations  
Table 5-105  
Table 5-106  
Table 5-107  
Table 5-108  
Table 5-109  
Table 5-110  
Descriptor-Data Format............................................................................. 5-74  
PERSISTENT RESERVATION IN Read Reservations  
Table 5-111  
Descriptor-Field Descriptions .................................................................... 5-75  
Persistent Reservation Type Codes and Their Meanings............................ 5-76  
When Do Conflicts Between Existing Reservations and New  
Table 5-112  
Table 5-113  
Reservations Exist?.................................................................................... 5-78  
Maxtor Atlas 10K V xvi  
Table 5-114  
PERSISTENT RESERVATION OUT Command Descriptor  
Block-Data Format.................................................................................... 5-79  
PERSISTENT RESERVATION OUT Command-Field Descriptions..... 5-80  
PERSISTENT RESERVATION OUT Command’s Service  
Table 5-115  
Table 5-116  
Action Descriptions................................................................................... 5-81  
Persistent Reservation Type Codes and Their Meanings............................ 5-85  
PERSISTENT RESERVATION OUT Parameter List-Data Format........ 5-86  
PERSISTENT RESERVATION OUT Parameter List-Field Descriptions 5-87  
Device Server Interpretation of Service and Scope Value .......................... 5-88  
READ (6) Command-Data Format........................................................... 5-89  
READ (6) Command-Field Descriptions................................................... 5-89  
READ (10) Command-Data Format ......................................................... 5-90  
READ (10) Command-Field Descriptions................................................. 5-90  
READ BUFFER Command-Data Format ................................................ 5-91  
READ BUFFER Command-Field Descriptions........................................ 5-92  
READ CAPACITY Command-Data Format............................................ 5-93  
READ CAPACITY Command-Field Descriptions ................................... 5-93  
READ CAPACITY Returned Data-Data Format..................................... 5-93  
READ DEFECT DATA (10) Command-Data Format ............................. 5-94  
READ DEFECT DATA (10) Command-Field Description ...................... 5-95  
Defect Descriptor-Block Format................................................................ 5-95  
Defect Descriptor-Bytes From Index Format, or Physical Sector Format.... 5-96  
Defect List Header -Data Format............................................................... 5-96  
Defect List Header-Field Descriptions........................................................ 5-96  
READ DEFECT DATA (12) Command-Data Format ............................. 5-97  
READ DEFECT DATA (12) Command-Field Description ...................... 5-97  
Defect Descriptor-Block Format................................................................ 5-98  
Defect Descriptor-Bytes From Index Format, or Physical Sector Format.... 5-98  
Defect List Header-Data Format................................................................ 5-98  
Defect List Header-Field Descriptions........................................................ 5-98  
READ LONG Command Descriptor Block-Data Format......................... 5-99  
READ LONG Command Descriptor Block-Field Descriptions................. 5-99  
READ LONG Command-Returned Data ................................................ 5-99  
REASSIGN BLOCKS Command Descriptor Block-Data Format........... 5-100  
REASSIGN BLOCKS Defect List Header-Data Format.......................... 5-100  
REASSIGN BLOCKS Defect List Header-Field Description .................. 5-100  
REASSIGN BLOCKS Defect Descriptor-Data Format ........................... 5-100  
Diagnostic Pages Supported by The Drives.............................................. 5-101  
RECEIVE DIAGNOSTIC RESULTS Command Descriptor  
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  
Block-Data Format.................................................................................. 5-101  
RECEIVE DIAGNOSTIC RESULTS Command Descriptor  
Table 5-151  
Block-Field Descriptions ......................................................................... 5-101  
Supported Diagnostics Pages Page-Data Format....................................... 5-102  
Translate Address Page-Data Format........................................................ 5-103  
Translate Address Page-Field Descriptions ............................................... 5-103  
RELEASE (6) Command Descriptor Block-Data Format ........................ 5-104  
Table 5-152  
Table 5-153  
Table 5-154  
Table 5-155  
Maxtor Atlas 10K V xvii  
Table 5-156  
Table 5-157  
Table 5-158  
Table 5-159  
RELEASE (6) Command-Field Descriptions........................................... 5-104  
RELEASE (10) Command Descriptor Block-Data Format ...................... 5-105  
RELEASE (10) Command-Field Descriptions ......................................... 5-105  
REPORT DEVICE IDENTIFIER Command Descriptor  
Block-Data Format.................................................................................. 5-106  
REPORT DEVICE IDENTIFIER Command Descriptor  
Table 5-160  
Block-Field Descriptions ......................................................................... 5-106  
REPORT DEVICE IDENTIFIER Parameter List-Data Format............. 5-106  
REPORT DEVICE IDENTIFIER Parameter List-Field Descriptions..... 5-106  
REPORT LUNS Command Descriptor Block-Data Format................... 5-107  
REPORT LUNS Command Descriptor Block-Field Description ........... 5-107  
LUN Reporting Parameter List -Data Format ......................................... 5-107  
REQUEST SENSE Command Descriptor Block-Data Format ............... 5-108  
REQUEST SENSE Command Descriptor Block-Field Description........ 5-108  
Sense Data Format for Error Code 70h or 71h-Data Format.................... 5-109  
Sense Data Fields (Error Code 70h)-Field Descriptions............................ 5-110  
Supported Sense Keys.............................................................................. 5-111  
Sense Key Information Field Contents..................................................... 5-112  
Supported Additional Sense Codes and Sense Code Qualifiers (in Hex)... 5-113  
Sense-Key Specific Field Contents........................................................... 5-121  
ILLEGAL REQUEST Sense Key Field Pointer Bytes\Data Format......... 5-122  
ILLEGAL REQUEST Sense Key Field Pointer Bytes\Field Descriptions 5-122  
NOT READY Sense Key - Progress Indication Bytes\Data Format........ 5-122  
NOT READY Sense Key - Progress Indication Bytes\Field Descriptions 5-122  
MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry  
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  
Count-Data Format................................................................................. 5-123  
MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry Count 5-  
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  
RESERVE (6) Command Descriptor Block-Data Format ....................... 5-124  
RESERVE (6) Command-Field Descriptions.......................................... 5-124  
RESERVE (10) Command Descriptor Block-Data Format ..................... 5-125  
RESERVE (10) Command-Field Descriptions ....................................... 5-125  
Extent Descriptors-Data Format .............................................................. 5-126  
Reservation Types................................................................................... 5-126  
Parameter List When LongID and Extent Bits = 1-Data Format.............. 5-126  
RESERVE (10) ID Only Parameter List-Data Format............................. 5-126  
REZERO UNIT Command Descriptor Block-Data Format................... 5-127  
SEEK (6) Command Descriptor Block-Data Format................................ 5-128  
SEEK (10) Command Descriptor Block-Data Format.............................. 5-129  
SEND DIAGNOSTIC Command Descriptor Block-Data Format .......... 5-130  
SEND DIAGNOSTIC Command-Field Descriptions............................. 5-130  
Supported Diagnostic Page List-Data Format........................................... 5-131  
Translate Address Page-Data Format........................................................ 5-131  
SET DEVICE IDENTIFIER Command Descriptor Block-Data Format. 5-132  
SET DEVICE IDENTIFIER Command Descriptor  
Block-Field Descriptions ......................................................................... 5-132  
Maxtor Atlas 10K V xviii  
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  
SET DEVICE IDENTIFIER Parameter List-Data Format....................... 5-132  
SET DEVICE IDENTIFIER Parameter List-Field Descriptions .............. 5-132  
START STOP UNIT Command Descriptor Block-Data Format ........... 5-133  
START STOP UNIT Command-Field Descriptions.............................. 5-133  
SYNCHRONIZE CACHE Command Descriptor Block-Data Format .. 5-134  
SYNCHRONIZE CACHE Command-Field Descriptions ..................... 5-134  
TEST UNIT READY Command Descriptor Block-Data Format........... 5-135  
VERIFY Command Descriptor Block-Data Format................................ 5-136  
VERIFY Command-Field Descriptions................................................... 5-136  
WRITE (6) Command Descriptor Block-Data Format............................ 5-137  
WRITE (6) Command-Field Descriptions............................................... 5-137  
WRITE (10) Command Descriptor Block-Data Format.......................... 5-138  
WRITE (10) Command-Field Descriptions............................................. 5-138  
WRITE AND VERIFY Command Descriptor Block-Data Format ........ 5-139  
WRITE AND VERIFY Command -Field Descriptions.......................... 5-139  
WRITE BUFFER Command Descriptor Block-Data Format................. 5-140  
WRITE BUFFER Command -Field Descriptions................................... 5-141  
WRITE LONG Command Descriptor Block-Data Format..................... 5-142  
WRITE LONG Command-Field Descriptions ....................................... 5-142  
SCSI-2/SCSI-3 Equivalent Terminology.................................................... A-1  
SCSI-3 Quick Reference – Commands...................................................... A-2  
SCSI-3 Quick Reference – Messages.......................................................... A-3  
SCSI-3 Quick Reference - Pages ............................................................... A-3  
SCSI-3 Quick Reference – Sense Keys....................................................... A-5  
SCSI-3 Quick Reference – Status Codes.................................................... A-5  
Transfer Period Factor Field Values When PARL = 1................................ B-1  
Transfer Period Factor Field Values When PARL = 0................................ B-2  
Settings for the QAS, DT, and IU Fields of the Negotiated Rate  
Table A-2  
Table A-3  
Table A-4  
Table A-5  
Table A-6  
Table B-1  
Table B-2  
Table B-3  
Information Page (INQUIRY Command) ................................................. B-2  
Maxtor Atlas 10K V xix  
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. Its primary audience is the OEM  
technical staff that makes disk drive purchase and configuration decisions, and system  
integrators that are responsible for the SCSI interface. This manual is not intended for  
end-users and is not a users manual or an installation guide. The manual provides  
information about installation, interface command implementation, maintenance, and  
gives the general specifications of the drive.  
1.2  
MANUAL ORGANIZATION  
This manual is organized into the following chapters:  
• Chapter 1 – About This Manual  
• Chapter 2 – General Description  
• Chapter 3 – Installation  
• Chapter 4 – Specifications  
• Chapter 5 – SCSI Description  
• Chapter 6 – Feature Descriptions  
• Appendix A – Quick Reference  
• Appendix B – Negotiated Page Information Page Reference  
• Glossary  
• Index  
Maxtor Atlas 10K V 1-1  
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. In addition, the following abbreviations are used in this  
manual:  
• ASIC  
• Kbpi  
• dB  
application-specific integrated circuit  
thousands of bits per inch  
decibels  
• dBA  
• ECC  
• Kfci  
• Gbit  
• GB  
decibels, A weighted  
error correcting code  
thousands of flux changes per inch  
gigabit  
gigabyte  
• Hz  
hertz  
• KB  
kilobytes  
• LSB  
• LVDS  
• mA  
• MB  
least significant bit  
low voltage differential SCSI  
milliamperes  
megabytes (1 MB = 1,000,000 bytes when referring to disk  
transfer rates or storage capacities and 1,048,576 bytes in all  
other cases)  
• Mbit/s  
• MB/s  
• MHz  
• ms  
megabits per second  
megabytes per second  
megahertz  
milliseconds  
• MSB  
• mV  
• ns  
most significant bit  
millivolts  
nanoseconds  
• SCSI  
• tpi  
Small Computer System Interface  
tracks per inch  
microseconds  
• ms  
• V  
volts  
1-2 Maxtor Atlas 10K V  
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. Examples are Prefetch Enable  
(PE) and Cache Enable (CE).  
• Hexadecimal Notation: The hexadecimal notation is given in 9-point  
subscript form. An example is 30H.  
• Signal Negation: A signal that is non-active or is in its non-asserted state.  
• Messages: A message that is sent from the drive to the host is listed in all  
capitals. An example is BUS DEVICE RESET.  
Naming Conventions:  
• Host: In general, the system in which the drive resides is referred to as  
the host.  
• Computer Voice: This refers to items you type at the computer  
keyboard. These items are listed in 10-point, all capitals, Courier font.  
An example is FORMAT.  
1.4  
REFERENCES  
For additional information about the SCSI interface, refer to:  
• ANSI Small Computer System Interface-2 (SCSI-2) Specification, ANSI  
X3T9.2/86-109, Revision 10k.  
• ANSI Small Computer System Interface-3 (SCSI-3) Specification, ANSI  
X3T10, August 1994.  
• SPI-3 Specification Revision SPI-4 Spec Revision 10  
Maxtor Atlas 10K V 1-3  
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.1, and 300 gigabytes (GB). These hard disk drives use  
nonremovable, 84 mm diameter hard disks and are available with the following SCSI  
configurations:  
• Ultra320 SCSI, Ultra2, Ultra SCSI 68-pin Wide (16-bit)  
• Ultra320 SCSI, Ultra2, Ultra SCSI 80-pin SCA-2 (16-bit)  
The Maxtor Atlas 10K V hard disk drives feature an embedded SCSI drive controller  
and use SCSI commands to optimize system performance. Because the drive manages  
media defects and error recovery internally, these operations are fully transparent to  
the user.  
The innovative design of the Maxtor Atlas 10K V hard disk drives enables Maxtor to  
produce a family of low-cost, high-reliability drives.  
2.2  
KEY FEATURES  
The Maxtor Atlas 10K V hard disk drive includes the following key features:  
General  
• Formatted storage capacity of 73.5 GB (1 disk, 2 heads), 147.1 GB (2 disks,  
4 heads), and 300 GB (4 disks, 8 heads)  
• Low profile, 1-inch height  
• Industry standard 3 1/2-inch form factor  
• Embedded SCSI controller  
Maxtor Atlas 10K V 2-1  
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. Look-ahead DisCache feature  
with continuous prefetch and WriteCache write-buffering capabilities  
• Read-on-arrival firmware  
• Tagged Command Queuing with Reordering  
• ECC on-the-fly  
• Highly automated SCSI protocol (including Auto Read/Write)  
• 1:1 interleave on read/write operations  
• High performance Ultra320 SCSI interface  
• SCSI-2, and SCSI-3 supported  
• Ultra 320 SCSI  
• Ultra 160 SCSI  
• Ultra-2 SCSI-3 LVDS transfer rates supported  
• Fast Ultra and Ultra-2 SCSI transfer rates supported (SCSI-3 compliant)  
• S.M.A.R.T. 2 (Self-Monitoring, Analysis and Reporting Technology)  
• SCSI bus active negation drivers  
• Burst data transfer rate of up to 6.0 MB/s asynchronous, 40 MB/s Ultra  
SCSI, 80 MB/s Ultra2 SCSI, 160 MB/s Ultra160 SCSI, and 320 MB/s  
Ultra320 SCSI.  
• SCSI bus fairness  
2-2 Maxtor Atlas 10K V  
• 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 Control  
Reliability  
• Automatic retry on read errors  
• 360-bit, interleaved Reed-Solomon Error Correcting Code (ECC), with  
cross checking correction up to three separate bursts of 32 bits each  
totalling up to 96 bits in length  
• Self-diagnostic firmware  
• Transparent media defect mapping  
• High performance, in-line defective sector skipping  
• Reassignment of defective sectors discovered in the field, without  
reformatting  
• Thermal Sensing monitors the drive temperature to ensure on-going drive  
reliability  
• Shock Protection System III (SPS III) protects the drive against specific  
types of handling events that could cause damage to the drive.  
Maxtor Atlas 10K V 2-3  
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.5 inch series drives.  
• Canadian Standards Association (CSA) Standard C.22.2 No. 950. This  
certificate is category c-UL recognized pertaining to all 3.5 inch series  
drives.  
• TUV Rheinland Standard EN60950. This certificate is a category  
certification pertaining to all 3.5 inch series drives.  
2-4 Maxtor Atlas 10K V  
Product EMI/EMC Qualifications:  
Maxtor Corporation’s disk drive products meet all domestic and international electro-  
magnetic 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.  
• MIC Mark (Korea) is a Certificate of registration for SCSI disk drives.  
• Maxtor’s disk drives are designed as a separate subassembly that conforms to  
the FCC Rules for Radiated and Conducted emissions, Part 15 Subpart J;  
Class B when installed in a given computer system.  
• Maxtor drives conform to Canadian EMC Standard ICES-003.  
2.4  
HARDWARE REQUIREMENTS  
The Maxtor Atlas 10K V hard disk drive is compatible with host computers and  
controllers that provide a 68-pin Wide, or 80-pin SCA-2 interface. A 50-pin to 68-  
pin adapter is required to use the 68-pin Wide drive in a 50-pin cabling configuration.  
Termination is required on the Maxtor Atlas 10K V hard disk drives as they do not  
support on-board SCSI termination.  
Maxtor Atlas 10K V 2-5  
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.  
• Remove power from the computer system (or expansion unit) before  
installing or removing the drive to prevent the possibility of electrical  
shock or damage to the drive. Unplug the unit containing the drive to  
provide an added measure of safety.  
• Read, understand, and observe all label warnings.  
3.1.2  
Handling  
Damage to the drive can occur as the result of careless handling, vibration, shock,  
or electrostatic discharge (ESD). Always handle the drive with care to avoid damage  
to the precision internal components.  
CAUTION: A 1/4-inch drop onto a hard surface can damage the drive.  
Follow these guidelines to avoid damage to the drive:  
• Always observe prescribed ESD precautions.  
• Keep the drive in its anti-static bag until ready to install.  
• Always use a properly fitted wrist strap or other suitable ESD protection  
when handling the drive.  
• Hold drive only by its sides. Do not touch any components on the  
PCBA.  
Maxtor Atlas 10K V 3-1  
• 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.  
• Do not stack objects on the drive.  
• Never force the drive or the mounting brackets into the drive bay.  
• Do not expose the drive to moisture.  
• Do not damage any seals on the drive; doing so may void the warranty.  
3.1.3  
Electrostatic Discharge (ESD) Protection  
Various electrical components within the disk drive are sensitive to static electricity  
and Electrostatic Discharge (ESD). Even a static buildup or discharge that is too  
slight to feel can be sufficient to destroy or degrade a component's operation.  
To minimize the possibility of ESD-related damage to the drive, we strongly  
recommend using both, a properly installed workstation anti-static mat and a  
properly installed ESD wrist strap. When correctly installed, these devices reduce  
the buildup of static electricity which might harm the drive.  
• Observe the following precautions to avoid ESD-related problems:  
• Use a properly installed anti-static pad on your work surface.  
• Always use a properly fitted and grounded wrist strap or other suitable  
ESD protection when handling the drive and observe proper ESD  
grounding techniques.  
• Hold the drive only by its sides. Do not touch any components on the  
PCBA.  
• Leave the drive in its anti-static bag until you are ready to install it in the  
system.  
• Place the drive on a properly grounded anti-static work surface pad  
when it is out of its protective anti-static bag.  
• Do not use the bag as a substitute for the work surface anti-static pad.  
The outside of the bag may not have the same anti-static properties as  
the inside. It could actually increase the possibility of ESD problems.  
• Do not use any test equipment to check components on the electronics  
module. There are no user-serviceable components on the drive.  
3-2  
Maxtor Atlas 10K V  
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.  
Maxtor Atlas 10K V 3-3  
 
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. The shock feet  
attenuate the short-pulse shocks that occur when placing the drive on a hard surface.  
If the drive is tested on a hard surface, it should be supported such that the shock  
feet are not in contact with a hard surface (the drive should be supported in the  
middle, between the shock feet).  
Note: To provide optimal protection the shock feet are designed to ex-  
ceed the form factor when uncompressed.  
3.3  
UNPACKING INSTRUCTIONS  
CAUTION: The maximum limits for physical shock can be exceeded if  
the drive is not handled properly. Special care should be  
taken not to bump or drop the drive.  
1. Open the shipping container and remove the packing assembly that contains  
the drive.  
2. Remove the drive from the packing assembly.  
CAUTION: During shipment and handling, the antistatic electrostatic dis-  
charge (ESD) bag prevents electronic component damage due  
to electrostatic discharge. To avoid accidental damage to the  
drive, do not use a sharp instrument to open the ESD bag.  
Save the packing materials for possible future use.  
3. When you are ready to install the drive, remove it from the ESD bag.  
3-4  
Maxtor Atlas 10K V  
Figure 3-2 shows the packing assembly for a single Maxtor Atlas 10K V hard disk  
drive. Shipping containers for 25-pack are available for multiple drive shipments.  
Figure 3-2 Drive Packing Assembly  
Maxtor Atlas 10K V 3-5  
 
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  
CAUTION: Before you begin, review the Safety, ESD, and Handling precau-  
tions described at the beginning of this manual to avoid personal in-  
jury or damage to equipment.  
3.4.2  
Jumper Options on the 68-Pin Wide PCB  
This section describes how to configure the jumpers on Maxtor Atlas 10K V disks  
with 68-pin SCSI interface connectors. The following features are jumper-  
selectable:  
• SCSI ID (0), (1), (2), (3) – SCSI Bus Device Identification  
• Delay Spin  
• Single-Ended, Disable LVD  
• Busy Out (Remote LED)  
• Write Protect  
• Stagger Spin  
Note: The disk drive does not support on-board SCSI termina-  
tion.  
Note: The configuration of a Maxtor Atlas 10K V hard disk  
drive depends on the host system in which it is to be in-  
stalled. Figure 3-3 shows the printed circuit board (PCB)  
assemblies for 68-pin SCSI configurations, indicating the  
jumpers that control some of these options.  
3-6  
Maxtor Atlas 10K V  
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
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
Note: 0 = No Jumper, 1 = Jumper Installed  
Configure the drive for remote (external) SCSI ID selection by removing the SCSI  
ID jumpers (if present) from the referenced SCSI ID pins. Then connect the leads  
from the external selection switch to the referenced pins. Observe the following  
guidelines while doing so:  
• ID bit 0, at Pin 8, is the Least Significant Bit.  
• SCSI ID bits 0, 1, 2, and 3 (pins 8, 6, 4, and 2, respectively) are active  
LOW signals. That is, the bit is a 1 if the corresponding remote switch  
is closed to ground or jumper installed.  
• Use pins 1, 3, 5 and 7 as the associated ground returns for ID bits 3, 2,  
1, and 0, respectively.  
3.4.2.1  
Write Protection  
To configure Write Protection for the drive, install a jumper across pin pair 11/12  
on the J3 Option Header. To disable Write Protection on the drive, remove the  
jumper.  
3-8  
Maxtor Atlas 10K V  
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  
3.4.2.4  
Single-Ended Operation – Force SE (Disable LVD)  
Install a jumper across pin pair 17/18 (SE) on the J3 Option Header to operate the  
disk drive as a single-ended device. Remove the SE jumper for LVD operation and  
monitoring of the DIFFSENS signal.  
Remote Busy and Fault Displays  
Busy and Fault status of the drive can be monitored remotely by connecting a  
remote (external) Busy and/or remote Fault display LEDs.  
Remote Fault LED  
On the J1 Option Connector, connect the cathode side of the remote Fault LED  
to pin 2, Fault LED. Connect the anode side of the LED to pin 11, +5V.  
Maxtor Atlas 10K V 3-9  
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.  
Note: The SCA-2 Connector version of the disk drives does not provide  
the following jumper configuration: TERMPWR, Active Termina-  
tion, or Write Protection.  
3.4.3.1  
Termination for the 80-Pin SCA-2 Connector Versions  
CAUTION: These versions of Maxtor Atlas 10K V disk drives cannot be  
configured to provide bus termination. Therefore, be sure to  
properly terminate the SCSI bus on which this drive is in-  
stalled.  
Note: Refer to your system or SCSI controller documentation regard-  
ing any additional recommendations regarding drive placement  
on the SCSI bus and SCSI bus termination.  
3-10 Maxtor Atlas 10K V  
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).  
Note: Refer to your system or SCSI controller documentation for spe-  
cific recommendations about assigning SCSI ID numbers for  
your specific system.  
Figure 3-4 Pin Locations on SCA-2 Connector  
Maxtor Atlas 10K V 3-11  
 
Table 3-2 SCSI ID Pin Assignments (SCA-2 Connector Versions of the Disk Drive)  
Location on SCA Connector  
SCSI ID  
ID3 - Pin  
ID2 - Pin 40 ID1 - Pin 79 ID0 - Pin 39  
80  
0
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
Note: 0 indicates an open circuit and 1 indicates ground.  
3.4.3.3  
Spin Up for the 80-Pin SCA-2 Connector Versions  
Maxtor Atlas 10K V drives have three Spin Up modes:  
Option 1 Spin up occurs immediately when power is applied.  
Option 2 Drive spin up occurs after a predetermined delay following power on.  
Set the delay parameters with the MODE SELECT Command,  
Maxtor (Vendor) Special Function Control Page (39h).The delay is  
equal to a user-specified multiplier multiplied by the numerical SCSI  
ID of the drive. This will give a staggered spin-up in multiple-drive  
installations.  
Option 3 Drive spin up is controlled by the START STOP UNIT command.  
Configure the desired spin up option (Table 3-3) by setting the state of the  
DELAY_SPIN (Pin 38) and STAGGER_SPIN (Pin 78) inputs on the 80-pin SCA-  
2 connector (Figure 3-4). The states of these signals are set by using either hard-  
wired connections at the backplane or backplane logic.  
3-12 Maxtor Atlas 10K V  
 
Table 3-3 Spin Up on Power On Options  
STAGGER_SPIN  
(Pin 78)  
DELAY_SPIN  
(Pin 38)  
Option  
Option 1 – Spin Up When Power is Applied  
Option 2 – Spin Up After Delay  
Option 3 – Spin Up on START Command  
Reserved  
Open  
Ground  
Open  
Open  
Open  
Ground  
Ground  
Ground  
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. To use this output,  
connect a user-supplied LED cathode to the BUSY_OUT connection, pin 77 on  
the SCA Connector (Figure 3-4). The LED anode must be attached to the proper  
+5 VDC supply through an appropriate current-limiting resistor.  
Maxtor Atlas 10K V 3-13  
 
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.  
Figure 3-5 J1 Interface Connector Configurations  
3-14 Maxtor Atlas 10K V  
 
Maxtor Atlas 10K V 3-15  
3.5.1  
68-Pin Wide SCSI Connector - LVD  
Table 3-4 68-Pin Wide LVD Pin Assignments  
CONNECTOR  
CONTACT  
NUMBER  
CONNECTOR  
CONTACT  
NUMBER  
SIGNAL  
NAME  
CABLE CONDUCTOR  
NUMBER  
SIGNAL  
NAME  
+DB (12)  
+DB (13)  
+DB (14)  
+DB (15)  
+DB (P1)  
+DB (0)  
+DB (1)  
+DB (2)  
+DB (3)  
+DB (4)  
+DB (5)  
+DB (6)  
+DB (7)  
+DB (P)  
GROUND  
DIFFSENS  
TERMPWR  
TERMPWR  
RESERVED  
GROUND  
+ATN  
GROUND  
+BSY  
+ACK  
+RST  
+MSG  
+SEL  
+C/D  
+REQ  
+I/O  
1
2
3
4
5
6
7
8
1
3
5
7
2
4
6
8
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
65  
66  
67  
68  
–DB (12)  
–DB (13)  
–DB (14)  
–DB (15)  
–DB (P1)  
–DB (0)  
–DB (1)  
–DB (2)  
–DB (3)  
–DB (4)  
–DB (5)  
–DB (6)  
–DB (7)  
–DB (P)  
GROUND  
GROUND  
TERMPWR  
TERMPWR  
RESERVED  
GROUND  
–ATN  
GROUND  
–BSY  
–ACK  
–RST  
–MSG  
–SEL  
–C/D  
–REQ  
–I/O  
–DB (8)  
–DB (9)  
–DB (10)  
–DB (11)  
9
10  
12  
14  
16  
18  
20  
22  
24  
26  
28  
30  
32  
34  
36  
38  
40  
42  
44  
46  
48  
50  
52  
54  
56  
58  
60  
62  
64  
66  
68  
11  
13  
15  
17  
19  
21  
23  
25  
27  
29  
31  
33  
35  
37  
39  
41  
43  
45  
47  
49  
51  
53  
55  
57  
59  
61  
63  
65  
67  
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
33  
34  
+DB (8)  
+DB (9)  
+DB (10)  
+DB (11)  
Note: The conductor number refers to the conductor position when  
using 0.635 mm (0.025 inch) centerline flat ribbon cable. Other  
cable types may be used to implement equivalent contact assign-  
ments.  
3.5.1.1  
68-Pin Wide Mating Connector  
The cable plug connector that mates with the 68-pin hard disk drive connector is  
the AMP AMPLIMITE .050 Series III, part number 749925-5.  
3-16 Maxtor Atlas 10K V  
 
3.5.2  
80-Pin SCA-2 SCSI Connector - LVD  
Table 3-5 80-Pin SCA-2 LVD Pin Assignments  
CABLE  
CONDUCTOR  
NUMBER  
80-PIN CONNECTOR CONTACT  
AND SIGNAL NAME  
80-PIN CONNECTOR CONTACT  
AND SIGNAL NAME  
12V CHARGE  
12V  
1
NOT  
APPLICABLE  
12V GROUND  
12V GROUND  
12V GROUND  
MATED 1  
OPT 3.3V CHARGE  
DIFFSNS  
+DB (11)  
+DB (10)  
+DB (9)  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
65  
2
12V  
3
12 V  
4
OPT 3.3 VOLTS  
OPT 3.3 VOLTS  
- DB (11)  
- DB (10)  
- DB (9)  
- DB (8)  
- I/O  
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
+DB (8)  
+I/O  
- REQ  
+REQ  
- C/D  
+C/D  
- SEL  
+SEL  
- MSG  
+MSG  
- RST  
+RST  
- ACK  
+ACK  
- BSY  
+BSY  
- ATN  
+ATN  
- DB (P0)  
- DB (7)  
- DB (6)  
- DB (5)  
- DB (4)  
-DB (3)  
+DB (P0)  
+DB (7)  
+DB (6)  
+DB (5)  
+DB (4)  
+DB (3)  
Maxtor Atlas 10K V 3-17  
–DB (2)  
–DB (1)  
–DB (0)  
–DB (P1)  
–DB (15)  
–DB (14)  
–DB (13)  
–DB (12)  
5V  
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  
66  
67  
68  
69  
70  
71  
72  
73  
74  
75  
76  
77  
78  
79  
80  
5V  
5V GROUND  
5V GROUND  
ACTIVE LED OUT  
DLYD_START  
SCSI ID (1)  
SCSI ID (3)  
5V CHARGE  
SPINDLE SYNC  
RMT START  
SCSI ID (0)  
SCSI ID (2)  
3.5.2.1  
80-Pin SCA-2 Mating Connectors  
The compatible 80-pin mating connectors are:  
• Right-angle receptacle, AMP CHAMP, .050 Series I, part number 787535-1.  
• Vertical receptacle, AMP CHAMP .050 Series I, part number 787311-2.  
• Vertical receptacle, BERG part number 71780-001.  
3-18 Maxtor Atlas 10K V  
3.5.3  
68-Pin Wide Single-Ended SCSI Connector  
Table 3-6 68-Pin Wide Single-Ended Pin Assignments  
CONNECTOR  
CONTACT  
NUMBER  
CONNECTOR  
CONTACT  
NUMBER  
SIGNAL  
NAME  
CABLE CONDUCTOR  
NUMBER  
SIGNAL  
NAME  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
RESERVED  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
1
2
3
4
5
6
7
8
1
3
5
7
2
4
6
8
35  
36  
37  
38  
39  
40  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
65  
66  
67  
68  
–DB (12)  
–DB (13)  
–DB (14)  
–DB (15)  
–DB (P1)  
–DB (0)  
–DB (1)  
–DB (2)  
–DB (3)  
–DB (4)  
–DB (5)  
–DB (6)  
–DB (7)  
–DB (P)  
GROUND  
GROUND  
RESERVED  
GROUND  
–ATN  
GROUND  
–BSY  
–ACK  
–RST  
–MSG  
–SEL  
–C/D  
–REQ  
–I/O  
–DB (8)  
–DB (9)  
–DB (10)  
–DB (11)  
9
10  
12  
14  
16  
18  
20  
22  
24  
26  
28  
30  
32  
38  
40  
42  
44  
46  
48  
50  
52  
54  
56  
58  
60  
62  
64  
66  
68  
11  
13  
15  
17  
19  
21  
23  
25  
27  
29  
31  
37  
39  
41  
43  
45  
47  
49  
51  
53  
55  
57  
59  
61  
63  
65  
67  
9
10  
11  
12  
13  
14  
15  
16  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
33  
34  
Note:  
1. The minus sign next to a signal indicates active low.  
2. The conductor number refers to the conductor position when using 0.635  
mm (0.025 inch) centerline flat ribbon cable. Other cable types may be used  
to implement equivalent contact assignments.  
Maxtor Atlas 10K V 3-19  
3.5.4  
80-Pin SCA-2 Single-Ended SCSI Connector  
Table 3-7 80-Pin SCA-2 Single-Ended Pin Assignments  
CABLE  
80-PIN CONNECTOR CONTACT  
AND SIGNAL NAME  
80-PIN CONNECTOR CONTACT  
CONDUCTOR  
NUMBER  
AND SIGNAL NAME  
12V CHARGE  
12V  
1
2
3
4
5
6
7
8
NOT APPLICABLE  
12V GROUND  
12V GROUND  
12V GROUND  
MATED 1  
41  
42  
43  
44  
45  
46  
47  
48  
49  
50  
51  
52  
53  
54  
55  
56  
57  
58  
59  
60  
61  
62  
63  
64  
65  
66  
67  
68  
69  
70  
71  
72  
1
12V  
12 V  
OPT 3.3 VOLTS  
OPT 3.3 VOLTS  
–DB (11)  
–DB (10)  
–DB (9)  
–DB (8)  
–I/O  
OPT 3.3V CHARGE  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
GROUND  
MATED 2  
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
26  
27  
28  
29  
30  
31  
32  
33  
34  
35  
36  
37  
38  
39  
40  
–REQ  
–C/D  
–SEL  
–MSG  
–RST  
–ACK  
–BSY  
–ATN  
–DB (P0)  
–DB (7)  
–DB (6)  
–DB (5)  
–DB (4)  
–DB (3)  
–DB (2)  
–DB (1)  
–DB (0)  
–DB (P1)  
–DB (15)  
–DB (14)  
–DB (13)  
–DB (12)  
5V  
74  
75  
76  
77  
78  
79  
80  
5V  
5V GROUND  
5V GROUND  
ACTIVE LED OUT  
DLYD_START  
SCSI ID (1)  
SCSI ID (3)  
5V CHARGE  
SPINDLE SYNC  
RMT START  
SCSI ID (0)  
SCSI ID (2)  
3-20 Maxtor Atlas 10K V  
 
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. For mounting, #6-32 UNC screws are  
recommended.  
Figure 3-6 Mounting Dimensions Maxtor Atlas 10K V Drives  
Maxtor Atlas 10K V 3-21  
 
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. Clearance from  
the drive to any other surface (except mounting surfaces) must be a minimum of  
1.25 mm (0.05 inches).  
Figure 3-7 Mounting Screw Clearance for Maxtor Atlas 10K V Drive  
CAUTION: The PCB is very close to the mounting holes. Do not exceed the speci-  
fied length for the mounting screws. The specified screw length allows full  
use of the mounting-hole threads, while avoiding damaging or placing  
unwanted stress on the PCB.  
Figure 3-7 specifies the minimum clearance between the PCB and the  
screws in the mounting holes. The maximum torque applied to the  
screws must not exceed 8.6 inch-pounds.  
3-22 Maxtor Atlas 10K V  
 
3.6.3  
3.6.4  
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.  
Ventilation  
The Maxtor Atlas 10K V hard disk drive may operate with or without a cooling fan  
provided that the maximum HDA temperature as measured on the drives’s top  
cover does not exceed 131×F (60×C). Drive reliability and warranty will be limited  
if the drive is exposed to temperatures greater than 60×C. Figures 3-8 and 3-9 show  
airflow recommended for adequate cooling. Clearance from the drive to any other  
surface above and below the drive must be a minimum of 1.25mm (1/16 inch).  
Maxtor leaves the design and application of cooling and clearance for the disk drive  
to the User, but the drive must maintain a case temperature at or below 60×C.  
Above Unit  
Below Unit  
Figure 3-8 Lengthwise Airflow Cooling  
Maxtor Atlas 10K V 3-23  
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  
DESCRIPTION  
Non-RoHS Model Numbers:  
8D073J0  
8D073L0  
8D147J0  
8D147L0  
8D300J0  
8D300L0  
RoHS Model Numbers:  
8J073J0  
8J073L0  
8J147J0  
8J147L0  
8J300J0  
8J300L0  
Formatted Capacity  
Nominal rotational speed (rpm)  
Number of Disks  
Number of R/W heads  
Data Organization:  
Maximum BPI  
73.5 GB  
147.1 GB  
300 GB  
10,000  
10,000  
10,000  
1
2
2
4
4
8
732K  
16  
732K  
16  
732K  
16  
Zones per surface  
Track density  
102,000 TPI  
81,782  
102,000 TPI  
81,782  
102,000 TPI  
81,782  
User Data Cylinders  
Sectors per track:  
Inside zone  
624  
1114  
624  
1114  
624  
1114  
Outside zone  
Total User Sectors  
Bytes per sector  
143,666,191  
512 - 524  
PRML  
287,332,383  
512 - 524  
PRML  
585,937,500  
512 - 524  
PRML  
Recording technology  
Maximum linear density  
678 fci  
678 fci  
678 fci  
Maxtor Atlas 10K V 4-1  
 
MAXTOR  
ATLAS 10K V  
73.5 GB  
MAXTOR  
ATLAS 10K V  
147.1 GB  
MAXTOR  
ATLAS 10K V  
300 GB  
DESCRIPTION  
Maximum effective areal  
density  
2
2
2
75 Gbits/in  
75 Gbits/in  
75 Gbits/in  
Servo Mechanical Timing Specifications:  
2
Sequential Head Switch Time  
0.3 ms read  
0.3 ms read  
0.3 ms read  
0.5 ms write  
0.5 ms write  
0.5 ms write  
3
Sequential Cylinder Switch Time  
0.3 ms read  
0.3 ms read  
0.3 ms read  
0.5 ms write  
0.5 ms write  
0.5 ms write  
4
Random Average Seek (Read)  
4.0 ms typical  
4.5 ms typical  
4.2 ms typical  
4.7 ms typical  
4.4 ms typical  
4.9 ms typical  
4
Random Average Seek (Write)  
5
Full Stroke Seek (Read)  
11.0 ms  
typical  
11.0 ms  
typical  
11.0 ms  
typical  
6
SCSI ‘Hard’ Reset Time  
22 ms typical  
25 sec  
22 ms typical  
25 sec  
22 ms typical  
25 sec  
maximum  
maximum  
maximum  
7
Power on to Drive Ready  
25 sec typical  
25 sec typical  
25 sec typical  
Data transfer Rates:  
Sequential Throughput  
Read/Write  
89 MB/s  
maximum  
89 MB/s  
maximum  
89 MB/s  
maximum  
Buffer Size  
Reliability:  
8 MB  
8 MB  
8 MB  
8
8
8
8
Seek error rate  
<10 in 10  
<10 in 10  
<10 in 10  
8
15  
15  
15  
Unrecoverable error rate  
<1 in 10  
<1 in 10  
<1 in 10  
Error correction method  
(with cross check)  
48 Bytes  
Reed-Solomon  
with XCHK  
48 Bytes  
Reed-Solomon  
with XCHK  
48 Bytes  
Reed-Solomon  
with XCHK  
Contact Start/Stop Cycles  
Auto head-park method  
50,000 min.  
50,000 min.  
50,000 min.  
Magnetic Latch  
Magnetic Latch  
Magnetic Latch  
Note: Seek time is defined as the time required for the actuator to seek  
to a new position and settle on a track. It is measured by averag-  
ing the execution time of a minimum of 1000 operations of the  
indicated type as shown in Table 4-1. The seek times include  
head settling time, but do not include command overhead time,  
time spent reading or writing data, or rotational latency delays.  
Unless otherwise specified, read/seek command settling criteria  
is assumed.  
4-2 Maxtor Atlas 10K V  
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. Sequential Cylinder Switch time is the time from the conclusion of the last  
sector of a cylinder to the first logical sector on the next cylinder. It includes  
sequencer overhead for write setup on head and cylinder switch.  
4. Random LBA.  
5. Full Stroke seek is defined as a seek from cylinder 0 to maximum cylinder  
or vice versa. It may include one head switch.  
6. SCSI ‘Hard’ Reset time is the time from Reset to Selection.  
7. At power on start-up error algorithms are used. These recovery routines  
may extend the time to Drive Ready by as much as 30 seconds.  
8. Refer to Section 4.11, “DISK ERRORS” for details on error rate  
definitions.  
4.2  
FORMATTED CAPACITY  
At the factory, the Maxtor Atlas 10K V receives a low-level format that creates  
the actual tracks and sectors on the drive. Table 4-2 shows the capacity resulting  
from this process. Formatting done at the user level for operation with DOS,  
UNIX, or other operating systems, will result in less capacity than the physical  
capacity shown.  
Table 4-2 Formatted Capacity  
MAXTOR  
ATLAS 10K V  
73.5 GB  
MAXTOR  
ATLAS 10K V  
147.1 GB  
MAXTOR  
ATLAS 10K V  
300 GB  
Formatted Capacity  
73.5 GB  
147.1 GB  
300 GB  
Number of 514-524  
byte  
139,463,602  
143,666,191  
279,041,740  
287,332,383  
566,793,894  
585,937,500  
sectors available  
512 byte Sectors  
Maxtor Atlas 10K V 4-3  
 
4.3  
4.4  
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.  
TIMING SPECIFICATIONS  
Table 4-3 illustrates the timing specifications of the Maxtor Atlas 10K V hard disk  
drive.  
Table 4-3 Timing Specifications for Maxtor Atlas 10K V  
MAXTOR ATLAS 10K V 73.5/147.1/300 GB  
PARAMETER  
1
1
TYPICAL NOMINAL  
MAXIMUM  
2
Sequential Head Switch Time  
0.3 ms typical (read)  
0.5 ms typical (write)  
N/A  
3
Sequential Cylinder Switch Time  
0.3 ms typical (read)  
0.5 ms typical (write)  
N/A  
4
Random Average Seek (Read)  
<4.0/ 4.2 / 4.4 ms  
4.5 / 4.7/ 4.9 ms  
3 ms  
4.8 ms  
5.3 ms  
4
Random Average Seek (Write)  
Average Rotational Latency  
3 ms  
5
1/3 Stroke Seek (Read)  
<3 ms  
4.5 ms  
6
Full-Stroke Seek  
11.0 ms  
12.0 ms  
20 ms  
7
SCSI “Hard Reset Time”  
20 ms  
8
Power On to Drive Ready  
25 seconds  
2.5 seconds  
30 seconds  
3 seconds  
Power On to Selection  
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.  
3. Sequential Cylinder Switch Time is the time from the conclusion of the  
last sector of a cylinder to the first logical sector on the next cylinder.  
4. Random LBA.  
5. 1/3 Stroke Seek is defined as any seek of maximum length cylinder/3. 1/  
3 stroke seek may include one head switch.  
6. Full Stroke Seek is defined as a seek from cylinder 0 to maximum cylinder  
or vice versa. Full stroke may include one head switch.  
7. SCSI “Hard Reset Time” is the time from Reset to Selection.  
4-4 Maxtor Atlas 10K V  
 
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  
+5 V  
+/-10% @ Spin up, +/- 5% While running  
+/- 5%  
Allowable ripple and noise for each voltage:  
+12 V  
+5 V  
800 mV p-p (100 Hz to 8 KHz)  
450 mV p-p (8 KHz to 20 KHz)  
250 mVp-p (20KHz - 20MHz)  
250 mV p-p (100 Hz to 20MHz)  
4.5.1  
4.5.2  
Power Sequencing  
You may apply the power in any order or manner, or open either the power or  
power return line with no loss of data or damage to the disk drive. However,  
data may be lost in the sector being written at the time of power loss. The drive  
can withstand transient voltages of +10% to –10% from nominal while powering  
up or down.  
Power Reset Limits  
When powering up, the drive remains reset (inactive) until both rising Voltage  
thresholds reset limits are exceeded for 100 ms. When powering down, the drive  
resets immediately when either supply voltage drops below the falling voltage  
threshold.  
Table 4-4 Power Reset Limits1  
DC VOLTAGE  
THRESHOLD  
4.31/4.43v  
+5 V  
+12 V  
9.59/9.77v  
Maxtor Atlas 10K V 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)  
1, 4  
TYPICAL AVERAGE CURRENT  
TYPICAL AVG.  
POWER (WATTS)  
5
(AMP RMS UNLESS OTHERWISE NOTED)  
MODE OF  
OPERATION  
+12V  
+5V  
147.1  
GB  
147.1  
GB  
147.1  
GB  
73.5 GB  
300 GB  
73.5 GB  
300 GB  
73.5 GB  
300 GB  
Startup  
peak1  
1.34  
0.33  
0.75  
1.33  
0.38  
0.78  
1.57  
0.56  
0.96  
0.84  
0.81  
0.84  
0.68  
0.77  
0.80  
0.69  
0.80  
0.83  
19.7  
8.01  
19.4  
8.52  
22.41  
10.77  
15.70  
Idle2  
Max Work  
13.16  
13.32  
Note:  
1. Current is RMS except for Startup. Startup current is the peak (> 10 ms)  
current required during spindle startup. Current measurements do not  
include power required for SCSI termination.  
2. Idle mode is in effect when the drive is not reading, writing, seeking, or  
executing any commands. A portion of the R/W circuitry is powered  
down, the motor is up to speed and the Drive Ready condition exists.  
3. Max Workload: Maximum workload is defined as a random read/write  
profile with a 50% read and 50% write distribution. The transfer length is 8  
blocks (4KB), and a queue depth of 4 is used.  
4. Power requirements reflect nominal values for +12V and +5V power  
supplies.  
4-6 Maxtor Atlas 10K V  
 
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  
SOUND POWER  
(MEAN)  
SOUND POWER  
(MEAN + 3 SIGMA)  
OPERATING MODE  
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  
3.60  
3.87  
3.96  
3.72  
4.04  
4.19  
147.1 GB  
300 GB  
1. The specifications for idle and operating acoustic noise as per ISO Standard  
7779, “Engineering Methods for Free Field Conditions Over a Reflecting  
PLane.” All specifications are sound power level maximum limits, A-  
weighted, referred to 1 picowatt as indicated in the standard. The drive will  
be mounted for the test in the manufacturer’s defined nominal position.  
The unit under test should be supported so that its bottom surface in the test  
orientation is less than or equal to 6 centimeters from the chamber floor, but  
not in contact with it. The unit should be supported with small, compliant,  
well-damped blocks that rest on the floor.  
2. The relationship between bels and dBA for sound power is 1 bel = 10dBA.  
4.6.1  
Acoustic Toned Quality  
A typical drive will have no discrete tones that exceeds a tone ratio of 8dB as  
measured per ECMA 74,8th Edition, December 2003.  
Maxtor Atlas 10K V 4-7  
 
4.7  
MECHANICAL  
The Maxtor Atlas 10K V hard disk drives have the following mechanical  
characteristics:  
Height1:  
Width:  
Depth:  
1.028 in. (26.1 mm)  
4.0 in. (101.6 mm)  
5.787 in. (147.0mm)  
(820 grams)  
Weight (4-disk): 1.8 Ib  
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.8  
ENVIRONMENTAL CONDITIONS  
Table 4-7 summarizes the environmental specifications of the Maxtor Atlas 10K  
V hard disk drive.  
Table 4-7 Environmental Specifications  
PARAMETER  
OPERATING  
NON-OPERATING  
Temperature  
5° to 55°C  
-40° to 70°C  
(Non-condensing)  
(41° to 131°F)  
(-40° to 158°F)  
Maximum HDA Temperature  
60°C  
N/A  
Temperature Gradient  
(Non-condensing)  
20°C/hr maximum  
30°C/hr maximum  
1
Humidity  
5% to 95% RH  
32°C (89.6°F)  
5% to 95% RH  
46°C (114°F)  
Maximum Wet Bulb  
Temperature  
Humidity Gradient  
30% per hour  
30%per hour  
2
Altitude  
-300 m to 3,048 m  
(-1,000 to 10,000 ft.)  
-300 m to 12,000 m  
(-1,000 to 40,000 ft.)  
1. No condensation.  
2. Altitude is relative to sea level. 1,000 feet = 305 meters.  
1.  
4-8 Maxtor Atlas 10K V  
 
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  
4.10  
Sensitivity to Magnetic Fields  
The Maxtor Atlas family of drives meet 3A @ 230V / 50 Hz specification.  
SHOCK AND VIBRATION  
The Maxtor Atlas 10K V hard disk drive can withstand levels of shock and  
vibration applied to any of its three mutually perpendicular axes, or principal base  
axis, as specified in Table 4-8. A functioning drive can be subjected to specified  
operating levels of shock and vibration. When a drive has been subjected to  
specified non-operating levels of shock and vibration, with power to the drive  
off, there will be no change in performance at power on.  
When packed in its 1-pack shipping container, the Maxtor Atlas 10K V drive can  
withstand a drop from 42 inches onto a concrete surface on any of its surfaces,  
six edges, or three corners. The 20-pack shipping container can withstand a drop  
from 36 inches onto a concrete surface on any of its surfaces, six edges, or three  
corners.  
Table 4-8 Shock and Vibration Specifications  
PARAMETER  
OPERATING  
NON-OPERATING  
1
1
1
Shock linear Half Sine  
2 msec  
Read/Write  
63G/30G  
250 G  
100 G  
1
1
Shock linear Half Sine  
15 G  
7000  
1
11 msec  
Shock rotational  
25,000  
2 1  
(rad/s ) , 2 msec  
1
Vibration Swept  
1.5G 0-p 5-500 Hz  
2.0G 0-p 5–500 Hz  
Vibration Random  
(G /Hz)  
0.008 10—300 Hz  
0.0012 300—500 Hz  
0.014 10—300 Hz  
0.01 300—500 Hz  
2
Note: 1. At ambient temperature and no unrecoverable errors.  
Maxtor Atlas 10K V 4-9  
 
4.11  
RELIABILITY  
Component Life:  
Preventive Maintenance (PM): Not required  
Contact Start/Stop: 50,000 cycles at ambient,  
5 years  
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.  
Table 4-9 Error Rates  
ERROR TYPE  
Recovered read errors  
MAXIMUM NUMBER OF ERRORS  
1
12  
<10 events per 10 bits read  
2
15  
Uncorrectable read errors  
1 event per 10 bits read  
1. Recovered read errors are errors which require retries for data correction.  
Errors corrected by ECC on-the-fly are not considered recovered read  
errors. Read on arrival is disabled to meet this specification.  
2. Uncorrectable read errors are those that are not correctable using an Error  
Correcting Code (ECC), or retries within the retry limits specified in the  
mode pages. The drive terminates the command either when a repeating  
error pattern occurs, or after both the specified number of retries and  
application of triple burst error correction fail to correct the error.  
3. A seek error occurs when the actuator fails to reach or remain on the  
requested cylinder, and/or the drive requires the execution of the full  
calibration routine to locate the requested cylinder.  
4-10 Maxtor Atlas 10K V  
 
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.1  
Overview of the SCSI Command Descriptions  
The disk drives support the SCSI-3 commands listed in Table 5-1. The command  
categories are sequential, normal, and immediate.  
Immediate commands are processed when received by the drive. In most cases, these  
commands do not require drive resources, do not change the state of the drive, and  
bypass the command queue (unless the command is tagged).  
Sequential commands execute in the order that they arrive (unless accompanied by  
a HEAD OF QUEUE tag) and execute to completion before a subsequent command  
is activated.  
Normal commands are allowed to execute concurrently (with the restriction that the  
drive executes overlapping writes in the order received). Normal commands are  
usually I/O commands  
Table 5-1 Supported SCSI Commands  
Command  
CHANGE DEFINITION  
FORMAT UNIT  
Operation Code  
Category  
Sequential  
Sequential  
Immediate  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
40h  
04h  
12h  
4Ch  
4Dh  
15h  
55h  
1Ah  
5Ah  
5Eh  
INQUIRY  
LOG SELECT  
LOG SENSE  
MODE SELECT (6)  
MODE SELECT (10)  
MODE SENSE (6)  
MODE SENSE (10)  
PERSISTENT RESERVATION IN  
Maxtor Atlas 10K V  
5-1  
 
Command  
PERSISTENT RESERVATION OUT  
READ (6)  
Operation Code  
5Fh  
Category  
Sequential  
Normal  
08h  
READ (10)  
28h  
Normal  
READ BUFFER  
3Ch  
25h  
Sequential  
Immediate  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Immediate  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Sequential  
Immediate  
Normal  
READ CAPACITY  
READ DEFECT DATA (10)  
READ DEFECT DATA (12)  
READ LONG  
37h  
B7h  
3Eh  
REASSIGN BLOCKS  
RECEIVE DIAGNOSTIC RESULTS  
RELEASE  
07h  
1Ch  
17h  
RELEASE (10)  
57h  
REPORT LUNS  
A0h  
A3h  
03h  
REPORT DEVICE IDENTIFIER  
REQUEST SENSE  
RESERVE  
16h  
RESERVE (10)  
56h  
REZERO UNIT  
01h  
SEEK (6)  
0Bh  
2Bh  
1Dh  
A4h  
1Bh  
35h  
SEEK (10)  
SEND DIAGNOSTIC  
SET DEVICE IDENTIFIER  
START STOP UNIT  
SYNCHRONIZE CACHE  
TEST UNIT READY  
VERIFY  
00h  
2Fh  
WRITE (6)  
0Ah  
2Ah  
2Eh  
Normal  
WRITE (10)  
Normal  
WRITE AND VERIFY  
WRITE BUFFER  
WRITE LONG  
Normal  
3Bh  
3Fh  
Sequential  
Sequential  
Sequential  
WRITE SAME  
41h  
5-2  
Maxtor Atlas 10K V  
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.  
Maxtor Atlas 10K V  
5-3  
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 six-  
byte CDB.  
Table 5-2 Typical (6-Byte) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code  
(MSB)  
1
Reserved  
Logical Block Address  
(LBA)  
Logical Block Address  
(LBA)  
2 - 3  
4
5
Transfer Length, Parameter List Length, or Allocation Length  
Control  
Note: Reserved fields in CDBs and Parameters have a value of 0; Re-  
served fields in states and other parameters sent to an initiator are  
set to 0.  
Table 5-3 contains a description of the CDB fields.  
Table 5-4 describes the data format for a typical CDB.  
Table 5-3 Command Descriptor Block-Field Descriptions  
Field  
Operation Code  
Description  
The first byte of a SCSI CDB contains an operation code. The operation code of the CDB has  
a Group Code field (bits 7-5) and a Command Code field (bits 4-0). The 3-bit Group Code field  
provides for eight groups of command codes. The 5-bit Command Code field provides for 32  
command codes in each group. A total, therefore, of 256 possible operation codes exist. Oper-  
ation codes are defined in the SCSI command standards. The group code for CDBs specified  
therein correspond to the length of the command descriptor as below:  
Group Code  
Meaning  
0
1
2
3
4
5
6
7
6-byte commands  
10-byte commands  
10-byte commands  
Reserved  
16-byte commands  
12-byte commands  
Vendor specific  
Vendor specific  
The operation code specifies the command being requested. The list of supported SCSI com-  
mands and their operation codes are contained in Table 5-1.  
5-4  
Maxtor Atlas 10K V  
   
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 Ad-  
dress that is needed. See the specific command descriptions for more detailed information.  
Relative Addressing indicates a technique used to determine the next Logical Block Address to  
be operated on. The drive does not support Relative Addressing, it defaults to a value of 0,  
which specifies that the Logical Block Address specifies the first logical block of a range of logical  
blocks to be operated on by the command.  
Transfer Length  
The transfer length field normally specifies the number of sectors to be transferred between the  
initiator and the drive. For several commands, the transfer length indicates the number of bytes  
(not sectors) to be sent. For these commands, this field may be identified by a different name  
Commands that use one byte for the transfer length value allow up to 256 sectors of data to be  
transferred by one command. A transfer length value of 0 indicates that 256 sectors are to be  
sent. Transfer length values of 1 through 255 indicate the number of sectors to be transferred.  
Commands that use multiple bytes for the transfer length value function differently. A transfer  
length value of 0 indicates that no data transfer is to occur. Transfer length values of 1 or greater  
indicate the number of sectors to be transferred.  
Parameter List Length  
Allocation Length  
The Parameter List Length is used to specify the number of bytes sent during the data-out buffer  
transfer. This field is typically used for parameters that are sent to a drive (for example, mode,  
diagnostic, and log parameters). A parameter list length of 0 indicates that no data is to be trans-  
ferred.  
The Allocation Length field specifies the maximum number of bytes that the initiator has allo-  
cated for returned data. The Allocation Length is used to limit the amount of data returned to  
the initiator.  
An Allocation Length of 0 indicates that no data is to be transferred from the drive to the initi-  
ator. The drive terminates the data-in buffer transfer when the specified number of bytes have  
been transferred to the initiator or when all available data has been transferred, whichever is less.  
Control Field  
The Control Field is the last byte of every Command Descriptor Block; its format is shown in  
Figure 5-2 and described in Table 5-3.  
Table 5-4 Typical (6-Byte) Command Descriptor Block - Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
5
Vendor Specific  
Reserved  
NACA  
Flag  
Link  
Maxtor Atlas 10K V  
5-5  
 
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  
NACA  
Description  
These bits must be 0.  
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. If the Link bit is one and the  
flag bit is zero, and the command completes successfully, the drive will continue  
the task and return a status of INTERMEDIATE and a service response of  
Linked Command Complete.  
If the Link bit and the Flag bit of the Control word are both set to one, and the  
drive completes a command with a status of INTERMEDIATE, the drive will  
return a service response of Linked Command Complete (with Flag). Refer to  
Section 5.4 for Linked Commands description.  
Flag Bit  
The Flag bit is used in conjunction with the Link Bit to notify the initiator in  
an expedient manner that a command has been completed. Aflag bit set to 1 is  
valid only when the Link Bit is set to 1.  
5-6  
Maxtor Atlas 10K V  
 
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. This phase occurs at the end of each  
command, unless the command is terminated by one of the following events:  
• ABORT TASK SET message  
• ABORT TASK message  
• TARGET RESET message  
• CLEAR QUEUE message  
• Unexpected disconnect  
The status code is contained in bits 1 through 5 of the status byte. Bits 0, 6, and 7 are  
reserved. Table 5-6 describes the status codes returned by the drive.  
Table 5-6 Status Codes  
Status  
Definition  
GOOD  
Meaning  
00h  
02h  
The drive successfully completed the command.  
An Auto Contingent Allegiance (ACA) condition occurred.  
CHECK CONDITION  
The drive cannot service the command at the moment, and its Com-  
mand Descriptor Block has been discarded. The initiator can retry the  
command at a later time. This status is returned when:  
A non-tagged command is received and the logical unit's com-  
mand queue is full (all internal command buffers are in use).  
A disconnect privilege was not granted in the IDENTIFY mes-  
sage of a queue-tagged I/O process (Parallel SCSI).  
A disconnect privilege was not granted in the IDENTIFY mes-  
sage of a non-tagged I/O process and a command from another  
initiator is currently active (Parallel SCSI)  
08h  
BUSY  
A command is received while an auto-contingent allegiance  
condition exists for another initiator.  
This status is returned for every command (except the last) in a series  
of linked commands that was successfully completed. However, if the  
command is terminated with other that GOOD status (such as  
CHECK CONDITION, RESERVATION CONFLICT, OR  
BUSY), the INTERMEDIATE status is not returned and the series of  
linked commands and the task is ended.  
10h  
INTERMEDIATE  
Another initiator has reserved the drive. (This status is never returned  
for INQUIRY or REQUEST SENSE commands.)  
18h  
28h  
RESERVATION CONFLICT  
TASK SET FULL  
The drive cannot service the command at the moment, and its Com-  
mand Descriptor Block has been discarded. (Returned for a tagged  
command when all of the drive's internal command buffers are in use,  
or when a host sends a tagged command while an Auto Contingent  
Allegiance condition is pending for that initiator)  
5.4  
Linked Commands  
An I/O Process (task) may contain multiple commands that are linked together. The  
initiator communicates this condition of linked (or unlinked) commands by setting (or  
clearing) the Link bit of the Command Descriptor Block’s control word. A linked  
Maxtor Atlas 10K V  
5-7  
   
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.  
All commands in a linked chain are addressed to the same nexus and are part of a single  
task (I/O process). The drive defers any commands that are not part of the linked chain  
until the chain is complete. The last command in the chain has the Link bit cleared.  
Note: Relative addressing is not supported by the Atlas 10K disk drive.  
5-8  
Maxtor Atlas 10K V  
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.  
Block field used by the drive to determine how much command-related data are to  
be transferred. The units (bytes or logical blocks) for the different Length fields are  
implied by the Length Field Name as shown in Table 5-7:  
Table 5-7 Length Fields  
Field Name  
Allocation Length  
Units Implied  
Bytes of data the drive is allowed to send to the initiator  
Bytes of data the initiator has available for the drive  
Logical data sectors the initiator wants transferred or verified  
Bytes of data the initiator wants transferred  
Parameter List Length  
Transfer Length  
Byte Transfer Length  
The DATA OUT column in Table 5-8 lists the information passed to the drive by the  
initiator as part of the command. The DATA IN column lists the information sent to  
the initiator by the drive.  
Numbers in parentheses after an item indicate the item’s length in bytes. In some cases,  
additional length information is communicated during the DATA phase. For example,  
a FORMAT UNIT Defect List Header contains a Defect List Length field that  
contains the total length of the Defect Descriptors that follow the Defect List Header.  
Table 5-8 does not include these cases.  
Table 5-8 DATA-Phase Command Contents  
Command  
Length in CDB  
Data Out (To Drive)  
Data In (To Initiator)  
CHANGE  
DEFINITION  
0
--  
--  
Defect List Header  
FORMAT UNIT  
INQUIRY  
0
Initialization Pattern (6-8)  
Defect Descriptors  
Standard Inquiry or a Vital Product  
Data page  
Allocation  
---  
Parameter List  
(must be 0)  
LOG SELECT  
LOG SENSE  
--  
--  
Allocation  
---  
Log Page  
Mode Parameter Header (4  
Block Descriptor (8  
Page(s))  
Parameter List  
MODE SELECT  
--  
Allocation  
Transfer  
---  
MODE SENSE  
Block Descriptor (8)  
PERSIST. RES. IN  
PERSIST. RES.  
OUT  
READ (6) (10)  
---  
Data  
Maxtor Atlas 10K V  
5-9  
   
Command  
READ BUFFER  
READ CAPACITY  
Length in CDB  
Data Out (To Drive)  
Data In (To Initiator)  
READ BUFFER Header (4)  
Mode-zero Buffer (512) or  
Section of Drive’s DRAM or  
READ BUFFER Desc. (4)  
Allocation  
---  
Allocation  
Allocation  
---  
---  
READ CAPACITY data (8)  
READ DEFECT  
DATA  
• Defect List (Hdr) (4)  
• Defect Descriptors  
• Data (512)  
• LBA Tag (2)  
• EDC (2)  
• ECC (60)  
• Fill (2)  
Byte Transfer  
(Must be 578)  
READ LONG  
---  
REASSIGN  
BLOCKS  
0
Defect List Header(4)  
Defect Descriptors  
Diagnostic Page  
RECEIVE  
DIAGNOSTIC  
RESULTS  
Allocation  
0
---  
---  
RELEASE  
---  
REPORT DEVICE  
IDENTIFIER  
REQUEST SENSE  
Allocation  
---  
---  
Sense Data (18)  
---  
0
(Extent List  
Option not  
supported)  
RESERVE  
REZERO UNIT  
Command  
0
---  
Data Out (To Drive)  
---  
---  
Length in CDB  
0
Data In (To Initiator)  
SEEK (6)(10)  
---  
---  
SEND DIAGNOS-  
TIC  
Parameter List  
Diagnostic Page  
SET DEVICE  
IDENTIFIER  
START STOP UNIT  
0
0
---  
---  
---  
---  
SYNCHRONIZE  
CACHE  
TEST UNIT READY  
VERIFY  
0
---  
---  
---  
---  
Transfer  
Transfer  
Data  
Data  
WRITE (6)(10)  
WRITE AND VERI-  
FY  
Transfer  
Data  
---  
---  
Zeros (4)  
Mode-zero buffer (512)  
or Data to put into DRAM  
or Microcode image  
or Microcode image  
(successive 16 KB pieces)  
Parameter List  
WRITE BUFFER  
5-10  
Maxtor Atlas 10K V  
Command  
Length in CDB  
Data Out (To Drive)  
Data In (To Initiator)  
• Data (512)  
• LBA Tag (2)  
• EDC (2)  
• ECC (60)  
• Fill (2)  
Byte Transfer  
(must be 578)  
WRITE LONG  
--  
0
Data (1 logical sector)  
WRITE SAME  
5.6  
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.  
The commands are presented in alphabetic order, and each command starts on a new,  
odd-numbered page.  
Common Fields  
Several fields that are common to many commands are described here, rather than  
being repeated throughout the descriptions. These fields include:  
Reserved – Reserved bits, fields, bytes, and code values are set aside for future  
standardization and must be set to 0. If the drive receives a command that contains  
non-0 bits in a reserved field or a reserved code value, the command is terminated with  
a CHECK CONDITION status and the sense key set to ILLEGAL REQUEST.  
However, there are some fields that are not checked for compatibility with older SCSI  
initiators.  
Control – The Link Bit and Flag Bit are supported.  
RelAdr – Not supported; must be 0.  
Maxtor Atlas 10K V  
5-11  
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.  
Table 5-9 CHANGE DEFINITION Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
Operation Code (40h)  
Reserved  
Reserved  
Save  
Rsv’d  
New Operating Definition  
(0, 1, 2, 3, 4, 5 and 6 are legal values for Parallel SCSI Disk Drives)  
4 - 7  
Reserved  
Parameter Data Length  
Control  
8
9
Table 5-10 CHANGE DEFINITION-Field Descriptions  
Field  
Description  
Save Parameters. When this field is set to 1, the new op-  
erating definition is saved in the drive's non-volatile  
memory.  
Save  
The values that can be supplied in the field are listed be-  
low:  
0 Current Definition  
1 SCSI-1  
New Operating Definition  
Parameter Data Length  
2 SCSI-1/CCS (Common Command Set)  
3 SCSI-2  
4 SCSI-3  
5 SCSI-3 U160  
6 SCSI-3 U320  
Length, in bytes, of the parameter data.  
Must be 0.  
5-12  
Maxtor Atlas 10K V  
   
5.8  
FORMAT UNIT Command (04h)  
The FORMAT UNIT command formats the disk's storage media into initiator-  
addressable 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.  
The FORMAT UNIT command updates the defective sector list, referred to as the  
Grown Defect List, that is maintained by the drive. As described below, the drive gives  
the initiator considerable control over this list. If certification is enabled, all initiator-  
addressable logical blocks are verified, and bad sectors are reassigned and added to the  
Grown Defect List.  
Note: During FORMAT UNIT command processing, the drive ig-  
nores the Read/Write AWRE and ARRE bits (from Error Re-  
covery Mode page) and does auto-revectoring as needed.  
The drive is physically formatted when it leaves the manufacturing facility. Therefore,  
it is not necessary to reformat the drive before using it. If the logical sector size of the  
drive is changed using the Block Descriptor of the MODE SELECT Command, it is  
recommended (but not necessary) to reformat the drive.  
The Immed bit that can be included in the FORMAT UNIT command parameter  
list allows the initiator to control whether the drive returns completion status either  
after fetching and validating the Command Descriptor Block and parameter list or  
after the FORMAT UNIT command completes. The FORMAT UNIT command  
parameters are described in Table 5-11 and Table 5-12  
The time required for the FORMAT UNIT command to format the disk primarily  
depends on the capacity of the drive. The number of defects detected and the number  
of defects already in the Primary and Grown Defect Lists also influence the time  
required to format the drive. If the Disable Certification bit is set to 1, formatting time  
is reduced.  
Defective sectors on the drive are managed through two lists: the Primary Defect List  
and the Grown Defect List. The Primary Defect List is created when the drive is  
manufactured and is the drive's initial defect list. The Primary Defect List is not  
affected by the FORMAT UNIT command. Sectors listed in it are revectored by the  
drive. The Grown Defect List contains a list of the sectors that have gone bad since  
the drive's primary list was generated.  
Defects are communicated in a data structure referred to as a Defect Descriptor. The  
SCSI specification defines several Defect Descriptor formats. The FORMAT UNIT  
command recognizes defect descriptors in Block format, Bytes From Index format,  
and Physical Sector format. (There is one exception: a value of FFFFFFFFh in either  
the defect Bytes From Index field or the Defective Sector Number fields is ignored).  
Maxtor Atlas 10K V  
5-13  
Table 5-11 FORMAT UNIT Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (04h)  
Reserved  
Fmt Data  
Cmp  
List  
Defect List Format  
2
3 - 4  
5
Vendor-Specific  
Interleave  
Control  
Table 5-12 FORMAT UNIT Command-Field Descriptions  
Field  
Description  
Format Data. When the Format Data value is 1, it indicates that a data-out buffer transfer  
occurs as part of the command execution. The FORMAT UNIT Parameter list (consist-  
ing of a Defect List Header and, optionally, a number of Block Format Defect Descrip-  
tors) is passed to the device during this phase.  
FmtData  
When the Format Data value is 0, the data-out buffer transfer does not occur.  
Complete List. When the Complete List value is 1, the drive deletes its current Grown  
Defect List and starts a new one, containing the Logical Block Numbers listed in the de-  
fect list supplied by the initiator during this format operation are added to the list, cre-  
ating a new Grown Defect List.  
CmpLst  
When the Complete List value is 0, the drive adds initiator-supplied and newly found  
defective Logical Block Numbers to the existing Grown Defective List.  
The Defect List Format value specifies the defect descriptor passed by the initiator to  
the drive when the Format Data value is 1. Acceptable values are:  
000b (Block [or Sector] Format)  
Defect List Format  
100b (Index Format)  
101b (Physical Sector Format)  
Vendor-Specific  
Interleave  
Not supported. Must be 0.  
Not supported. Ignored by the drive.  
5-14  
Maxtor Atlas 10K V  
   
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. Table 5-13 describes the  
contents of the Grown Defect List after FORMAT UNIT command execution.  
Table 5-13 FORMAT UNIT Command Supported Options  
Defect  
Contents of Grown Defect List after FORMAT UNIT  
FmtDat  
CmpLst  
List  
Command Execution  
Length  
All sectors found to be bad, but not listed in the Primary Defect List or  
Grown Defect List, are added to the Grown Defect List.  
0
1
0
0
N/A  
0
Same as above.  
The existing Grown Defect List is discarded. A new Grown Defect List is  
generated, containing All sectors found to be bad, but not listed in the Pri-  
mary Defect List.  
1
1
0
The Grown Defect List contains:  
Original Grown Defect List  
All sectors found to be bad, but not listed in the Primary Defect List.  
A list of sectors supplied by the initiator. These sectors are passed in defect  
descriptors in the data-out buffer transfer that occurs as part of the FOR-  
MAT UNIT command.  
1
1
0
1
>0  
>0  
Same as the case above, except that the current Grown Defect List is dis-  
carded before formatting begins.  
5.8.2  
FORMAT UNIT Parameter List  
The FORMAT UNIT Parameter List (Table 5-14) consists of a Defect List Header  
(Table 5-15) followed by one or more Defect Descriptors. Descriptors are either four  
bytes or eight bytes in length.  
Table 5-14 FORMAT UNIT Parameter List-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 - 3  
Defect List Header  
Initialization Pattern Descriptor (if any)  
Defect Descriptors (if any)  
Maxtor Atlas 10K V  
5-15  
   
5.8.2.1  
FORMAT UNIT Defect List Header  
The FORMAT UNIT Defect List Header (Table 5-15) provides several optional  
format control bits to give the initiator more control over the defect lists. Table 5-16  
provides descriptions of the data fields in the Defect List Header  
Table 5-15 .FORMAT UNIT Defect List Header-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Reserved  
STPF  
FOV  
DPRY  
DCRT  
IP  
DSP  
Immed  
VS  
2-3  
Defect List Length  
Table 5-16 FORMAT UNIT Defect List Header-Field Descriptions  
Name  
Description  
The Format Options Valid bit indicates that the remaining option bits in this byte are valid.  
If this bit is not set, the remaining bits, except Immed, are ignored.  
FOV  
The Disable Primary bit specifies whether the drive should ignore the Primary Defect List  
during the format to identify defective areas on the media. The drive's default is 0, indicating  
that the drive should replace sectors found in the Primary Defect List during the format.  
DPRY  
DCRT  
The Disable Certification bit specifies whether the drive should certify the media during the  
format. The drive’s default is 0, indicating that the drive should certify the media.  
The Stop Format bit specifies the error conditions under which the drive is to terminate the  
format. The state of the bit is ignored and the drive acts as if this bit is set. If either the Grown  
Defect List or the Primary Defect List is not found, the format operation terminates with a  
CHECK CONDITION status and a sense key of MEDIUM ERROR  
STPF  
The Initialization Pattern bit signals the drive that the FORMAT UNIT Parameter List con-  
tains initialization pattern information.  
An Initialization Pattern bit of 1 indicates that an initialization pattern descriptor (Table 5-  
17) is included in the FORMAT UNIT parameter list immediately following the Defect List  
Header.  
IP  
An Initialization Pattern bit of 0 indicates that an initialization pattern descriptor (Table 5-  
17) is not included in the FORMAT UNIT parameter list, and the drive will use its default  
initialization pattern of all zeros.  
The Disable Saving Parameter prohibits the drive from preserving MODE SELECT param-  
eters received while the Format is in progress. This bit is ignored, and the drive acts as if it  
were set.  
DSP  
When the Immediate bit is 0, the drive returns a status after the format operation completes.  
If the disconnect privilege is granted in the accompanying IDENTIFY message, the drive dis-  
connects from the bus after fetching and validating the Command Descriptor Block and the  
FORMAT UNIT Parameter List. If the disconnect privilege is not granted, the drive stays  
connected to the bus during the entire FORMAT UNIT command. When the Immediate bit  
is set to 1, the drive returns a status after the Command Descriptor Block and FORMAT  
UNIT Parameter List have been fetched and validated. In this case, the drive ignores the  
IDENTIFY message's disconnect privilege bit and remains connected to the bus while it val-  
idates the Command Descriptor Block and Parameter List. It returns the completion status  
before it disconnects. The drive then proceeds with the format.  
Immed  
VS  
Vendor-specific. Must be 0.  
Gives the length in bytes of the Defect Descriptors that follow. A value of 0 is valid and  
means that no Defect Descriptors follow. A CHECK CONDITION status is returned if this  
value is not a multiple of the defect descriptor size. The Defect List Length is equal to four  
times the number of defect descriptors if Block format is used, or eight times if Bytes From  
Index format or Physical Sector format is used.  
Defect List Length  
5-16  
Maxtor Atlas 10K V  
   
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
4
3
2
1
0
0 - 3  
Defective Block Address  
5.8.2.3  
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. The Bytes From Index defect descriptor specifies the location of a defect  
that is no more than eight bytes long.  
Each descriptor is comprised of the bytes shown in Table 5-18. The Cylinder Number  
of Defect is the most significant part of the address, and the Defective Sector Number  
or Defect Bytes From Index is the least significant part of the address. A value of  
FFFFFFFFh in bytes 4 to 7 is ignored  
Table 5-18 FORMAT UNIT Defect Descriptor- Physical Sector and Bytes  
From Index Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 - 2  
3
Cylinder Number of Defect  
Head Number of Defect  
Defective Sector Number  
or  
Defect Bytes from Index  
4 - 7  
5.8.2.4  
FORMAT UNIT Initialization Pattern Descriptor  
The Initialization Pattern option specifies that the logical blocks on the drive medium  
will contain a specified initialization pattern. The Initialization Pattern descriptor is  
sent to the drive as part of the FORMAT UNIT parameter list. Table 5-19 describes  
the Initialization Pattern descriptors. The contents of the descriptor fields are described  
Table 5-19 FORMAT UNIT Initialization Pattern Descriptor-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
IP Modifier = 0  
Reserved  
1
IP Type  
IP Length  
IP  
2 - 3  
4 - n  
Maxtor Atlas 10K V  
5-17  
     
Table 5-20 FORMAT UNIT Initialization Pattern Descriptor-Field Descriptions  
Name Description  
The Initialization Pattern Modifier must be 0.  
IP Modifier  
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.  
The Initialization Pattern Length field indicates the number of bytes contained in the Ini-  
tialization Pattern. The valid lengths (when IP Type = 1) are two or four bytes.  
IP Length  
IP  
Initialization Pattern.  
Table 5-21 FORMAT UNIT Initialization Pattern Type  
Initialization Pattern Type  
Description  
1
00h  
01h  
Use default pattern.  
2
Repeat the initialization pattern as required to fill the logical sector.  
Reserved.  
3
02h – FFh  
NOTES:  
1. If the Initialization Pattern Length is not 0, the drive terminates the command with  
CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST, and  
the additional sense code is set to INVALID FIELD IN PARAMETER LIST.  
2. If the Initialization Pattern Length is 0, the drive terminates the command with  
CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST, and  
the additional sense code is set to INVALID FIELD IN PARAMETER LIST.  
3. If the Initialization Pattern Type is not 0 or 1, the drive terminates the command  
with a CHECK CONDITION status. The Sense Key is set to ILLEGAL  
REQUEST, and the Additional Sense Code is set to INVALID FIELD IN  
PARAMETER LIST.  
5-18  
Maxtor Atlas 10K V  
   
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  
The drive can provide two categories of data in response to an INQUIRY command:  
Standard Inquiry Data and Vital Product Data. Standard Inquiry Data contains basic  
data about the drive, and Vital Product Data comprises several pages of additional data.  
Each Vital Product Data page requires a separate INQUIRY command from the  
initiator.  
An INQUIRY command is not affected by, nor does it clear, a Unit Attention  
condition.  
Table 5-22 INQUIRY Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
4
5
Operation Code (12h)  
Reserved  
CmdDt  
EVPD  
Page Code or Operation Code  
Reserved  
Allocation Length  
Control  
Table 5-23 INQUIRY Command Descriptor Block-Field Descriptions  
Field  
Description  
Command Support Data. If CmdDt = 0 and EVPD (see below) = 0, the drive returns the  
Standard Inquiry Data. If CmdDt = 1 with EVPD = 0, the drive returns the Command Data  
specified by Page Code/Operation.  
CmdDt  
Enable Vital Product Data. If EVPD = 0 and CmdDt (see above) = 0, the drive returns the  
Standard Inquiry Data. If EVPD = 1and CmdDt = 0, the drive returns the Vital Product  
Data Page specified by Page Code/Operation Code.  
EVPD  
Specifies the Vital Product Data Page or Command Support Data which is to be returned  
by the drive when EVPD is set. Specifies the SCSI Operation Code for command support  
data to be returned by the drive when CmdDt is set. A CHECK CONDITION status is re-  
turned if this field specifies an unsupported Page or Operation Code or if both EVPD and  
CmdDt are set. Table 5-27 lists the Page Codes for the Vital Product Pages supported by  
the drive. Table 5-37 lists the operation codes for the CmdDt information supported by the  
drive.  
Page Code or  
Operation Code  
Specifies the number of bytes of inquiry information the drive is allowed to return to the  
initiator during the command's data-in buffer transfer. Error status is not returned if the  
value in this field truncates the requested information.  
Allocation Length  
Maxtor Atlas 10K V  
5-19  
   
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  
Table 5-24 Standard Inquiry Data Page-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
Peripheral Device Type = 0  
(Direct Access Device)  
0
1
2
3
Peripheral Qualifier = 0  
RMB =  
Device Type Modifier = 0  
0
ANSI Version = 3  
(SCSI-3)  
ISO Version = 0  
ECMA Version = 0  
Norm  
ACA  
AERC  
TrmTsk  
Rsv’d  
Response Data Format = 2  
4
5
Additional Length = 5Bh  
Reserved  
Obsolete  
Obsolete  
Obsolete  
6
7
Rsv’d  
Rsv’d  
Port  
MultiP  
Sync  
Mchngr  
Linked  
Addr16  
SftRe  
Cmd  
Que  
Obsolete  
RelAdr  
Wbus16  
8 - 15  
16 - 31  
32 - 35  
36 - 47  
48 - 51  
52 - 53  
54  
Vendor Identification “MAXTOR”  
Product Identification  
Product Revision Level  
Drive Serial Number  
Reserved  
SCSI Hardware Revision Number  
Disk Controller Hardware Revision Number  
Electronics Pass Number  
55  
56  
Reserved  
Clocking  
QAS  
IUS  
57 - 95  
Reserved  
5-20  
Maxtor Atlas 10K V  
 
Table 5-25 Standard Inquiry Data Page-Field Descriptions  
Description  
Field Name  
Peripheral Qualifier  
Peripheral Device  
ANSI Version  
AERC  
Value  
0
0
Non-zero if initiator selects an invalid logical unit.  
0 indicates that this is a Direct Access Device.  
ANSI SCSI Level 3 (SCSI-3) is supported.  
Asynchronous Event Reporting is not supported.  
Does not support setting NACA in CDB Control word.  
Only used when MultiP = 1.  
3
0
NormACA  
Port  
0
0
MultiP  
0
This field set to 1 if it is a multiport device.  
Not embedded in or attached to a medium changer  
16-bit wide SCSI address  
Mchngr  
0
Addr16  
0/1  
0
TrmTSK  
TERMINATE TASK Function is not supported  
Response Data  
Format  
2
0
This Standard Inquiry Data is in the format specified in the International Standard.  
Relative Addressing is not supported.  
RelAdr  
The WBus bit is 1 if the drive supports 16-bit data transfer. The bit is 0 if the drive only  
supports 8-bit transfer.  
WBus 16  
0 or 1  
Sync  
Linked  
CmdQue  
1
1
1
The drive supports Synchronous Data Transfers.  
Linked Commands are supported.  
The drive supports Tagged Command Queuing  
The drive implements the hard reset option in response to assertion of the SCSI Bus reset  
line.  
SftRe  
VS  
0
0
Vendor Specific  
The  
ATLAS10K5_73WLS, ATLAS10K5_147WLS, ATLAS10K5_300WLS  
Product  
Identification  
value in  
this field  
is:  
ATLAS10K5_73SCA, ATLAS10K5_147SCA, ATLAS10K5_300SCA  
The contents of this field define the setting of the double-edge clocking option (See Chap-  
ter 6). Note that the clocking field does not apply to asynchronous transfers of data. Op-  
tions available are:  
Clocking  
11  
Code  
Description  
00b  
Indicates the device server supports only Single Transition  
(ST)  
01b  
Indicates the device server supports only Double Transition  
(DT)  
Reserved  
10b  
11b  
Indicates the device server supports ST and DT  
Quick Arbritrate Support. If the value of this field is 1, it indicates that the device server  
supports the quick arbitrate feature. A value of 0 indicates that the device server does not  
support this feature. 1 is default setting.  
QAS  
IUS  
1 (U160)  
1 (U320)  
Information Unit Supported. If the value of this field is 1, it indicates that the device server  
supports information units. A value of 0 indicates that the device server does not support  
information units. Default is 1.  
Note: Vendor Information, Product Identification, and Product  
Revision Level are returned as shown in Table 5-22.  
Maxtor Atlas 10K V  
5-21  
 
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.  
Table 5-26 Supported Vital Product Data Pages -Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Peripheral Qualifier  
= 0  
Peripheral Device Type = 0  
(Direct Access Device)  
1
2
Page Code (00h)  
Reserved  
3
Page Length = 08h  
Supported Page List  
4 - 10  
Table 5-27 Vital Product Data-Page Codes  
Page Code  
Description  
Size In Bytes  
00h  
80h  
81h  
82h  
83h  
Supported Vital Product Pages Page  
Unit Serial Number Page  
11  
12  
11  
32  
40  
Implemented Operating Definition Page  
ASCII Implemented Operating Page  
Device Identification Page  
5.9.2.2  
Unit Serial Number Page (80h)  
The Unit Serial Number page contains the drive's PCB Serial Number (Table 5-28)  
and the HDA Serial Number (Table 5-29).  
Table 5-28 Unit Serial Number Page-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
Peripheral Qualifier  
= 000b  
Peripheral Device Type = 000h  
(Direct Access Device)  
0
1
2
Page Code (80h)  
Reserved  
3
Page Length = 08  
HDA Serial Number  
4 - 11  
Table 5-29 Unit Serial Number Page-Field Descriptions  
Field Definition  
HDA Serial Number An 8-character ASCII representation of the drive’s HDA serial number  
5-22  
Maxtor Atlas 10K V  
       
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.  
Table 5-30 Implemented Operating Definition Page-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Peripheral Qualifier  
= 0  
Peripheral Device Type = 0  
(Direct Access Device)  
1
2
3
4
5
Page Code (81h)  
Reserved  
Page Length = 07h  
Rsvd  
Current Definition  
SavImp  
= 1  
Default Definition is SCSI-2 U160 (04h)  
Supported-1 Definition is SCSI-3 U320 (06h)  
Supported-2 Definition is SCSI-3 U160 (05h)  
Supported-3 Definition is SCSI-2 U160 (04h)  
Supported-4 Definition is SCSI-2 U80 (03h)  
Supported-5 Definition is SCSI-1-CCS (02h)  
6
7 *  
8
SavImp  
= 1  
SavImp  
= 1  
SavImp  
= 1  
9
SavImp  
=1  
10  
SavImp  
=1  
Table 5-31 Implemented Operating Definition Page-Field Descriptions  
Field  
Definition  
Save Implemented. If = 0, this bit indicates that the  
corresponding operation definition cannot be saved.  
When = 1, this bet indicates that the corresponding  
operating definition can be saved.  
SavImp  
Maxtor Atlas 10K V  
5-23  
   
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, SCSI-  
2, SCSI-1/CCS” in bytes 5 through 31 for Parallel SCSI. This is described in Table  
Table 5-32 ASCII Implemented Operating Definition Page - Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Peripheral Qualifier = 0  
Peripheral Device Type = 0  
(Direct Access Device)  
1
Page Code (82h)  
Reserved  
2
3
Page Length = 1Ch  
ASCII String Length = 1Bh  
4
5 - 31  
“SCSI-3, SCSI-2, SCSI-1/CCS” + byte of 0  
5.9.2.5  
Device Identification Page (83h) (SCSI-3 ONLY)  
The Device Identification Page provides the means to retrieve zero or more  
identification descriptors that apply to the logical unit (Table 5-33 and Table 5-34).  
Table 5-33 Device Identification Page - Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
Peripheral Qualifier  
(0)  
Peripheral Device Type (0)  
(Direct Access Device)  
0
1
Page Code (83h)  
Reserved  
2
3
Page Length (24h for SCSI)  
4
5
Reserved  
Reserved  
Code Set (1)  
Association (0)  
Reserved  
Identifier Length (8h)  
EUI-64 (Value Stored in Configuration Page 30h)  
Reserved Code Set (2)  
Association (0) Identifier Type (1)  
Reserved  
Identifier Type (2)  
6
7
8 – 15  
16  
17  
Reserved  
18  
19  
Identifier Length (14h)  
Vendor Identifier (“Maxtor “)  
Drive Serial Number  
20 – 27  
28 – 39  
5-24  
Maxtor Atlas 10K V  
   
Table 5-34 Device Identification Page - Field Description  
Field  
Definition  
This field specifies the code set used for the Identifier field. Applicable values are:  
Value Description  
0h Reserved  
Code Set  
1h The Identifier field contains binary values  
2h The Identifier field contains ASCII graphic codes (code values 20h through 7Eh)  
3h – Fh Reserved  
This field specifies the entity with which the Identifier field is associated. Applicable  
values are:  
Value Description  
Association  
0h The Identifier field is associated with the addressed physical or logical device.  
1h The identifier field is associated with the port that received the request.  
2h – 3h Reserved  
This field specifies the format and assignment authority for the identifier. Values in  
this field are:  
Value Description  
0h No assignment authority was used; there is no guarantee that the identifier is glo-  
bally unique (vendor-specific).  
1h The first 8 bytes of the Identifier field represent the Vendor ID.  
2h The Identifier field contains an IEEE Extended Unique Identifier, 64-bit (EUI-64).  
The Identifier Length field (Byte 7) is set to 8.  
Identifier Type  
3h Not applicable; for Fibre Channel devices.  
4h Not applicable; if the Association value = 1h, the value of the Identifier contains a  
4-byte, binary number that identifies the port relative to the other ports in the device.  
5h - Fh Reserved  
5.9.2.6  
Command Support Data Pages  
An application client can request command support data by setting the CmdDt bit of  
the INQUIRY command to 1, and specifying the SCSI operation code of the  
Command Descriptor Block (CDB) for which it wants information.  
Format of the command support data and definitions of the fields follow in Table 5-  
Table 5-35 Command Support Data Page-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Peripheral Qualifier  
= 0  
Peripheral Device Type = 0  
(Direct Access Device)  
1
2
Reserved  
Support  
ANSI-Approved Version  
ISO Version  
ECMA Version  
3 – 4  
5
Reserved  
CDB Size (m – 5)  
(MSB)  
6 – m  
CDB Usage Data  
(LSB)  
Maxtor Atlas 10K V  
5-25  
   
Table 5-36 Command Support Data Page-Field Descriptions  
Field  
Description  
The value of the Support field describes the type of support that the disk drive provides for Com-  
mand Support Data.  
Support  
Value  
Description  
Data about the requested SCSI operation code is not currently avail-  
able. In this case, all data after Byte 1 is undefined.  
000b  
The device does not support the SCSI operation code requested. In  
this case, all data after Byte 1 is undefined  
001b  
010b  
011b  
100b  
101b  
Reserved  
The device supports the SCSI operation code in conformance with  
the SCSI standard.  
Vendor-Specific  
The device supports the SCSI operation code, but in a vendor-spe-  
cific manner  
110b  
111b  
Vendor-Specific  
Reserved  
ISO-Version  
Must be 0.  
ECMA-Version  
Must be 0.  
ANSI-Approved  
Version  
Minimum operating definition for supported command.  
CDB Size  
This field contains the number of bytes in the CDB for the Operation Code being requested and  
the size of the CDB Usage Data in the data that is returned in response to the INQUIRY.  
This field contains information about the CDB for the Operation Code being queried. Note that  
the first byte of the CDB Usage Data contains the OpCode for the operation specified. All of the  
other bytes of the CDB Usage Data contain a map for bits in the CDB of the OpCode specified.  
CDB Usage Data  
Note: The bits in the map have a 1-to-1 correspondence to the CDB for the OpCode being queried. That is, if the  
device senses a bit as the entire field or as part of the field of the operation, the map in CDB Usage Data contains  
a 1 in the corresponding bit position. If the device ignores a bit or declares a bit as “reserved” in the CDB for  
the OpCode being queried, the map has a 0 in that corresponding bit position. Refer to Table 5-36 for a list  
of the data returned for each of the OpCode values that can be sent in the INQUIRY command.  
5-26  
Maxtor Atlas 10K V  
 
Table 5-37 Command Support Data Page Command or Operation Codes  
Hex Data Returned When INQUIRY is Received and CmdDt Bit  
= 1  
ANSI  
Version  
CDB  
Length  
CDB Size Usage  
Data  
OpCode  
Command  
Support  
00h  
01h  
03h  
04h  
TEST UNIT READY  
REZERO UNIT  
03  
03  
03  
03  
01  
01  
01  
01  
06  
06  
06  
06  
00E000000003  
01E000000003  
03E00000FF03  
04FFFFFFFF03  
REQUEST SENSE  
FORMAT UNIT  
REASSIGN  
BLOCKS  
07h  
03  
01  
06  
070E00000003  
08h  
0Ah  
0Bh  
12h  
READ (6)  
WRITE (6)  
SEEK (6)  
INQUIRY  
03  
03  
03  
03  
01  
01  
01  
01  
06  
06  
06  
06  
08FFFFFFFF03  
0AFFFFFFFF03  
0BFFFFFF0003  
12E3FF00FF03  
MODE  
SELECT (6)  
15h  
03  
01  
06  
15F10000FF03  
16h  
17h  
1Ah  
1Bh  
RESERVE (6)  
RELEASE (6)  
03  
03  
03  
03  
01  
01  
01  
01  
06  
06  
06  
06  
16FEFFFFFF03  
17FEFF000003  
1AE8FF00FF03  
1BE100000103  
MODE SENSE (6)  
START STOP UNIT  
REC. DIAG.  
RESULTS  
1Ch  
1Dh  
25h  
28h  
2Ah  
2Bh  
2Eh  
2Fh  
35h  
37h  
3Bh  
3Ch  
3Eh  
3Fh  
03  
03  
03  
03  
03  
03  
03  
03  
03  
03  
03  
03  
03  
03  
01  
01  
01  
01  
01  
01  
01  
01  
01  
01  
01  
01  
01  
01  
06  
06  
1CE1FFFFFF03  
1DF700FFFF03  
END  
DIAGNOSTIC  
READ  
CAPACITY  
25E0FFFFFFFF0000  
0103  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
0A  
28F8FFFFFFFF00FF  
FF03  
READ (10)  
WRITE (10)  
SEEK (10)  
2AF8FFFFFFFF00F  
FFF03  
2BE0FFFFFFFF000  
00003  
WRITE AND  
VERIFY  
2EF2FFFFFFFF00F  
FFF03  
2FF2FFFFFFFF00FF  
FF03  
VERIFY  
35E0FFFFFFFF00FF  
FF03  
SYNCH. CACHE  
READ DEFECT  
DATA  
37E01F00000000FF  
FF03  
WRITE  
BUFFER  
3BEFFFFFFE00FFF  
FFF03  
3CEFFFFFFFFFFFF  
FFF03  
READ BUFFER  
READ LONG  
WRITE LONG  
3EE2FFFFFFFF00F  
FFF03  
3FE0FFFFFFFF00F  
FFF03  
Maxtor Atlas 10K V  
5-27  
 
Hex Data Returned When INQUIRY is Received and CmdDt Bit  
= 1  
40E0017F000000000  
40h  
41h  
CHANGE DEF.  
WRITE SAME  
03  
03  
01  
01  
0A  
0A  
003  
41E2FFFFFFFF00FF  
FF03  
4CE3C000000000FF  
FF03  
4Ch  
4Dh  
LOG SELECT  
LOG SENSE  
03  
03  
01  
01  
0A  
0A  
4DE1FF00000000FF  
FF03  
55h  
56h  
57h  
5Ah  
5Eh  
5Fh  
A0h  
MODE SELECT (10)  
RESERVE (10)  
03  
03  
03  
03  
03  
03  
03  
01  
03  
03  
01  
03  
03  
03  
0A  
0A  
0A  
0A  
0A  
0A  
0C  
55100000000000FFF  
F03  
5610FFFF000000FF  
FF03  
RELEASE (10)  
5710FFFF000000FF  
FF03  
MODE SENSE (10)  
5AE8FF00000000FF  
FF03  
PERSIST.  
RES. IN  
5E1F0000000000FF  
FF03  
PERSIST.  
RES. OUT  
5F1FFF00000000FF  
FF03  
REPORT LUNS  
A00000000000FFFF  
FFFF0003  
5-28  
Maxtor Atlas 10K V  
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-38 LOG SELECT Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (4Ch)  
Reserved  
PCR  
SP  
2
PC  
Reserved  
3 – 6  
7 – 8  
9
Reserved  
Parameter List Length  
Control  
Table 5-39 LOG SELECT Command Descriptor Block-Field Descriptions  
Field  
Description  
Parameter Code Reset. Must be 1. Causes all the imple-  
mented counters to be set to 0.  
PCR  
Save Parameters. A value of 1 indicates that certain  
counters are to be cleared from non-volatile memory.  
SP  
PC  
Page Control. Must be 01b OR 11b.  
Parameter  
List Length  
Must be 0.  
Maxtor Atlas 10K V  
5-29  
   
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.  
Table Table 5-40 lists the log pages supported by the drive. Contact your Maxtor  
Applications Engineer for more information.  
Table 5-40 Disk Drive Log Pages  
Page Code  
00h  
Description  
Supported Log Pages  
Buffer Overruns and Underruns  
Write Error Counter  
01h  
02h  
03h  
Read Error Counter  
05h  
Verify Error Counter  
Non-Medium Error Counter Page  
Last n-Error Events Page  
Format Status Page  
06h  
07h  
08h  
0Dh  
0Eh  
Temperature Page  
Start-Stop Cycle Counter  
Application Client Page  
Self Test Results Page  
EWS Status  
0Fh  
10h  
2Fh  
5-30  
Maxtor Atlas 10K V  
 
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.  
Table 5-41 LOG SENSE Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (4Dh)  
Reserved  
1
PPC  
SP  
2
PC  
Page Code  
3 – 4  
5 – 6  
7 – 8  
9
Reserved  
Parameter Pointer  
Allocation Length  
Control  
Table 5-42 LOG SENSE Command Descriptor Block-Field Descriptions  
Field  
Description  
The Parameter Pointer Control bit controls the type of parameters that can be requested  
from the drive. This bit must be 0, indicating that all log parameters for the specified page  
(subject to the allocation length specified) are returned to the initiator.  
PPC  
The Save Pages bit specifies whether the parameters are to be saved. This bit must be 0,  
indicating that no parameters are to be saved and are reset at power-on or by a TARGET  
RESET.  
SP  
The Page Control field defines the type of parameter values to be selected. The field must  
be 01b indicating that the current values are to be returned. Mode 11b (return default val-  
ues) is not supported because all counters have a default value of 0.  
PC  
The value specified as the Page Code determines the page to be returned. Table 5-40 con-  
tains a list of supported log pages and their page codes.  
Page Code  
Parameter Pointer  
Allocation Length  
This field is related to the PPC field. This bit must be 0.  
This specifies the number of bytes of data that the drive is allowed to pass during the  
DATA IN phase. The requested page is truncated if its length exceeds the number of bytes  
specified in this field.  
Maxtor Atlas 10K V  
5-31  
   
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-43 LOG SENSE Log Page Format-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Reserved  
Page Code  
1
Reserved  
2 – 3  
Page Length (n-3)  
4 to  
x+3  
Log Parameter (first)  
1
(length x)  
n-y+1  
to n  
Log Parameter (last)  
1
(length y)  
Note: 1Length x or y is the sum of parameter header and parameter data  
value bytes.  
Table 5-44 LOG SENSE Log Page Format-Field Descriptions  
Field  
Description  
Page Code  
The page code as given in Table 5-39.  
The allocation length for the page minus the  
4-byte header.  
Page Length  
One or more log data entities that are returned as par of  
a Log Page. Each Log Parameter starts with a 4-byte  
header followed by one or more bytes of value data. In  
most cases, the parameter value is a 4-byte longword  
that contains the present value of an error or perfor-  
mance counter. See Table 5-45 for the format of a  
generic log parameter.  
Log Parameter  
Table 5-45 Generic Log Parameter-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 – 1  
2
Parameter Code  
ETC  
DU  
DS  
TSD  
TMC  
LBIN  
LP  
3
Page Length (n-3)  
Parameter Value  
4 – n  
5-32  
Maxtor Atlas 10K V  
     
Table 5-46 Generic Log Parameter-Field Descriptions  
Field  
Description  
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.  
Parameter Code  
The following pages in this manual contain the lists of applicable parameters for each  
Log page.  
DU  
DS  
Disable Update. This parameter is 1 when updates are not enabled.  
Disable Save. This parameter is 1 when parameters are not saved by the drive.  
Target Save Disable. This parameter is 0 indicating that the drive provides a target-spe-  
cific way of saving parameters.  
TSD  
ETC  
TMC  
Enable Threshold Comparison. This parameter is always 0. The drive does not use  
thresholds for any of its parameters.  
Threshold Met Comparison. This parameter is always 0. The drive does not use thresh-  
olds for any of its parameters.  
List in Binary. This bit only valid if LP = 1. If LP = 1 and LBIN = 0, then the List Pa-  
rameter is a string of ASCII graphic codes (code values 20h through 7Eh). If LP = 1 and  
LBIN = 1, then the parameter is a list of binary information.  
LBIN  
LP  
List Parameter. When 0, indicates that the parameter value for this parameter is a nu-  
meric value. When LP is a 1, it indicates that the parameter value is an alphanumeric  
ASCII-string list.  
This parameter is always 0.  
Parameter Length  
Parameter Value  
Specifies the length, in bytes, of the parameter’s value.  
Contains the parameter’s current value when the PC field of the LOG SENSE command  
is 01b.  
Note: The DU, DS, TSD, ETC, TMC, LBIN and LP fields are collec-  
tively referred to as the Parameter Control Byte. This byte gen-  
erally has a value of 0; however, if the page is non-volatile but  
the drive is not spun up or the GLTSD bit is set in Mode Page  
0Ah, then the value would be 20h. If the page is volatile, then  
the value is 60h.  
Maxtor Atlas 10K V  
5-33  
 
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.  
The new mode parameters are then stored in the drive’s non-volatile memory. The  
MODE SELECT CDB is described in Table 5-47 and a description of the fields in  
Table 5-47 MODE SELECT (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (15h)  
1
2 – 3  
4
Reserved  
PF  
Reserved  
SP  
Reserved  
Parameter Length List  
Control  
5
Table 5-48 MODE SELECT (6) Command Field Descriptions  
Data Field  
Description  
Page Format. The drive ignores the content of this field and produces a mode  
parameter list that contains a mode header optionally followed by a sector de-  
scriptor and one or more pages that conform to the format shown here.  
PF  
Save Pages. When SP = 0, the drive performs the specified MODE SELECT  
operation and does not save any pages. When SP = 1, the drive performs the  
specified operation and stores all savable pages, (PS =1 on MODE SENSE re-  
turn) including any sent during the data-out buffer transfer. The changes made  
when SP = 1 become permanent changes to the drive’s SCSI setup.  
SP  
This field tells the drive how many bytes of Mode Parameters to fetch in the  
data-out buffer transfer. A CHECK CONDITION status is returned if this val-  
ue truncates a page.  
Parameter List Length  
5.12.1  
Initiator-Changeable Mode Pages  
Table 5-49 lists the mode pages that are supported by the drive. An initiator can  
change these pages by supplying them, with the desired changes included, in the  
MODE SELECT command’s data-out buffer transfer.  
The initiator should first use a MODE SENSE command to read the appropriate pages  
and leave non-changeable values as read when the initiator subsequently writes the  
changeable pages with the MODE SELECT command. If a non-changeable field  
contains an invalid value, the drive returns a CHECK CONDITION status.  
5-34  
Maxtor Atlas 10K V  
   
Table 5-49 Initiator-Changeable Mode Pages  
Size In  
Bytes  
Page Code  
Page Name  
Function  
Unit Attention reporting (enables  
00h  
Unit Attention Control Page  
or  
4
disables)  
Medium Access Error recovery  
and  
Read-Write Error Recovery Page  
01h  
02h  
12  
16  
reporting procedures for  
READ and WRITE commands  
Bus behavior during data trans-  
fers  
Disconnect-Reconnect Page  
Verify Error Recovery Page  
Medium Access Error recovery  
and reporting procedures for the  
VERIFY command  
1
12  
07h  
1
Caching Page  
Cache policy  
20  
12  
08h  
1
Control Mode Page  
Command processing policy  
0Ah  
Drive geometry  
reporting  
0Ch  
Notch and Partition Page  
24  
19h  
Port Control Page  
Margin Control  
Defines port control parameters  
Margin control values  
8
19h(1h)  
16  
Saved Training  
Configuration  
Saved training  
19h(2h)  
19h(3h)  
19h(4h)  
1Ah  
234  
14  
configuration values  
Negotiated settings for current  
I_T Nexus  
Negotiated Settings  
Report Transfer  
Capabilities  
Transfer capabilities  
14  
Enable and set time intervals for  
Idle and Standby modes  
Power Condition Page  
12  
Information Exceptions Control Page  
and operations of specific information-  
al exception  
Defines methods to control re-  
porting  
1Ch1  
12  
conditions.  
NOTE:  
1. This page is not supported by the SCSI-1/CCS Operating Mode.  
Maxtor Atlas 10K V  
5-35  
 
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 spec-  
ification states that a drive can maintain Mode parameters on a per-initiator basis if it so chooses.  
The Drives do not support this option.  
The current mode page set contains the values supplied in the last MODE SELECT command re-  
ceived from an initiator. If no initiator has sent a MODE SELECT command since the drive was  
last reset or powered up, the current pages contain  
Current  
Saved values if saved pages exist (from a previous MODE SELECT command SP parameter).  
Default values if pages have never been saved.  
The drives generate a Unit Attention condition for all initiators (except for the one that was the  
source of the MODE SELECT command) whenever one initiator modifies the Mode parameters.  
The default mode page set contains the factory default values that are listed in each page’s descrip-  
Default  
Saved  
tion.  
The saved mode page set contains values preserved in the drive’s non-volatile memory by a pre-  
vious SP-modified MODE SELECT command.  
The changeable mode page set provides a means for an initiator to determine which pages it is  
allowed to change and the specific bits within those pages that it is allowed to change. This page  
set is read-only and is fetched with a MODE SENSE command.  
Changeable  
5.12.3  
Mode Parameter List  
Table 5-51 shows the format of the Mode Parameter List that is passed by the initiator  
to the drive during the command’s data-out buffer transfer. Table 5-52 describes the  
fields. Table 5-53 and Table 5-54 provides a description of the data format and fields  
of the Mode Parameter Header. Table 5-55 and Table 5-56 describe the format and  
field descriptions for the Mode Parameter Block Descriptor.  
Table 5-51 Mode Parameter List-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 – 3  
Mode Parameter Header  
Block Descriptor  
(optional)  
4 – 11  
4 – n  
or  
12 – n  
Page(s)  
(optional)  
5-36  
Maxtor Atlas 10K V  
   
Table 5-52 Mode Parameter List-Field Descriptions  
Field  
Description  
Contains information about the remainder of the pa-  
rameter list and is always present (see Table 5-53 and  
Mode Parameter Header  
Allows the initiator to set the drive’s Logical Block  
Size and number of Logical Block Addresses (see Ta-  
Block Descriptor  
Page(s)  
The page code(s) of the pages that are a part of this  
command.  
Table 5-53 Mode Parameter Header (6-Byte)-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
Mode Data Length  
Medium Type  
Device-Specific Parameter  
Block Descriptor Length  
Table 5-54 Mode Parameter Header- Field Descriptions  
Field  
Description  
Mode Data Length  
Medium Type  
Reserved. Must be 0.  
Ignored by the drive.  
Ignored by the drive.  
Device-specific Parameter  
Zero (0) if no Block Descriptor is supplied. The length  
is eight (8) if a Block Descriptor is supplied.  
Block Descriptor Length  
Table 5-55 Mode Parameter Block Descriptor-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 – 3  
4
Number of Blocks  
Reserved  
5 – 7  
Block Length  
Maxtor Atlas 10K V  
5-37  
       
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 ca-  
pacity, the device shall be set to that number of blocks. If the block size has not changed,  
the device shall not become format corrupted. This capacity setting shall be retained  
through power cycles, hard resets, logical unit resets and I_T nexus losses:  
Number of Blocks  
If the number of blocks field is set to a value greater than the maximum capacity of the  
device and less than FFFF FFFFh, then the command is terminated with a CHECK  
CONDITION status. The sense key is set to ILLEGAL REQUEST. The device shall re-  
tain its previous block descriptor settings; or  
If the number of blocks is set to FFFF FFFFh, the device shall be set to its maximum  
capacity. If the block size has not changed, the device shall not become format corrupt-  
ed. This capacity setting shall be retained through power cycles, hard resets, logical unit  
resets, and I_T nexus losses.  
Block Length  
This field specifies the length, in bytes, of each logical sector.  
5.12.4  
Categories of Changeable Pages  
The drive’s changeable pages are described on the following pages. The data fields for  
each of these pages fall into one of the categories described in Table 5-57.  
Table 5-57 Categories of Changeable Pages  
Category  
Description  
A field in this category can be modified by the MODE SELECT command, can be saved and can  
affect the drives processing. The drive uses the value in the field and, if the SP bit is set, preserves  
the new value of the field in non-volatile memory on the drive. (The PS bit must have been set  
when the mode page was returned with a MODE SENSE command.)  
Fully Supported  
Ignored  
A value in this field is never used or validated; it is never looked at by the drive. Ignored fields are  
not underlined in the Mode Parameter Pages’ figures or tables and are not described in the Field  
Description tables.  
5.12.5  
Unit Attention Condition Page (00h)  
The Unit Attention Page is used to enable or disable the generation of Unit Attention  
Conditions. The Unit Attention Condition Page format and field descriptions are  
Table 5-58 Unit Attention Condition Page (Page 0)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
PS  
Rsvd  
Page Code (00h)  
Page Length (02h)  
DUA  
Reserved  
Reserved  
Reserved (00h)  
5-38  
Maxtor Atlas 10K V  
     
Table 5-59 Unit Attention Condition Page (Page 0)  
Field  
Default Value  
Description  
Parameters Savable. This bit is only used with the MODE SENSE com-  
mand. A returned value of 1 indicates that the target is capable of sav-  
ing the page in a non-volatile, vendor-specific location. The bit is  
reserved with the MODE SELECT command.  
PS  
1
Disable Unit Attention. When set to the default value of 0, the drive re-  
ports a CHECK CONDITION for any UNIT ATTENTION condition  
(power-on, SCSI bus reset, etc.)  
DUA  
0
5.12.6  
Read-Write Error Recovery Page (01h)  
The Read-Write Error Recovery page controls the drive’s response to error  
conditions that arise during the course of READ (6), READ (10), WRITE (6),  
WRITE (10) command processing and during the write portion of WRITE AND  
VERIFY command processing. The Read-Write Error Recovery page format and  
field descriptions are described in Table 5-60 and Table 5-61 respectively.  
Table 5-60 Read-Write Error Recovery Page-(Page 1)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
PS  
Rsvd  
Page Code (01h)  
Page Length (0Ah)  
RC EER  
1
2
AWRE  
ARRE  
TB  
PER  
DTE  
DCR  
3
Read Retry Count  
Correction Span  
Head Offset Count  
Data Strobe Offset Count  
Reserved  
4
5
6
7
8
9
Write Retry Count  
Reserved  
10 – 11  
Recovery Time Limit  
Maxtor Atlas 10K V  
5-39  
   
Table 5-61 Read-Write Error Recovery Page - Field Descriptions  
Default  
Value  
Field  
Description  
Parameters Savable. This bit is only used with the MODE SENSE command. A returned val-  
ue 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.  
PS  
1
Automatic Write Reallocation Enable. When the value is 1, it causes the drive to automati-  
cally reallocate bad sectors encountered during a write operation. If it succeeds in replacing  
the bad sector, the drive adds the revectored sector’s Logical Block Number to the Grown  
Defect List.  
AWRE  
1
When AWRE is 0, the drive does not automatically reallocate bad sectors encountered during  
a write operation.  
Automatic Read Reallocation Enable. When the value is 1, it causes the drive to automatical-  
ly reallocate bad sectors encountered during a read operation. If it succeeds in replacing the  
bad sector, the drive adds the revectored sector’s Logical Block Number to the Grown Defect  
List. Reallocation is done only when the drive is able to recover the sector’s data unless the  
Reallocate Uncorrected Errors bit of the Maxtor (Vendor) Special Function Control Page is  
set.  
ARRE  
TB  
1
0
When ARRE is 0, the drive does not automatically reallocate bad sectors encountered during  
a read operation. See also Maxtor-Unique Page 39h (RUEE).  
Transfer Block. When the value is 1, the drive sends best-guess information to the initiator  
when it encounters a defective sector whose data cannot be fully recovered.  
When the value is 0, data that cannot be fully recovered is not returned to the initiator.  
Read Continuous. When the value is 0, the drive attempts error recovery when it encounters  
an error. When the value is 1, the drive suppresses error recovery. The drive ignores any val-  
ue placed in this field.  
RC  
0
0
EER  
Enable Early Recovery. Not supported by the drive.  
Post Error Recovery. When the value is 0, the drive returns a GOOD status in cases where  
error recovery is invoked and successful.  
PER  
DTE  
0
0
When the value is 1, the drive returns a CHECK CONDITION status for recovered errors,  
sets the sense key to RECOVERED ERROR, and posts the appropriate additional sense key.  
Disable Transfer on Error. Not supported by the drive.  
Disable Correction. When the value is 0, ECC correction is applied as a means of recovering  
erred data. On write operations, a valid ECC is written to each data sector regardless of the  
value in the DCR bit.  
DCR  
0
When the value is 1, Firmware ECC correction only is disabled (but not retries or reads), and  
ECC errors greater than hardware correctable cannot be corrected.  
Read Retry  
Count  
4
Specifies the number of retries attempted for a failed read operation.  
Specifies the maximum number of bits in a data sector that the drive is allowed to correct. A  
value less than the default value can cause an otherwise correctable error to be reported as  
uncorrectable. If the initiator specifies a value larger than the default value, the drive auto-  
matically rounds down the number to the default value. A value of 0 causes the drive to use  
the default value. The drive ignores any value placed in this field.  
Correction  
Span  
240  
Head Offset  
Count  
0
0
8
Not supported by the drive.  
Data Strobe  
Offset Count  
Not supported by the drive.  
Write Retry  
Count  
Specifies the number of retries attempted for a failed write operation.  
5-40  
Maxtor Atlas 10K V  
 
Default  
Value  
Field  
Description  
Specifies the maximum time, in milliseconds, that a retry is attempted on a failed sector dur-  
ing 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.  
Recovery  
Time Limit  
0
Maxtor Atlas 10K V  
5-41  
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.  
Table 5-62 Disconnect–Reconnect Page (Page 2)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
PS  
Rsvd  
Page Code (02h)  
1
2
Page Length (0Eh)  
Buffer Full Ratio  
3
Buffer Empty Ratio  
Bus Inactivity Limit  
Disconnect Time Limit  
Connect Time Limit  
Maximum Burst Size  
4 – 5  
6 – 7  
8 – 9  
10 – 11  
12  
EMDP  
Fairness Arbitration  
DImm  
Reserved  
First Burst Size  
DTDC  
13  
14 – 15  
Table 5-63 Disconnect-Reconnect-Field Descriptions (Page 2)  
Default  
Field  
Description  
Value  
Parameters Savable. This bit is only used with the MODE SENSE command. A re-  
turned 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.  
PS  
0
0
The Buffer Full Ratio indicates how full the buffer should be prior to requesting an  
interconnect tenancy. Applies to READ operations only. The default of 0 indicates  
to the drive that it should use its default ratio.  
Buffer Full  
Ratio  
The Buffer Empty Ratio indicates how full the buffer should be prior to requesting  
an interconnect tenancy. Applies to READ operations only. The default of 0 indi-  
cates to the drive that it should use its default ratio. Not supported by the drive.  
Buffer Empty  
Ratio  
0
0
Bus Inactivity  
Limit  
The Bus Inactivity Limit indicates the maximum duration of any interconnect ten-  
ancy during which no data is transferred. Not supported by the drive.  
The Disconnect Time Limit specifies the minimum time, in 100 microsecond in-  
crements, that the drive waits after releasing the SCSI bus before reselecting. The  
drive supports a maximum value of 0xFF. Values greater than 0xFF are treated as  
0xFF. The default value of 0 indicates that the drive can reslect immediately after  
releasing the bus.  
Disconnect  
Time Limit  
0
0
Connect Time  
Limit  
The Connect Time Limit indicates the maximum duration of a single interconnect  
tenancy. Not supported by the drive.  
The Maximum Burst Size  
specifies the maximum amount of data that the drive will transfer during a data  
phase before disconnecting from the bus, assuming it was given the disconnect  
privilege. This value is expressed in increments of data sectors (that is, a value of  
1 indicates 512 bytes, a value of 2 indicates 1024 bytes). The default value of 0 in-  
dicates that there is no limit on the amount of data transferred per connection. This  
field is reserved for the SCSI-1/CCS operating mode.  
MaximumBurst  
Size  
0
5-42  
Maxtor Atlas 10K V  
   
Default  
Value  
Field  
Description  
Enable MODIFY DATA POINTER. Not supported by the drive.  
EMDP  
0
Fairness  
Arbitration  
111b  
(Def)  
Indicates whether or not the target should use fair or unfair (e.g., priority) arbitra-  
tion 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).  
Disconnect Immediate. When set to a 1, to reduce on-bus time, the drive is forced  
to disconnect from the SCSI Bus after a SCSI Command is received. Disconnect  
Immediate works only when a typical, error-free command is received. Disconnect  
Immediate does not apply in exception conditions (for example, SDTR received,  
error, etc.).  
DImm  
DTDC  
0
Data Transfer Disconnect Control. This field of three bits defines further restrictions when a discon-  
nect is permitted. These are as follows:  
Value  
Description  
000b  
(Def)  
Data transfer disconnect control is not used. Disconnect is controlled by other  
fields in this page.  
001b - A target will not attempt to disconnect once the data transfer of a command  
has started until all data of the command has been transferred. The connect time  
limit and bus inactivity limit are ignored during the transfer.  
010b - Reserved  
011b - A target will not attempt to disconnect once the data transfer of a command  
has started, until the command is complete. The connect time limit and bus inac-  
tivity limit are ignored once the transfer has started.  
This field indicates the maximum amount of data that a target may transfer for a  
command during the same interconnect in which it receives the command. Not ap-  
plicable for parallel SCSI.  
First Burst Size  
0
5.12.8  
Verify Error Recovery Page (07h)  
The Verify Error Recovery Page controls the drive’s response to error conditions that  
arise during the VERIFY command and during the verify operation of the WRITE  
AND VERIFY command. The Verify Error Recovery Page is not supported in the  
SCSI-1/CCS Operating Mode. The data format and field descriptions are described  
Table 5-64 Verify Error Recovery Page-(Page 7)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
PS  
Rsvd  
Page Code (07h)  
1
2
Page Length (0Ah)  
EER  
Reserved  
PER  
DTE  
DCR  
3
Verify Retry Count  
Verify Correction Span  
Reserved  
4
5 – 9  
10 – 11  
Verify Recovery Time Limit  
Maxtor Atlas 10K V  
5-43  
 
Table 5-65 Verify Error Recovery Page-Field Descriptions (Page 7)  
Default  
Value  
Field  
Description  
Parameters Savable. This bit is only used with the MODE SENSE command. A returned val-  
ue 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.  
PS  
0
0
EER  
Enable Early Recovery. Not supported by the drive.  
Post Error Recovery. When the value is 1, the drive returns CHECK CONDITION status for  
recovered errors, sets the sense key to RECOVERED ERROR, and posts the appropriate ad-  
ditional sense code.  
PER  
0
When set to the default value of 0, it causes the drive to return GOOD status in cases where  
error recovery is invoked and is successful. The only recoverable error that can occur during  
a VERIFY operation is a failed read that succeeds after retries.  
DTE  
DCR  
0
0
Disable Transfer on Error. Not supported by the drive.  
Disable Correction. When the value is 1, it disables ECC Firmware only (but not retries) on  
the READ portion of a VERIFY operation. When set to the default value of 0, the ECC cor-  
rection is always applied as a means of recovering erred data.  
Verify  
Retry Count  
The Verify Retry Count specifies the number of retries that are attempted per sector on a  
failed READ portion of a VERIFY operation.  
4
The Verify Correction Span specifies the maximum number of bits in a sector that the drive  
is allowed to correct. A value less than the default value can cause an otherwise correctable  
error to be reported as uncorrectable. If the initiator specifies a value larger than 80, the drive  
rounds down to 80 without reporting the change. A value of 0 causes the drive to use its de-  
fault value. The drive ignores any value in this field.  
Verify  
Correction  
Span  
240  
Verify  
Recovery  
Time Limit  
The Verify Recovery Time Limit specifies (in milliseconds) the maximum time that a retry  
is attempted on a failed sector during the read portion of a verify operation. The default value  
of 0 indicates that there is no time limit. The minimum permissible is 100 milliseconds.  
0
5.12.9  
Caching Page (08h)  
The Caching Page controls the drive’s cache management policy. The data format and  
field descriptions are described in Table 5-66 and Table 5-67 respectively.  
Table 5-66 Caching Page-(Page 8)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
1
PS  
Rsvd  
Page Code (08h)  
Page Length (12h)  
DISC Size  
2
IC  
ABPF  
CAP  
WCE  
MF  
RCD  
3
Demand Read Retention Priority  
Demand Write Retention Priority  
4 – 5  
6 – 7  
8 – 9  
Disable Pre-Fetch Transfer Length  
Minimum Pre-Fetch  
Maximum Pre-Fetch  
10 – 11  
12  
Maximum Pre-Fetch Ceiling  
FSW  
LBCSS  
DRA  
VS  
VS  
Reserved  
13  
Number of Cache Segments  
Cache Segment Size  
Reserved  
14 – 15  
16  
17 – 19  
Non-Cache Segment Size  
5-44  
Maxtor Atlas 10K V  
   
NOTES:  
Bytes 12 to 19 are returned only if the device operating definition is SCSI-3.  
Table 5-67 Caching Page - Field Descriptions  
Default  
Field  
Description  
Value  
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  
PS  
1
non-volatile, vendor-specific location. Bit reserved with MODE SELECT com-  
mand.  
An initiator control (ic) enable bit set to one specifies that the device server use  
the NUMBER OF CACHE  
IC  
0
SEGMENTS field or the CACHE SEGEMENT SIZE field, dependent upon the  
SIZE bit, to control the caching algorithm rather than the device server’s own  
adaptive algorithm.  
Enable Abort Prefetch. When set, this bit requests the device abort pre-fetch  
ABPF  
CAP  
0
0
work on the receipt of a new command.Ignored by the drive  
A caching analysis permitted (cap) bit set to one specifies that the device server  
perform caching analysis during subsequent operations. A cap bit set to zero  
specifies that the caching analysis be disabled to reduce overhead time or to pre-  
vent non pertinent operations from impacting tuning values.  
A discontinuity (DISC) bit set to one specifies that the device server continue  
the pre-fetch across time discontinuities (e.g., across cylinders) up to the limits  
of the buffer, or segment, space available for the pre-fetch. A DISC bit set to  
zero specifies that pre-fetches be truncated or wrapped at time discontinuities.  
ignored by drive.  
DISC  
Size  
0
0
Specifies which of two fields are used to configure the cache. When Size=0, the  
Number of Cache Segments field is used. When Size=1, the Cache Segment  
Size field is used.  
Write Cache Enable. The default value of 1 enables write-back caching when  
processing a WRITE command. When set to 0 the drive returns a GOOD status  
and COMMAND COMPLETE only after successfully writing all the data to the  
media.  
When WCE = 1, write-back caching is enabled while processing a WRITE com-  
mand. The drive returns a GOOD status and COMMAND COMPLETE only af-  
ter fetching the data from the initiator and placing it in the drive’s cache  
memory.  
WCE  
1
Note: For maximum data integrity, it is strongly recommended that when WCE  
is set to 1, the Read-Write Error Recovery Page (01h) fields be set as follows:  
• AWRE to 1  
• RC to 0  
• DCR to 0  
• Correction Span set to 170  
• Head Offset to 0  
• Servo Offset to 0  
Multiplication Factor (value must be 0). The drive interprets the minimum and  
maximum pre-fetch fields values in terms of the number of logical blocks for  
each of the respective types of prefetch.  
MF  
0
0
Read Cache Disable. The default value of 0 enables the read cache capability  
and allows the drive to use cache-resident data or medium data to satisfy a  
READ command.  
RCD  
When the value is 1, read caching is disabled and the data returned in response  
to a READ command is fetched from the medium and not from the drive’s cache  
memory.  
Maxtor Atlas 10K V  
5-45  
 
Default  
Value  
Field  
Description  
Demand Read Re-  
tention  
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.  
0
Priority  
Demand Write Re-  
tention  
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.  
0
Priority  
This field specifies the selective disabling of anticipatory pre-fetch  
on long transfer lengths. The value in this field is compared to the number of  
sectors requested by the current READ command. If the number of sectors is  
greater the than the value specified, anticipatory pre-fetch is not performed for  
the command. When 0, anticipatory pre-fetch is disabled.  
Disable  
Pre-Fetch Transfer  
Length  
FFFFh  
Minimum  
Pre-fetch  
This field specifies the desired number of sectors to be pre-fetched preceding  
the requested Data.  
0x100  
0x200  
Maximum  
Pre-fetch  
This field specifies the desired amount of total number of sectors to be pre-  
fetched surrounding the requested data.  
Specifies an upper limit on the number of logical blocks computed as the max-  
imum pre-fetch. If this number of sectors is greater than the maximum pre-  
fetch, then the number of logical blocks to pre-fetch is reduced to the value  
stored in the maximum pre-fetch ceiling field.  
Maximum  
Pre-fetch  
Ceiling  
0x200  
FSW  
0
The Force Sequential Write bit. Not supported by the drive.  
Selects the units of the cache segment Size field. When LBCSS=0, Units are  
bytes per segment. When LBCSS=1, Units are blocks per segment.  
LBCSS  
TBD  
When set, the device server will not read into cache any logical blocks beyond  
the addressed logical block (s). When not set, the device server may continue to  
read logical blocks beyond the addressed logical block (s).  
DRA  
VS  
0
The Vendor-Specific bits. Not supported by the drive.  
Number of Cache  
Segments  
Specifies the number of cache segments to divide the cache into. This field is  
used when the Size bit is 0.  
variable  
variable  
0
Specifies the cache segment size, in either bytes per segment or blocks per seg-  
ment, depending on the state of the LBCSS bit. This field is used when the Size  
bit is 1  
Cache Segment Size  
Non-CacheSegment  
Size  
Not supported by the drive.  
5.12.10 Control Mode Page (0Ah)  
The Control Mode page controls the drive’s command processing and error handling  
policies. The data format and field descriptions are described in Table 5-68 and Table  
Table 5-68 Control Mode Page - Data Format (Page 0Ah)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
PS  
Rsvd  
Page Code (0Ah)  
Page Length (0Ah)  
Reserved  
Queue Algorithm Modifier  
GLTSD  
RLEC  
DQue  
Re-  
served  
3
Qerr  
5-46  
Maxtor Atlas 10K V  
 
UAAER  
P
4
EECA  
RAC  
Reserved  
SWP  
Reserved  
RAERP  
EAERP  
5
6 – 7  
8 – 9  
10  
Ready AEN Holdoff Period  
Busy Timeout Period  
MSB  
Extended Selftest Completion Time  
11  
Extended Selftest Completion Time  
LSB  
NOTES:  
Bytes 8 to 11 are returned only if the device operating definition is SCSI-3.  
Maxtor Atlas 10K V  
5-47  
Table 5-69 Control Mode Page-Field Descriptions  
Field Value Default  
Description  
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, ven-  
dor-specific location. The bit is reserved with the MODE SELECT command.  
PS  
1
Global Logging Target Save Disable. If this bit = 1, the ability to save log ages to disk  
is disabled. If a LOG SELECT with the SP bit is received by the drive, the current cu-  
mulative values will be cleared. The on-disk values will not be changed. If a LOG  
SENSE with the SP bit set is received by the drive and the GLTSD bit is set and the unit  
is ready, the last LOG counter values written to disk will be returned (not the current  
cumulative values).  
GLTSD  
RLEC  
0
If a STOP UNIT command or a LOG SENSE command with the SP bit set is issued to  
the drive, the cumulative values of the Log Counters page will be written to disk. A  
LOG SENSE command will return the cumulative values since the counters were  
cleared, not since the drive was powered on.  
Report Log Exception Condition. The drive does not report log exception conditions.  
Not supported by the drive.  
0
This field specifies restrictions on the algorithm used for re-ordering commands that are  
tagged with the SIMPLE message.  
A value of 0 specifies that the drive orders the actual execution sequence with a SIM-  
PLE statement.  
Queue  
Algorithm  
Modifier  
0001b  
A value of 1 (Unrestricted Re-ordering Allowed) specifies that the drive can re-order  
the actual execution sequence of the commands with a SIMPLE in any manner. Any  
data integrity exposures related to command sequence order are explicitly handled by  
the initiator through the selection of appropriate commands and queue tag messages.  
Queue Error Management. This field controls the drive’s processing of queued com-  
mands when a Contingent Allegiance (CA) condition or Extended Contingent Alle-  
giance (ECA) is cleared. Processing of queued commands is resumed when a CA/ECA  
condition is cleared.  
QErr  
00b  
0
Disable Queue. When set to the default value of 0, the drive supports tagged command  
queuing.  
DQue  
When the Disable Queue bit is set to 1, tagged command queuing is disabled. A subse-  
quent tagged message from the initiator is rejected with a MESSAGE REJECT message  
and the I/O process is executed as an untagged command.  
EECA  
RAC  
0
0
AEN enabled.  
Report A Check Condition bit. Ignored by the drive.  
SWP - Soft-  
ware Write  
Protect  
This file controls the drive’s write protection feature. If set, the drive returns check con-  
dition for the command with sense code/ASC/ASCQ - 07/27/00  
0
RAERP  
UAAERP  
EAERP  
0
0
0
Ready AER Permission. Not supported by the drive.  
Unit Attention AER Permission. Not supported by the drive.  
Error AER Permission. Not supported by the drive.  
Ready AER  
Holdoff  
Period  
0
Not supported by the drive.  
Busy Timeout  
Period  
FFFFh  
200h  
Not supported by the drive.  
Extended Self  
Test Comple-  
tion Time  
Contains advisory data that indicates the approximate time, in seconds, required to com-  
plete an extended self-test when not interrupted by subsequent commands and no errors  
occur during execution of the self-test.  
5-48  
Maxtor Atlas 10K V  
 
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.  
Maxtor Atlas 10K V  
5-49  
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. The data format and  
field descriptions are described in Table 5-70 and Table 5-71 respectively.  
Table 5-70 Notch and Partition Page-(Page 0Ch)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
1
PS  
Rsvd  
Page Code (0Ch)  
Page Length (16h)  
Reserved  
2
ND  
LPN  
3
Reserved  
Maximum Number of Notches  
Active Notch  
4 – 5  
6 – 7  
8 – 11  
12 – 15  
16 – 23  
Starting Boundary  
Ending Boundary  
Pages Notched  
5-50  
Maxtor Atlas 10K V  
 
Table 5-71 Notch and Partition Page-Field Descriptions  
Data Field  
Description  
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 SE-  
LECT command.  
PS  
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.  
ND  
The default value of 1 indicates that the device is notched. For each supported ac-  
tive notch value, this page defines the starting and ending boundaries of the notch.  
Logical or Physical Notch. The default value of 0 indicates that the boundaries of  
the notch are based on the physical parameters of the logical unit. The cylinder is  
considered most significant and the head least significant.  
LPN  
A value of 1 indicates that the notch boundaries are based on logical blocks of the  
logical unit.  
This field indicates the maximum number of notches supported by the logical unit.  
The value cannot be changed.  
MaxNotch  
Active Notch  
The Active Notch field indicates the notch referenced by this, and subsequent  
MODE SELECT and MODE SENSE commands. The value in this field can be  
changed by a later MODE SELECT command. The value of the active notch must  
be = 0 and = 24. An active notch of 0 indicates that this and subsequent MODE  
SELECT and MODE SENSE commands refer to the parameters that apply across  
all notches.  
This field indicates the beginning of the active notch or, if the active notch is 0, the  
beginning boundary of the logical unit. If the LPN value is 1, the starting boundary  
is a Logical Block Address.  
Starting Boundary  
Ending Boundary  
If the LPN value is 0, the three most significant bytes designate the starting cylin-  
der number and the least significant byte is the starting head number. This field is  
unchangeable. When used with the MODE SELECT command, this field is ig-  
nored.  
This field indicates the ending of the active notch, or if the active notch is zero, the  
ending of the logical unit. If the LPN value is 0, the 3 most significant bytes des-  
ignate the ending cylinder and the least significant byte is the ending head number.  
This is a 64-bit bitmap that indicates which MODE command pages contain pa-  
rameters that may be different for different notches. The most significant bit  
(MSB) corresponds to Page 3Fh (Vendor-Unique Caching Page), and the least sig-  
nificant bit (LSB) corresponds to Page 00h  
(Unit Attention Control Page).  
Pages Notched  
If a bit is 1, the corresponding mode page contains parameters that may be differ-  
ent for different notches.  
If a bit is 0, the corresponding mode page contains parameters that are constant for  
all notches.  
The value of 1 in bits 3 and 12 indicates that Page 03h and 0Ch contain different  
parameters for different notches.  
Maxtor Atlas 10K V  
5-51  
 
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.  
The target will maintain an independent set of port control mode page parameters for  
each initiator. The parameters saveable bit in the mode page format header returned  
with MODE SENSE command will be set to zero if the long mode page format is  
being used (LONG bit set to one), indicating the parameters are not saved through  
resets.  
Table 5-72 Port Control Page Short Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
4
5
6
7
PS  
LONG(0)  
Page Code (19h)  
Page Length (06h)  
Reserved  
Protocol Identifier (1h)  
Reserved  
MSB  
Synchronous Transfer Timeout  
Synchronous Transfer Timeout  
Reserved  
LSB  
Reserved  
The Protocol Identifier field of 1h indicates the protocol that this mode page applies  
to a SPI SCSI device. See the SCSI Primary Commands-2 standard for other port  
control page protocol identifiers.  
The Synchronous Transfer Timeout field indicates the maximum amount of time in  
1 millisecond increments that the target will wait before generating an error by doing  
an unexpected bus free. The target will only go to a BUS FREE phase if one of the  
following events causes the timer, once started, to not reset or reload before expiring:  
• If there is a REQ transition when there are no outstanding REQs  
waiting for an ACK then load and start the timer.  
• If there is a REQ transition when there are any outstanding REQs  
waiting for an ACK then there is no effect on the timer.  
• If there is an ACK transition when there are outstanding REQs waiting  
for an ACK then load and start the timer.  
• If after an ACK transition there are no outstanding REQs waiting for  
an ACK then stop the timer.  
• A SYNCHRONOUS TRANSFER TIMEOUT field value of 0000h  
indicates that the function is disabled. A value of FFFFh indicates an  
unlimited period.  
5-52  
Maxtor Atlas 10K V  
 
Table 5-73 Port Control Page Long Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
4
5
6
n
PS  
LONG (1)  
Page Code (19h)  
Subpage Code  
Page Length (n-3)  
Page Length (n-3)  
Reserved  
MSB  
LSB  
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. The sense key will be set to ILLEGAL REQUEST  
and the additional sense code set to ILLEGAL FIELD IN PARAMETER LIST.  
The Page Length field specifies the length in bytes of the subpage protocol specific  
mode page parameters after the Page Length field.  
The Protocol Identifier field of 1h indicates the protocol that this mode page applies  
to a SPI SCSI device. See the SCSI Primary Commands-2 standard for other port  
control page protocol identifiers.  
Maxtor Atlas 10K V  
5-53  
 
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.  
Table 5-74 Margin Control Subpage (01h)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Reserved  
1
Driver Strength  
Drive’s Asymmetry  
Drive’s Slew Rate  
Reserved  
2
Driver Precompensation  
Reserved  
3
4
Reserved  
Reserved  
Reserved  
5
6
7
Vendor Specific  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
8
9
10  
11  
12  
13  
14  
15  
Table 5-75 Field Descriptions  
Description  
Field  
Driver  
Strength  
The DRIVER STRENGTH field indicates the relative amount of driver source cur-  
rently used by the driver. The Driver Strength field affects both the strong and week  
drivers. A larger value indicates more driver source current.  
Driver Pre-  
compensation  
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.  
Driver  
Asymmetry  
The Driver Asymmetry field indicates the relative difference between the amplitudes  
of asserted and negated signals launched from the driver. A larger value indicates a  
relatively stronger asserted signal compared to the negated signal.  
Driver Slew  
rate  
The DRIVER SLEW RATE field indicates the relative difference between the asser-  
tion and negation magnitudes divided by the rise or fall time. A larger value indicates  
a faster slew rate.  
5-54  
Maxtor Atlas 10K V  
 
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.  
The Driver Asymmetry field indicates the relative difference between the amplitudes  
of asserted and negated signals launched from the driver. A larger value indicates a  
relatively stronger asserted signal compared to the negated signal.  
The Driver Slew Rate field indicates the relative difference between the assertion and  
negation magnitudes divided by the rise or fall time. A larger value indicates a faster  
slew rate.  
Maxtor Atlas 10K V  
5-55  
5.12.12.2 Saved Training Configuration Values Subpage (Sub Page 2 of Mode Page 19)  
The saved training configuration values subpage is used to report the SCSI device's  
saved training configuration values. These vendor specific values are maintained by the  
SCSI device when the retain training information option is enabled. The fields are  
listed in Table 5-76; however the content of the fields is vendor specific. Only values  
for the current I_T nexus are reported.  
Table 5-76 Saved Training Configuration Subpage (02h)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
MSB  
Reserved  
3
4
LSB  
LSB  
MSB  
DB(0) Value  
7
64  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
MSB  
DB(15) Value  
P_ORCA Value  
P1 Value  
67  
68  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
LSB  
71  
72  
75  
76  
BSY Value  
SEL Value  
RST Value  
REQ Value  
ACK Value  
ATN Value  
C/D Value  
I/O Value  
79  
80  
83  
84  
87  
88  
91  
92  
95  
96  
99  
100  
103  
104  
107  
108  
MSG Value  
Reserved  
111  
112  
227  
5-56  
Maxtor Atlas 10K V  
 
5.12.12.3 Negotiated Settings Subpage (Sub Page 3 of Mode Page 19)  
The negotiated settings subpage, shown in Table 5-77, is used to report the negotiated  
settings of a target for the current I_T nexus.  
Table 5-77 Negotiated Settings Subpage (03h)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
4
5
Transfer Period Factor  
Reserved  
Req/Ack Offset  
Transfer Width Exponent  
Protocol Option Bits  
Transceiver  
Reserved  
Reserved  
SENT_  
PCOMP_EN  
RECEIVED  
PCOMP_EN  
Mode  
Reserved  
Vendor Specific  
6
7
The Transfer Period Factor field indicates the negotiated transfer period factor for the  
current I_T nexus.  
Table 5-78 Transceiver Period Factor  
Code  
0-7  
Transceiver Period Factor  
Reserved  
8
TP=6.25ns Fast - 160 (U320)  
TP=12.5ns Fast - 80 (U160)  
TP=25ns Fast - 40 (Ultra2)  
TP=30.3 ns Fast - 40  
Fast - 20  
9
0x0A  
0x0B  
0x0C-  
0x18  
0x19-  
0x31  
Fast - 10  
Fast - 5  
0x32-  
0xFF  
The Req/Ack Offset field indicates the negotiated REQ/ACK offset for the current  
I_T nexus.  
The Transfer Width Exponent field indicates the negotiated transfer width exponent  
for the current I_T nexus.  
The Protocol Options Bits field contain the negotiated protocol options for the  
current I_T nexus.  
Maxtor Atlas 10K V  
5-57  
 
The TRANSCEIVER MODE field specifies the current bus mode of the target as  
Table 5-79 Transceiver Mode  
Code  
Transceiver Mode  
Unknown (device not capable of reporting bus mode)  
Single-ended  
00b  
01b  
10b  
11b  
Low-Voltage Differential  
High-Voltage Differential  
The SENT PCOMP_EN bit contains the value of the PCOMP_EN bit sent by the  
target for the current I_T nexus.  
The RECEIVED PCOMP_EN bit contains the value of the PCOMP_EN bit  
received by the target for the current I_T nexus.  
5-58  
Maxtor Atlas 10K V  
 
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.  
Table 5-80 Report Transfer Capabilities Subpage (4)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Minimum Transfer Period Factor  
Reserved  
2
Maximum Req/Ack Offset  
Maximum Transfer Width Exponent  
Protocol Option Bits Supported  
Reserved  
3
4
5-7  
Table 5-81 Field Descriptions  
Description  
Field  
Minimum  
Transfer  
Period  
The MINIMUM TRANSFER PERIOD FACTOR field shall be set to the smallest  
value of the transfer period factor  
Factor  
Maximum  
Req/ack  
Offset  
The MAXIMUM REQ/ACK OFFSET shall be set to the largest value of the  
REQ/ACK offset  
Maximum  
Transfer  
Width  
The MAXIMUM TRANSFER WIDTH EXPONENT shall be set to the  
largest value of the transfer width exponent  
Exponent  
Protocol  
The SCSI target port shall set the bits in the PROTOCOL OPTIONS BITS  
SUPPORTED field to indicate the protocol options supported by the SCSI  
target port.  
Options Bits  
Supported  
Bit Name  
Description  
7
6
5
4
3
2
PCOMP_EN Precompensation enable  
RTI  
Retain training information  
RD_STRM  
WR_FLOW  
Read streaming and read flow control enable  
Write flow control enable  
HOLD_MCS Hold margin control settings  
QAS_REQ  
QAS enable request  
1
0
DT_REQ  
IU_REQ  
DT clocking enable request  
Information units enable request  
Maxtor Atlas 10K V  
5-59  
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. An informational exception condition may occur asynchronous to  
any commands issued by an application client.  
The data format and field descriptions are described in Table 5-82 and Table 5-83  
respectively. The Codes Used by the MRIE Field are described in Table 5-84.  
Table 5-82 Information Exceptions Control Page-(Page 1Ch)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
PS  
Page Code (1Ch)  
Page Length (0Ah)  
EWASC DExcpt  
Perf  
Reserved  
Reserved  
Test  
Rsv’d  
LogErr  
MRIE  
(MSB)  
4 - 7  
Interval Timer  
(LSB)  
(LSB)  
(MSB)  
8 – 11  
Report Count  
5-60  
Maxtor Atlas 10K V  
 
Table 5-83 Information Exceptions Control Page-Field Descriptions (Page 1Ch)  
Default  
Field  
Description  
Value  
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, ven-  
dor-specific location. This bit is reserved with the MODE SELECT command.  
PS  
1
Performance. This bit enables/disables performance-sensitive functions. For Atlas 10K  
V, this means enabling or disabling flushing of SMART data to the media (done hourly).  
The prediction algorithm is designed to reset the current accumulated data approximate-  
ly every 100,000 blocks read or written per head.  
PERF  
1
When this bit = 0, current accumulated SMART data is preserved across power cycles.  
When this bit = 1, current accumulated SMART data is lost across power cycles.  
Enable Warning ASC. When this bit = 0, reporting of thermal warming is disabled.  
EWASC  
DExcpt  
1
0
When this bit = 1, thermal warning reports are enabled.  
Disable Exceptions. This bit is used to enable or disable SMART exception reporting.  
When this bit = 0, SMART exception reporting is enabled.  
When this bit = 1, all SMART functions are disabled, including reporting SMART ex-  
ceptions, running the prediction algorithm, and accumulating SMART data.  
When this bit = 0, the test function is disabled.  
When this bit = 1, the disk drive reports false SMART trip reports as prescribed in the  
MRIE field (see below). Interval timer field and report count and method fields apply.  
When the test bit forces a SMART failure, the failure is reported with a sense code/qual-  
ifier of 5D/FF.  
Test  
0
When this bit = 0, it indicates that log sense information is vendor-unique.  
NOTE: LogErr = 0 is the only value supported.  
LogErr  
MRIE  
0
4
Method of Reporting Informational Exceptions. The value within this field indicates the  
method that will be used by the disk drive to report informational exception conditions,  
as shown in Table 5-84. The relative priority of reporting of multiple informational ex-  
ceptions is vendor-specific.  
This field indicates the period, in 100 millisecond increments, for reporting that an in-  
formational exception condition has occurred. The disk drive will not report such con-  
ditions more frequently than the time specified by the Interval Timer field and as soon  
as possible after the timer interval has elapsed. After the condition has been reported,  
the interval timer restarts.  
Interval  
Timer  
A value of 0 in the Interval Timer field indicates that the disk drive will only report the  
informational exception condition once. A value of FFFFFFFFh in the Interval Timer  
field indicates that the timer interval is vendor-specific.  
0
If the disk drive’s predictor detects a SMART threshold trip, it reports the failure only  
if it has not reported a failure within the last interval timer period. A value of 0 means  
that there is no required waiting between SMART reports.  
NOTE: The Interval Timer field does not apply to MRIE mode 6.  
The value contained in this field indicates the number of times to report an informational  
exception condition to the application client. A value of 0 in this field indicates there is  
no limit on the number of times the disk drive will report an informational exception  
condition.  
Each time the disk drive detects a SMART failure, the SMART status is reported the  
number of times indicated by the value of the Report Count field.  
Report Count  
1
The disk drive then resets its cumulative values and continues with its predicting activ-  
ity. The SMART threshold trip remains permanent (or until a LOG SELECT command  
clears it) and can be retrieved at any time using MRIE mode 6.  
NOTE: The Report Count field does not apply to MRIE mode 6.  
Maxtor Atlas 10K V  
5-61  
 
Table 5-84 Codes Used by the MRIE Field  
Field  
Description  
No reporting of informational exception condition. This method instructs the disk drive not to report these  
conditions.  
0h  
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 Ar-  
chitecture Model and the relevant Protocol Standard. The sense key will be set to RECOVERED ERROR  
and the additional sense code will indicate the cause of the informational exception condition.  
1h  
2h  
Generate Unit Attention. This method of reporting instructs the disk drive to report informational excep-  
tion conditions by returning a CHECK CONDITION status on any command.  
The sense key is set to UNIT ATTENTION and the additional sense code will indicate the cause of the  
information exception condition. The command that has the CHECK CONDITION will not be executed  
before the informational exception condition is reported.  
Conditionally Generate Recovered Error. This method of reporting instructs the disk drive to report infor-  
mational exception conditions dependent on the value of the PER bit of the Error  
Recovery Parameters Mode Page, by returning a CHECK CONDITION status on any command. The  
sense key will be set to RECOVERED ERROR and the additional sense code will indicate the cause of  
the informational exception condition. The command that has the CHECK CONDITION will complete  
before and informational exception condition is reported.  
3h  
4h  
Unconditionally Generate Recovered Error. This method of reporting instructs the disk drive to report in-  
formational exception conditions regardless of the value of the PER bit of the Error Recovery Parameters  
Mode Page, by returning a CHECK CONDITION status on any command. The sense key will be set to  
RECOVERED ERROR and the additional sense code will indicate the cause of the informational excep-  
tion condition. The command that has the CHECK CONDITION will complete without error before any  
informational exception condition will be reported.  
Generate No Sense. This method of reporting instructs the disk drive to report informational exception  
conditions by returning a CHECK CONDITION status on any command. The sense key will be set to NO  
SENSE and the additional sense code will indicate the cause of the informational exception condition. The  
command that has the CHECK CONDITION will complete without error before any informational excep-  
tion condition is reported.  
5h  
6h  
Only Report Informational Exception Condition On Request. This method of reporting instructs the disk  
drive to preserve the informational exception(s) data. To learn about these exception conditions, the ap-  
plication client polls the disk drive via an unsolicited REQUEST SENSE command. The sense key is set  
to NO SENSE and the additional sense code will indicate the cause of the informational exception condi-  
tion.  
7h – Bh  
Ch – Fh  
Reserved.  
Vendor-specific.  
5-62  
Maxtor Atlas 10K V  
 
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),  
Header (10 Byte) — Data Format and Table 5-87 for the Mode Parameter Block  
Descriptor – Data Format. See Table 5-48 for mode parameter block field  
descriptions.  
Table 5-85 MODE SELECT (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (55h)  
PF  
1
Reserved  
Reserved  
SP  
2 - 6  
7 - 8  
9
Reserved  
Parameter List Length  
Control  
Table 5-86 Mode Parameter Header (10-Byte)-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 1  
Mode Data Length  
(LSB)  
2
3
Medium Type  
Device-Specific Parameter  
Reserved  
4 - 5  
(MSB)  
6 - 7  
Block Descriptor Length  
(LSB)  
Table 5-87 Mode Parameter Block Descriptor-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 - 3  
4
(MSB)  
Number of Blocks  
Density Code  
(LSB)  
(MSB)  
5 - 7  
Block Length  
(LSB)  
Maxtor Atlas 10K V  
5-63  
     
Table 5-88 Mode Parameter Block Descriptor-Field Descriptions  
Data Field  
Description  
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.  
Number of  
Blocks  
The Density Code field is unique for each device type. Direct access devices value is  
zero.  
Density Code  
Block Length  
The value in this field specifies the length in bytes of each logical block described by  
the block descriptor.  
5-64  
Maxtor Atlas 10K V  
 
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-89 MODE SENSE (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
4
5
Operation Code (1Ah)  
DBD  
Reserved  
Reserved  
PC  
Page Code  
Sub Page Code  
Allocation Length  
Control  
Table 5-90 MODE SENSE Command-Field Descriptions  
Data Field  
Description  
Disable Block Descriptor. When the value is 0, the drive returns its Block Descriptor  
followed by the requested page(s). When the value is 1, the drive returns only the re-  
quested pages.  
DBD  
Page Control. Determines which type of page values are returned. These values are:  
00b Current  
01b Changeable  
10b Default  
11b Saved  
PC  
The Page Code field determines the pages to be returned to the initiator in the com-  
mand's data-in buffer transfer. Refer to Table 5-49 and Table 5-93 for a complete list of  
the Mode Pages (changeable and read-only). A Page Code of 3Fh causes all supported  
pages to be returned.  
Page Code  
The Sub Page Code field determines the sub pages to be returned to the initiator in the  
command's data-in buffer transfer. A Sub Page Code of 0xFF causes all supported sub  
pages to be returned.  
Sub Page Code  
Table 5-91 Mode Parameter Header (6 Byte)-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
3
Mode Data Length  
Medium Type  
Device-Specific Parameter  
Block Descriptor Length  
Maxtor Atlas 10K V  
5-65  
     
Table 5-92 Mode Parameter Header and Block Descriptor-Field Descriptions  
Data Field  
Description  
Mode Data Length  
Medium Type  
Length of the returned data  
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  
Number of Blocks  
If DBD is 1, then the Block Descriptor Length is eight (8).  
The value in this field specifies the number of logical blocks on the unit that are affected by the  
current MODE SELECT command. When this field = 0, the MODE SELECT parameters are put  
into effect for all logical blocks on the unit. The maximum value allowed is the total number of  
initiator-addressable logical blocks for the value specified in the Block Length field. A value that  
is less than the maximum value will decrease the number of initiator-accessible logical blocks to  
the amount specified.  
Block Length  
The value in this field specifies the length, in bytes, of each block.  
5.14.1  
Read-Only Mode Pages  
Table 5-93 lists read-only mode pages. Table 5-49 lists initiator-changeable mode pages.  
Table 5-93 Read-Only Mode Pages  
Page Code (Sub Page)  
Page Name  
Reports the drive's  
Size (bytes)  
03h  
Format Device  
Medium format  
24  
Total cylinder head and  
rotational speed  
04h  
Rigid Disk Geometry  
24  
5.14.2  
Format Device Page (03h)  
The Format Drive Page (Table 5-94) describes the drive's medium format.  
The data fields are described in Table 5-95. Note that the page is savable but no  
parameters are changeable.  
Table 5-94 Format Device Page-(Page 3)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
PS  
Rsvd  
Page Code (03h)  
1
Page Length (16h)  
Tracks Per Zone  
2 - 3  
4 - 5  
6 - 7  
8 - 9  
Alternate Sectors/Zone  
Alternate Tracks/Zone  
Alternate Tracks/Logical Unit  
Sectors/Track  
10 - 11  
12 - 13  
14 - 15  
16 - 17  
18 - 19  
20  
Data Bytes/Physical Sector  
Interleave  
Track Skew Factor  
Cylinder Skew Factor  
SURF  
SSEC  
HSEC  
RMB  
Reserved  
5-66  
Maxtor Atlas 10K V  
     
21 - 23  
Reserved  
Maxtor Atlas 10K V  
5-67  
Table 5-95 Format Device Page-Field Descriptions (Page 3)  
Field  
Description  
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.  
PS  
Tracks/Zone  
The number of physical tracks per cylinder.  
Alternate  
Sectors/Zone  
The number of spare locations within a notch.  
Alternate Tracks/  
Zone  
The drive does not have any alternate tracks.  
Alternate Tracks/  
Logical Unit  
The number of tracks reserved for defect handling.  
The number of Physical Block Address sectors per track. The value depends on the  
Notch value selected in the Notch and Partitions page.  
Sectors/Track  
Data Bytes/  
This value is the current disk sector size.  
The drive does not support interleave.  
Physical Sector  
Interleave  
Track Skew  
Factor  
The number of physical sectors between the last logical sector on one track and the  
first logical sector on the next track within a cylinder.  
Cylinder Skew  
Factor  
The number of physical sectors between the last logical sector on one cylinder and  
the first logical sector on the next cylinder.  
SSEC  
HSEC  
RMB  
The drive does not use soft sector formatting.  
The drive supports hard sector formatting only.  
The drive does not support removable logical media.  
A Surface bit value of 0 indicates that the drive allocates progressive addresses to  
all logical blocks within a cylinder prior to allocating addresses on the next cylin-  
der.  
SURF  
5-68  
Maxtor Atlas 10K V  
 
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-96 Rigid Disk Geometry Page-(Page 4)  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
1
PS  
Rsvd  
Page Code (04h)  
Page Length (16h)  
Number of Cylinders  
Number of Heads  
2 - 4  
5
6 - 8  
Starting Cylinder - Write Precompensation  
Starting Cylinder - Reduced Write Current  
Drive Step Rate (0)  
9 - 11  
12 - 13  
14 - 16  
17  
Landing Zone Cylinder  
Reserved  
RPL  
18  
Rotational Offset  
19  
Reserved  
20 - 21  
22 - 23  
Medium Rotation Rate  
Reserved  
Maxtor Atlas 10K V  
5-69  
 
Table 5-97 Rigid Disk Geometry Page-Field Descriptions (Page 4)  
Field  
Description  
Parameters Savable. This bit is only used with the MODE SENSE com-  
mand. 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.  
PS  
Number of Cylinders  
Number of Heads  
Starting Cylinder  
The number of physical cylinders that hold host data.  
The number of heads that can access host data.  
The value in this field is the physical cylinder at  
which write precompensation is to begin. The first cylinder number is 0. If  
the starting cylinder is equal to the value in the Number of Cylinders field,  
write precompensation is disabled.  
Write  
Precompensation  
Starting Cylinder  
Reduced Write  
Current  
The value in this field is the physical cylinder at which write current is re-  
duced. The first cylinder number is 0. If the starting cylinder for reduced  
write current is equal to the value in the Number of Cylinders field, reduced  
write current is disabled.  
Drive Step Rate  
Applies to stepper-motor actuators. Not applicable.  
This field indicates a two’s complement location where the drive positions  
the disk heads. A negative value indicates that the heads are positioned be-  
low cylinder 0 by that number of cylinders. A positive value greater than the  
number of cylinders indicates that the heads are positioned beyond the cyl-  
inders used for data storage at the location specified.  
Landing Zone  
Cylinder  
Rotational Position Locking is used for spindle synchronization in storage  
arrays. The modes are:  
00b – Disabled  
10b – Master  
RPL  
01b – Slave  
11b – Not supported  
RPL can be overridden if the Maxtor (Vendor) Special Function Control  
page Auto field value = 1. This drive does not support spindle synchroniza-  
tion.  
Rotational Offset indicates the amount of rotational offset that the drive  
uses when synchronized. The rotational offset is applied in the retarded di-  
rection (lagging the synchronized spindle master). The value in the field is  
determined by the following formula:  
Offset = 0 … 255  
256  
Rotational Offset  
For example, a numerator of 128 indicates an offset of 1/2 revolution  
(180°).  
The valid parameter values are 0 to 255.  
The specified value may be rounded. Rotational offset is not used when the  
drive is configured as the synchronized-spindle master.  
Medium Rotation Rate  
The disk rotation speed in RPM.  
5-70  
Maxtor Atlas 10K V  
 
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,  
for Mode Parameter Block Descriptor – Data Format. Refer to Table 5-90,Table 5-  
Table 5-98 MODE SENSE (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (5Ah)  
DBD  
Reserved  
Reserved  
2
PC  
Page Code  
3
Sub Page Code  
Reserved  
4 – 6  
(MSB)  
7 – 8  
9
Allocation Length  
Control  
(LSB)  
Table 5-99 Mode Parameter Header (10 Byte)-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 1  
Mode Data Length  
(LSB)  
2
Medium Type  
Device-Specific Parameter  
Reserved  
3
4 - 5  
6 - 7  
Block Descriptor Length  
Field Descriptions for the Mode Parameter Header are given in the table that follows.  
Table 5-100 Mode Parameter Block Descriptor-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 3  
4
Number of Blocks  
Density Code  
(LSB)  
(MSB)  
5 - 7  
Block Length  
(LSB)  
Maxtor Atlas 10K V  
5-71  
     
Table 5-101 Mode Parameter Header & Block Descriptor-Field Descriptions  
Data Field Description  
Mode Data Length  
Medium Type  
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.  
Device Specific  
Parameter  
The value = 0 if no Block Descriptor is supplied; the length is 8 if a block descriptor is  
supplied.  
Block Descriptor Length  
Density Code  
Ignored by the drive.  
The value in this field specifies the number of logical blocks on the unit that are affected  
by the current MODE SELECT command. When this field = 0, the MODE SELECT  
parameters are put into effect for all logical blocks on the unit. The maximum value al-  
lowed is the total number of initiator-addressable logical blocks for the value specified  
in the Block Length field. A value that is less than the maximum value will decrease the  
number of initiator-accessible logical blocks to the amount specified.  
Number of Blocks  
Block Length  
The value in this field specifies the length, in bytes, of each logical block.  
5-72  
Maxtor Atlas 10K V  
 
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.  
Note that a if device that has RESERVE (10), RESERVE (6), extent reservations, or  
SCSI Media Changer (SMC) element reservations active receives a PERSISTENT  
RESERVATION IN command, the PERSISTENT RESERVATION IN  
command is rejected with a RESERVATION CONFLICT status reported.  
Table 5-102 illustrates the format of the PERSISTENT RESERVATION IN  
command. Table 5-103 explains the data fields of the command.  
Table 5-102 PERSISTENT RESERVATION IN Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (5Eh)  
1
Reserved  
Service Action  
2 - 6  
Reserved  
(MSB)  
Allocation Length  
(LSB)  
7 – 8  
9
Control  
Maxtor Atlas 10K V  
5-73  
 
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.  
Service action codes available are:  
Code Name Description  
00h Read Keys Reads all registered Reservation keys  
01h Read Reservations Reads all current persistent reservations  
02 – 1Fh Reserved  
A “Read Keys” service action requests that the device server return a parameter list that includes  
a header and a complete list of all of the reservation keys currently registered with the device serv-  
er. If multiple initiators have registered with the same key, then the key is listed multiple times,  
once for each registration. Refer to Table 5-104 and Table 5-105 for information about Read Keys  
parameter data.  
A “Read Reservation” service action requests that the device server return a parameter list that  
contains a header and a complete list of all persistent reservations that are presently active in the  
device server and its extents. Note that duplicate persistent reservations from the same initiator are  
not reported. Refer to Table 5-108 and Table 5-107 for information about Read Reservations pa-  
rameter data.  
Allocation  
Length  
This field indicates how much space has been reserved for the returned parameter list (Read Keys  
or Read Reservations parameters). The actual length of the parameter data is indicated in the pa-  
rameter data field for those parameters.  
If the Allocation Length is not sufficient to contain the entire list of parameters, the first portion  
of the list that does fit is returned. If it is determined that the remainder of the list is required, the  
client should send a new PERSISTENT RESERVATION IN command with an Allocation Length  
field large enough to contain the entire list of parameters.  
The data format and field descriptions for the Read Keys Parameters are described in  
Table 5-104 Read Keys Parameters-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
(MSB)  
0 - 3  
Generation  
(LSB)  
(LSB)  
(MSB)  
4 - 7  
Additional Length (n – 7)  
(Reservation Key List Follows in Bytes 8 – n)  
(MSB)  
(MSB)  
8 - 15  
First Reservation Key  
(LSB)  
(LSB)  
n – 7 to n  
Last Reservation Key  
5-74  
Maxtor Atlas 10K V  
   
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 PER-  
SISTENT RESERVATION OUT command requests a Register, Clear, Pre-empt, or Pre-empt and  
Clear operation. Note that PERSISTENT RESERVATION IN commands do not increment the  
counter, nor do PERSISTENT RESERVATION OUT commands that perform a Reserve or Re-  
lease service action, or by a PERSISTENT RESERVATION OUT command that is not done due  
to an error or a reservation conflict. The value in the Generation field is set to 0 as part of the power  
on or reset processes.  
Generation  
The value in the Generation field allows the application client that examines the value to verify  
that the configuration of the initiators attached to a logical unit has not been modified by another  
application client without any notification of the application client doing the examination.  
This field contains the count of the number of bytes that are in the Reservation Key list (bytes 8 –  
n). Note that this field contains the number of bytes in the reservation key list regardless of the  
value prescribed by the Allocation Length field in the command’s CDB.  
Additional  
Length  
Each of the Reservation Keys appear as items in a list as bytes 8 through n. Each entry reflects an  
8-byte reservation key registered with the device server via the PERSISTENT RESERVATION  
OUT, Reserve, Pre-empt, Pre-empt and Clear, or Register service actions. Each key can be exam-  
ined by the application client for correlation with a set of initiators and SCSI ports  
Reservation Keys  
The data format and field descriptions for the Read Reservations Parameters are  
Table 5-106 Read Reservations Parameters-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 3  
4 - 7  
8 - n  
Generation  
(LSB)  
(LSB)  
(MSB)  
(MSB)  
Additional Length (n – 7)  
Reservation Descriptors  
(See Figure 5-53 / Table 5-55 for detail of a Descriptor Field)(LSB)  
Maxtor Atlas 10K V  
5-75  
   
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 PER-  
SISTENT RESERVATION OUT command requests a Register, Clear, Pre-empt, or Pre-empt and  
Clear operation. Note that PERSISTENT RESERVATION IN commands do not increment the  
counter, nor do PERSISTENT RESERVATION OUT commands that perform a Reserve or Re-  
lease service action, or by a PERSISTENT RESERVATION OUT command that is not done due  
to an error or a reservation conflict. The value in the Generation field is set to 0 as part of the power  
on or reset processes.  
Generation  
The value in the Generation field allows the application client that examines the value to verify  
that the configuration of the initiators attached to a logical unit has not been modified by another  
application client without any notification of the application client doing the examination.  
This field contains the count of the number of bytes of Reservation descriptors (bytes 8 – n). Note  
that this field contains the number of bytes regardless of the value prescribed by the Allocation  
Length field in the command’s CDB.  
Additional  
Length  
One Reservation descriptor is reported for each unique persistent reservation on the logical unit  
when the PERSISTENT RESERVATION IN command has indicated a Read Reservations action.  
Table 5-112 and Table 5-109 detail the contents of each Reservation Descriptors field.  
Reservations De-  
scriptors  
The data format and field descriptions for the PERSISTENT RESERVATION IN  
Read Reservations Descriptor are described in Table 5-108 and Table 5-109  
respectively.  
Table 5-108 PERSISTENT RESERVATION IN Read Reservations Descriptor-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 7  
Reservation Key  
Scope-Specific Address  
Reserved  
(LSB)  
(LSB)  
(MSB)  
(MSB)  
8 - 11  
12  
13  
Scope  
Type  
14 - 15  
Extent Length  
(LSB)  
5-76  
Maxtor Atlas 10K V  
   
Table 5-109 PERSISTENT RESERVATION IN Read Reservations Descriptor-Field Descriptions  
Data  
Description  
Field  
Reserva-  
tion Key  
The Reservation key field contains an 8-byte value that identifies the reservation key under which the per-  
sistent reservation is held.  
If the Scope field (Byte 13, bits 4 – 7) represents an “Extent” reservation, the Scope-Specific Address field  
contains the logical block address (LBA) of the first block of the extent and the Extent Length field (Bytes  
14 – 15) contains the number of blocks in the extent.  
Scope-  
Specific  
Address  
If the Scope field represents an “Element” reservation, the Scope-Specific Address field contains the Ele-  
ment address, zero-filled in the most significant bytes to fit the field and the Extent Length field is set to  
zero.  
The value in this field indicates whether a persistent reservation applies to an entire logical unit, to a part  
of the logical unit (defined as an extent), or to an element.  
The values for the Scope field are:  
Code Name Description  
0h LU Logical Unit. Persistent reservation applies to the full logical unit. The LU scope is therefore imple-  
mented by all device servers that implement PERSISTENT RESERVATION OUT.  
1h Extent Persistent reservation applies to the specified extent. When Extent is the scope, it indicates that  
the persistent reservation applies to the extent of the logical unit defined by the Scope-Specific Address and  
Extent Length fields in the PERSISTENT RESERVATION OUT command’s parameter list. Note that an  
extent is defined only for devices defining contiguous logical block addresses. The Extent scope is optional  
for all device servers that implement PERSISTENT RESERVATION OUT.  
Scope  
2h Element Persistent reservation applies to the specified element. When Element is the scope, it indicates  
that the persistent reservation applies to the element of the logical unit defined by the Scope-Specific Ad-  
dress field in the PERSISTENT RESERVATION OUT parameter list. An element is as defined by the  
SCSI-3 Medium Changer Commands (SMC) standard. The Element scope is optional for all device servers  
that implement PERSISTENT RESERVATION OUT.  
3h – Fh Reserved  
The value of the Type field specifies the characteristics of the persistent reservation being established for  
all data blocks within the extent or within the logical unit. Refer to Table 5-56 for the applicable Type codes  
and their meanings  
Type  
Table 5-110 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).  
Maxtor Atlas 10K V  
5-77  
 
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.  
WRITES: Prohibited; any command from any initiator that performs a transfer from  
the initiator to the disk results in a reservation conflict.  
0h  
READ Shared  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical  
unit, extents, or elements as long as the persistent reservations do not conflict with any  
reservations already known to the device server.  
READS: Shared; any application client on any initiator may execute commands that  
perform transfers from the disk to the initiator.  
WRITES: Exclusive; any command from any initiator other than the initiator that  
holds the persistent reservation that attempts a transfer to the disk results in a reserva-  
tion conflict  
WRITE  
Exclusive  
1h  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical  
unit, extents, or elements as long as the persistent reservations do not conflict with any  
reservations already known to the device server.  
READS: Exclusive; any command from any initiator other than the initiator that holds  
the persistent reservation that attempts a transfer from the disk results in a reservation  
conflict  
WRITES: Shared; any application client on any initiator may execute commands that  
perform transfers to the disk from the initiator.  
2h  
READ Exclusive  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical  
unit, extents, or elements as long as the persistent reservations do not conflict with any  
reservations already known to the device server.  
READS: Exclusive; any command from any initiator other than the initiator holding  
the persistent reservation that attempts a transfer from the disk results in a reservation  
conflict.  
WRITES: Exclusive; any command from any initiator other than the initiator holding  
the persistent reservation that attempts a transfer to the disk results in a reservation  
conflict.  
Exclusive  
Access  
3h  
ADDITIONAL RESERVATIONS: Restricted; any PERSISTENT RESERVATION  
OUT command with the Reserve service action from any initiator other than the ini-  
tiator holding the persistent reservation results in a reservation conflict. The initiator  
that holds the persistent reservation can reserve the logical unit, extents, or elements  
as long as the persistent reservations do not conflict with any reservations already  
known to the device server.  
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.  
4h  
Shared Access  
ADDITIONAL RESERVATIONS: Restricted; any PERSISTENT RESERVATION  
OUT command with the Reserve service action from any initiator other than the ini-  
tiator holding the persistent reservation results in a reservation conflict. The initiator  
that holds the persistent reservation can reserve the logical unit, extents, or elements  
as long as the persistent reservations do not conflict with any reservations already  
known to the device server.  
5-78  
Maxtor Atlas 10K V  
 
Code  
Name  
Description  
READS: Shared; any application client on any initiator may execute commands that  
perform transfers from the disk to the initiator.  
WRITES: Exclusive; any command from an initiator that has not previously per-  
formed a Register service action with the device server that attempts a transfer to the  
disk results in a reservation conflict  
WRITE  
Exclusive,  
Registrants Only  
5h  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical  
unit, extents, or elements as long as the persistent reservations to not conflict with any  
reservations already known to the device server.  
READS: Exclusive; any command from an initiator that has not previously performed  
a Register service action with the device server that attempts a transfer from the disk  
results in a reservation conflict.  
Exclusive  
Access,  
Registrants Only  
WRITES: Exclusive; any command from an initiator that has not previously per-  
formed a Register service action with the device server that attempts a transfer to the  
disk results in a reservation conflict  
6h  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical  
unit, extents, or elements as long as the persistent reservations to not conflict with any  
reservations already known to the device server.  
7h - Fh  
Reserved  
N/A  
Maxtor Atlas 10K V  
5-79  
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.  
Table 5-111 When Do Conflicts Between Existing Reservations and New Reservations Exist?  
Persistent Reservation Already Held  
Persistent Res-  
ervation Being  
Attempted  
WRITE  
Exclusive  
RO  
Exclusive  
Access  
RO  
READ  
Shared  
LU EX  
WRITE  
Exclusive  
LU EX  
READ  
Exclusive  
LU EX  
Exclusive  
Access *  
LU EX  
Shared  
Access *  
LU EX  
LU EX  
LU EX  
LU  
READ Shared  
EX  
N N  
N N  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
N N  
N N  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
N N  
N N  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
N N  
N N  
Y Y  
O O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
N N  
N N  
LU  
WRITE  
Exclusive  
EX  
LU  
READ  
Exclusive  
EX  
LU  
Exclusive  
Access *  
EX  
LU  
Shared  
Access *  
EX  
Y Y  
Y O  
LU  
WRITE  
Exclusive  
RO  
N N  
N N  
EX  
LU  
Exclusive  
Access RO  
EX  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
Y Y  
Y O  
N N  
N N  
N N  
N N  
KEY: LU = Logical Unit Scope  
EX = Extent or Element Scope  
RO = Registrants Only  
* = Conflicts with all reservation requests from other ini-  
tiators.  
N = No Conflict  
Y = Conflict  
O = Conflict occurs if extent or element overlaps  
with existing extent or element  
reservation.  
5-80  
Maxtor Atlas 10K V  
 
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.  
Initiators that perform PERSISTENT RESERVATION OUT actions are identified  
by a reservation key assigned by the application client. The client may use the  
PERSISTENT RESERVATION IN command to identify which other initiators  
within a system hold conflicting or invalid persistent reservations and use the  
PERSISTENT RESERVATION OUT command to preempt those reservations if  
necessary.  
Note that since persistent reservations are not reset by the TARGET RESET task  
management function or other global actions, they can be used to enact device sharing  
among multiple initiators. The PERSISTENT RESERVATION OUT and  
PERSISTENT RESERVATION IN commands provide the means for resolving  
contentions in multiple-initiator systems with multiple port target. By using the  
reservation key to identify persistent reservations, it is possible to determine which  
ports hold conflicting persistent reservations and to take over such reservations from  
failing or “greedy” initiators.  
illustrates the format of the PERSISTENT RESERVATION OUT command. Table  
5-113 explains the data fields of the command.  
Table 5-112 PERSISTENT RESERVATION OUT Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (5Fh)  
Reserved  
Service Action  
2
Scope  
Type  
3 - 6  
Reserved  
(MSB)  
7 – 8  
9
Parameter List Length (18h)  
(LSB)  
Control  
Maxtor Atlas 10K V  
5-81  
 
Table 5-113 PERSISTENT RESERVATION OUT Command-Field Descriptions  
Data Field  
Description  
Service actions that require information about persistent reservation and registrations may require  
enabling of nonvolatile memory within the logical unit.  
Service action codes available are:  
Service Action  
Code  
00h  
01h  
02h  
03h  
Name  
Description  
Register Register a reservation key with the device server  
Reserve Create a persistent reservation using a reservation key  
Release  
Clear  
Release a persistent reservation  
Clear all reservation keys and all persistent reservations  
Pre-  
empt  
04h  
Pre-empt persistent reservations from another initiator  
Pre-  
empt &  
Clear  
Pre-empt persistent reservations from another initiator and  
clear the task set for the pre-empted initiator  
05h  
Re-  
served  
06 – 1Fh  
Reserved  
Refer to Table 5-114 for detailed descriptions of each of the service action codes.  
The value in this field indicates whether a persistent reservation applies to an entire logical unit, to  
a part of the logical unit (defined as an extent), or to an element.  
Scope  
The values for the Scope field are:  
Code  
Name  
Description  
Logical Unit. Persistent reservation applies to the full logical  
unit. The LU scope is therefore implemented by all device serv-  
ers that implement PERSISTENT RESERVATION OUT.  
0h  
LU  
Persistent reservation applies to the specified extent.  
When Extent is the scope, it indicates that the persistent reser-  
vation applies to the extent of the logical unit defined by the  
Scope-Specific Address and Extent Length fields in the PER-  
SISTENT RESERVATION OUT command’s parameter list.  
Note that an extent is defined only for devices defining contig-  
uous logical block addresses. The Extent scope is optional for  
all device servers that implement PERSISTENT RESERVA-  
TION OUT.  
1h  
Extent  
Persistent reservation applies to the specified element.  
When Element is the scope, it indicates that the persistent res-  
ervation applies to the element of the logical unit defined by the  
Element Scope-Specific Address field in the PERSISTENT RESERVA-  
TION OUT parameter list. An element is as defined by the  
SCSI-3 Medium Changer Commands (SMC) standard. The El-  
ement scope is optional for all device servers that implement  
PERSISTENT RESERVATION OUT.  
2h  
Re-  
3h – Fh  
Reserved  
served  
The value of the Type field specifies the characteristics of the persistent reservation being estab-  
lished for all data blocks within the extent or within the logical unit. Refer to Table 5-115 for the  
applicable Type codes and their meanings  
Type  
Fields contained in the PERSISTENT RESERVATION OUT parameter list specify the reservation  
keys and extent information required to perform a persistent reservation service action.  
Parameter List  
Length  
The parameter list is 24 bytes in length; the Parameter List Length field contains 24 (18h) bytes.  
5-82  
Maxtor Atlas 10K V  
 
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 Commands 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. The device server holds these reservation  
keys from each initiator that performs a PERSISTENT RESERVATION OUT command  
with a Register service action until the key is changed by a new PERSISTENT RESERVA-  
TION OUT command with Register service action from the same initiator, or until the ini-  
tiator registration is removed by:  
• Powering down the logical unit, if the last  
Activate Persist Through Power Loss  
(APTPL; see Figure 5-55 and Table 5-61)  
received by the device server was 0;  
• Performing a Clear service action;  
00h  
Register  
• Performing a Pre-empt service action;  
• Performing a Pre-empt and Clear service  
action; or  
• Performing a Register service action from the  
same initiator with the value of the service  
action reservation key set to 0.  
When a reservation key has not yet been established or when the reservation key has been  
removed, a reservation key of 0 is used when the initiator performs a PERSISTENT RES-  
ERVATION OUT with the Register service action. When the reservation has been removed,  
no information is reported for the initiator in the Read Keys service action of the resulting  
PERSISTENT RESERVATION IN command.  
A PERSISTENT RESERVATION OUT command with Reserve service action creates a  
persistent reservation with a specified Scope and Type.  
Persistent reservations are not superseded by a new persistent reservation from any initiator  
except by the execution of a PERSISTENT RESERVATION OUT command that specifies  
either a Pre-empt or Pre-empt and Clear service action. New persistent reservations that do  
not conflict with an existing persistent reservation execute normally. Persistent reservations  
of logical units or extents having the same Type value are permitted if no conflicting persis-  
tent reservations are held by another initiator. When these types of overlapping reservations  
are released, each of the extent reservations and logical unit reservations are removed with  
a separate Release service action. Multiple identical reservations from the same initiator are  
all released simultaneously via a single Release service action that matches the reservations.  
01h  
Reserve  
Maxtor Atlas 10K V  
5-83  
 
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 res-  
ervation. Sending of a PERSISTENT RESERVATION OUT command that specifies a Re-  
lease service action when no persistent reservation exists from that initiator does not result  
in an error. Instead, the device server returns a GOOD message without altering any other  
reservation: the reservation key is not changed by the Release service action.  
The device server returns a CHECK CONDITION status for any PERSISTENT RESER-  
VATION OUT command that specifies the release of a persistent reservation held by the  
requesting initiator that matches some but not all of the Scope, Type, Reservation Key, and  
extent values. The sense key is set to ILLEGAL REQUEST and additional sense data is set  
to INVALID RELEASE OF ACTIVE PERSISTENT RESERVATION. Attempts to release  
persistent reservations in which none of the Scope, Type, Reservation Key, and extent val-  
ues match an existing persistent reservation held by the initiator making the request are not  
errors.  
02h  
Release  
An active persistent reservation may also be released by:  
1. Powering off. When the most recent APTPL value received by the device server is 0, a  
power-off performs a hard reset, clears all persistent reservations, and removes all registered  
reservation keys;  
or  
2. Executing a PERSISTENT RESERVATION OUT command from another initiator with  
a persistent reserve service action of Pre-empt or Pre-empt and Clear.  
Note that a Release service action should not be performed if any operations interlocked by  
the persistent reservation have not yet completed.  
A PERSISTENT RESERVATION OUT command with a successful Clear service action  
removes all persistent reservations for all initiators. All reservation keys are also removed.  
Any commands from any initiator that have been accepted by the device server as non-con-  
flicting continue their normal executions.  
03h  
Clear  
A UNIT ATTENTION condition is established for all initiators for the cleared logical unit.  
The sense key is set to UNIT ATTENTION; the additional sense data is set to RESERVA-  
TIONS PREEMPTED.  
Note that applications should not use the Clear action service except during recoveries as-  
sociated with initiator or system reconfiguration, since data integrity may be compromised.  
5-84  
Maxtor Atlas 10K V  
Code  
Name  
Description  
A PERSISTENT RESERVATION OUT command with a successful Pre-empt service ac-  
tion removes all persistent reservations for all initiators that have been registered with the  
Service action Reservation key specified in the PERSISTENT RESERVATION OUT com-  
mand’s parameter list. A persistent reservation is also established for the pre-empting initi-  
ator. Any commands from any initiator that have been accepted by the device server as non-  
conflicting continue their normal executions. If a PERSISTENT RESERVATION OUT  
command is sent that specifies a Pre-empt service action and no persistent reservation exists  
for the initiator identified by the Service action Reservation key, it is not an error condition.  
A UNIT ATTENTION condition is established for the pre-empted initiators. The sense key  
is set to UNIT ATTENTION; the additional sense data is set to RESERVATIONS PRE-  
EMPTED. Commands that follow are subject to the persistent reservation restrictions set by  
the pre-empting initiator.  
The persistent reservation thus created by the pre-empting initiator is defined by the Scope  
and Type fields of the PERSISTENT RESERVATION OUT command and the correspond-  
ing fields of the command’s parameter list.  
04h  
Pre-empt  
The registration keys for the pre-empted initiators are removed by the Pre-empt service ac-  
tion; the reservation key for an initiator that has performed a Pre-empt service action with  
its own Reservation key specified in the Service action Reservation key remains unchanged,  
although all other specified releasing actions and reservation actions are performed.  
Note that persistent reservations are not superseded by a new persistent reservation from any  
initiator except by the execution of a PERSISTENT RESERVATION OUT that specifies  
either the Pre-empt or the Pre-empt and Clear service actions. New persistent reservations  
that do not conflict with an existing persistent reservation execute normally. The persistent  
reservation of a logical unit or extents having the same Type value are permitted if no con-  
flicting persistent reservations other than the reservations being pre-empted are held by an-  
other initiator.  
Note: Service Action (Code) 4 is not supported by Atlas 10K V.  
Maxtor Atlas 10K V  
5-85  
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 Ser-  
vice action Reservation key specified in the PERSISTENT RESERVATION OUT com-  
mand’s parameter list. It also establishes a persistent reservation for the pre-empting  
initiator. Any commands from the initiators being pre-empted are terminated as if an  
ABORT TASK management function had been performed by the pre-empted initiator. If a  
PERSISTENT RESERVATION OUT command is sent that specifies a Pre-empt & Clear  
service action and no persistent reservation exists for the initiator identified by the Service  
action Reservation key, it is not an error condition. If the key is registered, however, the  
Clear portion of the action executes normally.  
A UNIT ATTENTION condition is established for the pre-empted initiators. The sense key  
is set to UNIT ATTENTION; the additional sense data is set to RESERVATIONS PRE-  
EMPTED. Commands that follow, and retries of commands that timed out because there  
were cleared are subject to the persistent reservation restrictions set by the pre-empting ini-  
tiator.  
The persistent reservation thus created by the pre-empting initiator is defined by the Scope  
and Type fields of the PERSISTENT RESERVATION OUT command and the correspond-  
ing fields of the command’s parameter list.  
Pre-empt &  
Clear  
05h  
The Pre-empt & Clear service action clears any ACA or CA condition associated with the  
initiator that is pre-empted and clears any tasks with an ACA attribute from that initiator.  
Any Asynchronous Event Reporting operations in progress that were initiated by the device  
server are unaffected by a Pre-empt and Clear service action.  
The reservation key for the other initiators pre-empted are removed by the Pre-empt & Clear  
service action. The reservation key for an initiator that has sent a Pre-empt & Clear action  
with its own reservation key specified in the service action’s reservation key remains un-  
changed, although all other specified clearing actions, releasing actions, and reservation ac-  
tions are performed.  
Persistent reservations are not superseded by a new persistent reservation from any initiator  
except via execution of a PERSISTENT RESERVATION OUT that specifies either the Pre-  
empt or Pre-empt & Clear service action. New persistent reservations not in conflict with an  
existing persistent reservation execute normally. The persistent reservation of a logical unit  
or extent that has the same Type value is permitted as long as no conflicting persistent res-  
ervations other than the reservations being pre-empted are permitted.  
5-86  
Maxtor Atlas 10K V  
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).  
Table 5-115 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.  
WRITES: Prohibited; any command from any initiator that performs a transfer from the  
initiator to the disk results in a reservation conflict.  
0h  
READ Shared  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical unit,  
extents, or elements as long as the persistent reservations do not conflict with any res-  
ervations already known to the device server.  
READS: Shared; any application client on any initiator may execute commands that  
perform transfers from the disk to the initiator.  
WRITES: Exclusive; any command from any initiator other than the initiator that holds  
the persistent reservation that attempts a transfer to the disk results in a reservation con-  
flict  
WRITE Exclu-  
sive  
1h  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical unit,  
extents, or elements as long as the persistent reservations do not conflict with any res-  
ervations already known to the device server.  
READS: Exclusive; any command from any initiator other than the initiator that holds  
the persistent reservation that attempts a transfer from the disk results in a reservation  
conflict  
WRITES: Shared; any application client on any initiator may execute commands that  
perform transfers to the disk from the initiator.  
2h  
READ Exclusive  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical unit,  
extents, or elements as long as the persistent reservations do not conflict with any res-  
ervations already known to the device server.  
READS: Exclusive; any command from any initiator other than the initiator holding the  
persistent reservation that attempts a transfer from the disk results in a reservation con-  
flict.  
WRITES: Exclusive; any command from any initiator other than the initiator holding  
the persistent reservation that attempts a transfer to the disk results in a reservation con-  
flict.  
3h  
Exclusive Access  
ADDITIONAL RESERVATIONS: Restricted; any PERSISTENT RESERVATION  
OUT command with the Reserve service action from any initiator other than the initiator  
holding the persistent reservation results in a reservation conflict. The initiator that  
holds the persistent reservation can reserve the logical unit, extents, or elements as long  
as the persistent reservations do not conflict with any reservations already known to the  
device server.  
Maxtor Atlas 10K V  
5-87  
 
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.  
4h  
Shared Access  
ADDITIONAL RESERVATIONS: Restricted; any PERSISTENT RESERVATION  
OUT command with the Reserve service action from any initiator other than the initiator  
holding the persistent reservation results in a reservation conflict. The initiator that  
holds the persistent reservation can reserve the logical unit, extents, or elements as long  
as the persistent reservations do not conflict with any reservations already known to the  
device server.  
READS: Shared; any application client on any initiator may execute commands that  
perform transfers from the disk to the initiator.  
WRITE  
WRITES: Exclusive; any command from an initiator that has not previously performed  
a Register service action with the device server that attempts a transfer to the disk results  
in a reservation conflict  
Exclusive,  
5h  
Registrants Only  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the logical unit,  
extents, or elements as long as the persistent reservations to not conflict with any reser-  
vations already known to the device server.  
READS: Exclusive; any command from an initiator that has not previously performed  
a Register service action with the device server that attempts a transfer from the disk re-  
sults in a reservation conflict.  
Exclusive  
WRITES: Exclusive; any command from an initiator that has not previously performed  
a Register service action with the device server that attempts a transfer to the disk results  
in a reservation conflict  
6h  
Registrants  
Only  
ADDITIONAL RESERVATIONS: Allowed; any initiator may reserve the  
logical unit, extents, or elements as long as the persistent reservations  
to not conflict with any reservations already known to the device  
server.  
N/A  
7h - Fh Reserved  
The PERSISTENT RESERVATION OUT command requires a parameter list,  
illustrated in Table 5-116 and defined in Table 5-117. Each of the fields of the  
parameter list are sent for every PERSISTENT RESERVATION OUT command,  
even if the field is not required for the specific Service action and/or Scope values  
Table 5-116 PERSISTENT RESERVATION OUT Parameter List-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 – 7  
(MSB)  
Reservation Key  
Service Action Reservation Key  
Scope-Specific Address  
(LSB)  
(LSB)  
(MSB)  
(MSB)  
8 – 15  
16 – 19  
(LSB)  
20  
21  
Reserved  
Reserved  
APTPL  
5-88  
Maxtor Atlas 10K V  
 
(MSB)  
Extent Length  
22 – 23  
(LSB)  
Maxtor Atlas 10K V  
5-89  
Table 5-117 PERSISTENT RESERVATION OUT Parameter List-Field Descriptions  
Data Field  
Description  
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 com-  
mand is received. If there is no match, the device server returns a RESERVATION CONFLICT  
status. The Reservation Key of the initiator is valid for all Service action and Scope values.  
Reservation Key  
This field contains information needed for 3 service actions: the Register service action, the Pre-  
empt service action, and the Pre-empt & Clear service action. The Service Action Reservation Key  
is ignored for all other service actions.  
For the Register service action, the Service Action Reservation Key field contains the new Reser-  
vation Key to be registered.  
Service Action  
Reservation Key  
For the Pre-empt and the Pre-empt & Clear service actions, the Service Action Reservation Key  
contains the reservation key of the persistent reservations that are being pre-empted. For the Pre-  
empt and the Pre-empt & Clear actions, any failure of the Service Action Reservation Key to  
match any registered keys results in the device server returning a RESERVATION CONFLICT  
status.  
If the Scope is an Extent reservation, this field contains the Logical Block Address of the extent  
and the Extent Length field (bytes 22 – 23) contain the number of blocks in the extent.  
Scope-Specific  
Address  
If the Scope signifies an Element reservation, the Scope-Specific Address field contains the Ele-  
ment Address, zero-filled in the most significant bytes to fit the field; the Extent Length is set to 0.  
If the Service action is Register or Clear, or if the Scope is a Logical Unit reservation, both the  
Scope-Specific Address and Extent Length fields are set to 0.  
Activate Persist Through Power Loss. This bit is valid only for Register service actions; it is ig-  
nored for all other types of service actions.  
Support for APTPL set to 1 is optional. If a device server that does not support APTPL receives a  
1 in that bit in a Register service action, it returns a CHECK CONDITION status, with the sense  
key set to ILLEGAL REQUEST and additional sense data set to INVALID FIELD IN PARAM-  
ETER LIST.  
APTPL  
If the last valid APTPL bit value received by the device server is 0, the loss of power in the target  
releases any persistent reservations and removes all reservation keys. If the last valid APTPL bit  
value is 1, the logical unit retains all persistent reservations and all reservation keys for all initia-  
tors even if power is lost and later returned. The most recently received valid APTPL value from  
any initiator governs the logical unit’s behavior in the event of a power loss.  
5-90  
Maxtor Atlas 10K V  
 
Table 5-118 illustrates which fields are set by the application client and interpreted by  
the device server for each Service and Scope value.  
Table 5-118 Device Server Interpretation of Service and Scope Value  
Parameters  
Element or  
Allowed  
Scope  
Service Action  
Service Action  
Type  
Element  
Reservation Key  
Parameters  
Register  
Reserve  
Ignored  
LU  
Ignored  
Valid  
Valid  
Valid  
Valid  
Valid  
Valid  
Ignored  
Ignored  
Valid  
Valid  
Valid  
Valid  
Valid  
Valid  
Valid  
Ignored  
Ignored  
Ignored  
Ignored  
Ignored  
Ignored  
Ignored  
Ignored  
Valid  
Ignored  
Ignored  
Reserve  
Extent  
Element  
LU  
Extent Valid  
Ignored  
Reserved  
Release  
Ignored  
Release  
Extent  
Element  
Ignored  
Ignored  
LU  
Extent Valid  
Element Valid  
Ignored  
Release  
Clear  
Clear  
Ignored  
Pre-empt  
Ignored  
Pre-empt  
Extent  
Element  
LU  
Valid  
Extent Valid  
Element Valid  
Ignored  
Pre-empt  
Valid  
Pre-empt & Clear  
Pre-empt & Clear  
Pre-empt & Clear  
Valid  
Extent  
Element  
Valid  
Extent Valid  
Element Valid  
Valid  
Maxtor Atlas 10K V  
5-91  
 
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  
Table 5-119 READ (6) Command-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
Operation Code (08h)  
Logical Block Address  
Logical Block Address (continued)  
1
2 - 3  
4
Reserved  
Transfer Length  
Control  
5
Table 5-120 READ (6) Command-Field Descriptions  
Field  
Description  
Specifies the logical block address where the read operation  
will begin.  
Logical Block Address  
Specifies the number of contiguous logical blocks of data to  
transfer. A transfer length of 0 indicates that 256 logical  
blocks will be transferred. Any other value indicates the  
number of logical blocks that will be transferred.  
Transfer Length  
5-92  
Maxtor Atlas 10K V  
   
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  
Table 5-121 READ (10) Command-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
Operation Code (28h)  
DPO FUA  
1
2 - 5  
6
Reserved  
Reserved  
RelAdr  
Logical Block Address  
Reserved  
7 - 8  
9
Transfer Length  
Control  
Table 5-122 READ (10) Command-Field Descriptions  
Field  
Description  
Disable Page Out. When the value is 0, the drive caches the data read, using its normal  
Logical Read Unit policies.  
DPO  
FUA  
When the value is 1, the drive assigns to logical blocks accessed by the READ (10)  
command the lowest priority for being fetched into or retained by the cache.  
Force Unit Access. When the value is 0, the drive is allowed to satisfy the read with  
cache-resident data.  
A value of 1 indicates that the drive accesses the media in performing the command  
before returning GOOD status.  
RelAdr  
Relative Addressing. The drive does not support relative addressing. Must be 0  
Specifies the logical sector address where the read operation will begin.  
Logical Block Address  
Specifies the number of contiguous logical blocks of data to transfer. A transfer length  
of 0 indicates that no logical blocks are to be transferred.  
Transfer Length  
Any other value indicates the number of logical blocks to be transferred. The drive  
returns a CHECK CONDITION status with the correct sense data if the specified  
transfer extends beyond the logical sector space.  
Maxtor Atlas 10K V  
5-93  
   
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. In addition, these commands can be used to verify the caching  
policies of the drive controller or other kinds of diagnostic and verification work.  
Both the READ BUFFER and the WRITE BUFFER commands have a buffer ID  
and a buffer offset data field defined in their Control Descriptor Block. In the  
Combined Header and Data Mode, if both are set to 0, reference is made to a single  
512-byte buffer set aside in the drive controller's data memory (independent of cache).  
This allows an initiator to verify the data path from the controller's data memory to  
the initiator without affecting the drive's internal data caches. The data format and field  
Table 5-123 READ BUFFER Command-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (3Ch)  
Reserved  
Mode  
2
Buffer ID  
Buffer Offset  
Allocation Length  
Control  
3 - 5  
6 - 8  
9
5-94  
Maxtor Atlas 10K V  
 
Table 5-124 READ BUFFER Command-Field Descriptions  
Field  
Description  
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:  
Mode  
Combined Header and Data – In this mode, data to be transferred is preceded by a 4-byte header that  
contains the buffer capacity. The resulting descriptor and data are transferred to the initiator during the  
command’s data-in buffer transfer.  
0000b  
0010b  
Buffer ID must be 0  
Buffer Offset must be 0  
Allocation length must be set to between 0 and 516 (4 bytes of header and up to 512 bytes of data).  
Data Only– In this mode, the data-in buffer transfer contains data from the controller’s memory.  
Buffer ID. When non-zero, the value specifies a specific track line in the controller’s cache. If Buffer  
ID of zero is specified, the buffer referenced is the same as if a Buffer ID of one were specified.  
Buffer Offset. When non-zero, the value of Buffer Offset can range from 0 to one less than the number  
of sectors/track multiplied by 512. This value must be either a zero or a multiple of 512.  
Allocation Length Must be between zero and the maximum number of sectors/track multiplied by 512.  
Descriptor Only  
When requesting a descriptor (a description of the buffer referenced in the Buffer IDfield), the resulting  
data is the offset boundary requirements and the length of each buffer.  
Buffer ID When non-zero, the value specifies a specific track line within the controller’s cache. If Buff-  
0011b  
1010b  
er ID of 0 is specified, the buffer referenced is the same as if a Buffer ID of 1 were specified.  
Buffer Offset Must be zero  
Allocation Length Must be between 4 (header) and the maximum number of sectors/track multiplied  
by 512 + header size.  
Read Data from Echo Buffer  
In this mode, the drive transfers data to the host from the echo buffer. The echo buffer will transfer the  
same data as when the WRITE BUFFER command with the mode field set to echo buffer was issued.  
Buffer ID Ignored.  
Buffer Offset Ignored.  
Maxtor Atlas 10K V  
5-95  
 
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.  
Table 5-125 READ CAPACITY Command-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (25h)  
Reserved  
RelAdr  
2 - 5  
6 - 7  
8
Logical Block Address  
Reserved  
Reserved  
PMI  
9
Control  
Table 5-126 READ CAPACITY Command-Field Descriptions  
Field  
Description  
RelAdr  
Relative Addressing is not supported by the drive; the field must be 0.  
Used in conjunction with the PMI bit. Must be 0 when the PMI bit is 0.  
Logical Block Address  
Partial Media Indicator. When the value in the field is 0, the Returned Log-  
ical Block Address (Table 5-127) is that of the last logical sector of the log-  
ical unit.  
When the value is 1, the Returned Logical Block Address is that of the last  
sector on the same cylinder as the Logical Block Address supplied in the  
Command Descriptor Block's LBA field. That is, the Returned Logical  
Block Address is that of the Logical Block Address before a substantial de-  
lay in data transfer will be encountered).  
PMI  
In either case, Block Length in Bytes (Table 5-127) is the unit's logical sec-  
tor size, as determined by the Block Length field in the Mode parameter  
Block Descriptor.  
Table 5-127 shows the READ CAPACITY Returned Data - Data Format that will  
be sent during the data-in buffer transfer for the command. Refer to the PMI  
description in Table 5-126 for a description of these data fields.  
Table 5-127 READ CAPACITY Returned Data-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 - 3  
4 - 7  
Returned Logical Block Address  
Block Length in Bytes  
5-96  
Maxtor Atlas 10K V  
     
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 data-  
in buffer transfer consists of a four-byte Defect List header (Table 5-132 and  
The READ DEFECT DATA (10) Command Descriptor Block is shown in  
Table 5-136; the data fields are described in Table 5-129.  
Table 5-128 READ DEFECT DATA (10) Command-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (37h)  
Reserved  
2
Reserved  
Plist  
Glist  
Defect List Format  
3 - 6  
Reserved  
(MSB)  
7 - 8  
9
Allocation Length  
Control  
(LSB)  
Maxtor Atlas 10K V  
5-97  
 
Table 5-129 READ DEFECT DATA (10) Command-Field Description  
Description  
Field  
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.  
GList  
When both PList and GList are set to 1, the Primary Defect List and the Grown Defect List are re-  
turned. The Plist is returned followed by the Glist (the lists are not merged). When both are set to  
0, only the Defect List Header (Table 5-132) is reported to the initiator.  
Defect List  
Format  
This field specifies the format in which the defect descriptors are to be returned. The supported for-  
mats are:  
1
000b  
Block Format (Table 5-130).  
Bytes from the Index (Figure 5-63). The data returned  
from this mode does not include defects outside normal  
user space.  
100b  
Physical Sector Format (Table 5-131). Default format.  
The defects returned from this mode do not include de-  
fects outside normal user space.  
101b  
If the number of defect descriptors the SCSI device has assigned does not exceed the capability of  
the ALLOCATION LENGTH field size but contains a value that is insufficient to transfer all of  
the defect descriptors, the defect list length shall not be adjusted to reflect the truncation and the  
device server shall not create a CHECK CONDITION status. The initiator is responsible for  
comparing the defect list length and the allocation length to determine that a partial list was  
received. If the number of defect descriptors the SCSI device has assigned exceeds the capability  
of the ALLOCATION LENGTH field size, the drive shall transfer no data and return a CHECK  
CONDITION status and the sense key shall be set to ILLEGAL REQUEST and the additional  
sense code set to INVALID FIELD IN CBD.  
Allocation  
Length  
1 All in-line spared blocks do not have an associated LBA, and, therefore, will not be  
seen in Logical Block Format.  
Table 5-130 shows the Block Format returned when the Defect List Format is 000b  
Table 5-130 Defect Descriptor-Block Format.  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 - 3  
Defective Block Address  
5-98  
Maxtor Atlas 10K V  
   
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.  
Table 5-131 Defect Descriptor-Bytes From Index Format, or Physical Sector Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 - 2  
3
Cylinder Number of Defect  
Head Number of Defect  
4 - 7  
Defective Bytes From Index / Defective Sector Number  
Table 5-132 Defect List Header -Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Reserved  
1
Reserved  
Plist  
Glist  
Defect List Format  
2 - 3  
Defect List Length  
Table 5-133 Defect List Header-Field Descriptions  
Field  
Description  
Primary Defect List. 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.  
Grown Defect List. When the value is 0, the returned data does not include the Grown Defect List.  
GList  
When the value is 1, the returned data includes the Grown Defect List.  
Defect List  
Format  
This field indicates the format of the descriptors returned. If this differs from the format requested in  
the Command Descriptor Block, a recovered error is returned.  
Defect List  
Length  
This filed indicates the actual number of bytes that follow the defect list header.  
Maxtor Atlas 10K V  
5-99  
     
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).  
The READ DEFECT DATA (12) Command Descriptor Block is shown in Table 5-  
Table 5-134 READ DEFECT DATA (12) Command-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (B7h)  
Plist Glist  
Reserved  
1
Reserved  
Defect List Format  
2 - 5  
(MSB)  
6 - 9  
Allocation Length  
(LSB)  
10  
11  
Reserved  
Control  
Table 5-135 READ DEFECT DATA (12) Command-Field Description  
Description  
Field  
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.  
GList  
When both PList and GList are set to 1, the Primary Defect List and the Grown Defect List are  
returned. The Plist is returned followed by the Glist (the lists are not merged). When both are set  
to 0, only the Defect List Header (Table 5-138) is reported to the initiator.  
Defect List  
Format  
This field specifies the format in which the defect descriptors are to be returned. The supported  
formats are:  
1
000b  
100b  
Bytes from the Index (Table 5-137). The data returned from this mode  
does not include defects outside normal user space.  
101b  
Physical Sector Format (Table 5-137). Default format. The defects re-  
turned from this mode do not include defects outside normal user space.  
Allocation  
Length  
If the number of defect descriptors the SCSI device has assigned does not exceed the capability of  
the ALLOCATION LENGTH field size but contains a value that is insufficient to transfer all of  
the defect descriptors, the defect list length shall not be adjusted to reflect the truncation and the  
device server shall not create a CHECK CONDITION status. The initiator is responsible for  
comparing the defect list length and the allocation length to determine that a partial list was  
received. If the number of defect descriptors the SCSI device has assigned exceeds the capability  
of the ALLOCATION LENGTH field size, the drive shall transfer no data and return a CHECK  
CONDITION status and the sense key shall be set to ILLEGAL REQUEST and the additional  
sense code set to INVALID FIELD IN CDB.  
1
All in-line spared blocks do not have an associated LBA, and, therefore, will not be seen in Logical Block Format.  
5-100 Maxtor Atlas 10K V  
   
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
4
3
2
1
0
0 - 3  
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.  
Table 5-137 Defect Descriptor-Bytes From Index Format, or Physical Sector Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 - 2  
3
Cylinder Number of Defect  
Head Number of Defect  
4 - 7  
Defective Bytes From Index / Defective Sector Number  
Table 5-138 Defect List Header-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Reserved  
1
Reserved  
Plist  
Glist  
Defect List Format  
2 - 3  
4 - 7  
Reserved  
Defect List Length  
Table 5-139 Defect List Header-Field Descriptions  
Field  
Description  
Primary Defect List. When the value is 0, the returned data does not include the Primary Defect  
PList  
GList  
List.  
When the value is 1, the returned data includes the Primary Defect List.  
Grown Defect List. 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.  
Defect List  
Format  
This field indicates the format of the descriptors returned. If this differs from the format requested  
in the Command Descriptor Block, a recovered error is returned.  
Defect List  
Length  
This field indicates the actual number of bytes that follow the defect list header.  
Maxtor Atlas 10K V  
5-101  
       
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. The data format and field descriptions are shown in Table 5-140 and  
Table 5-141 respectively.  
Table 5-140 READ LONG Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (3Eh)  
Reserved  
Correct  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Byte Transfer Length (578)  
Control  
Table 5-141 READ LONG Command Descriptor Block-Field Descriptions  
Field  
Correct  
RelAdr  
Description  
When the value in this field is 1, the drive corrects the data by the ECC before transferring it to  
the initiator. When the value is 0, the drive does not perform ECC correction on the data.  
NOTE: This bit, not the DCR bit of the Read Recovery page, governs the effect of error correction  
for the READ LONG command.  
Relative addressing is not supported by the drive. This value must be 0.  
Logical Block Ad-  
dress  
Specifies the logical sector to read.  
Must be 578. This value reflects the number of bytes spanned by the ECC, including the ECC it-  
self, rounded up to the next word (this is easiest understood in bits: 4096 data bits + 1 force error  
Byte Transfer Length bit + 15 Logical Block Address bits + 16 cross check bits + 2 pad bits + 480 ECC bits + 6 pad bits  
that are not written to media but are only needed for transfer = 4496 bits or 578 bytes). Any other  
value in this field results in a CHECK CONDITION status and the appropriate sense data.  
Table 5-142 shows the format of the data that is returned during the READ LONG  
Command's data-in buffer transfer. The returned data always consists of 512 bytes of  
data, followed by a two LBA bytes, two EDC bytes, and 60 ECC-related bytes.  
Table 5-142 READ LONG Command-Returned Data  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 - 511  
Data (512 Bytes)  
512 - 513  
514 - 515  
516 - 577  
Logical Block Address Bits + Force Error Bit  
EDC (8 Bits)  
60 ECC Bits + 8 Pad Bits  
5-102 Maxtor Atlas 10K V  
     
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.  
Table 5-143 READ SKIP MASK Command-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (E8h)  
Reserved  
(MSB)  
(LSB)  
2 - 5  
6
Logical Block Address  
Skip Mask Length  
Transfer Length  
Reserved  
7 - 8  
9
(MSB)  
VU  
(LSB)  
Flag  
Link  
Table 5-144 READ SKIP MASK Command-Field Description  
Field  
Description  
This field specifies the first logical block of the corresponding READ (10) COMMAND. This al-  
lows a SEEK to begin immediately. The LBA of the following READ (10) command must be the  
same as the LBA of the READ SKIP MASK command,  
Logical Block Ad-  
dress  
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. The mask consists of a sequence of bits where a "1" bit is for the blocks  
of data to be transferred and a "0" for the blocks of data that are to be skipped. The first "1" bit of  
the mask corresponds to the first LBA to be transferred. Any unused bits at the end of the last byte  
in the mask must be set to 0. The mask is transferred in the data-out buffer transfer of the skip mask  
command.  
Skip Mask Length  
Transfer Length  
This field must be equal to the transfer length in the linked READ (10) command. The transfer  
length field must be equal to the number "1" bits in the skip mask. If a READ (10) is used with 0  
as the transfer length, a transfer length of 256 data blocks is implied.  
Maxtor Atlas 10K V  
5-103  
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. The Defect  
List consists of a Defect List Header (Table 5-146) followed by zero or more Defect  
Descriptors (Table 5-148). Table 5-147 contains the field description for the Defect  
List Header. If multiple Logical Block Addresses are specified, they are listed in  
ascending order.  
The REASSIGN BLOCKS Command Descriptor Block is shown in Table 5-145.  
Table 5-145 REASSIGN BLOCKS Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (07h)  
Reserved  
1 - 4  
5
Control  
Table 5-146 REASSIGN BLOCKS Defect List Header-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 - 1  
2 - 3  
Reserved  
Defect List Length  
Table 5-147 REASSIGN BLOCKS Defect List Header -Field Description  
Field  
Description  
The contents of this field indirectly indicates the number of defective Logical Block Ad-  
dresses passed in the Defect List. The value must be four times the number of Defect De-  
scriptors supplied. Zero (0) is a valid value and makes the command a NOP.  
Defect List  
Length  
Table 5-148 REASSIGN BLOCKS Defect Descriptor-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0 - 3  
Defect Logical Block Address  
The drive returns a CHECK CONDITION status if it cannot complete the  
command. If this happens because the drive ran out of spare sectors, the drive sets the  
sense key to MEDIUM ERROR and the additional sense code to NO DEFECT  
SPARE LOCATION AVAILABLE. The sense key and additional sense key are set  
appropriately for any other cause. The Logical Block Address of the first defect  
descriptor not reassigned is returned in the command-specific information field of the  
5-104 Maxtor Atlas 10K V  
       
sense data. If all defects were reassigned, but some other error occurred, then  
FFFFFFFFh is posted in the command-specific field.  
Maxtor Atlas 10K V  
5-105  
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  
Table 5-149 Diagnostic Pages Supported by The Drives  
Page  
Code  
Description  
Size In Bytes  
00h  
Supported Diagnostic Pages  
6
14  
40h  
Translate Address Page (SEND DIAG)  
Translate Address Page (RECEIVE DIAG)  
40h  
14 or more  
The RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block is shown in  
Table 5-150; the data fields are described in Table 5-151.  
To receive one or both of the two diagnostic pages that are available, the initiator first  
sends the desired page code(s) to the drive using a SEND DIAGNOSTICS command.  
The SEND DIAGNOSTICS command tells the drive which page it should return in  
response to the next RECEIVE DIAGNOSTICS RESULTS command. The page  
specified in the most recent SEND DIAGNOSTICS command is always the page  
returned in response to the RECEIVE DIAGNOSTICS RESULTS command.  
Table 5-150 RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (1Ch)  
Reserved  
PCV  
2
Page Code Value  
Allocation Length  
3 - 4  
5
Reserved  
Control  
Table 5-151 RECEIVE DIAGNOSTIC RESULTS Command Descriptor Block-Field Descriptions  
Field  
Description  
Specifies the number of bytes of diagnostic-page results the drive is allowed to send to the  
initiator. A CHECK CONDITION is not returned if this value truncates the information  
available.  
Allocation  
Length  
5-106 Maxtor Atlas 10K V  
     
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
2
1
0
0
1
Page Code (00h)  
Reserved  
2 - 3  
4
Page Length (0002h)  
Supported Diagnostics Pages Page (00h)  
Translate Address Page (40h)  
5
To obtain the Supported Diagnostics Pages list, the initiator must:  
1. Send a Supported Diagnostics Page to the drive with a SEND DIAGNOSTICS  
command (the Page Length in the Supported Diagnostics page must be 0).  
2. Send a RECEIVE DIAGNOSTIC RESULTS command to the drive. The listing  
of Supported Diagnostic Pages is returned by the drive.  
5.27.2  
Translate Address Page (40h)  
The Translate Address Page allows the initiator to translate a logical sector address,  
physical address, or physical bytes for an index address into any one of the other  
formats. The address to be translated is passed to the drive with the SEND  
DIAGNOSTIC command, and the results are returned to the initiator by the  
RECEIVE DIAGNOSTIC RESULTS command.  
Table 5-153 shows the format of the Translate Address Page that is returned in  
response to a RECEIVE DIAGNOSTIC RESULTS command, and Table 5-154  
contains a description of the data fields. Multiple translated addresses are returned if  
the logical sector size is greater than 512 bytes (more than one physical data sector).  
Maxtor Atlas 10K V  
5-107  
 
Table 5-153 Translate Address Page-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
1
Operation Code (40h)  
Reserved  
2 - 3  
Page Length (2 + (8 x n))  
(where n = number of sectors / LBA)  
4
5
Reserved  
Supplied Format =  
000b (LBA)  
RAREA  
ALT-  
SEC  
ALT-  
TRK  
Reserved  
Translate Format =  
101b (Physical Sector)  
1
6 - 8  
9
Translated Address (Cylinder Number)  
1
Translated Address (Head Number)  
1
10 - 13  
Translated Address (Sector Number or Bytes From Index)  
y -  
y + 2  
Translated Address (Cylinder Number)  
Where y = ((n-1) x 8) + 6  
y + 3  
Translated Address (Head Number)  
y + 4  
-
y + 7  
Translated Address (Sector Number or Bytes From Index)  
Note: 1. Bytes 6 through 13: One set of these bytes is required for each  
sector per Logical Block Address.  
Table 5-154 Translate Address Page-Field Descriptions  
Field  
Description  
The Supplied Format field specifies the format of the following Translate Address field. Must be  
000b, which specifies the LBA format.  
Supplied Format  
RAREA  
Reserved Area is not used. Must be 0.  
An Alternate Sector bit of 1 indicates that the translated address from the SEND DIAGNOSTIC  
command is physically located in an alternate sector on the disk.  
ALTSEC  
When ALTSEC is 0, it indicates either that no part of the translated address is located in an alter-  
nate sector of the medium or that the drive is unable to determine this information.  
An Alternate Track bit of 1 indicates either that part or all of the translated address is located on  
an alternate track of the medium or, the drive cannot determine if all or part of the translated ad-  
dress is located on an alternate track.  
ALTTRK  
When ALTTRK is 0, it indicates that no part of the translated address is located on an alternate  
track of the medium  
The Translate Format field specifies the format into which the initiator wants the address translat-  
ed. The value must be 101b, specifying the Physical Sector format.  
Translate Format  
5-108 Maxtor Atlas 10K V  
   
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  
Table 5-155 RELEASE (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (17h)  
3rdPty Third Party Device ID  
Reserved  
Extent  
2
Reservation Identification  
Reserved  
3 - 4  
5
Control  
Table 5-156 RELEASE (6) Command -Field Descriptions  
Field  
Description  
Third Party Release allows an initiator to release a logical unit that was previously reserved. If the  
value in this field is 0, third party release is not requested.  
3rdPty  
When the value is 1, the drive releases the specified logical unit, but only if the reservation was  
made by the initiator using a third-party reservation that requested the release for the same SCSI  
device as specified in the Third Party Device ID field.  
Required if the 3rdPty bit is 1. This field specifies the SCSI ID (0 through 7 only) of the initiator  
whose third party reservation is being released. (This field must be set if the initiator of the original  
third party RESERVE is the source of the RELEASE.)  
Third Party Device  
ID  
Extent  
The drive supports reservations only on entire logical units. The value must be 0.  
Reservation  
Identification  
Any value in this field is ignored by the drive.  
Note: Assuming that the RELEASE Command Descriptor Block is valid, the drive  
always returns a GOOD status for this command. An actual release only hap-  
pens if the initiator has the unit reserved for itself or a third-party initiator.  
Maxtor Atlas 10K V  
5-109  
   
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  
Table 5-157 RELEASE (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (57h)  
Reserved  
3rdPty  
Reserved  
LongID  
Extent  
2
Reservation Identification  
Third Party Device ID  
Reserved  
3
4 - 6  
(MSB)  
Parameter List Length  
(LSB)  
7 - 8  
9
Control  
Table 5-158 RELEASE (10) Command — Field Descriptions  
Field  
Description  
Third Party Release allows an initiator to release a logical unit that was previously reserved. If the  
value in this field is 0, third party release is not requested. If 3rdPty = 1, then the device server will  
release the specified logical unit, but only if the initiator ID, 3rdPty bit, and third party device ID  
are identical when compared to the RESERVE command that established the reservation.  
3rdPty  
If the Long ID bit is set to 1, the Parameter List Length is 8 and the eight bytes of the parameter  
list carry the device ID of the third party device; the contents of the Third Party Device ID in the  
CDB (byte 3) are ignored.  
LongID  
If the Third Party Device ID value that is connected with the reservation release is smaller than  
255, the LongID bit may be 0 and the ID value sent in the CDB. If LongID bit = 0, the Parameter  
List Length field also = 0. If the Third Party Device ID value is greater than 255, LongID = 1.  
Third Party De-  
vice ID  
Device servers that support device IDs greater than 255 will accept commands with LongID = 1;  
device servers that do not support IDs greater than 255 may reject commands with LongID set =  
1. Device ID formats are protocol-specific.  
Parameter List  
Length  
The contents of this field specify the length, in bytes, of the parameter list that will be transferred  
from the initiator to the target.  
Extent  
The drive supports reservations only on entire logical units. The value must be 0.  
Reservation Iden-  
tification  
Any value in this field is ignored by the drive.  
Note: Assuming that the RELEASE Command Descriptor Block is valid, the drive  
always returns a GOOD status for this command. An actual release only hap-  
pens if the initiator has the unit reserved for itself or a third-party initiator.  
5-110 Maxtor Atlas 10K V  
   
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  
Table 5-159 REPORT DEVICE IDENTIFIER Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (A3h)  
Service Action (05h)  
1
Reserved  
2 – 5  
Reserved  
(MSB)  
Allocation Length  
(LSB)  
6 – 9  
10  
11  
Reserved  
Control  
Table 5-160 REPORT DEVICE IDENTIFIER Command Descriptor Block-Field Descriptions  
Field  
Description  
Service Action  
Must = 05h. Any other value forces Check Condition, Illegal Request.  
If the length is not sufficient to contain all of the parameter data, the first  
portion of the data is returned, and this is not considered to be an error.  
The actual length of the parameter data is available in the Identifier  
Length field in the parameter data. If the remainder of the parameter data  
is required, the application client must send a new REPORT DEVICE  
IDENTIFIER command with an Allocation Length field large enough to  
contain all of the data.  
Allocation Length  
The REPORT DEVICE IDENTIFIER command’s parameter list contains a 4-byte  
field that provides the length, in bytes, of the parameter list and the logical unit’s  
identifier. The data format and field descriptions are shown in Table 5-161 and Table  
5-162 respectively.  
Table 5-161 REPORT DEVICE IDENTIFIER Parameter List-Data Format  
Bit  
7
6
5
4
3
2
1
0
Byte  
0 – 3  
4 – n  
(MSB)  
Identifier Length (n – 4)  
Identifier  
(LSB)  
Table 5-162 REPORT DEVICE IDENTIFIER Parameter List-Field Descriptions  
Field  
Description  
This field specifies the length, in bytes, of the Identifier field. If the Al-  
location Length field in the CDB is insufficient in size to transfer all of  
the Identifier, the length is not adjusted to reflect any truncation of infor-  
mation. The Identifier is initially set = 0, and is changed only by a suc-  
cessful SET DEVICE IDENTIFIER command.  
Identifier Length  
Maxtor Atlas 10K V  
5-111  
       
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 re-  
sets, power cycles, and formatting of media.  
Identifier  
5-112 Maxtor Atlas 10K V  
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.  
Table 5-163 REPORT LUNS Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (A0h)  
Reserved  
1 - 5  
(MSB)  
Allocation Length  
(LSB)  
6 – 9  
10  
11  
Reserved  
Control  
Table 5-164 REPORT LUNS Command Descriptor Block-Field Description  
Field  
Description  
If the Allocation Length is not sufficient to contain the logical unit number values for all  
configured logical units, the device server still reports as many logical number values as will  
fit in the Allocation Length.  
Allocation  
Length  
The format of the report of configured logical units is shown in Table 5-165.  
Table 5-165 LUN Reporting Parameter List -Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 3  
4 - 7  
LUN List Length (n – 7)  
Reserved  
(LSB)  
(MSB)  
8 - 15  
n-7 – n  
LUN (first LUN)  
(LSB)  
LUN (last LUN, if more than one)  
The LUN List Length field contains the length in bytes of the LUN list that can be  
transferred. The LUN list length equals the number of logical unit numbers reported  
multiplied by eight. If the allocation length in the CDB is too small to allow transfer  
of information about all of the logical units configured, the LUN list length value is  
not adjusted to reflect the truncation. The data format for the LUN Reporting  
Parameter List is described in Table 5-165.  
Maxtor Atlas 10K V  
5-113  
     
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.  
Table 5-166 REQUEST SENSE Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1 - 3  
4
Operation Code (03h)  
Reserved  
Allocation Length  
Control  
5
Table 5-167 REQUEST SENSE Command Descriptor Block-Field Description  
Field  
Description  
Allocation Length  
The drives can return a maximum of 18 bytes of sense data. The initiator should set  
this field to the maximum value to receive all the sense data.  
5.32.1  
Sense Data Availability  
Sense data is available if the initiator is responsible for an in-progress FORMAT  
UNIT command (Format Progress Indication is available in the Format Progress  
Indication Bytes).  
The drive returns a sense key of NO SENSE and an additional sense code of NO  
ADDITIONAL SENSE INFORMATION if it has no sense data available for the  
initiator.  
For Parallel SCSI disk drives, sense data is available if the previous command from the  
initiator terminated with a CHECK CONDITION status, or if the previous  
command from the initiator ended with an unexpected BUS FREE error.REQUEST  
Clearing Sense Data  
Sense data is cleared from the drive's memory by one of the following conditions:  
• After being returned from a REQUEST SENSE command.  
• As soon as any other command is received from the initiator except  
INQUIRY.  
5-114 Maxtor Atlas 10K V  
   
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.  
Note that any of the previous conditions overwrites the current sense data with the  
sense data describing the error encountered by the REQUEST SENSE command  
(that is, for the condition stated in the first bulleted entry, the new sense data reflects  
that a non-zero reserved bit was detected in the Command Descriptor Block).  
The drive returns a maximum of 18 bytes of sense data. The initiator should set the  
Allocation Length field in the Command Descriptor Block to 18 to receive all sense  
data. If the Allocation Length is set to 0, four bytes of data will be returned (this option  
maintains compatibility with SCSI-1 systems).  
5.32.3  
Sense Data Format for Error Code 70h and Error Code 71h  
The sense data format for error code 70h (current error) and error code 71h (deferred  
error) is shown in Table 5-168; the data fields are defined in Table 5-169. The  
Supported Sense Keys are described in Table 5-170 and the field contents in Table 5-  
171. The Supported Additional Sense Codes and Sense Code Qualifiers are described  
Table 5-168 Sense Data Format for Error Code 70h or 71h-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
2
Valid  
Error Code (70h or 71h)  
Segment Number = 00h  
Rsvd Sense Key  
FileMrk  
= 0  
EOM  
= 0  
ILI  
3 - 6  
7
Information  
Additional Sense Length = 0Ah  
Command-Specific Information  
Additional Sense Code  
8 - 11  
12  
13  
Additional Sense Code Qualifier  
Field Replaceable Unit Code  
Sense-Key Specific  
14  
15  
SKSV  
16 - 17  
Sense-Key Specific (continued)  
Maxtor Atlas 10K V  
5-115  
 
Table 5-169 Sense Data Fields (Error Code 70h)-Field Descriptions  
Field  
Definition  
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.  
Valid  
Either 70h, indicating that current errors are to be reported, or 71h, indicating deferred errors are to be  
reported.  
Error Code  
Segment  
Number  
This feature is not supported and will return a zero value.  
FileMrk  
The File Mark field is reserved for sequential access devices. This field will return a zero value.  
The End-of-Medium field is reserved for sequential access and printer devices. This field will return a  
zero value.  
EOM  
Incorrect Length Indicator. When this bit is set to 1, it indicates that the requested logical sector length  
did not match the logical sector length of the data on the media. This field is only set for incorrect byte  
transfer lengths on a READ LONG and WRITE LONG command descriptor block.  
ILI  
The sense key, additional sense code, and additional sense code qualifier provide a hierarchy of infor-  
mation. The sense key provides the highest level of information about error and exception conditions.  
The additional sense code and qualifier provided more detailed information.  
Sense Key  
The sense keys supported by the drive are described in Table 5-173.  
The Information field contains the following device-type or command-specific information:  
1) The unsigned logical sector address associated with the sense key.  
Information 2) The difference between the requested length and the actual length in either bytes or sectors, as de-  
termined by the command. This difference is called the residue.  
3) A description of each of the drive's supported commands definition for this field is contained in Ta-  
Additional  
Sense  
Length  
The Additional Sense Length field indicates the number of addition sense bytes that can follow. If the  
Allocation Block Length specified in the Command Descriptor Block is too small to transfer all of the  
additional sense bytes, the Additional Sense Length byte value is not adjusted to reflect the truncation.  
Command-  
Specific In-  
formation  
The Command-Specific Information field is valid only for Sense Data for a failed REASSIGN  
BLOCKS command. It contains either the Logical Block Address of the first defect descriptor not re-  
assigned or, if all the defect descriptors were reassigned, FFFFFFFFh.  
The Additional Sense Code field indicates further information related to the error or exception condi-  
tion reported in the sense key. If the drive does not have further related information, the additional  
sense key is set to NO ADDITIONAL SENSE INFORMATION. See Table 5-172.  
Additional  
Sense Code  
Additional  
Sense Code  
Qualifier  
The Additional Sense Code Qualifier field indicates detailed information related to the additional sense  
code. If the drive does not have detailed information, the field is set to 0.  
Field Re-  
placeable  
Unit  
The Field Replaceable Unit Code specifies a unit that has failed:  
Code  
FRU  
1
2
3
Host  
Hard Disk Assembly (HDA)  
Printed Circuit Board Assembly (PCBA)  
Sense-Key Specific Valid bit. This bit is 1 for all sense keys listed in Table 5-170 (exception: NOT  
READY and UNIT ATTENTION/RPL Status Change). The SKSV bit and Sense-Key Specific bytes  
may be 0 when the sense key is NOT READY.  
SKSV  
Sense-Key  
Specific  
The contents of the Sense-Key Specific field are unique to each sense key. Table 5-171 summarizes  
the sense keys for which the drive supplies sense-key specific information. (See SKSV.)  
5-116 Maxtor Atlas 10K V  
 
Table 5-170 Supported Sense Keys  
Sense Key  
Code  
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 CON-  
DITION or COMMAND TERMINATED status because one of the following bits is set  
to 1: File Mark, EOM, or ILI.  
NO SENSE  
0h  
The last command completed successfully with some recovery action performed by the  
drive. Details may be contained in the additional sense bytes and the Information field.  
When multiple recovered errors occur during one command, the choice of which error  
to report (first, last, most severe, etc.) is device specific.  
RECOV-  
ERED ER-  
ROR  
1h  
2h  
3h  
4h  
The logical unit cannot be accessed. Operator intervention may be required to correct  
this condition.  
NOT READY  
The command terminated with a non-recovered error condition that was probably  
caused by a flaw in the medium or an error in the recorded data. This sense key can also  
be returned if the drive is unable to distinguish between a flaw in the medium and a spe-  
cific hardware failure (Sense Key  
MEDIUM  
ERROR  
HARDWARE  
ERROR  
The drive detected a non-recoverable hardware failure while performing the command  
or during a self-test. The error type could be controller failure, device failure, etc.  
The drive detected an illegal parameter in the Command Descriptor Block or in the ad-  
ditional parameters supplied as data for some commands. If the drive detects an invalid  
parameter in the Command Descriptor Block, it terminates the program without altering  
the medium. If the drive detects an invalid parameter in the additional parameters sup-  
plied as data, the drive may have already altered the medium. This sense key may also  
indicate that an invalid IDENTITY message was received.  
ILLEGAL  
REQUEST  
5h  
The drive generates this sense key whenever the drive is reset by a TARGET RESET  
message, a hard reset condition, or by a power-on reset. Other conditions that generate  
a UNIT ATTENTION include:  
The mode parameters in effect for this initiator have been changed by another initia-  
tor.  
• The microcode has been changed.  
UNIT  
ATTENTION  
6h  
• Tagged commands queued for this initiator were cleared by another initiator.  
• INQUIRY data has been changed.  
• The mode parameters in effect for the initiator have been restored from non-volatile  
memory.  
• Other events that require the attention of the initiator.  
DATA  
A Read or Write command was attempted on a sector that is protected for this operation.  
The requested operation was not performed.  
7h  
9h  
Bh  
Eh  
PROTECT  
VENDOR  
SPECIFIC  
This sense key is used to report specific Maxtor conditions.  
ABORTED  
COMMAND  
The drive aborted the command. The initiator may be able to reissue the command suc-  
cessfully.  
MISCOM-  
PARE  
The source data did not match the data read from the medium (i.e., a mismatch).  
Maxtor Atlas 10K V  
5-117  
 
Table 5-171 Sense Key Information Field Contents  
Command  
Sense Key  
Field Contents  
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 au-  
tomatically reallocated by the drive.  
RECOVERED  
ERROR  
FORMAT UNIT  
ILLEGAL  
REQUEST  
The first illegal defect descriptor encountered in the Defect Descriptor List.  
The address of the first bad sector found during the read (possible only when  
PER=1, DTE=0, and DCR=0.). For a RECOVERED ERROR, the last Logi-  
cal Block Address in the error is returned; for a MEDIUM ERROR the first  
Logical Block Address is returned.  
RECOVERED/  
MEDIUM  
READ(6)(10)  
READ LONG  
ERROR  
RECOVERED/  
MEDIUM  
READ(6)(10) error recovery qualifiers apply. The information field echoes  
this command's Logical Block Address field.  
ERROR  
The transfer length residue (requested, minus correct length) if the transfer  
ILLEGAL  
REQUEST  
length is wrong.  
Note: ILI will be set.  
REASSIGN  
BLOCKS  
HARDWARE  
ERROR  
The address of the first logical sector is not reassigned (the drive ran out of  
spare sectors).  
ILLEGAL  
REQUEST  
The first illegal defect descriptor encountered in the Defect Descriptor List.  
The first invalid sector address detected by the command.  
ILLEGAL  
REQUEST  
SEEK(6)(10)  
VERIFY  
WRITE(6)(10) error recovery qualifiers apply. Contains the Logical Block  
Address that may have failed the write or verify (compare) operation. For a  
RECOVERED ERROR, the last Logical Block Address in the error is re-  
turned; for a MEDIUM ERROR the first Logical Block Address is returned.  
RECOVERED/  
MEDIUM  
ERROR  
The address of the first bad sector found during the write. (Possible only when  
PER=1, DTE=0, and DCR=0.) For a RECOVERED ERROR, the last Logical  
Block Address in the error is returned; for a MEDIUM ERROR the first Log-  
ical Block Address is returned.  
RECOVERED/  
MEDIUM  
WRITE(6)(10)  
ERROR  
WRITE(6)(10) error recovery qualifiers apply. This field contains the Logical  
Block Address that may have failed the write or verify (compare) operation.  
For a RECOVERED ERROR, the last Logical Block Address in the error is  
returned; for a MEDIUM ERROR the first Logical Block Address is returned.  
RECOVERED/  
MEDIUM  
WRITE AND  
VERIFY  
ERROR  
RECOVERED/  
MEDIUM  
Write (10) error recovery qualifiers apply. The information field echoes the  
WRITE LONG command’s Logical Block Address.  
WRITE LONG  
ERROR  
The transfer length residue (requested minus correct length) if the transfer  
ILLEGAL  
REQUEST  
length is wrong.  
Note: ILI will be set.  
5-118 Maxtor Atlas 10K V  
 
Table 5-172 Supported Additional Sense Codes and Sense Code Qualifiers (in Hex)  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
No additional sense information  
0x00  
0x00  
0x0B  
0x5D  
0x5D  
0x5D  
0x5D  
0x5D  
0x5E  
0x5E  
0x5E  
0x5E  
0x00  
0x02  
0x03  
0x03  
0x09  
0x0B  
0x0C  
0x0C  
0x15  
0x15  
0x15  
0x15  
0x15  
0x16  
0x16  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x00  
0x01  
0x00  
0x01  
0x02  
0x5B  
0xFF  
0x00  
0x01  
0x02  
0x03  
0x80  
0x00  
0x00  
0x01  
0x00  
0x01  
0x00  
0x01  
0x02  
0x80  
0x81  
0x82  
0x83  
0x00  
0x83  
0x00  
0x01  
0x86  
0x91  
0x92  
0x93  
0x94  
0x95  
0x96  
0x97  
0x98  
0x99  
0x9A  
No Sense  
SMART overtemperature trip  
Smart triggered  
Smart triggered due to Read TA Factor  
Smart triggered due to Write Err Factor  
Smart triggered due to spin retry  
Smart test trigger  
Power State: ACTIVE  
Power State: IDLE  
Power State: STANDBY  
Power State: SLEEP  
0x01  
Rec  
Error  
H-Grown: Backout prev Grown  
No seek complete: recovered  
Write fault: recovered  
Pre-Amp write unsafe: recovered  
Track following error: recovered  
SMART overtemperature trip  
Recovered write error  
Write error - recovered with auto reallocation  
Positioning error detected by read: recovered  
Positioning error detected by read on write: recovered  
Servo Write Not OK assertion: recovered  
Servo Read Not OK assertion: recovered  
Spoke address error: recovered  
Data synchronization mark error: recovered  
Spoke synchronization mark error: recovered  
Recovered data with no ECC applied  
Recovered data with retries  
EC REC SVO MISSED STM  
TA Err-1st. - recovered  
TA Err-2nd. - recovered  
Bad Sync-1st. - recovered  
Bad Sync-2nd. - recovered  
Offtrack Prediction Err-1st. - recovered  
Offtrack Prediction Err-2nd. - recovered  
Head Spoke Num Miscompare-1 - recovered  
Head Spoke Num Miscompare-2 - recovered  
Timeout waiting burst/Spoke-1 - recovered  
Timeout waiting burst/Spoke-2 - recovered  
Maxtor Atlas 10K V  
5-119  
 
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
Possible Bump-1st - recovered  
0x01  
Rec  
Error  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x17  
0x18  
0x18  
0x18  
0x18  
0x1C  
0x40  
0x40  
0x40  
0x41  
0x42  
0x5D  
0x5D  
0x5D  
0x5D  
0x5D  
0x80  
0x80  
0x80  
0x82  
0xA0  
0xA1  
0xA2  
0xA3  
0xA4  
0xA5  
0xA6  
0xA7  
0xA8  
0xA9  
Bump Err-2nd - recovered  
Defective Wdg-1st - recovered  
Defective Wdg-2nd - recovered  
Map'd Wdg-1st - recovered  
Map'd Wdg-2nd - recovered  
Id Err-1st - recovered  
Id Err-2nd - recovered  
Unknown Wdg Err-1st - recovered.  
Unknown Wdg Err-2nd - recovered  
0xAA Shock detected - recovered  
Shock Detected Err-2nd. - recovered  
0xAB  
0xAF  
0xB0  
0xB2  
0xB3  
0xB5  
0x00  
0x02  
0x05  
0x85  
0x00  
0x85  
0x86  
0x8C  
0x86  
0x00  
0x00  
0x01  
0x02  
0x5B  
0xFF  
0x10  
0x11  
0x12  
0x20  
Recovered data with ECC on-the-fly  
Confined sync timeout - recovered  
Context Acquire Timeout - recovered  
Context Acquire Data Addr Valid T/O - recovered  
False SSMF - recovered  
Recovered data with ECC applied  
Recovered data - data auto-reallocated  
Recovered data - recommend reassignment (TA err)  
Recovered data - thermal asperity error  
Requested Defect List Not Found  
EDC check failed - recovered  
Controller FIFO over/underflow error: recovered  
LBA mismatch error: recovered.  
Required HW process did not complete: recovered  
Power On or Self Test failed  
Smart triggered  
Smart triggered due to Write TA Factor  
Smart triggered due to Write Err Factor  
Smart triggered due to spin retry  
Smart test tripped  
Block Slow PLL Error: recovered.  
Split Slow PLL Error: recovered.  
Block state machine disabled: recovered  
Spoke-to-spoke time error: recovered  
5-120 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x02  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x04  
0x19  
0x19  
0x31  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x02  
0x03  
0x03  
0x0C  
0x0C  
0x0C  
0x11  
0x11  
0x11  
0x11  
0x11  
0x11  
0x15  
0x15  
0x15  
0x00  
0x01  
0x02  
0x04  
0x09  
0x80  
0x82  
0x83  
0x84  
0x85  
0x86  
0x88  
0x91  
0x92  
0x01  
0x03  
0x00  
0x80  
0x81  
0x82  
0x83  
0x84  
0x85  
0x86  
0x99  
0x00  
0x01  
0x84  
0x00  
0x02  
0x03  
0x00  
0x04  
0x0C  
0x8B  
0x81  
0x84  
0x00  
0x02  
0x80  
Drive Not Ready  
Not Ready  
Drive Not Ready, in process of coming ready  
Drive Not Ready, use START cmd  
Drive Not Ready, formatting  
Drive Not Ready, self test in progress  
FileSystem Boot Area unreadable @ POR  
File has not been written - can not read  
Error reading diskware file  
Diskware not loaded yet - issue start cmd  
Code jumped to Dead Vector  
Drive Not Ready, config page 8/HDA mismatched  
Error reading Config Page file  
Drive Not Ready, selfscan is running  
NVR image not compatible  
Drive Not Ready, Unknown defect list  
Drive Not Ready, Bad grown defect list  
Drive Not Ready, Format corrupted  
Drive Not Ready, Unknown HW problem  
Drive Not Ready, NVR is Corrupt  
Drive Not Ready, CP section of EEPROM is Corrupt  
Drive Not Ready, Failed HDA test  
Drive Not Ready, Failed PCB test  
Drive Not Ready, PM section of EEPROM is Corrupt  
Drive Not Ready, Flash vector table is Corrupt  
ROM and resident code are incompatible  
No seek complete.  
0x03  
Medium Error  
Pre-Amp write unsafe  
DIAG: Write fault  
Write error  
Write error - auto reallocation failed.  
Write error - recommend reassignment  
Unrecovered read error  
Unrecovered read error - auto reallocate failed  
Unrecovered read error - pending reallocation  
Unrecovered read error - thermal asperity error  
System file has checksum error  
Error reading Diskware vector table file  
Positioning error detected by drive, check UPT  
Positioning error detected by read  
Positioning error detected by write  
Maxtor Atlas 10K V  
5-121  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x03  
0x15  
0x15  
0x15  
0x16  
0x16  
0x19  
0x19  
0x19  
0x19  
0x19  
0x27  
0x31  
0x31  
0x32  
0x32  
0x41  
0x44  
0x44  
0x80  
0x80  
0x80  
0x80  
0x82  
0x02  
0x03  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x81  
0x82  
0x83  
0x00  
0x83  
0x00  
0x01  
0x03  
0x80  
0x81  
0x00  
0x00  
0x01  
0x00  
0x01  
0x86  
0x80  
0x81  
0x00  
0x10  
0x11  
0x12  
0x20  
0x00  
0x00  
0x80  
0x81  
0x82  
0x83  
0x84  
0x85  
0x86  
0x87  
0x88  
0x89  
0x8A  
0x8B  
0x8C  
0x8D  
0x8E  
0x8F  
Servo Write Not OK  
Servo Read Not OK  
Spoke address error  
Medium Error  
Data synchronization mark error  
Spoke synchronization mark error  
MCS is invalid  
Unknown defect list  
Bad grown defect list  
Replacement block bad  
Found two bad RBNs  
Write protected  
Format corrupted  
Format command failed  
No available replacement block  
Failed replacement I/O (servo dead?).  
Required HW process did not complete  
Error writing FileSystem (neg cyl) file  
Error reading FileSystem (neg cyl) file.  
Forced error  
Block Slow PLL Error  
Split SLow PLL Error  
Block state machine disabled error  
Spoke-to-spoke time error  
No seek complete  
0x04  
Hdwe Error  
Write fault  
PES calibration results are bad  
BIAS calibration results are bad  
ID GAMMA calibration values out of range  
Recal record timeout  
Seek fail during feed forward scale Cal.  
Initial track grab failed.  
Seek failure during Bias Calibration  
Seek failure during KT/J Calibration  
Seek failure during PES Calibration  
Recal servo not ready  
Switch Point calibration results are bad  
Recal track number bad  
Seek failure during switch point cal  
Not all Head(s) in USER head map were found alive  
Valid SAMs not found!!!  
Sync To Disk Spokes failed  
5-122 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x04  
Hdwe Error  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x06  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x90  
0x91  
0x92  
0x93  
0x94  
0x95  
0x96  
0x97  
0x98  
0x99  
0x9A  
0x9B  
0x9C  
0x9D  
0x9E  
0x9F  
0xA0  
0xA1  
0xA2  
0xA3  
0xA4  
0xA5  
0xA6  
0xA7  
0xA8  
0xA9  
Invalid CP18 on disk  
Invalid CP21 on disk  
Invalid CP22 in NVR  
Head polarity cal failed.  
Svo: Invalid head polarity vector in CP23  
Seek 1 failure during servo writer erase band resync  
Seek failure during ARCs Calibration  
Seek failure during Pes Linearization  
Error during Pes Lin bode measurement  
Seek 2 failure during servo writer erase band resync  
Seek failure during pes linearization table update  
Motor speed error after turbo spin recovery  
Electrical offset calibration returned an invalid value  
Went servo dead during head polarity/coarse ATT cal.  
Data consistency failure during PES Linearization  
Couldn't find sync in the erase band & couldn't restart servo  
Went servo dead after completing a seek  
Successful sync not in the erase band  
ID GAMMA projected value out of range  
OD GAMMA calibration values out of range  
OD GAMMA projected value out of range  
Could not start estimator on printed media  
Too many spoke errors on printed media-1st  
Too many spoke errors on printed media-2nd  
Too much variation in position at crash stop  
Unable to determine a unique index  
0xAA Too much runout at the crash stop even with BCVs  
0xAB  
0xAC  
Crash stop position too large or too small  
Too much position runout at the crash stop  
0xAD Milli plant mag out of range  
0xAE  
0xAF  
0xB0  
0xB1  
0xB2  
0x00  
0x91  
0x92  
0x93  
0x94  
0x95  
Milli loop mag out of range  
Seek error for gamma frequency  
Seek error for FF Gain  
Cant find good track  
Servo Busy too long  
Track following error  
Svo:TA Err-1st  
Svo:TA Err-2nd  
Svo:Bad Sync-1st  
Svo:Bad Sync-2nd  
Svo: Offtrack Prediction Err-1st  
Maxtor Atlas 10K V  
5-123  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
Svo: Offtrack Prediction Err-2nd.  
0x04  
Hdwe Error  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x09  
0x15  
0x15  
0x32  
0x96  
0x97  
0x98  
0x99  
0x9A  
0x9B  
0x9C  
0x9D  
0x9E  
0xA0  
0xA1  
0xA2  
0xA3  
0xA4  
0xA5  
0xA6  
0xA7  
0xA8  
0xA9  
Svo:Head Spoke Number Miscompare-1st  
Svo:Head Spoke Number Miscompare-2nd  
Svo:Timeout waiting for burst/Spoke-1st  
Svo:Timeout waiting for burst/Spoke-2nd  
Svo: BCV err - 1st  
Svo: BCV err - 2nd  
Svo: Serial port timeout - 1st  
Svo: Serial port timeout - 2nd  
Svo:Possible Bump-1st  
Svo:Bump Err-2nd  
Svo: Timeout waiting for burst/Spoke - 1st  
Svo: Timeout waiting for burst/Spoke - 2nd  
Svo:Map'd Wdg-1st  
Svo:Map'd Wdg-2nd  
Svo:Id Err-1st.  
Svo:Id Err-2nd  
Svo:Unknown Wdg Err-1st  
Svo:Unknown Wdg Err-2nd  
0xAA Svo:Shock detected error-1st  
0xAB  
0xAC  
Svo:Shock detected error-2nd  
Svo: Seek time out  
0xAD Svo: Bad measured timing values  
0xAE  
0xAF  
0xB0  
0xB1  
0xB2  
0xB3  
0xB4  
0xB5  
0xB6  
0xB7  
0xB8  
0xB9  
0xBA  
0xBB  
0xBC  
0x00  
0x02  
0x00  
Svo: Not spinning at proper speed-1st  
Svo: Not spinning at proper speed-2nd  
Svo:Confined sync timeout  
Svo:R/W serial timeout  
Svo:Context Acquire Timeout  
Svo:Context Aquire Data Addr Valid Timeout  
Svo:Context Aquire Bad Track Number  
Svo: False SSMF - 1st  
Svo: False SSMF - 2nd  
Svo: Servo Dead Loading Channel  
Svo: Servo Dead  
Svo: Servo died during sync-to-index  
Svo: Servo Dead Seek Command  
Svo: Bogus seek command type  
Svo: Servo Command Procesor Timeout  
Random positioning error  
Positioning error detected by read  
A-list is full  
5-124 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x3E  
0x3E  
0x03  
0x04  
Logical Unit failed self test  
Logical unit log update failure  
Maxtor Atlas 10K V  
5-125  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x04  
Hdwe Error  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x40  
0x44  
0x44  
0x90  
0x80  
0x82  
0x83  
0x84  
0x85  
0x86  
0x88  
0x89  
0x90  
0x91  
0x92  
0x93  
0x8A  
0x8C  
0x8D  
0x8E  
0xA0  
0xA1  
0xA2  
0xA3  
0xA4  
0xA5  
0xA6  
0xA7  
0xA8  
0xA9  
Unknown HW problem  
Hardware Bug Check (check Info field)  
Failed HDA test.  
Failed PCB test.  
EDC check failed.  
Controller FIFO over/underflow error.  
DIAG: Drive failed to read servowriter serial number.  
DIAG: Failed XOR test.  
EDC Check Failed 0  
EDC Check Failed 1  
EDC Check Failed 2  
EDC Check Failed3  
Servo restart failed after set RPM command  
LBA mismatch error  
ETM test failure, drive failed to spin  
Could not achieve target RPM  
Test did not complete  
Test completed successfully, but failed.  
Invalid parameter was received.  
Invalid data in servo record. Prevented algorithm from completing.  
Servo record did not complete  
Read seek failed  
Write seek failed  
Raw seek failed  
Servo Diagnostic Test running.  
Invalid 97/98 super cmd seq. Must send 97 before 98  
0xAA Super Command 97 already running  
0xAB  
0xAC  
Complex magnitude is zero  
Could not complete the low-level BCV write function  
0xAD Got a divide by zero error in complex divide.  
0xAE  
0xAF  
0xB0  
0xB1  
0xB2  
0xB3  
0xB4  
0x00  
0x84  
0x01  
WGATE negated due to shock or bump during BCV write  
Servo Death occurred during a BVC write operation  
Seek command completion timeout occurred  
Read an impossibility high number of good BCVS on this  
No read passes resulted in enough test BCVs being read  
The last read pass for test BCVs was good but shouldn’t be  
DestinationLoc expected vs actual mismatch. servo death recovery  
Logical assertion (firmware consistency check)  
Insufficient buffer memory for operation  
Serial Port Packet Receive Error  
5-126 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x04  
Hdwe Error  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0x00  
0x01  
0x02  
0x03  
0x81  
0x82  
0x83  
0x84  
0x85  
0x86  
0x87  
0x88  
0x89  
0x8A  
0x8B  
0x8C  
0x8D  
0x8E  
0x8F  
0x90  
0x91  
0x92  
0x93  
0x94  
New wrt cmd overlaps deferred write error  
New wrt cmd overlaps deferred read error  
New rd cmd overlaps deferred write error  
New rd cmd overlaps deferred read error  
Failed to load the FSBA  
a power-up servo calibration failed  
head check failed  
Loading of disk config pages from filesystem failed  
Diskware loaded, but failed validation  
Loading of disware from filesystem failed  
Validation of Vector Table failed  
Failed to load diskware vector table from filesystem  
Servo could not successfully complete pre-diskware calibrations  
Servo couldn’t successfully complete post-diskware calibrations  
config page 19 corrupt  
No disk config pages loaded  
Loading of Orca table has failed  
Loading of log pages from file system has failed  
DBN write/read failed on head  
Diagnostics failed on unit  
Failed to spin up in time  
Head load failed  
FLT bit set in spinup  
Selfscan could not load Script (0x30)  
Maxtor Atlas 10K V  
5-127  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x04  
Hdwe Error  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0x95  
0x96  
0x97  
0x98  
0x99  
0x9A  
0x9B  
0x9C  
Selfscan could not load results (0x31)  
Selfscan could not load Defect (0x32)  
Selfscan could not load Defect Manager files  
Selfscan could not load SuperZoneData file  
Selfscan timeout waiting for drive to come ready  
Load Selfscan overlays failed  
Selfscan overlays do not match firmware  
Failed to lock within TBD seconds0x04/0xA0/0xA0 Spin time-out  
INIT  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0x9D  
0x9E  
0x9F  
0xA0  
0xA1  
0xA2  
0xA3  
0xA4  
0xA5  
0xA6  
0xA7  
0xA8  
0xA9  
Retract timeout  
Drive Not Ready, CP section of EEPROM is Corrupt  
Drive Not Ready, PM section of EEPROM is Corrupt  
Spin time-out - INIT  
Spin time-out - STOP_PENDING  
Spin time-out - BRAKE  
Spin time-out - Stopped  
Spin time-out - PSENSE  
Spin time-out - DOUBLE ALIGN  
Spin time-out - OPEN_LOOP  
Spin time-out - SYNC  
Spin time-out - SYNC2  
Spin time-out - CLOSED_LOOP  
0xAA Spin time-out - CLOSED_LOOP-2  
0xAB Spin time-out - CLOSED_LOOP-3  
5-128 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x04  
Hdwe Error  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xA0  
0xAC  
Spin time-out - SETTLE  
0xAD Spin time-out - STEADY  
0xAE  
0xAF  
0xB0  
0xB1  
0xB2  
0xB3  
0xB4  
0xB5  
0xB6  
0xB7  
0xB8  
0xB9  
0xBA  
0xBB  
0xC0  
0xC1  
0xC2  
0xC3  
0xC4  
0xC5  
0xC6  
0xC8  
0xC9  
0xCA  
0xCB  
0xCD  
0xCE  
0xCF  
Spin time-out - FAULT  
Spin time-out - ETM  
Spin time-out - ROCKSPINDLE  
Spin time-out - ANTILOCK  
Spin time-out - SYNC4BRAKE  
Diablo shutdown due to high temp  
VCM wasn’t updated in time  
Spindle clk is missing  
Sync-to-Index, servo went dead  
Sync-to-Index failed  
No spokes found  
Seeking too long  
Potential spindle out od synch  
fast head switch channel/preamp count mismatch  
Drive Not Ready, NVR G Image copies corrupt  
Drive Not Ready, PM section has invalid version id  
Context acquire timeout  
Track acquire timeout  
Head Pin Layer Reversal  
Heads cannot find servo sync (no PLR but heads with nosyncFound).  
Could not find sync in the erase band  
Could not arm Block State Machine, no matching pairs  
Could not arm Block State Machine, retry exhausted  
Could not arm Block State Machine  
OFM logical list synchronization timeout  
Bias Cal failed during power-up calibrations  
Gamma Cal failed during power-up calibrations  
ARCS Cal failed during power-up calibrations  
Maxtor Atlas 10K V  
5-129  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x05  
Illegal Request  
0x1A  
0x20  
0x20  
0x20  
0x21  
0x24  
0x25  
0x26  
0x26  
0x26  
0x26  
0x26  
0x26  
0x26  
0x26  
0x2C  
0x3D  
0x84  
0x84  
0x84  
0x00  
0x00  
0xFE  
0xFF  
0x00  
0x00  
0x00  
0x00  
0x02  
0x04  
0x80  
0x81  
0x82  
0x83  
0x84  
0x00  
0x00  
0x01  
0x10  
0x11  
Parameter list length error  
Invalid command.  
ETM can't run with motor spinning  
Selfscan code not loaded or bad  
Invalid LBA  
Invalid bits set in CDB  
Invalid LUN specified  
Invalid fields in parameters  
Bad fields in parameters  
Invalid release of persistent reservation  
Invalid Code image checksum failed  
Incorrect product code loaded  
Invalid Offset for image  
Invalid ASIC for this code load  
Invalid Code image - New PCBA cannot take old code  
Invalid command sequence  
Invalid bit set in identify message  
Aborted b/c of internal TO DER of a cmd other than current  
Aborted b/c of internal TO before going to BBR for cur cmd  
Aborted b/c of internal TO BBR of a cmd other than current  
5-130 Maxtor Atlas 10K V  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
SMART overtemperature trip  
0x06  
0x0B  
0x28  
0x29  
0x29  
0x29  
0x29  
0x29  
0x29  
0x29  
0x2A  
0x2A  
0x2A  
0x2A  
0x2A  
0x2f  
0x01  
0x00  
0x01  
0x02  
0x03  
0x04  
0x05  
0x06  
0x86  
0x01  
0x02  
0x03  
0x04  
0x05  
0x00  
0x01  
0x05  
0x01  
0x02  
0x00  
0x01  
0x02  
0x5B  
0x80  
0xFF  
0x00  
Unit Attn  
Not Ready to Ready transition  
Power-On-Reset occurred  
SCSI bus reset occurred  
Bus device reset message  
Recovered from bug check  
Bus mode changed to single ended  
Bus mode changed to LVDS  
Reset after too many ACK's  
Mode parameters were changed  
Log parameters were changed  
Persistent Reservations were cleared  
Persistent Reservations were released  
Registration Preempted  
Cmd Queue cleared by another initiator  
Microcode has been changed  
Device Identifier changed  
Spindle synced  
0x3f  
0x3f  
0x5C  
0x5C  
0x5D  
0x5D  
0x5D  
0x5D  
0x5D  
0x5D  
0x27  
Spindle not synced  
Smart triggered  
Smart triggered due to Write TA Factor  
Smart triggered due to Write Err Factor  
Smart triggered due to spin retry  
Smart test tripped  
0x06  
Unit Attn  
Smart test tripped  
0x07  
Data Protect  
Data write protected  
0x09  
Vendor Specific  
0x81  
0x81  
0x81  
0x81  
0x00  
0x01  
0x02  
0x03  
New command overlaps deferred write error  
New wrt cmd overlaps deferred write  
New rd cmd overlaps deferred write  
New rd cmd overlaps deferred read error  
Maxtor Atlas 10K V  
5-131  
Sense  
Key  
Sense Sense  
Code Qualifier  
Meaning  
0x0B  
Aborted Cmd  
0x00  
0x0E  
0x1B  
0x25  
0x3F  
0x43  
0x45  
0x47  
0x47  
0x47  
0x47  
0x47  
0x48  
0x49  
0x4B  
0x4B  
0x4B  
0x4B  
0x4E  
0x84  
0x1D  
0x00  
0x01  
0x00  
0x00  
0x0F  
0x00  
0x00  
0x00  
0x01  
0x02  
0x03  
0x04  
0x00  
0x00  
0x02  
0x03  
0x04  
0x05  
0x00  
0x00  
0x00  
Aborted.  
Abort: IU too short (data frame with length = 0)  
Abort: Synchronous transfers timeout  
Aborted with invalid LUN  
Aborted: Echo buffer overwritten  
Abort: Message reject error  
Abort: Reselection failed  
Abort: Bus parity error  
Abort: pCRC error detected  
Abort: Bus parity error during ST data phase  
Abort: Information Unit CRC error  
Abort: Async Protection error  
Abort: Initiator detected error  
Aborted with invalid Message  
Abort: Too much write data received  
Abort: ACK/NAK timeout  
Abort: NAK received  
Abort: Data offset error  
Overlapped commands attempted  
Aborted b/c of internal TO in DER for cur cmd  
Data miscompare error  
0x0E  
Table 5-173 Sense-Key Specific Field Contents  
Field  
Contents  
Sense Key  
Initiator Interpretation  
Field pointer  
bytes  
ILLEGAL  
REQUEST  
Illegal field's offset (in the Command Descriptor Block or data-out  
buffer transfer parameters).  
Progress Indica-  
tion  
NOT READY  
Indicates progress of FORMAT UNIT Command.  
RECOV-  
ERED  
Retry count  
Number of retries for I/O operation  
Number of retries for I/O operation  
ERROR  
MEDIUM  
ERROR  
Retry count  
The data format of the Field Pointer bytes associated with the ILLEGAL REQUEST  
Table 5-174 ILLEGAL REQUEST Sense Key Field Pointer Bytes\Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
15  
SKSV =  
1
C/D  
Reserved  
BPV  
Bit Pointer  
5-132 Maxtor Atlas 10K V  
   
16 - 17  
Field Pointer  
Table 5-175 ILLEGAL REQUEST Sense Key Field Pointer Bytes\Field Descriptions  
Field  
SKSV  
C/D  
Description  
Sense-Key Specific Valid  
Command/Data. When the value in this field is 1, the Field Pointer identifies the first  
byte in error in the Command Descriptor Block.  
When 0, the Field Pointer identifies the first byte in error in the data parameters sent  
by the initiator in the data-out buffer transfer.  
BPV  
Bit Pointer Valid. The drive does not support Bit-level resolution; the bit value must  
be 0.  
Bit Pointer  
The drive does not support Bit-level resolution; the bit value must be 0.  
Field Pointer  
Indicates the first byte in error in either the Command Descriptor Block or in the data  
parameters sent by the initiator.  
The data format of the Progress Indication bytes associated with the NOT READY  
sense key is shown in Table 5-176; the description of the data is contained in  
Table 5-176 NOT READY Sense Key - Progress Indication Bytes\Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
15  
SKSV =  
1
Reserved  
16 - 17  
Progress Indication  
Table 5-177 NOT READY Sense Key - Progress Indication Bytes\Field Descriptions  
Field  
Description  
SKSV  
Sense-Key Specific Valid  
Indication of percent complete for the FORMAT UNIT command. The re-  
turned value is the numerator of a fraction that has 65536 (10000h) as the de-  
nominator (Progress Indication/10000h = percent complete).  
Progress Indication  
The data format of the Retry Count bytes associated with the MEDIUM ERROR  
or RECOVERED ERROR sense key is shown in Table 5-178; the description of  
the data is contained in Table 5-179.  
Table 5-178 MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry Count-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
15  
SKSV =  
1
Reserved  
16 - 17  
Retry Count  
Table 5-179 MEDIUM ERROR or RECOVERED ERROR Sense Key - Retry Count  
Maxtor Atlas 10K V  
5-133  
         
-Field Descriptions  
Description  
Field  
SKSV  
Sense-Key Specific Valid  
Retry  
Count  
The number of times an I/O operation was retried  
5-134 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 5-  
Table 5-180 RESERVE (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (16h)  
3rdPty Third Party Device ID  
Reserved  
Extent  
2
Reservation Identification  
Extent List Length  
Control  
3 - 4  
5
Table 5-181 RESERVE (6) Command-Field Descriptions  
Field  
Description  
3rd Pty  
When set to 1, it indicates that the Third Party Device ID field is valid.  
Required and used only when the 3rdPty bit is set, in which case this field specifies the SCSI ID (0  
through 7 only) of the initiator to be granted the reservation of the logical unit. The drive preserves the  
reservation until one of the following occurs:  
• It is superseded by another valid RESERVE command from the initiator.  
• It is released by the same initiator  
• It is released by a TARGET RESET message from any initiator.  
• It is released by a hard reset condition.  
Third  
Party  
Device ID  
The drive ignores any attempt to release the reservation made by any other initiator. For example, if  
ID7 sends ID2 a Third Party reservation on behalf of ID6 (the target at ID2 gets reserved for the initiator  
ID6), then only ID7 can release the target at ID2 (using a Third Party release). ID6 cannot release the  
reservation even though the reservation was made on its behalf.  
Extent  
The drive supports reservations only on entire logical units. The value must be 0.  
Reserva-  
tion Identi- Any value in this field is ignored by the drive.  
fication  
Extent List  
Any value in this field is ignored by the drive.  
Length  
Note: The drive returns RESERVATION CONFLICT status if the unit is already  
reserved for another initiator. Once the reservation is honored, any command  
from another initiator (except INQUIRY or REQUEST SENSE) is rejected  
with RESERVATION CONFLICT status.  
Maxtor Atlas 10K V  
5-135  
   
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-182 RESERVE (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (56h)  
Reserved  
3rdPty  
Reserved  
LongID  
Extent  
2
Reservation Identification  
Third Party Device ID  
Reserved  
3
4 - 6  
(MSB)  
7 - 8  
9
Parameter List Length  
Control  
(LSB)  
Table 5-183 RESERVE (10) Command-Field Descriptions  
Description  
Field  
3rd Pty  
When set to 1, it indicates that the Third Party Device ID field is valid.  
When 0, indicates that the third party device associated with the reservation release has a number  
smaller than 255 and the ID value can be sent within the CDB. If set = 1, indicates that the third  
party device ID is greater than 255, the ID value within the CDB is ignored, and the parameter list  
length is at least eight.  
LongID  
Required and used only when the 3rdPty bit is set, in which case this field specifies the SCSI ID  
of the initiator to be granted the reservation of the logical unit. The drive preserves the reservation  
until one of the following occurs:  
• It is superseded by another valid RESERVE command from the initiator.  
• It is released by the same initiator.  
• It is released by a TARGET RESET message from any initiator.  
• It is released by a hard reset condition.  
Third Party  
Device ID  
The drive ignores any attempt to release the reservation made by any other initiator. For example,  
if ID7 sends ID2 a Third Party reservation on behalf of ID6 (the target at ID2 gets reserved for the  
initiator ID6), then only ID7 can release the target at ID2 (using a Third Party release). ID6 cannot  
release the reservation even though the reservation was made on its behalf.  
If 0, requests that the entire logical unit be reserved for use only by the initiator until the request  
is supplanted by another valid RESERVE command from the same initiator, or until released via  
a RELEASE (10) command from the reserving initiator, a hard reset, or a power on cycle.  
If set = 1, the extent reservation option is implemented. This option allows an application client in  
a multitasking environment to have multiple reservations.  
Extent  
The size of the extent list is defined by the contents of the Parameter List Length field. The extent  
list consists of zero or more descriptors. Each descriptor defines an extent beginning at the speci-  
fied logical block address for the specified number of blocks. If the number of blocks is 0, the ex-  
tent begins at the specified logical block address and continues through the last logical block  
address on the logical unit. The data format of extent descriptors is shown in Table 5-184.  
5-136 Maxtor Atlas 10K V  
   
Table 5-184 Extent Descriptors-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Reserved  
RelAdr  
Reservation Type  
(MSB)  
(MSB)  
1 - 3  
Number of Blocks  
(LSB)  
4 - 7  
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  
READ shared. No write operations are permitted by any initiator to the re-  
served extent. Any initiator may read from the extent.  
00b  
WRITE exclusive. No other initiator may write to the indicated extent.  
Any initiator may read from the extent.  
01b  
10b  
11b  
READ exclusive. While this reservation is active, no other initiator may be  
permitted to read to the indicated extent.  
Exclusive access. While this reservation is active, no other initiator is per-  
mitted any access to the reserved extent.  
RelAdr is always 0: The Maxtor Atlas 10K V hard disk drive does not support relative  
addressing.  
If both the LongID and the Extent bits = 1, then the parameter list takes the format  
Table 5-186 Parameter List When LongID and Extent Bits = 1-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 7  
Third Party Device ID  
Extent Descriptors  
(LSB)  
(MSB)  
8 - n  
(See Figure 5-91 Above)(LSB)  
If the LongID bit = 1 and the Extent bit = 0, then the parameter list length is eight  
and the parameter list has the format shown in Table 5-187.  
Table 5-187 RESERVE (10) ID Only Parameter List-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 - 7  
Third Party Device ID  
(LSB)  
Maxtor Atlas 10K V  
5-137  
       
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. The  
data format is shown in Table 5-188.  
Table 5-188 REZERO UNIT Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (01h)  
Reserved  
1 - 4  
5
Control  
5-138 Maxtor Atlas 10K V  
 
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.  
Table 5-189 SEEK (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (0Bh)  
Logical Block Address  
Logical Block Address  
Reserved  
2 - 3  
4
Reserved  
Control  
5
Maxtor Atlas 10K V  
5-139  
 
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.  
Table 5-190 SEEK (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (2Bh)  
Reserved  
1
2 - 5  
6 - 8  
9
Logical Block Address  
Reserved  
Control  
5-140 Maxtor Atlas 10K V  
 
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  
command. Table 5-191 shows the SEND DIAGNOSTIC CDB data format and  
Table 5-192 shows the field descriptions.  
Table 5-191 SEND DIAGNOSTIC Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (1Dh)  
PF Rsvd  
Reserved  
Self  
Test  
1
Function  
DevOnl  
UnitOfl  
2
3 - 4  
5
Parameter List Length  
Control  
Table 5-192 SEND DIAGNOSTIC Command-Field Descriptions  
Field  
Description  
When the SelfTest bit is set to one, the Function code field is 000b. When the SelfTest bit is  
cleared to zero, the content of the Function code field is specified as follows:  
000b: Value to be used when the SelfTest bit is set to one or if the SEND DIAGNOSTIC command  
is not invoking one of the other self-test function codes (for example, Translate Address page)  
001b: Background short self-test. The device server will start its short self-test routine in the back-  
ground mode.  
010b: Background extended self test. The device server will start its extended self-test routine in  
the background mode.  
011b: Reserved  
Function  
100b: Abort background self-test. Abort the current self-test running in background mode. This  
value is only valid if a previous SEND DIAGNOSTIC command specified a Background self-test  
function and that function has not completed. If either of these conditions is not true, then the de-  
vice server will respond by returning a CHECK CONDITION with a sense key of NOT READY  
and an additional sense code of LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS.  
101b: Foreground short self-test. The device server will start its short self-test routine in the fore-  
ground mode  
110b: Foreground extended self-test. The device server will start its extended self-test routine in  
the foreground mode  
111b: Reserved  
Page Format. When the PF bit is 1, the parameters that follow conform to the Supported Diagnos-  
tic Page List (Table 5-193) or the Translate Address Page  
PF  
SelfTest is ignored when PF = 1.  
The PF bit must be 1 if Parameter List Length is not 0.  
Maxtor Atlas 10K V  
5-141  
   
Field  
Description  
If the PF bit is 0 and the SelfTest bit is 1, the drive runs its self-test routine. GOOD status is re-  
turned to the initiator if the self-test passes. CHECK CONDITION status is returned along with  
any available sense data if the self-test fails.  
SelfTest  
This field is ignored if the PF bit is 1.  
DevOnl  
UnitOfl  
Any value in this field is ignored by the drive.  
Any value in this field is ignored by the drive.  
When the Parameter List Length field is non-zero, the value specifies the length (in bytes) of the  
parameter list that is to be transferred from the initiator to the drive during the command's data-  
out buffer transfer.  
Parameter List  
Length  
This field is only valid when the PF bit = 1 and must be 0 when the PF bit is 0.  
5.38.1  
Supported Diagnostic Page List  
Table 5-193 shows the Supported Diagnostic Page List that can be supplied with a  
SEND DIAGNOSTIC command to request that the Supported Diagnostic Page List  
be returned after the next RECEIVE DIAGNOSTIC RESULTS command.  
Table 5-193 Supported Diagnostic Page List-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Page Code (00h)  
Reserved  
1
2 - 3  
Page Length (00h)  
5.38.2  
Translate Address Page  
Table 5-194 shows the Translate Address Page that can be supplied with a SEND  
DIAGNOSTIC command to request that the Translate Address Page be returned after  
the next RECEIVE DIAGNOSTIC RESULTS command.  
Table 5-194 Translate Address Page-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Page Code (40h)  
Reserved  
2 - 3  
4
Page Length (0Ah)  
Supplied Format  
000b (LBA)  
Reserved  
Reserved  
5
Translate Format  
101b (Physical Sector)  
6 - 9  
Address to Translate  
(LBA Format)  
10 - 13  
Reserved  
5-142 Maxtor Atlas 10K V  
   
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  
Upon successful completion of a SET DEVICE IDENTIFIER command, a Unit  
Attention is generated for all initiators except the one that issued the command.  
Table 5-195 SET DEVICE IDENTIFIER Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (A4h)  
Service Action (06h)  
1
Reserved  
2 – 5  
Reserved  
(MSB)  
6 – 9  
Parameter List Length  
(LSB)  
10  
11  
Reserved  
Control  
Table 5-196 SET DEVICE IDENTIFIER Command Descriptor Block-Field Descriptions  
Field  
Description  
Service Action  
Must = 06h. Any other value forces Check Condition, Illegal Request.  
This field specifies the length, in bytes, of the Identifier to be transferred from the ap-  
plication client to the device server. The maximum value for this field is 64 bytes. A  
parameter list length of 0 indicates that no data will be transferred, and that subsequent  
REPORT DEVICE IDENTIFIER commands will return an Identifier length of 0. If  
the parameter list length exceeds 64 bytes, then the drive returns a Check Condition  
status with the sense key set to Illegal Request, and an additional sense code of Invalid  
Field in CDB.  
Parameter List Length  
The SET DEVICE IDENTIFIER command’s parameter list contains Identifier to be  
set by the logical unit to which the command is sent. The parameter list is shown  
below in Table 5-197 and the field descriptions are shown in Table 5-198.  
Table 5-197 SET DEVICE IDENTIFIER Parameter List-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
(MSB)  
0 – n  
Identifier  
(LSB)  
Table 5-198 SET DEVICE IDENTIFIER Parameter List-Field Descriptions  
Field  
Description  
The value reported in this field is the data to be returned by all subsequent  
REPORT DEVICE IDENTIFIER commands, until a new SET DEVICE  
IDENTIFIER command is issued that changes the data.  
Identifier  
Maxtor Atlas 10K V  
5-143  
       
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 spin-  
up and spin-down. The data format and field descriptions are shown in Table 5-199  
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. See Chapter 3 for jumper-programming  
instructions for your specific hard disk drive.  
Table 5-199 START STOP UNIT Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (1Bh)  
Reserved  
Immed  
Start  
2 - 3  
4
Reserved  
Power Conditions  
Reserved  
LoEj  
5
Control  
Table 5-200 START STOP UNIT Command-Field Descriptions  
Field Description  
Immediate. When 1, the drive returns GOOD status immediately after validating the  
Command Descriptor Block, but before the drive spins up.  
Immed  
When 0, the drive does not return GOOD status until after the drive has spun up success-  
fully and is ready for media access commands.  
Load Eject. This value must be zero, because the disk drive contains non-removable me-  
dium.  
LoEj  
Start  
When Start is 1, the unit spins up (if it is not currently spinning) and is left in a state where  
subsequent media access commands can succeed.  
When the value is 0, the drive spins down. Subsequent media access commands are re-  
jected with CHECK CONDITION status and the proper sense data.  
Power  
Conditions  
The Power Conditions field is not supported.  
5-144 Maxtor Atlas 10K V  
   
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. Logical  
blocks are not necessarily removed from the cache as a result of the Synchronize Cache  
operation. The data format and field descriptions are shown in Table 5-201 and Table  
5-202 respectively.  
Table 5-201 SYNCHRONIZE CACHE Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (35h)  
Reserved  
Immed  
= 0  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Number of Blocks  
Control  
Table 5-202 SYNCHRONIZE CACHE Command-Field Descriptions  
Field  
Immed  
RelAdr  
Description  
Immediate. Must be 0. The drive returns status after the synchronize cache operation has  
been completed.  
Relative Address. Must be 0. Relative addressing is not supported.  
Logical Block  
Address  
The address of the first logical sector of the range to be operated upon by this command.  
Specifies the total number of contiguous logical blocks within the range. When set to 0,  
the drive removes all sectors from the given Logical Block Address on.  
Number of  
Blocks  
When Number of Blocks and Logical Block Address are both 0, the drive removes all un-  
written cache sectors to the medium.  
It is not considered an error when no sectors within the specified range are in the cache  
memory.  
Maxtor Atlas 10K V  
5-145  
   
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.  
Table 5-203 TEST UNIT READY Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (00h)  
Reserved  
1 - 4  
5
Control  
5-146 Maxtor Atlas 10K V  
 
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 5-  
Table 5-204 VERIFY Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (2Fh)  
Reserved  
DPO  
Reserved  
BytChk  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Verification Length  
Control  
Table 5-205 VERIFY Command-Field Descriptions  
Field  
Description  
Disable Page Out. When the value of the field = 1, the device server will assign the logical  
blocks accessed by this command the lowest priority for being fetched into or retained by the  
cache.  
DPO  
When DPO = 0, the priority will be determined by fields in the Caching page.  
Byte Check. When the value is 1, the drive performs a byte-by-byte comparison of the data  
on the medium with the data sent by the initiator in the data-out buffer transfer.  
BytChk  
RelAdr  
When 0, the drive performs a medium verification with no data comparison. In this case, no  
data is sent by the initiator.  
Relative Address. This feature is not supported; the field must be 0.  
Logical  
Block  
Address  
The address of the first logical sector to be verified.  
The number of contiguous sectors that are to be verified. The drive returns a CHECK CON-  
DITION status with the correct sense data if the specified transfer extends beyond out of the  
logical sector space.  
Verifica-  
tion Length  
Maxtor Atlas 10K V  
5-147  
   
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 5-  
Table 5-206 WRITE (6) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (0Ah)  
Logical Block Address  
Logical Block Address  
Reserved  
2 - 3  
4
Transfer Length  
Control  
5
Table 5-207 WRITE (6) Command-Field Descriptions  
Field  
Description  
Logical Block  
Address  
The address of the first logical block where the Write operation will occur.  
The number of contiguous logical blocks of data to transfer. A transfer length of 0  
indicates 256 logical blocks are to be transferred. Any other value indicates the ac-  
tual number of logical blocks that will be transferred.  
Transfer Length  
5-148 Maxtor Atlas 10K V  
   
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.  
Table 5-208 WRITE (10) Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (2Ah)  
DPO FUA  
Reserved  
Reserved  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Transfer Length  
Control  
Table 5-209 WRITE (10) Command-Field Descriptions  
Field  
Description  
Disable Page Out. When the value of the field is 1, the drive tells the controller to bypass  
cache as much as possible. The buffers used for the WRITE data are given a low priority.  
This bit may be useful if the host CPU is performing a background copy operation and  
does not want to wipe out the drive's cache.  
DPO  
FUA  
When DPO is 0, the drive tells the controller to cache this WRITE data in a normal man-  
ner.  
NOTE: The drive normally assigns a low priority to write caching. Therefore, the DPO  
bit in a WRITE command is ignored.  
Force Unit Access. When 1, the data must be written on the medium before GOOD status  
is returned. When 0, GOOD status may be returned after the data is fetched from the ini-  
tiator and before it is written to the medium. If the WCE (Write Cache Enable) bit on the  
MODE SELECT command Caching Page is clear, the FUA bit is ignored and behaves as  
if it were always set (that is, if WCE = 0, the controller forces FUA = 1).  
Logical Block  
Address  
The address of the first logical block where the Write operation will occur.  
RelAdr  
Relative Address. This drive does not support this feature; the field must be 0.  
The number of contiguous logical blocks of data to write. The drive returns CHECK  
Transfer Length CONDITION status with the correct sense data if the specified transfer would cause the  
write operation to extend beyond the Logical Block Address space.  
Maxtor Atlas 10K V  
5-149  
   
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 WRITE AND VERIFY Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (2Eh)  
Reserved  
DPO  
Reserved  
BytChk  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Transfer Length  
Control  
Table 5-211 WRITE AND VERIFY Command-Field Descriptions  
Field Description  
Disable Page Out. When the value of the field is 1, the drive tells the controller to by-  
pass cache as much as possible. The buffers used for the WRITE data are given a low  
priority. This bit may be useful if the host CPU is performing a background copy oper-  
ation and does not want to wipe out the drive's cache.  
DPO  
When DPO is 0, the drive tells the controller to cache this WRITE data in a normal  
manner.  
NOTE: The drive normally assigns a low priority to write caching. Therefore, the DPO  
bit in a WRITE command is essentially ignored.  
Byte Check. When 1, the drive performs a byte-by-byte comparison of the data written  
on the media with the data transferred from the initiator.  
BytChk  
RelAdr  
When 0, the drive performs a medium verification with no data comparison of the sec-  
tors written by the command.  
Relative Address. This feature is not supported and the field must be 0.  
Logical Block  
Address  
The address of the first logical block where the WRITE operation will occur.  
The number of contiguous logical blocks of data to write and verify. The drive returns  
CHECK CONDITION status with the correct sense data if the specified transfer would  
cause the write operation to extend beyond the Logical Block Address space.  
Transfer Length  
5-150 Maxtor Atlas 10K V  
   
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. The data format and  
field descriptions are shown in Table 5-212 and Table 5-213 respectively.  
Both the READ BUFFER and WRITE BUFFER commands have a Buffer ID and a  
Buffer Offset data field defined in their Command Descriptor Block. In combined  
Header and Data Mode, if both are set to 0, reference is made to a single, 512-byte  
buffer set aside in the controller's data memory, independent of cache. This allows an  
initiator to verify the data path from the controller's data memory to the initiator  
without affecting the drive's internal data caches.  
Table 5-212 WRITE BUFFER Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (3Bh)  
Reserved  
Mode  
2
Buffer ID  
Buffer Offset  
3 - 5  
6 - 8  
9
Parameter List Length  
Control  
Maxtor Atlas 10K V  
5-151  
 
Table 5-213 WRITE BUFFER Command-Field Descriptions  
Field  
Description  
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 fol-  
lows:  
Mode  
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. The resulting descriptor and data are fetched from the initiator  
during the command's data-out buffer transfer and, after the descriptor has been validated, only the data is  
written to the controller's memory.  
0000b  
Buffer ID must be 0  
Buffer Offset must be 0  
Parameter List Length must be set to between 0 and 516 (4 bytes of header and up to 512 bytes of data).  
Data Only– In this mode, the data-out buffer transfer contains buffer data. Data is written to the drive's  
buffer starting at the location specified by the Buffer ID and Buffer Offset.  
Buffer ID. When non-zero, the value specifies a specific track line in the controller’s cache. If Buffer ID  
of zero is specified, the buffer referenced is the same as if Buffer ID of one were specified.  
0010b  
Buffer Offset. When non-zero, the value can range from 0 to one less than the number of sectors/track  
multiplied by 512. This value must be either a zero or a multiple of 512.  
Parameter List Length. This value must be a multiple of 512. The maximum value for this field is one  
more than the number of sectors/track times 512. The minimum value is 0.  
Download Microcode and Save. In this mode, a microcode image is transferred to the drive, and if valid,  
is saved in the controller's non-volatile memory. This image must be transferred with all buffers of the  
same size (the last buffer of the transfer cannot be of a different size) and the buffer size must be a multiple  
of 512. Most images are multiples of 512 and 1K. In that case, it is safe to have 512 byte transfers or 1K  
transfers. For example, if the image size is 369K, then 738 512-byte buffers can be transferred or 369 1K  
byte buffers can be transferred. It is also possible to transfer the image in one large buffer.  
The controller does a hard reset on command completion. In Download Microcode and Save mode, the  
other Command Descriptor Blocks are supported as follows:  
0101b  
Buffer ID – Undefined and ignored.  
Buffer Offset – The offset of the buffer being transferred. For example: for 512 byte transfers use 0, 512,  
1024, 1536,.... For 1K byte transfers use 0, 1024, 2048, 3072...  
Parameter List Length – Must be the size of the buffer being transferred.  
7
Download Microcode and Save with Offset. This mode acts the same as mode 0101b but is restricted to  
sending the bytes in sequential order.  
(0111b)  
Write Data from Echo Buffer  
In this mode, the host transfers data and stores it in an echo buffer. The data will be preserved in the echo  
buffer unless there is an intervening command.  
1010b  
Buffer ID Ignored.  
Buffer Offset Ignored.  
5-152 Maxtor Atlas 10K V  
 
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  
Table 5-214 WRITE LONG Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (3Fh)  
Reserved  
RelAdr  
2 - 5  
6
Logical Block Address  
Reserved  
7 - 8  
9
Byte Transfer Length (578)  
Control  
Table 5-215 WRITE LONG Command-Field Descriptions  
Field Description  
RelAdr  
Relative Address. This drive does not support this feature; the field must be 0.  
The address of the first logical sector where the Write operation will occur.  
Logical Block  
Address  
Must be 578. This value reflects the number of bytes spanned by the ECC, including  
the ECC itself, rounded up to the next word (this is easiest understood in bits: 4096  
data bits + 1 force error bit + 15 Logical Block Address bits + 16 cross check bits + 2  
pad bits + 480 ECC bits + 6 pad bits that are not written to media but are only needed  
for transfer = 4496 bits or 578 bytes). Any other value in this field results in a CHECK  
CONDITION status and the appropriate sense data.  
Byte Transfer  
Length  
The initiator should first issue a READ LONG, then modify the data portion only, and  
then issue a WRITE LONG. It is also recommended that the drive be reformatted after  
these commands are used.  
5.49  
WRITE SAME COMMAND  
The WRITE SAME command requests that the drive write the single sector of data  
transferred by the initiator to the medium mulitple times. The data format and field  
descriptions are shown in Table 5-11 and 5-12 Table respectively.  
Maxtor Atlas 10K V  
5-153  
   
Table 5-216 WRITE SAME Command Descriptor Block-Data Format  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
1
Operation Code (41h)  
Reserved  
PBdata  
LBdta  
RelAdr  
2-5  
6
Logical Block Address  
Reserved  
Number of Blocks  
Control  
7-8  
9
Table 5-217 WRITE SAME Field Description  
Field  
Description  
Physical Block Data - Not supported. This feild must be  
zero.  
PBdata  
Logical Block Data - A value of 1 requests that the drive  
replace the first four bytes of the data to be written to the  
current logical sector with the logical sector address of the  
sector currently being written.  
LBdata  
RelAdr  
Relative Address. - Not supported. This feild must be  
zero  
The address of the first logical sector where the Write op-  
eration will occur.  
Logical Block Address  
Number of Blocks  
This feild contains the number of contiguous logical  
blocks that are to be written. A value of 0 requests that all  
the remaining logical blocks on the medium are to be  
written.  
5.50  
WRITE SKIP MASK Command (EAh)  
The WRTIE SKIP MASK command allows the initiator to condition the function of  
the WRITE commands to allow only selected data to be transferred over the SCSI  
interface. A WRITE SKIP MASK command precedes a WRITE (10) command; the  
WRITE (10) command must be linked to the WRITE SKIP MASK command or the  
skip mask is lost and a CHECK CONDITION status is returned.  
Table 5-218 WRITE SKIP MASK Command (EAh)  
Bit  
Byte  
7
6
5
4
3
2
1
0
0
Operation Code (EAh)  
Reserved  
1
2 - 5  
(MSB)  
Logical Block Address  
Skip Mask Length  
Transfer Length  
Reserved  
(LSB)  
(LSB)  
6
7 - 8  
(MSB)  
9
VU  
Flag  
Link  
5-154 Maxtor Atlas 10K V  
Table 5-219 WRITE SKIP MASK Command - Field Description  
Field  
Description  
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,  
Logical Block Ad-  
dress  
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. The mask consists of a sequence of bits where a "1" bit is for the blocks  
of data to be transferred and a "0" for the blocks of data that are to be skipped. The first "1" bit of  
the mask corresponds to the first LBA to be transferred. Any unused bits at the end of the last byte  
in the mask must be set to 0. The mask is transferred in the data-out buffer transfer of the skip mask  
command.  
Skip Mask Length  
Transfer Length  
This field must be equal to the transfer length in the linked WRITE (10) command. The transfer  
length field must be equal to the number "1" bits in the skip mask. If a WRITE (10) is used with  
0 as the transfer length, a transfer length of 256 data blocks is implied.  
Maxtor Atlas 10K V  
5-155  
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.1 GB, or 300 GB formatted capacity (512 bytes to 524 bytes/  
block selectable in increments of 2 bytes)  
• GMR heads and banded recording for higher overall bit-densities  
• Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T.)  
Revision 2 support  
• Optimized Reordering Command Algorithm and tagged command  
queuing for greater throughput  
• 8 MB segmented cache buffer ECC protected  
• 10,000 rpm rotational speed yielding 3 ms average latency  
• 4.0 ms / 4.5 ms average read/write seek time for the 73.5 GB disk drives,  
4.2 ms / 4.7 ms average read/write seek time for the 147.1 GB disk  
drives; and 4.4 ms / 4.9 ms average read/write seek time for the 300 GB  
disk drives.  
• Embedded servo system for exceptional head positioning accuracy and  
long life  
• “Zero latency” reads and writes reduce data access time  
• Full SCSI-3 compliance1 (compatible with SCSI-2 and SCSI-1)  
• Variable BPI  
• Just-in Time Seeks  
• Read/Write Ahead  
Maxtor Atlas 10K V 6-1  
• 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: 1The drives are in compliance with the SCSI-3 draft proposed ANSI  
standards as they exist at the time of product release; SCSI-3 features  
may not be enabled on drives when shipped.  
Many of these features are described in this chapter.  
The drive contains a large, segmented buffer in RAM that is used to maximize the  
throughput for sequential read streams. This cache is organized as a number of separate  
segments.  
The buffer is also used to combine or coalesce I/O data on a track-by-track basis, prior  
to accessing the disk media. Performance is greatly improved by gathering and  
combining the data on a track basis rather than on a command basis. With this unique  
system, multiple commands for a particular track are coalesced in the buffer before  
accessing the media.  
As a result, multiple I/O commands, that address a single track are logically combined  
to avoid multiple disk accesses on multiple rotations. Since most reads and writes are  
sequential, this greatly increases throughput for most applications.  
6.2  
WRITE-BACK CACHING  
The drive supports write-back caching. In this case, writes are considered complete  
when the data is loaded into the cache, before it is written to the media. This allows  
the host to go on to other tasks, while the drive assumes responsibility for the data and  
ensuring that it is written to media as soon as possible. If write-back caching is  
employed, it is recommended that an uninterruptible power source (UPS) be  
provided for optimal data security.  
6-2 Maxtor Atlas 10K V  
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. When the initial data address read is reached again, that data  
in the buffer is transferred to the bus. This ensures that the track data goes out in media  
order and eliminates the rotational latency associated with waiting for the starting  
address to rotate to the head.  
Writing works essentially the same way only in reverse. The data is first transferred to  
the drive's buffer. After seeking to the desired track, a write pointer is set to the current  
location of the head on the track and writing is commenced from the buffer, starting  
at the corresponding place in the data.  
6.4  
DISCONNECT-RECONNECT  
System throughput can be improved by disconnecting the drive from the initiator  
during physical positioning operations, thereby freeing up the SCSI bus for other I/  
O processes. After the drive has determined that there will be a delay, it disconnects  
itself from the SCSI bus by sending a DISCONNECT message and enters the BUS  
FREE phase.  
When the drive is ready to resume data transfer, it arbitrates for the SCSI bus and, after  
winning arbitration, reconnects to the initiator and sends an IDENTIFY message via  
the MESSAGE IN phase. This revives the I_T_L nexus (initiator-target-logical unit  
connection) so the initiator can retrieve the correct set of data pointers for the I/O  
process. The initiator restores the active pointers to their most recent saved values, and  
the drive continues to finish the original I/O process.  
Disconnect-Reconnect is controlled with the Mode Select Command (15h) for the  
Disconnect/Reconnect (02h) mode page.  
6.5  
TRACK AND CYLINDER SKEWING  
The disk drive improves data throughput by skewing track and cylinder addresses.  
When the drive switches heads or tracks, or both, to access sequential data, the  
rotation of the disk media allows one or more physical blocks to pass by the read/write  
head before the head is ready to continue the transfer. Skewing adjusts the block  
addresses so that the head switch and settle times and the media rotation coincide to  
bring the head exactly to the next logical block. This minimizes rotational latency (and  
increases throughput) when data is accessed sequentially.  
6.6  
6.7  
AVERAGE ACCESS TIME  
A 10,000 rpm rotation speed yields an average latency of 3 ms.  
EMBEDDED SERVO SYSTEM  
Embedded servo information is written in a spoke configuration on every track, on  
every disk surface. The spokes (or headers) consist of quadrature analog patterns and  
Maxtor Atlas 10K V 6-3  
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.8  
DATA INTEGRITY AND SECURITY  
The disk drives use a combination of parity checking, error detection coding (EDC),  
error correction coding (ECC), and checkpointing to protect stored data from media  
errors, transfer or addressing errors, or errors introduced during block reallocation.  
6.8.1  
Media Error Protection  
To ensure that data read is the same as data written, the drive computes and appends  
an Error Correction Code (ECC) to each block of data stored. The drive uses a 352-  
bit Reed Solomon code with a 4:1 interleave, which can correct up to 20 bytes in  
each block.  
The drive can also correct up to 2 bytes per interleave (up to 8 per block) in hardware  
(“on-the-fly”), with no loss in throughput.  
6.8.2  
6.8.3  
Transfer Error Protection  
An end-to-end error detection code (EDC) protects data from any errors introduced  
by internal buses, the disk controller chip, the data cache, or the SCSI interface.  
An EDC is calculated and added to each data block as the data arrives from the SCSI  
bus (after SCSI bus parity is checked). The EDC is stored with the data and protected  
by the block ECC for added security. On reading or writing, the EDC is checked as  
the data is transferred between buffer RAM and the media or the SCSI bus.  
Addressing Error Protection  
Each data block on the media is identified and located by a servo spoke address. The  
spoke address consists of a two-byte word. Each spoke has multiple copies of the least  
significant bytes of the address. The disk hardware requires that a majority of the  
copies agree and that the result agrees with the expected head, track, and spoke  
number, before it will read or write the data.  
To further protect against addressing errors, the logical address (LBA) of the data is  
added to the EDC of each block. If data is written to the wrong block and  
subsequently read, or read from the wrong block, the error will be flagged.  
The hardware does not allow a blind read of a data block; the firmware must request  
specific data blocks. Even if the head selection hardware malfunctions, it is not possible  
for the drive to return data from the wrong head.  
6.8.4  
Data Sector Reallocation Error Protection  
In any SCSI disk drive, bad blocks may be reallocated. However, a power failure or  
unrecoverable data could threaten data integrity during a block reallocation.  
The reallocation and defect list storage algorithms prevent a reallocation from being  
lost due to a power failure. Once a reallocation starts, the information about the data  
block to be moved is stored on the media. As the reallocation progresses, checkpoint  
6-4 Maxtor Atlas 10K V  
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. First, the integrity of data in selected areas of the  
media can be checked using the VERIFY command. Secondly, the WRITE AND  
VERIFY command writes host-supplied data and then verifies that it was written  
correctly.  
The Verify Error Recovery Page of the MODE SELECT COMMAND controls the  
drive's response to error conditions that arise during the VERIFY command and  
during the verify operation of the WRITE AND VERIFY command.  
6.9  
TAGGED COMMAND QUEUING  
The drive supports all three SCSI-defined queue tag messages. When queuing is  
enabled (default condition), the drive can accept any of the following:  
• Simple - specifies that the command is to be placed in the drive's  
command task set (queue). If several commands are present, the drive  
may reorder them to increase overall throughput.  
• Head of Queue - directs the drive to place the command at the  
beginning of the queue, to be executed next. Consecutive commands  
with Head of Queue specified are executed in last-in-first-out (LIFO)  
order. Queue depth is 64.  
• Ordered - specifies that commands in the drive's task set are to be  
executed in the order received (FIFO).  
The DQue bit (disable queuing) of the Control Mode page can be used to disable  
tagged command queuing.  
6.10  
6.11  
COMMAND REORDERING  
The drive uses Optimized Reordering Command Algorithm (ORCA) and tagged  
command queuing to provide greater throughput by reordering any commands  
queued on the drive to minimize rotational latency, seek time and head selection time.  
BANDED RECORDING  
In banded recording, the disk is divided into multiple bands (also called partitions,  
notches, or bit-zoned areas). Starting at the inner band, each band further out has  
more blocks per track (a higher recording frequency). This use of multiple-frequency  
recording increases the capacity of the drive.  
Maxtor Atlas 10K V 6-5  
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 self-  
diagnostic 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.  
If the drive passes the self-tests (and the spin-up jumper is installed), it spins up and  
performs further diagnostics on the Head Disk Assembly (HDA). The drive indicates  
“not ready” until the HDA tests are completed successfully.  
The drive diagnostics test the following:  
• RAM and ROM chips  
• Buffer memory  
• Gate array chips  
• Read/write encoding circuits  
• Basic servo functions  
After a SELECTION TIME following power-on, the disk drive is able to respond  
with appropriate status and sense data to the TEST UNIT READY, INQUIRY, and  
REQUEST SENSE commands.  
6.12.2  
Periodic Self-Adjustments  
During normal drive operation, certain periodic functions occur automatically so the  
drive can verify and maintain the integrity of its operations and optimize performance.  
The operations performed include those listed below.  
• Move/Switch idle heads  
• Adaptive seek profile calibration  
• ROM checksum  
Such periodic functions can make the drive appear to be active when no commands  
are outstanding, because the drive appears to be seeking. Periodic calibrations occur  
only after the drive has been inactive for 30 seconds.  
Note: If a media access command is received during a calibration, the drive  
aborts the calibration process and acts on the command.  
If desired, calibrations can be suspended to reduce drive overhead by setting the  
Manual Calibration bit in the (Vendor) Special Function Control page. If this is done,  
manual calibrations can still be initiated by performing a REZERO UNIT command.  
6-6 Maxtor Atlas 10K V  
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  
6.13  
Log Sense  
Maxtor implements multiple LOG SENSE pages which logically group together  
parameters related to disk and subsystem activities. Monitoring this data enables users  
to observe drive performance and possibly predict failures.  
ERROR RECOVERY  
The mode pages control all error recovery. Any error recovery that is enabled is  
attempted without host intervention.  
6.13.1  
6.13.2  
Seek Error Recovery  
Seek error recovery is automatic if the hardware is physically able to position to the  
correct track.  
Data Read Errors  
Data read errors are recovered, if possible, by one or more of the following methods:  
• Correction of the data “on-the-fly” with ECC hardware.  
• Re-try the operation.  
• Reload read channel registers to calibrated values.  
• Off-track Recovery. Use different off-track offsets and re-try.  
• Use a fixed gain while retrying.  
• Margin servo thresholds to facilitate seek and detent.  
• Margin the error tolerance of sync mark detection.  
• Force sync mark detection while retrying.  
• Skip Sector Rereads. Retries, each without one of eight earlier servo  
blocks.  
• Correction of the bad data with the software ECC algorithm.  
• Switching the bias current of the MR head between retries.  
• TA baseline compensation, and other TA recovery methods.  
6.13.3  
Reallocation of Bad Blocks  
Most of the spare blocks are located on the inner cylinders of the drive. All defective  
blocks are in-line spared at the factory or at format time. Some spare blocks are  
Maxtor Atlas 10K V 6-7  
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 Read-  
Write 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. If the write tests fail, the original data is  
reassigned to a new location.  
6.14  
THE ULTRA160 and ULTRA320 LOW VOLTAGE DIFFERENTIAL  
(LVD) SCSI INTERFACE  
SCSI-3 provides increased performance and versatility to SCSI disks. LVD uses lower  
level voltage swings, differential signaling, and double transition (DT) clocking to  
allow a maximum bus speed of 160 or 320 MB/second in wide SCSI configurations.  
The Maxtor Atlas 10K V disk drive supports the LVD/MSE (Multi-Mode LVD and  
Single-Ended) interface standard. When installed on a bus with only LVD devices the  
Maxtor Atlas 10K V disk drive operates in LVD mode at transfer rates up to 160 or  
320 MB/second. It is fully compatible with Ultra2 LVD devices operating at slower  
transfer rates. If an Maxtor Atlas 10K V disk drive is installed on a bus with one or  
more single-ended (SE) devices, it automatically switches modes to operate in SE  
mode at the slower, legacy data rates.  
Differential SCSI operation has the advantage of higher reliability of data transfer  
through increased immunity to electrical noise. Differential signaling uses a two-wire  
active system in which current from each wire flows in opposite directions and  
reverses direction for a signal transition. The direction of current flow determines  
whether the voltage levels on the two wires have a high/low or low/high relationship  
to each other. The common mode, or reference, level for the two LVD signals is  
+1.25 volts. High and low is defined relative to this level. LVD permits a wide range  
of signal amplitudes. The Maxtor Atlas 10K V interface drivers are designed to provide  
a high to low range on each signal of approximately 400 millivolts in a nominal  
configuration, resulting in a differential signal of approximately 800 millivolts.  
Single-ended SCSI, in contrast, uses one-wire active signaling with the signal return  
wire connected to ground. The active signal range is switched between a high in the  
range of +2.4 - 3.0 volts and a low in the range of 0 - +.5 volts. LVD/MSE SCSI  
devices in single-ended mode do not have the signal return wires connected directly  
to ground, as these same pins must be driven to LVD levels when the device is  
operating in LVD mode. Instead, when in single-ended mode, the device turns on a  
driver transistor for each return line that acts as a switch to connect the signal return  
to ground.  
6-8 Maxtor Atlas 10K V  
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.3 volts unless some device is  
holding the signal at ground. HVD devices pull DIFFSENS up to +5 volts via a  
resistor.  
The Maxtor Atlas 10K V disk drive is designed with a circuit that monitors the level  
of DIFFSENS at power-on. The drive then enables the appropriate circuits for LVD  
or single-ended operation, or disables its interface completely if it detects an HVD  
level on DIFFSENS.  
The two normal operating environments for the Maxtor Atlas 10K V disk drive are  
an all-LVD or (LVD/MSE) bus, in which case it operates in its LVD mode, or a bus  
that contains at least one single-ended device, in which case the Maxtor Atlas 10K V  
disk drive operates in single-ended mode.  
HVD mode is not supported by the Maxtor Atlas 10K V disk drive. Signal levels on  
an HVD bus can reach as high as +15 volts due to allowed common mode transients.  
CAUTION: The LVD and HVD alternatives are mutually exclusive and  
damage may occur to SCSI devices if an LVD device is  
plugged into an operating HVD bus.  
6.14.2  
DIFFSENS SWITCHING  
After establishing its initial operating mode, the Maxtor Atlas 10K V disk drive  
continues to monitor the DIFFSENS signal. If a change in level is detected, such as  
might occur if a device is added to or removed from the bus, the DIFFSENS circuit  
detects the change and presents a mode change interrupt to the drive firmware. The  
operating mode of the interface switches to the new mode 100 msec after the change  
is detected, providing the new level has remained constant. This delay is required to  
prevent spurious mode switches due to noise on the DIFFSENS line.  
Maxtor Atlas 10K V 6-9  
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. Lower frequency clocks  
result in a more reliable bus. Figure 6-1 illustrates the difference between DT and ST  
clocking.  
Figure 6-1 ST and DT CLocking  
The Maxtor Atlas 10K V disk drive can operate at speeds up to 80 MB/sec in either  
ST or DT modes, depending on the capabilities of the host adapter. Transfer rates  
above 80 MB/sec are only supported in DT mode, as required by the SPI-3 SCSI  
standard.  
6-10 Maxtor Atlas 10K V  
 
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. At the end of  
a data burst, the sending device transfers its CRC character and the receiving device  
compares the sender's CRC with its own. If the two CRC characters match, then the  
data burst transferred without error.  
In ST mode, the Maxtor Atlas 10K V uses the traditional parity checking method to  
ensure error free data transfers.  
6.14.5  
DOMAIN VALIDATION  
A new feature (also known as “physical layer integrity checking”) in Ultra160 and  
Ultra320 SCSI interfaces is the capability of the initiator and target devices to execute  
a test sequence of commands before customer operation begins to ensure that the  
SCSI bus can support the desired transfer rate. If errors are found, the initiator can  
negotiate different transfer parameters until a working configuration is found.  
• Domain validation can detect configuration problems such as:  
• Wide devices with a narrow bus segment between them  
• DT devices connect through an ST expander  
• Broken connections  
It may also detect poor quality cables, marginal quality signals, and improper  
termination.  
Domain validation is implemented using standard SCSI commands and new versions  
of the WRITE BUFFER and READ BUFFER commands. The sequence of  
commands used for domain validation may vary from system to system. The selection  
of commands used is entirely under control of host firmware and software.  
6.14.6  
Adaptive Active Filter (AAF)  
Also known as “receiver equalization with filtering.”AAF is a closed-loop method of  
improving received signal quality by amplifying the fundamental frequency of the  
signal while filtering noise and other undesirable components. Devices implementing  
AAF establish the gain of its amplifiers by setting the amplitude of the high-frequency  
portion of the training pattern to be the same as the low-frequency portion at the  
beginning of the training pattern. Using the training pattern to perform this  
adjustment of signal amplitude provides for an inherent closed-loop system that can  
adjust signal quality for different cable plants and changes in system conditions (e.g.,  
when a new device is added to a system causing the electrical characteristics of the  
cable plant to change). AAF settings may be adjusted as often as necessary because  
either the initiator or target may initiate the training pattern sequence. A receiver may  
disable transmitter pre-compensation in a transmitter as AAF performs better in the  
configuration.  
Maxtor Atlas 10K V 6-11  
6.14.7  
6.14.8  
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.  
Free Running Clock (FRC)  
FRC is used to improve integrity of the clock signal by removing inter-symbol  
interference (ISI). By having a clock running at a constant neutralized. The free  
running clock is restricted for use with DT information unit transfers at 320 megabytes  
per second.  
6.14.9  
Skew Compensation  
Skew compensation of data signals relative to the clock signal; an Ultra320 SCSI  
device can establish skew compensation simultaneously for each of the received  
transitions on the data lines so that they occur at the correct time relative to the clock.  
6.14.10 Information Unit Transfers  
IUT (or “IU Transfers,” also known as “packetized transfers”) is a method to  
encapsulate non-data information (like commands sent from the initiator to the target  
and status sent from the target to the initiator) into packets and transfer those packets  
at the maximum negotiated data rate of up to 320 megabytes per second. A method  
to transfer packets for a number of I/O processes without an intervening physical  
disconnection. A method to minimize overhead by eliminating several bus phase  
changes per I/O process.  
6.15  
HOT PLUGGING/REMOVAL AND INSERTION OF SCSI DEVICES  
The Maxtor Atlas 10K V SCA low voltage differential (LVD) disk drives are designed  
for use in “Hot Swap” applications within a properly designed and configured SCSI  
system. With care, system integrators can design storage arrays and/or SCSI buses  
using Maxtor Atlas 10K V disk drives that are “Hot Swap Case 4" tolerant.  
Case 4 is defined as follows:  
• Devices are powered and the bus may have active I/O processes  
ongoing, but the device being removed or inserted must be idle (no  
ongoing I/O processes during the insertion/removal).  
• Ground connections to the drive must be made and maintained for 1  
millisecond before, during, and 1 millisecond after the insertion/  
removal. The SCA-2 connector used on the Maxtor Atlas 10K V disk  
drive meets this requirement.  
• Device circuitry connected to bus pins must remain “glitch” free during  
power up or power down.  
Note: In a multimode environment, any insertion or removal that changes  
the bus mode causes a transceiver mode change reset event.  
6-12 Maxtor Atlas 10K V  
6.15.1  
System Considerations  
It is not possible for the suppliers of various system components (e.g., targets, initiators,  
backplanes, terminators) to guarantee that a system can operate under “Hot Swap Case  
4" conditions. Therefore, the system integrator bears the responsibility for ensuring  
that the system can meet “Hot Swap Case 4" operational criteria.  
There are two metrics key to ensuring “Hot Swap Case 4" tolerance:  
1. When a drive is being hot inserted into an active bus, a smaller capacitance on the  
SCSI bus pins create a smaller (that is, a lesser charge) transient spike on the bus.  
2. When the drive is the closest drive to the connector at which another drive is  
being hot inserted, it is desirable that the input receivers ignore short low  
amplitude transients (usually via a low pass filter).  
LVD SCSI devices may require more stringent system design to tolerate transients that  
occur during Case 4 insertion or removal. System integrators should consider the  
following when designing their backplanes or buses:  
1. Larger connector-to-connector spacing causes the transients associated with hot  
swapping to be attenuated dramatically before reaching an operating drive.  
2. Larger SCSI signal-trace capacitance (that is, lower impedance) is preferable for  
minimizing transient spikes, but can cause other bus problems unrelated to hot  
swapping. Draft standard SCSI-3 SCSI SPI-2 (SCSI Parallel Interface), Revision  
18, Section 6.6.2 illustrates the trade-offs between trace capacitance and drive-to-  
drive spacing.  
3. The universe of drives needs to be homogeneous. A 15 pF drive hot-inserted into  
a rack of 15 pF drives presents no difficulty. A 30 pF drive inserted into a rack of  
10 pF drives with very close connector spacing, however, is more likely to cause  
problems.  
Maxtor Atlas 10K V 6-13  
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.1996  
- Documents 20 Mega-transfer/second operation  
- Defined active negation  
• SPI-4 Specification Revision 10 Defines LVD signaling  
- Defines Multimode (LVD/SE) transceivers  
- Defined LVD active terminators  
- Defines Multimode (LVD/SE) terminators  
- Defines new functionality for the DIFFSENS pins  
- Documents 40 Mega-transfer/second operation  
- Documents LVD connector pin assignments for LVD buses  
- This document is a superset of SCSI standards, incorporating contents of  
both SPI and Fast-20  
6-14 Maxtor Atlas 10K V  
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; Re-  
served 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.  
Table A-1 SCSI-2/SCSI-3 Equivalent Terminology  
SCSI-2  
SCSI-3  
abort  
abort tag  
abort task set  
abort task  
bus device reset  
clear queue  
command complete  
continue I/O process  
head of queue tag  
ordered queue tag  
target reset  
clear task set  
task complete  
continue task  
head of queue  
ordered  
incorrect initiator connection overlapped commands  
I/O process  
phase  
queue  
queue full  
simple queue tag  
task  
service  
task set  
task set full  
simple  
Maxtor Atlas 10K V A-1  
 
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-2 SCSI-3 Quick Reference – Commands  
Command  
Op Code (Hex)  
CHANGE DEFINITION  
FORMAT UNIT  
INQUIRY  
40  
04  
12  
4C  
4D  
15  
55  
1A  
5A  
5E  
5F  
08  
28  
3C  
25  
37  
B7  
3E  
E8  
07  
81  
1C  
82  
17  
57  
A3  
A0  
03  
16  
56  
01  
0B  
2B  
1D  
A4  
1B  
35  
00  
2F  
0A  
2A  
2E  
3B  
3F  
41  
EA  
LOG SELECT  
LOG SENSE  
MODE SELECT (6)  
MODE SELECT (10)  
MODE SENSE (6)  
MODE SENSE (10)  
PERSISTENT RESERVE IN  
PERSISTENT RESERVE OUT  
READ (6)  
READ (10)  
READ BUFFER  
READ CAPACITY  
READ DEFECT DATA (10)  
READ DEFECT DATA (12)  
READ LONG  
READ SKIP MASK  
REASSIGN BLOCKS  
REBUILD  
RECEIVE DIAGNOSTIC RESULTS  
REGENERATE  
RELEASE (6)  
RELEASE (10)  
REPORT DEVICE IDENTIFIER  
REPORT LUNS  
REQUEST SENSE  
RESERVE (6)  
RESERVE (10)  
REZERO UNIT  
SEEK (6)  
SEEK (10)  
SEND DIAGNOSTIC  
SET DEVICE IDENTIFIER  
START/STOP UNIT  
SYNCHRONIZE CACHE  
TEST UNIT READY  
VERIFY  
WRITE (6)  
WRITE (10)  
WRITE AND VERIFY  
WRITE BUFFER  
WRITE LONG  
WRITE SAME  
WRITE SKIP MASK  
A-2 Maxtor Atlas 10K V  
 
Table A-3 SCSI-3 Quick Reference – Messages  
Messages  
Msg. Code (Hex)  
ABORT  
06  
0D  
0C  
0E  
ABORT TAG  
BUS DEVICE RESET  
CLEAR QUEUE  
COMMAND COMPLETE  
CONTINUE I/O PROCESS  
DISCONNECT  
00  
12  
04  
EXTENDED MESSAGE  
01  
HEAD OF QUEUE TAG  
21  
IDENTIFY  
80 – FF  
25  
IGNORE WIDE RESIDUE  
INITIATOR DETECTED ERROR  
LINKED COMMAND COMPLETE  
LINKED COMMAND COMPLETE w/FLAG  
MESSAGE PARITY ERROR  
MESSAGE REJECT  
05  
0A  
0B  
09  
07  
NO OPERATION  
08  
ORDERED QUEUE TAG  
22  
PARALLEL PROTOCOL REQUEST  
QUICK ARBITRATION AND SELECTION  
RELEASE RECOVERY  
04  
55  
10  
SAVE DATA POINTER  
02  
SIMPLE QUEUE TAG  
20  
SYNCHRONOUS DATA TRANSFER REQUEST  
TARGET TRANSFER DISABLE  
WIDE DATA TRANSFER REQ.  
01  
13  
03  
A.3  
SCSI Pages  
Table A-4 lists the SCSI pages, along with the page codes and commands.  
Table A-4 SCSI-3 Quick Reference - Pages  
Pages  
Page Code  
Cmd  
ASCII Implemented Operating Definition  
ASCII Information  
Buffer Overruns and Underruns  
Caching  
Control Mode  
Device Identification  
Disconnect-Reconnect  
82  
01, 02, 03  
01  
12  
12  
4D  
15, 55  
15, 55  
12  
08 *  
0A *  
83  
02  
15, 55  
Maxtor Atlas 10K V A-3  
   
Format Device  
03  
1A  
Format Status  
08  
4D  
Implemented Operating Definition  
Last n Error Events  
81  
07  
12  
4D  
Medium Types Supported  
Non-Medium Error Counter  
Notch and Partition  
Peripheral Device  
Port Control Page  
Margin Control Subpage  
0B  
06  
0C  
09  
19  
1A  
4D  
15, 55  
1A, 5A  
15, 55  
15, 55  
15, 55  
19 (Sub Page 1)  
19 (Sub Page 2)  
Saved Training Configuration Values Sub-  
page  
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 Control  
Unit Serial Number  
Verify Error Counter  
Verify Error Recovery  
Write Error Counter  
19 (Sub Page 3)  
19 (Sub Page 4)  
15, 55  
15, 55  
4D  
15  
15, 55  
03  
01  
04  
**  
00  
00  
00  
40  
00  
80  
05  
07  
02  
1C  
4D  
12  
1C  
15, 55  
12  
4D  
15, 55  
4D  
Note: * Not supported in SCSI-1/CSS mode  
A-4 Maxtor Atlas 10K V  
A.4  
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  
Sense Code - Hex  
0
1
2
3
4
5
6
7
9
B
E
A.5  
Status Codes  
Table A-6 lists the status codes.  
Table A-6 SCSI-3 Quick Reference – Status Codes  
Status Codes  
Status Code - Hex  
GOOD  
CHECK CONDITION  
BUSY  
RESERVATION CONFLICT  
TASK SET FULL  
00  
02  
08  
18  
28  
Maxtor Atlas 10K V A-5  
   
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.1  
TRANSFER PERIOD FACTOR FIELD  
Table B-1 provides the codes and meanings allowed for the Transfer Period Factor  
field if the value of PARL (Parallel Protocol, bit 2 of byte 6 of the Negotiated Rate  
Information Page) is 1.  
Table B-2 provides the allowable codes when the value of PARL = 0.  
Table B-1 Transfer Period Factor Field Values When PARL = 1  
Code  
00h – 07h  
Description  
Reserved.  
08h  
Transfer period=6.25ns (Fast160 or U320 is latched every 6.25 ns)  
This code is valid only if the protocol options bits (QAS,DT and IU) of  
the page have values selected that support double transition (DT) Trans-  
fers.  
00h – 08h  
09h  
Transfer Period=6.25ns (Fast160 or U320 is latched every 6.25 ns)  
This code is valid only if the protocol options bits (QAS,DT and IU) of  
the page have values selected that support double transition (DT) Trans-  
fers.  
Transfer period = 12.5 ns (Fast-80 or U160 is latched every 12.5 ns).  
This code is valid only if the protocol options bits (QAS, DT, and IU) of  
the page have values selected that support double transition (DT) data  
transfers.  
0Ah  
0Bh  
Transfer period = 25 ns (Fast-40 or Ultra2 data is latched every 25 ns).  
Transfer period = 30 ns (Fast-40 data is latched every 30 ns).  
Maxtor Atlas 10K V B-1  
 
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  
32h - FFh  
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).  
Transfer period = the period factor x 4 (Fast-5 data is latched using a  
transfer period of less than or equal to 1020 ns and greater than or  
equal to 200 ns).  
Table B-2 Transfer Period Factor Field Values When PARL = 0  
Code  
Description  
00h – 09h  
0Ah  
Reserved.  
Transfer period = 25 ns (Fast-40 data is latched every 25 ns).  
Transfer period = 30 ns (Fast-40 data is latched every 30 ns).  
0Bh  
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  
19h – 31h  
32h - FFh  
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).  
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).  
Transfer period = the period factor x 4 (Fast-5 data is latched using a  
transfer period of less than or equal to 1020 ns and greater than or  
equal to 200 ns).  
B-2 Maxtor Atlas 10K V  
 
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
1
1
1
0
0
1
1
Selects Single Transition phases. Use ST DATA IN and ST DATA  
OUT phases to transfer data  
0
0
1
Use DT DATA IN and DT DATA OUT phases with data group  
transfers.  
Use DT DATA IN and DT DATA OUT phases with information unit  
transfers.  
Use DT DATA IN and DT DATA OUT phases with information unit  
transfers and use QAS for arbitration.  
Maxtor Atlas 10K V B-3  
GLOSSARY  
ANSI – Abbreviation for American National  
Standards Institute  
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.  
ASCII – Abbreviation for American Standard  
Code for Information Interchange  
ASIC – Acronym for Application Specific  
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.)  
Integrated Circuit.  
AVERAGE SEEK TIME – The average time it  
takes for the read/write head to move to a  
specific location. Calculated by dividing the  
time it takes to complete a large number of  
random seeks by the number of seeks  
performed.  
ACTIVE I/O PROCESS– An I/O process that  
is currently in execution (not queued).  
B
ACTUATOR – Also known as the positioner.  
The internal mechanism that moves the read/  
write head to the proper track. The Maxtor  
actuator consists of a rotor connected to head  
mounting arms that position the heads over the  
desired cylinder. Also known as rotary actuator.  
BACKUP – A copy of a file, directory, or  
volume on a separate storage device from the  
original, for the purpose of retrieval in case the  
original is accidentally erased, damaged, or  
destroyed.  
AIRLOCK – A patented Maxtor feature that  
ensures durable and reliable data storage. Upon  
removal of power from the drive for any reason,  
the read/write heads automatically park and  
lock in a non data area called the landing zone.  
Airlock allows the drive to withstand high levels  
of non-operating shock. When power is applied  
to the drive, airflow created from the spinning  
disks causes the Airlock arm to swing back and  
unlock the actuator, allowing the heads to  
move from the landing zone. Upon power  
down, the Airlock swings back to the locked  
position, locking the heads in the landing zone.  
A park utility is not required to park the heads  
on drives equipped with Airlock (all Maxtor  
drives).  
BAD BLOCK – A block (usually the size of a  
sector) that cannot reliably hold data due to a  
physical flaw or damaged format markings.  
BAD TRACK TABLE – A label affixed to the  
casing of a hard disk drive stating which tracks  
are flawed and cannot hold data. This list is  
typed into the low-level formatting program  
when the drive is installed. Maxtor users can  
ignore bad track tables since Maxtor’s built-in  
defect-management protections compensate for  
these flaws automatically.  
BANDING – A method of variable frequency  
recording on the media that attempts to keep  
the bit density constant, regardless of the track  
radius. Banding greatly increases capacity and  
data transfer rates.  
ALLOCATION – The process of assigning  
particular areas of the disk to specific data or  
instructions. An allocation unit is a group of  
sectors on the disk reserved for specified  
information. On hard disks for small computer  
systems, the allocation unit is usually in the form  
of a sector, block, or cluster. (See also allocation  
unit.)  
BEZEL – A plastic panel that extends the face  
of a drive so that it covers a computer’s drive  
bay opening. The bezel usually contains a drive-  
activity LED. Also known as the faceplate.  
BIT – Abbreviation for binary digit. A binary  
digit may have one of two values—1 or 0. This  
contrasts with a decimal digit, which may have  
a value from 0 to 9. A bit is one of the logic 1or  
logic 0 binary settings that make up a byte of  
data. (See also byte.)  
ALLOCATION UNIT – An allocation unit,  
also known as a cluster, is a group of sectors on  
the disk that can be reserved for the use of a  
particular file.  
Maxtor Atlas 10K V  
G-1  
Glossary  
BLOCK – In UNIX workstation  
CONNECT – The initiator function that  
selects a target to establish a nexus and to start  
an I/O process. The connection that results is  
an initial connection.  
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  
CONNECTION – An initial connection or  
reconnection that can occur only between one  
initiator and one target.  
configuration of the hard drive. See sector for  
comparison.)  
CONTINGENT ALLEGIANCE – A  
condition generated by a CHECK  
CONDITION or  
BPI – Bits Per Inch. A measure of how densely  
information is packed on a storage medium.  
(See also FCI.)  
COMMAND TERMINATED status during  
which execution of all tagged I/O processes (for  
the associated I_T_X nexus) are suspended until  
the condition is cleared. A target preserves an  
I_T_X nexus until it is cleared by a hard or soft  
reset, an abort message or another command for  
that I_T_X nexus. While the contingent  
allegiance condition exists, the target maintains  
sense data for the initiator.  
BUFFER – An area of RAM reserved for  
temporary storage of data that is waiting to be  
sent to a device that is not yet ready to receive  
it. The data is usually on its way to or from the  
hard disk drive or some other peripheral device.  
BUS – The part of a chip, circuit board, or  
interface designed to send and receive data.  
CLUSTER – In DOS environments, the  
smallest contiguous area that can be allocated  
for the storage of data. DOS clusters are usually  
2 Kbytes (4 sectors) in size.  
BYTE – The basic unit of computer memory,  
large enough to hold one character of  
alphanumeric data. Comprised of eight bits.  
(See also bit.)  
CONTROLLER – The chip or circuit that  
translates computer data and commands into a  
form suitable for use by the hard drive. Also  
known as disk controller.  
C
CACHE – Specialized High-speed RAM used  
to optimize data transfers between system  
elements with different performance  
characteristics, e.g., disk to main memory or  
main memory to CPU.  
CONTROLLER CARD – An adapter  
containing the control electronics for one or  
more hard disks. Usually installed in a slot in the  
computer.  
CPU – Central Processing Unit. The  
microprocessor chip that performs the bulk of  
data processing in a computer.  
CAPACITY – The amount of information that  
can be stored on a hard drive. Also known as  
storage capacity. (See also formatted capacity.)  
CRC – Cyclic Redundancy Check. An error  
detection procedure that identifies incomplete  
or faulty data in each sector.  
CLEAN ROOM – An environmentally  
controlled dust-free assembly or repair facility  
in which hard disk drives are assembled or can  
be opened for internal servicing.  
CYLINDER – When disks are placed directly  
above one another along the shaft, the circular,  
vertical “slice” consisting of all the tracks  
located in a particular position.  
CMOS – Acronym for complementary metal  
oxide semiconductor. A low-power, low-heat,  
high-density semiconductor.  
COMMAND QUEUE – The queue used to  
store I/O processes.  
D
G-2  
Maxtor Atlas 10K V  
GLOSSARY  
DATA SEPARATOR – The circuit that  
extracts data from timing information on drives  
that store a combined data and clock signal.  
DRIVE GEOMETRY – The functional  
dimensions of a drive, including the number of  
heads, cylinders, and sectors per track. (See also  
logical format.)  
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.)  
E
ECC – Error Correction Code. The  
incorporation of extra parity bits in transmitted  
data in order to detect errors that can be  
corrected by the controller.  
DEFECT MANAGEMENT – A technique  
ensuring long-term data integrity. Consists of  
scanning disk drives both at the factory and  
during regular use, de-allocating defective  
sectors before purchase and compensating for  
new defective sectors afterward.  
EDC – Abbreviation for error detection code.  
An end-to-end cyclic redundancy code that is  
used to protect data from errors that may be  
introduced by the connecting busses, the disk  
controller chip, the data cache, or the SCSI  
interface in a disk drive. See also, CRC.  
DIFFERENTIAL TERMINATION – One of  
two methods for terminating the SCSI bus,  
characterized by a two-line signal: a (+) signal  
and a (-) signal. Used to improve noise  
resistance when long bus cables are required.  
See also single-ended termination.  
ELECTRONICS MODULE – The printed  
circuit board containing the drive electronics.  
EMBEDDED SERVO – A timing or location  
signal placed on tracks that store data. These  
signals allow the actuator to fine-tune the  
position of the read/write heads.  
DISK – In general, any circular-shaped data-  
storage medium that stores data on the flat  
surface of the platter. The most common type  
of disk is the magnetic disk, which stores data as  
magnetic patterns in a metal or metal-oxide  
coating. Magnetic disks come in two forms:  
floppy and hard. Optical recording is a newer  
disk technology that gives higher capacity  
storage but at slower access times.  
ENCODING – The conversion of data into a  
pattern of On/Off or 1/0 signals prior to being  
written on the disk surface. (See also RLL and  
MFM.)  
EPROM – Erasable Programmable Read-Only  
Memory. An integrated circuit memory chip  
that can store programs and data in a non-  
volatile state. These devices can be erased by  
ultraviolet light and reprogrammed with new  
data.  
DISK CONTROLLER – A plug-in board, or  
embedded circuitry on the drive, that passes  
information to and from the disk. The Maxtor  
hard disk drives all have controllers embedded  
on the drive printed-circuit board. (See also  
controller.)  
EXTENDED CONTINGENT  
DMA – Direct Memory Access. A process for  
transferring data directly to and from main  
memory, without passing through the CPU.  
DMA improves the speed and efficiency by  
allowing the system to continue processing  
even while new data is being retrieved.  
ALLEGIANCE – A condition generated by a  
target and announced with a INITIATE  
RECOVERY message. The mode is used  
when multi-step extended error recovery  
procedures are required to prevent interference  
as from other initiators in a multi-initiator  
system. See also contingent allegiance.  
DOS – Disk Operating System. The most  
common operating system used in IBM PCs.  
Manages all access to data on the disk.  
EXTERNAL DRIVE – A drive mounted in an  
enclosure separate from the computer system  
enclosure, with its own power supply and fan,  
and connected to the system by a cable.  
DRIVE – Short form of disk drive.  
Maxtor Atlas 10K V  
G-3  
Glossary  
FORMATTED CAPACITY – The amount of  
room left to store data on a disk after writing  
sector headers, boundary definitions, and  
timing information during a format operation.  
The size of a Maxtor drive is always expressed  
in formatted capacity, accurately reflecting the  
usable space required.  
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.  
FORM FACTOR – The industry standard that  
defines the physical, external dimensions of a  
particular device. For example, most Maxtor  
hard disk drives use a 3 1/2-inch form factor.  
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.)  
FULL HEIGHT – Term used to describe a disk  
that occupies the vertical space (3.250 inches) of  
a full sized 5.25-inch drive. See also half height,  
low profile.  
FIELD – A logically related group of one or  
more physically contiguous bits.  
FILE SERVER – A computer that provides  
network stations with controlled access to  
shareable resources. The network operating  
system is loaded on the file server, and most  
shareable devices (disk subsystems, printers) are  
attached to it. The file server controls system  
security and monitors station-to-station  
communications. A dedicated file server can be  
used only as a file server while it is on the  
network. A non dedicated file server can be  
used simultaneously as a file server and a  
workstation.  
G
GIGABYTE (GB) –1 billion bytes. The total  
accessible capacity varies depending on the  
operating environment.  
Glist – Abbreviation. When the drive  
encounters a defective sector during regular use,  
it adds the address of the sector to the Grown  
Defect List (Glist). See also Plist.  
GUIDE RAILS – Plastic strips attached to the  
sides of a hard disk drive in an IBM PC/AT or  
compatible computer so that the drive easily  
slides into place.  
FIRMWARE – Permanent instructions and  
data programmed directly into the circuitry of  
read-only memory for controlling the operation  
of the computer. Distinct from software, which  
can be altered by programmers.  
H
FLUX DENSITY – The number of magnetic  
field patterns that can be stored in a given length  
of disk surface. The number is usually stated as  
flux changes per inch (FCI), with typical values  
in the thousands. (See also FCI.)  
HALF-HEIGHT – Standard drive size  
equivalent to half the vertical space of a 5 1/4-  
inch drive.  
HARD DISK – A type of storage medium that  
retains data as magnetic patterns on a rigid disk,  
usually made of an iron oxide or alloy over a  
magnesium or aluminum platter. Because hard  
disks spin more rapidly than floppy disks, and  
the head flies closer to the disk, hard disks can  
transfer data faster and store more in the same  
volume.  
FLYING HEIGHT – The distance between  
the read/write head and the disk surface, made  
up of a cushion of air that keeps the two objects  
from touching. Smaller flying heights permit  
denser data storage but require more precise  
mechanical designs. Also known as fly height.  
FORMAT – To write a magnetic track pattern  
onto a disk surface, specifying the locations of  
the tracks and sectors. This information must  
exist on a disk before it can store data.  
HARD ERROR – A data error that persists  
when the disk is re-read, usually caused by  
defects in the physical surface.  
G-4  
Maxtor Atlas 10K V  
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.)  
I
INITIALIZATION – See low-level formatting.  
INTERFACE – A hardware or software  
protocol, (contained in the electronics of the  
disk controller and disk drive) that manages the  
exchange of data between the drive and  
computer. The most common interfaces for  
small computer systems are AT (also known as  
IDE) and SCSI.  
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. Head crash can also be caused by  
dust and other particles.  
INTERLEAVE – The arrangement of sectors  
on a track. The Interleave Factor is the number  
of sectors that pass beneath the read/write heads  
before the next sector arrives. For example, a  
3:1 interleave factor means that the heads read a  
sector, then let two pass by before reading  
another, requiring three full revolutions of the  
disk to access the complete data track. Maxtor  
drives have an interleave factor of 1:1, allowing  
the system to access a full track of data in a single  
revolution.  
HEAD ASSEMBLY – The tiny  
electromagnetic or magneto-resistive element  
used to write and read back the magnetic  
patterns of data on the recording media. See also  
Diamond Head.  
HEAD DISK ASSEMBLY (HDA) – The  
assembly made up of the spindle motor, spindle,  
head positioner (actuator), head preamp  
electronics, and magnetic disk assembly.  
INTERLEAVE FACTOR – The number of  
sectors that pass beneath the read/write heads  
before the next numbered sector arrives. When  
the interleave factor is 3:1, a sector is read, two  
pass by, and then the next is read. It would take  
three revolutions of the disk to access a full track  
of data. Maxtor drives have an interleave of 1:1,  
so a full track of data can be accessed within one  
revolution of the disk, thus offering the highest  
data throughput possible.  
HIGH-CAPACITY DRIVE – By industry  
conventions typically a drive of 100 megabytes  
or more.  
HIGH-LEVEL FORMATTING – Formatting  
performed by the operating system to create the  
root directory, file allocation tables and other  
basic configurations. (See also low-level formatting.)  
INTERNAL DRIVE – A drive mounted  
inside one of a computer’s drive bays, or a hard  
disk on a card installed in one of the computer’s  
expansion slots.  
HOME – Reference track used for  
recalibration of the actuator. Usually the  
outermost track (track 0).  
HOST ADAPTER – A plug-in board that acts  
as the interface between a computer system bus  
and the disk drive.  
I/O PROCESS – An I/O process consists of an  
initial connection (nexus) followed by zero or  
more reconnections, all pertaining to a single  
command or a group of linked commands. An  
I/O process normally ends with a BUS FREE  
phase following a COMMAND COMPLETE  
or a RELEASE RECOVERY message.  
Maxtor Atlas 10K V  
G-5  
Glossary  
3 1/2-inch form factor, which are only 1 inch  
high. The standard form factor drives are 1.625  
inches high.  
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.  
LPS – Low Profile Series.  
LOW-VOLTAGE DIFFERENTIAL (LVD)  
— Is a differential bus technology that  
K
combines much of the bus length, noise,  
immunity, and performance benefits to  
conventional differential SCSI with the power  
consumption and cost of single-ended SCSI  
Interfaces. Ultra2 SCSI (LVD) increase bus data  
rates to 80 Mbytes/sec, provides differential  
data integrity, extends the SCSI bus cable  
length to 12 meters, and provides easy system  
configuration for up to 15 peripherals.  
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.  
LATENCY – The time during which the read/  
write heads wait for the data to rotate into  
position after the controller starts looking for a  
particular data track. If a disk rotates at 3,600  
rpm, the maximum latency time is 16.4  
milliseconds, and the average latency time is 8.2  
milliseconds.  
M
MB – See megabyte.  
MAGNETO-RESISTIVE – A unique  
characteristic of some metals, which, when  
combined, yields a variable electrical resistance  
to varying magnetic fluxes. The resistance varies  
directly with the strength of the flux, field, not  
simply to a change in flux as with magneto-  
inductance.  
LBA – Abbreviation for Logical Block Address.  
A sequentially-numbered identity of a multi-  
byte block of user data. It does not refer directly  
to the physical location of the data in a disk  
drive.  
MEDIA – The magnetic film that is deposited  
or coated on an aluminum substrate which is  
very flat and in the shape of a disk. The media  
is overcoated with a lubricant to prevent  
damage to the heads or media during head take  
off and landing. The media is where the data is  
stored inside the disk in the form of magnetic  
flux or polarity changes.  
LOGICAL FORMAT – The logical drive  
geometry that appears to the computer system  
BIOS as defined by the drive tables and stored  
in CMOS.  
LOGICAL UNIT – A physical or virtual  
peripheral device addressable through a target.  
MEGABYTE (MB) – A unit of measurement  
equal to 1,000 kilobytes, or 1,024,000 bytes.  
(See also kilobyte.)  
LOOK AHEAD – The process of anticipating  
events in order to speed up computer  
operations. For example, the system can buffer  
data into cache RAM by reading blocks in  
advance, preparing the system for the next data  
request.  
MEGAHERTZ – A measurement of frequency  
in millions of cycles per second.  
MHz – See megahertz.  
LOW-LEVEL FORMATTING – The process  
of creating sectors on the disk surface so that the  
operating system can access the required areas  
for generating the file structure. Maxtor drives  
are shipped with the low-level formatting  
already completed. Also known as initialization.  
MICROPROCESSOR – The integrated  
circuit chip that performs the bulk of data  
processing and controls the operation of all of  
the parts of the system. A disk drive also  
contains a microprocessor to handle all of the  
internal functions of the drive and to support  
the embedded controller.  
LOW PROFILE – Describes drives built to the  
G-6  
Maxtor Atlas 10K V  
GLOSSARY  
MICROSECOND (µs) – One millionth of a  
second (.000001 sec.).  
OXIDE – A metal-oxygen compound. Most  
magnetic coatings are combinations of iron or  
other metal oxides, and the term has become a  
general one for the magnetic coating on tape or  
disk.  
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.  
P
PARITY – An error checking technique  
wherein the sum of the bits in a data byte is used  
to set or reset an extra parity bit, depending on  
whether the sum is an odd or an even number.  
A second parity check after the data is  
transferred to a new location checks that the  
new parity bit matches the transferred bit. Parity  
checking can only detect an odd number of bit  
errors (1,3,5, etc.). Parity is defined as odd or  
even, depending on which condition (odd or  
even) is used to set the parity bit.  
MTTR – Mean Time To Repair. The average  
time it takes to repair a drive that has failed for  
some reason. This only takes into consideration  
the changing of the major sub-assemblies such  
as circuit board or sealed housing. Component  
level repair is not included in this number as this  
type of repair is not performed in the field.  
PARKING ZONE – A position in a non-data  
area on a disk platter reserved for resting the  
heads when power is off. Using this area  
prevents the heads from touching the surface in  
data areas upon power down, adding to the data  
integrity and reliability of the disk drive. The  
parking zone is most often inside the disk's  
inner-most cylinder.  
N
.NANOSECOND (ns) – One billionth of a  
second (0.000 000 001 second or 10-9 second).  
NEXUS – A relationship between two devices  
that begins with the establishment of an initial  
connection and ends with the completion of an  
I/O process. A nexus relationship is further  
defined by the letters I (initiator), T (target), L  
(logical unit), R (target routine), x (either L or  
R), Q (queue tag), and x_y (either an x or a Q)  
PARTITION – A portion of a hard disk  
dedicated to a particular operating system and  
application and accessed as a single logical  
volume.  
PERFORMANCE – A measure of the speed  
of the drive during normal operation. Factors  
affecting performance are seek times, transfer  
rate and command overhead.  
O
OVERHEAD – Command overhead refers to the  
processing time required by the controller, host  
adapter, or drive prior to the execution of a  
command. Lower command overhead yields  
higher drive performance. Disk overhead refers  
to the space required for non-data information  
such as location and timing. Disk overhead  
often accounts for about ten percent of drive  
capacity. Lower disk overhead yields greater  
disk capacity.  
OVERWRITE – To write data on top of  
existing data, erasing it.  
Maxtor Atlas 10K V  
G-7  
Glossary  
PERIPHERAL – A device added to a system as  
an enhancement to the basic CPU, such as a  
disk drive, tape drive or printer.  
R
RAM – Random Access Memory. An  
integrated circuit memory chip that allows  
information to be stored and retrieved by a  
microprocessor or controller. The information  
may be stored and retrieved in any order, and all  
storage locations are equally accessible.  
PHYSICAL FORMAT – The actual physical  
layout of cylinders, tracks, and sectors on a disk  
drive.  
PHYSICAL SECTOR –See sector, data.  
RAM DISK – A “phantom” disk drive created  
by setting aside a section of RAM as if it were a  
group of regular sectors. Access to RAM disk  
data is extremely fast, but is lost when the  
system is reset or turned off.  
PLATTER – Common term referring to the  
hard disk.  
POH – Power On Hours. The unit of  
measurement for Mean Time Between Failure  
as expressed in the number of hours that power  
is applied to the device regardless of the amount  
of actual data transfer usage. (See also MTBF.)  
READ – The function of detecting, processing  
and transmitting data that has been recorded  
(written) on a magnetic disk or some other  
media.  
POSITIONER – See actuator.  
READ AFTER WRITE – A mode of  
operation requiring that the system read each  
sector after data is written, checking that the  
data read back is the same as the data recorded.  
This operation lowers system speed but raises  
data reliability.  
PREFETCH –The technique of buffering data  
into cache RAM by reading subsequent blocks  
in advance to anticipate the next request for  
data. Prefetch speeds up disk accesses to  
sequential blocks of data.  
READ VERIFY – A data accuracy check  
performed by having the disk read data to the  
controller, which then checks for errors but  
does not pass the data on to the system.  
PRML – Partial-Response Maximum-  
Likelihood. A sophisticated data-detection  
method that improves data throughput and  
increases areal density. PRML read channels are  
used in place of peak-detection read channels.  
READ/WRITE HEAD – The tiny  
electromagnetic coil and metal pole piece used  
to create and read back the magnetic patterns  
(write or read information) on the disk. Each  
side of each platter has its own read/write head.  
Q
QUEUE – A prioritized list or set of processes.  
A queue may be a FIFO (first-in, first-out),  
LIFO (last-in, first -out) or a random-access  
entity.  
RECONNECT – The act of reviving a nexus  
to continue an I/O process. An initiator  
reconnects to a target using the SELECTION  
and MESSAGE OUT phases after winning  
arbitration. The target reconnects to the  
initiator using RESELECTION and  
QUEUE TAG – The value associated with an  
I/O process that uniquely identifies it from  
other queued I/O processes in the logical unit  
from the same initiator.  
MESSAGE IN phases after winning arbitration.  
RECONNECTION – The state which results  
from a reconnect. It exists from the assertion of  
BSY in the SELECTION or RESELECTION  
phase and lasts until the next BUS FREE phase.  
QUEUED I/O PROCESS – An I/O process  
that is in the command queue.  
G-8  
Maxtor Atlas 10K V  
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.  
SCA-2 – An improved Single Connector  
Attachment that incorporates two electrostatic  
discharge (ESD) pins on either end of the  
connector to improve safety when making a  
connection.  
SCSI – Small Computer System Interface. An  
interface designed for Apple Macintosh systems  
and UNIX workstations.  
RLL – Abbreviation for Run Length Limited.  
An advanced method used to encode (or  
compress) data for storage on a disk. RLL  
encoding stores almost 50 percent more data  
than MFM (Modified Frequency Modulation).  
RLL code improves MFM code by encoding  
data bits in groups rather than singly. Many  
encoding schemes are possible. The best  
achieve optimum values of code rates, clocking,  
power spectrum, error propagation and  
encoding complexity. A number pair (e.g., 1,7)  
is usually stated with RLL references. It refers to  
the minimum number of 0;s(1) and the  
maximum number of 0's (7) that can separate  
data 1's stored on the disk.  
SCSI-1 – The first small computer system  
interface standard.  
SCSI-2 – An enhanced small computer system  
interface as defined and published by ANSI in  
standard X3.131-1994. One of the major  
features of SCSI-2 is integrating the controller  
into the peripheral device, making the device  
independent of the initiator.  
SCSI-3 – A new set of related ANSI standards  
are currently under development by the X3T10  
committee. The old SCSI-2 standard has been  
divided into a new set of standards for SCSI-3.  
Some of these [working draft] standards are:  
ROM – Read-Only Memory. Integrated  
circuit memory chip containing programs that  
can be accessed and read but can not be  
modified.  
SAM (SCSI Architecture Model) for the  
architecture;  
SBC (SCSI Block Commands) for the disk  
drive specific command set.  
ROTARY ACTUATOR – The rotary  
actuator replaces the stepper motor used in the  
past by many hard disk manufacturers. The  
rotary actuator is perfectly balanced and rotates  
around a single pivot point. It allows closed-  
loop feedback positioning of the heads, which is  
more accurate than stepper motors.  
SPC (SCSI Primary Commands) for the  
primary command set; and  
SIP (SCSI Interlocked Protocol) for the  
protocol layer;  
ROTATIONAL LATENCY – The delay  
between when the controller starts looking for  
a specific block of data on a track and when that  
block rotates around to where it can be read by  
the read/write head. On average, it is half of the  
time needed for a full rotation (about 8 ms.).  
SPI (SCSI Parallel Interface) for the physical  
layer;  
Layering the standards documents in this  
manner allows substitution of parts of the  
structure as new technology arrives.  
SCSI ADDRESS – The unique address  
assigned to a SCSI bus device. Normally, the  
address is assigned and set during system  
installation with priority being a consideration.  
A SCSI address is a value of 0 to 7 (or 0 to 15  
for “wide” SCSI).  
S
SCA – Single Connector Attachment. A drive  
connector that combines the signal and power  
connectors into one. Typically, SCA-type  
connectors are used in RAID (Redundant  
Array of Inexpensive Devices) systems.  
Maxtor Atlas 10K V  
G-9  
Glossary  
SCSI BUS – A multi-signal parallel bus that  
interconnects SCSI devices in a daisy-chain  
fashion.  
center.  
SERVO DATA – Magnetic markings written  
on the media that guide the read/write heads to  
the proper position.  
SCSI DEVICE – A host adapter or a target  
controller that can be attached to the SCSI bus.  
SERVO SURFACE – A separate surface  
containing only positioning and disk timing  
information but no data.  
SCSI ID – The bit-significant representation of  
the SCSI address referring to one of eight (or  
one of sixteen) data lines.  
SETTLE TIME – The interval between the  
arrival of the read/write head at a specific track,  
and the lessening of the residual movement to a  
level sufficient for reliable reading or writing.  
SECTOR – On a PC hard drive, the minimum  
segment of track length that can be assigned to  
store information. On Macintosh and UNIX  
drives, sectors are usually grouped into blocks  
or logical blocks that function as the smallest  
data unit permitted. Since these blocks are often  
defined as a single sector the terms block and  
sector are sometimes used interchangeably in  
this context. (Note: The usage of the term  
block in connection with the physical  
SHOCK RATING – A rating, expressed in  
“G’s”, of how much shock a disk drive can  
sustain without damage.  
SIGNAL ASSERTIOn – The act of driving a  
signal to the true (logical-one) state. An asserted  
signal on the SCSI bus is a low voltage resulting  
from driving a transistor ON.  
configuration of the disk is different from its  
meaning at the system level. See also block and  
cluster for comparison.)  
SIGNAL NEGATION – The act of driving a  
signal to the false (0) state, or allowing the cable  
terminators to bias the signal to the false state by  
placing the data driver in the high impedance  
(off) condition. A negated signal on the SCSI  
bus is a high voltage resulting from all OR-tied  
transistors being OFF.  
SEEK – A movement of the disk read/write  
head to a specific data track.  
SEGMENTED CACHE BUFFER – A cache  
buffer that is organized into multiple track lines.  
Segmenting the cache allows track data to be  
saved in separate segments when the head is  
switched rather than having to erase the entire  
cache. Segmenting the cache enables command  
reordering on a more efficient track-basis rather  
than on a command-basis.  
SIGNAL RELEASE – The act of allowing the  
cable terminators to bias the signal to the false  
state by placing the bus driver in the high  
impedance (off) condition.  
SENSE DATA – Information returned to an  
initiator regarding error conditions in the drive.  
SINGLE-ENDED TERMINATION – One  
of two methods for terminating the SCSI bus,  
characterized by signal values that conform to  
the ANSI-defined levels for SCSI  
implementation. Typically used for short cable  
runs. See also differential termination.  
SERVO SECTOR TIME – The time (in µsec)  
between reading one servo header (or “spoke”)  
and reading the next header.  
SERVO SPOKE DATA – In embedded servo  
technology, digital and quadrature analog servo  
data is written (embedded) in multiple headers  
(or “spokes”) on each track on the data-  
recording area of each disk surface. The digital  
portion of the spoke data are read and used to  
locate the correct 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  
SKEW – To shift sector addresses when  
switching tracks or cylinders to create a slight  
overlap under the read/write heads. The  
overlap works to delay the arrival of the next (in  
sequence) sector from arriving under the  
selected head until the track or cylinder switch  
has been done. Skewing minimizes latency time  
(increasing data throughput) when data on the  
drive is accessed sequentially.  
G-10  
Maxtor Atlas 10K V  
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.  
T
TARGET – An SCSI device that performs an  
operation requested by an initiator.  
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.  
TARGET ROUTINE – An I/O process  
directed to a target and not to a logical unit.  
SOFT-SECTORED – Old time-based method  
of indicating the start of each sector on a disk.  
Soft-sectored drives require that location  
instructions be located in the data fields. (See  
also hard-sectored.)  
THIN FILM – A type of coating allowing very  
thin layers of magnetic material, used on hard  
disks and read/write heads. Hard disks with thin  
film surfaces can store greater amounts of data.  
THIRD-STROKE SEEK – A method of  
evaluating the power requirements of a hard  
drive. It involves monitoring drive current  
while seeking to a selected track, waiting for 1/  
2 a revolution, then seeking to a track that is 1/  
3 of the total actuator stroke from the first. The  
seek/wait cycle is usually repeated three times.  
SPINDLE – The drive’s center shaft, on which  
the hard disks are mounted. A synchronized  
spindle is a shaft that allows two disks to spin  
simultaneously as a mirror image of each other,  
permitting redundant storage of data.  
SPUTTER – A special method of coating the  
disk that results in a hard, smooth surface  
capable of storing data at a high density. Maxtor  
disk drives use sputtered thin film disks.  
TPI – Tracks Per Inch. The number of tracks  
written within each inch of disk’s surface, used  
as a measure of how closely the tracks are  
packed on a disk surface. Also known as track  
density.  
STEPPER – A type of motor that moves in  
discrete steps with each electrical pulse. Stepper  
were originally the most common type of  
actuator engine, since they can be geared to  
advance a read/write head one track per step.  
However, they are not as fast, reliable, or  
durable as the voice coil actuators found in  
Maxtor disk drives. (See also voice coil.)  
TRACK – One of the many concentric  
magnetic circle patterns written on a disk  
surface as a guide for storing and reading data.  
Also known as channel.  
TRACK DENSITY – How closely the tracks  
are packed on a disk surface. The number is  
specified as tracks per inch (TPI).  
SUBSTRATE – The material underneath the  
magnetic coating of a disk. Common substrates  
include aluminum or magnesium alloys for hard  
drives, glass, for optical disks, and mylar for  
floppy disks.  
TRACK-TO-TRACK SEEK TIME – The  
time required for the read/write heads to move  
to an adjacent track.  
SURFACE – The top or bottom side of a disk,  
which is coated with the magnetic material for  
recording data. On some drives one surface may  
be reserved for positioning information.  
TRANSFER RATE – The rate at which the  
disk sends and receives data from the controller.  
The sustained transfer rate includes the time  
required for system processing, head switches  
and seeks, and accurately reflects the drive’s true  
performance. The burst mode transfer rate is a  
much higher figure that refers only to the  
movement of data directly into RAM.  
SYNCHRONOUS DATA TRANSFER –  
Data transfer that allows transfer of multiple  
blocks of data between request or  
acknowledgment signals, since request and  
acknowledgment signals need not be sent  
TRUE – Refers to the logical-one (or  
Maxtor Atlas 10K V  
G-11  
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
WRITE – The operation of recording or  
storing data on a magnetic or other media. See  
also, read.  
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. After formatting, user data  
can be stored on the remaining disk space,  
known as the formatted capacity.  
WRITE ONCE – An optical disk technology  
that allows the drive to store and read back data,  
but prevents the drive from erasing information  
once it has been written.  
WRITE SAME - A command requests that  
the drive write the single sector of data  
transferred by the initiator to the meduim  
multiple times.  
ULTRA SCSI– Doubles the bandwidth of  
SCSI Fast. it provides 8-bit (SCSI NARROW)  
data rates of 20 Mbytes per second and 16-bit  
(SCSI Wide) data rates of 40 Mbytes per  
second. Shorter cables may be required. Also  
known as Fast-20.  
UNFORMATTED CAPACITY – The total  
number of usable bytes on a disk, including the  
space that will be required to later to record  
location, boundary definitions, and timing  
information. (See formatted capacity for  
comparison.)  
V
VOICE COIL – A fast and reliable actuator  
motor that works like a loud speaker, with the  
force of a magnetic coil causing a proportionate  
movement of the head. Voice coil actuators are  
more durable than their stepper counterparts,  
since fewer parts are subject to daily stress and  
wear. Voice coil technology is used in all  
Maxtor drives.  
W
Wide SCSI – SCSI protocol permits wide data  
transfers of 16 or 32 bits.  
Wide data transfer – Data transfer that allows  
information transfer across 16 (or future 32)  
bits. Faster than standard 8-bit data transfer.  
WEDGE SERVO – The position on every  
track that contains data used by the closed loop  
positioning control. This information is used to  
fine tune the position of the read/write heads  
exactly over the track center.  
G-12  
Maxtor Atlas 10K V  
INDEX  
Caching Page 5-46, 5-138  
CHANGE DEFINITION Command 5-  
14  
Numerics  
4-pin DC power connector 3-21  
512-byte sectors available 4-3  
Changeable Pages 5-41  
clearance 3-24  
Clearing Sense Data 5-108  
Command Queuing 5-23  
component life 4-10  
A
abbreviations 1-2  
Connect Time Limit 5-44  
connector 3-15, 3-16, 3-17, 3-20  
contact start/stop cycles 4-2  
Contingent Allegiance Condition 5-8  
Control Mode 5-8, 5-48, 5-49  
Control Mode Page 5-48, 5-49  
Correction Span 5-43, 5-46  
Cylinder Number of Defect 5-19  
Cylinder Skew Factor 5-66  
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  
D
ASCII Implemented Operating Definition  
Page 5-26  
data transfer rate 2-2, 4-4  
Data transfer Rates 4-2  
audience definition 1-1  
auto head-park method 4-2  
average write 4-2  
Defect Descriptors 5-11, 5-12, 5-100  
Defect List Format 5-95, 5-96, 5-97, 5-98  
Defect List Header 5-11, 5-12, 5-17, 5-  
18, 5-95, 5-96, 5-97, 5-98, 5-100  
Defect List Length 5-17, 5-18, 5-96, 5-  
98, 5-100  
AWRE 5-15, 5-43, 5-47  
B
Defect Lists 5-15  
Bit Pointer 5-122  
Defective Sector Number 5-19  
Disconnect Time Limit 5-44  
Disconnect-Reconnect Page 5-44  
disk errors 4-3, 4-11  
disks 4-1  
DOS 4-3  
Block Descriptor 5-11, 5-15, 5-40, 5-41,  
5-63, 5-64, 5-65, 5-70  
Block Length 5-41, 5-110  
Buffer Empty Ratio 5-44  
Buffer Full Ratio 5-44  
Buffer ID 5-92, 5-140, 5-141  
Buffer Offset 5-92, 5-140, 5-141  
buffer size 4-2  
Drive Step Rate 5-68  
drop 4-10  
Bus Inactivity Limit 5-44  
bus interface connector 3-16, 3-17, 3-20  
Byte Transfer Length 5-11, 5-99, 5-142  
bytes per sector 4-1  
E
ECC 5-12, 5-15, 5-43, 5-46, 5-99, 5-  
142  
encoding method 4-2  
Ending Boundary 5-51  
environmental conditions 4-8  
C
Caching 5-46, 5-47, 5-138  
I-1  
Maxtor Atlas 10K V  
error correction method 4-2  
Error Reporting 5-7  
error type 4-11  
5-25, 5-26  
Initialization Pattern Descriptor 5-19  
input power connections 3-21  
inside zone 4-1  
ESD 3-4  
Extent List Length 5-124  
interface connector 3-15  
Interleave 5-66  
F
J
faceplate 3-3  
Field Pointer Bytes 5-122  
Firmware Revision 5-27  
Firmware Revision Page 5-27  
Flag Bit 5-6, 5-13  
J1 12-pin Auxiliary Connector 3-22  
Jumper Configurations and Connections  
(16-bit Drives) 3-6  
jumpers 3-7  
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  
K
key features 2-1  
L
G
Landing Zone Cylinder 5-68  
Link Bit 5-6, 5-13  
Log Pages 5-33  
LOG SELECT Command 5-32  
LOG SENSE Command 5-33, 5-34  
Logical Block Address 5-40, 5-51, 5-89,  
5-90, 5-93, 5-99, 5-100, 5-110, 5-  
112, 5-127, 5-128, 5-129, 5-134,  
5-136, 5-137, 5-138, 5-139, 5-142  
low 4-3  
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  
hardware options 3-6  
hardware requirements 2-4  
Head Offset Count 5-43  
host system 3-7  
hot plugging 6-11  
humidity 4-8  
low-level format 4-3  
M
manual organization 1-1  
mating connectors 3-21  
Maximum Burst Size 5-44  
maximum effective areal density 4-2  
maximum linear density 4-1  
maximum number of errors 4-11  
maximum screw torque 3-24  
maximum specifications 4-4  
MEDIUM ERROR 5-18, 5-100, 5-111,  
5-112, 5-122  
I
idle 4-6  
Immed 5-15, 5-18, 5-133, 5-134  
Implemented Operating Definition 5-25,  
5-26  
Implemented Operating Definition Page  
Medium Rotation Rate 5-68  
MaxtorAtlas10KV  
I-2  
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  
Parameter Pointer 5-34  
Parameter Pointer Control 5-34  
PCBA 3-24  
performance 2-2  
Peripheral Device 5-23  
Peripheral Qualifier 5-23  
physical shock 3-4  
pin assignments 3-22  
PList 5-95, 5-96, 5-97, 5-98  
PM 4-10  
POWER 4-5  
power down 4-5  
MODE SENSE (10) 5-1, 5-69  
Module Serial Number 5-24  
mounting 3-23, 3-24  
power on 4-4  
power requirements 4-6  
power sequencing 4-5  
Primary Defect List 5-15, 5-17, 5-18, 5-  
95, 5-96, 5-97, 5-98  
printed circuit board 3-7  
product overview 2-1  
Progress Indication 5-108, 5-121, 5-122  
Progress Indication Bytes 5-108  
multiple drive shipments 3-5  
N
naming conventions 1-3  
New Operating Definition 5-14  
NO SENSE 5-8, 5-111  
NOT READY 5-110, 5-111, 5-121, 5-  
122  
Notch and Partition 5-38, 5-50, 5-51  
Notch and Partition Page 5-50  
Number of Blocks 5-41, 5-134  
Number of Cylinders 5-68  
Number of Heads 5-68  
Q
Queue Algorithm Modifier 5-49  
R
R/W heads 4-1  
READ (10) Command 5-90  
READ (6) Command 5-71, 5-89  
READ BUFFER Command 5-91, 5-92  
READ CAPACITY Command 5-93, 5-  
94, 5-95, 5-97  
O
orientation 3-23  
outside zone 4-1  
READ DEFECT DATA Command 5-95  
READ LONG Command 5-99  
Read Retry Count 5-43  
P
Read-Write Error Recovery 5-38, 5-42,  
5-47  
Read-Write Error Recovery Page 5-42  
REASSIGN BLOCKS Command 5-100  
recording technology 4-1  
RECOVERED ERROR 5-43, 5-46, 5-  
111, 5-112  
Recovery Time Limit 5-43, 5-46  
packing assembly 3-5  
packing materials 3-4  
Page Length 5-35  
Pages Notched 5-51  
Parameter Code Reset 5-32  
Parameter List 5-11, 5-12, 5-17, 5-18, 5-  
37, 5-39, 5-130, 5-141  
Parameter List Length 5-37, 5-130, 5-141  
I-3  
Maxtor Atlas 10K V  
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  
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  
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,  
5-124  
RESERVE Command 5-124, 5-125  
reset 4-5  
Supported Additional Sense Codes 5-109,  
5-113  
Supported Diagnostic Page List 5-130, 5-  
131  
Response Data Format 5-23  
Retry Count 5-122  
Returned Logical Block Address 5-93  
REZERO UNIT Command 5-127  
Rigid Disk Geometry 5-67, 5-68  
Rigid Disk Geometry Page 5-67  
Rotational Offset 5-68  
Supported Diagnostics Page 5-102  
Supported Diagnostics Pages 5-102  
Supported Sense Keys 5-111  
SURF 5-66  
SYNCHRONIZE CACHE Command 5-  
134  
Synchronous Data Transfer 5-23  
rotational speed 4-1  
RPL Status Change 5-110  
T
TARGET TRANSFER DISABLE 5-23  
temperature 4-8  
terminology 1-2  
TEST UNIT READY Command 5-135  
Third Party Device ID 5-104, 5-105, 5-  
124, 5-125  
timing specifications 4-4  
total tracks 4-1  
total user sectors 4-1  
Track Skew Factor 5-66  
tracks density 4-1  
Transfer Length 5-11, 5-47, 5-89, 5-90,  
5-99, 5-137, 5-138, 5-139, 5-142  
transferred data 4-4  
S
SCSI configurations 2-1  
SCSI ID bits 3-8  
SCSI interface configurations 3-3  
SCSI-2 specification 1-3  
SEEK (10) Command 5-129  
SEEK (6) Command 5-128  
Segment Number 5-110  
SEND DIAGNOSTIC Command 5-130  
Sense Data Availability 5-108  
Sense Key 5-20, 5-110, 5-111, 5-112, 5-  
121, 5-122  
Sense Key Information Field Contents 5-  
112  
transient voltages 4-5  
Sense Keys 5-111  
Translate Address 5-101, 5-102, 5-103,  
5-130, 5-131  
Translate Address Page 5-101, 5-102, 5-  
131  
Translate Format 5-103  
typical specifications 4-4  
typographical conventions 1-3  
sequential switch times 4-4  
sequential throughput 4-2  
shipping container 3-4  
shock 4-10  
Shock Feet 3-4  
space requirements 3-3  
specifications 4-1, 4-10  
MaxtorAtlas10KV  
I-4  
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 returns 3-21  
Volume Serial Number 5-24, 5-25  
W
WRITE (10) Command 5-138  
WRITE (6) Command 5-137  
WRITE AND VERIFY Command 5-139  
WRITE BUFFER Command 5-140, 5-  
141  
WRITE LONG Command 5-142  
Write Retry Count 5-43  
WRITE SAME 5-12,5-13  
Z
zones per surface 4-1  
I-5  
Maxtor Atlas 10K V  

IKEA Cooktop ICR416RB01 User Manual
Intel 80C186XL User Manual
Lenovo ThinkVision L2440p User Manual
Line 6 3 7 User Manual
NEC LCD1501 User Manual
Nortel Networks Nortel Business Series Terminal T7316 User Manual
Panasonic DVD RV26 User Manual
Philips 32RF52S User Manual
Philips 107E50 User Manual
Philips Nicam 21PT5304 User Manual