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.

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.

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.

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 user’s

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

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

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

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 30_H.

• 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.

Figure 3-1 Dimensions for the Maxtor Atlas 10K V Hard Disk 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

through 3.5.4.

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

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).

Refer to Table 3-2 for SCSI ID pin assignments.

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

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

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

RESERVED

GROUND

+ATN

GROUND

+BSY

+ACK

+RST

+MSG

+SEL

+C/D

+REQ

+I/O

–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

TERMPWR

RESERVED

GROUND

–ATN

GROUND

–BSY

–ACK

–RST

–MSG

–SEL

–C/D

–REQ

–I/O

–DB (8)

–DB (9)

–DB (10)

–DB (11)

+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

NOT

APPLICABLE

12V GROUND

MATED 1

OPT 3.3V CHARGE

DIFFSNS

+DB (11)

+DB (10)

+DB (9)

12V

12 V

OPT 3.3 VOLTS

- DB (11)

- DB (10)

- DB (9)

- DB (8)

- I/O

+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)

NOT

APPLICABLE

+DB (2)

+DB (1)

+DB (0)

+DB (P1)

+DB (15)

+DB (14)

+DB (13)

+DB (12)

MATED 2

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

RESERVED

GROUND

–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

RESERVED

GROUND

–ATN

GROUND

–BSY

–ACK

–RST

–MSG

–SEL

–C/D

–REQ

–I/O

–DB (8)

–DB (9)

–DB (10)

–DB (11)

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

NOT APPLICABLE

12V GROUND

MATED 1

12V

12 V

OPT 3.3 VOLTS

–DB (11)

–DB (10)

–DB (9)

–DB (8)

–I/O

OPT 3.3V CHARGE

GROUND

MATED 2

–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 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

732K

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

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

75 Gbits/in

Servo Mechanical Timing Specifications:

Sequential Head Switch Time

0.3 ms read

0.5 ms write

Sequential Cylinder Switch Time

0.3 ms read

0.5 ms write

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

Random Average Seek (Write)

Full Stroke Seek (Read)

11.0 ms

typical

11.0 ms

typical

11.0 ms

typical

SCSI ‘Hard’ Reset Time

22 ms typical

25 sec

22 ms typical

25 sec

22 ms typical

25 sec

maximum

Power on to Drive Ready

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

Seek error rate

<10 in 10

Unrecoverable error rate

<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.

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

TYPICAL NOMINAL

MAXIMUM

Sequential Head Switch Time

0.3 ms typical (read)

0.5 ms typical (write)

N/A

Sequential Cylinder Switch Time

0.3 ms typical (read)

0.5 ms typical (write)

N/A

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

Random Average Seek (Write)

Average Rotational Latency

3 ms

1/3 Stroke Seek (Read)

<3 ms

4.5 ms

Full-Stroke Seek

11.0 ms

12.0 ms

20 ms

SCSI “Hard Reset Time”

20 ms

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 Limits¹

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)

(AMP RMS UNLESS OTHERWISE NOTED)

MODE OF

OPERATION

+12V

+5V

147.1

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,8^thEdition, December 2003.

Maxtor Atlas 10K V 4-7

4.7

MECHANICAL

The Maxtor Atlas 10K V hard disk drives have the following mechanical

characteristics:

Height¹:

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

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

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.

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

Shock linear Half Sine

2 msec

Read/Write

63G/30G

250 G

100 G

Shock linear Half Sine

15 G

7000

11 msec

Shock rotational

25,000

2 1

(rad/s ) , 2 msec

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

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

<10 events per 10 bits read

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

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

described in Table 5-58 an d Table 5-59 respectively.

Table 5-58 Unit Attention Condition Page (Page 0)

Bit

Byte

Rsvd

Page Code (00h)

Page Length (02h)

DUA

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.

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

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

Rsvd

Page Code (01h)

Page Length (0Ah)

RC EER

AWRE

ARRE

PER

DTE

DCR

Read Retry Count

Correction Span

Head Offset Count

Data Strobe Offset Count

Reserved

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.

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

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

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.

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

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

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

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

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

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 an d Table 5-63.

Table 5-62 Disconnect–Reconnect Page (Page 2)

Bit

Byte

Rsvd

Page Code (02h)

Page Length (0Eh)

Buffer Full Ratio

Buffer Empty Ratio

Bus Inactivity Limit

Disconnect Time Limit

Connect Time Limit

Maximum Burst Size

4 – 5

6 – 7

8 – 9

10 – 11

EMDP

Fairness Arbitration

DImm

Reserved

First Burst Size

DTDC

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.

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

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

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

5-42

Maxtor Atlas 10K V

Default

Value

Field

Description

Enable MODIFY DATA POINTER. Not supported by the drive.

EMDP

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

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

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

in Table 5-64 and Table 5-65 respectively.

Table 5-64 Verify Error Recovery Page-(Page 7)

Bit

Byte

Rsvd

Page Code (07h)

Page Length (0Ah)

EER

Reserved

PER

DTE

DCR

Verify Retry Count

Verify Correction Span

Reserved

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.

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

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

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.

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.

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

Byte

Rsvd

Page Code (08h)

Page Length (12h)

DISC Size

ABPF

CAP

WCE

RCD

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

Maximum Pre-Fetch Ceiling

FSW

LBCSS

DRA

Reserved

Number of Cache Segments

Cache Segment Size

Reserved

14 – 15

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

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

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

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

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

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.

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.

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.

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

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

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

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

5-69 respectively.

Table 5-68 Control Mode Page - Data Format (Page 0Ah)

Bit

Byte

Rsvd

Page Code (0Ah)

Page Length (0Ah)

Reserved

Queue Algorithm Modifier

GLTSD

RLEC

DQue

Re-

served

Qerr

5-46

Maxtor Atlas 10K V

UAAER

EECA

RAC

Reserved

SWP

Reserved

RAERP

EAERP

6 – 7

8 – 9

Ready AEN Holdoff Period

Busy Timeout Period

MSB

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.

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

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.

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

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

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

RAERP

UAAERP

EAERP

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

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

Byte

Rsvd

Page Code (0Ch)

Page Length (16h)

Reserved

LPN

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.

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.

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 T a ble 5-72 and T a ble 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

LONG(0)

Page Code (19h)

Page Length (06h)

Reserved

Protocol Identifier (1h)

Reserved

MSB

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

LONG (1)

Page Code (19h)

Subpage Code

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

Reserved

Driver Strength

Drive’s Asymmetry

Drive’s Slew Rate

Reserved

Driver Precompensation

Reserved

Vendor Specific

Reserved

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 T a ble 5-76; however the content of the fields is vendor specific. Only values

for the current I_T nexus are reported.

Table 5-76 Saved Training Configuration Subpage (02h)

Bit

Byte

MSB

Reserved

LSB

MSB

DB(0) Value

MSB

DB(15) Value

P_ORCA Value

P1 Value

LSB

BSY Value

SEL Value

RST Value

REQ Value

ACK Value

ATN Value

C/D Value

I/O Value

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

Transfer Period Factor

Reserved

Req/Ack Offset

Transfer Width Exponent

Protocol Option Bits

Transceiver

Reserved

SENT_

PCOMP_EN

RECEIVED

PCOMP_EN

Mode

Reserved

Vendor Specific

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

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

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

defined in Table 5-79.

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

Minimum Transfer Period Factor

Reserved

Maximum Req/Ack Offset

Maximum Transfer Width Exponent

Protocol Option Bits Supported

Reserved

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

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

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 T a ble 5-82 and T a ble 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

Page Code (1Ch)

Page Length (0Ah)

EWASC DExcpt

Perf

Reserved

Test

Rsv’d

LogErr

MRIE

(MSB)

4 - 7

Interval Timer

(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.

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

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

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

When this bit = 0, it indicates that log sense information is vendor-unique.

NOTE: LogErr = 0 is the only value supported.

LogErr

MRIE

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.

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

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.

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.

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.

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.

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),

Table 5-88, for descriptions of the fields. See Table 5-86 for the Mode Parameter

Header (10 Byte) — Data Format and Table 5-87 for the Mode Parameter Block

Descriptor – Data Format. See Table 5-48 for mode parameter block field

descriptions.

Table 5-85 MODE SELECT (10) Command Descriptor Block-Data Format

Bit

Byte

Operation Code (55h)

Reserved

2 - 6

7 - 8

Reserved

Parameter List Length

Control

Table 5-86 Mode Parameter Header (10-Byte)-Data Format

Bit

Byte

(MSB)

0 - 1

Mode Data Length

(LSB)

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

Byte

0 - 3

(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-92.

Table 5-89 MODE SENSE (6) Command Descriptor Block-Data Format

Bit

Byte

Operation Code (1Ah)

DBD

Reserved

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

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

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

Total cylinder head and

rotational speed

04h

Rigid Disk Geometry

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

Byte

Rsvd

Page Code (03h)

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

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.

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

Byte

Rsvd

Page Code (04h)

Page Length (16h)

Number of Cylinders

Number of Heads

2 - 4

6 - 8

Starting Cylinder - Write Precompensation

Starting Cylinder - Reduced Write Current

Drive Step Rate (0)

9 - 11

12 - 13

14 - 16

Landing Zone Cylinder

Reserved

RPL

Rotational Offset

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.

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,

Table 5-99 for Mode Parameter Header (1 0 Byte) — Data Format, and Table 5-100

for Mode Parameter Block Descriptor – Data Format. Refer to Table 5-90,Table 5-

92 , and Table 5-101 for descriptions of the fields.

Table 5-98 MODE SENSE (10) Command Descriptor Block-Data Format

Bit

Byte

Operation Code (5Ah)

DBD

Reserved

Page Code

Sub Page Code

Reserved

4 – 6

(MSB)

7 – 8

Allocation Length

Control

(LSB)

Table 5-99 Mode Parameter Header (10 Byte)-Data Format

Bit

Byte

(MSB)

0 - 1

Mode Data Length

(LSB)

Medium Type

Device-Specific Parameter

Reserved

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

(MSB)

0 - 3

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

Operation Code (5Eh)

Reserved

Service Action

2 - 6

Reserved

(MSB)

Allocation Length

(LSB)

7 – 8

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 and Table 5-105 respectively.

Table 5-104 Read Keys Parameters-Data Format

Bit

Byte

(MSB)

0 - 3

Generation

(LSB)

(MSB)

4 - 7

Additional Length (n – 7)

(Reservation Key List Follows in Bytes 8 – n)

(MSB)

8 - 15

First Reservation Key

(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

described in Table 5-106 and Table 5-107 respectively.

Table 5-106 Read Reservations Parameters-Data Format

Bit

Byte

(MSB)

0 - 3

4 - 7

8 - n

Generation

(LSB)

(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

(MSB)

0 - 7

Reservation Key

Scope-Specific Address

Reserved

(LSB)

(MSB)

8 - 11

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.

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

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.

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

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.

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

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

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

Access

READ

Shared

LU EX

WRITE

Exclusive

LU EX

READ

Exclusive

LU EX

Exclusive

Access *

LU EX

Shared

Access *

LU EX

READ Shared

N N

Y Y

Y O

Y Y

Y O

Y Y

Y O

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

Y Y

Y O

Y Y

Y O

Y Y

Y O

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

WRITE

Exclusive

READ

Exclusive

Access *

Shared

Access *

Y Y

Y O

WRITE

Exclusive

N N

Exclusive

Access RO

Y Y

Y O

Y Y

Y O

Y Y

Y O

Y Y

Y O

Y Y

Y O

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

Operation Code (5Fh)

Reserved

Service Action

Scope

Type

3 - 6

Reserved

(MSB)

7 – 8

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

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.

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.

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.

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 Command’s Service Action Descriptions

Code

Name

Description

When the command executes a Register service action, it registers a reservation key with a

device server without generating a reservation. 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

• 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;

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.

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

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.

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.

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.

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,

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

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

Byte

0 – 7

(MSB)

Reservation Key

Service Action Reservation Key

Scope-Specific Address

(LSB)

(MSB)

8 – 15

16 – 19

(LSB)

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

Type

Element

Reservation Key

Parameters

Reserve

Ignored

Valid

Ignored

Valid

Ignored

Valid

Ignored

Reserve

Extent

Element

Extent Valid

Ignored

Reserved

Release

Ignored

Release

Extent

Element

Ignored

Extent Valid

Element Valid

Ignored

Release

Clear

Ignored

Pre-empt

Ignored

Pre-empt

Extent

Element

Valid

Extent Valid

Element Valid

Ignored

Pre-empt

Valid

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

descriptions are shown in Table 5-119 and Table 5-120 respectively.

Table 5-119 READ (6) Command-Data Format

Bit

Byte

Operation Code (08h)

Logical Block Address

Logical Block Address (continued)

2 - 3

Reserved

Transfer Length

Control

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

descriptions are shown in Table 5-121 and Table 5-122 respectively.

Table 5-121 READ (10) Command-Data Format

Bit

Byte

Operation Code (28h)

DPO FUA

2 - 5

Reserved

RelAdr

Logical Block Address

Reserved

7 - 8

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

descriptions are shown in Table 5-123 and Table 5-124 respectively.

Table 5-123 READ BUFFER Command-Data Format

Bit

Byte

Operation Code (3Ch)

Reserved

Mode

Buffer ID

Buffer Offset

Allocation Length

Control

3 - 5

6 - 8

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

Operation Code (25h)

Reserved

RelAdr

2 - 5

6 - 7

Logical Block Address

Reserved

PMI

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

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

Table 5-133), followed by any Defect Descriptors (Table 5-130 and Table 5-131).

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

Operation Code (37h)

Reserved

Plist

Glist

Defect List Format

3 - 6

Reserved

(MSB)

7 - 8

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:

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

¹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

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

Byte

0 - 2

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

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-1 37).

The READ DEFECT DATA (12) Command Descriptor Block is shown in Table 5-

134; the data fields are described in Table 5-135.

Table 5-134 READ DEFECT DATA (12) Command-Data Format

Bit

Byte

Operation Code (B7h)

Plist Glist

Reserved

Defect List Format

2 - 5

(MSB)

6 - 9

Allocation Length

(LSB)

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:

000b

100b

Block Format (Table 5-136).

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.