Hard Disk Drive Specification

Ultrastar C10K147

2.5 inch Serial Attached SCSI (SAS) Hard Disk Drive Models: HUC101414CSS300 HUC101473CSS300

Version 1.0

04 May 2007
Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal of downlevel versions is the responsibility of the document holder.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specificationn
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification
Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal of down-level versions is the responsibility of the document holder.
1st Edition (Rev 1.0) (04 May 2007)
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: HITACHI GLOBAL STORAGE TECHNOLOGIES PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer or express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Hitachi may make improvements or changes in any products or programs described in this publication at any time. It is possible that this publication may contain reference to, or information about, Hitachi products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Hitachi intends to announce such Hitachi products, programming, or services in your country. Technical information about this product is available by contacting your local Hitachi Global Storage Technologies representative or on the Internet at http://www.hitachigst.com Hitachi Global Storage Technologies may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Copyright Hitachi Global Storage Technologies Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with Hitachi Global Storage Technologies.

Table of Contents

1.0 General....1 1.1 Introduction....1 1.2 Glossary....1 1.3 Caution....1 2.0 Outline of the Drive...3 3.0 Fixed-disk Subsystem Description...5 3.1 Control Electronics....5 3.2 Head Disk Assembly....5 3.3 Actuator....5 4.0 Drive Characteristics....7 4.1 Formatted Capacity....7 4.2 Data Sheet....7 4.3 Inquiry Information....8 4.3.1 Product ID....8 4.3.2 World Wide ID - Block Assignment...8 4.4 Cylinder allocation....9 4.5 Performance characteristics....10 4.5.1 Mechanical positioning...11 4.5.2 Drive ready time....12 4.5.3 Spindle stop time....12 4.5.4 Data transfer speed....13 4.5.5 Buffering operation (read ahead/write cache)...13 5.0 Data Integrity.....15 5.1 Equipment Status...15 5.2 Error Recovery Procedure...15 6.0 Physical Format....17 6.1 Shipped Format (P-List)....17 6.2 Reassigned Format (G-List)....17 7.0 Electrical Interface....19 7.1 SAS Connector....19 7.1.pin Serial Attached SCSI (SAS) Connector Definition.19 7.1.2 Voltage and Ground Signals....20 7.1.3 Ready LED output....20 8.0 Environment....21 8.1 Temperature and humidity....21 8.2 Storage requirements....22 8.2.1 Packaging....22 8.2.2 Storage time....22 8.3 Corrosion test....22 8.4 Cooling requirements....23 9.0 DC Power Requirements....25 9.1 Power Supply Current, Average and Peak...26

11.6 Heads Unload and Actuator Lock
Heads are moved out from the disks (unload) to protect the disk data during shipping, moving or storage. At power down, the heads are automatically unloaded from over the disk area and the head actuator locking mechanism will secure the heads in the unload position.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 36

12.0 Vibration and Shock

All vibration and shock measurements in this section are made with a bare drive. The input for the measurements are applied to the normal drive mounting points unless noted otherwise.

12.1 Operating Vibration

12.1.1 Random Vibration
The drive is designed to operate without unrecoverable errors while being subjected to the vibration levels as defined below. The assessments are carried out during 30 minutes of random vibration using the power spectral density (PSD) levels as follows. No Errors: 0.4 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes.
No Data Loss: 1.2 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes. No Data Loss: 1.5 G RMS, 10-300 Hz for each of the three mutually perpendicular axes. Note: The specified levels are measured at the mounting points.
12.1.2 Swept Sine Vibration
The drive will meet the criterion while operating in the respective conditions as described below. No errors: No data loss: 0.5 G 0-peak, 5-400-5 Hz sine wave, 0.5 octave/minute sweep rate 1.5 G 0-peak, 5-300-5 Hz sine wave, 0.5 octave/minute sweep rate
12.2 Non-operating Vibrations
The drive will not sustain permanent damage or loss of recorded data after being subjected to the environments as described below.

12.2.1 Random Vibration

The test consists of a random vibration applied for each of the three mutually perpendicular axes. A time duration of ten minutes per axis. 1.04 G RMS, 5-500 Hz, flat PSD profile.
12.2.2 Swept Sine Vibration
The test consists of a swept sine vibration applied for each of the three mutually perpendicular axes. 1.5 G 0-peak, 5 - 500 Hz sine wave, 0.5 octave/minute sweep rate.

12.3 Operating shock

The drive will meet the criterion while operating in the respective conditions as described below. No data loss: No data loss: 15G, 11 ms duration, half sinewave shock pulse 30G, 2 ms duration, half sinewave shock pulse
The shock pulses of each level are applied to the drive, ten pulses for each direction and for all three mutually perpendicular axes. There must be a minimum of thirty seconds delay between shock pulses. The input level is applied to a base plate where the drive is attached using four mounting screws.

The labels may be integrated with other labels.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 41
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 42
15.0 Electromagnetic Compatibility
The drive, when installed in a suitable enclosure and exercised with a random accessing routine at a maximum data rate will comply with the worldwide EMC requirements listed below. The drive is designed for system integration and installation into a suitable enclosure for use. As such, the drive is supplied as a subassembly and is not subject to Subpart B of Part 15 of the FCC Rules and Regulations. The design of the drive serves to minimize radiated emissions when installed in an enclosure that provides reasonable shielding. As such, the drive is capable of meeting FCC Class B limits. However, it is the users responsibility to assure that the drive meets the appropriate EMC requirements in their system. Shielded I/O cables may be required if the enclosure does not provide adequate shielding, with the shields grounded to the enclosure and to the host computer.
Radiated and Conducted EMI CISPR22 AS/NZS CISPR22 CNS13438 (Taiwan) EN55022 (EU) FCC Title47 Part 15 (USA) GB9254 (China) ICES-003, Issue 4 VCCI (Japan) Class B Class B Class B Class B Class B Class B Class B Class B

ITE Immunity EN55024

Power Line Harmonics EN61000-3-2 (EU) GB17625.1 (China)
Voltage Fluctuations and Flicker EN61000-3-3 (EU) GB17625.2 (China)
15.1 Class B Regulatory Notices
European Union This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC, as amended by Council Directive 93/68/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. Hitachi cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-Hitachi option cards. This product has been tested and found to comply with the limits for Class B Information Technology Equipment according to
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 43
European Standard EN 55022. The limits for Class B equipment were derived for typical residential environments to provide reasonable protection against interference with licensed communication devices. Canada This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numrique de la classe B est conforme la norme NMB-003 du Canada. Germany Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse B EU-Richtlinie zur Elektromagnetischen Vertrglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 89/336/EWG zur Angleichung der Rechtsvorschriften ber die elektromagnetische Vertrglichkeit in den EU-Mitgliedsstaaten. und hlt die Grenzwerte der EN 55022 Klasse B ein. Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu installieren und zu betreiben. Des Weiteren drfen auch nur von der HITACHI empfohlene Kabel angeschlossen werden. HITACHI bernimmt keine Verantwortung fr die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der HITACHI verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne Empfehlung der HITACHI gesteckt/eingebaut werden. Deutschland: Einhaltung des Gesetzes ber die elektromagnetische Vertrglichkeit von Gerten Dieses Produkt entspricht dem "Gesetz ber die elektromagnetische Vertrglichkeit von Gerten (EMVG)". Dies ist die Umsetzung der EU-Richtlinie 89/336/EWG in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz ber die elektromagneti-sche Vertrglichkeit von Gerten (EMVG) vom 18. September 1998 (bzw. der EMC EG Richtlinie 89/336) fr Gerte der Klasse B Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das EG-Konformittszeichen - CE - zu fhren. Verantwortlich fr die Konformittserklrung nach Paragraf 5 des EMVG ist die Hitachi Global Storage Technologies , 5600 Cottle road, San Jose, California 95193. Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4: Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse B. Korea (MIC)

Taiwan (BSMI)

Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 44

16.0 Standards

The following shows the safety standards for different countries.
16.1 UL and C-UL Standard Conformity
The drive is qualified per ULIEC 60950-1: 2001, First Edition for use in Information Technology Equipment, including Electric Business Equipment. The UL recognition, or the C-UL certification, is maintained for the product life. The UL and C-UL recognition mark appears on the drive.
16.2 European Standards Compliance
The product is certified to EN60950.

16.3 German Safety Mark

The product is approved by TUV on Test requirement: EN 60950, but the GS mark is not applicable to internal devices such as these drives.

16.4 Flammability

The printed circuit boards used in this drive are made of material with a UL recognized flammability rating of V-1 or better. The flammability rating is marked or etched on the board. All other parts not considered electrical components are made of material with a UL recognized flammability rating of V-1 or better.
16.5 Corporate Standards Compliance
This product has been designed to meet the following Corporate Standards: - NB 3-0501-201 Product Safety, National Requirements-All Countries. - CS 3-0501-070 Electrical, Mechanical and Flammability - NB 3-0501-033 Product Safety National Certification Conformity Requirement - CS 1-9700-020 Eco-Product Design Requirement Hitachi GST encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is no longer needed. Hitachi GST offers a variety of programs and services to assist equipment owners in recycling their IT products.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 45
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 46

17.0 SAS Attachment

This section defines some basic terminology and describes the behavior of the drive when attached to a Serial Attached Scsi (i.e. SAS) domain.

17.1 General

This section introduces some of the terminology that is used in describing Serial Attached SCSI (i.e. SAS). SAS is logically a bi-directional, point to point serial data channel that leverages the Scsi protocol set. Nodes are physically connected via a Port. Ports may be connected point-to-point via SAS expanders, to form a complex switching network, referred to as a SAS domain. SAS is defined in terms of a hierarchy of functions or 'protocol layers'. This discussion will focus in on the aspects of SAS that are relevent to this product. SCSI Application Layer - Clause 10 SSP Transport Layer (Serial SCSI Protocol) - Clause 9 SAS Port Layer - Clause 8 SSP Link Layer - Clause 7 SAS PHY Layer - Clause 6 SAS Physical Layer - Clause 5

Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 50
Link Reset sequence Phy Reset sequence

OOB sequence

Speed Negotiation sequence

Identification sequence

SAS w/Hard Reset
Link Reset Sequence with hard Reset Phy Reset sequence Hard Reset Sequence Phy Reset sequence Identification sequence

17.5.2 Hard Reset

A Hard Reset sequence on a port will not affect the other port, but the outstanding commands on the other port will be aborted due to the LUN reset associated with the Hard Reset. The effect of a Hard Reset will be similar to a Power on Reset, and will result in the re-initialization of all Drive resources. The first command issued from every initiator on the port that received the Hard Reset will result in a CHECK CONDITION with a sense key of UNIT ATTENTION and an additional sense code of SCSI BUS RESET OCCURRED. The first command issued from every initiator on the other port will result in a CHECK CONDITION and an additional sense code of BUS DEVICE RESET OCCURRED.
A Hard Reset Sequence will never be issued by the Drive. A link reset will be initiated by the drive on the affected port upon completion of Hard Reset processing.
17.5.3 SAS OOB (Out of Band)
Out of band (OOB) signals are low-speed signal patterns detected by the Phy that do not appear in normal data streams. They consist of defined amounts of idle time followed by defined amounts of burst time. During the idle time, D.C. idel is transmitted. During the burst time, ALIGN (0) primitives are transmitted repeatedly. The signals are differentiated by the length of idle time between the burst times. As a SAS compliant device, the Drive uses three OOB signals: COMINIT/COMRESET and COMWAKE and COMSAS.OOB operations are beyond the scope of this specification. Please refer to the ANSI SAS 1.1 specification for more details. The drive will initiate OOB by sending COMINITs, under the following conditions: POR loss of sync
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 51

Identify timeout

17.5.4 SAS Speed Negotiation
The Drive supports both G1 (1.5 Gbps) and G2 (3.0 Gbps) negotiation speeds. The default maximum negotiation rate is G2 speed (per byte 32 in the Phy Control and Discover Mode Page 19 subpage 1) and the drive will always attempt to negotiate this rate. If the Link will not support G2, the drive will fall back to a G1 negotiated rate.

Qualifier is set to zero to indicate that the LUN specified is currently supported. Qualifier is set to 011b when the LUN specified is not present 1 Peripheral Device Type is set to zero to indicate that the device is a Direct-Access Peripheral Device. Removal Media Bit (RMB) is always set to zero to indicate no removal media exists. Version indicates the level of the ANSI standard that the product supports. The drive supports ANSI SCSI version 3. NormACA (Normal ACA) field of 0 indicates the device server does not support setting the NACA bit to one in the Control Byte of the CDB as defined in the SAM. HiSup bit of 1 indicates that the drive uses the hierarchical addressing model to assign LUNs to logical units. Response Data Format is set to two to indicate that the INQUIRY Data Format as specified in the ANSI SCSI version 2 is supported by the Target. Additional Length indicates the number of bytes of INQUIRY information that follows.
1.If an INVALID LUN is specified, a Check Condition status will be returned for all commands except INQUIRY and REQUEST SENSE.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 76
SCCS bit of zero indicates that the device does not contain an embedded storage array controller component. ACC bit of zero indicates that no access controls coordinator may be addressed through this logical unit. ALUA bit of zero indicates that the device does not support asymmetric logical unit access. 3PC bit of zero indicates that the device does not support thrid-party copy commands. Protect bit of one indicates that the drive supports protection information BQue bit shall be zero if the CmdQue bit is one. EncSer(Enclosure Services) bit of 0 indicates that the Target does not contain an embedded enclosure services component. Port bit of 0 indicates that the drive received the Inquiry command on port A, while a Port bit of 1 indicates that the drive received the Inquiry command on port B. MultiP (MultiPort) bit of 1 indicates that the Target has multiple ports and implements multi-port requirements. MChngr (Medium Changer) bit is always 0 to indicate MChngr is not supported. Addr16 (Wide SCSI Address 16) bit of 0 indicates that the Target does not support 16-bit wide SCSI Addresses. Wb_16 is set to zero to indicate that the Target does not support 16-bit wide data transfers. Sync is set to zero to indicate that the Target does not support synchronous data transfer. Link is set to zero to indicate that the Target does not support linked commands. CmdQue is set to one to indicate that the drive supports command queuing. Vendor ID is HITACHI padded with ASCII blanks. Product ID is specified in table 3 of Section 4.3.1. Product Revision Level indicates the level of microcode. Unit Serial Number contains the drive serial number.

Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 86
18.5.1.10 Inquiry Data Format - EVPD = 1, Page Code - D2h
Table 48: Inquiry Data - EVPD = 1 (Page Code = D2h) BIT Byte 5 - 22 - 39 - 6 Qualifier = 0 Peripheral Device Type = 0 Page Code = D2h Reserved = 0 Page Length = 52 (34h) HDC Version Length = 16 (10h) ASCII HDC Version Card Serial Number Length = 16 (10h) ASCII Card Serial Number Card Assembly Part Number Length = 16 (10h) ASCII Card Assembly Part Number Reserved = 0
Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported. Peripheral Device Type is set to zero to indicate that the device is Direct Access. Page Code is set to the value of the page code field in the CDB. Page Length is set to 52, and this field specifies the length of the following page data. Note: Note: If the media is not available, bytes 0 through 3 are valid. All the other fields are ASCII blanks (20h). All ASCII fields are alphanumeric, left aligned, and padded on the right with ASCII blanks (20h).
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 87

18.6 LOG SELECT (4C)

Table 49: Log Select (4C) Bit Byte 9 Reserved = 0 FLAG (MSB) Reserved = 0 Parameter List Length = 0 (LSB) LINK Reserved = 0 PC 0 Command Code = 4Ch Reserved = 0 Reserved = 0 PCR SP
The LOG SELECT command provides a means for the Initiator to clear statistical information maintained by the drive and reported via the LOG SENSE command. PCR The Parameter Code Reset determines whether the Log Sense parameters will be cleared and unit attention posted for all other Initiators. A value of 1 indicates that the parameters be cleared, while a value of zero (except when PC = 11b) indicates that the parameters not be cleared. Parameter list length must be zero when PCR is 1. The PC field is ignored for list parameters, i.e. when the Format and Linking (F&L) field contains 01b or 11b. SP The Save Parameters bit value of zero indicates that the page parameters not be saved. A value of 1 indicates that the page parameters that are savable be saved after they have been changed. SP bit MUST be 1 if parameter list length is greater than zero. Otherwise it will result in a Check Condition status being returned. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB. PC The Page Control field defines the type of parameters to be selected. The PC field set to 11b (and PCR is then a don't care) indicates that the Default Cumulative values are set to their default values of 0. If the PC field is set to 01b and PCR is set to 1, the Current Cumulative values are also set to their default values of 0. Parameter List Length MUST be zero when PC = 11b. Otherwise the command is terminated and a Check Condition status is returned. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB. Parameter List Length The Parameter List Length field specifies the length in bytes of the parameter list that shall be located in the DATA OUT buffer. A parameter list length zero indicates that no pages shall be transferred. Note: A specified length greater than 0x00FF will result in a Check Condition status being returned. A length that results in log data being truncated will generate a Check Condition status. Note: For page 0Fh, the maximum parameter list length supported is 4004h (4 bytes for the header and 100h bytes for each of the 40h parameters that are supported). The Parameter List Length must be an integral of the number of parameters plus the 4 byte header. (Ex: Parameter length =104h for one parameter, 204h for 2 parameters,. 4004h for all 40h parameters). The drive allows updates to the current cumulative values only. A value of zero is acceptable and is not considered an error. The drive updates only pages 0Eh, the Start/Stop Cycle page and 0Fh, the Application Client page. For other pages the parameters are ignored. If the data out buffer contains multiple pages then the application client should send the pages in ascending order. If the data out buffer contains multiple log parameters within a page,all log parameters within the page should be sent

Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 91
18.7.1 Log Page parameters
Each log page begins with a 4-byte page header followed by zero or more variable-length log parameters. Page header Page Code field identifies which log page is being transferred. The Page Length field specifies the length in bytes of the following log parameters. Log parameters Each log parameter begins with a 4-byte parameter header followed by one or more bytes of parameter value data. The Parameter Code field identifies which log parameter is being transferred for that log page. The Parameter Control field, the 3rd byte of each parameter header, contains several fields. - DU The Disable Update bit is set to 0 to indicate that the drive updates the log parameter value to reflect events that should be noted by that parameter. - TSD The Target Save Disable bit is set to zero to indicate that the drive provides a Target defined method for saving log parameters. - ETC The enable Threshold Comparison bit is set to 0 to indicate the drive does not perform comparisons between cumulative and any threshold values. - TMC The Threshold Met Criteria field is not valid because this drive does not perform threshold comparisons. This field is set to 0. - Format and Linking The F & L field indicates the type of log parameter and how parameters that reach their maximum value are handled. - 00b: Data counter: If any other parameter in this log page reaches its maximum value, then this parameter shall stop incrementing until reinitialized by a Log Select command. - 01b: List format ASCII data: No maximum values to handle - 10b: Data counter: If another parameter reported in this log page reaches its maximum value, then this parameter shall not stop incrementing. This parameter may be reinitialized by a Log Select command. - 11b: List format binary data: No maximum values to handle.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 92

18.7.2 Log Sense Page 0

Page 0 indicates the supported log sense pages. This page is used to determine which additional pages an Initiator can request. Table 51: Log Sense Page 0 Bit Byte 1 2-Reserved Page code = 0 Reserved Page Length = 000E(Number of Pages Supported) First supported page 00h Second supported page 02h Third supported page 03h Fourth supported page 05h Fifth supported page 06h Sixth supported page 0Dh Seventh supported page 0Eh Eighth supported page 0Fh Ninth supported page 10h Tenth supported page 15h Eleventh supported page 18h 16 Twelfth supported page 2Fh Thirteenth supported Page Code =30h Fourteenth supported Page Code = 37h
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 93

18.7.3 Log Sense Page 2

This page contains counters for write errors. Table 52: Log Sense Page 2 (part 1 of 2) Bit Byte 1 2-3 4-7 8-15 16-19 20-27 28-31 32-39 40-43 44-51 52-55 56-63 Table 53: Log Sense Page 2 (part 2 of 2) Bit Byte 7 64-Parameter Code = 0005h DU = 0 DS = 0 DU = 0 DS = 0 DU = 0 DS = 0 DU = 0 DS = 0 DU = 0 DS = Reserved Page code = 02h Reserved PageLength = 54h Parameter Code = 0000h TSD = 0 ETC = 0 TMC = 0 F&L = 00b

Note: When WCE = 1, a SYNCHRONIZE CACHE command must be done to ensure data are written to the media before powering down the Target. MF (Multiplication Factor) bit determines how the Maximum and Minimum Pre-fetch parameters are interpreted. If this bit is set to zero, the parameters are used as is. If the bit is set to one, the parameters are multiplied by the number of blocks requested in the Read Command. RCD (Read Cache Disable) bit set at zero indicates that the drive may return some or all of the data requested by a READ (6) or READ (10) command by accessing the data buffer, not the media. An RCD bit set at one indicates that the Target does not return any of the data requested by a READ (6) or READ (10) command by accessing the data buffer. All of the data requested is read from the media instead. Demand Read Retention Priority sets the retention priority of data requested on a Read command. It may be set as defined below: Value 0h 1h Fh Definition Do not distinguish between requested data and other data Replace requested data before other data. Replace other data before requested data.
where the value is the Demand Read Retention Priority or Write Retention Priority. Requested data is the blocks specified in the Read or Write command. Other data is data in the cache from any other operation such as pre-fetch, read-ahead, etc. If the Read Retention Priority is not set to Fh or if the DPO bit on the Read command is set to one, the requested data is overwritten by read-ahead data. If the DPO bit is set to zero and the Read Retention Priority is set to Fh, the requested data is not overwritten with read-ahead data. If the requested transfer is larger than the segment, the requested data is overwritten with more requested data and there is no read-ahead Write Retention Priority sets the retention priority of data provided on a Write command. See the definition of Demand Read Retention Priority above for more details. Disable Pre-fetch Transfer Length is used to prevent read-ahead after Read commands that are longer than the specified number of blocks. If this parameter is set to zero, a read-ahead is not performed. Minimum Pre-fetch specifies the minimum number of LBAs that the drive should after each READ command. A value of zero indicates that read ahead should be terminated immediately after a new command arrives, except when the new command is on the current head and track. Maximum Pre-fetch specifies the maximum number of LBAs to read ahead after a Read command. Maximum Pre-fetch Ceiling specifies the maximum number of blocks the drive should attempt to read ahead. This field is ignored. FSW (Force Sequential Write) is not supported and is ignored. All logical blocks will be written in sequential order. LBCSS (Logical Block Cache Segment Size) bit when set to one indicates that the Cache Segment Size field units shall be interpreted as logical blocks. When it is set to zero, the Cache Segment Size field units shall be interpreted as bytes. DRA (Disable Read Ahead) bit when set to one requests that the Target not read into the buffer any logical block beyond the addressed logical block(s). When it is set at zero, the Target may continue to read logical blocks into the buffer beyond the addressed logical block(s). Number of Cache Segments field is used to select the number of data buffer cache segments. This parameter is valid only when the SIZE bit is set at zero. It is ignored when SIZE is set at one. Cache Segment Size field indicates the requested segment size in Bytes or Blocks, depending upon the value of the LBCSS bit. The Cache Segment Size field is valid only when the SIZE bit is one. It is ignored when SIZE is set at zero. Non Cache Segment Size is not supported and is ignored.

18.53 WRITE (16) - (8A)

Table 177: Write (16) - (8A) Bit Byte (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Tranfer Length (LSB) VU = 0 Reserved = 0 Reserved = 0 FLAG LINK WRPROTECT 1 0
Command Code = 8Ah DPO FUA Rsvd=0 FUA_NV Rsvd=0
The WRITE(16) command causes the drive to write data from the initiator to the media. See the WRITE(10) description for the definitions of the fields in this command.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 226
18.54 WRITE (32) - (7F/0B)
Table 178: Write (32) - (7F/0B) Bit Byte 2-7 8-11 (MSB) 12-19 Logical Block Address (LSB) (MSB) 20-23 Expected Initial Logical Block Reference Tag (LSB) (MSB) 24-25 Expected Logical Block Application Tag (LSB) (MSB) 26-27 Logical Block Application Tag Mask (LSB) (MSB) 28-31 Transfer Length (LSB) WRPROTECT Reserved = 0 VU = 0
Command Code = 7Fh Reserved = 0 Reserved = 0 Group Number = 0 Additional CDB Length = 18h Service Action = 0009h DPO FUA Rsvd=0 FUA_NV Rsvd=0 FLAG LINK
The WRITE command requests that the drive write data transferred from the initiator to disk. Each logical block transferred
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 227
includes user data and may include protection information, based on the WRPROTECT field and the drive format. Each logical block written includes user data and, if the drive is formatted with protection information enabled, protection information. If the RTO_EN bit is set to zero in the READ CAPACITY (16) parameter data, Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code. If RTO_EN is one, this command will be processed normally. See WRITE (10) - (2A) for descriptions of the WRPROTECT, DPO, FUA, Logical Block Address, and Transfer Length fields. When checking of the Logical Block Reference Tag field is enabled, the Expected Initial Logical Block Reference Tag field contains the value of the Logical Block Reference Tag field expected in the protection information of the first logical block accessed by the command, instead of a value based on the LBA. If the ATO bit is set to one in Mode Page 0A and checking of the Logical Block Application Tag field is enabled, the Logical Block Application Tag Mask field contains a value that is a bit mask for enabling the checking of the Logical Block Application Tag field in the protection information for each logical block accessed by the command. A Logical Block Application Tag Mask bit set to one enables the checking of the corresponding bit of the Expected Logical Block Application Tag field with the corresponding bit of the Logical Block Application Tag field in the protection information. If the ATO bit is set to one in Mode Page 0A and the checking of the Logical Block Application Tag field is disabled, or if the ATO bit is set to zero, the Logical Block Application Tag Mask field and the Expected Logical Block Application Tag field are ignored.

18.59.4 Download Microcode and Save (Mode 00101b) -Single Binary File
In this mode the data is transferred to the drive to save into the System reserved area on the disk. This is for functional upgrade and configuration change reflecting the user's requirements and the manufacturers reason or both, and it is stored in the media as a permanent copy. The newly downloaded code becomes effective after the drive issues and completes a self-initiated Power On Reset. Note: It requires up to 30 seconds to update the microcode including the Flash ROM update. Note: New code to be downloaded to the drive will be provided by development either by request of a customer for an additional function or as a result of a functional change by development. However please note that not all possible fixes or new functions can be applied to a drive in this manner and that there is a very high dependency on the level of ROM code contained within the drive. If an invalid code or a code not compatible with the ROM code is downloaded, the drive will usually reject this code and will continue normal operation. However there is a small possibility that an invalid code will be accepted. If this occurs, the unit usually becomes inoperable and will have to be returned to the manufacturer for recovery.
Buffer ID field is used to indicate which portion of the microcode image is being downloaded. To download microcode, the buffer ID should be set to 00h. Other values are reserved for Hitachi development purposes only.
18.59.5 Download Microcode and Save (Mode 00111b) - Multiple Binary Files
In this mode the target receives a segment of the binary microcode file. The Parameter List Length (segment length) of each segment shall be a multiple of 4K bytes. The total length of all segments received shall be equal to the total length of the binary microcode file. All segments must be sent in the proper sequential order.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 236
If an invalid Parameter List Length is specified, Check Condition status is returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. The first segment sent in this mode indicates, by default, the first segment of the binary microcode file. If a Check Condition status is returned in this mode, a Buffer ID == 00h in the subsequent Write Buffer command in this mode indicates the first segment of the binary microcode file. Otherwise the Buffer ID field is ignored. The Buffer Offset field is ignored. After all segments of the binary microcode file have been received, the drive behavior is the same as Download Microcode and Save (Mode 00101b) - Single Binary File.

If SCSI reset or target reset message is received, all contents of segmented buffer is flushed. Even if an error occurs during the Read ahead, the error will not be reported to the Initiator. The data read before the error occurred will be stored as valid data by the Read Ahead function.
20.9 Multiple Initiator Systems
This section describes how the target behaves in a multiple initiator system. Up to 64 initiators may be supported at any one time.

20.9.1 Sense Data

A separate sense data area is reserved for each initiator. Each area is maintained independently. This allows a command from one initiator to complete with a CHECK CONDITION status and generate sense data without being affected by a subsequent command from a different initiator. There is no requirement for the first initiator to send a REQUEST SENSE command to retrieve the Sense Data prior to the execution of a command from a different initiator.

20.9.2 Mode Pages

A single set of Mode pages is maintained. This includes both current and saved parameters. If a MODE SELECT command is executed that updates the current parameters, a unit attention condition is generated for all initiators except the one that issued the command. See 20.1.5, Unit Attention Condition on page 247 for more information.
20.10 Multiple Initiator Environment
20.10.1 Initiator Sense Data
Separate sense data is reserved for each I-T-L. Each sense data is maintained independent of commands from other initiators.
20.10.2 Initiator Mode Select/Mode Sense Parameters
A single shared copy of the Mode Select/Mode Sense parameters is maintained by the drive. This includes both the current and saved parameters.
Hitachi Ultrastar C10K147 (SAS) Hard Disk Drive Specification 261

20.11 Reset

Reset actions will return the drive to a known, initialized state. This device supports the Hard reset option as defined in the SCSI standards (see 7.1.9 Dev_Ctrl_Code_x on page 33) and the reset sources discussed below.

20.11.1 Reset Sources

There are four sources of resets detected by the target: Reset Name Power-On Reset Self-Initiated reset Reset Source This is the signal generated by the hardware at initial power-on This is a software-generated reset that occurs when a catastrophic error is detected by the microcode. This is the Hard Reset performed during a Link Reset Sequence. This is a LUN RESET TMF (08h) sent in a TASK IU.

Hard Reset LUN Reset

20.11.2 Reset Actions
The action taken by the drive following a reset is dependent on the source of the reset.
20.11.2.1 Power-On reset and Self-Initiated reset
These two reset conditions cause the following to be performed in the order shown: A power-up sequence

Internal Target Failure F123 Invalid request to enter sleep mode F128 DRAM test in progress F129 DRAM test complete F12A DRAM test error F132 GEM FH track read error 1201 Error in UEC class 1202 Error in UEC cause 1301 Motor: Recovered internal error 1303 Motor: Recovered Open Loop Commutation failure 1305 Motor: Recovered No feedback detected 1307 Motor: Recovered Settle timeout 1309 Motor: Recovered Gross speed error 130B Motor: Recovered 12V OK error
Hitachi Ultrastar C10K147 SAS Hard Disk Drive Specification 285
130D Motor: Recovered Speed error 1311 Motor: Recovered Internal 12V not OK timeout 1313 Motor: Recovered Iductive Sense measurement timeout 1315 Motor: Recovered Spin Sense speed error 1319 Motor: Recovered Target speed error 131B Motor: Recovered Power driver version error 131D Motor: Recovered Over current error 1321 Motor: Recovered Negative regulator fault 1323 Motor: Recovered Module overtemp error 1325 Motor: Recovered 12V or 5V OK error 1327 Motor: Recovered unknown error 1401 Servo: Recovered Requested rezero head does not exist 1403 Servo: Recovered Back EMF movement in progress 1405 Servo: Recovered Back EMF timeout error 1407 Servo: Recovered ADC conversion timeout 1409 Servo: Recovered Load/unload calibration error 140B Servo: Recovered Invalid 5 volts 140D Servo: Recovered Invalid 12 volts 140F Servo: Recovered Invalid harmonic requested 1411 Servo: Recovered Gain BEMF Calibration error 1413 Servo: Recovered VOFF BEMF calibration error 1415 Servo: Recovered Invalid temperature 1417 Servo: Recovered Truncated rezero 1419 Servo: Recovered Heads not loaded 1425 Servo: Recovered KT Seek out of range 1427 Servo: Recovered DAC Offset calibration error 1429 Servo: Recovered Load speed error 142D Servo: Recovered ADC Calibration error 142F Servo: Recovered ADC Offset error 1431 Servo: Recovered ADC Limit error 1433 Servo: Recovered Balancer Resistance error 1435 Servo: Recovered Balancer Resistance Limit error 1437 Servo: Recovered First Cylinder error 1439 Servo: Recovered Valid Cylinder error 143B Servo: Recovered ADC Saturation error 143D Servo: Recovered Latch Break timeout 143F Servo: Recovered MR Resistance out of range error 1441 Servo: Recovered VCM Retract error 1443 Servo: Recovered Load Retry error 1445 Servo: Recovered DFT Sharp error
Hitachi Ultrastar C10K147 SAS Hard Disk Drive Specification 286
1447 Servo: Recovered Load/Unload state error 1606 Recovered data with PPM or precomp load 1608 Recovered data with TA (Thermal Asperity) detection 160A Recovered data with SMM or VM or DDF 160C Recovered data with pre-PPM or FH (Fly Height) detection 160E Recovered data with write or pre-TA detection 1610 Recovered data with pre-SMM or VM or STM or DDF 1612 Recovered data with NRZ parity error 1614 Recovered parity PP correction or STW 1616 Recovered channel error 1618 Recovered AE thermal asperity 161A Recovered AE open MR element error 161C Recovered AE IC over temperature error 161E Recovered AE IP clock count error 1620 Recovered AE write data BLS error 1624 Recovered AE invalid head address error 1626 Recovered AE power supply error 162A Recovered AE write transition error 162C Recovered AE no write head current error 162E Recovered Channel Pre-TA error 1630 Recovered Channel write or NRZ parity error 1632 Recovered Channel write synth unlock error 1634 Recovered AE Short write read head error 1636 Recovered AE Short write head error 1638 Recovered AE Non-selected write head error 163C Recovered AE IH open short error 163E Recovered AE IH delay error 1640 Recovered Channel coarse tune timeout error 1642 Recovered AE Readback error 1712 Recovered ECC error 1716 Recovered overrun 171A Recovered ECC overrun 171C Recovered DRAM CRC error 171E Recovered ID Parity error 1731 Recovered write fault 1759 Unknown recovered error 1792 Recovered Current pointer error 1798 Recovered ID not found error 179C Recovered Channel write or NRZ parity error 17B4 Recovered Shock sensor error