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.
Version: 1.8
April 14, 2016
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
Page 2
1st Edition(Rev 1.8) (14 April 2016)
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with
local law: HGST, A WESTERN DIGITAL COMPANY, PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRAN TIES 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. HGST 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, HGST 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 HGST intends to announce such HGST products, programming, or services in your country.
T echnical information about this product is available by contacting your local HGST representative or on the Internet at http://
www.hgst.com
HGST 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.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
Page 17
1.0 General
1.1 Introduction
This document describes the specifications of the following HGST 3.5 inch SAS drives.
Table 1: Product ID table
Drive NameModel NameType Capacity Encryption
Enabled
Ultrastar 7K4000-4000HUS724040ALS640
Ultrastar 7K4000-4000HUS724040ALS641
Ultrastar 7K4000-3000HUS724030ALS640
Ultrastar 7K4000-3000HUS724030ALS641
Ultrastar 7K4000-2000HUS724020ALS640
Ultrastar 7K4000-2000HUS724020ALS641
Note: The specifications in this document are subject to change without notice.
For technical and ordering information, please visit our website at http://www.hgst.com.
DK7SSD400
DK7SSD400
DK7SSD300
DK7SSD300
DK7SSD200
DK7SSD200
4TB No
4TB Yes
3TB No
3TB Yes
2TB No
2TBYes
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
1
Page 18
1.2 Glossary
WordMeaning
ESDElectrostatic Discharge
Kbpi1,000 bits per inch
Ktpi1,000 tracks per inch
Gbps1,000,000,000 bits per second
Mbps 1,000,000 bits per second
MB/s1,000,000 bytes per second
TB 1,000,000,000,000 bytes (for Drive Capacity)
GB 1,000,000,000 bytes (for Drive Capacity)
MB 1,048,576 bytes (for Memory Size)
KB 1,024 bytes (for Memory Size)
S.M.A.R.T. Self-Monitoring Analysis and Reporting Technology
DFTDrive Fitness Test
ADMAutomatic Drive Maintenance
1.3 Caution
The drive can be damaged by shock or ESD (Electrostatic Discharge). Any damage sustained by the drive after removal from
the shipping package and opening the ESD protective bag are the responsibility of the user.
1.4 References
• SAS Compliance
–"Serial Attached SCSI - 2 (SAS-2)"
• SAS Protocol
–This drive supports Serial SCSI Protocol (SSP).
–STP (Tunneled SATA) and SMP (Management protocol) protocols are NOT supported.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
2
Page 19
2.0 Outline of the Drive
• Data capacities of 4TB/3TB/2TB
• Spindle speeds of 7200 RPM
• Fluid Dynamic Bearing motor
• Dual Stage Actuator
• SAS Interface 6/3/1.5Gbps
• Supports dual-ported operations
• Supports full duplex operations
• Variable sector size (512 - 528 bytes in multiples of eight)
• Closed-loop actuator servo
• Load/Unload mechanism, non head disk contact start/stop
• Automatic Actuator lock
• Seek time of 8.2 ms typical (without Command Overhead
• Sector Buffer size of 64MB
(Upper 15MB is used for firmware, this is typical value, it depends on firmware revision)
• Write Cache
• Back to back write
• On The Fly Data correction
• Automatic defect reallocation
• Self diagnostics at power on
• Power saving modes (T10)
• S.M.A.R.T. (Self Monitoring and Analysis Reporting Technology)
• 64 bit addressing feature
• Adaptive zone formatting
• RVS (Rotational Vibration Safeguard)
• SAS-2 compliant
• ANSI T10 Protection Information (End-to-End)
• Support TCG Enterprise_A SSC Encryption (specific model only)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
3
Page 20
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
4
Page 21
3.0 Fixed-disk Subsystem Description
3.1 Control Electronics
The drive is electronically controlled by a microprocessor, several logic modules, digital/analog modules, and various drivers
and receivers. The control electronics performs the following major functions:
•Controls and interprets all interface signals between the host controller and the drive.
•Controls read write accessing of the disk media, including defect management and error recovery.
•Controls starting, stopping, and monitoring of the spindle.
•Conducts a power-up sequence and calibrates the servo.
•Analyzes servo signals to provide closed loop control. These include position error signal and estimated velocity.
•Monitors the actuator position and determines the target track for a seek operation.
•Controls the voice coil motor driver to align the actuator in a desired position.
•Constantly monitors error conditions of the servo and takes correspon ding action if an error occurs.
•Monitors various timers such as head settle and servo failure.
•Performs self-checkout (diagnostics).
3.2 Head Disk Assembly
The head/disk assembly (HDA) is assembled in a clean room environment and contains disks, a spindle motor, actuator assembly, and voice coil motor. Air is constantly circulated and filtered when the drive is operational. Venting of the HDA is accomplished via a breather filter.
The spindle is driven directly by a brushless, sensorless DC drive moto r. Dynamic braking is used to stop the spindle quickly.
3.3 Actuator
The read/write heads are mounted in the actuator. The actuator is a swing-arm assembly driven by a voice coil motor. A
closed-loop positioning servo controls the movement of the actuator. An embedded servo pattern supplies feedback to the
positioning servo to keep the read/write heads centered over the desired track.
The actuator assembly is balanced to allow vertical or horizontal mounting without adjustment.
When the drive is powered off, the actuator automatically moves the head to the actuator ramp outside of the disk where it
parks.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
5
Page 22
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
6
Page 23
4.0 Drive Characteristics
4.1 Formatted Capacity
Table 2: Formatted Capacity
Description2TB model3TB model4TB model
Physical Layout
Label capacity 2TB3TB4TB
Bytes per Sector512512512
Number of Heads6810
Number of Disks445
Number of Cylinders262,604262,604262,604
Number of Sectors3,907,029,1685,860,533,1687,814,037,168
Total Logical Data Bytes2,000,398,934,0163,000,592,982,0164,000,787,030,016
4.2 Data Sheet
Table 3: Data Sheet
Description2TB3TB4TB
ModelModelModel
Max Data transfer rate (Mbps)182818281828
Interface transfer rate (MB/s)600
1
Data buffer size
Rotational speed (RPM)7,200
Number of buffer segments 1-254
Recording density- max (Kbpi)167716771677
Track density (Ktpi)311311311
Areal density - max (Gbits/in
Number of data bands40
(MB)
2
)
522522522
64
1
Upper 15MB are used for firmware, this is a typical value, it depends on firmware revision
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
7
Page 24
4.3 Inquiry Information
4.3.1 Product ID
Product ID in Section 18.5.1, “Inquiry Data” on page 79, is as follows:
Table 4: Product ID in Inquiry Command
Product IDDescription
HUS724040ALS6404 TB, SAS
HUS724040ALS6414 TB, SAS
HUS723030ALS6403 TB, SAS
HUS723030ALS6413 TB, SAS
HUS723020ALS6402 TB, SAS
HUS723020ALS6412 TB, SAS
4.3.2 World Wide ID - Block Assignment
Block Assignment of World Wide ID is as follows:
Table 5: Block assignment of World Wide ID in INQUIRY Command
Manufacturing SiteProductBlock Assignment
Thailand
HU S 7 2 303 0 A LS 6 4 0 (YH S e r i al N u m be r 3 T B)
HUS723030ALS641 – Common SATA/ SAS S/N’s
HUS723030ALS640
HUS723030ALS641
Thailand
HU S 7 2 302 0 A LS 6 4 0 (YH S e r i al N u m be r 2 T B)
HUS723020ALS641 – Common SATA/ SAS S/N’s
HUS723020ALS640
HUS723020ALS641
Thailand
HUS723020ALS640 (YH Serial Number 2TB 7 dn)
HUS723020ALS641 – Common SATA/ SAS S/N’s
HUS723020ALS640
HUS723020ALS641
Note (1) - Additional block assignment wi ll be issued as needed based on actual production vol um e .
01Ah
01Bh
01Ch
(1)
(1)
(1)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
8
Page 25
4.4 Performance characteristics
Drive performance is characterized by the following parameters:
•Command overhead
•Mechanical head positioning
- Seek time
- Latency
•Data transfer speed
•Buffering operation (read ahead/write cache)
Note: All the above parameters contribute to drive performance. There are other parameters that contribute to the performance of the actual system. This specification tries to define the bare drive characteristics, not system throughput, which
depends on the system and the application.
4.4.1 Mechanical positioning
4.4.1.1 Average seek time (without command overhead, including settling)
Table 6: Mechanical positioning performance
Command Type Typical (ms)Max (ms)
Read8.210.2
Write8.210.2
The terms “Typical” and “Max” are used throughout this specification with the following meanings:
Typical . The average of the drive population tested at nominal environmental and voltage conditions.
Max. The maximum value measured on any one drive over the full range of the environmental and voltage
conditions. (See Section 6.2, “Environment” and Section 6.3, “DC Power Requirements”)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
9
Page 26
4.4.1.2 Full stroke seek time
Table 7: Full stroke seek time
FunctionTypical (ms)MAx (ms)
Read14.524.0
Write14.524.0
4.4.1.3 Average latency
Table 8: Latency time
RotationTime for a revolution (ms)Average latency (ms)
7200 RPM8.334.16
4.4.2 Drive ready time
Table 9: Drive ready time
ModelTypical (sec)Maximum (sec)
4TB22.630
3TB18.730
2TB17.430
ReadyThe condition in which the drive is able to perform a media access command (such as read, write)
immediately.
Power on This includes the time required for the internal self diagnostics.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
10
Page 27
4.4.3 Data transfer speed:
Table 10: Data transfer speed (sector size 512 Byte case)
Instantaneous0203203
Measured typical values for
sustained disk-buffer transfer rate0183183
Instantaneous39103103
Measured typical values for
sustained disk-buffer transfer rate399494
Notes:
•Instantaneous disk-buffer transfer rate is derived by: (Number of sectors on a track) x 512 x (revolutions/sec)
•For this table, '1 MB / Sec' should be interpreted as 1,000,000 bytes per Second.
•The number of sectors per track varies in each zone (radius) as a result of constant linear density recording.
•Sustained disk-buffer transfer rate is the average rate measured while transferring multiple cylinders of data. It differs
from the instantaneous transfer rate because of the time required to change tracks (Track skew and Head skew). In
addition, time is added for the occasional missed track switch.
This hard disk drive has a buffer for read ahead see 20.8, “Segmented Caching” on page 295.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
11
Page 28
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
12
Page 29
5.0 Data Integrity
The drive retains recorded information under all non-write operations.
No more than one sector can be lost by power down during a write operation while write cache is disabled. If power down
occurs before completion of a data transfer from write cache to disk while write cache is enabled, the data remaining in the
write cache will be lost. To prevent this data loss at power off, the following action is recommended:
•Confirm successful completion of a SYNCHRONIZE CACHE (35h) command
5.1 Equipment Status
Equipment status is available to the host system any time the drive is not ready to READ, WRITE or SEEK. This status normally exists at power-on time and will be maintained until the following conditions are satisfied:
•Access recalibration/tuning is complete
•Spindle speed meets requirements for reliable operations
•Self-check of drive is complete
Appropriate error status is made available to the host system if any of the following conditions occur after the drive has
become ready:
•Spindle speed goes outside of requirements for reliable operation
•“Write fault” is detected
5.2 Error Recovery Procedure
Errors occurring with the drive are handled by the error recovery procedure.
Errors that are uncorrectable after application of the error recovery procedures are reported to the host system as non-recover-
able errors.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
13
Page 30
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
14
Page 31
6.0 Physical Format
Media defects are remapped to the next available sector during the Format Process in manufacturing. The mapping from Logical Block Address (LBA) to the physical Block locations is calculated using internally maintained tables.
6.1 Shipped Format (P-List)
•Data areas are optimally used.
•All pushes generated by defects are absorbed by available tracks of the inner notch.
P-List Physical Format
Note: Defects are skipped without any constraint, such as track or cylinder boundary. The calculation from LBA to physical
is done automatically by internal table.
6.2 Reassigned Format (G-List)
•G-List has a capacity of 22,000 Customer LBAs
•Multiple reassignments of the same Customer LBA increase the number of G-List entries.
•A track for spare sectors is inserted after every 800 nominal customer tracks.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
15
Page 32
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
16
Page 33
7.0 Electrical Interface
7.1 SAS Connector
The drive uses the standard 29 pin Serial Attached SCSI (SAS) connector which conforms to the mechanical requirements of
SFF 8482. The connector is expected to be used in an environment which uses a common connector structure for racking disk
drives in a cabinet. The connector allows for plugging a drive directly into a backplane by providing the necessary electrical
connection. Mechanical stability and device retention must be provided by a mechanism outside the drive.
7.1.1 29 pin Serial Attached SCSI (SAS) Connector Definition
Diagram of top and bottom of connector showing pinouts.
Table 11: 29-pin Connector Signal Definition
Pin NumberSignalDescription
S1GNDGND for SAS Primary Port
S2RP+SAS Primary Port Receive
(positive) signal
S3RP-SAS Primary Port Receive
(negative) signal
S4GNDGND for SAS Primary Port
S5TP-SAS Primary Port Transmit
(negative) signal
S6TP+SAS Primary Port Transmit
(positive) signal
S7GNDGND for SAS Primary Port
S8GNDGND for SAS Secondary
Port
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
17
Page 34
Pin NumberSignalDescription
S9RS+SAS Secondary Port Receive
(Positive) signal
S10RS-SAS Secondary Port
S11GNDGND for SAS Secondary
S12TS-SAS Secondary Port
S13TS+SAS Secondary Port
S14GNDGND for SAS Secondary
P1+3.3VNOT USED (Pins P1-P3
P2+3.3VNOT USED (Pins P1-P3
P3+3.3VNOT USED (Pins P1-P3
P4GNDGROUND
P5GNDGROUND
P6GNDGROUND
P7+5V-ChargePre-charge pin for +5V
Receive (negative) signal
Port
Receive (negative) signal
Receive (positive) signal
Port
tied internally)
tied internally)
tied internally)
P8+5V+5V power supply input
P9+5V+5V power supply input
P10GNDGROUND
P11READY LEDREADY LED output
P12GNDGROUND
P13+12V=ChargePre-charge pin for +12V
P14+12V+12V power supply input
P15+12V+12V power supply input
7.1.2 Voltage and Ground Signals
The 12V and 5V contacts provide all of the voltages required by the drive. The two voltages share a common ground plane to
which all of the ground contacts are connected.
7.1.3 Ready LED output
The drive provides an open-drain driver with 15mA of current sink capability to the Ready LED Output signal. The
cathode of the LED should be connected to this signal. The LED and the current-limiting resistor must be provided by the
enclosure
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
18
Page 35
8.0 Environment
8.1 Temperature and humidity
Table 12: Operating and non-operating conditions
Operating conditions
Ambient Temperature5°C to 60ºC
Relative humidity5 to 90%, non-condensing
Maximum wet bulb temperature29.4ºC, non-condensing
Maximum surface temperature gradient20ºC/hour
Altitude-305 to 3,048 m
Shipping conditions
Ambient Temperature-40°C to 70ºC
Relative humidity5 to 95%, non-condensing
Maximum wet bulb temperature35ºC, non-con densing
Maximum surface temperature gradient30ºC/hour
Altitude-305 to 12,192 m
Storage conditions
Ambient Temperature-40°C to 70ºC
Relative humidity5 to 90%, non-condensing
Maximum wet bulb temperature35ºC, non-con densing
Altitude-305 to 12,192 m
Environments that contain elevated levels of corrosives (e.g. hydrogen sulfide, sulfur oxides, or hydrochloric acid) should be
avoided. Care must be taken to avoid using any compound/material in a way that creates an elevated level of corrosive materials in the atmosphere surrounding the disk drive. Care must also be taken to avoid use of any organometallic (e.g. organosilicon or organotin) compound/material in a way that creates elevated va por levels of th ese compounds/materials in the
atmosphere surrounding the disk drive.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
19
Page 36
8.2 Storage requirements
8.2.1 Packaging
The drive or option kit must be heat-sealed in a moisture barrier bag with desiccant inside the bag supplied by HGST, a Western Digital Company.
8.2.2 Storage time
The drive may not remain inoperative for a period of more than one year. During this time, the maximum time the drive may
be stored after the bag is opened is six months.
8.3 Corrosion test
The hard disk drive shows no signs of corrosion inside or outside of the hard disk assembly and remains functional after
being exposed to a temperature of 50ºC and relative humidity of 90% for seven days
8.4 Cooling requirements
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
20
Page 37
Drive component surface temperatures must remain within the limits specified in the following table. The drive may require
forced air cooling to meet specified operating temperatures.
Table 13: Maximum allowable surface temperatures
Module nameLocationMaximum allowable surface temperature
HDD base castingas noted in picture60ºC
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
21
Page 38
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
22
Page 39
9.0 DC Power Requirements
The following voltage specification applies at the drive power connector. Connections to the drive should be made in a safety
extra low voltage (SELV) circuit. There is no power on or power off sequencing requirement.
Adequate secondary over-current protection is the responsibility of the system.
Note: -8% is acceptable during spin up, but the spin up time is not guaranteed.
Absolute Max
Spike Voltage
Supply Rise TimeCapacitance
9.1 Power Supply Current, Average and Peak
The following current and power requirements are typical when operating under the following conditions: Nominal 5 and 12V,
Background Media Scan (BMS) disabled for Idle, Write Caching disabled and the drive reporting a temperature of 40C.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
23
Page 40
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
24
Page 41
9.2 Ripple Voltage
Table 15: Power Supply Generated Ripple at Drive Power Connector
Maximum (mV pp)MHz
+5 V DC250 0-10
+12 V DC2500-10
During drive start up and seek, 12 volt ripple is generated by the drive (referred to as dynamic loading). If the power of several
drives is daisy chained, the power supply ripple plus other drive dynamic loading must remain within the regulation tolerance
of +5%. A common supply with separate power leads to each drive is a more desirable method of power distribution.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
25
Page 42
To prevent external electrical noise from interfering with the drive's performance, the drive must be held by four screws in a
user system frame that has no electrical level difference at the four screw positions. The drive enclosure must not be used in
the current return path of the drive power supply. The maximum common-mode noise current passing through the drive must
not exceed 20 mA.
9.3 Power Consumption Efficiency Index
Table 16: Power Consumption Efficiency Index
Model4 TB Model3 TB Model2 TB Model
Power Consumption Efficiency Index -Idle Mode (W/GB)0.00190.00220.0033
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
26
Page 43
10.0 Reliability
10.1 Start/Stop Cycles
The drive is designed to withstand a minimum of 50,000 start/stop cycles at ambient environment.
The drive is designed to withstand a minimum of 10,000 start/stop cycles at the operating environment conditions specified in
Chapter 8.0, “Environment” on page 19.
10.2 Load/Unload Cycles
The drive is designed to withstand a minimum of 600,000 load/unload cycles at the operating environmental conditions specified in Chapter 8.0, “Environment” on page 19
10.3 Data Reliability
•The probability of an uncorrectable data error is 1 in 1x1015 bits read.
•The channel design is changed from the prior generation of DASD devices to use an LDPC channel having similar code
rate to prior Reed Solomon error correction. The design of the LDPC channel includes usage of media defect detection circuits for locating defects and performing erasure correction, replacing the offline erasure correction capability
of RS codes. Modulation coding properties for timing and gain recovery are equivalent to prior product generation
•LDPC implementation:
•Single LDPC codeword per sector with 576 bits of parity
•Media defect detection circuit using erasure flags to zero LLR values
•LDPC code designed to correct defects up to 425 bits
•LBA seeded 80 bit CRC for miscorrect detection
10.4 Seek errors
A non-recoverable seek/ID miscompare error is defined as a seek operation that cannot be recovered by the error recovery procedure of the drive. The drive reports sense key 04 and sense code 02 for this error.
No drive has more than one non-recoverable seek/ID miscompare error per 100 million seek operations (1 in 1x 10
operated at the full range of voltage and environmental conditions.
8
) when
10.5 Failure prediction (S.M.A.R.T)
A recoverable equipment error is an error other than a seek/ID miscompare error or read error that is detected and corrected by
the drive error recovery procedure. Examples are Write Fault, Drive Not Ready and internal drive errors.
SMART Monitoring Parameters are checked to determine if the (Read/Write/Seek) error rates exceed the drive’s threshold
value when an error occurs and a minimum amount of operation has been completed. A check is also performed for a minimum level of Spare Sector Availability.
The Head Load / Unload Count, Spin Up Time and Spin Up Retry Count parameters are checked prior to reporting a “Ready”
condition at Power On.
Non-recoverable equipment errors indicate a defective drive.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
27
Page 44
10.6 MTBF (Mean Time Between Failure): 2.0 M hours.
This MTBF target is based on a sample population and is estimated by statistical measurements and acceleration algorithms
under nominal operating conditions. MTBF ratings are not intended to predict an individual drive’s reliability. MTBF does not
constitute a warranty.
10.7 Preventive Maintenance
None.
10.8 Temperature Warning
Temperature Warning is enabled by setting the EWASC (Enable Warning Additional Sense Code) bit to 1 and setting DEXCPT (Disable Exception Control) bit to 0 in Mode Page 1C. For mode page settings, refer to Section 18.10.14, “.Mode Page
1C (Informational Exceptions Control)” on page 173. The warning is issued as sense data (Sense Key 01h , Code 0Bh, Qual
01h).
The drive temperature is reported in Log Sense page 2F. Refer to Section 18.7.12, “Log Sense Page 18” on page 121.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
28
Page 45
11.0 Mechanical Specifications
11.1 Outline
S
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
29
Page 46
11.2 Mechanical Dimensions
The drive complies with SFF-8301.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
30
Page 47
Table 17: Physical Dimensions
Height [mm]26.1 MAX
Width [mm]101.6 ± 0.25
Length [mm]147 MAX
Weight [grams - maximum]2 TB Model 673 grams
3 TB Model 673 grams
4 TB Model 696 grams
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
31
Page 48
11.3 Interface Connector
11.4 Mounting Positions and Tappings
The mounting hole location and size for the hard disk drive is shown below.
Thread(1)(2)(3)(4)(5)(6)(7)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
The drive will operate in all axes (6 directions). Performance and error rate will stay within specification limits if the driv e is
operated in the other orientations from which it was formatted.
The recommended mounting screw torque is 0.6 - 1.0 Nm (6 - 10 kgf-cm). The recommended mounting screw depth is 4 mm
maximum for bottom and 4.5 mm maximum for horizontal mounting .
T o avoid performance degradation, mount the drive in the system securely enough to prevent excessive motion or vibration of
the drive at seek operation or spindle rotation, using appropriate screws or equivalent mounting hardware. Consult with the
issuer of this specification for actual application if necessary.
Drive level vibration tests and shock tests are to be conducted with the drive mounted to a table using the bottom four screws.
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.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
33
Page 50
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
34
Page 51
12.0 Vibration and Shock
All vibration and shock measurements recorded in this section are made with a drive that has no mounting attachments for the
systems. The input power for the measurements is applied to the normal drive mounting points.
12.1 Operating vibration
12.1.1 Random vibration (Linear)
The test is 30 minutes of random vibration using the power spectral density (PSD) levels shown below in each of three mutually
perpendicular axes. The disk drive will operate without non-recoverable errors when subjected to the below random vibration
levels.
Table 18: Random vibration PSD profile break points (operating)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
35
Page 52
12.2 Nonoperating vibration
The drive does not sustain permanent damage or loss of previously recorded data after being subjected to the environment described below
12.2.1 Random vibration
The test consists of a random vibration applied for each of three mutually perpendicular axes with the time duration of 10 minutes per axis. The PSD levels for the test simulate the shipping and relocation environment shown below. The overall RMS
(Root Mean Square) level of vibration is 10.2 m/sec
Table 20: Random vibration PSD profile break points (non operating)
Frequency2 Hz4 Hz8 Hz40 Hz55 Hz70 Hz200 Hz
[(m/sec2)2/Hz]0.0962.892.890.2890.9620.9620.096
12.2.2 Swept sine vibration
• 19.6 m/sec2 (2 G) (Zero to peak), 5 to 500 to 5 Hz sine wave
• 0.5 oct/min sweep rate
• 3 minutes dwell at two major resonances
2
(1.04 G).
12.3 Operating shock
The drive meets the following criteria while operating in the conditions described below. The shock test consists of 10 shock
inputs in each axis and direction for total of 60. There must be a delay between shock pulses long enough to allow the drive to
complete all necessary error recovery procedures.
• No error occurs with a 98.1 m/sec
• No data loss occurs with a 294 m/sec
• No data loss occurs with a 686 m/sec
2
(10 G) half-sine shock pulse of 11 ms duration
2
(30 G) half-sine shock pulse of 4 ms duration.
2
(70 G) half-sine shock pulse of 2 ms duration.
12.4 Nonoperating shock
The drive will operate without non-recoverable errors after being subjected to shock pulses with the followin g characteristics.
12.4.1 Trapezoidal shock wave
•Approximate square (trapezoidal) pulse shape
•Approximate rise and fall time of pulse is1 ms
•Average acceleration level is 490 m/sec
rise time and before the 1 ms fall with a time "duration of 11 ms")
•Minimum velocity change is 4.23 m/sec
2
(50 G). (Average response curve value during the time following the 1 ms
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
36
Page 53
12.4.2 Sinusoidal shock wave
The shape is approximately half-sine pulse. The figure below shows the maximum acceleration level and duration.
Table 21: Sinusoidal shock wave
Acceleration level (m/sec2)Duration (ms)
2940 (300G)1
1470 (150G)
11
12.5 Nonoperating Rotational shock
All shock inputs shall be applied around the actuator pivot axis.
Table 22: Sinusoidal shock wave
DurationRad/Sec
1 ms30,000
2 ms
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.
2
20,000
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
37
Page 54
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
38
Page 55
13.0 Acoustics
The upper limit criteria of the octave sound power levels are given in Bels relative to one picowatt and are shown in the following table. The sound power emission levels are measured in accordance with ISO 7779.
Table 23:
Idle2.9 / 3.4
Operating Seek Mode3.6 / 4.0
Mode definition:
Sound power levels
Mode7200rpm (Typical / Max)
Idle mode. The drive is powered on, disks spinning, track following, unit ready to receive and respond to interface
commands.
Operating mode. Continuous random cylinder selection and seek operation of the actuator with a dwell time at each
cylinder. The seek rate for the drive is to be calculated as shown below:
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
39
Page 56
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
40
Page 57
14.0 Identification
14.1 Labels
The following labels are affixed to every hard disk drive shipped from the drive manufacturing location in accordance with
appropriate hard disk drive assembly drawing:
•A label containing the HGST logo, HGST part number and the statement “Made by HGST,” or HGST approved
equivalent.
•A label containing drive model number, manufacturing date, formatted capacity, country of origin or HGST approved
equivalent and UL, C-UL, TUV, CE, MIC, BSMI,CTICK, RoHS and Recycle logos.
•A bar code label containing the drive serial number.
•A user designed label, per agreement
•Interface definition mark, SAS-2 Model
The labels may be integrated with other labels.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
41
Page 58
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
42
Page 59
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
CISPR22Class B
AS/NZS CISPR22Class B
CNS13438 (Taiwan)Class B
EN 55022: 2006 + A1:2007Class B
FCC Title47 Part 15 (USA)Class B
GB9254 (China)Class B
ICES-003, Issue 4Class B
VCCI (Japan)Class B
ITE Immunity
EN 55024: 1998 +A1:2001 +A2:2003
Power Line Harmonics
EN 61000-3-2:2006+A1:2009+A2:2009
GB17625.1 (China)
Voltage Fluctuations and Flicker
EN 61000-3-3:2008
GB17625.2 (China)
15.1 Class B Regulatory Notices
European Union
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of
the laws of the Member States relating to electromagnetic compatibility. HGST 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-HGST option cards.
This product has been tested and found to comply with the limits for Class B Information Technology Equipment according to
European Standard EN 55022. The limits for Class B equipment were derived for typical residential environments to provide
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
43
Page 60
reasonable protection against interference with licensed communication devices.
Canada
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
Germany
Deutschsprachiger EU Hinweis:
Hinweis für Geräte der Klasse B EU-Richtlinie zur Elektromagnetischen Verträglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 89/336/EWG zur Angleichung der Rechtsvorschriften über die elektromagnetische V erträglichkeit in den EU-Mitgliedsstaaten. und hält die Grenzwerte der EN 55022 Klasse B ein. Um dieses sicherzustellen, sind
die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der HGST
empfohlene Kabel angeschlossen werden. HGST übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der HGST verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern
ohne Empfehlung der HGST gesteckt/eingebaut werden.
Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem "Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG)". Dies ist die
Umsetzung der EU-Richtlinie 89/336/EWG in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagneti-sche Verträglichkeit von Geräten (EMVG) vom
18. September 1998 (bzw. der EMC EG Richtlinie 89/336) für Geräte der Klasse B Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen. Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die HGST, a Western Digital Company, 3403 Yerba Buena Road
San Jose, CA 95135. Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse B.
Korea (MIC)
Taiwan (BSMI)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
44
Page 61
16.0 Safety Standards
The following shows the safety standards for different countries.
16.1 UL and C-UL Standard Conformity
This drive is used as a component in Information Technology Equipment (ITE) business equipment systems. This drive is
certified for use in the United States per UL 60950-1, Second Edition, A1:2011-12-19 and in Canada per
CSA C22.2 No. 60950-1-07 Second Edition, 2011-12. The cRUus UL component recognition mark is specifically used on
component parts that are part of a larger product or system and indicates compliance with both Canadian and U.S. requirements. The recognition mark appears on the drive label and is maintained for the life of the product.
16.2 European Standards Compliance
The product is additionally certified to the following standard:
International Electrotechnical Commission (IEC) Safety Standard:
IEC 60950-1:2005 Second Edition + A1:2009
16.3 German Safety Mark
This product has received the TUV Bauart Certification mark under EN 60950-1:2006 + A11:2009 + A1:2010 + A12:2011
safety standard. The GS mark is not applicable to internal subsystem drives.
16.4 Flammability
The printed wiring boards, flex cables, and connectors used in this drive meet or exceed the UL minimum flammability classifications listed in the table below.
The flammability rating is marked or etched on the board.
ComponentFlammability Rating
Rigid Printed Wiring Board Min. V-1
Flex Cable - no components Min. V-2
Flex Cable with components Min. V-1
Interface & motor connectors Min. V-2
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
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
45
Page 62
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
46
Page 63
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 relevant to this product.
•SCSI Application Layer - Clause 10
•SSP Transport Layer (
•SAS Port Layer - Clause 8
•SSP Link Layer - Clause 7
•SAS PHY Layer - Clause 6
•SAS Physical Layer - Clause 5
All layers are defined in the following ANSI standard.
•"Serial Attached SCSI - 2 (SAS-2)"
In addition, this drive claims compliance with the following ANSI standards.
•SCSI Architecture Model (SAM-3)
•SCSI Block Commands (SBC2)
Serial SCSI Protocol) - Clause 9
17.2 SAS Features
The following SAS features are supported by the Drive.
• SAS Compliance
- "Serial Attached SCSI - 2 (SAS-2)"
• SAS Protocol
- This drive supports
Serial SCSI Protocol (SSP).
- STP (Tunneled SATA) and SMP (Management protocol) protocols are
NOT supported.
• SAS Dual Ported Operation
- single PHY ports (i.e. Narrow port. Wide Port NOT supported)
- ports function independently with separate firmware controls
- Multiple DMA engines capable of accessing either port
- full duplex and dual port DMA data/data operations
- Maximum outstanding credit of four per port
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
- Largely Automated OOB and speed negotiation sequences
- Optional Support for the hot-plug timeout in hardware
• Partial support for Disconnect/Reconnect Mode Page (0x02)
- Maximum Connect Time Limit - SUPPORTED
- Bus Inactivity Time Limit - NOT SUPPORTED
- Maximum Burst Size - SUPPORTED
- First Burst Size - NOT SUPPORTED
•Others...
- Connection Rate Matching
- Hard Reset primitive sequence detection and validation in hardware
- Support for NOTIFY (Enable Spin-up) and NOTIFY (Power Loss Expected)
- Hashed WWN validation in hardware
- extended CDB support
17.3 SAS Names and Identifiers
In SAS, device and port names are worldwide unique names within a transport protocol. Port identifiers are the values by
which ports are identified within a domain, and are used as SAS addresses. Phy identifiers are unique within a device.
Table 24: Names and identifiers
ObjectSAS Implementation
Port IdentifierSAS address
Port NameNot defined
Device NameSAS address
Phy IdentifierPhy identifier
Where the SAS Address format is defined by ANSI as follows:
Byte/Bit76543210
0NAA (5h)(MSB)
1IEEE Company ID
2
3(LSB) (MSB)
4
5
6
Vendor Specific Identifier
7
(LSB)
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
48
Page 65
The SAS Device Name is a unique SAS address world wide name. This device name is reported through the SCSI Vital Products Data.
Each of the two SAS ports also has a unique SAS address world wide name. These port identifiers are reported in the IDENTIFY Address frame and are used as source and destination addresses in the OPEN address frame. They are also reported
through the SCSI Vital Products Data.
Since this drive is one device with two ports it has three SAS addresses. All SAS Addresses are in 64-bit IEEE Registered
Name format, as illustrated in Table 25.
Table 25: IEEE Registered Name format
Bit
63-60 59-3635-2423-21-0
0101OUI in Canonical FormBlock AssignmentS/NObject
The Name Address Authority field (5h) specifies the format used for the rest of the name as follows:
FieldDescription
OUIOrganizationally Unique Identifier (24 bits). Canonical form means that each
byte is stored in “bit reversed” order.
Block AssignmentBlock assignment within HGST, a Western Digital Company
ObjectDevice Name/Port Identifier
00bLogical Unit Name
01bPort 1
10bPort 2
11bTarget Device Name
S/NSequentially increasing drive serial number assigned at manufacturing.
17.4 Spin up
The drive supports the Active Wait, Active, and S topped states specified by the SAS standard. After power on, the drive enters
the Active Wait state. The Drive will not spin up it's spindle motor after power on until it receives a NOTIFY (Enable Spinup)
primitive on either port to enter the Active state. If a NOTIFY (Enable Spinup) primitive is received prior to receiving a StartStop Unit command with the Start bit set to one, spin up will begin immediately. For SAS, this is analogous to auto-spinup
function in legacy SCSI. This provision allows the system to control the power spikes typically incurred with multiple drives
powering on (and spinning up) simultaneously.
If a StartStop command with the Start bit set to one is received prior to receiving a NOTIFY (Enable Spinup), the Drive will
not
start it’s spindle motor until Notify (Enable Spinup) is received on either port. Successful receipt of a NOTIFY (Enable
Spinup)
is a prerequisite to spin up.
If the StartStop Unit command with the Start bit set, also has the immediate bit set, status will be returned prior to actually
spinning up the motor, but the actual act of spinning up the motor is deferred until receipt of the NOTIFY (Enable Spinup)
primitive. If a media access command is received after sending immediate Status and prior to receiving a NOTIFY (Enable
Spinup), the Drive will terminate the command with CHECK CONDITION status with a sense key of NOT READY and an
additional sense code of LUN NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED. If a media access command is
received after receiving the NOTIFY (Enable Spinup) primitive and before the drive is finished spinning up, the Drive will terminate the command with CHECK CONDITION status with a sense key of LUN NOT READY and an addition sense code of
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
49
Page 66
LUN IS IN THE PROCESS of BECOMING READY.
Active WaitStopped
Active
Power On
NOTIFY
(ENABLE SPINUP)
STOP UNIT
START UNIT
STOP UNIT
17.5 PHY Layer
The Phy layer defines 8b10b coding and OOB signals. The Phy layer is the interface between the link layer and the physical
layer. This section describes Phy Layer behaviors of the Drive. For a complete description of SAS Phy Layer, please see the
ANSI specification, SAS 1.1.
17.5.1 Link Reset Sequence
The Link Reset Sequences for SAS are defined in the SAS 2 ANSI specification and shown below. As show in the diagram, a
Phy Reset sequence, consists of an OOB sequence, followed by speed negotiations. Link Reset Sequences will always include
a PHY Reset Sequence, followed by an Identification Sequence. Inclusion of a Hard reset sequence is optional. If Hard Reset
is performed, it will be preceded by a Phy Reset sequence, and will be followed by Phy Reset/Identification sequences.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
50
Page 67
17.5.2 Hard Reset
Link Reset Sequence with hard Reset
Time
Phy Reset sequence
Identification sequence
Phy Reset sequenceHard Reset Sequence
Phy Reset sequenceIdentification sequence
Time
SAS
SAS w/Hard Reset
Link Reset sequence
OOB sequenceSpeed Negotiation
sequence
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. id le is transm itted. 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 COMW AKE and COMSAS.OOB
operations are beyond the scope of this specification. Please refer to the ANSI SAS 2 specification for more details.
The drive will initiate OOB by sending COMINITs, under the following conditions:
• POR
• loss of sync
• Identify timeout
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
51
Page 68
17.5.4 SAS Speed Negotiation
The Drive supports G1 (1.5 Gbps), G2 (3.0 Gbps), and G3 (6.0 Gbps) negotiation speeds. The default max imum negotiation
rate is G3 speed (per byte 32 in the Phy Control and Discover Mode Page 19 subpage 1). Drive is SAS2 device and supports
SNW-1, SNW-2, and SNW -3 speed negotiation with Phy capabilities exchange, and training (Train-SNW). Phy capabilities is
defined in table below:
Phy Capabilities:
Byte /Bit76543210
0S t a r t = 1 b T X S S C
Type = 0b
1G1 W i th out
SSC=1b
2
3
G1 With
SSC=0b
Reserved
G2 Without
SSC=1b
Reserved
G2 With
SSC=0b
G3 Without
SSC=1b
Reserved
Requested Logical Link Rate = 0h
G3 With
SSC=0b
Reserved
Parity
•Start bit is 1 to indicate the beginning of the Phy capabilities
•TX SSC Type bit is set to 0 to indicate that Phy’s transmitter uses down spreading SCC when is enabled (e.g.
the phy is a SAS phy).
•Request Logical Link Rate field is 0 to indicate that drive does not support multiplexing
•G1 Without SSC bit set to 1 indicates that drive supports G1(1.5 Gbps) without SSC
•G2 Without SSC bit set to 1 indicates that drive supports G2(3.0 Gbps) without SSC
•G3 Without SSC bit set to 1 indicates that drive supports G3(6.0 Gbps) without SSC
•G1 With SSC bit set to 1 indicates that drive supports G1(1.5 Gbps) with SSC
•G2 With SSC bit set to 1 indicates that drive supports G2(3.0 Gbps) with SSC
•G3 With SSC bit set to 1 indicates that drive supports G3(6.0 Gbps) with SSC
•Parity bit is set to 1 for even parity of the total number of SNW-3 phy capabilities, including Start bit.
Training is based on the highest untried commonly supported settings on the exchan ged SNW-3 supported settings bits. If a
Train-SNW is invalid and there are additional, untried, commonly supported settings exchanged during SNW-3, then a new
Train-SNW will be performed based on the next highest untried, commonly supported settings. Table 26 defines the priority of
the supported settings bits.
Table 26: Supported Settings Bit Priorities
PriorityBit
Highest G3 With SSC bit
... G3 Without SSC bit
... G2 With SSC bit
... G2 Without SSC bit
... G1 With SSC bit
Lowest G3 Without SSC bit
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
52
Page 69
17.5.5 PHY Error Handling
This section defines the PHY layer error handling of the drive.
Error Error Handling Procedure
Link Reset After POR or Hard Reset, the drive initiates link reset by transmitting exactly 1
COMINIT . For other resets, the drive does not initiate Link Reset.
COMINIT Timeout If COMINIT or COMSAS is not received before the ”Hot Plug Timeout" period
expires, the drive continues to transmit DC zero and wait for COMINIT/COMSAS. Firmware is notified.
This is not considered an error.
COMSAS Timeout If COMINIT is detected, COMSAS is transmitted, and COMSAS is not
received before the COMSAS Detect Timeout timer expires, firmware is notified and the drive continues to transmit DC zero and wait for COMINIT.
Speed Negotiation Errors If speed negotiation fails with no match, or if the drive fails retrying the matched
link rate, firmware is notified and the drive continues to transmit DC zero and
wait for COMINIT. If the match link rate retry fails, the Phy Reset Problem
counter is incremented (Log Page 0x18).
Loss of SyncIf the drive loses DWORD sync long enough for the loss of sync timer to expire,
firmware is notified and the drive transmits a COMINIT to initiate a new link
reset. The Loss of DWORD sync counter is incremented (Log Page 0x18).
Disparity/Invalid DWORD
Error
If a disparity error or an invalid DWORD is detected by the drive, the Invalid
DWORD Count is incremented (Log Page 0x18). The Running Disparity Error
Count in Log Page 0x18 is not used
17.6 Link Layer
The SAS link layer defines primitives, address frames, and connections. The Link layer is the interface between the Port layer
and the Phy layer. This section describes Link Layer behaviors of the Drive. For a complete description of SAS Link Layer,
please see the ANSI specification, SAS 1.1.
17.6.1 Address Frames
Address frames are used for the identification sequence and for connection requests and are only sent outside connections. The
Address Frame format is defined below:
Table 27: Address Frame Format
ByteBit
76543210
0RsvdDevice TypeAddress Frame Type
1-27Frame Type Dependent bytes
28-31CRC
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
53
Page 70
•The ADDRESS FRAME TYPE field indicates the type of address frame and is defined in table 28. This field determines
the definition of the frame type dependent bytes.
Table 28: Frame type:
Value Address Frame Type Description
0000b IDENTIFY: Identification Sequence
0001b OPEN: Connection Request
Others RESERVED
17.6.1.1 Identify Address Frame
The IDENTIFY address frame format is used for the identification sequence. The IDENTIFY address frame is sent after the
phy reset sequence completes. The Identify Address Frame format is defined as follows:
Table 29: Identify Address Frame
ByteBit
7654 3210
0R s v d D e v i c e T y p e = 1Ad d r e s s F r a m e Ty p e = 0
1ReservedReason
2Reserved SSP
Initiator
Port=0b
3Reserved SSP
Target
Port=1b
STP
Initiator
Port=0b
STP
Target
Port=0b
SMP
Initiator
Port=0b
SMP
Target
Port=0b
Rsvd
Rsvd
4-11Device Name
12-19SAS Address
20PHY Identifier
21Reserved Inside
ZPSDS Persistent=0b
Requested
Inside
ZPSDS=0b
Break_Reply
Capable=1b
22-27Reserved
28-31CRC
•Device Type: set to 001b to indicate that this drive is an "End Device".
•Address Frame Type: set to 00b to indicate that this is an IDENTIFY.
•Reason: field indicates the reason for link reset sequence as defined inTable 30 on page 55
• Initiator Port bits: set to 000b since this device is a target device only
•Target Port bits: set to 100b since this device is a SSP target device only
•Device Name: field contains Target Device Identifier
•SAS ADDRESS: field contains the port identifier of the SAS port transmitting this frame.
•PHY Identifier: field contains the PHY identifier of the PHY transmitting this frame.
•Break_Reply Capable: set to 1b to indicate that this port is capable of sending BREAK_REPLY primi tive sequence in
responding of receiving BREAK primitive sequences
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
54
Page 71
•Requested Inside ZPSDS: set to 0b since this is an "End Device"
•Inside ZPSDS Persistent: set to 0b since this is an "End Device"
Table 30: Reason field
Value Address Frame Type Description
00b Power on
01b OPEN: Connection Request
02b Hard Reset (received a Hard Reset during hard reset sequence)
04b Loss of dword synchronization
07b Break timeout timer expired
08b Phy test function stopped
Others RESERVED
17.6.1.2 OPEN Address Frame
The OPEN address frame format is used for the identification sequence. The OPEN address frame is sent after the phy reset
sequence completes. The OPEN Address Frame format is defined as follows:
ByteBit
76543210
0Initiator
Protocol = 1Address Frame Type = 1
P o r t = 0
1Features = 0Connection Rate = 8h or 9h or Ah
2-3Initiator Connection Tag
4-11Destination SAS Address
12-19Source SAS Address
20Source Zone Group
21Pathway Blocked Count
22-23Arbitration Wait Time
24-27More Compatible Features
28-31CRC
•Initiator Port: This bit is set to zero when the Drive is the source port acting as a SAS target.
•Protocol: this field is set to 001b to indicate SSP Protocol.
•Features: this field is set to zero and ignored by the Drive per SAS 1.1.
•Connection Rate: field should be set to 8h (1.5Gbps) or 9h (3Gbps), depending on requested link rate. Rate matc hing is
supported by the Drive, therefore if the Link to the drive is 3.0Gbps, and the Connection Rate is 1.5Gbps, the Drive will
insert ALIGNs between DWords, to match the Connection Rate.
•Initiator Connection Tag: The Drive will set this value to the last value received from this Initiator.
•Destination SAS Address: field contains the port identifier of the SAS port to which a connection is being requested.
•Source SAS Address: field contains the port identifier on the port that originated this frame (i.e. the drive’s port address).
•Source Zone Group: This field is set to zero and ignored by the Drive per SAS 2.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
55
Page 72
•Pathway Blocked Count: this field indicates the number of times the port has retried this connection requ est due to
receiving OPEN_REJECT (P ATHWAY BLOCKED). The Drive willl not increment the PATHWA Y BLOCKED COUNT
value past FFh.
•Arbitration Wait Time: this field indicates how long the port transmitting the OPEN address frame has been waiting for
a connection request to be accepted. For values from 0000h to 7FFFh, the Arbitration Wait Time timer increments in one
microsecond steps. For values from 8000h to FFFFh, the Arbitration Wait Time timer increments in one millisecond step.
•More Compatible Features: this field is set to zero and ignored by the Drive per SAS 1.1.
17.6.2 Link Layer Error Handling
This section defines the Link layer error handling of the drive.
Error Error Handling Procedure
IDENTIFY TimeoutIf IDENTIFY is not received before the IDENTIFY timer expires (1ms), firm-
ware is notified and the drive transmits a COMINIT to initiate a new link reset.
BREAK ReceivedIf BREAK is received while the drive has ACK/NAK balance, BREAK or
BREAK_REPLY is transmitted and a new connection may be opened if the
drive still has frames to transmit. Firmware is not notified. If BREAK is
received while the drive does NOT have ACK/NAK balance, BREAK or
BREAK_REPLY is transmitted and the current command is aborted and will
return Check Condition status with sense data indicating an ACK/NAK timeout.
NAK and ACK/NAK Timeout If a NAK is received on a RESPONSE frame, the RESPONSE frame is retrans-
mitted with the RETRANSMIT bit set to zero. If an ACK or NAK is not
received for a RESPONSE frame within 1ms, the RESPONSE frame will be
retransmitted with the RETRANSMIT bit set to one. The drive will retry sending a RESPONSE frame once.
Bad Frame CRCIf a frame fails the CRC check, the frame is NAKed by the drive and discarded.
This is a link layer function. The command associated with a NAKed DATA or
XFER_RDY frame is aborted with check condition status and sense data corresponding to DATA_PHASE_ERROR is returned. COMMAND frames that fail
the CRC check are NAKed and discarded.
OPEN_REJECTOPEN_REJECT – Retryable Variations
•OPEN_REJECT(RETRY) - Will be retried indefinitely by the drive. This
case is considered to be occur when the initiator is temporarily not available
to accept connections (for example when it is not able to extend R-Rdy
credit at this time due to lack of buffers...), so the initiator will ask us to
keep "RETRY"-ing, until it becomes available at a later time. Thus, we
don't consider this an error condition, but part of normal behavior for the
initiator.
•OPEN_REJECT(RATE_NOT_SUPPORTED) – If this occurs, it must
mean that a link between the drive and initiator renegotiated to a lower link
rate after the command was received. In this case, we retry in a new connection at 1.5Gbps. If this error is received for a 1.5Gbps connection, the command is internally aborted.
OPEN_REJECT – (PATHWAY_BLOCKED)
•OPEN_REJECT(BAD_DESTINATION),
OPEN_REJECT(WRONG_DESTINATION),
OPEN_REJECT(PROTOCOL_NOT_SUPPORTED) – If these
OPEN_REJECTs are received, we internally abort the command.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
56
Page 73
Credit TimeoutIf credit is not received before the credit timer expires,
DONE(CREDIT_TIMEOUT) is sent to the Initiator.
DONE TimeoutIf credit is extended and the DONE timer expires, BREAK is sent by hardware
to tear down the connection.
CREDIT_BLOCKEDIf CREDIT BLOCKED is received and the drive has frames to send in the cur-
rent connection, DONE(CREDIT_TIMEOUT) is returned. Otherwise,
DONE(NORMAL) is returned.
OPEN Frame CheckingReserved fields in the OPEN frame are not checked.
•The Dest Address field is checked, and if it doesn’t match
OPEN_REJECT(WRONG_DESTINATION) is returned.
•The Protocol field is checked and if it isn’t set to SSP
OPEN_REJECT(PROTOCOL_NOT_SUPPORTED) is returned.
•If the Link Rate exceeds the physical link rate on that port,
OPEN_REJECT(LINK_RATE_NOT_SUPPORTED) is returned.
•The Initiator bit is not checked.
OPEN Response TimeoutIf AIP or OPEN_ACCEPT is not received before the OPEN Respon se ti mer
expires, the hardware transmits BREAK.
CLOSE TimeoutIf CLOSE is not received before the CLOSE timer expires, the hardware trans-
mits BREAK.
Phy Not ReadyIf Link Reset occurs outside of a connection, commands can execute normally
across the link reset. If a link reset occurs inside of a connection, the behavior is
similar to BREAK in that it is treated as an abruptly closed connection. In cases
where the command cannot be continued normally (e.g. a frame is corrupted by
OOB signals, or we do not have ACK/NAK balance), the command is terminated with CHECK CONDITION status with sense data corresponding to ACK/
NAK TIMEOUT.
\
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
57
Page 74
17.7 Transport Layer
The Transport layer defines frame formats. The Transport layer is the interface between the application layer and port layer. It
is responsible for constructing and parsing frame contents. For SSP, the transport layer only receives frames from the port layer
that are going to be ACKed by the link layer. This section describes Transport Layer behaviors of the Drive. For a complete
description of SAS Transport Layer, please see the ANSI specification, SAS 1.1.
The transport layer defines the frame format as follows.
Table 31: SAS Frame Format
ByteBit
76543210
0Frame Type
1-3Hashed Destination Address
4Reserved
5-7Hashed Source Address
8-9Reserved
10Reser v ed TLR Control = 00b Ret r y Dat a
Frames =0b
11Reserved # of fill bytes
12-15Reserved
Retransmit
Rsvd
16-17Tag
18-19Target Port Transfer Tag
20-23Data Offset
24-mInfo rma tion Unit
Fill Bytes (if Needed)
(n-3)-nCRC
• FRAME TYPE field, which defines the format of the INFORMATION UNIT field as follows:
CodeName of FrameInformation UnitOriginatorIU Size (bytes)
01hDATADataInitiator or Target1-1024
05hXFER_RDYData T ransfer ReadyTarget12
06hCOMMANDCommandInitiator28-284
07hRESPONSEResponseTarget24-1024
16hTASKTask Management
Initiator28
Function
f0-ffhvendor specific
all othersreserved
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
58
Page 75
• The HASHED DESTINATION SAS ADDRESS field contains the hashed value of the destination SAS address.
• The HASHED SOURCE SAS ADDRESS field contains the hashed value of the source SAS address.
•The TLR CONTROL field is not supported
•The RETRY DATA FRAMES is not supported
•The CHANGING DATA POINTER is not supported
• The NUMBER OF FILL BYTES field indicates the number of fill bytes between the INFORMATION UNIT field and
the CRC field. The RETRANSMIT bit is set to one for RESPONSE fr ames when attemptin g to retransmit this frame
due to receiving an error during the initial transmission. It shall be set to zero for all other frame types. The NUM-BER OF FILL BYTES field shall be set to zero for all frame types except DATA frames
•. The TAG field contains a value that allows the SSP port to establish a context for commands and task management functions.
• The TARGET PORT TRANSFER TAG field is set and used by the drive. The initiator should echo this field in out-
bound data IU.
• The INFORMATION UNIT field contains the information unit, the format of which is defined by the FRAME TYPE
field.
• Fill bytes shall be included after the INFORMATION UNIT field so the CRC field is aligned on a four byte boundary.
17.7.1 Command Information Unit
The COMMAND frame is sent by an SSP initiator port to request that a command be processed by the drive.
Table 32: COMMAND Information Unit
ByteBit
76543210
0-7Logical Unit Number
8Reserved
9Disable
first
burst=0
10Reserved
11Additional CDB Length (in Dwords) Rsvd
12-27CDB
28-nAdditional CDB Bytes
• The LOGICAL UNIT NUMBER field contains the address of the logical unit. The drive only supports a LUN of 0’s.
• A DISABLE FIRST BURST bit is not supported by the drive
• The TASK ATTRIBUTE fi eld is defined as follows:
Value Attribute
Reserved
Task
Attribute
000b Simple_Q
001b Head_of_Q
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
• The ADDITIONAL CDB LENGTH field contains the length in dwords (four bytes) of the ADDITIONAL CDB field.
• The CDB and ADDITIONAL CDB BYTES fields together contain the CDB.
17.7.2 TASK Information Units
Table 33: TASK Information Unit
ByteBit
76543210
0-7Logical Unit Number
8-9Reserved
10Task Management Function
11Reserved
12-13Tag of Task to be Managed
14-27Reserved
• The LOGICAL UNIT NUMBER field contains the address of the logical unit. The drive only supports a LUN of 0’s.
• The TASK MANAGEMENT FUNCTION field is defined as follows:
Value Function
01h ABOR T TASK: The Drive shall perform the ABORT TASK associated with the value of the
TAG OF TASK TO BE MANAGED field
02hABORT TASK SET: The Drive shall perform the ABORT TASK SET by aborting all out-
standing tasks for the Initiator that sent the TMF.
04h CLEAR TASK SET: This TMF causes the Drive to abort all tasks in the task set. The action
is equivalent to receiving a series of Abort Task requests from all Initiators.
A unit attention condition shall be generated for all other Initiators with tasks in the task set.
The Additional Sense Code shall be Commands cleared by another Initiator.
08hLUN RESET: The LUN RESET causes the Target to execute a hard reset. This means:
1. Abort all tasks for all Initiators on either both ports.
2. Release any device reservation on either port.
3. Set a Unit Attention condition for all Initiators.
40hCLEAR ACA (not supported)
80hQUERY TASK: The drive shall return a response of FUNCTION SUCCEEDED if the spec-
ified task exists, or FUNCTION COMPLETE if the specified task does not exist.
81hQUERY TASK SET: The drive shall return a response of FUNCTION SUCCEEDED if
there is any task exist, or FUNCTION COMPLETE if there is no task exist.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
60
Page 77
82hQUERY ASYNCHRONOUS EVENT (formerly QUERY UNIT ATTENTION): The drive
shall return a response of FUNCTION SUCCEEDED if there is a unit attention or a deferred
error pending, or FUNCTION COMPLETE if there is no unit attention or no deferred error
pending.
othersRESERVED: The Drive will return a RESPONSE frame with the
RESPONSE_DATA and its
RESPONSE CODE field set to TASK MANAGEMENT FUNC-
DATAPRES field set to
TION NOT SUPPORTED.
• If TMF is set to ABORT TASK or QUERY TASK, the TAG OF TASK TO BE MANAGED field specifies the TAG
value from the COMMAND frame that contained the task to be aborted or checked. For all other TMF’s, this field is
ignored.
•If TMF is set to QUERY ASYNCHRONOUS EVENT, the Additional Response Information argument is set to 000000h
for the response of FUNCTION COMPLETE. If the response is FUNCTION SUCCEED, the Additional Response
Information argument is set as defined in table 34.
Table 34: Additi onal Response Information argument for Query Async Event
ByteBit
76543210
0 RESERVEDUADE DEPTH SENSE KEY
1ADDITIONAL SENSE CODE
2ADDITIONAL SENSE CODE QUALIFIER
The UADE DEPTH is the number of pending unit attention conditions or deferred errors. It is defined as in table Table 35:
The SENSE KEY field is the value of the SENSE KEY field in the highest-priority pending unit attention condition or
deferred error.
The ADDITIONAL SENSE CODE field is the value of the ADDITIONAL SENSE CODE field in the highest-priority pending unit attention condition or deferred error.
The ADDITIONAL SENSE CODE QUALIFIER field is the value of the ADDITIONAL SENSE CODE QUALIFIER field in
the highest-priority pending unit attention condition or deferred error
Table 35: UADE DEPTH field
Code Description
00bThe combined number of unit attention conditions and deferred errors is unknown
01bThe combined number of unit attention conditions and deferred errors is one
10bThe combined number of unit attention conditions and deferred errors is greater than one
11bReserved
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
61
Page 78
17.7.3 XFER_RDY Information Units
The XFER_RDY frame is sent by the Drive to request write data (i.e. out bound data) from the initiator.
Table 36: XFER_RDY Information Unit
ByteBit
76543210
0 - 3REQUESTED OFFSET
4 - 7WRITE DATA LENGTH
8 - 11RESERVED
•The REQUESTED OFFS ET field contains the buffer of fset of the segment of write data the Initiator may transmit to the
Drive (using DATA frames). The requested offset shall be a multiple of four.
•The WRITE DATA LENGTH field contains the number of bytes of write data the Initiator may transmit to the Drive
(using DATA frames) from the requested offset.
17.7.4 DATA Information Units
The DATA frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data).
Table 37: DATA Information Unit
ByteBit
76543210
0 - (n-1)DATA
17.7.5 RESPONSE Information Units
The RESPONSE frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data).
Table 38: Response Information Unit
ByteBit
76543210
0-7RESERVED
8-9MSB RETRY DELAY TIMER LSB
10RESERVEDDataPres
11STATUS
12 - 15Reserved
16 - 19SENSE DATA LENGTH (n bytes)
20 - 23RESPONSE DATA LENGTH (m bytes)
24 - (24+m)RESPONSE DATA
(24+m) -
(23+m+n)
SENSE DATA
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
62
Page 79
•The RETRY DELAY TIMER field contains the retry delay timer code which is defined as follows:
Status CodeRetry Delay Timer CodeDescription
0000h Same as normal busy
0001h-FFEFh The number of 100 milliseconds increments which Ini-
BUSY
tiator should wait before sending another command to
Drive
FFF0h-FFFDhRESERVED
FFEFhInitiator should stop sending commands to Drive
QUEUE FULL
FFFFh
0000h Same as normal busy
0001h-FFEFhInitiator should wait before sending another command
Drive is not able to accept the command
to the Drive until:
a) At least the number of 100 milliseconds increments
•The DATAPRES field, which indicates the format and content of the STATUS field, SENSE DATA LENGTH field,
RESPONSE DATA LENGTH field, RESPONSE DATA field, and SENSE DATA field.
Value DATAPRES Description
00b NO DATA: no data present
01b RESPONSE_DATA: response data present
10b SENSE_DATA: sense data present
11b RESERVED
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
63
Page 80
Table 39: RESPONSE DATA
ByteBit
76543210
0 - 2RESERVED
3RESPONSE CODE
• RESPONSE CODES are defined as follows:
Value RESPONSE Code Description
00b T a sk Management Function complete
02b Invalid Frame
04b Task Management Function not supported
05b Task Management Function failed
08b Task Management Function succeeded
09b Invalid LUN
others RESERVED
17.7.6 Sequences of SSP Information Units
SSP Information Units are used in conjunction with one another to execute SCSI commands. This section provides a brief
overview of SAS SSP Information Unit sequences, that would be required to complete a SCSI command.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
64
Page 81
Figure 1: SSP Information Unit Sequences
InitiatorTarget
Command IU
Data IU (s)
Response IU
TimeTime
Read Type Command
IU Sequence
InitiatorTarget
Command IU
Data IU (s)
Response IU
TimeTime
Write Type Command
IU Sequence
Xfr_Rdy IU
17.7.7 Transport Layer Error Handling
This section defines the Transport layer error handling by the drive.
Error Error Handling Procedure
SSP Header Field CheckingReserved fields in SSP frames are not checked.
Data Offset ErrorIf a DATA frame with an invalid Data Offset is received, the command associ-
ated with the DATA frame is aborted with Check Condition status and sense
data corresponding to a DATA OFFSET ERROR is returned
I_T NEXUS Loss TimeoutIf a connection cannot be established to an initiator before the I_T NEXUS
Initiator Response TimeoutIf DATA frames corresponding to an outstanding XFER_RDY frame are not
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
LOSS timer expires (Mode Page 0x19), all commands from the initiator are
internally aborted. The first new command received from the affected Initiator
results in a CHECK CONDITION with sense data corresponding to I_T
NEXUS LOSS OCCURRED.
received before the Initiator Response timer expires (Mode Page 0x19), the
command is aborted with CHECK CONDITION status and sense data corresponding to INITIATOR RESPONSE TIMEOUT is returned for the affected
command.
65
Page 82
Data OverflowIf more data is received than requested via an XFER_RDY frame, the affected
command is aborted with CHECK CONDITION status with sense data corresponding to TOO MUCH WRITE DATA is returned.
Invalid Target Port Transfer Tag If a DATA frame is received and the TPTT is not set to the value used in the cor-
responding XFER_RDY frame, the frame is discarded. If a COMMAND or
TASK frame is received with the TPTT set to a value other than 0xFFFF, a
RESPONSE frame with RESPONSE_DATA set to INVALID FRAME is
returned.
Invalid Frame LengthIf a DATA frame is received with zero bytes of payload data, the frame is dis-
carded. This is not considered an error. If a COMMAND/TASK frame that is too
short is received, RESPONSE data corresponding to INVALID FRAME is
returned. The additional CDB length field of a COMMAND frame is not
checked for correctness. If a DATA frame is received with a payload greater
than 1024 bytes, the frame is discarded and the command is aborted with
CHECK CONDITION status and sense data corresponding to
DATA_PHASE_ERROR is returned.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
66
Page 83
18.0 SCSI Command Set
Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory
Table 40: SCSI Commands Supported
Type Code Description
M 04h FORMAT UNIT (04), page 70
M 12h INQUIRY (12), page 78
O 4Ch LOG SELECT (4C), page 98
O 4Dh LOG SENSE (4D), page 101
O 15h MODE SELECT (15), page 134
O 55h MODE SELECT (55), page 135
O 1Ah MODE SENSE (1A), page 136
O 5Ah MODE SENSE (5A), page 176
O5EhPERSISTENT RESERVE IN (5E), page 177
O5FhPERSISTENT RESERVE OUT (5F), page 180
O 34h PRE-FETCH (34), page 185
O 90h PRE-FETCH (90), page 186
M 08h READ (6) - (08), page 187
M 28h READ (10) - (28), page 188
OA8hREAD (12) - (A8), page 190
O88hREAD (16) - (88), page 191
O7Fh/09hREAD (32) - (7F/09), page 1 92
O 3Ch READ BUFFER (3C ), page 194
M 25h READ CAPACITY (10) - (25), page 198
O9Eh/10hREAD CAPACITY (16) (9E/10), page 200
O 37h READ DEFECT DA TA (37), page 201
OB7hREAD DEFECT DATA (B7), page 205
O 3Eh READ LONG (3E), page 207
O 9Eh READ LONG (9E), page 208
O 07h REASSIGN BLOCKS (07), page209
O 1Ch RECEIVE DIAGNOSTICS RESULTS (1C), page 211
M 17h RELEASE (17), page 213
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
68
Page 85
18.1 SCSI Control Byte
The Control Byte is the last byte of every CDB. The format of this byte is shown below.
Table 41: SCSI Co ntrol Byte
BIT
7
VU = 0
VU
VU stands for Vendor Unique.
Note: * - The drive ignores the link bit and flag bit in the CDB.
6 5 4 3 2 1 0
Reserved = 0
18.2 Abbreviations
These abbreviations are used throughout the following sections:
LUNLogical Unit Number. An encoded three bit identifier for the logical unit.
VUVendor Unique bits
LBALogical Block Address
RSVD Reserved
MSBMost Significant Byte
LSBLeast Significant Byte
18.3 Byte ordering conventions
In this specification, where it is not explicitly stated, all multi-byte values are stored with the most significant byte first. For
example, in a 4 byte field, byte 0 will contain the MSB and byte 3 the LSB.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
69
Page 86
18.4 FORMAT UNIT (04)
Table 42: FORMAT UNIT (04)
ByteBIT
7 6 543210
0Command Code = 04h
1FMTPINFO
2VU = 0
3-4Obsolete = 0
5VU = 0 Reserved = 0 FLAG LINK
• FMTPINFO (Format Protection Information) in combination with the Protection Field Usage field in the Parameter
List Header specifies whether or not the drive enables or disables the use of protecti on information (see table defined
in the Parameter List Header section).
• FmtData set to one specifies that a Data Out phase follows the Command phase. The Data Out phase consists of a
Parameter List header, optionally followed by an Initialization Pattern Descri ptor, optionally followed by a Defect
List. If FmtData=0, the following defaults are assumed: DPRY=0, DCRT=1, STPF=1, IP=0, DSP=0, Immed=0.
• CmpLst
• Set to one specifies that the Grown Defect List (GList) existing prior to the issuance of the Format Unit command
be discarded. If provided, the DList then becomes the GList. Following these operations, the Drive will be formatted
with the PList and GList.
• Set to zero specifies that the GList existing prior to the issuance of the Format Unit command is retained. If provided, the DList is combined with the GList to become the new GList. Following these operations, the Drive will be
formatted with the PList and GList.
Note: The drive manages two internal defect lists and one external. The Plist is created at time of manufacture. The Glist is
built after manufacture by the Initiators’ use of the REASSIGN BLOCK command and the Automatic Reallocate functions.
The Dlist is an external list. It is supplied by the Initiator in the Data Out phase of the FORMAT UNIT command.
• Defect List Format specifies the format of the defect descriptor transferred to the Target when FmtData bit is set to one.
The Target supports the following three defect descriptor formats for the FORMAT UNIT command:
LONG
LIST=0
FMTDATA
CMPLISTDefect List Format
Format Description
000b Block format
100bBytes From Ind e x format
101b Physical Sector format
If the FmtData bit is set to zero, this field must also be zero. Otherwise the command will complete with a CHECK
CONDITION with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
•Notes:It is recommended that the MODE SELECT command be issued prior to the FORMAT UNIT command to specify
parameters that affect the formatting process.
The Block Length parameter of the Mode Select Parameter List’s Block Descriptor is used during formatting and is
saved following a successful format operation. If a MODE SELECT command has not been issued since the last reset
or start-up (bring-up) sequence, then the Block Length from the previous format operation is used.
Subsequent to receiving a FORMAT UNIT command, the Target responds to commands as follows:
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
70
Page 87
- All commands except REQUEST SENSE and INQUIRY return Check Condition status, while the format operation
is an active I/O process.
- When tagged queuing is enabled (DQue = 0), all commands except REQUEST SENSE and INQUIRY return
Queue Full status, while the FORMAT UNIT command is a queued I/O process.
- When tagged queuing is disabled (DQue = 1), all commands except REQUEST SENSE and INQUIRY return Busy
status, while the FORMAT UNIT command is a queued I/O process
- If a REQUEST SENSE command is received while a format operation is an active I/O process, the Target returns
Good status. The sense key is set to Not ready and the additional sense code and qualifier is set to Format In Progress.
- If an INQUIRY command is received while a format operation is an active I/O process, the Target returns Good
status and Inquiry data as requested.
The format operation must complete successfully for the Drive to be usable. If the command is interrupted by a reset,
power down, or an unrecoverable error, the Drive enters a degraded mode of operation in which reading and writing
are prohibited. To exit the degraded mode, another FORMAT UNIT command must be sent by the Initiator and completed successfully by the Target.
The FORMAT UNIT command sets the Unit Attention Condition for all Initiators except the one that issued the FORMAT UNIT command.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
71
Page 88
18.4.1 Parameter List Header
Following is the format of the Parameter List Header sent during the data out phase when FmtData is set to one.
Table 43: Format of the Short Parameter List Header
Byte
76543210
BIT
0Reserved = 0 Protection Field Usage
1
FOV DPRY DCRT STPF =1IP
ObsoleteImmed Vendor-specific
2 -3(MSB)Defect List Length (LSB)
4-nInitialization Pattern Descriptor
(n+1) - mDefect Descriptor
Table 44: Format of the Long Parameter List Header
• Protection Field Usage: in combination with the format protection information (FMTPINFO) field in the CDB specifies
whether or not the drive enables or disables the use of protection information:
FMTPINFOProtection Field UsageDescription
00h000hThe drive will be formatted to type 0 protection
01hxxxh
Check Condition status will be returned with the sense key set to Illegal
Request and the additional sense code set to Invalid Field in the CDB.
10h000hThe drive will be formatted to type 1 protection
11h000hThe drive will be formatted to type 2 protection
Type 3 protection is not supported - Check Condition status will be
11h001h
returned with the sense key set to Illegal Request and the additional
sense code set to Invalid Field in the Parameter List
All other combinations of FMTPINFO and Protection Field Usage will result in Check Condition status to be returned with the
sense key set to Illegal Request and the additional sense code set to Invali d Field in the Parameter List.
T ype 0 protection specifies that the drive shall disable the use of protection information and format to the block size specified.
Following a successful format, the PROT_EN bit in the READ CAPACITY (16) parameter data will indicate that protection
information is disabled.
T ype 1 and type 2 protection specifies that the drive shall enable the use of protection information and format to the block size
specified + 8 (e.g., if the block length is 512, then the formatted block length is 520). See format of data below. When protection information is written during a FORMA T UNIT command, protection information shall be written with a default value of
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
72
Page 89
all 0xFF's. Following a successful format, the PROT_EN bit in the READ CAPACITY (16) parameter data will indicate that
protection information is enabled and the P_TYPE field in the READ CAP ACITY (16) parameter data will indicate the protection type.
Byte
76543210
BIT
0... nUser Data
n... n+1 Logical Block Guard
n+2... n+3 Logical Block Application Tag
n+4... n+7 Lo gical Block Reference Tag
•The Logical Block Guard field contains a CRC that covers the preceding user data. This field is generated/checked per
the SBC standard.
The Logical Block Applica tion Tag field may be modified by the initiator if the A T O bit is set to zero in mode page 0x0A. If
the ATO bit is set to one, then the initiator shall not mod ify the Logical Block Application Tag field. This field is generated/
checked per the SBC standard.
•The Logical Block Reference Tag field is generated/checked depending on protection types. With Type 1 protection, the
Logical Block Reference Tag in the first logical block of the data transfer shall contain th e least significant four bytes
of the LBA contained in the Logical Block Address field of the command. Subsequent blocks shall contain the previous logical block reference tag plus one. With Type 2 protection, the Logical Block Reference Tag in the first logical
block of the data transfer shall contain the value in the Expected Initial Logical Block Reference Tag field of the
command. Subsequent blocks shall contain the previous logical block reference tag plus one.
• FOV (Format Options Valid) bit set to zero indicates that the Target should use its default settings for the DPRY (0),
DCRT (1), STPF (1), IP (0), and DSP (1) bits. These bits must all be set to zero in the Parameter List Header when
FOV=0, or the command will be terminated with Check Condition status, sense key of Illegal Request, and additional
sense code of Invalid Field in Parameter List. FOV=1 indicates that the values set in DPRY, DCRT, STPF, IP, and
DSP will be defined as specified below.
• DPRY (Disable Primary) bit set to zero indicates that the Target does not use portions of the medium identified as defec-
tive in the primary defect Plist for Initiator addressable logical blocks. If the Tar get cannot locate the Plist or it cannot
determine whether a Plist exists, the Target terminates the FORMAT UNIT command as described for STPF=1. A
DPRY bit set to one indicates that the Target does not use the Plist to identify defective areas of the medium. The Plist
is not deleted. DPRY must be set to 0 when DCRT is set to 0.
• DCRT (Disable Certification) bit set to zero indicates that the Target performs a medium certification operation and gen-
erates a Certification List (Clist), and adds the Clist to the Glist. DPRY must be set to 0 when DCRT is set to 0. A
DCRT bit of one indicates that the Target does not generate a Clist or perform a certification process.
Note:Since the DCRT bit is part of the Data Out phase that follows the FORMAT command, the FCERT bit in
Mode Page 0 is provided to control certification when the FORMAT command is issued with no Data Out
phase. If a FORMAT comman d is issued with a Data Out phase then FCERT is ignored.
• STPF (Stop Format) bit must be set to one. If one or both of the following conditions occurs, the Target terminates the
FORMAT UNIT command with Check Condition status. The sense key is set to Medium Error and the additional
sense code is set to Defect List Not Found if the first condition occurred or to Defect List Error if the second condition occurred.
• The Target cannot locate a required Dlist nor determine that the list exists.
•The Target encounters an unrecoverable error while accessing a required Dlist.
• IP (Initialization Pattern) bit set to zero specifies that an initialization pattern descriptor is not included and all customer
data will be initialized to zeroes. An IP bit of one specifies that an Initialization Pattern Descriptor is included in the
FORMAT UNIT parameter list following the parameter list header.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
73
Page 90
18.4.2 Initialization Pattern
Table 45: Initialization Pattern Descriptor:
BIT
Byte
0IP Modifier = 0S IReserved = 0
1 Initia lization Pattern Type = 0 or 1
2 - 3Initialization Pattern Length (n-3)
76543210
4
...
n
• IP Modifier must be set to 0, indicating that the drive will not modify the initialization pattern.
• SI (Security Initialize) bit set to one specifies that all customer data sectors, including those that have been previously
reassigned, will be initialized. SI set to zero specifies that only the current customer accessible sectors will be formatted.
• Initialization Pattern Type
- Type of 0 will use a default initialization pattern.
- Type of 1 specifies that the Initialization Pattern specified shall be repeated as required to fill each logical block.
• Initialization Pattern Length specifies the number of bytes that follow in the Initialization Pattern field, and must be
less than or equal to the current block size, and non-zero.
- If Initialization Pattern Type is 0 and the Initialization Pattern Length is not set to 0, Check Condition status will be
returned, with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter
List
- If Initialization Pattern Type is 1 and the Initialization Pattern Length is set to 0, Check Condition status will be
returned, with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter
List.
• DSP (Disable Saving Parameters) bit when zero indicates the target is to save all the current MODE SELECT saveable
parameters during the format operation. When the bit is one, the target is not to save the current MODE SELECT
saveable parameters.
• Immed (Immediate) bit set to zero requests that status be returned at the end of the format operation. An immediate bit
set to one requests that status be returned immediately following CDB validation and transfer of data in the Data Out
phase. If the format operation, with the immediate bit set to one, terminates in error, DEFERRED ERROR SENSE
data is generated.
• Defect List Length field specifies the total length in bytes of the defect descriptors that foll ow (not including the Initial-
ization Pattern Descriptor, if any). Up to 1024 defect descriptors are allowed. The Defect List Length must be equal
to four times the number of defect descriptors for BLOCK format, or eight times the number of defect descriptors for
BYTES FROM INDEX and PHYSICAL SECTOR formats. Otherwise the command is terminated with Check Condition status with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter
List.
Initialization Pattern
...
Initialization Pattern
18.4.3 Defect Descriptor
Three defect descriptor formats are supported. Entries are not required to be in ascending order. If an entry does not correspond to a valid user addressable media location, the command terminates with Check Condition status with the sense key set
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
74
Page 91
to Illegal Request and the additional sense code set to Invalid Field in Parameter List.
18.4.3.1 Block Format - 000b
Format of the Dlist sent during the data out phase when Dlist Format is Block format (000b) and FmtData is set to one.
Table 46: Defect Descriptor - Block Format (for n + 1 defects)
ByteBIT
7
6543210
(MSB)
Defective Logical Block Address
0 - 3
(LSB)
4n
4n+1
(MSB)
Defective Logical Block Address n
4n+2
4n+3
(LSB)
The Block format of the Dlist is the LBA of each defective sector.
Note:If a Defective LBA entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
75
Page 92
18.4.3.2 Bytes From Index Format - 100b
Format of the Dlist sent during the data out phase when Dlist Format is Bytes From Index format (100b) and FmtData is set to
one.
Table 47: Defect Descriptor - Bytes From Index Format (for n = 1 defects)
BIT
Byte
76543210
(MSB)
0 - 2
3Head Number of Defect
(MSB)
Cylinder Number of Defect
(LSB)
4 - 7
Defect Bytes from Index
(LSB)
8n
8n + 1
8n + 2
(MSB)
Cylinder Number of Defect n
(LSB)
8n + 3Head Number of Defect n
8n + 4
(MSB)
8n + 5
Defect (n) Bytes from Index
8n + 6
(LSB)
8n + 7
Each defect descriptor for the Bytes From Index format specifies that the sector containing this byte be marked defective. The
defect descriptor is comprised of the cylinder number of the defect, the head number of the defect, and the number of the
defect byte relative to index.
Note:If a Byte From Index entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
76
Page 93
18.4.3.3 Physical Sector Format - 101b
Format of the Dlist sent during the data out phase when Dlist Format is Physical Sector format (101b) and FmtData is set to
one.
Table 48: Defect Descriptor - Physical Sector Format (for n + 1 defects)
Byte
BIT
76543210
0
1
(MSB)
Cylinder Number of Defect
2
3Head Number of Defect
4
(MSB)
5
Defect Sector Number
6
7
8n
8n + 1
(MSB)
Cylinder Number of Defect n
8n + 2
8n + 3Head Number of Defect n
8n + 4
(MSB)
8n + 5
Defect (n) Sector Number
8n + 6
8n + 7
(LSB)
(LSB)
(LSB)
(LSB)
Each defect descriptor for the Physical Sector format specifies a defective sector. The def ect descript or is compri sed of the cylinder number of the defect, the head number of the defect, and the defect’s sector number.
Note:If a Physical Sector entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
The INQUIRY command requests the parameters of the Target to be sent to the Initiator.
An EVPD An EVPD bit of one specifies that the target return the vital product data page identified by the Page Code field in
the CDB The available VPD pages are defined in the addendum provided for each different drive model in the section entitled
Inquiry Data Format.
The Page Code specifies which page of vital product data information the drive shall return.
Table 50: Page Code descriptions
EVPD
0 0 The Target returns the standard INQUIRY data.
0 Non Zero
1Non ZeroThe drive returns the vital product data of page code requested.
Allocation Length specifies the number of bytes that the Initiator has allocated for INQUIRY data to be returned. An alloca-
tion length of zero implies that no data is to be returned. The Target will terminate the DATA IN phase when all available
INQUIRY data has been transferred or when allocation length bytes have been transferred, whichever is less.
Note:If an INQUIRY command is received from an Initiator with a pending unit attention condition (before the target
reports Check Condition status), the Target processes the INQUIRY command. The unit attention condition is not cleared by
this action.
Note:The INQUIRY command is a Priority command and is not queued.
Note:The inquiry data is set at the time of manufacture and will not change, with the following exceptions:
• Product Revision Level (EVPD=0) can be changed when microcod e is downloaded with the Write Buffer command.
• The information returned for EVPD=1, Page Code = 3 is not fixed.
Note: The inquiry data returned when media is not available will not be complete.
Byte 0 of the returned data on an INQUIRY command is the same no matter which page(s) is(are) returned. This description is
to be used for all the following page definitions.
The Peripheral Qualifier field of zero (0) indicates that the peripheral device is currently connected to this logical unit. A
Peripheral Device Type field of zero (0) indicates that this device is a Direct Access Storage Device (DASD).
PAGE
CODE
Description
The drive returns Check Condition status with the sense key of Illegal Request and
the additional sense code of Invalid Field in CDB.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
78
Page 95
18.5.1 Inquiry Data
Fields with a value shown inside quotes (e.g. Value =’xyz’) are character fields. A value not in quotes is a numeric value.
Character fields are alphanumeric and represented in either ASCII.
18.5.1.1 Inquiry Data Format - EVPD = 0, Page Code = 0
Table 51: Inquiry Data- EVPD = 0
BIT
Byte
0 Qualifier = 0Peripheral Device Type = 0
1 RMB = 0 Reserved=0
2 Version = 6
8-23Reserved = 0
24-35ASCII uCode Identifier
36-39ASCII Servo P/N
40-41Major Version
42-43Minor Version
76543210
44-47User Count
48-51Build Number
52-83Build Date String
84-91Product ID
92-99Interface ID
100-107Code Type
108-119User Name
120-135Machine Name
136-167Directory Name
168-171Operating State
172-175Functional Mode
176-179Degraded Reason
180-183Broken Reason
184-187Code Mode
188-191Flash Code Revision Level
• 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.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
82
Page 99
• Page Length field specifies the length (in bytes) of the vendor unique VPD information (bytes 4 - 163). If the allocation length of the
CDB is too small to transfer all the data, the Page Length field is not adjusted to reflect the truncation.
• ASCII uCode Identifier contains the drive’s microcode identifier. The field is alphanumeric (ASCII), left aligned, and the unused
bytes are ASCII spaces (20h).
• ASCII Servo P/N contains the part number of the Servo microcode installed on the drive. This field is hex numeric ASCII (i.e., the
characters will be in the set 0...9, A...F).
• Major Version and Minor Version are version numbers of the code loaded on the drive.
• User Count is the number of times the code has been built since the master build.
• Build Number is the master build version numbe r.
• Build Date String is the date the code on the drive was built, in an extended string format.
• Product ID is the name of the product this code is for.
• Interface ID is the interface type and serial interface speed (e.g. SAS 6Gbps or FCAL 4Gbps) of the code.
• Code Type is the intended use of the this code. (e.g. local, released, test)
• User Name is the username of the person who built this version of the code.
• Machine Name is the workstation on which this version of the code was built.
• Directory Name is the last 32 characters of the directory from where this code was built.
• Operating State is the drive operating state. The least significant bit contains the following:
0 = OM_BROKENWe have detected a hardware failure.
1 = OM_DEGRADEDWe have a soft failure; i.e., incomplete format. Motor is still spinning.
2 = OM_INACCESSIBLEDrive is good but motor is stopped.
3 = OM_STARTINGMotor is starting.
4 = OM_SPINNINGMotor is started but reserved area is not loaded yet.
5 = OM_NORMALDrive is spinning and ready to read/write.
6 = OM_POWERSAVEDrive is ready but has entered power save mode.
7 = OM_STOPPEDDrive has come ready but now has been stopped.
8 = OM_NOTIFY Drive is good but NOTIFY has not arrived (SAS)
9 = OM_SUSPEND Similar to OM_STOPPED, but spin-up is automatic like OM_SLEEP
10 = OM_WAKEUP Similar to OM_STARTING, but LUN BECOMING READY during spinup is not
reported
11 = OM_NOTIFY_WAKEUP Similar to OM_NOTIFY, but next transition is to OM_WAKEUP
• Functional Mode is the drive functional mode. The least significant byte (0x0000000n) contains the following:
0 = OM_NORMAL_MODENot in special or recovery mode.
1 = OM_SPECIAL_CMDSpecial command mode on.
• Degraded Reason (UECType) is why the file is in a degraded mode; i.e., how to exit this mode.
• Bro ken Reason (UECType) is why the drive believes the hardware is broken.
•
Code Mode is the type of code the drive is running. The least significant bit contains the following:
- 0 = OM_FLASHDrive is running flash code
- 1 = OM_FLASH_OVERLAYDrive is running flash overlay code
- 2 = OM_DISKDrive is running code that has been loaded from disk
- 3 = OM_TRANSIENTDrive is running code that has been downloaded but not saved
• Flash Code Revision Level is the revision level of the code in flash.
HGST Ultrastar 7K4000 (SAS) Hard Disk Drive Specification
83
Page 100
18.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h