Maxtor DIAMONDMAXTM 83240D3, DIAMONDMAXTM 88400D8, DIAMONDMAXTM 2160, DIAMONDMAXTM 84320D4, DIAMONDMAXTM 82160D2 User Manual

...

DiamondMax™ 2160

88400D8, 86480D6, 84320D4 83240D3 and 82160D2

Part #1384/A

All material contained herein Copyright © 1997 Maxtor Corporation. CrystalMax™, CrystalMax™ 1080, DiamondMax™, DiamondMax™ 1750, DiamondMax™ 2160 and MaxFax™ are trademarks of Maxtor Corporation. No Quibble® Service is a registered trademark of Maxtor Corporation. Other brands or products are trademarks or registered trademarks of their respective holders. Contents and specifications subject to change without notice. All rights reserved. Printed in the U.S.A. 9/97

Corporate Headquarters

510 Cottonwood Drive Milpitas, California 95035

Tel: 408-432-1700 Fax: 408-432-4510

Research and Development Engineering Center

2190 Miller Drive Longmont, Colorado 80501

Tel: 303-651-6000 Fax: 303-678-2165

Revisions Manual No. 1384

VER.ONCENOITCESNOITPIRCSED ETAD

AB14687

llAesaelerlaitinI 0

79/

Before Y ou Begin

Thank you for your interest in the Maxtor DiamondMax™ 2160 AT hard disk drives. This manual provides technical information for OEM engineers and systems integrators regarding the installation and use of the 88400D8, 86480D6, 84320D4, 83240D3 and 82160D2.

Drive repair should be performed only at an authorized repair center. For repair information, contact the Maxtor Customer Service Center at 800-2MAXTOR or 408-432-1700.

Before unpacking the hard drive, please review Sections 1 through 4.

CAUTION

Maxtor DiamondMax 2160 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.

2 3

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.

Please do not remove or cover up Maxtor factory-installed drive labels.

They contain information required should the drive ever need repair.

DIAMONDMAX 1750 PRODUCT MANUAL

Contents

Section 1 — Introduction

Maxtor Corporation 1 - 1

Products 1 - 1

Support 1 - 1 Manual Organization 1 - 1 Abbreviations 1 - 1 Conventions 1 - 2

Key Words 1 - 2

Numbering 1 - 2

Signal Conventions 1 - 2

Section 2 — Product Description

The DiamondMax™ 2160 Product Features 2 - 2

Functional/Interface 2 - 2

Zone Density Recording 2 - 2 Read/Write Multiple Mode 2 - 2 UltraDMA - Mode 2 2 - 2 Multi-word DMA (EISA Type B) - Mode 2 2 - 2 Sector Address Translation 2 - 2 Logical Block Addressing 2 - 3 Defect Management Zone 2 - 3 On-the-Fly Hardware Error Correction Code (ECC) 2 - 3 Software ECC Correction 2 - 3 Automatic Head Park and Lock Operation 2 - 3

Cache Management 2 - 4

Buffer Segmentation 2 - 4

Read-Ahead Mode 2 - 4

Automatic Write Reallocation (AWR) 2 - 4

Write Cache Stacking 2 - 4 Major HDA Components 2 - 5

Drive Mechanism 2 - 5

Rotary Actuator 2 - 5

Read/Write Electronics 2 - 5

Read/Write Heads and Media 2 - 5

Air Filtration System 2 - 5

Microprocessor 2 - 5 Subsystem Configuration 2 - 6

Dual Drive Support 2 - 6

Cable Select Option 2 - 6 Jumper Location/Configuration 2 - 6

4092 Cylinder Limitation 2 - 6

DIAMONDMAX 1750 PRODUCT MANUAL

Section 3 — Product Specifications

Configuration 3 - 1 Performance 3 - 1 Physical Dimensions 3 - 2 Power Requirements 3 - 3 Power Mode Definitions 3 - 3 Environmental 3 - 3 Shock and Vibration 3 - 4 Reliability and Maintenance 3 - 4 Data Reliability 3 - 4 Acoustic Noise 3 - 4 EPA Energy Star Compliance 3 - 4 EMC/EMI 3 - 5 Standard Test Methods 3 - 5 Safety Regulatory Compliance 3 - 5

Section 4 — Handling and Installation

Pre-formatted Drive 4 - 1 Important Notice 4 - 1 Hard Drive Handling Precautions 4 - 1 Electro-Static Discharge (ESD) 4 - 1 Unpacking and Inspection 4 - 2 Repacking 4 - 3 Physical Installation 4 - 3 Drive Jumper Settings 4 - 4 Mounting Drive in System 4 - 4 Attaching IDE Interface and Power Cables 4 - 6 Attaching System Cables 4 - 7 System Setup 4 - 8 Hard Drive Preparation 4 - 10

Section 5 — AT Interface Description

Interface Connector 5 - 1 Pin Description Summary 5 - 1 Pin Description Table 5 - 2 PIO Timing 5 - 3 DMA Timing 5 - 4 Ultra DMA Timing Parameters 5 - 5

DIAMONDMAX 1750 PRODUCT MANUAL

Section 6 — Host Software Interface

Task File Registers 6 - 1

Data Register 6 - 1

Error Register 6 - 1

Features Register 6 - 1

Sector Count Register 6 - 2

Sector Number Register 6 - 2

Cylinder Number Registers 6 - 2

Device/Head Register 6 - 2

Status Register 6 - 2 Command Register 6 - 3

Read Commands 6 - 3

Write Commands 6 - 3

Mode Set/Check Commands 6 - 3

Power Mode Commands 6 - 3

Initialization Commands 6 - 3

Seek, Format, and Diagnostic Commands 6 - 3

S.M.A.R.T. Commands 6 - 3 Summary 6 - 4 Control Diagnostic Registers 6 - 5

Alternate Status Register 6 - 5

Device Control Register 6 - 5

Digital Input Register 6 - 5 Reset and Interrupt Handling 6 - 6

iii

DIAMONDMAX 1750 PRODUCT MANUAL

Section 7 — Interface Commands

Command Summary 7 - 1 Read Commands 7 - 2

Read Sector(s) 7 - 2 Read Verify Sector(s) 7 - 2 Read Sector Buffer 7 - 2 Read DMA 7 - 3 Read Multiple 7 - 3 Set Multiple 7 - 3

Write Commands 7 - 4

Write Sector(s) 7 - 4 Write Verify Sector(s) 7 - 4 Write Sector Buffer 7 - 4 Write DMA 7 - 5 Write Multiple 7 - 5 Ultra DMA 7 - 5

Set Feature Commands 7 - 5

Set Features Mode 7 - 5

Power Mode Commands 7 - 7

Standby Immediate 7 - 7 Idle Immediate 7 - 7 Standby 7 - 7 Idle 7 - 7 Check Power Mode 7 - 7 Set Sleep Mode 7 - 7 Default Power-on Condition 7 - 7

Initialization Commands 7 - 9

Identify Drive 7 - 9

Initialize Drive Parameters 7 - 12 Seek, Format, and Diagnostic Commands 7 - 13 S.M.A.R.T. Command Set 7 - 14

Section 8 — Service and Support

Service Policy 8 - 1 No Quibble Service 8 - 1 Support 8 - 1

Glossary

Glossary GL - 1

DIAMONDMAX 1750 PRODUCT MANUAL

Figures

Figure Title Page

2 - 1 PCBA Jumper Locations and Configuration 2 - 6 3 - 1 Outline and Mounting Dimensions 3 - 2 4 - 1 Multi-pack Shipping Container 4 - 2 4 - 2 Single-pack Shipping Container (Option A) 4 - 3 4 - 3 Single-pack Shipping Container (Option B) 4 - 3 4 - 4 Master/Slave Jumper Detail 4 - 4 4 - 5 5.25-inch Mounting Brackets/Slider Rails 4 - 4 4 - 6 5.25-inch Installation 4 - 5 4 - 7 3.5-inch Installation 4 - 5 4 - 8 IDE Interface and Power Cabling Detail 4 - 6 4 - 9 System Interface Card Cabling 4 - 7 4 - 10 System Mother Board Cabling 4 - 7 4 - 11 J46 (4092 Cylinder Limitation) Detail 4 - 9 5 - 1 Data Connector 5 - 1 5 - 2 PIO Data Transfer to/from Device 5 - 3 5 - 3 Multi-word DMA Data Transfer 5 - 4 5 - 4 Initiating an Ultra DMA Data In Burst 5 - 5 5 - 5 Sustained Ultra DMA Data In Burst 5 - 6 5 - 6 Host Pausing an Ultra DMA Data In Burst 5 - 6 5 - 7 Device Terminating an Ultra DMA Data In Burst 5 - 7 5 - 8 Host Terminating an Ultra DMA Data In Burst 5 - 7 5 - 9 Initiating an Ultra DMA Data Out Burst 5 - 8 5 - 10 Sustained Ultra DMA Data Out Burst 5 - 8 5 - 11 Device Pausing an Ultra DMA Data Out Burst 5 - 9 5 - 12 Host Terminating an Ultra DMA Data Out Burst 5 - 9 5 - 13 Device Terminating an Ultra DMA Data Out Burst 5 - 10

DIAMONDMAX 1750 – INTRODUCTION

SECTION 1

Introduction

Maxtor Corporation

Maxtor Corporation has been providing high-quality computer storage products since 1982. Along the way, we’ve seen many changes in data storage needs. Not long ago, only a handful of specific users needed more than a couple hundred megabytes of storage. Today, downloading from the Internet and CD-ROMs, multimedia, networking and advanced office applications are driving storage needs even higher. Even home PC applications need capacities measured in gigabytes, not megabytes.

Products

Maxtor’s products meet those demanding storage capacity requirements with room to spare. They feature proven compatibility and reliability. While DiamondMax™ 2160 is the latest addition to our family of high performance desktop hard drives, the DiamondMax™ 1750 and CrystalMax™ 1080 series hard drives deliver industry-leading capacity, performance and value for many PC applications.

Support

No matter which capacity, all Maxtor hard drives are supported by our commitment to total customer satisfaction and our No Quibble (http://www.maxtor.com) – puts you in touch with either technical support or customer service. We’ll provide you the information you need quickly, accurately and in the form you prefer – a fax, a downloaded file or a conversation with a representative.

Service guarantee. One call – or a visit to our home page on the Internet

Manual Organization

This hard disk drive reference manual is organized in the following method:

❏ Section 1 – Introduction ❏ Section 2 – Description ❏ Section 3 – Specifications ❏ Section 4 – Installation ❏ Section 5 – AT Interface ❏ Section 6 – Host Software Interface ❏ Section 7 – Interface Commands ❏ Section 8 – Service and Support ❏ Appendix – Glossary

Abbreviations

VRBBANOITPIRCSEDVRBBANOITPIRCSED

ATAtnemhcattaTABMetybagem

ipbhcnirepstibces/stibMdnocesrepstibagem

SHCrotces-daeh-rednilycces/BMdnocesrepsetybagem

bdslebicedzHMztrehagem

ABddethgiewA,slebicedsmdnocesillim

AMDsseccayromemtceridBSMtibtnacifingistsom

CCEedocnoitcerrocrorreVmstlovillim

icfhcnirepsegnahcxulfsnsdnocesonan

GnoitareleccaOIPtuptuo/tupnidemmargorp

BGetybagigMPRetunimrepsnoitulover

zHztrehipthcnirepskcart

BKetybolikAMDUsseccayromemtceridartlu

ABLsserddakcolblacigolcesµdnocesorcim

BSLtibtnacifingistsaelVstlov

AmserepmaillimWsttaw

1 – 1

DIAMONDMAX 1750 – INTRODUCTION

Conventions

If there is a conflict between text and tables, the table shall be accepted as being correct.

Key Words

The names of abbreviations, commands, fields and acronyms used as signal names are in all uppercase type (e.g., IDENTIFY DRIVE). Fields containing only one bit are usually referred to as the “name” bit instead of the “name” field.

Names of drive registers begin with a capital letter (e.g., Cylinder High register).

Numbering

Numbers that are not followed by a lowercase “b” or “h” are decimal values. Numbers that are followed by a lowercase “b” (e.g., 01b) are binary values. Numbers that are followed by a lowercase “h” (e.g., 3Ah) are hexadecimal values.

Signal Conventions

Signal names are shown in all uppercase type. All signals are either high active or low active signals. A dash character (-) at the end of a signal name

indicates that the signal is low active. A low active signal is true when it is below ViL and is false when it is above ViH. A signal without a dash at the end indicates that the signal is high active. A high active signal is true when it is above ViH and is false when it is below ViL.

When a signal is asserted, it means the signal is driven by an active circuit to its true state. When a signal is negated, it means the signal is driven by an active circuit to its false state. When a signal is released, it means the signal is not actively driven to any state. Some signals have bias

circuitry that pull the signal to either a true or false state when no signal driver is actively asserting or negating the signal. These instances are noted under the description of the signal.

1 – 2

PRODUCT DESCRIPTION

SECTION 2

Product Description

Maxtor DiamondMax™ 2160 AT disk drives are 1-inch high, 3.5-inch diameter random access storage devices which incorporate an on-board Ultra DMA/ATA controller. High capacity is achieved by a balanced combination of high areal recording density and the latest data encoding and servo techniques.

Maxtor's latest advancements in electronic packaging and integration methods have lowered the drive's power consumption and increased its reliability. Advanced magneto-resistive read/write heads, an state-of-the-art head/ disk assembly using an integrated motor/spindle design allow up to four disks in a 3.5-inch package.

Exceptionally high data transfer rates and < 9.7 ms access times make these performance series disk drives especially well-suited to high speed desktop and server applications.

DiamondMax 2160 Key Features

ANSI ATA-4 compliant PIO Mode 4 interface (Enhanced IDE) Supports Ultra DMA Mode 2 for 33 MB/sec data transfers 256 KB buffer with multi-adaptive cache manager < 9.7 ms seek time Zone density and I.D.-less recording

High reliability with Outstanding shock resistance at 150 Gs High durability with 50K constant start/stop cycles Advanced multi-burst on-the-fly Error Correction Code (ECC) Extended data integrity with ECC protected data and fault tolerant servo synchronization fields Supports EPA Energy Star Standards (Green PC Friendly) with ATA powering savings commands Auto park and lock actuator mechanism Low power consumption S.M.A.R.T. Capability

Note: Maxtor defines one megabyte as 106 or one million bytes and one gigabyte as 109 or one billion bytes.

500,000 hour MTBF

2 – 1

PRODUCT DESCRIPTION

Product Features

Functional / Interface

Maxtor DiamondMax™ 2160 hard drives contain all necessary mechanical and electronic parts to interpret control signals and commands from an AT-compatible host computer. See Section 3 Product Specifications, for complete drive specifications.

Zone Density Recording

The disk capacity is increased with bit density management – common with Zone Density Recording. Each disk surface is divided into 16 circumferential zones. All tracks within a given zone contain a constant number of data sectors. The number of data sectors per track varies in different zones; the outermost zone contains the largest number of data sectors and the innermost contains the fewest.

Read/Write Multiple Mode

This mode is implemented per ANSI ATA/ATAPI-4 specification. Read/Write Multiple allows the host to transfer a set number of sectors without an interrupt request between them, reducing transfer process overhead and improving host performance.

UltraDMA - Mode 2

Maxtor DiamondMax 2160 hard drives fully comply with the new ANSI Ultra DMA protocol, which greatly improves overall AT interface performance by significantly improving burst and sustained data throughput.

Multi-word DMA (EISA Type B) - Mode 2

Supports multi-word Direct Memory Access (DMA) EISA Type B mode transfers.

Sector Address Translation

All DiamondMax 2160 drives feature a universal translate mode. In an AT/EISA-class system, the drive may be configured to any specified combination of cylinders, heads and sectors (within the range of the drive's formatted capacity). DiamondMax 2160 drives power-up in a translate mode:

LEDOMSREDNILYCSDAEHSROTCESYTICAPAC

8D00488872,616136BM004,8

6D08468593,315136BM084,6

4D02348039,85136BM023,4

3D04238796,65136BM042,3

2D06128564,45136BM061,2

2 – 2

PRODUCT DESCRIPTION

Logical Block Addressing

The Logical Block Address (LBA) mode can only be utilized in systems that support this form of translation. The cylinder, head and sector geometry of the drive, as presented to the host, differs from the actual physical geometry.

The host AT computer may access a drive of set parameters: number of cylinders, heads and sectors per track, plus cylinder, head and sector addresses. However, the drive can’t use these host parameters directly because of zoned recording techniques. The drive translates the host parameters to a set of logical internal addresses for data access.

The host drive geometry parameters are mapped into an LBA based on this formula:

LBA = (HSCA - 1) + HHDA x HSPT + HNHD x HSPT x HCYA (1)

where HSCA = Host Sector Address, HHDA = Host Head Address

= (HSCA - 1) + HSPT x (HHDA + HNHD x HCYA) (2)

HCYA = Host Cylinder Address, HNHD = Host Number of Heads HSPT = Host Sectors per Track

The LBA is checked for violating the drive capacity. If it does not, the LBA is converted to physical drive cylinder, head and sector values. The physical address is then used to access or store the data on the disk and for other drive related operations.

Defect Management Zone (DMZ)

Each drive model has a fixed number of spare sectors per drive, all of which are located at the end of the drive. Upon detection of a bad sector that has been reassigned, the next sequential sector is used.

For example, if sector 3 is flagged, data that would have been stored there is “pushed down” and recorded in sector 4. Sector 4 then effectively becomes sector 3, as sequential sectors are “pushed down” across the entire drive. The first spare sector makes up for the loss of sector 3, and so maintains the sequential order of data. This push down method assures maximum performance.

On-the-Fly Hardware Error Correction Code (ECC)

10 bits, single burst, guaranteed

Software ECC Correction

64 bits, single burst, guaranteed 28 bits, double bursts, guaranteed

Automatic Park and Lock Operation

Immediately following power down, dynamic braking of the spinning disks delays momentarily allowing the read/write heads to move to an inner mechanical stop. A small fixed magnet holds the rotary actuator in place as the disk spins down. The rotary actuator is released only when power is again applied.

2 – 3

PRODUCT DESCRIPTION

Cache Management

Buffer Segmentation

The data buffer is organized into two segments: the data buffer and the micro controller scratch pad. The data buffer is dynamically allocated for read and write data depending on the commands received. A variable number of read and write buffers may exist at the same time.

Read-Ahead Mode

Normally, this mode is active. Following a read request, disk read-ahead begins on the first sector and continues sequentially until the allocated buffer is full. If a read request is received during the read-ahead operation, the buffer is examined to determine if the request is in the cache. If a cache hit occurs, readahead mode continues without interruption and the host transfer begins immediately.

Automatic Write Reallocation (AWR)

This feature is part of the write cache and reduces the risk of data loss during deferred write operations. If a disk error occurs during the disk write process, the disk task stops and the suspect sector is reallocated to a pool of alternate sectors located at the end of the drive. Following reallocation, the disk write task continues until it is complete.

Write Cache Stacking

Normally, this mode is active. Write cache mode accepts the host write data into the buffer until the buffer is full or the host transfer is complete. A command complete interrupt is generated at the end of the transfer.

A disk write task begins to store the host data to disk. Host write commands continue to be accepted and data transferred to the buffer until either the write command stack is full or the data buffer is full. The drive may reorder write commands to optimize drive throughput.

2 – 4

PRODUCT DESCRIPTION

Major HDA Components

Drive Mechanism

A brush-less DC direct drive motor rotates the spindle at 5,200 RPM (±0.1%). The dynamically balanced motor/spindle assembly ensures minimal mechanical run-out to the disks. A dynamic brake provides a fast stop to the spindle motor upon power removal. The speed tolerance includes motor performance and motor circuit tolerances.

Rotary Actuator

All DiamondMax™ 2160 drives employ a rotary voice coil actuator which consists of a moving coil, an actuator arm assembly and stationary magnets. The actuator moves on a low-mass, low-friction center shaft. The low friction contributes to fast access times and low power consumption.

Read/Write Electronics

An integrated circuit mounted within the sealed head disk assembly (near the read/write heads) provides up to eight head selection (depending on the model), read pre-amplification and write drive circuitry.

Read/Write Heads and Media

Low mass, low force magneto-resistive read/write heads record data on 3.5-inch diameter disks. Maxtor uses a sputtered thin film medium on all disks for DiamondMax 2160 drives.

Air Filtration System

All DiamondMax 2160 drives are assembled in a Class 100 controlled environment. Over the life of the drive, a 0.1 micron filter and breather filter located within the sealed head disk assembly (HDA) maintain a clean environment to the heads and disks. DiamondMax 2160 drives are designed to operate in a typical office environment with minimum environmental control.

Microprocessor

The microprocessor controls the following functions for the drive electronics:

Command execution Cache management Data correction and error recovery Diagnostic execution Data sequencing Head positioning (including error recovery) Host interface Index detection Spin speed control Seeks Servo S.M.A.R.T.

2 – 5

PRODUCT DESCRIPTION

Subsystem Configuration

Dual Drive Support

Two drives may be accessed via a common interface cable, using the same range of I/O addresses. The drives are jumpered as device 0 or 1 (Master/Slave), and are selected by the drive select bit in the Device/Head register of the task file.

All Task File registers are written in parallel to both drives. The interface processor on each drive decides whether a command written to it should be executed; this depends on the type of command and which drive is selected. Only the drive selected executes the command and activates the data bus in response to host I/O reads; the drive not selected remains inactive.

A master/slave relationship exists between the two drives: device 0 is the master and device 1 the slave. When J50 is closed (factory default, figure 2-1), the drive assumes the role of master; when open, the drive acts as a slave. In single drive configurations, J50 must be closed.

Cable Select Option

CSEL (cable select) is an optional feature per ANSI ATA specification. Drives configured in a multiple drive system are identified by CSEL’s value:

– If CSEL is grounded, then the drive address is 0. – If CSEL is open, then the drive address is 1.

Jumper Location/Configuration

Darkened jumper pins indicate factory-installed (default) shunts.

Figure 2-1

PCBA Jumper Location and Configuration

evalS/retsaM

tceleSelbaC

*delbasiD

delbanE

*delbasiD

delbanE

devreseRyrotcaFO

devreseRyrotcaF O

NOITARUGIFNOCREPMUJ05J84J64J44J24J

*metsysevirdelgnisnievirdylnO

*metsysevirdlaudnievirdretsaM

metsysevirdlaudnievirdevalS

noitatimiLrednilyC2904

desolC=CtluafeD=*yeK

)dellatsnirepmuj(

nepO=O

)dellatsnirepmujon(

4092 Cylinder Limitation

On some older BIOS', primarily those that auto-configure the disk drive, a hang may occur when the drive cylinder value exceeds 4096. The 4092 Cylinder Limitation jumper reduces the capacity in the Identify Drive to 4092 allowing large capacity drives to work with older BIOS'. A software driver is required to access the full capacity of the drive.

2 – 6

Product Specifications

Models and Capacities

LEDOM8D004886D084684D023483D042382D06128

yticapaCdettamroF )edoMABL( BM004,8BM084,6023,4BMBM042,3BM061,2

Drive Configuration

LEDOM8D004886D084684D023483D042382D06128

dohteMgnidocnE71/61LLR4RPE

evaelretnI1:1

metsySovreSdeddebmE

epyT/eziSreffuB MARDODE/BK652

sdaeH/secafruSataD86432

ytisneDlaireAni/bM005,1

ecafruSrepskcarT)srednilyC(528,7

ytisneDkcarTipt777,7

ytisneDxulFicfk902-461

ytisneDgnidroceRipbk791-551

kcarTrepsrotceS213-591

evirDrepsrotceS808,184,61677,856,21481,934,8883,923,6295,912,4

01saetybagemenosenifedrotxaM

ecafretnI/rellortnoCdetargetnIEDIE/4-ATA

ecafruSrepsenoZataD61

kcolB/rotceSrepsetyB215

01saetybagigenodnasetybnoillimenoro

.setybnoillibenoro

PRODUCT SPECIFICATIONS

SECTION 3

Performance Specifications

LEDOM8D004886D084684D023483D042382D06128

semiTkeeS)lacipyt(

kcart-ot-kcarTsm0.1<

egarevA

mumixaM

ycnetaLegarevAsm77.5

deepSlanoitatoR)%1.0±(MPR002,5

daehrevOdnammoCrellortnoCsm3.0<

etaRrefsnarTataD

artlU()2edoM-AMD

ecafretnImorf/oT

aideMmorf/oT

emiTtratS )ydaeRevirDot0( lacipytces3.7

)2edoM-AMDdrow-itluM/4OIP(

7.9

sm81

ces/BM0.33otpu

otpu

ces/BM7.61

ces/BM0.71ot6.01

3 – 1

PRODUCT SPECIFICATIONS

Physical Dimensions

RETEMARAPDRADNATSCIRTEM

thgieHhcni00.1sretemillim4.52

htgneLsehcni57.5sretemillim1.641

htdiWsehcni00.4sretemillim6.101

thgieWsdnuop2.1smargolik5.0

3 – 2

Figure 3 - 1

Outline and Mounting Dimensions

PRODUCT SPECIFICATIONS

Power Requirements (Average)

EDOM%8±V21%5±V5REWOP

pu-nipS)kaep(Am0701Am093W0.41

keeSAm035Am514W5.8

etirW/daeRAm552Am544W0.5

eldIAm052Am052W0.4

ybdnatSAm2Am041W7.0

Power Mode Definitions

Spin-up

The drive is spinning up following initial application of power and has not yet reached full speed.

Seek

A random access operation by the disk drive.

Read/Write

Data is being read from or written to the drive.

Idle

The drive is spinning, the actuator is parked and powered off and all other circuitry is powered on. The drive is capable of responding to read commands within 40 ms.

Standby

The spin motor is not spinning. The drive will leave this mode upon receipt of a command that requires disk access. The time-out value for this mode is programmable. The buffer is active to accept write data.

EPA Energy Star Compliance

Maxtor Corporation supports the goals of the U.S. Environmental Protection Agency’s Energy Star program to reduce the electrical power consumption of computer equipment.

Environmental Limits

RETEMARAPGNITAREPOEGAROTS/GNITAREPO-NON

erutarepmeTC°55otC°5 .3.205dohtem,E018-DTS-LIMrep)C°04-(erutarepmetwol

.snoitidnocdecudni-toh;yrogetaccitamilc

tneidarGlamrehT (ruohrepC°52)mumixam

ytidimuHevitaleR %59ot%5gnisnednoc-non()

bluBteW 72°C )mumixam(

edutitlAteef000,01ot002-

)egnarsiht

esioNcitsuocA)edomeldI(rewopdnuosegarevaABd73

gnirruccoyllarutanynahtiw(

nihtiwetarytidimuhdnaerutarepmet

)enohporcim01,9777OSIrep(

.erusserptnemtrapmoc

,3.105dohtem,E018-DTS-LIMrep)C°17(erutarepmethgih

tset)edutitla(erusserpwol,3.005dohtem,E018-DTS-LIMreP

ogractfarcriatropsnart,2noitidnoctset;egarots.Ierudecorp

3 – 3

PRODUCT SPECIFICATIONS

Shock and Vibration

RETEMARAPGNITAREPOGNITAREPO-NON

kcohSlacinahceMsrorreon,sm0.2,sG02 egamadon,sm0.2,sG051

noitarbiVmodnaRcisaB,4.415dohteM,E018-DTS-LIMreP

noitarbiVeniStpewS

zH02-5

zH003-12

Reliability Specifications

AFR

< 1.7% The annualized average failure rate (AFR) applies to the period prior

zH/

G5210.0tazH01

G5210.0tazH04

zH/

G521000.0tazH005

zH/

edutilpmakaepG0.1

edutilpmaelbuodsehcni940.0

.eliforpDSPsixalacitreV,noitatropsnart

G510.0tazH01

zH/

G510.0tazH04

zH/

G51000.0tazH005

zH/

to the expiration of component design life, and is based on failures chargeable to Maxtor. Determination of the AFR takes into account: a.) in-warranty field failure returns less quality acceptance-related failures and b.) an AFR equaling an exponentially weighted moving and average monthly failure rate multiplied by 12.

cisaB,4.415dohteM,E018-DTS-LIMreP

.eliforpDSPsixalacitreV,noitatropsnart

MTBF

> 500,000 hours Maxtor does not differentiate between various usage profiles (e.g.,

power-on hours, power saving modes, non-operating periods or operating temperatures within the published specification.)

Quality Acceptance Rate

99.85% (< 1,500 DPPM) The quality acceptance rate indicates the percentage of Maxtor products successfully installed by our customers, and/or the number of defective parts per million (DPPM) encountered during the entire installation process.

Start/Stop Cycles

50,000 (minimum) This indicates the minimum cycles for reliable start/stop function at a

≥ 60% confidence level.

Data Reliability

< 1 per 10

bits read Data errors (non-recoverable). Average data error rate allowed with all

error recovery features activated.

< 1 per 10

seeks Seek errors

Component Design Life

5 years (minimum) Component design life is defined as a.) the time period before

identified wear-out mechanisms impact the failure rate, or b.) the time period up to the wear-out point at which useful component life expires.

3 – 4

PRODUCT SPECIFICATIONS

EMC/EMI

Radiated Electromagnetic Field Emissions - EMC Compliance

The hard disk drive mechanism is designed as a subassembly for installation into a suitable enclosure and is therefore not subject to Subpart J of Part 15 of FCC Rules (47CFR15) or the Canadian Department of Communications Radio Interference Regulations. Although not required, the disk mechanism has been tested within a suitable end-use product and found to comply with Class B limits of the FCC Rules and Regulations of the Canadian Department of Communications.

The CE Marking indicates conformity with the European Union Low Voltage Directive (73/23/EEC) when the disk mechanism is installed in a typical personal computer. Maxtor recommends that testing and analysis for EMC compliance be performed with the disk mechanism installed within the user's end-use application.

Canadian Emissions Statement

This digital apparatus does not exceed the Class B limits for radio noise emissions from digital apparatus as set out in the radio interference regulations of the Canadian department of communications.

Le present appareil numerique n'emet pas de bruit radioelectriques depassant les limites applicables aux appareils numeriques de Class B prescrites dans le reglement sur le brouillage radioelectrique edicte par le ministere des communications du Canada.

Radiated Magnetic Field Emissions

Minimum of VDE Class B and MIL-STD-461/462, Method RE01 (stand-alone test configuration).

Radiated Electromagnetic Field Immunity

IEC 801-3, Class 2 compliance.

Radiated Magnetic Field Immunity

Per MIL-STD-461/462, Method RD01(15 Hz to 100 kHz, stand-alone test configuration).

Standard Test Methods

Traditional hard drive specifications are open to incorrect interpretation, but MIL-STD test methods accurately measure how products perform in real-world conditions. These methods have gained worldwide acceptance since they reflect actual environments, have well-defined test requirements, are easily understood and provide repeatable results. They objectively demonstrate to our customers the reliable, durable design of Maxtor hard drives. Each MIL-STD specification provides the basic method and condition information needed for reference by a knowledgeable Test and Qualification Engineer.

Acoustic specifications such as sound pressure are misleading because the test methods used are not controlled by recognizable standards. The sound pressure measurement itself is the least meaningful indicator of noise emissions as it relates to the human ear. The specification of sound power, loudness and sharpness are considered the most accurate acoustic measurement methodologies recognized by the leading acoustic measurement experts. ISO 7779, sound power, ISO 532B, loudness and sharpness (proposed ANSI standard by Eberhard Zwicker) are repeatable test methods providing results reproducible in any properly equipped acoustic lab.

Safety Regulatory Compliance

All Maxtor DiamondMax™ 2160 drives comply with relevant product safety standards such as CE, CUL, TUV and UL rules and regulations. As delivered, DiamondMax 2160 hard disk drives are designed for system integration before they are used.

3 – 5

SECTION 4

Handling and Installation

Pre-formatted Drive

This Maxtor hard drive has been formatted at the factory. Do not use a low-level formatting program.

Important Notice

There are a number of system BIOS’s currently in use which do not support hard drives with more than 4095 cylinders (2.1 gigabytes). This section contains information describing the conditions which may identify this limitation. In order to obtain the full capacity of your Maxtor drive, you will need to follow the recommended installation instructions.

Hard Drive Handling Precautions

◆ During handling, board assembly (PCBA).

◆ Hard drives are sensitive to electrostatic discharge (ESD) damage. Use proper ESD practices by grounding yourself and the computer system the hard drive will be installed in.

NEVER

drop, jar, or bump a drive. Handle the drive by its sides and avoid touching the printed circuit

INSTALLATION

◆ Allow the hard drive to reach room temperature

◆

NEVER

switch DC power onto the drive by plugging an electrically live DC source cable into the drive's connector.

NEVER

connect a live connector to the hard drive's IDE interface connector.

BEFORE

installing it in your computer system.

Electro-Static Discharge (ESD)

To avoid some of the problems associated with ESD, Maxtor advises that anyone handling a disk drive use a wrist strap with an attached wire connected to an earth ground. Failure to observe these precautions voids the product warranty.

Manufacturers frequently experience “unsolved” component/hardware malfunctions often caused by ESD. To reduce the incidence of ESD-related problems, Maxtor recommends that any electronics manufacturing plans include a comprehensive ESD program, the basic elements and functions of which are outlined here:

ESD Program Element ESD Program Function Management Institute and maintain Chief coordinator Organize and enforce Multi-department committee Evaluate and improve Employee training Educate and inform

ESD program supplies typically include: wrist- and foot-worn grounding straps; counter-top and floor antistatic matting; wrist strap testers; ESD video and training materials. Sources for such supplies include:

Static Control Systems – 3M Charleswater 225-4S, 3M Center 93 Border St. St. Paul, MN 55144 West Newton, MA 02165-9990

Maxtor also offers a complete video training package, “Care and Handling of Maxtor Disk Drives.” Contact your Maxtor representative for details.

4 – 1

INSTALLATION

Unpacking and Inspection

Retain any packing material for reuse. Inspect the shipping container for evidence of damage in transit. Notify the carrier immediately in case of damage to the shipping container.

As they are removed, inspect drives for evidence of shipping damage or loose hardware. If a drive is damaged (and no container damage is evident), notify Maxtor immediately for drive disposition.

4 – 2

Figure 4 - 1

Multi-pack Shipping Container

INSTALLATION

Figure 4 - 2

Single Pack Shipping Container (Option A)

Single Pack Shipping Container (Option B)

Figure 4 - 3

Repacking

If a Maxtor drive requires return, repack it using Maxtor packing materials, including the antistatic bag.

Physical Installation

Recommended Mounting Configuration

The DiamondMax™ 2160 drive design allows greater shock tolerance than that afforded by larger, heavier drives. The drive may be mounted in any attitude using four size 6-32 screws with 1/8-inch maximum penetration and a maximum torque of 5-inch pounds. See Figure 3-1 for mounting dimensions. Allow adequate ventilation to the drive to ensure reliable operation.

4 – 3

INSTALLATION

Drive Jumper Settings

Figure 4-4 shows the valid jumper settings for the Maxtor hard drive.

Master Device Slave Device

J50 J48 J46 J44 J42 J50 J48 J46 J44 J42

EIDE Interface Connector J1

J50 – Master/Slave

J48 – Cable Select

J46 – 4092 Cylinder Limitation

J44 – Factory Reserved J42 – Factory Reserved

Power Connector J2

Figure 4 - 4

Master/Slave Jumper Detail

Mounting Drive in System

Turn the computer OFF, disconnect the power cord and remove the cover. Refer to your computer user’s manual for additional information.

Installing 5.25-inch Mounting Brackets

Mounting brackets are only needed when the drive will be installed in a 5.25-inch drive bay. This step is not necessary when installing the drive in a 3.5-inch bay. See Figure 4-5 below.

Mounting Rails

Mounting rails are attached to the mounting bracket for systems requiring this feature. See Figure 4-5 below.

4 – 4

Figure 4 - 5

5.25-inch Mounting Brackets/Slider Rails

INSTALLATION

Note: The following figures are examples of typical computer systems and mounting placements. The computer system the Maxtor hard drive is being installed in may have implemented a different mounting and placement methodology.

Mounting Drive in 5.25-inch Bay

If the Maxtor hard drive will be mounted in a 5.25-inch bay, install it as shown in Figure 4-6 below.

Figure 4 - 6

5.25-inch Installation

Mounting Drive in 3.5-inch Bay

If the Maxtor hard drive will be mounted in a 3.5-inch bay, install it as shown in Figure 4-7 below.

Figure 4 - 7

3.5-inch Installation

4 – 5

INSTALLATION

Attaching IDE Interface and Power Cables

In order for your computer to recognize that the Maxtor hard drive is in the system, the IDE interface and power cables must be connected to the hard drive, the mother board or the IDE hard drive interface card.

1 Attach an available IDE interface connector to J1 (see Figure 4-8 below) on the Maxtor hard drive.

This connector is keyed and will only fit in one orientation. Do not force the connector. The striped or colored edge of the IDE interface cable indicates pin 1. Pin 1 on the IDE interface cable should

match pin 1 on the drive connector. On the Maxtor hard drive, pin 1 is closest to the power connector.

2 Connect an available power connector to J2 (see Figure 4-8 below) on the Maxtor hard drive.

This connector is keyed and will only fit in one orientation. Do not force the connector.

Striped/colored edge is pin 1

Figure 4 - 8

IDE Interface and Power Cabling Detail

IMPORTANT: After attaching the IDE interface cable and the power cable to the Maxtor hard drive, verify

that all other cables connected to other devices, the mother board or interface cards are correctly seated.

4 – 6

Attaching System Cables

Attach the 40-pin IDE interface cable from the Maxtor hard drive to the IDE connector on the IDE interface card.

INSTALLATION

Figure 4 - 9

System Interface Card Cabling

Attach the 40-pin IDE interface cable from the Maxtor hard drive to the IDE connector on the mother board.

Figure 4 - 10

System Mother board Cabling

4 – 7

INSTALLATION

System Setup

The following procedures are designed for systems using the DOS 5.0 (or higher) or Windows 95 operating systems. For other operating systems (e.g., OS2 operating system user’s manual for the BIOS setting and other installation requirements

Setting the BIOS (CMOS)

In order for the computer system to recognize the new Maxtor hard drive, it is necessary to set the system BIOS with the correct information about the hard drive. To do this, run the system SETUP (BIOS) program.

The SETUP (BIOS) program identifies the system configuration information (e.g., floppy disk drives, hard disk drives, video, etc.) used by the computer during system boot. This includes the information about what kind and how many hard drives are attached to the system.

If you are unsure of how to access the system BIOS and/or program the BIOS settings, refer to the computers user’s manual for detailed instructions.

WARNING: When entering the settings for the new Maxtor hard drive, be careful not to change any of the other BIOS settings, or other parts of the system may not work correctly.

Note: Most of the systems with newer BIOS’ (typically with a date of July 1994 or newer), support large

capacity hard drives. It is necessary to determine if the system provides support for large capacity hard drives before entering the settings, as this affects how to correctly set the BIOS parameters for the Maxtor hard drive.

, UNIX®, LINUX and Novell NetWare®), refer to the

Set the BIOS (CMOS) parameters as follows:

IMPORTANT: Major BIOS manufacturers like AMI, Award and Phoenix provide their core BIOS programs to system board manufacturers and OEM's who have the capability of making modifications to some of the descriptions and definitions to meet their unique requirements. These changes include, but are not limited to, how to access the BIOS, the apeearance of the information on the screens and the location of parameters within the BIOS. Refer to the system or BIOS manufacturers documentation for the correct procedure to enter the BIOS setup program for your system.

A Turn the system ON. During the system start-up sequence, run the SETUP (BIOS) program or similar

commands to access the system BIOS. Note: Newer systems will typically display a message (e.g., press DEL to Enter Setup) identifying how to

access the SETUP (BIOS) program.

B Once the SETUP (BIOS) program is active, do one of the following to set the hard drive BIOS parameters.

1 If the SETUP program provides an “AUTO DETECT” capability, use this feature to detect the

Maxtor hard drive. Note: After the SETUP program has detected the hard drive, verify that the Logical

Block Addressing (LBA) mode is enabled for this drive.

If the SETUP program does not provide an “AUTO DETECT” capability, set the drive parameters as defined in step 2).

Comment: When LBA is enabled, some BIOS programs will change the values of the cylinders and heads by dividing the cylinders by 2, 4, 8 or 16 and multiplying the heads by the same value. This does not change the capacity of the hard drive.

4 – 8

2 If the SETUP program does not provide an “AUTO DETECT” capability, the drive parameters

must be set using the User Definable Type (UDT). Select the appropriate UDT for the Maxtor hard drive and set the cylinder, head and sector values for the model being installed from the table below.

INSTALLATION

Drive Paramters

LEDOMLYCDHTPSenoZLmocPWYTICAPAC

8D00488872,616136)*()*(BM004,8

6D08468593,315136)*()*(BM084,6

4D02348039,85136)*()*(BM023,4

3D04238796,65136)*()*(BM042,3

2D06128564,45136)*()*(BM061,2

(*) The fields LZone (Landing Zone) and WPcom (Write Pre-comp) are not used by the Maxtor hard drive and the values may be either 0 or the values set by the BIOS. All capacities listed in the parameters table are based on 10

or one million bytes.

Only the values for cylinders, heads and sectors listed in the table must be entered. All other values may be zero (0). Set the LBA mode to enabled for this drive. If the SETUP program does not provide the UDT, set the BIOS to the drive type with the largest capacity of those listed in the BIOS.

C After the drive parameters are entered, follow the SETUP program procedures to save the settings and exit

the SETUP program. After changing BIOS settings, saving the values and exiting, the SETUP program should force the system to re-boot.

Note: Each BIOS manufacturer uses different methods of identifying the UDT. Newer BIOS’ from all

manufacturers will usually include an entry called “User” or “User 1.” Older BIOS’ vary in the method used to identify the UDT: AMI = Type 47, Award = Type 47 and Phoenix = Type 48.

System Hangs During Boot

If the system hangs after installing the Maxtor hard drive, either before or after setting the system BIOS, the system many have a BIOS with a cylinder limitation. This may occur for hard drives with capacities larger than

2.1 GB. If this happens, do the following:

1 Turn the system OFF.

Master Device Slave Device

J50 J48 J46 J44 J42 J50 J48 J46 J44 J42

EIDE Interface Connector J1

J50 – Master/Slave

J48 – Cable Select

J46 – 4092 Cylinder Limitation

J44 – Factory Reserved J42 – Factory Reserved

Power Connector J2

4 – 9

INSTALLATION

2 Install the cylinder reduction jumper (J46) on the drive using the spare jumper shipped across pins J46 and

J48; or, if the drive is installed as a Slave, store the spare jumper across J42 and J44.

3 If the BIOS was set to AUTO DETECT, boot the system with the MaxBlast installation software diskette

to complete the hard drive installation. If other BIOS settings were used, access the system BIOS SETUP program and set the BIOS parameters to a User Definable Type with 4,092 cylinders, 16 heads and 63 sectors per track for the Maxtor hard drive. Then boot the system with the MaxBlast installation software diskette to complete the hard drive installation.

IMPORTANT: When jumper J46 is installed, the Maxtor hard drive must be prepared using the

Hard Drive Preparation

To complete the Maxtor hard drive installation, the drive must be partitioned and formatted. 1 Boot the system to the bootable MaxBlast software installation diskette received with the hard drive and

proceed to step 2.

2 The MaxBlast installation software will load and the first screen of the program will display. Complete the

information in the System Configuration Information table and follow the on-screen prompts to complete the hard drive installation.To complete the installation of the Maxtor hard drive, the drive must be partitioned and formatted.

MaxBlast installation software.

System/Drive Information

The first time MaxBlast installation software is run, it will display information in a format similar to the System Configuration Information table. Subsequent executions start at the main menu and allow the user to optionally display this information.

The information in the System Configuration table must be completed for your records. This information will be requested by the Maxtor Technical Assistance representative in the event that you call for assistance.

The Maxtor hard drive model number and serial number are also located on the top cover label of the hard drive. System information should be available in the computer users’s manual or in the documentation for the different devices attached to the system.

NOITAMROFNIEVIRD/METSYS

evirDksiDdraHrotxaM

rebmuNledoMrebmuNlaireS

metsySretupmoC

ledoMrerutcafunaM

)zHM09,.e.i(deepS)muitneP,.e.i(rossecorP

draCecafretnI

ledoMrerutcafunaM

)puteS/SOMC(SOIB

noisreVrerutcafunaMetaD

evirDksiDdraHrehtO

ledoMrerutcafunaM

TPSsdaeHsrednilyC:gnitteSSOIB

seciveDEDIrehtO

)MOR-DC,.e.i(epyT

ledoMrerutcafunaM

4 – 10

Once the information in this table is copied from the screen, continue with the installation or exit the MaxBlast installation software as shown on the screen. EZMAX is a menu-driven program with on-line help to guide you through the installation process.

AT INTERFACE DESCRIPTION

SECTION 5

AT Interface Description

Interface Connector

All DiamondMax™ 2160 AT drives have a 40-pin ATA interface connector mounted on the PCBA. The drive may connect directly to the host; or it can also accommodate a cable connection (max cable length: 18 inches).

Figure 5-1

Data Connector

Pin Description Summary

NIPLANGISNIPLANGIS

10-teseR20dnuorG

307DD408DD

506DD609DD

705DD8001DD

904DD0111DD

113DD2121DD

312DD4131DD

511DD6141DD

710DD8151DD

91dnuorG02)nipyek(

12QRAMD22dnuorG

32POTS:-WOID42dnuorG

52EBORTSH:YDRAMDH:-ROID62dnuorG

72EBORTSD:YDRAMDD:YDROI82LESC

92-KCAMD03dnuorG

13QRTNI23

331AD43-GAIDP

530AD632AD

73-0SC83-1SC

93-PSAD04dnuorG

61SCOI

etelosbO

5 – 1

AT INTERFACE DESCRIPTION

Pin Description Table

EMANNIPNIPO/IEMANLANGISNOITPIRCSEDLANGIS

-TESER10I teseRtsoH .retfaevitcanidnapurewopgnirudevitcA.metsystsohehtmorflangisteseR

0DD71O/IsuBataDtsoH retsigerrofdesustib8rewoL.evirddnatsohneewtebsubatadlanoitcerid-ibtib61

1DD51O/I

2DD31O/I

3DD11O/I

4DD90O/I

5DD70O/I

6DD50O/I

7DD30O/I

8DD40O/I

9DD60O/I

01DD80O/I

11DD01O/I

21DD21O/I

31DD41O/I

41DD61O/I

51DD81O/I

QRAMD12O tseuqeRAMD eht,langissihtgnitressayB.srefsnartAMDrofKCAMDhtiwdesusilangissihT

-WOID

32I etirWO/ItsoH ehtnoretsigeraotsubatadtsohehtmorfatadskcolcebortsetirWfoegdegnisiR

POTS

-ROID

52I daeRO/ItsoH .subatadtsohehtotnoevirdehtnoretsigeramorfatadselbaneebortsdaeR

YDRAMDH

EBORTSH

YDROI

72O ydaeRlennahCO/I .selcycO/ItsohotnisetatstiawtresniotevirdehtybwolnevirdebyamlangissihT

YDRAMDD

EBORTSD

LESC82tceleSelbaC metsystsohnognilbaclaicepsseriuqeR.elbacaivnoitcelesevalS/retsaMrofdesU

-KCAMD92I egdelwonkcAAMD eht,langissihtgnitressayB.srefsnartAMDrofQRAMDhtiwdesusilangissihT

QRTNI13O tpurretnItsoH

61SCOI23O/Itib61eciveDetelosbO

-GAIDP43O/IcitsongaiDdessaP .edomretsaMninehwevirdottupnI;edomevalSninehwevirdybtuptuO

0AD53I suBsserddAtsoH .evirdehtniretsigeratcelesottsohehtmorfsserddayranibtib3

1AD33I

2AD63I

-0SC73I 0tceleSpihCtsoH .evirdehtnisretsigerkcolBdnammoCehtsseccaotdesutsohehtmorftcelespihC

-1SC83I 1tceleSpihCtsoH sihT.evirdehtnisretsigerlortnoCehtsseccaotdesutsohehtmorftcelespihC

-PSAD93O/I1evirD/evitcAevirD

DNG20A/NdnuorG.dnuorglangiS

YEK02A/NyeK.rotcennocecafretniehtgniyekrofdesuniP

tseuqeR

tneserP

.evird

.tneserpsi1ecived

.srefsnartatadrofdesustib61llA.srefsnartetybCCEdna

.tsohehtmorfdnaotderefsnartebotydaersiatadtahtsetacidnievird

.stsrubniatadAMDartlUgnirudydaerAMD

.stsrubtuoatadAMDartlUgnirudebortsataD

.stsrubtuoatadAMDartlUgnirudydaerAMD

.stsrubniatadAMDartlUgnirudebortsataD

.repmujtceleSelbaCfonoitallatsnidna

.elbaliavasiatadtahtgnitacidnisiroatadfotpiecerehtgnigdelwonkcasitsoh

.tsohehtmorfnoitnettaseriuqerevirdehtnehwdetressatsohehtottpurretnI

.xeh7F1-0F1sesserddaO/IfoedocedasilangissihT

.xeh7F3-6F3sesserddaO/Ifoedocedasilangis

tahtro,evitcasievirdatahtsetacidnihcihwtuptuorotcellocnepo,dexelpitlum-emiT

5 – 2

AT INTERFACE DESCRIPTION

PIO Timing

SRETEMARAPGNIMIT0EDOM1EDOM2EDOM3EDOM4EDOM

0temiTelcyC

1tputes-WOID/-ROIDotdilavsserddA

2ttib-61-WOID/-ROID

i2temityrevocer-WOID/-ROID

3tputesatad-WOID

4tdlohatad-WOID

5tputesatad-ROID

6tdlohatad-WOID

Z6tetatsirtatad-ROID

9tdlohdilavsserddaot-WOID/-ROID

dRtevitcaYDROIotdilaVataDdaeR

AtemiTputeSYDROIsn53sn53sn53sn53sn53

BthtdiWesluPYDROI

)nim(

)xam(

nim(

)nim(

)xam(

sn006sn383sn042sn081sn021

)sn07sn05sn03sn03sn52

sn561sn521sn001sn08sn07

sn07sn52

sn06sn54sn03sn03sn02

sn03sn02sn51sn01sn01

sn05sn53sn02sn02sn02

sn5sn5sn5sn5sn5

sn03sn03sn03sn03sn03

sn02sn51sn01sn01sn01

00000

sn0521sn0521sn0521sn0521sn0521

Figure 5 - 2

PIO Data Transfer To/From Device

5 – 3

AT INTERFACE DESCRIPTION

DMA Timing

0temiTelcyC

CtyaledQRAMDotKCAMD

Dt-WOID/-ROID

Etsseccaatad-ROID

Ftdlohatad-ROID

Gtputesatad-WOID/-ROID

Htdlohatad-WOID

Itputes-WOID/-ROIDotKCAMD

JtdlohKCAMDot-WOID/-ROID

rKthtdiweslupdetagen-ROID

wKthtdiweslupdetagen-WOID

rLtyaledQRAMDot-ROID

wLtyaledQRAMDot-WOID

Ztetatsirtot-KCAMD

SRETEMARAPGNIMIT0EDOM1EDOM2EDOM

)nim(

)xam(

sn084sn051sn021

sn512sn08sn07

sn051sn06

sn5sn5sn5

sn001sn03sn02

sn02sn51sn01

000

sn02sn5sn5

sn05sn05sn52

sn512sn05sn52

sn021sn04sn53

sn04sn04sn53

sn02sn52sn52

5 – 4

Figure 5 - 3

Multi-word DMA Data Transfer

Ultra DMA Timing

SRETEMARAPGNIMIT )sdnocesonannisemitlla(

CYC

SVD

HVD

ILM

HAZ

DAZ

VNE

SFR

ZYDROI

YDROIZ

KCA

emiTelcyC)egdeEBORTSotegdeEBORTSmorf(4115755

emitelcycowTroegdegnisirtxenotegdegnisirmorf(

emitputesataD)tneipicerta(5101707

emitdlohataD)tneipicerta( 555

EBORTStsriF)EBORTStsrifdnesotecivedrofemit(003200020071

)tnegarehtoehtyb

emitepolevnEehtnihtiwerasnoitisnartlangislortnoclla(

-KCAMD

gnippotssirednes

rednestaemitputesdilavataDgniebsubatadmorfemit(

)egdeEBORTSlitnudilav

rednestaemitdlohdilavataDegdeEBORTSmorfemit(

)dilavniogyamatadlitnu

emitkcolretnidetimiLybnoitcananeewtebdewollaemit(

muminimhtiwemitkcolretnI020202

emitkcolretnidetimilnU 000

)etatsdesaelermorf(

YDRAMDotEBORTSehterusneotemitesnopser(

emitEBORTS-lanif-ot-ydaeRyamsegdeEBORTSeromon(

emitesuap-ot-ydaeRemussayamtneipiceralitnuemit(

0EDOM1EDOM2EDOM

NIMXAMNIMXAMNIMXAM

EBORTSfoegdegnillaftxenotegdegnillafmorf)

esaelerotstuptuorofdewollaemitmumixaM010101

)emithcumsihtybepolevneKCAMD

)noitagen-YDRAMDgniviecerretfagnolsihttneseb

desaelerebotYDROIgniwollaerofebemitpu-lluP020202

YDROIgnivirderofebtiawllahsecivedemitmuminiM 000

fonoitagendnanoitressaerofebsemitdlohdnaputeS

ehtnehwnoitressaPOTSotegdeEBORTSmorfemiT

532651711

0784435

66602

noitcagniwollofehtdna,ecivedrotsohrehtie,tnegaeno

005100510 051

020202

nogninrutsrevirdtuptuorofderiuqeremityaledmuminiM

000

020702070207

)gnisuapsitneipicerehtnehwesacesuapsuonorhcnys

)-YDRAMDfonoitagenretfadesuapsahrednesehttaht

050302

570605

061521001

020202

050505

AT INTERFACE DESCRIPTION

DMARQ (device)

DMACK-

(host)

STOP (host)

HDMARDY-

(host)

DSTROBE

(device)

DD(15:0)

DA0, DA1, DA2,

CS0-, CS1-

ACK

ZIORDY

ENV

ZAD

VDS

Figure 5 - 4

Initiating an Ultra DMA Data In Burst

DVH

5 – 5

AT INTERFACE DESCRIPTION

DSTROBE

at device

DD(15:0) at device

DSTROBE

at host

DVH

CYC

DVS

2CYC

DVH

CYC

2CYC

DVS

DVH

DD(15:0)

at host

DMARQ (device)

DMACK-

HDMARDY-

DSTROBE

DD(15:0)

(host) STOP

(host)

(device)

Figure 5 - 5

Sustained Ultra DMA Data In Burst

RFS

5 – 6

Figure 5 - 6

Host Pausing an Ultra DMA Data In Burst

DMARQ

(

)

(

)

(

)

device

DMACK-

(host)

STOP

(host)

HDMARDY-

(host)

DSTROBE

device

DD(15:0)

DA0, DA1, DA2,

CS0-, CS1-

AT INTERFACE DESCRIPTION

MLI

ACK

DVH

IORDYZ

ZAH

DVS

CRC

ACK

DMARQ

(device)

DMACK-

(host)

STOP

host

HDMARDY-

(host)

DSTROBE

(device)

DD(15:0)

DA0, DA1, DA2,

CS0-, CS1-

Figure 5 - 7

Device Terminating an Ultra DMA Data In Burst

RFS

ZAH

MLI

DVS

CRC

ACK

IORDYZ

DVH

ACK

Figure 5 - 8

Host Terminating an Ultra DMA Data In Burst

5 – 7

AT INTERFACE DESCRIPTION

(

)

DMARQ

(device)

DMACK-

host

STOP

(host)

DDMARDY-

(device)

HSTROBE

(host)

DD(15:0)

(host)

DA0, DA1, DA2,

CS0-, CS1-

HSTROBE

at host

DD(15:0)

at host

ACK

ZIORDY

ACK

ENV

Figure 5 - 9

Initiating an Ultra DMA Data Out Burst

2CYC

CYC

DVH

DVS

DVH

CYC

DVS

DVH

2CYC

DVH

HSTROBE

at device

DD(15:0) at device

Figure 5 - 10

Sustained Ultra DMA Data Out Burst

5 – 8

DMARQ (device)

DMACK-

(host)

STOP (host)

DDMARDY-

(device)

HSTROBE

(host)

DD(15:0)

(host)

RFS

Figure 5 - 11

Device Pausing an Ultra DMA Data Out Burst

AT INTERFACE DESCRIPTION

DMARQ (device)

DMACK-

(host)

STOP (host)

DDMARDY-

(device)

HSTROBE

(host)

DD(15:0)

(host)

DA0, DA1, DA2,

CS0-, CS1-

MLI

DVS

ACK

IORDYZ

DVH

CRC

ACK

Figure 5 - 12

Host Terminating an Ultra DMA Data Out Burst

5 – 9

AT INTERFACE DESCRIPTION

(

)

(

)

DMARQ

(device)

DMACK-

(host)

STOP

host

DDMARDY-

device

HSTROBE

(host)

DD(15:0)

(host)

DA0, DA1, DA2,

CS1-

CS0-

MLI

DVS

RFS

CRC

Figure 5 - 13

Device Terminating an Ultra DMA Data Out Burst

ACK

IORDYZ

ACK

DVH

ACK

5 – 10

HOST SOFTWARE INTERFACE

SECTION 6

Host Software Interface

The host communicates with the drive through a set of controller registers accessed via the host’s I/O ports. These registers divide into two groups: the Task File, used for passing commands and command parameters and the Control/Diagnostic registers.

Task File Registers

The Task File consists of eight registers used to control fixed disk operations. The host accesses each register by the I/O port address shown in this Task File register map:

TROPO/IDAERETIRW

h0F1retsigeRataDretsigeRataD

h1F1retsigeRrorrEretsigeRserutaeF

h2F1tnuoCrotceStnuoCrotceS

h3F1rebmuNrotceSrebmuNrotceS

h4F1woLrednilyCwoLrednilyC

h5F1hgiHrednilyChgiHrednilyC

h6F1)HDS(daeH/evirD)HDS(daeH/evirD

h7F1retsigeRsutatSretsigeRdnammoC

Data Register

Provides access to the drive’s sector buffer for read and write operations. With the exception of ECC byte transfers (which, during Read long and Write long commands, are 8 bits wide), data transfers through the Data register are all 16 bits wide.

Error Register

A read-only register containing specific information regarding the previous command. Data interpretation differs depending on whether the controller is in operational or diagnostic mode. A power up, reset, software reset, or receipt of a diagnostic command sets the controller into diagnostic mode. This mode invalidates contents of the Status register. The contents of the Error register reflect a completion code.

Issuing any command (apart from a Diagnostic command) places the controller into operational mode. In operational mode, the Error register is valid only when the Error bit in the Status register is set. The bit definitions for operational mode follow:

765432 10

0CCE0 FNDI0TRBA0KTFNMA

ecafretnI

CRC

Interface CRC Data ECC Error Firmware Problem ID Not Found Aborted Command Track 0 Error Address Mark Not Found

ataD

rorrECCE

– An interface CRC error occurred during an Ultra DMA transfer.

– An non-correctable ECC error occurred during a Read Sector command.

– Indicates a firmware problem was detected, (e.g., invalid interrupt, divide overflow).

– Either a matching ID field not found, or a CRC error occurred.

– Invalid commands, write fault, no seek complete, or drive not ready.

– Track 0 was not found during execution of a Restore command.

toN

desU

– The Address Mark could not be found after an ID match.

dnuoFtoN

toN

desU

detrobA

dnammoC

0kcarT

rorrE

sserddA

toNkraM

dnuoF

Features Register

Enables or disables features through the Set Features command.

6 – 1

HOST SOFTWARE INTERFACE

Sector Count Register

Holds the number of sectors to be sent during a Read or Write command, and the number of sectors per track during a Format command. A value of zero in this register implies a transfer of 256 sectors. A multisector operation decrements the Sector Count register. If an error occurs during such an operation, this register contains the remaining number of sectors to be transferred.

Sector Number Register

Holds the starting sector number for any disk operation. The register is updated as each sector is processed in a multi-sector operation.

Cylinder Number Registers

Two 8-bit Cylinder Number registers (Low and High) specify the starting cylinder for disk operation.

Device/Head Register

Used to specify the drive and head number to be operated on during any disk operations. Within the context of a Set Parameters command, this register specifies the maximum number of heads on the drive. Bit definitions follow:

765432 10

1ABL1VRD3SH2SH1SH0SH

edoM

evirD

tceleStceleS

daeH

tceleS

daeH

tceleS

daeH

tceleS

Select LBA Mode

the Task File register contents are defined as follows for the Read/Write and translate command:

Drive Select Head Select

– Enabling this bit for commands not supported by LBA mode will abort the selected command. When set,

STNETNOCSTIBABL

rebmuNrotceS7-0

woLrednilyC51-8

hgiHrednilyC32-61

daeH/evirD72-42

– Set to 0 to select the master drive; set to 1 to select the slave drive. – Specifies the binary coded address of the head to be selected.

Status Register

Contains results of the last command executed, and the drive’s status. The other seven Task File registers may be read only when bit 7 (BUSY) of the Status register is low. Reading any of the Task File registers when BUSY is high returns the value of the Status register. Reading the Status register also clears any interrupt request to the host. Bit definitions follow:

7654 3210

YSUBYDRDFDCSDQRD0 0 RRE

rellortnoC

ysuB

Controller Busy

execution. After a command, this bit resets.

Device Ready Device Fault Device Seek Complete Data Request Error

– The Error bit sets when the previous command has completed with a non-recoverable error.

eciveD

ydaeR

– Goes active when a command is written to the Command register, indicating controller task

– Indicates that the drive is ready for commands. If drive ready is not present, all commands abort.

– Indicates the drive’s detection of a write fault condition, causing all commands to abort.

– Indicates that the drive’s sector buffer is ready for data transfer.

eciveD

tluaF

– Signifies a seek completion, and that the drive is on track.

keeSeciveD

etelpmoC

ataD

tseuqeR

rorrE

6 – 2

HOST SOFTWARE INTERFACE

Command Register

Contains code for the command to be performed. Additional command information should be written to the task file before the Command register is loaded. When this register is written, the BUSY bit in the Status register sets, and interrupt request to the host clears; invalid commands abort. (Detailed information on interface commands is given in Section 7.) Hex values for valid command formats follow:

Read Commands

Read Sector(s) 20h Normal reads; retries enabled

Read Verify Sector(s) 40h Retries enabled

Read Sector Buffer E4h Read Multiple C4h Read DMA C8h

Write Commands

Write Sector(s) 30h Normal writes; retries enabled

Write Verify Sector(s) 3Ch Write Sector Buffer E8h Write Multiple C5h Write DMA CAh

21h Normal reads; retries disabled 22h Read Long; retries enabled 23h Read Long; retries disabled

41h Retries disabled

C9h No retries

31h Normal writes; retries disabled 32h Write Long; retries enabled 33h Write Long; retries disabled

CBh No retries

Mode Set/Check Commands

Set Features EFh Set Multiple Mode C6h

Power Mode Commands

Standby Immediate 94/E0h Stops drive spindle; do not change time-out value Idle Immediate 95/E1h Starts spindle; do not change time-out value Standby 96/E2h Stops spindle; change time-out value Idle 97/E3h Starts spindle; change time-out value Check Power Mode 98/E5h Set Sleep Mode 99/E6h

Initialization Commands

Identify Drive ECh Initialize Drive Parameters 91h Re-calibrate 1xh

Seek, Format, and Diagnostic Commands

Seek 7xh Format Track 50h Execute Drive Diagnostic 90h

S.M.A.R.T. Commands

Execute S.M.A.R.T. B0h

6 – 3

HOST SOFTWARE INTERFACE

Summary

etarbilaceR 0001xxxx NNNN D

)s(rotceSdaeR 001000Lx NYYY Y

AMDdaeR 1100 100x NYYY Y

)s(rotceSetirW 00 1100Lx NYYY Y

AMDetirW 1100101x NYYY Y

)s(rotceSyfireVetirW 00 111100 NYYY Y

)s(rotceSyfireVdaeR 0100000x NYYY Y

kcarTtamroF 010 10000 NNNY Y

keeS 0111xxxx NNYY Y

citsongaiDetucexE 100 10000 NNNN D

sretemaraPezilaitinI 100 10001 NYNN Y

reffuBrotceSdaeR 11 10 0 10 0 NNNN D

reffuBrotceSetirW 11 10 1 0 0 0 NNNN D

evirDyfitnedI 1110 1 10 0 NNNN D

serutaeFteS 11101111 YNNN D

elpitluMdaeR 11000100 NYYY Y

elpitluMetirW 11000101 NYYY Y

edoMelpitluMteS 11000 110 NYNN D

DESUSRETEMARAPEDOCDNAMMOCEMANDNAMMOC

7b6b5b4b3b2b1b0bFCSNSC HDS

EULAVREMITDOIREPTUO-EMIT

0delbasidtuo-emiT

042-1sdnoces)5*eulav(

152-142setunim)03*)042-eulav((

252setunim12

352sruoh01=doirepeuqinurodneV

452devreseR

552sdnoces51,setunim12

6 – 4

HOST SOFTWARE INTERFACE

Control Diagnostic Registers

These I/O port addresses reference three Control/Diagnostic registers:

TROPO/IDAERETIRW

h6F3sutatSetanretlAlortnoCksiDdexiF

h7F3tupnIlatigiDdesutoN

Alternate Status Register

Contains the same information as the Status register in the Task File. However, this register may be read at any time without clearing a pending interrupt.

Device Control Register

Contains the software Reset and Enable bit to enable interrupt requests to the host. Bit definitions follow:

765432 10

00000 TSRSNEI0

teseRelbanEQRI

Reset – Setting the software Reset bit holds the drive in the reset state. Clearing the bit re-enables the drive. The software Reset bit must be held active for a minimum of 5 µsec.

IRQ Enable

to 1, IRQ14 is tri-stated, and interrupts to the host are disabled. Any pending interrupt occurs when the bit is set to 0. The default state of this bit after power up is 0 (interrupt enabled).

– Setting the Interrupt Request Enable to 0 enables the IRQ 14 signal to the host. When this bit is set

Digital Input Register

Contains information about the state of the drive. Bit definitions follow:

765432 10

xGW-3SH-2SH-1SH-0SH-1SD-0SD

devreseR

etaG

daeH

3tceleS

daeH

2tceleS

daeH

1tceleS

daeH

0tceleS

evirD

1tceleS

evirD

0tceleS

Bit 7 of the host data bus is not driven when this register is read.

-Write Gate

-Head Select 3 through -Head Select 0

-Drive Select 1

-Drive Select 0

– Reflects the state of the active low write gate signal on the drive.

– Represents the ones complement of the currently selected head number. – Is 0 if drive 1 selected; 1 otherwise. – Is 0 if drive 0 selected; 1 otherwise.

6 – 5

HOST SOFTWARE INTERFACE

Reset and Interrupt Handling

Reset Handling

One of three different conditions may cause a reset: power on, hardware reset or software reset. All three cause the interface processor to initialize itself and the Task File registers of the interface. A reset also causes a set of the Busy bit in the Status register. The Busy bit does not clear until the reset clears and the drive completes initialization. Completion of a reset operation does not generate a host interrupt.

Task File registers are initialized as follows:

Error 1 Sector Count 1 Sector Number 1 Cylinder Low 0 Cylinder High 0 Drive/Head 0

Interrupt Handling

The drive requests data transfers to and from the host by asserting its IRQ 14 signal. This signal interrupts the host if enabled by bit 1 (IRQ enable) of the Fixed Disk Control register.

Clear this interrupt by reading the Status register, writing the Command register, or by executing a host hardware or software reset.

6 – 6

Interface Commands

The following section describes the commands (and any parameters necessary to execute them), as well as Status and Error register bits affected.

Read Commands

Read Sector(s) Read Verify Sector(s) Read Sector Buffer Read DMA

Multi-word DMA

Ultra DMA Read Multiple Set Multiple

Write Commands

Write Sector(s) Write Verify Sector(s) Write Sector Buffer Write DMA

Multi-word DMA

Ultra DMA Write Multiple

INTERFACE COMMANDS

SECTION 7

Set Feature Commands

Set Features Mode

Power Mode Commands

Standby Immediate Idle Immediate Standby Idle Check Power Mode Set Sleep Mode Default Power-on Condition

Initialization Commands

Identify Drive Initialize Drive Parameters

7 – 1

INTERFACE COMMANDS

Read Commands

Read Sector(s)

Reads from 1 to 256 sectors, as specified in the Command Block, beginning at the specified sector. (A sector count of 0 requests 256 sectors.) Immediately after the Command register is written, the drive sets the BSY bit and begins execution of the command. If the drive is not already on the desired track, an implied seek is performed.

Once at the desired track, the drive searches for the data address mark of the requested sector. The data address mark must be recognized within a specified number of bytes, or the Data Address Mark Not Found error will be reported. Assuming the data address mark is found:

1. The data field is read into the sector buffer.

2. Error bits are set (if an error was encountered).

3. The DRQ bit is set.

4. An interrupt is generated.

The DRQ bit is always set, regardless of the presence or absence of an error condition after the sector. Upon command completion, the Command Block registers contain the numbers of the cylinder, head and sector of the last sector read. Back-to-back sector read commands set DRQ and generate an interrupt when the sector buffer is filled at the completion of each sector. The drive is then ready for the data to be read by the host. DRQ is reset and BSY is set immediately when the host empties the sector buffer.

If an error occurs during Read Sector commands, the read terminates at the sector where the error occurred. The host may then read the Command Block to determine the nature of that error, and the sector where it happened. If the error type is a correctable or an non-correctable data error, the flawed data is loaded into the sector buffer.

A Read Long command sets the Long bit in the command code and returns the data and the ECC bytes in the data field of the specified sector. During a Read Long, the drive does not check the ECC bytes to determine if there has been a data error. The Read Long command is limited to single sector requests.

Read Verify Sector(s)

Identical to the Read Sector(s) command, except that:

1. DRQ is never set,

2. No data is transferred back to the host and

3. The long bit is not valid.

7 – 2

INTERFACE COMMANDS

Read DMA

Multi-word DMA

Identical to the Read Sector(s) command, except that

1. The host initializes a slave-DMA channel prior to issuing the command,

2. Data transfers are qualified by DMARQ and are performed by the slave-DMA channel and

3. The drive issues only one interrupt per command to indicate that data transfer has terminated and status is available.

Ultra DMA

With the Ultra DMA Read protocol, the control signal (DSTROBE) that latches data from DD(15:0) is generated by the devices which drives the data onto the bus. Ownership of DD(15:0) and this data strobe signal are given DSTROBE to the drive during an Ultra DMA data in burst.

During an Ultra DMA Read burst, the drive always moves data onto the bus, and, after a sufficient time to allow for propagation delay, cable settling, and setup time, the sender shall generate a DSTROBE edge to latch the data. Both edges of DSTROBE are used for data transfers.

Any unrecoverable error encountered during execution of a Read DMA command terminates data transfer after the transfer of all sectors prior to the sector where the error was detected. The sector in error is not transferred. The drive generates an interrupt to indicate that data transfer has terminated and status is available. The error posting is identical to the Read Sector(s) command.

Read Multiple

Performs similarly to the Read Sector(s) command, except that for each READ MULTIPLE command data transfers are multiple sector blocks and the Long bit is not valid.

Execution is also similar to that of the READ SECTOR(S) command, except that:

1. Several sectors are transferred to the host as a block, without intervening interrupts.

2. DRQ qualification of the transfer is required only at the start of each block, not of each sector.

The block count consists of the number of sectors to be transferred as a block. (The block count is programmed by the Set Multiple Mode command, which must be executed prior to the Read Multiple command.) READ LONG command is limited to single sector requests.

When the Read Multiple command is issued, the Sector Count register contains the number of sectors requested — not the number of blocks or the block count. If the number of sectors is not evenly divisible by the block count, as many full blocks as possible are transferred, followed by a final, partial block transfer. This final, partial block transfer is for N sectors, where N = (sector count) modulo (block count)

The Read Multiple operation will be rejected with an Aborted Command error if attempted:

1. Before the Set Multiple Mode command has been executed, or

2. When Read Multiple commands are disabled.

The controller reports disk errors encountered during Read Multiple commands at the start of the block or partial block transfer. However, DRQ still sets, and the transfer occurs normally, along with the transfer of any corrupt data. Remaining block data from the following the sector in error is not valid.

If the Sector Count register contains 0 when the Set Multiple Mode command is issued, Read Multiple and Write Multiple commands are disabled; no error is returned. Once the appropriate action has been taken, the controller resets BSY and generates an interrupt. At power up, or after a hardware or software reset, Read Multiple and Write Multiple commands are disabled by default.

7 – 3

INTERFACE COMMANDS

Set Multiple Mode

Enables the controller to perform Read and Write Multiple operations, and establishes the block count for these commands. Before issuing this command, the Sector Count register should be loaded with the number of sectors per block. The drives support block sizes of 2, 4, 8 and 16 sectors.

When this command is received, the controller sets BSY and examines the Sector Count register contents. If they contain a valid and supported block count value, that value is loaded for all subsequent Read and Write Multiple commands, and execution of those commands is enabled. An invalid and unsupported block count in the register results in an Aborted Command error and disallows Read Multiple and Write Multiple commands.

Write Commands

Write Sector(s)

Writes from 1 to 256 sectors, beginning at a sector specified in the Command Block. (A sector count of 0 requests 256 sectors.)

When the Command register is written, the drive sets the DRQ bit and waits for the host to fill the sector buffer with the data to be written. An interrupt is not generated to start the first buffer fill operation.

Once the buffer is full, the drive resets DRQ, sets BSY, and begins command execution. If the drive is not already on the desired track, an implied seek is performed.

The data loaded in the buffer is written to the data field of the sector, followed by the ECC bytes. Upon command completion, the Command Block registers contain the cylinder, head and sector number of the last sector written. The next time the buffer is ready to be filled during back-to-back Write Sector commands, DRQ is set and an interrupt is generated.

After the host fills the buffer, DRQ is reset and BSY is set. If an error occurs, Write Sector operations terminate at the sector containing the error.

The Command Block registers then contain the numbers of the cylinder, head and sector where the error occurred. The host may read the Command Block to determine the nature of that error, and on which sector it happened. A Write Long may be executed by setting the Long bit in the command code. The Write Long command writes the data and the ECC bytes directly from the sector buffer; the drive itself does not generate the ECC bytes. Restrict Write Long commands to PIO Mode 0.

Write Verify Sector(s)

Identical to the Write Sector(s) command, except that the requested sectors are verified immediately after being written. The verify operation reads (without transferring), and checks for data errors. Any errors encountered during this operation are reported.

Write Sector Buffer

Allows the host to overwrite the contents of the drive’s sector buffer with a selected data pattern. When this command is received, the drive:

1. Sets BSY,

2. Sets up the sector buffer for a write operation,

3. Sets DRQ,

4. Resets BSY and

5. Generates an interrupt.

7 – 4

The host may then write up to 256 words of data to the buffer. A disk write task begins to store the host data to disk. Host write commands continue to be accepted and data transferred to the buffer until either the write command stack is full or the data buffer is full. The drive may reorder write commands to optimize drive throughput.

INTERFACE COMMANDS

Write Multiple

Performs similarly to the Write Sector(s) command, except that:

1. The controller sets BSY immediately upon receipt of the command,

2. Data transfers are multiple sector blocks and

3. The Long bit and Retry bit is not valid.

Command execution differs from Write Sector(s) because:

1. Several sectors transfer to the host as a block without intervening interrupts.

2. DRQ qualification of the transfer is required at the start of the block, not on each sector.

The block count consists of the number of sectors to be transferred as a block and is programmed by the Set Multiple Mode command, which must be executed prior to the Write Multiple command. When the Write Multiple command is issued, the Sector Count register contains the number of sectors requested — not the number of blocks or the block count.

If the number of sectors is not evenly divisible by the block count, as many full blocks as possible are transferred, followed by a final, partial block transfer. This final, partial block transfer is for N sectors, where N = (sector count) modulo (block count)

The Write Multiple operation will be rejected with an Aborted Command error if attempted:

1. Before the Set Multiple Mode command has been executed, or

2. When Write Multiple commands are disabled.

All disk errors encountered during Write Multiple commands report after the attempted disk write of the block or partial block in which the error occurred.

The write operation ends with the sector in error, even if it was in the middle of a block. When an error occurs, subsequent blocks are not transferred. When DRQ is set at the beginning of each full and partial block, interrupts are generated.

Write DMA

Multi-word DMA

Identical to the Write Sector(s) command, except that:

1. The host initializes a slave-DMA channel prior to issuing the command,

2. Data transfers are qualified by DMARQ and are performed by the slave-DMA channel and

3. The drive issues only one interrupt per command to indicate that data transfer has terminated at status is available.

Ultra DMA

With the Ultra DMA Write protocol, the control signal (HSTROBE) that latches data from DD(15:0) is generated by the devices which drives the data onto the bus. Ownership of DD(15:0) and this data strobe signal are given to the host for an Ultra DMA data out burst.

During an Ultra DMA Write burst, the host always moves data onto the bus, and, after a sufficient time to allow for propagation delay, cable settling, and setup time, the sender shall generate a HSTROBE edge to latch the data. Both edges of HSTROBE are used for data transfers.

Any error encountered during Write DMA execution results in the termination of data transfer. The drive issues an interrupt to indicate that data transfer has terminated and status is available in the error register. The error posting is the same as that of the Write Sector(s) command.

7 – 5

INTERFACE COMMANDS

Set Feature Commands

Set Features Mode

Enables or disables features supported by the drive. When the drive receives this command it:

1. Sets BSY,

2. Checks the contents of the Features register,

3. Clears BSY and

4. Generates an interrupt.

If the value of the register is not a feature supported by the drive, the command is aborted. The acceptable values in the Features register are defined as follows:

EULAVNOITPIRCSED

*h20ehcacetirwdelbanE

h30retsigertnuoCrotceSnieulavnodesabedomrefsnartteS

h44 ehtnideificepssdnammocgnoLetirW/gnoLdaeRnodedneppaatadfohtgneL

h55erutaefdaeha-kooldaerelbasiD

*h66stluafedno-rewopotgnitreverelbasiD

h28ehcacetirwelbasiD

*hAAerutaefdaeha-kooldaerelbanE

*hBB sdnammocgnoLetirW/gnoLdaeRnodedneppaatadcificepsrotxaMfosetyb4

hCCstluafedno-rewopotgnitreverelbanE

*.tluafedybpurewoptadelbanE

noitamrofnieciveDyfitnedI

7 – 6

INTERFACE COMMANDS

Power Mode Commands

Standby Immediate – 94h/E0h

Spin down and do not change time out value. This command will spin the drive down and cause the drive to enter the STANDBY MODE immediately. If the drive is already spun down, the spin down sequence is not executed.

Idle Immediate – 95h/E1h

Spin up and do not change time out value. This command will spin up the spin motor if the drive is spun down, and cause the drive to enter the IDLE MODE immediately. If the drive is already spinning, the spin up sequence is not executed. The actuator is parked and some circuits are powered off.

Standby – 96h/E2h

Spin down and change time out value. This command will spin the drive down and cause the drive to enter the STANDBY MODE immediately. If the drive is already spun down, the spin down sequence is not executed. A non-zero value placed in the sector count register will enable the Automatic Power Down sequence. The timer will begin counting down when the drive returns to the IDLE MODE. A value of zero placed in the sector count register will disable the Automatic Power Down sequence.

Idle – 97h/E3h

Spin up and change time out value. This command will spin-up the spin motor if the drive is spun-down. If the drive is already spinning, the spin up sequence is not executed. A non-zero value placed in the Sector Count register will enable the Automatic Power Down sequence and their timer will begin counting down immediately. A value of zero placed in the Sector Count register will disable the Automatic Power Down sequence. The actuator is parked and some circuits are powered off.

Check Power Mode – 98h/E5h

This command returns a code in the Sector Count register that determines the current Power Mode status of the drive. If the drive is in, going to, or recovering from the STANDBY MODE the drive sets the Sector Count register to OOh. If the drive is in the IDLE MODE or ACTIVE MODE, the drive sets the Sector Count register to FFh.

Set Sleep Mode – 99h/E6h

This command will spin the drive down and cause the drive to enter the SLEEP MODE immediately. If the drive is already spun down, the spin down sequence is not executed.

Note: The only way to recover from SLEEP MODE is with a software reset or a hardware reset.

Default Power-on Condition

The drive’s default power on condition is the ACTIVE MODE. Upon receiving a Power Mode command, except the SLEEP MODE command, the drive sets BSY and

performs the requested power operation. Once the requested Power Mode change has begun, the drive resets BSY and generates an interrupt - without waiting for the drive to spin up or spin down. Upon receiving a SLEEP MODE command the drive is spun down, and when it is stopped, the drive resets BSY and generates an interrupt.

7 – 7

INTERFACE COMMANDS

When enabling the Automatic Power Down sequence, the value placed in the Sector Count register is multiplied by five seconds to obtain the Time-out Interval value. If no drive commands are received from the host within the Time-out Interval, the drive automatically enters the STANDBY mode. The minimum value is 5 seconds.

0delbasidtuo-emiT

252setunim12

35201=doirepeuqinurodneV

452devreseR

552sdnoces51,setunim12

While the drive is in STANDBY MODE, any commands received from the host are accepted and executed as they would in normal operation, except that the spin motor is started if required to execute a disk command. Under these conditions, the drive will set BSY when command processing would normally begin and will leave BSY set until the drive comes up to speed and the disk command can be executed. Disk commands issued while the drive is in STANDBY MODE, restarts the Time-out Interval after completing the command. A reset must be issued before attempting to issue any commands while the drive in SLEEP MODE.

EULAVREMITDOIREPTUO-EMIT

042-1sdnoces)5*eulav(

152-142setunim)03*)042-eulav((

sruoh

7 – 8

INTERFACE COMMANDS

Initialization Commands

Identify Drive

Allows the host to receive parameter information from the drive. When the command is received, the drive:

1. Sets BSY,

2. Stores the required parameter information in the sector buffer,

3. Sets the DRQ bit and

4. Generates an interrupt.

The host may then read the information out of the sector buffer. Parameter words in the buffer follow. Note that all reserved bits or words should be zeroes.

DROWNOITPIRCSEDTNETNOC

0noitarugifnoclareneG

)IPATA=1,ATA=0(ecived=51

desuton=8-41

atadaidemelbavomer=1,7

ecivedro/dnarellortnocelbavomerton=1,6

devreser=1-5

1srednilycforebmuN

2devreseR

3sdaehlacigolforebmuN

5-4desutoN

6kcartrepsrotceslacigolforebmuN

9-7desutoN

91-01)sretcarahcIICSA04(rebmunlairesevirD

02desutoN

12)deificepston=h0000(stnemercnietyb215niezisreffuB

22 sdnammocgnoLetirW/daeRnoelbaliavasetybcificepsrotxaMforebmuN

62-32)sretcarahcIICSA8(noisivererawmriF

64-72)sretcarahcIICSA04(rebmunledoM

74 sdnammocelpitlumetirwdnadaernotpurretnirepderrefsnartebnactahtsrotcesforebmunmumixaM

84devreseR

94seitilibapaC

devreser=41-51

)cificepsrotxaMeraseulav=0,detroppuseradradnatssihtnideificepssaseulav=1(remitybdnats=31

)troppusedomOIPdecnavda(devreser=21

detroppusebyamYDROI=0,detroppusYDROI=1,11

delbasidebnacYDROI=1,01

devreser=8-9

desuton=0-7

7 – 9

INTERFACE COMMANDS

DROWNOITPIRCSEDTNETNOC

05devreseR

15edomrefsnartatadOIP=8-51

25edomrefsnartatadAMD=8-51

35devreser=51

45srednilyclacigoltnerrucforebmuN

55sdaehlacigoltnerrucforebmuN

65kcartrepsrotceslacigolforebmuN

85-75srotcesniyticapactnerruC

95devreser=9-51

dnammoc

16-06)ylnoedomABL(srotceselbasserddaresuforebmunlatoT

26devreseR

36evitcaedomrefsnartAMDdrow-itluM=8-51

46devreser=8-51

56 )sdnocesonanniemitelcyc=0-51(emitelcycrefsnartAMDdrow-itlummuminiM

66 )sdnocesonanniemitelcyc=0-51(emitelcycrefsnartAMDdrow-itlumdedemmocers'rerutcafunaM

76 )sdnocesonanniemitelcyc=0-51(lortnocwolftuohtiwemitelcycrefsnartOIPmuminiM

86 )sdnocesonanniemitelcyc=0-51(lortnocwolfYDROIhtiwemitelcycrefsnartOIPmuminiM

97-96devreseR

08devreser=5-51

18rebmunnoisrevroniM

28 .detroppustonnoitacifitontesdnammochFFFFroh0000=38dna28sdrowfI.detroppustesdnammoC

desuton=0-7

dilavtonera88sdrownidetroppussdleifeht=0,dilavera88sdrownidetroppussdleifeht=1,2

dilavtonera07-46sdrownistropersdleifeht=0,dilavera07-46sdrownistropersdleifeht=1,1

dilavtonera85-45sdrownistropersdleifeht=0,dilavera85-45sdrownistropersdleifeht=1,0

dilavsignittesrotceselpitlum=1,8

elpitluMetirW/daeRnotpurretnirepderrefsnartrepnactahtsrotcesforebmunrofgnittestnerruc=hxx0-7

detroppussedomrefsnartAMDdrow=itluM=0-7

detroppussedomrefsnartOIPdecnavda=0-7

4-ATAstroppus=1,4

3-ATAstroppus=1,3

2-ATAstroppus=1,2

1-ATAstroppus=1,1

devreser,0

dnammocAMDeciveDyfitnedIehtstroppus=1,51

dnammocPONehtstroppus=1,41

dnammocreffuBetirWehtstroppus=1,31

dnammocreffuBdaeRehtstroppus=1,21

dnammocreffuBdaeRehtstroppus=1,11

teserutaefaerAdetcetorP-tsoHstroppus=1,01

dnammocteseReciveDehtstroppus=1,9

tpuretnIecivreSstroppus=1,8

tpuretnIesaeleRstroppus=1,7

daehAkooLstroppus=1,6

ehcaCetirWstroppus=1,5

teserutaefdnammoctekcaPehtstroppus=1,4

dnammocerutaeftnemeganaMrewoPehtstroppus=1,3

dnammocerutaefelbavomeRehtstroppus=1,2

dnammocerutaefytiruceSehtstroppus=1,1

teserutaefTRAMSehtstroppus=1,0

7 – 10

DROWNOITPIRCSEDTNETNOC

38 tonnoitacifitontesdnammochFFFFroh0000=48dna38,28sdrowfI.detroppusstesdnammoC

.detroppus

orezotderaelcebllahs=51

enoottesebllahs=41

devreser=1-31

48 tesdnammochFFFFroh0000=68dna58,48sdrowfI.detroppussnoisnetxetesdnammoC

.detroppustonnoitacifiton

orezotderaelcebllahs=51

enoottesebllahs=41

devreser=0-31

58 tonnoitacifitontesdnammochFFFFroh0000=68dna58,48sdrowfI.delbanetesdnammoC

.detroppus

delbanednammocPON=1,41

delbanetpurretnIecivreS=1,8

delbanetpurretnIesaeleR=1,7

delbanedaehAkooL=1,6

delbaneehcaCetirW=1,5

68 tonnoitacifitontesdnammochFFFFroh0000=78dna68,58sdrowfI.delbanestesdnammoC

.detroppus

orezotderaelcebllahs=51

enoottesebllahs=41

devreser=1-31

78 tonnoitacifitontesdnammochFFFFroh0000=78dna68,58sdrowfI.delbanestesdnammoC

.detroppus

orezotderaelcebllahs=51

enoottesebllahs=41

devreser=0-31

88AMDartlU

devreseR11-51

INTERFACE COMMANDS

dnammocedocorciMdaolnwoDstroppus=1,0

delbanednammocAMDeciveDyfitnedI=1,51

delbanednammocreffuBetirW=1,31

delbanednammocreffuBdaeR=1,21

delbanednammocyfireVetirW=1,11

delbaneteserutaefaerAdetcetorPtsoH=1,01

delbanednammocteseReciveD=1,9

delbaneteserutaefdnammoctekcaP=1,4

delbaneteserutaeftnemegnaMrewoP=1,3

delbaneteserutaefelbavomeR=1,2

delbaneteserutaefytiruceS=1,1

delbaneteserutaefTRAMS=1,0

dnammocedocorciMdaolnwoDstroppus=1,0

detcelessi2edoMAMDartlU=101

devreseR3-7

721devreseR

821sutatSytiruceS

devreseR9-51

devreseR5-7

nezorfytiruceS=13

dekcolytiruceS=12

delbaneytiruceS=11

detroppusytiruceS=10

031-921devreseR

131 .delbanesipu-rewoptanipsonnehwdetressasi0tub,pu-rewoptanipS

951-231)desuton(cificeps-rotxaM

552-061devreseR

detcelessi1edoMAMDartlU=19

detcelessi0edoMAMDartlU=18

detroppuserawolebdna2sedoMAMDartlU=12

detroppuserawolebdna1sedoMAMDartlU=11

detroppustonsi1edoMAMDartlU=0

detroppussi0sedoMAMDartlU=10

detroppustonsi0edoMAMDartlU=0

mumixaM=1,hgiH=0leveLytiruceS8

deripxetnuocytiruceS=14

7 – 11

INTERFACE COMMANDS

Initialize Drive Parameters

Enables the drive to operate as any logical drive type. The drive will always be in the translate mode because of Zone Density Recording, which varies the number of sectors per track depending on the zone. Through setting the Sector Count Register and Drive Head Register, this command lets the host alter the drive's logical configuration. As a result, the drive can operate as any equal to or less than capacity drive type. Do not exceed the total number of sectors available on the drive:

When this command is executed, the drive reads the Sector Counter Register and the Drive Head Register (and so determines the number of the logical sectors per track and maximum logical head number per cylinder and will calculate the number of logical cylinders.)

Upon receipt of the command, the drive:

1. Sets BSY,

2. Saves the parameters,

3. Resets BSY and

4. Generates an interrupt.

To specify maximum heads, write 1 less than the maximum (e.g. write 4 for a 5 head drive). To specify maximum sectors, specify the actual number of sectors (e.g. 17 for a maximum of 17 sectors/track).

The sector count and head values are not checked for validity by this command. If they are invalid, no error will be posted until an illegal access is made by some other command.

Moves the read/write heads from anywhere on the disk to cylinder 0. When this command is received, the drive:

1. Sets BSY and

2. Issues a seek to cylinder zero.

The drive waits for the seek to complete, then the drive:

1. Updates status,

2. Resets BSY and

3. Generates an interrupt.

If the drive cannot reach cylinder 0, the Error bit is set in the Status register, and the Track 0 bit is set in the Error register.

NOTE: If a maximum head and sector number is selected – such that the number of cylinders will exceed 65,535 – then the maximum cylinder value will be reduced to 65, 535.

7 – 12

INTERFACE COMMANDS

Seek, Format and Diagnostic Commands

Seek

Initiates a seek to the track, and selects the head specified in the Command block.

1. Sets BSY in the Status register,

2. Initiates the Seek,

3. Resets BSY and

4. Generates an interrupt.

The drive does not wait for the seek to complete before returning the interrupt. If a new command is issued to a drive during the execution of a Seek command, the drive will wait (with BSY active) for the Seek to complete before executing the new command.

Format Track

Formats the track specified in the Command Block. Shortly after the Command register is written, the drive sets the bit, and waits for the host to fill the sector buffer with the interleave table. When the buffer is full, the drive resets DRQ, sets BSY and begins command execution. If the drive is not already on the desired track, an implied seek is performed. Once at the desired track the data fields are written with all zeroes.

Execute Drive Diagnostic

Commands the drive to implement the internal diagnostic tests. (These tests are executed only upon command receipt; they do not run automatically at power up or after a reset.)

The drive sets BSY immediately upon receiving this command. The following table presents the codes and their descriptions. Note that the value in the Error register should be viewed as a unique 8 bit Code.

EDOCRORRENOITPIRCSED

10detcetedrorreoN

00deliafevirdretsaM

28,08deliafsevirdevalsdnaretsaM

18deliafevirdevalS

Note: If a slave drive fails diagnostics, the master drive OR’s 80h with its own status, and loads that code into the Error register. If a slave drive passes diagnostics (or a slave is absent), the master drive OR’s 00 with its own status and loads that code into the Error register.

7 – 13

INTERFACE COMMANDS

S.M.A.R.T. Command Set

Execute S.M.A.R.T.

The Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.) command has been implemented to improve the data integrity and data availability of hard disk drives. In some cases, a S.M.A.R.T. capable device will predict an impending failure with sufficient time to allow users to backup their data and replace the drive before data loss or loss of service.

The S.M.A.R.T. sub-commands (listed below) comprise the ATA S.M.A.R.T. feature set that provide access to S.M.A.R.T. attribute values, attribute thresholds and other logging and reporting information.

Prior to writing a S.M.A.R.T. command to the device’s command register, key values must be written by the host into the device’s Cylinder Low and Cylinder High registers, or the command will be aborted. For any S.M.A.R.T. sub-command, if a device register is not specified as being written with a value by the host, then the value in that register is undefined and will be ignored by the device. The key values are:

Key Register

4Fh Cylinder Low (1F4h) C2h Cylinder High (1F5h)

The S.M.A.R.T. sub-commands use a single command code (B0h) and are differentiated from one another by the value placed in the Features register. In order to issue a command, the host must write the subcommand-specific code to the device’s Features register before writing the command code to the command register. The sub-commands and their respective codes are:

D0h S.M.A.R.T. Read Attribute Value

This feature returns 512 bytes of attribute information to the host.

D1h S.M.A.R.T. Read Attribute Thresholds

D2h Enable/Disable Autosave

D3h S.M.A.R.T. Save Attribute Value

D4h Perform Off-Line Data Collection

D8h Enable S.M.A.R.T. D9h Disable S.M.A.R.T. DAh S.M.A.R.T. Return Status

This feature returns 512 bytes of warranty failure thresholds to the host.

To enable this feature, set the sector count register to F1h (enable) or 0 (disable). Attribute values are automatically saved to non-volatile storage on the device after five minutes of idle time and before entering idle, sleep or standby modes. This feature is defaulted to “enabled” when S.M.A.R.T. is enabled via the S.M.A.R.T. Enable Operations commands. The autosave feature will not impact host system performance and does not need to be disabled.

This feature saves the current attribute values to non-volatile storage.

Data is collected from random seeks, timed pattern seek times and head margin tests.

This feature allows the host to assess the status of a S.M.A.R.T. capable device by comparing all saved attribute values with their corresponding warranty failure thresholds. If no thresholds are exceeded, the drive is declared to have a positive health status. If any warranty failure threshold is exceeded, the drive is declared to have a negative health status. Executing this sub-command results in all attribute values being saved to non-volatile storage on the device.

7 – 14

DBh Enable/Disable Automatic Off-Line

To enable this feature, set the Sector Count register to F1h or 0 to disable.

SERVICE AND SUPPORT

SECTION 8

Service and Support

Service Policy

Repairs to any DiamondMax™ 2160 drive should be made only at an authorized Maxtor repair facility. Any unauthorized repairs or adjustments to the drive void the warranty.

To consistently provide our customers with the best possible products and services, Maxtor developed the Total Customer Satisfaction (TCS) program. Through the ongoing TCS process, Maxtor employees take direct responsibility for every customer’s level of satisfaction – with Maxtor technology, price, quality, delivery, service and support.

No Quibble® Service

Another TCS feature is Maxtor’s No Quibble® Service policy. By minimizing paperwork and processing, No Quibble Service dramatically cuts the turnaround time normally required for repairs and returns.

Here’s how it works:

1. Customer calls 1-800-2MAXTOR for a Return Material Authorization (RMA) number and provides a credit card number,

2. Maxtor ships a replacement drive within 48 hours, and

3. Customer returns the original drive and credit card draft is destroyed.

Support

Technical Assistance

Highly-trained technicians are available 6 a.m. to 6 p.m. (Mountain Standard Time) Monday through Friday to provide detailed technical support.

U.S. and Canada Language support: English, Spanish

Voice 800-2MAXTOR, press 1 (800-262-9867) E-mail Technical_Assistance@maxtor.com Fax 303-678-2260

Outside U.S. and Canada 303-678-2015 Europe Language support: English, French, German

Voice + 353 1 204 11 11 E-mail Eurotech_Assistance@maxtor.com Fax + 353 1 286 14 19

Asia/Pacific

Voice Contact your local Maxtor Sales Office for assistance E-mail Apactech_Assistance@maxtor.com

Language support: English

MaxInfo Service

Use a touch-tone phone to listen to technical information about Maxtor products and the top Q&A’s from our 24-hour automated voice system.

U.S. and Canada 800-2MAXTOR (800-262-9867)

Press 1, wait for announcement, press 1.

Outside U.S. and Canada 303-678-2015, press 1

8 – 1

SERVICE AND SUPPORT

MaxFax™ Service

Use a touch-tone phone to order Technical Reference Sheets, Drive Specifications, Installation Sheets and other documents from our 24-hour automated fax retrieval system. Requested items are sent to your fax machine.

U.S. and Canada Language support: English, Spanish

Phone 800-2MAXTOR, press 3 (800-262-9867) Outside U.S. and Canada 303-678-2618 Europe Language support: English, French, German

Phone + 353 1 204 11 22 Asia/Pacific Language support: English

Phone + 61 2 9369 4733

Internet

Browse the Maxtor home page on Internet, download files from our FTP site.

Home Page http://www.maxtor.com

Bulletin Board Service

A 24-hour seven-day-a-week Bulletin Board Service (BBS) is available. Use the BBS to access and download information and utilities maintained in the Maxtor data files, including utilities, drive specifications and jumper options. Modem settings are 14,400 Baud or lower, 8, 1, N.

U.S. and Canada Language support: English

Data Phone 303-678-2222 Asia/Pacific Language support: English

Data Phone + 61 2 9369 4293

Customer Service

All Maxtor products are backed by No Quibble

Service, the benchmark for service and support in the

industry. Customer Service is available 6 a.m. to 5 p.m. (Pacific Standard Time) Monday through Friday.

U.S. and Canada Language support: English, Spanish

Voice 800-2MAXTOR, press 2 (800-262-9867)

E-mail RMA@maxtor.com

Fax 408-922-2050 Europe Language support: English, French, German

Voice + 353 1 204 11 11

E-mail Eurotech_Assistance@maxtor.com

Fax + 353 1 286 14 19 Asia/Pacific Call Singapore Customer Service from the countries listed below.

Customer Service is available 8 a.m. to 5:30 p.m.

(Singapore time is GMT +8).

From Dial

Australia 1-800-124-328 Hong Kong +800-3387 Indonesia +001-800-65-6500 Japan +0031-65-3616 Korea +088-65-800-6500 Malaysia 1-800-1126 New Zealand +0800-44-6542 Singapore 1-800-481-6788 Taiwan +0080-65-1062 Thailand +001-800-65-6500

8 – 2

Maxtor DIAMONDMAXTM 83240D3, DIAMONDMAXTM 88400D8, DIAMONDMAXTM 2160, DIAMONDMAXTM 84320D4, DIAMONDMAXTM 82160D2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual