Technical information

ManualsBrandsHGST ManualsInternal Hard DrivesC15K600 450GB 20 Pack

HGST Ultrastar C15K600 Hard Disk Drive Specification

Hard Disk Drive Specification

Ultrastar C15K600

2.5” SAS Hard Disk Drive

Models

HUC156060CSS200 HUC156060CS4200

HUC156060CSS201 HUC156060CS4201

HUC156060CSS204 HUC156060CS4204

HUC156060CSS205 HUC156060CS4205

HUC156045CSS200 HUC156045CS4200

HUC156045CSS201 HUC156045CS4201

HUC156045CSS204 HUC156045CS4204

HUC156045CSS205 HUC156045CS4205

HUC156030CSS200 HUC156030CS4200

HUC156030CSS201 HUC156030CS4201

HUC156030CSS204 HUC156030CS4204

Version: 1.1

HUC156030CSS205 HUC156030CS4205

25 February 2014

Summary of content (455 pages)

PAGE 1
Hard Disk Drive Specification Ultrastar C15K600 2.
PAGE 2
Revised Edition (Rev 1.1) (25 February 2014) 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 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
PAGE 3
Table of Contents 1 General ............................................................................................................................................................... 20 1.1 Introduction ................................................................................................................................................................. 20 1.2 Glossary ..........................................................................................................................
PAGE 4
8.3 Corrosion Test .............................................................................................................................................................. 36 8.4 Cooling Requirements .................................................................................................................................................. 37 9 DC Power Requirements................................................................................................................................
PAGE 5
15.1 16 Class B Regulatory Notices ........................................................................................................................................... 56 Safety Certification ........................................................................................................................................ 58 16.1 UL and CSA Standard Conformity ................................................................................................................................
PAGE 6
18.7.6 18.7.7 18.7.8 18.7.9 18.7.10 18.7.11 18.7.12 18.7.13 18.7.14 18.7.15 18.7.16 18.7.17 Log Sense Page 6 ............................................................................................................................................... 129 Log Sense Page D ............................................................................................................................................... 130 Log Sense Page E ........................................................................
PAGE 7
18.21.3 18.21.4 18.21.5 18.21.6 18.21.7 Descriptor (Mode 00011b) ................................................................................................................................ 214 Read Data from Echo Buffer (Mode 01010b) .................................................................................................... 214 Echo Buffer Descriptor (Mode 01011b) .............................................................................................................
PAGE 8
18.43 SYNCHRONIZE CACHE (10) - (35) ........................................................................................................................... 264 18.44 SYNCHRONIZE CACHE (16) - (91) ........................................................................................................................... 265 18.45 TEST UNIT READY (00) ........................................................................................................................................... 266 18.
PAGE 9
20.1.10 20.2 Command Processing while Reserved ............................................................................................................... 310 Priority Commands .................................................................................................................................................... 312 20.3 Command Queuing ....................................................................................................................................................
PAGE 10
21.4 Encryption Algorithms ............................................................................................................................................... 334 21.4.1 Advanced Encryption Standard (AES) Support .................................................................................................. 334 21.4.2 Level 0 Discovery Vendor Specific Data ............................................................................................................. 334 21.4.
PAGE 11
23 Appendix. UEC list ....................................................................................................................................
PAGE 12
List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Product ID Table ......................................
PAGE 13
Table 51 Table 52 Table 53 Table 54 Table 55 Table 56 Table 57 Table 58 Table 59 Table 60 Table 61 Table 62 Table 63 Table 64 Table 65 Table 66 Table 67 Table 68 Table 69 Table 70 Table 71 Table 72 Table 73 Table 74 Table 75 Table 76 Table 77 Table 78 Table 79 Table 80 Table 81 Table 82 Table 83 Table 84 Table 85 Table 86 Table 87 Table 88 Table 89 Table 90 Table 91 Table 92 Table 93 Table 94 Table 95 Table 96 Table 97 Table 98 Table 99 Table 100 Table 101 Table 102 Table 103 Table 104 RETRY DELAY TIMER Fi
PAGE 14
Table 105 Table 106 Table 107 Table 108 Table 109 Table 110 Table 111 Table 112 Table 113 Table 114 Table 115 Table 116 Table 117 Table 118 Table 119 Table 120 Table 121 Table 122 Table 123 Table 124 Table 125 Table 126 Table 127 Table 128 Table 129 Table 130 Table 131 Table 132 Table 133 Table 134 Table 135 Table 136 Table 137 Table 138 Table 139 Table 140 Table 141 Table 142 Table 143 Table 144 Table 145 Table 146 Table 147 Table 148 Table 149 Table 150 Table 151 Table 152 Table 153 Table 154 Table 155 Ta
PAGE 15
Table 159 Table 160 Table 161 Table 162 Table 163 Table 164 Table 165 Table 166 Table 167 Table 168 Table 169 Table 170 Table 171 Table 172 Table 173 Table 174 Table 175 Table 176 Table 177 Table 178 Table 179 Table 180 Table 181 Table 182 Table 183 Table 184 Table 185 Table 186 Table 187 Table 188 Table 189 Table 190 Table 191 Table 192 Table 193 Table 194 Table 195 Table 196 Table 197 Table 198 Table 199 Table 200 Table 201 Table 202 Table 203 Table 204 Table 205 Table 206 Table 207 Table 208 Table 209 Ta
PAGE 16
Table 213 Table 214 Table 215 Table 216 Table 217 Table 218 Table 219 Table 220 Table 221 Table 222 Table 223 Table 224 Table 225 Table 226 Table 227 Table 228 Table 229 Table 230 Table 231 Table 232 Table 233 Table 234 Table 235 Table 236 Table 237 Table 238 Table 239 Table 240 Table 241 Table 242 Table 243 Table 244 Table 245 Table 246 Table 247 Table 248 Table 249 Table 250 Table 251 Table 252 Table 253 Table 254 Table 255 Table 256 Table 257 Table 258 Table 259 Table 260 Table 261 Table 262 Table 263 Ta
PAGE 17
Table 267 Table 268 Table 269 Table 270 Table 271 Table 272 Table 273 Table 274 Table 275 Table 276 Table 277 Table 278 Table 279 Table 280 Table 281 Table 282 Table 283 Table 284 Table 285 Table 286 Table 287 Table 288 Table 289 Table 290 Table 291 Table 292 Table 293 Table 294 Table 295 Table 296 Table 297 Table 298 Table 299 Table 300 Table 301 Table 302 Table 303 Table 304 Table 305 Table 306 Table 307 Table 308 Table 309 Table 310 Table 311 Table 312 Table 313 Table 314 Table 315 Table 316 Table 317 Ta
PAGE 18
Table 321 Table 322 Table 323 Table 324 Table 325 Field Replaceable Unit Sense Data Descriptor Format .................................................... 417 Block Command Sense Data Descriptor Format ............................................................... 417 Vendor Unique Unit Error Code Sense Data Descriptor .................................................. 418 Vendor Unique Physical Error Record Sense Data Descriptor ........................................ 418 Unit Error Codes ..............
PAGE 19
List of Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 SAS Connector.......................................................................................................................... 33 Environmental Specification ................................................................................................... 36 Current and Power Requirements .......................................................................................... 39 Power vs IOPS .......................
PAGE 20
1 1.1 General Introduction This document describes the specifications of the following HGST 2.5 inch SAS drives.
PAGE 21
1.2 Glossary Word Meaning BMS Background Media Scan Kb Kilobit = 1000 bits Mb Megabit = 1,000,000 bits Gb Gigabit = 1,000,000,000 bits ESD Electrostatic Discharge Kbpi 1,000 bit per inch Ktpi 1,000 tracks per inch Gbps 1,000,000,000 bits per sec GB 1,000,000,000 bytes (for drive capacity) MB 1,048,576 bytes (for Memory Size) SAS Serial Attached SCSI SFF Small Form Factor S.M.A.R.T.
PAGE 22
2 Outline of the Drive - Data capacities of 600GB/450GB/300GB - Spindle speed of 15030 RPM - Low power Rotating Shaft Spindle Motor - SAS interface 12Gbps, 6Gbps, 3Gbps, 1.5 Gbps - 128MB Memory - SAS Power Down Support (P3) - Dual Stage Actuator - ECS ground - Supports dual-ported operations - Supports full duplex operations - Variable sector sizes of 512, 520, 528, 4096, 4112, 4160, 4224 - Tagged Command Queuing support - Automatic read/write data transfer - 2.
PAGE 23
3 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.
PAGE 24
4 Drive Characteristics 4.
PAGE 25
4.3 4.3.
PAGE 26
4.3.
PAGE 27
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.
PAGE 28
4.4.1.2 Full Stroke Seek Time Common to all models and all seek modes Table 7 Full Stroke Seek Time Function Read Write Typical (ms) 5.9 6.2 Max (ms) 7.3 7.7 Full stroke seek is measured as the average of 1,000 full stroke seeks with a random head switch from both directions (inward and outward). 4.4.1.3 Average Latency Table 8 Latency Time Rotational Speed Time for a Revolution (ms) Average Latency (ms) 15,030 RPM 3.992 1.
PAGE 29
4.4.2 Drive Ready Time Table 9 Drive Ready Time Model Typical (sec) Maximum (sec) 600 GB Model (512n/4kn/512e) 9 15 450 GB Model (512n/4kn/512e) 7 15 300 GB Model (512n/4kn/512e) 6 15 Model Typical (sec) Maximum (sec) 600 GB Model (512n/4kn/512e) 11 15 450 GB Model (512n/4kn/512e) 8 15 300 GB Model (512n/4kn/512e) 8 15 4.4.3 Spindle Stop Time Table 10 Spindle Stop Time The period from power off to the complete stop of the rotating spindle is categorized as ’operating’.
PAGE 30
Table 12 Data Transfer Speed (sector size 4096 Byte case) Description Typical (MB / Sec) Disk - buffer transfer Zone Model Read Write Instantaneous 0 600/450/300 GB 290.4 290.4 Typical values for sustained disk - buffer transfer rate 0 600/450/300 GB 271.3 271.3 Instantaneous 39 600/450/300 GB 202.1 202.1 Typical values for sustained disk - buffer transfer rate 39 600/450/300 GB 188.8 188.8 Notes: • For this table, '1 MB / Sec' is defined as 1,000,000 bytes per Second.
PAGE 31
5 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: - 5.
PAGE 32
6 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.
PAGE 33
7 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 8680. 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.
PAGE 34
P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 7.1.
PAGE 35
8 8.1 Environment Temperature And Humidity Table 14 Operating and Non-operating Conditions Operating Conditions Ambient Temperature 5°C to 55ºC Relative humidity 5 to 90%, non-condensing Maximum wet bulb temperature 29.
PAGE 36
Figure 2 Environmental Specification 8.2 8.2.1 Storage Requirements Packaging The drive or option kit must be heat-sealed in a moisture barrier bag with bag supplied by HGST. 8.2.2 Storage Time Cumulative storage time in the package must not exceed six months. After the drive is unpackaged, it must not remain inoperative for longer than six months. 8.
PAGE 37
8.4 Cooling Requirements Drive component temperatures must remain within the limits specified in the following table. Maximum component temperature ratings must not be exceeded under any operating condition. The drive may require forced air cooling to meet the specified, maximum operating temperatures.
PAGE 38
9 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. Table 16 Input Voltage And Capacitance Supply Tolerance Absolute Max Spike Voltage Supply Rise Time Capacitance 5V +/- 5% 5.
PAGE 39
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 45C.
PAGE 40
Table 17 600 GB, 4K Table 18 600 GB, 512 HGST Ultrastar C15K600 Hard Disk Drive Specification 40
PAGE 41
Table 19 450 GB, 4K Table 20 450 GB, 512 HGST Ultrastar C15K600 Hard Disk Drive Specification 41
PAGE 42
Table 21 300 GB, 4K Table 22 300 GB, 512 HGST Ultrastar C15K600 Hard Disk Drive Specification 42
PAGE 43
Figure 4 Power vs IOPS 9.2 Ripple Voltage Table 23 Power Supply Generated Ripple at Drive Power Connector Maximum (mV pp) MHz +5 V DC 250 0-10 +12 V DC 250 0-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%.
PAGE 44
9.3 Power Consumption Efficiency Index Table 24 Power Consumption Efficiency Index Model Idle_W GB Value 600 5.8 600 0.0096 450 5.1 450 0.0113 300 5.0 300 0.
PAGE 45
10 10.1 Reliability 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”. 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”. 10.
PAGE 46
10.6 MTBF (Mean Time Between Failure): 2.0M 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.
PAGE 47
11 Mechanical Specifications 11.1 Outline 11.2 Mechanical Dimensions The drive complies with SFF-8201. Table 25 Physical Dimensions Height [mm] 14.8 ± 0.2 Width [mm] 70 Length (base) [mm] 100.3 ± 0.15 Length (including connector) [mm] 100.6 ± 0.7 Weight [grams - maximum] 600 GB Model 450/300 GB Model ± 0.
PAGE 48
Figure 5 Top and Side Views and Mechanical Dimensions All dimensions are in millimeters.
PAGE 49
11.3 Interface Connector The interface conforms to the specification SFF-8223, 2.5 Drive Form Factor with Serial Connector. 11.
PAGE 50
11.5 Drive Mounting The drive will operate in all axes (6 directions). Performance and error rate will stay within specification limits if the drive is operated in the other orientations from which it was formatted. The recommended mounting screw torque is 0.45 Nm (4.5 Kgf-cm). The recommended mounting screw depth is 2.5 mm maximum for bottom and 3.0 mm maximum for horizontal mounting.
PAGE 51
12 Vibration and Shock All vibration and shock measurements in this section are made with a bare drive. are applied The input for the measurements to the normal drive mounting points unless noted otherwise. 12.1 Operating Vibration 12.1.1 Random Vibration The drive is designed to operate without unrecoverable errors while being subjected to the vibration levels as defined below.
PAGE 52
No data loss: 30G, 2 ms duration, half sinewave shock pulse, write operation mode The shock pulses of each level are applied to the drive, ten pulses for each direction and for all three mutually perpendicular axes. There must be a minimum of thirty seconds delay between shock pulses. The input level is applied to a base plate where the drive is attached using four mounting screws. 12.
PAGE 53
13 Acoustics 13.1 Sound Power Levels The upper limit criteria of A-weighted sound power levels are given in Bel, relative to one pico watt, and are shown in the following table. The measurement method is in accordance with ISO-7779. Table 26 A-weighted Sound Power Levels A-weighted Sound Power Level (Bel) Model 1200 GB Mode Typical Maximum Idle 3.2 3.4 Operating 3.8 4.1 Background power levels of the acoustic test chamber for each octave band are to be recorded.
PAGE 54
14 14.1 Identification Labels 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.
PAGE 55
15 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.
PAGE 56
KN 61000-4-3:2011-10 Electrical Fast Transient/Burst (EFT/B) Immunity KN 61000-4-4:2011-10 Surge Immunity KN 61000-4-5:2008-05 Conducted RF Immunity KN 61000-4-6:2013-06 Power Frequency Magnetic Field Immunity KN 61000-4-8:2013-06 Voltage Dips and Interruptions Immunity KN 61000-4-11:2008-05 15.
PAGE 57
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 2004/108/EC in der Bundesrepublik Deutschland. Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagneti-sche Verträglichkeit von Geräten (EMVG) vom 20 July 2007 (bzw.
PAGE 58
16 Safety Certification The following shows the safety standards for different countries. 16.1 UL and CSA 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, 2011-12-19 and in Canada per CSA C22.2 No. 60950-1-07, Second Edition, 2011-12.
PAGE 59
17 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.
PAGE 60
• 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 - Maximum outstanding credit of four per port • Physical Link Rates - G1 (1.5 Gbs), G2 (3.0 Gbps), G3 (6.0 Gbps), and G4 (12.
PAGE 61
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.
PAGE 62
The Name Address Authority field (5h) specifies the format used for the rest of the name as follows: Field OUI Block Assignment Object S/N Description Organizationally Unique Identifier (24 bits). Canonical form means that each byte is stored in “bit reversed” order. Block assignment within HGST, a Western Digital Company Device Name/Port Identifier 00b Device 01b Port 1 10b Port 2 11b Not assigned Sequentially increasing drive serial number assigned at manufacturing.
PAGE 63
17.4 PHY Layer The PHY layer defines 8b10b encoding 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, SPL-3. 17.4.1 Link Reset Sequence The Link Reset sequences for SAS are defined in the SPL-3 ANSI specification with a general overview shown below.
PAGE 64
17.4.2 Hard Reset A Hard Reset sequence on a port will not affect the other port, but the outstanding commands on the other port will be aborted due to the LUN reset associated with the Hard Reset. The effect of a Hard Reset will be similar to a Power on Reset, and will result in the re-initialization of all drive resources.
PAGE 65
17.4.4 SAS Speed Negotiation The drive supports G1 (1.5 Gbps), G2 (3.0 Gbps), G3 (6.0 Gbps), and G4 (12.0 Gbps) negotiation speeds. The default maximum negotiation rate is G4 speed (per byte 32 in the PHY Control and Discover Mode Page 19 subpage 1). Drive is SAS3 device and supports SNW-1, SNW-2, SNW-3 speed negotiation with PHY capabilities exchange, and both transmitter training (Train_Tx-SNW, at 12G only) and receiver training (Train_Rx-SNW or Train-SNW).
PAGE 66
… G1 With SSC bit G1 Without SSC bit Lowest HGST Ultrastar C15K600 Hard Disk Drive Specification 66
PAGE 67
17.4.5 PHY Error Handling This section defines the PHY layer error handling of the drive. Table 32 PHY Layer Error Handling 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.
PAGE 68
17.5 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, SPL-3. 17.5.1 Address Frames Address frames are used for the identification sequence and for connection requests and are only sent outside connections.
PAGE 69
17.5.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.
PAGE 70
 Requested Inside ZPSDS: set to 0b since this is an "End Device"  Break_Reply Capable: set to 1b to indicate that this port is capable of sending BREAK_REPLY primitive sequence in responding of receiving BREAK primitive sequences  Pwr_DIS Capable is set to 1b to indicate the drive does support the PWR_DIS signal as defined in SAS-3 HGST Ultrastar C15K600 Hard Disk Drive Specification 70
PAGE 71
Table 36 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.5.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.
PAGE 72
 Initiator Connection Tag is set by the drive to the last value received from this Initiator.  Destination SAS Address contains the port identifier of the SAS port to which a connection is being requested.  Source SAS Address contains the port identifier on the port that originated this frame (i.e. the drive’s port address).
PAGE 73
Table 39 Link Layer Error Handling (part 2 of 2) Error Error Handling Procedure OPEN_REJECT OPEN_REJECT – Retry-able Variations • OPEN_REJECT(RETRY) - Will be retried indefinitely by the drive. This case is considered to occur when the initiator is temporarily not available to accept connections • OPEN_REJECT(RATE_NOT_SUPPORTED) – If this occurs, it must mean that a link between the drive and initiator negotiated to a lower link rate after the command was received.
PAGE 74
17.6 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, SPL-3.
PAGE 75
 FRAME TYPE field, which defines the format of the INFORMATION UNIT field as follows: Table 41 FRAME TYPE Field Code Name of Frame Information Unit Originator IU Size (bytes) 01h DATA Data Initiator or Target 1-1024 05h XFER_RDY Data Transfer Ready Target 12 06h COMMAND Command Initiator 28-284 07h RESPONSE Response Target 24-1024 16h TASK Task Management Function Initiator 28 f0-ffh Vendor Specific all others Reserved  Hashed Destination SAS Address contains the hashed
PAGE 76
17.6.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 42 COMMAND Information Unit Bit Byte 7 6 5 4 0-7 Logical Unit Number 8 Reserved 9 Disable First Burst=0 Reserved 10 3 2 1 0 Task Attribute Reserved 11 Additional CDB Length (in Dwords) 12-27 CDB 28-n Additional CDB Bytes Reserved  Logical Unit Number contains the address of the logical unit. The drive only supports a LUN of 0’s.
PAGE 77
17.6.2 TASK Information Units Table 44 TASK Information Unit Bit Byte 7 6 5 4 3 2 0-7 Logical Unit Number 8-9 Reserved 10 Task Management Function 11 Reserved 12-13 Tag of Task to be Managed 14-27 Reserved 1 0  Logical Unit Number field contains the address of the logical unit. The drive only supports a LUN of 0’s.
PAGE 78
others RESERVED: The Drive will return a RESPONSE frame with the DATAPRES field set to RESPONSE_DATA and its RESPONSE CODE field set to TASK MANAGEMENT FUNCTION NOT SUPPORTED.
PAGE 79
 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 45.
PAGE 80
17.6.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 48 XFER_RDY Information Units Bit Byte 7 6 5 4 3 2 0-3 Requested Offset 4-7 Write Data Length 8 - 11 Reserved 1 0  Requested Offset contains the buffer offset 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.
PAGE 81
0 - (n-1) Data HGST Ultrastar C15K600 Hard Disk Drive Specification 81
PAGE 82
17.6.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).
PAGE 83
Table 52 RETRY DELAY TIMER Field (part 2 of 2) Status Code Retry Delay Timer Code Description CHECK CONDITION 0000h-FFFFh Reserved CONDITION MET 0000h-FFFFh Reserved RESERVATION CONFLICT 0000h-FFFFh Reserved ACA ACTIVE 0000h-FFFFh Reserved TASK ABORT 0000h-FFFFh Reserved  DataPres indicates the format and content of the STATUS field, SENSE DATA LENGTH field, RESPONSE DATA LENGTH field, RESPONSE DATA field, and SENSE DATA field.
PAGE 84
09b Invalid LUN others Reserved 17.6.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.
PAGE 85
17.6.7 Transport Layer Error Handling This section defines the Transport layer error handling by the drive. Table 56 Transport Layer Error Handling Error Error Handling Procedure SSP Header Field Checking Reserved fields in SSP frames are not checked.
PAGE 86
18 SCSI Command Set Summaries of the SCSI commands supported by the drive are listed below.
PAGE 87
Table 58 SCSI Commands Supported (part 2 of 2) Type Code Description O 56h RESERVE (56) O 01h REZERO UNIT (01) O 48h SANITIZE (48) M 1Dh SEND DIAGNOSTIC (1D) O A4h/06h O 1Bh START STOP UNIT (1B) O 35h SYNCHRONIZE CACHE (10) - (35) O 91h SYNCHRONIZE CACHE (16) - (91) M 00h TEST UNIT READY (00) O 2Fh VERIFY (10) - (2F) O AFh VERIFY (12) - (AF) O AFh VERIFY (16) - (8F) O 7Fh/0Ah M 0Ah WRITE (6) - (0A) M 2Ah WRITE (10) - (2A) O AAh WRITE (12) - (AA) O 8Ah WRITE
PAGE 88
18.1 SCSI Control Byte The Control Byte is the last byte of every CDB. The format of this byte is shown below. VU = VU stands for Vendor Unique. Table 59 SCSI Control Byte Bit 7 6 5 VU = 0 4 3 2 1 0 Reserved = 0 Note: * - The drive ignores the link bit and flag bit in the CDB. 18.2 Abbreviations These abbreviations are used throughout the following sections: LUN Logical Unit Number. An encoded three bit identifier for the logical unit.
PAGE 89
18.4 FORMAT UNIT (04) Table 60 FORMAT UNIT Bit Byte 7 6 5 0 1 4 3 1 0 Command Code = 04h FMTPINFO LONG LIST=0 FMTDATA CMPLIST 2 VU = 0 3-4 Obsolete = 0 5 2 VU = 0 Defect List Format 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 protection information (see table defined in the Parameter List Header section).
PAGE 90
- 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.
PAGE 91
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.
PAGE 92
Type 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. Type 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).
PAGE 93
- 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. 18.4.
PAGE 94
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 to Illegal Request and the additional sense code set to Invalid Field in Parameter List. 18.4.3.
PAGE 95
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.
PAGE 96
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.
PAGE 97
18.5 INQUIRY (12) Table 69 INQUIRY (12) Bit Byte 7 6 5 0 4 3 2 1 0 CmdDt =0 EVPD FLAG LINK Operation Code = 12h 1 Reserved = 0 2 Page Code 3-4 Allocation Length 5 VU = 0 Reserved = 0 The INQUIRY command requests the parameters of the Target to be sent to the Initiator.
PAGE 98
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.
PAGE 99
- SCCS bit of zero indicates that the device does not contain an embedded storage array controller component. - ACC bit of zero indicates that no access controls coordinator may be addressed through this logical unit. - TGPS field of zero indicates that the device does not support asymmetric logical unit access. - 3PC bit of zero indicates that the device does not support third-party copy commands.
PAGE 100
18.5.1.
PAGE 101
18.5.1.
PAGE 102
- Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to zero to indicate that the device is Direct Access. - Page Code is set to the value of the page code field in the CDB. - - Page Length field specifies the length (in bytes) of the vendor unique VPD information (bytes 4 - 163).
PAGE 103
18.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h Table 74 Inquiry Data - EVPD = 1 (Page Code = 80h) Bit Byte 7 0 6 Qualifier = 0 5 4 3 2 1 0 Peripheral Device Type = 0 1 Page Code = 80h 2 Reserved = 0 3 Page Length = 16 (10h) 4-19 Serial Number (ASCII) - 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 104
18.5.1.
PAGE 105
Table 76 Inquiry Data Format - EVPD = 1, (Page Code - 83h) (part 2 of 2) Bit Byte 7 48 6 5 4 3 2 Protocol Identifier = 0h 49 PIV=0 RSVD 1 0 Code Set = 3 Association=2 Identifier Type = 8 50 Reserved = 0 51 Identifier Length =24 (18h) 52-55 "naa" (ASCII) (MSB) 56-71 Target Device Name Identifier (World Wide ID) in ASCII (LSB) 72-75 - Reserved = 0 Protocol Identifier is valid only when PIV=1.Protocol Identifier = 0 indicates Fibre Channel devices.
PAGE 106
18.5.1.
PAGE 107
- WRITE BUFFER command with the MODE field set to 0Dh and the PO_ACT bit set to one. HRA_SUP (Hard Reset Activation Supported) bit is set to zero to indicate that the device server does not support a WRITE BUFFER command with the MODE field set to 0Dh and the HR_ACT bit set to one. VRA_SUP (Vendor Specific Activation Supported) bit is set to zero to indicate that the device server does not support a WRITE BUFFER command with the MODE field set to 0Dh and the VSE_ACT bit set to one.
PAGE 108
18.5.1.
PAGE 109
- Code Set specifies the data type for the identifier field. Code Set = 1 indicates binary data - PIV (Protocol Identifier Valid) set to one indicates that the Protocol Identifier field contains a valid value. - Association specifies the entity with which the Identifier field is associated: 1h for Target or Relative Port. - Identifier Type specifies the format and assignment authority for the identifier: 3h indicates NAA format of the WWID for Target Port.
PAGE 110
18.5.1.10 Inquiry Data - EVPD = 1, Page Code - 90h Table 81 Inquiry Data - EVPD = 1 (Page Code = 90h) Bit Byte 7 0 6 5 4 3 Qualifier = 0 2 1 0 Peripheral Device Type = 0 1 Page Code = 90h 2-3 Page Length = 24 (0018h) 4-15 Protocol-specific logical unit information descriptor 0. 16-27 Protocol-specific logical unit information descriptor 1. - Qualifier field is set to zero to indicate that the LUN specified in the Command Block is currently supported.
PAGE 111
1 Page Code = 91h 2-3 Page Length = 24 (0018h) 4-15 Port Information Descriptor 0 16-27 Port Information Descriptor 1 - Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to zero to indicate that the device is Direct Access. - Page Code is set to the value of the page code field in the CDB. - Page Length is set to 24, and this field specifies the length of the following page data.
PAGE 112
- PHY Identifier is set to 0 for Port A (Primary Port) or 1 for Port B (Secondary Port).
PAGE 113
18.5.1.
PAGE 114
- implement the UNMAP command. Optimal Unmap Granularity: set to 0000_0000h to indicate that the optimal unmap granularity is not specified. UGAVALID - Unmap Granularity Alignment VALID: set to zero indicates that the UNMAP GRANULARITY ALIGNMENT field is not valid. Unmap Granularity Alignment: set to zero and is not valid. Maximum Write Same Length: set to zero which indicates that there is no reported limit on the number of logical blocks that may be requested for a single WRITE SAME command. 18.5.1.
PAGE 115
18.5.1.
PAGE 116
18.5.1.
PAGE 117
18.5.1.
PAGE 118
18.6 LOG SELECT (4C) Table 91 Log Select (4C) Bit Byte 7 6 5 0 4 3 1 0 PCR SP Command Code = 4Ch 1 Reserved = 0 2 PC Reserved = 0 Page Code 3 SubPage Code = 0 4-6 Reserved = 0 7 2 (MSB) Parameter List Length = 0 8 9 (LSB) Reserved = 0 FLAG LINK The LOG SELECT command provides a means for the Initiator to clear statistical information maintained by the drive and reported via the LOG SENSE command.
PAGE 119
with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB. Note: A specified length greater than 0x00FF will result in a Check Condition status being returned. A length that results in log data being truncated will generate a Check Condition status. Note: For page 0Fh, the maximum parameter list length supported is 4004h (4 bytes for the header and 100h bytes for each of the 40h parameters that are supported).
PAGE 120
- Total errors recovered - Number of times recovery invoked - Total bytes verified - LBAs with hard error.
PAGE 121
18.7 LOG SENSE (4D) Table 92 Log Sense (4D) Bit Byte 7 6 5 0 4 3 Reserved = 0 2 PC Reserved = 0 Subpage Code = 0 4 Reserved = 0 9 0 PPC=0 SP Page Code 3 7 8 1 Command Code = 4Dh 1 5 6 2 (MSB) Parameter Pointer (LSB) (MSB) Allocation Length (LSB) Reserved = 0 FLAG LINK The LOG SENSE command allows the Initiator to retrieve the statistical data regarding the drive. - PPC (Parameter Pointer Control) bit must be set to zero.
PAGE 122
18.7.1 Log Page parameters Each log page begins with a 4-byte page header followed by zero or more variable-length log parameters. Page header Page Code field identifies which log page is being transferred. The Page Length field specifies the length in bytes of the following log parameters. Log parameters Each log parameter begins with a 4-byte parameter header followed by one or more bytes of parameter value data.
PAGE 123
18.7.2 Log Sense Page 0 Page 0 indicates the supported log sense pages. This page is used to determine which additional pages and Initiator can request.
PAGE 124
18.7.3 Log Sense Page 2 This page contains counters for write errors.
PAGE 125
Table 95 Log Sense Page 2 (part 2 of 2) Bit Byte 7 6 5 64-65 66 4 3 1 0 Parameter Code = 0005h DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 67 Parameter Length = 08h 68-75 Total bytes written 76-77 Parameter Code = 0006h 78 2 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 79 Parameter Length = 08h 80-87 Count of hard errors F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of
PAGE 126
18.7.4 Log Sense Page 3 This page contains counters for read errors.
PAGE 127
Table 97 Log Sense Page 3 (part 2 of 2) Bit Byte 7 66 DU = 0 6 5 4 DS = 0 TSD = 0 ETC = 0 3 TMC = 0 67 Parameter Length = 08h 68-75 Total bytes read 76-77 Parameter Code = 0006h 78 DU = 0 DS = 0 TSD = 0 ETC = 0 2 TMC = 0 79 Parameter Length = 08h 80-87 Count of hard errors 1 0 F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of all recovery steps attempted on all s
PAGE 128
18.7.5 Log Sense Page 5 This page contains counters for verify errors.
PAGE 129
Table 99 Log Sense Page 5 (part 2 of 2) Bit Byte 7 66 DU = 0 6 5 4 3 DS = 0 TSD = 0 ETC = 0 TMC = 0 67 Parameter Length = 08h 68-75 Total Bytes Verified 76-77 Parameter Code = 0006h 78 DU = 0 DS = 0 2 TSD = 0 TMC = 0 79 Parameter Length = 08h 80-87 Count of hard errors 1 0 F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of all recovery steps attempted on all sect
PAGE 130
18.7.7 Log Sense Page D This page contains temperature information. Table 101 Log Sense Page D Bit Byte 7 0 6 5 4 3 Reserved 2 Reserved 2-3 Page Length = 0Ch 4-5 Parameter Code = 0000h DU = 0 DS = 1 TSD = 0 ETC = 0 TMC = 0 7 Parameter Length = 02h 8 Reserved 9 Temperature (degrees Celsius) 10-11 Parameter Code 0001h 12 DU = 0 DS = 1 TSD = 0 ETC = 0 F&L = 00b TMC = 0 F&L = 00b 13 Parameter Length = 02h 14 Reserved 15 Reference Temperature (degrees Celsius) 18.7.
PAGE 131
Table 103 Log Sense Page E (part 2 of 2) Bit Byte 7 6 5 4 3 2 12-13 Week of Manufacture (2 ASCII characters) 14-15 Parameter Code 0002h 16 DU=0 DS=0 TSD=0 ETC=0 TMC = 0 17 Parameter Length = 06h 18-21 Accounting Date Year (4 ASCII characters) 22-23 Accounting Date Week (2 ASCII characters) 24-25 Parameter Code 0003h 26 DU=0 DS=1 TSD=0 ETC=0 TMC = 0 27 Parameter Length = 04h 28-31 Specified cycle count over device lifetime 32-33 Parameter Code 0004h 34 DU=0 DS=1 TSD=0
PAGE 132
18.7.9 Log Sense Page F This page contains the Application Client Log. Table 104 Log Sense Page F Bit Byte 7 0 6 5 4 Reserved 3 2 0 1 Page code = 0Fh Reserved 1 2-3 Page length = 4000h Application client log parameter 4-259 1st application client log parameter 16132-16387 64th application client log parameter The following table describes the application client log parameter structure.
PAGE 133
18.7.10 Log Sense Page 10 This page contains self-test results. The results of the 20 most recent self-tests are stored in this Log page.
PAGE 134
Table 108 Log Sense Page 10, self-test results Value 0h The self-test routine completed without error. 1h The background self-test routine was aborted by the initiator using a SEND DIAGNOSTIC command with the Abort Background self-test function. 2h The self-test routine was aborted by the application client by a Task Management function or a reset. 3h An unknown error occurred while the Target was executing the self-test routine and the Target was unable to complete the self-test routine.
PAGE 135
command and Power on Diagnostics. 18.7.11 Log Sense Page 15 This page contains information about Background Medium Scan operations. Table 110 Log Sense Page 15 Bit Byte 7 0 6 5 4 3 Reserved 2 1 0 1 0 Page code = 15h 1 Reserved 2-3 Page Length = (19 + 24N -3) Background Medium Scan parameters 4-19 BMS Status Parameter 20-43 First Medium Scan Parameter ... 19+24N Last Medium Scan Parameter The following table describes the BMS Status Parameter structure.
PAGE 136
Table 112 BMS Status BMS Status Description 00h No scans active 01h Background medium scan is active 03h-04h 05h Background scan halted due to medium formatted without P-List 06h Background scan halted due to a vendor-specific cause 07h Background scan halted due to temperature out of range 08h Scan suspended until BMS Interval Timer expires 09h - FFh - - Not supported Reserved The Number of Background Scans Performed field indicates the total number of back ground scans (i.e.
PAGE 137
Table 113 Medium Scan Parameter structure Bit Byte 7 6 5 0-1 4 3 2 1 0 Parameter Code = 0001h - 0800h 2 DU=0 DS=0 TSD=0 ETC=0 TMC=0 3 Page Length = 14h 4-7 Power On Minutes 8 Reassign Status F&L = 11b Sense Key 9 Additional Sense Code 10 Additional Sense Code Qualifier 11 Head (MSB) Cylinder (MSB) 12-13 Cylinder (LSB) (MSB) 14-15 Sector (LSB) 16-23 LBA - Power On Minutes indicates the total power on minutes at the time the error was detected.
PAGE 138
18.7.12 Log Sense Page 18 This page contains protocol-specific log parameters.
PAGE 139
Table 117 SAS Log Descriptor (part 2 of 3) Bit Byte 7 6 5 4 3 2 1 0 14 Reserved Attached Attached Attached SSP STP SMP Reserved Initiator Port Initiator Port Initiator Port 15 Reserved Attached SSP Target Port Attached STP Target Port Attached SMP Target Port Reserved (MSB) 16-23 SAS Address (the address of the target port) (LSB) (MSB) 24-31 Attached SAS Address (the address received in the incoming IDENTIFY) (LSB) Attached PHY Identifier (the PHY identifier received in the incoming IDEN
PAGE 140
(LSB) HGST Ultrastar C15K600 Hard Disk Drive Specification 140
PAGE 141
Table 118 SAS Log Descriptor (part 3 of 3) Bit Byte 7 6 5 4 3 72-74 Reserved 75 PHY Event Source (02h) (Running Disparity Error Count) 2 1 0 (MSB) 76-79 PHY Event (LSB) (MSB) 80-83 Peak Value Detector Threshold (00h) (LSB) 84-86 Reserved 87 PHY Event Source (03h) (Loss of Dword Sync) (MSB) 88-91 PHY Event (LSB) (MSB) 92-95 Peak Value Detector Threshold (00h) (LSB) 96-98 Reserved 99 PHY Event Source (04h) (PHY Reset Problem) (MSB) 100-103 PHY Event (LSB) (MSB) 104-107 Peak Valu
PAGE 142
                 - set to Bh when the PHY is enabled and the negotiated speed is 12.0G The Generation Code is a one-byte counter that shall be incremented by one by the device server every time the values in this mode page or the SAS-3 PHY mode page field values are changed. A GENERATION CODE field set to 00h indicates the generation code is unknown. The device server shall wrap this field to 01h as the next increment after reaching its maximum value (i.e., FFh).
PAGE 143
18.7.
PAGE 144
- Idle Time Intervals indicates the cumulative number of idle times spent while there are no commands in the task set and there are no commands being processed by the logical unit. Idle time is calculated using the time interval in parameter 0003h: idle time = (time increments not processing commands x time interval) The time interval descriptor contains the time interval in seconds.
PAGE 145
18.7.
PAGE 146
18.7.15 Log Sense Page 2F This page contains SMART Status and Temperature Reading.
PAGE 147
18.7.16 Log Sense Page 30 This page contains Performance Counters.
PAGE 148
command determines which seek counter is incremented. The Zero Seek counter is incremented if a seek is not required or if only a head switch is required to access the first Logical Block. After the initial seek, no further counter incrementing is performed for that command. Note: The length of a seek as reported in page 30 may differ from expected results. The reason for this is that the drive executes Idle Time Functions between operations of the drive.
PAGE 149
- DEVICE CACHE FULL READ HITS The number of times that all of the data requested by the read operation was obtained from the device read or write cache. - DEVICE CACHE PARTIAL READ HITS The number of times that a portion, but not all, of the data requested by the read operation was obtained from the device read or write cache. A physical operation to the device media was required to obtain the remaining data.
PAGE 150
18.7.17 Log Sense Page 37 This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.
PAGE 151
HGST Ultrastar C15K600 Hard Disk Drive Specification 151
PAGE 152
18.8 MODE SELECT (15) Table 125 Mode Select (15) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 15h 1 Reserved = 0 PF=1 Reserved = 0 2 3 Reserved = 0 4 Parameter List Length 5 VU = 0 Reserved = 0 SP FLAG LINK The MODE SELECT (15) command provides a means for the Initiator to specify LUN or device parameters to the Target. It also allows an Initiator to specify options the Target uses in error recovery, caching, and formatting.
PAGE 153
18.9 MODE SELECT (55) Table 126 Mode Select (55) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 55h 1 Reserved = 0 2-6 PF=1 Reserved = 0 SP Reserved = 0 (MSB) 7-8 Parameter List Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The MODE SELECT (55) command provides a means for the Initiator to specify LUN or device parameters to the Target. See the MODE SELECT (15) command for a description of the fields in this command.
PAGE 154
18.10 MODE SENSE (1A) Table 127 Mode Sense (1A) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 1Ah 1 Reserved= 0 2 PCF RSVD DBD Page Code 3 Subpage Code 4 Allocation Length 5 VU = 0 Reserved = 0 Reserved = 0 FLAG LINK The MODE SENSE (1A) command provides a means for the drive to report various device parameters to the Initiator. It is the complement to the MODE SELECT command. If the DBD (Disable Block Descriptor) bit is zero, the Target will return a Block Descriptor.
PAGE 155
- 1 1 Report saved value. The drive returns the saved value for the page code specified. Saved values are one of the following: - the values saved as a result of MODE SELECT command - identical to the default values - zero when the parameters are not supported The Page Length byte value of each page returned by the drive indicates up to which fields are supported on that page. Page Code: This field specifies which page or pages to return. Page code usage is defined in the figure below.
PAGE 156
18.10.1 Mode Parameter List The mode parameter list contains a header followed by zero or one block descriptors followed by zero or more variable length pages. 18.10.1.1 Header The header used for the 6-byte CDB is defined below. Table 129 Mode parameter header (6) Bit Byte 7 6 5 4 3 2 0 Mode Data Length 1 Medium Type = 0 2 WP=0 Reserved=0 DPOFUA = 1 3 1 0 Reserved = 0 Block Descriptor Length (= 0 or 8) The header used for the 10-byte CDB is defined below.
PAGE 157
supported by the Target, respectively corresponding to an absent Block Descriptor, a single Short LBA Block Descriptor, and a single Long LBA Block Descriptor. Note: DPOFUA is ignored during Mode Select command processing although the SCSI Standard states that it is reserved during Mode Select. Ignoring it allows the Mode Sense Parameter List for the byte containing this bit to be re-used as a Mode Select Parameter List. 18.10.1.
PAGE 158
18.10.1.3 Page Descriptor Table 133 Mode Parameter Page Format Byte 0 PS SPF Page Code Byte 1 Page Length Byte 2-n Mode Parameters Each mode page contains a page code, a page length, and a set of mode parameters. When using the MODE SENSE command, a Parameter Savable (PS) bit of one indicates that the mode page can be saved by the drive in the reserved area of the drive. A PS bit of zero indicates that the supported parameters cannot be saved.
PAGE 159
18.10.
PAGE 160
- - - - - - - - - IGRA (Ignore Reassigned LBA) bit works in conjunction with the RC bit (Mode Page 01h, byte 2, bit 4).The main purpose of this bit is to avoid undesirable read processing time delays due to reassigned LBA processing for continuous data availability requirements such as Audio Visual applications. If IGRA is set to one and RC is set to one, out-of-line reassigned LBAs will not be processed.
PAGE 161
18.10.
PAGE 162
- - to continue when recovered errors are encountered. DCR - Reserved Read Retry Count sets a limit on the amount of DRP passes in which the Target attempts to recover read errors. A value of zero disables all data recovery procedures. When AVERP bit (Mode Page 0 Byte 6 Bit 6) is zero, a value of non-zero in Read Retry Count enables all steps of DRP. When AVERP bit is one, the number in Read Retry Count sets the maximum retry count of DRP.
PAGE 163
PERDTEDCRTB DESCRIPTION 0000 Retries and Error Correction are attempted. Recovered or corrected data (if any) or both are transferred with no Check Condition status at the end of the transfer. no err The transfer length is exhausted. soft err The transfer length is exhausted. Transferred data includes blocks containing recovered errors. hard err Data transfer stops when an unrecoverable error is encountered. The unrecoverable block is not transferred to the Initiator.
PAGE 164
0100 Illegal Request-DTE must be zero when PER is zero. 0101 Illegal Request-DTE must be zero when PER is zero. 0110 Illegal Request-DTE must be zero when PER is zero. 0111 Illegal Request-DTE must be zero when PER is zero. 1000 The highest level error is reported at the end of transfer. Retries and error correction are attempted. Recovered or corrected data (if any) or both are transferred with Check Condition status and Recovered Error sense key set at the end of the transfer.
PAGE 165
attempted. Recovered or corrected data (if any) or both are transferred with Check Condition status and Recovered Error sense key set at the end of the transfer. no err The transfer length is exhausted. soft err The transfer stops on the first soft error detected. The information in the sense data shall contain the LBA of the block in error. hard err Data transfer stops on the unrecoverable error. The unrecoverable error block is returned to the Initiator.
PAGE 166
18.10.
PAGE 167
- there is no limit on the amount of data transferred per data transfer operation. First Burst Size is not supported.
PAGE 168
18.10.
PAGE 169
- Tracks per Zone specifies the number of tracks within the zone. This field is a function of the active notch. - Sectors per Track specifies the number of physical sectors within each track. This field is a function of the active notch. Data Bytes per Physical Sector specifies the number of user data bytes per physical sector. The value depends upon the current formatted Block Length. Interleave value of 1 or 0 is valid. However, the drive will ignore this.
PAGE 170
18.10.
PAGE 171
18.10.
PAGE 172
18.10.
PAGE 173
but before writing it to the media. When WCE = 1, the drive operates as if AWRE = 1. Note: When WCE = 1, a SYNCHRONIZE CACHE command must be done to ensure data are written to the media before powering down the Target. - MF (Multiplication Factor) bit determines how the Maximum and Minimum Pre-fetch parameters are interpreted. If this bit is set to zero, the parameters are used as is. If the bit is set to one, the parameters are multiplied by the number of blocks requested in the Read Command.
PAGE 174
18.10.
PAGE 175
- - - - - Allegiance (CA condition) is pending. Those blocked tasks are allowed to resume execution in a normal fashion after the CA condition is cleared. 01b: Specifies that all tasks from all Initiators are aborted when the Target returns Check Condition status. A unit attention condition will be generated for each Initiator that had commands in the queue except for the Initiator that received the Check Condition status.
PAGE 176
18.10.9.
PAGE 177
18.10.9.2 Control Extension Subpage 02h Table 144 Application Tag mode page: Bit Byte 0 7 6 5 PS SPF=1 4 3 2 1 0 1 0 Page Code = 0Ah 1 Subpage Code = 02h 2-3 Page Length = n-4 4-15 Reserved = 0 16-39 Application Tag descriptor [first] ... ...
PAGE 178
additional sense code set to INVALID FIELD IN PARAMETER LIST. - The LOGICAL BLOCK COUNT field specifies the number of logical blocks to which this Application Tag descriptor applies. - A LOGICAL BLOCK COUNT field set to 0000_0000_0000_0000h specifies that this Application Tag descriptors hall be ignored. Busy Timeout Period is not supported and is ignored.
PAGE 179
18.10.
PAGE 180
- - Mode Page 3 - Alternate Sector per Zone - Alternate Track per Zone - Alternate Track per Logical Unit - Sector per Track - Track Skew Factor - Cylinder Skew Factor Starting Boundary contains the first physical location of the active notch. The first three bytes are the cylinder number and the last byte is the head. The value sent in this field is ignored. Ending Boundary contains the last physical location of the active notch.
PAGE 181
18.10.12 Mode Page 19h (Port Control Parameters) The Protocol-Specific Port mode page contains parameters that affect SSP target port operation. There is one copy of the mode page shared by all SSP initiator ports. 18.10.12.
PAGE 182
 TIMEOUT expires, the associated command will be aborted. An INITIATOR RESPONSE TIMEOUT field value of zero indicates that the SSP target port shall disable the timer. This value is enforced by the transport layer. The default value of 7D0h, specifies a 2 second time period.
PAGE 183
18.10.12.3 PHY Control and Discover (Subpage 1) Table 150 PHY Control and Discover (Subpage 1) Bit Default Byte 0 7 6 5 PS SPF=1 1 4 3 2 1 0 Page Code = 19h D9h Subpage Code = 1 01h (MSB) Page Length = 0064h 2-3 0064h (LSB) 4 5 Reserved Reserved 00h Protocol Identifier = 6h 06h 6 Generation Code 00h 7 Number of PHYS = 2 02h 8-55 SAS PHY Mode Descriptor 0 ... 56-103 SAS PHY Mode Descriptor 1 ... The PHY Control and Discover subpage contains PHY-specific parameters.
PAGE 184
Table 151 SAS PHY Mode Descriptor Bit Byte 7 6 5 4 3 2 0 Reserved 1 PHY Identifier 1 0 (MSB) Reserved 2-3 4 (LSB) Reserved 5 Attached Device Type Attached Reason Reason Negotiated Logical Link Rate 6 Reserved Attached SSP Initiator Port 7 Reserved Attached SSP Target Port Attached STP Initiator Port Attached SMP Initiator Port Attached STP Target Port Attached STP Target Port Reserved Reserved (MSB) SAS Address 8-15 (LSB) (MSB) Attached SAS Address 16-23 (LSB) 24 25 Att
PAGE 185
                 PHY Identifier indicates the unique PHY Identifier for the PHY associated with the other data in this SAS PHY Mode Descriptor Page. Attached Reason indicates the value of the REASON field in the last received IDENTIFY address frame associated with the PHY Identifier list in this SAS PHY Mode Descriptor. See Table 34.
PAGE 186
5  Reserved Protocol Identifier = 6 06h 6-7 Power Loss Timeout 0000h 8 - 15 Reserved 00h Power Loss Timeout is the maximum time, in one millisecond increments, that the drive port will respond to connection requests with OPEN_REJECT(RETRY) after receiving NOTIFY(POWER LOSS EXPECTED).The Power Loss Timeout will be restarted after each NOTIFY(POWER LOSS EXPECTED) that is received.
PAGE 187
18.10.12.
PAGE 188
 PHY Capabilities are defined under the “SAS Speed Negotiation” 18.10.
PAGE 189
power management - CCF Idle CHECK CONDITION if from idle, 00b: restricted. 01b Returning CHECK CONDITION status if transition was from an idle power condition is disabled. 10b: Returning CHECK CONDITION status if transition was from an idle power condition is enable, 11b: reserved. - CCF Standby CHECK CONDITION if standby, 00b: restricted. 01b: Returning CHECK CONDITION status if transition was from a standby power condition is disabled.
PAGE 190
Table 156 PM_BG_PRECEDENCE field Code Vendor Specific 00h Vendor Specific – Background operations take precedence over maintaining low power conditions (same as 01b) 01b Performing background functions take precedence over maintaining low power conditions as follows: a) if the logical unit is in a low power condition as the result of a power condition timer associated with that condition expiring, then: 1) the logical unit shall change from that power condition, if necessary, to the power condition req
PAGE 191
18.10.14 Mode Page 1C (Informational Exceptions Control) Table 157 Page 1C (Informational Exceptions Control) Bit Default Byte 0 7 6 PS 0 5 3 2 1 0 Page Code = 1Ch 1 2 4 9Ch Page Length = 0Ah PERF 3 RSVD EBF EWASC DEXCPT Reserved = 0 0Ah TEST EBACK LOGERR ERR Method of Reporting 10h 03h 00h (MSB) 00h 4-7 Interval Timer 00h (LSB) 00h (MSB) 8-11 Report Count 00h (LSB) - PERF (Performance) bit is not supported and is ignored.
PAGE 192
Code Description 0h No reporting of informational exception condition: This method instructs the Target to not report informational exception condition. Asynchronous event reporting: Not supported. Generate unit attention: This method instructs the Target to report informational exception conditions by returning a Check Condition status on any command. The sense key is set to Unit Attention and the additional sense code indicates the cause of the informational exception condition.
PAGE 193
18.10.14.
PAGE 194
18.11 MODE SENSE (5A) Table 159 Mode Sense (5A) Bit Byte 7 6 5 0 4 3 Reserved = 0 2 PCF LLBAA DBD 0 Subpage code 4-6 Reserved = 0 (MSB) VU = 0 Reserved = 0 Page Code 3 9 1 Command Code = 5Ah 1 7-8 2 Allocation Length Reserved = 0 (LSB) FLAG LINK The MODE SENSE (5A) command provides a means for the drive to report various device parameters to the initiator. See the MODE SENSE (1A) command for a description of the fields in this command.
PAGE 195
18.12 PERSISTENT RESERVE IN (5E) Table 160 Persistent Reserve In (5E) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 5Eh 1 Reserved = 0 2-6 Service Action Reserved = 0 (MSB) 7-8 Allocation Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The PERSISTENT RESERVE IN command is used to obtain information about persistent reservations and reservation keys that are active within the controller. This command is used in conjunction with the PERSISTENT RESERVE OUT command PERSISTENT RESERVE OUT (5F).
PAGE 196
18.12.2 Parameter data for Read Keys Table 162 PERSISTENT RESERVE IN, parameter data for Read Keys Bit Byte 7 6 5 4 3 2 1 0 (MSB) 0-3 Generation (LSB) (MSB) 4-7 Additional length (n-7) (LSB) (MSB) 8-15 First reservation key (LSB) : (MSB) (n-7) - n Last reservation key (LSB) Generation is a counter that increments when PERSISTENT RESERVE OUT command with “Register” or “Preempt and Clear” completes successfully.
PAGE 197
18.12.3 Parameter Data for Read Reservations Table 163 PERSISTENT RESERVE IN, parameter data for Read Reservations Bit Byte 7 6 5 4 3 2 1 0 (MSB) 0-3 Generation (LSB) (MSB) 4-7 Additional length (n-7) (LSB) (MSB) 8-n Reservation descriptors (LSB) The Generation field shall be as defined for the Persistent Reserve in Read Keys parameter data. The Additional Length field contains a count of the number of bytes to follow in the Reservation Descriptor(s).
PAGE 198
18.13 PERSISTENT RESERVE OUT (5F) Table 165 PERSISTENT RESERVE OUT (5F) Bit Byte 7 6 5 0 4 3 2 1 0 FLAG LINK Command Code = 5Fh 1 Reserved = 0 2 Service Action Scope=0 Type 3-6 Reserved = 0 7-8 Parameter List Length = 18h 9 VU = 0 Reserved = 0 The PERSISTENT RESERVE OUT command is used to request service actions that reserve the drive for the exclusive or shared use of the initiator. The command uses other service actions to manage and remove such reservations.
PAGE 199
18.13.2 Type The Type field specifies the characteristics of the persistent reservation being established for all customer data sectors. The table below describes the supported types and how read and write commands are handled for each reservation type. Table 167 PERSISTENT RESERVE OUT, Type Code Code Name Description 0h Reserved 1h Write Exclusive 2h Reserved 3h Exclusive Access 4h Reserved Reserved Reads Shared: Any initiator may execute commands that transfer from the media.
PAGE 200
18.13.3 Parameter list The Parameter List required to perform the PERSISTENT RERSERVE OUT command is defined in the table below. All fields must be sent on all PERSISTENT RESERVE OUT commands, even if the field is not required for the specified service action.
PAGE 201
power cycles. The RESPONSE frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data). 18.13.
PAGE 202
18.13.4.4 APTPL The APTPL (Active Persist Through Power Loss) is valid only for the Register service action. The drive ignores the APTPL in other service actions. The following table shows the relationship between the last valid APTPL value and information held by the drive.
PAGE 203
18.14 PRE-FETCH (34) Table 171 PRE-FETCH (34) Bit Byte 7 6 0 5 4 3 2 1 0 Immed = 0 Obsolete Command Code = 34h 1 Reserved = 0 Reserved = 0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the Initiator. - Transfer length field specifies the number of contiguous blocks of data that are to be transferred into the cache.
PAGE 204
18.15 PRE-FETCH (90) Table 172 PRE-FETCH (90) Bit Byte 7 6 5 0 4 3 2 1 0 Immed = 0 Reserved = 0 Command Code = 90h 1 Reserved = 0 Reserved = 0 (MSB) 2-9 Logical Block Address (LSB) 10-13 14 15 Transfer Length Restricted For MMC-4 VU = 0 Reserved = 0 GROUP NUMBER = 0 Reserved = 0 FLAG LINK The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the Initiator.
PAGE 205
18.16 READ (6) - (08) Table 173 READ (6) - (08) Bit Byte 7 6 5 0 1 3 2 1 0 Command Code = 08h Reserved = 0 (MSB) LBA Logical Block Address 2-3 (LSB) 4 5 4 Transfer Length VU = 0 Reserved = 0 FLAG LINK The READ command requests the drive to transfer from the medium to the initiator the specified number of blocks (Transfer Length) starting at the specified Logical Block Address (LBA). - Logical block address field specifies the logical unit at which the READ operation shall begin.
PAGE 206
18.17 READ (10) - (28) Table 174 READ (10) - (28) Bit Byte 7 6 5 0 4 3 2 1 0 FUA_NV Obsolete Command Code = 28h 1 RDPROTECT DPO FUA RSVD=0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The READ (10) command requests the drive to transfer data to the Initiator.
PAGE 207
- Logical Block Reference Tag is checked RDPROTECT=010b - Protection information is transmitted to the initiator with the user data - Logical Block Guard is not checked - Logical Block Application Tag is checked (applies to READ(32) command only) - Logical Block Reference Tag is checked RDPROTECT=011b - Protection information is transmitted to the initiator with the user data - Logical Block Guard is not checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not
PAGE 208
18.18 READ (12) - (A8) Table 175 READ (12) - (A8) Bit Byte 7 6 5 4 3 0 1 2 1 0 FUA_NV RSVD = 0 Command Code = A8h RDPROTECT DPO FUA RSVD = 0 (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 The READ(12) command causes the drive to transfer data to the initiator. definitions of the fields in this command.
PAGE 209
18.19 READ (16) - (88) Table 176 READ (16) - (88) Bit Byte 7 6 5 0 4 3 2 1 0 RSVD= 0 FUA_NV RSVD=0 Command Code = 88h 1 RDPROTECT DPO FUA (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Transfer Length (LSB) 14 15 Restricted For MMC-4 Reserved = 0 VU = 0 GROUP NUMBER Reserved = 0 The READ(16) command causes the drive to transfer data to the initiator. definitions of the fields in this command.
PAGE 210
18.
PAGE 211
the corresponding bit of the Expected Logical Block Application Tag field with the corresponding bit of the Logical Block Application Tag field in the protection information.
PAGE 212
18.21 READ BUFFER (3C) Table 178 READ BUFFER (3C) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 3Ch 1 Reserved = 0 2 Mode Buffer ID = 0 (MSB) 3-5 Buffer Offset (LSB) (MSB) 6-8 Allocation Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The READ BUFFER command is used in conjunction with the WRITE BUFFER command as a diagnostic function for testing the memory of the drive and the SCSI bus integrity. This command does not alter the medium.
PAGE 213
18.21.1 Combined Header And Data (Mode 00000b) In this mode a 4-byte header followed by data bytes is returned to the Initiator during the DATA IN phase. The Buffer ID and the buffer offset field are reserved. The drive terminates the DATA IN phase when allocation length bytes of header plus data have been transferred or when the header and all available data have been transferred to the Initiator, whichever is less.
PAGE 214
18.21.3 Descriptor (Mode 00011b) In this mode, a maximum of four bytes of READ BUFFER descriptor information are returned. The drive returns the descriptor information for the buffer specified by the Buffer ID. - Buffer ID field should normally be set to zero, indicating the drive data transfer buffer. If any other value is specified, the results may be unpredictable. Buffer Offset field is reserved. Allocation Length should be set to four or greater.
PAGE 215
18.21.5 Echo Buffer Descriptor (Mode 01011b) In this mode, a maximum of four bytes of Read Buffer Descriptor information is returned. The drive returns the descriptor information for the echo buffer. The Buffer Offset field is reserved in this mode and must be zero. The drive transfers the lesser of the allocation length or four bytes of following Echo Buffer Descriptor.
PAGE 216
FFh Clear error history I_T Nexus and release error history snapshot Ignored Yes The drive will terminate the Read Buffer command with Check Condition status with the sense key set to Illegal Request and the additional sense code set to Operation In Progress if the drive receives a Read Buffer command: a) with the Mode field set to 1Ch; b) with the Buffer ID field set to a value that is constrained by error history I_T nexus; c) if an error history I_T nexus exists and the command is received from an I_
PAGE 217
Table 184 Error History Directory Entry Bit Byte 7 6 5 4 3 0 Supported Buffer ID 1-3 Reserved 2 1 0 (MSB) 4-7 Maximum Available Length (LSB) • Supported Buffer ID field indicates the error history buffer ID associated with this entry. • Maximum Available Length field indicates the maximum number of data bytes contained in the buffer indicated by the Supported Buffer ID field. The actual number of bytes available for transfer may be smaller.
PAGE 218
18.22 READ CAPACITY (10) - (25) Table 185 READ CAPACITY (10) - (25) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 25h 1 Reserved = 0 Reserved = 0 Obsolete (MSB) 2-5 Logical Block Address (LSB) 6-7 Reserved = 0 8 Reserved = 0 9 VU = 0 PMI Reserved = 0 FLAG LINK The READ CAPACITY command returns information regarding the capacity of the drive. - Logical Block Address is used in conjunction with the PMI bit.
PAGE 219
18.23 READ CAPACITY (16) (9E/10) Table 187 Read Capacity (16) (9E/10) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 9Eh 1 Reserved = 0 Service Action = 10h (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Allocation Length (LSB) 14 Reserved = 0 15 VU = 0 PMI Reserved = 0 FLAG Link The READ CAPACITY (16) (9E/10) command returns information regarding the capacity of the drive. command is processed like the standard READ CAPACITY (25) command. 18.23.
PAGE 220
The protection type (P_TYPE) field and the protection enable (PROT_EN) bit indicate the drive's current type of protection.
PAGE 221
READ DEFECT DATA (37) Table 191 READ DEFECT DATA (37) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 37h 1 Reserved = 0 2 Reserved = 0 3-6 Reserved = 0 Plist Glist 0 Defect List Format Reserved = 0 (MSB) 7-8 Allocation Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The READ DEFECT DATA command requests that the Target transfer the medium defect data to the Initiator.
PAGE 222
available Defect Data has been transferred to the Initiator, whichever is less. The Read Defect Data contains a 4-byte header followed by zero or more defect descriptors. 18.23.2 Defect List Header Table 193 Defect List Header Bit Byte 7 6 5 4 3 2 1 0 Defect List Header 0 Reserved = 0 1 Reserved = 0 Plist Glist Defect List Format (MSB) 2-3 Defect List length (LSB) 18.23.
PAGE 223
18.23.4 Bytes from Index Format (100b) Table 195 Defect Descriptors of Bytes from Index Format Byte Defect Descriptors (MSB) 0-2 Cylinder Number of Defect (LSB) 3 Head Number of Defect (MSB) 4-7 Defect Bytes from Index (LSB) Defect Bytes from Index is gotten using the following equation: Bytes from Index = (Physical Sector Number) * N Where: N = Bytes per sector 18.23.
PAGE 224
18.24 READ DEFECT DATA (B7) Table 197 READ DEFECT DATA (B7) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = B7h 1 Reserved = 0 Plist 2-5 Glist Defect List Format Reserved = 0 (MSB) 6-9 Allocation Length (LSB) 10 Reserved = 0 11 VU = 0 Reserved = 0 FLAG LINK (See Section 18.24 “READ DEFECT DATA (37)”) 18.24.
PAGE 225
18.24.2 Defect List Descriptor Table 199 Defect List Descriptor Bit Byte 7 6 5 4 3 2 1 0 Defect List Descriptor 0-7 Defect Descriptor 0 . 8n - (8n+7) Defect Descriptor n (See Defect List Descriptor for Read Defect Data (37) in Section 18.24.2 "Defect List Descriptor".) 18.24.
PAGE 226
18.25 READ LONG (3E) Table 202 READ LONG (3E) Bit Byte 7 6 0 5 4 3 2 1 0 Correct = 0 Obsolete Command Code = 3Eh 1 Reserved = 0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Byte Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The READ LONG command requests the drive to transfer one block of data to the Initiator. The transfer data includes data and MEDC field data.
PAGE 227
18.26 READ LONG (9E) Table 203 READ LONG (9E) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 9Eh 1 Reserved = 0 Service Action (11h) (MSB) 2-9 Logical Block Address (LSB) 10-11 Reserved = 0 (MSB) 12-13 Byte Transfer Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 PBLOCK CORRCT FLAG LINK The READ LONG command requests the drive to transfer one block of data to the Initiator. The transfer data includes data and MEDC field data.
PAGE 228
18.27 REASSIGN BLOCKS (07) Table 204 REASSIGN BLOCKS (07) Bit Byte 7 6 0 4 3 2 1 0 LONGLBA Reserved = 0 FLAG LINK Command Code = 07h 1 Reserved = 0 2-4 5 5 Reserved = 0 VU = 0 Reserved = 0 The REASSIGN BLOCKS command requests the drive to reassign a logical block to an available spare. The REASSIGN BLOCKS command attempts to allocate spare blocks on a spare track. The LBA is transferred to the drive during the DATA OUT phase.
PAGE 229
Following is the format of the data sent by the Initiator during the DATA OUT phase. Table 205 Format of Reassign Blocks Parameter List data Bit Byte 7 0-1 6 5 4 3 2 1 Reserved = 0 (MSB) 2-3 Defect List Length (LSB) 4-n Defect LBA List - Defect List Length is the total number of bytes in the Defective LBA List (n - 4). - Defective LBA List is a list of zero to four Logical Block Addresses to be reassigned.
PAGE 230
18.28 RECEIVE DIAGNOSTICS RESULTS (1C) Table 206 RECEIVE DIAGNOSTIC RESULTS (1C) Bit Byte 7 6 5 0 4 2 1 0 Command Code = 1Ch 1 Reserved = 0 Reserved = 0 2 3 4 3 PCV Page Code (MSB) Allocation Length (LSB) 5 VU = 0 Reserved = 0 FLAG LINK The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTIC command be sent to the Initiator.
PAGE 231
18.28.2 Receive Diagnostic Results Page 40 Using the SEND DIAGNOSTIC command, an address in either physical or logical format is supplied to the drive. This page is then used to retrieve the address translated into the other format.
PAGE 232
10-13 Sector Number or Bytes from Index HGST Ultrastar C15K600 Hard Disk Drive Specification 232
PAGE 233
18.29 RELEASE (17) Table 210 RELEASE (17) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 17h Reserved = 0 3rdPty=0 3rd Party ID 2 Reservation Identification 3-4 Reserved = 0 5 1 VU = 0 Reserved = 0 Ext=0 FLAG LINK The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that is not currently active. The drive returns Good status without altering the reservation. - 3rdPty must be 0. Third Party reservations are not supported.
PAGE 234
18.30 RELEASE (57) Table 211 RELEASE (57) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 57h Reserved = 0 3rdPty=0 Reserved = 0 2 Reservation Identification 3 3rd Party Device ID 4-8 Reserved = 0 9 1 VU = 0 Reserved = 0 Ext = 0 FLAG LINK The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that is not currently active. The drive returns Good status without altering the reservation. - 3rdPty must be 0.
PAGE 235
18.31 REPORT DEVICE IDENTIFIER (A3/05) Table 212 REPORT DEVICE IDENTIFIER (A3/05) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A3h 1 Reserved = 0 Service Action = 05h 2 Reserved = 0 3 Reserved = 0 (MSB) 4-5 LUN=0 (LSB) (MSB) 6-9 Allocation Length (LSB) 10 Reserved = 0 11 VU = 0 Reserved = 0 FLAG LINK The REPORT DEVICE IDENTIFIER command requests that the device server send device identification information to the application client.
PAGE 236
identifier length initially equals zero and is changed only by a successful SET DEVICE IDENTIFIER command. The IDENTIFIER field contains a vendor specific value. The value reported is the last value written by a successful SET DEVICE IDENTIFIER command. The value of the identifier is changed only by a SET DEVICE IDENTIFIER command. The identifier value persist through resets, power cycles, media format operations. The Target return the same Identifier to all Initiators on all ports.
PAGE 237
18.32 REPORT LUNS (A0) Table 214 REPORT LUNS (A0) Bit Byte 7 6 5 4 3 0 Command Code = A0h 1-5 Reserved 2 1 0 (MSB) 6-9 Allocation Length (LSB) 10 Reserved 11 VU = 0 Reserved = 0 FLAG LINK The REPORT LUNS command requests that the Target return the known LUN to the Initiator. The REPORT LUNS command should always be available and is unaffected by any reservations. The Allocation Length must be at least 16 bytes.
PAGE 238
18.33 REPORT SUPPORTED OPERATION CODES (A3/0C) Table 216 REPORT SUPPORTED OPERATION CODES (A3/0C) Bit Byte 7 6 5 0 3 2 Reserved = 0 0 RCTD Service Action = 0Ch Reserved = 0 3 Requested Operation Code 4-5 Requested Service Action 6-9 Allocation Length 10 Reserved = 0 11 1 Command Code = A3h 1 2 4 VU = 0 Reserved Reporting Options FLAG LINK The REPORT SUPPORTED OPERATION CODES command requests information on commands that the drive supports.
PAGE 239
The command support data for the operation code and service action specified in the Requested Operation Code field and Requested Service Action field will be returned in the one_command parameter data format.
PAGE 240
18.33.1 All_commands parameter data format The Report Supported Operation Codes all_command parameter data format begins with a four-byte header that contains the length in bytes of the parameter data, followed by a list of supported commands. Each command descriptor contains information about a single supported command CDB (i.e. one operation code and service action combination, or one non-service action operation code).
PAGE 241
18.33.2 One_command parameter data format The Report Supported Operation Codes one_command parameter data format contains information about the CDB and a usage map for bits in the CDB for the command specified by the Reporting Options, Requested Operation Code, and Requested Service Action fields in the Reported Supported Operation Codes CDB.
PAGE 242
18.33.3 Command timeouts descriptor format 18.33.3.1 Overview The command timeouts descriptor (see Table 215) returns time-out information for commands supported by the logical unit based on the time from the start of processing for the command to its reported completion. Values returned in the command timeouts descriptor do not include times that are outside the control of the device server (e.g.
PAGE 243
18.33.3.
PAGE 244
18.34 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D) Table 224 Report Supported Task Management Functions (A3/0D) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A3h 1 Reserved = 0 Service Action = 0Dh 2-5 Reserved = 0 6-9 Allocation Length 10 Reserved = 0 11 VU = 0 Reserved = 0 Flag Link The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command requests information on task management functions supported by the drive.
PAGE 245
QUERY TASK is not supported.
PAGE 246
TRS (Target Reset) bit set to one indicates that TARGET RESET is supported. A TRS bit of zero indicates that TARGET RESET is not supported. WAKES (Wakeup) bit set to one indicates that WAKEUP is supported. A WAKES bit of zero indicates that WAKEUP is not supported. A QUERY UNIT ATTENTION supported (QUAS) bit set to one indicates the QUERY UNIT ATTENTION task management function (see SAM-4) is supported by the logical unit.
PAGE 247
18.35 REQUEST SENSE (03) Table 226 REQUEST SENSE (03) Bit Byte 7 6 5 4 3 0 Command Code = 03h 1 Reserved = 0 2-3 Reserved = 0 4 Allocation Length 5 VU = 0 2 Reserved = 0 1 0 DESC FLAG LINK The REQUEST SENSE command requests the drive to transfer sense data. The Descriptor Format (DESC) bit specifies which sense data format the device shall return in the parameter data. The Allocation Length specifies the maximum number of bytes of sense data that the drive should return.
PAGE 248
18.36 RESERVE (16) Table 228 RESERVE (16) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 16h 1 Reserved = 0 2 3rdPty=0 3rd Party ID Ext=0 Reservation Identification (MSB) 3-4 Extent List Length = 0 (LSB) 5 VU = 0 Reserved = 0 FLAG LINK The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the command or for a third party as specified by the Initiator. Extents are not supported by the drive. The Ext bit must be zero.
PAGE 249
18.37 RESERVE (56) Table 229 RESERVE (56) Bit Byte 7 6 0 5 4 3 2 1 0 Command Code = 56h 1 Reserved = 0 3rdPty=0 2 Reservation Identification 3 Third Pay Device ID 4-6 Reserved = 0 Reserved Ext=0 (MSB) 7-8 Extent List Length = 0 (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the command or for a third party as specified by the Initiator.
PAGE 250
18.38 REZERO UNIT (01) Table 230 REZERO UNIT (01) Bit Byte 7 6 5 0 1 3 2 1 0 FLAG LINK Command Code = 01h Reserved = 0 2-4 5 4 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 The REZERO UNIT command requests that the Target seek LBA 0.
PAGE 251
18.39 SANITIZE (48) Table 231 SANITIZE (48) Bit Byte 7 6 5 0 1 4 3 2 0 FLAG LINK Command Code = 48h Immed RSVD AUSE Service Action 2-6 Reserved 7-8 Parameter List Length 9 1 VU = 0 Reserved • Immed bit is to specify 0 Status is to be returned at the end of the operation. 1 Good status shall always be returned immediately after command has been received. The TEST UNIT READY command may be used to determine when the drive becomes ready.
PAGE 252
18.39.1 Sanitize (48) Service Action Codes The following service action codes are implemented. If a reserved service action code is specified, the drive returns a Check Condition status. The sense key is set to Illegal Request and the additional sense data is set to Invalid Field in CDB.
PAGE 253
terminate the command 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 field specifies the data pattern to be used to write the user data. This data pattern is repeated as necessary to fill each logical block. For each logical block, the first byte of the user data shall begin with the first byte of the initialization pattern.
PAGE 254
18.40 SEND DIAGNOSTIC (1D) Table 234 SEND DIAGNOSTIC (1D) Bit Byte 7 6 0 5 4 3 2 1 0 SlfTst Dev0fl Unt0fl Command Code = 1Dh 1 Function Code 2 PF RSVD =0 Reserved = 0 (MSB) 3-4 Parameter List Length (LSB) 5 VU = 0 Reserved = 0 FLAG LINK The SEND DIAGNOSTIC command requests the drive to perform its self-diagnostic test or to perform a function based on a page of information sent in a Data Out phase during the command.
PAGE 255
Table 235 SEND DIAGNOSTIC Function Code (1D) Value Function name Description 000b NA Value to be used when the SlfTst bit is set to one or if the SEND DIAGNOSTIC command is not invoking one of the other self-test function codes. 001b Background Short self-test The device server starts its short self-test routine in background mode. 010b Background extended self-test The device server starts its extended self-test routine in background mode. 011b NA Reserved.
PAGE 256
18.40.1 Send Diagnostic Page 0 This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS command. Table 236 Diagnostic page 0 Bit Byte 7 6 5 4 3 0 Page Code = 0 1 Reserved = 0 2-3 Page Length = 0 2 1 0 18.40.
PAGE 257
- Phy Test Pattern specifies the phy test pattern to be transmitted when the Phy Test Function is set to 01h. If an unsupported value is specified, Check Condition status will be returned with a sense key of Illegal Request and additional sense of Invalid Field in Parameter List. Phy Test Function Description 00h If the selected phy is performing a phy-test function, then the selected phy stop performing the phy test function and originate a link reset sequence.
PAGE 258
- - sense of Invalid Field in Parameter List. Phy Test Pattern SATA bit set to 0 indicates that the phy transmits the phy test pattern as a SAS phy. If this bit is set to 1, Check Condition status will be returned with a sense key of Illegal Request and additional sense of Invalid Field in Parameter List Phy Test Pattern SSC field specifies the SSC modulation type which the phy test pattern will be transmitted.
PAGE 259
18.40.3 Send Diagnostic Page 40 This allows the Initiator to translate a LBA or physical sector address to the other format. The address to be translated is passed to the Target with the SEND DIAGNOSTIC command and the results are returned to the Initiator by the RECEIVE DIAGNOSTICS command. The Target will read the parameter list from the Initiator, and, if no errors are detected in the parameter list, Good status will be returned.
PAGE 260
18.41 SET DEVICE IDENTIFIER (A4/06) Table 243 SET DEVICE IDENTIFIER (A4/06) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A4h 1 Reserved = 0 Service Action = 06h 2 Reserved = 0 3 Reserved = 0 4-5 Restricted = 0 (MSB) 6-9 Parameter List Length (LSB) 10 Reserved = 0 11 VU = 0 Reserved = 0 FLAG LINK The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the SET DEVICE IDENTIFIER parameter list.
PAGE 261
18.42 START STOP UNIT (1B) Table 245 START STOP UNIT (1B) Bit Byte 7 6 5 4 3 2 0 Command Code = 1Bh 1 Reserved = 0 2 0 Immed Reserved = 0 3 Reserved = 0 4 Power Condition 5 1 VU = 0 Power Condition Modifier Reserved=0 Reserved = 0 LoEj= 0 Start FLAG LINK The START STOP UNIT command is used to spin up or stop the spindle motor.
PAGE 262
Table 246 Power Conditions Power Condition Code Name Power Condition Modifier 0h START_VALID 0h Process the START bit 1h ACTIVE 0h Place the device into the active power condition 2h IDLE_A 0h Place the device into the idle-a power condition 2h IDLE_B 1h Place the device into the idle-b power condition 2h IDLE_C 2h Place the device into the idle-c power condition 3h STANDBY_Z 0h Place the device into the standby_Z power condition 3h STANDBY_Y 1h Place the device into the standb
PAGE 263
If the START STOP UNIT command is processed with the POWER CONDITION field set to FORCE_IDLE_0 or FORCE_STANDBY_0, then the device server shall: a) force the specified timer to zero, cause the logical unit to transition to the specified power condition, and return control of the power condition to the device server; or b) terminate a START STOP UNIT command that selects a timer that is not supported by the device server or a timer that is not active.
PAGE 264
18.43 SYNCHRONIZE CACHE (10) - (35) Table 247 SYNCHRONIZE CACHE (10) - (35) Bit Byte 7 6 5 0 4 3 2 1 0 Immed = 0 Obsolete Command Code = 35h 1 Reserved = 0 Reserved = 0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Number of Blocks (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded on the media. - Logical Block Address is to specify where the operation is to begin.
PAGE 265
18.44 SYNCHRONIZE CACHE (16) - (91) Table 248 Synchronize Cache (16) - (91) Bit Byte 7 6 0 5 4 3 2 0 Immed = 0 Rsvd=0 FLAG LINK Command Code = 91h 1 Reserved = 0 2-9 Logical Block Address 10-13 Number of Blocks 14 Reserved = 0 15 1 VU = 0 Reserved = 0 The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded on the media. See the SYNCHRONIZE CACHE (10) description for definitions of the fields in this command.
PAGE 266
18.45 TEST UNIT READY (00) Table 249 TEST UNIT READY (00) Bit Byte 7 6 0 1 4 3 2 1 0 FLAG LINK Command Code = 00h Reserved = 0 2-4 5 5 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 The TEST UNIT READY command allows the Initiator to check if the drive is READY. The SCSI specification defines READY as the condition where the device will accept a media-access command without returning Check Condition status. The drive will first verify that the motor is spinning at the correct speed.
PAGE 267
18.46 VERIFY (10) - (2F) Table 250 VERIFY (10) - (2F) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 2Fh 1 VRPROTECT DPO RSVD =0 ByteChk RSVD = 0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Verification Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that no data will be transferred. This condition is not considered an error.
PAGE 268
The Verification Length is the number of blocks to check. The data (if any) from the data-out phase and the data from the media are not retained in the cache. Therefore, the DPO bit has no effect on this command and is ignored. VRPROTECT defines the manner in which protection information read from disk shall be checked during processing of the command.
PAGE 269
VRPROTECT=000b If the drive is not formatted with protection information, only user data is verified.
PAGE 270
18.47 VERIFY (12) - (AF) Table 252 VERIFY (12) - (AF) Bit Byte 7 6 5 4 0 1 3 2 1 0 Command Code = AFh VRPROTECT DPO FUA Reserved = 0 ByteChk (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Verification Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 The VERIFY(12) command causes the drive to verify data written on the media. for the definitions of the fields in this command.
PAGE 271
18.48 VERIFY (16) - (8F) Table 253 VERIFY (16) - (8F) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 08Fh 1 VRPROTECT DPO RSVD =0 ByteChk RSVD = 0 (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Verification Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 FLAG The VERIFY command requests that the drive verify the data written on the media. description for the definitions of the fields in this command.
PAGE 272
18.
PAGE 273
logical block accessed by the command. A Logical Block Application Tag Mask bit set to one enables the checking of the corresponding bit of the Expected Logical Block Application Tag field with the corresponding bit of the Logical Block Application Tag field in the protection information. If the ATO bit is set to zero, the Logical Block Application Tag Mask field and the Expected Logical Block Application Tag field are ignored.
PAGE 274
18.50 WRITE (6) - (0A) Table 255 WRITE (6) - (0A) Bit Byte 7 6 5 0 1 3 2 1 0 Command Code = 0Ah Reserved = 0 (MSB) LBA Logical Block Address 2-3 (LSB) 4 5 4 Transfer Length VU = 0 Reserved = 0 FLAG LINK The WRITE command requests the drive to write the specified number of blocks of data (Transfer Length) from the Initiator to the medium starting at the specified Logical Block Address (LBA). See Section 18.16 "READ (6) - (08)" for the parameters.
PAGE 275
18.51 WRITE (10) - (2A) Table 256 WRITE (10) - (2A) Bit Byte 7 6 5 0 1 4 3 2 1 0 Rsvd=0 FUA_NV Obsolete Command Code = 2Ah WRPROTECT DPO FUA (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The WRITE (10) command requests that the drive write the data transferred from the Initiator. This command is processed like the standard WRITE (6) - (0A) command except for the longer transfer length.
PAGE 276
WRPROTECT defines the manner in which protection information written to disk shall be checked during processing of the command. Protection information may be transmitted to the drive with the user data, based on the WRPROTECT bit and the drive format. If the drive is not formatted with protection information, WRPROTECT must be set to 000b, else Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB.
PAGE 277
18.52 WRITE (12) - (AA) Table 257 WRITE (12) - (AA) Bit Byte 7 6 0 5 4 3 2 1 0 Rsvd=0 FUA_NV Rsvd=0 Command Code = AAh 1 WRPROTECT DPO FUA (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved=0 VU = 0 Reserved = 0 FLAG The WRITE(12) command causes the drive to write data from the initiator to the media. description for the definitions of the fields in this command.
PAGE 278
18.53 WRITE (16) - (8A) Table 258 WRITE (16) - (8A) Bit Byte 7 6 0 5 4 3 2 1 0 Rsvd=0 FUA_NV Rsvd=0 Command Code = 8Ah 1 WRPROTECT DPO FUA (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Transfer Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 The WRITE(16) command causes the drive to write data from the initiator to the media. description for the definitions of the fields in this command.
PAGE 279
18.
PAGE 280
expected in the protection information of the first logical block accessed by the command. If the ATO bit is set to one in Mode Page 0Ah, the Logical Block Application Tag Mask field contains a value that is a bit mask for enabling the checking of the Logical Block Application Tag field in the protection information for each logical block accessed by the command.
PAGE 281
18.55 WRITE AND VERIFY (10) - (2E) Table 260 WRITE AND VERIFY (10) - (2E) Bit Byte 7 6 5 0 1 4 3 2 1 0 Command Code = 2Eh WRPROTECT DPO RSVD =0 ByteChk Obsolete (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK WRITE AND VERIFY command requests that the drive writes the data transferred from the Initiator to the medium and then verify that the data is correctly written.
PAGE 282
in the Mode Select Page 8 Caching parameters. A DPO bit of zero indicates the priority is determined by the retention priority. The Initiator should set the DPO bit when the blocks written by this command are not likely to be read again in the near future.
PAGE 283
18.56 WRITE AND VERIFY (12) - (AE) Table 262 WRITE and VERIFY (12) - (AE) Bit Byte 7 6 0 5 4 3 2 1 0 Command Code = AEh 1 WRPROTECT DPO Reserved =0 ByteChk Obsolete (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The WRITE AND VERIFY command requests that the drive write the data transferred from the Initiator to the medium and then verify that the data is correctly written.
PAGE 284
18.57 WRITE AND VERIFY (16) - (8E) Table 263 WRITE and VERIFY (16) - (8E) Bit Byte 7 6 0 5 4 3 2 1 0 Command Code = 8Eh 1 WRPROTECT DPO RSVD =0 ByteChk Obsole te (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Transfer Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The WRITE AND VERIFY command requests that the drive write the data transferred from the Initiator to the medium and then verify that the data is correctly written.
PAGE 285
18.
PAGE 286
18.59 WRITE BUFFER (3B) Table 265 WRITE BUFFER (3B) Bit Byte 7 6 5 0 1 4 3 2 0 FLAG LINK Command Code = 3Bh Mode Specific Mode 2 Buffer ID 3-5 Buffer Offset 6-8 Parameter List Length 9 1 VU = 0 Reserved = 0 The WRITE BUFFER command is used in conjunction with the READ BUFFER command as a diagnostic function for testing the memory of the drive and the SCSI bus integrity. This command does not alter the medium of the drive.
PAGE 287
18.59.1 Combined Header And Data (Mode 00000b) In this mode, the data to be transferred is preceded by a four-byte header. Buffer ID must be zero. If another value is specified, no download function is performed and the command is terminated with Check Condition status. And the drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in CDB. Buffer Offset must be zero.
PAGE 288
drive shall set the sense key to Illegal Request and additional sense code to Illegal Field In CDB. Buffer Offset must be zero. If an invalid value is specified, the command is terminated with Check Condition status. The drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in CDB. Parameter List Length must be the size of the data set to be downloaded. It may also be set to 0000h in which case no code is updated and command status is returned.
PAGE 289
HGST Ultrastar C15K600 Hard Disk Drive Specification 289
PAGE 290
18.59.6 Write Data to Echo Buffer (Mode 01010b) In this mode the Target transfers data into the echo buffer. The echo buffer is assigned in the same manner by the Target as it would for a WRITE operation. Data will be sent aligned on 4-byte boundaries. Upon successful completion of a WRITE BUFFER command the data will be preserved in the echo buffer unless there is an intervening command to any logical unit, in which case it may be changed. 18.59.
PAGE 291
HGST Ultrastar C15K600 Hard Disk Drive Specification 291
PAGE 292
18.60 WRITE LONG (10) (3F) Table 268 WRITE LONG (3F) Bit Byte 7 6 0 1 5 4 3 2 1 0 Command Code = 3Fh COR_DIS WR_UNCOR PBLOCK=0 Reserved = 0 Obsolete (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Byte Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The WRITE LONG command requests the drive to write one block of data transferred from the Initiator.
PAGE 293
e) On a read to the LBA, return check condition status with the sense key set to Medium Error and the additional sense code set to read error marked bad by client. The error state for LBA written with the COR_DIS or WR_UNCOR bits set, will remain in effect until the LBA is rewritten by a write, write same, format, write long without COR_DIS set, reassign or write verify command. - Logical Block Address field specifies the logical block at which the write operation shall occur. - Byte Transfer Length.
PAGE 294
18.61 WRITE LONG (16) - (9F) Table 269 WRITE LONG (9F) Bit Byte 7 6 0 1 5 4 3 2 1 0 Command Code = 9Fh COR_DIS WR_UNCOR PBLOCK=0 Service Action (11h) (MSB) 2-9 Logical Block Address (LSB) 10-11 Reserved = 0 (MSB) 12-13 Byte Transfer Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 Refer to Write Long (10) for field definitions.
PAGE 295
18.62 WRITE SAME (10) - (41) Table 270 WRITE SAME (41) Bit Byte 7 6 5 0 1 4 3 2 1 0 LBDATA=0 Obsolete Command Code = 41h WRPROTECT Reserved = 0 PBDATA=0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Number of Blocks (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The WRITE SAME command instructs the Target to write a single block of data transferred to the Target from the Initiator to a number of sequential logical blocks.
PAGE 296
18.63 WRITE SAME (16) - (93) Table 271 WRITE SAME (16) - (93) Bit Byte 7 6 5 0 4 3 2 1 0 PBDATA=0 LBDATA=0 Obsolete Command Code = 93h 1 WRPROTECT Reserved = 0 (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Number of Blocks (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The Write Same command instructs the Target to write a single block of data transferred to the Target from the Initiator to a number of sequential logical blocks.
PAGE 297
18.
PAGE 298
The Expected Initial Logical Block Reference Tag field contains the value of the Logical Block Reference Tag field expected in the protection information of the first logical block accessed by the command. If the ATO bit is set to one in Mode Page 0Ah, the Logical Block Application Tag Mask field contains a value that is a bit mask for enabling the checking of the Logical Block Application Tag field in the protection information for each logical block accessed by the command.
PAGE 299
19 SCSI Status Byte Upon the completion of a command a status byte is sent to the initiator. Additional sense information may also be available depending on the contents of the status byte. The following section describes the possible values for the status byte and sense data. All Reserved fields are set to zero. Table 273 SCSI Status Byte. Format of the SCSI STATUS byte.
PAGE 300
20 Additional information This chapter provides additional information or descriptions of various functions, features, or operating models supported by the Target that are not fully described in previous chapters. 20.1 SCSI Protocol There are various operating conditions that prevent the Target from executing a SCSI command. This section describes each of these operating conditions and their relative priority. 20.1.
PAGE 301
20.1.3 Overlapped Commands The drive does not perform any overlapped command checking. 20.1.4 Command Processing During Execution of Active I/O Process When the target is not executing any I/O processes, a new I/O process is permitted to execute (unless execution is prevented by another internal target condition listed in 20.1.1 "Priority of SCSI Status Byte Reporting").
PAGE 302
20.1.5 Unit Attention Condition The target generates a unit attention condition when one of the following occurs: - The target has been reset This includes a power-on reset or a reset caused by a LUN Reset Task Management function or Hard Reset sequence. In all of these cases, a unit attention condition is generated for each initiator. - MODE SELECT command has been executed In this case, a unit attention condition is generated for all initiators except the one that issued the MODE SELECT command.
PAGE 303
If the target receives a command from an initiator before reporting a CHECK CONDITION status for a pending unit attention condition for that initiator, the target's response varies with the command as follows: Inquiry Report Luns Request Sense All Others Execute the command, return GOOD status, and preserve the unit attention condition. Same as above Execute the command, return any pending sense data, return GOOD status, and preserve the unit attention condition.
PAGE 304
20.1.6 Command Processing During Startup and Format Operations If the Target receives a command from an Initiator while the Target is executing a startup or format operation, the response of the Target varies with the command as follows: INQUIRY The drive sends inquiry data and returns appropriate status. REQUEST SENSE Executes the command, returns a Sense key of NOT READY and an Additional Sense Code of LOGICAL UNIT NOT READY and returns GOOD STATUS.
PAGE 305
20.1.9 Degraded Mode There are certain errors or conditions which may impair the ability of the drive to function normally. Rather than fail hard the drive is designed to be as responsive as possible. Also, in most cases, some action on the part of the initiator may be used to restore normal operation. This mode of limited operation is called Degraded Mode.
PAGE 306
20.1.9.2 Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up Table 275 Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up Command (w/Option) Response Request Sense Executed.
PAGE 307
20.1.9.3 Response to SCSI Command in Degraded Mode - Spindle Start Failure Table 276 Spindle Motor Degraded Mode - Spindle Start Failure Command (w/Option) Response Request Sense Executed.
PAGE 308
20.1.9.4 Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command Table 277 Spindle Motor Degraded Mode - Spindle Stopped by Command Command (w/Option) Response Request Sense Executed.
PAGE 309
20.1.9.5 Self Configuration Failure Degraded Mode Table 278 Self Configuration Failure Degraded Mode Command (w/Option) Response Request Sense Executed.
PAGE 310
20.1.9.6 Format Command Failure Degraded Mode Table 279 Format Command Failure Degraded Mode Command (w/Option) Response Request Sense Executed.
PAGE 311
- A Reserve command results in a Reservation Conflict Status. - A Release command is permitted but is ignored. - Any other command is permitted. If a Reservation Conflict Status is not reported and the command is permitted, then the Target checks the next highest priority internal condition to determine whether execution is allowed. See Section 20.1.
PAGE 312
20.2 Priority Commands Certain SCSI commands always execute without returning a Busy Status or Reservation Conflict Status in response to the command. These commands are - Inquiry - Request Sense - Report LUNs - Test Unit Ready These commands are executed prior to attempting to complete the execution of any other pending command in the queue. These commands are never queued. 20.
PAGE 313
20.4 Command Reordering Command reordering is supported when enabled by the Queue Algorithm Modifier in mode page 0A (see 18.10.9 "Mode Page 0A (Control Mode Page Parameters)”. 20.5 Concurrent I/O Process Concurrent commands are always allowed to execute concurrently with non-priority commands. A second priority command received while a priority command is being executed is put at the head of the command queue.
PAGE 314
The target will automatically reallocate for the following commands. - Write - Write Same - Write portion of Write and Verify For all other commands the AWRE setting is ignored and the target will not automatically reallocate. Auto Reallocate information is communicated via the sense data returned following a command during which a site was determined to need rewriting or reassignment. The LBA returned in the sense data is the LBA that was determined to need rewriting or reassignment.
PAGE 315
20.8 Segmented Caching 20.8.1 Overview Segmented Caching divides the data buffer into several smaller buffers. Each buffer is used as Read/ Write/Read-Ahead buffer. 20.8.2 Read Ahead The Read Ahead function consists of reading data that the Initiator has not yet requested to the drive buffer. This function is intended to improve performance for an initiator that frequently accesses sequential data with successive SCSI read commands.
PAGE 316
20.11 Reset Reset actions will return the drive to a known, initialized state. This device supports the Hard reset option as defined in the SCSI standards and the reset sources discussed below. 20.11.
PAGE 317
20.12 Diagnostics The drive will execute Power on Diagnostics at power on time to assure the correct operation of the drive by validating components (ROM, RAM, Sector Buffer, EEPROM, HDC, Spindle Motor, Actuator), checking stored information in the Reserved Area and EEPROM, and verifying fault detects circuits. Self-test can be invoked by issuing a SEND DIAGNOSTIC command. 20.12.1 Power on Diagnostics At power on time the following tests are executed: 1. Validation of ROM and EEPROM 2.
PAGE 318
20.12.2.3 Self-test Modes There are two modes for short and extended self-tests: a foreground mode and a background mode. These modes are described in the following clauses. Foreground mode When the drive receives a SEND DIAGNOSTIC command specifying a self-test to be performed in the foreground mode, the drive will return status for that command after the self-test has been completed.
PAGE 319
Table 281 Short and Extended Self-Test Description Segment Number Short Self-Test Extended Self-Test Test Description 1h Drive Ready Test Internal check to insure drive is “ready”, similar to a Test Unit Ready command. 2h Drive Diagnostics This test is comprised of the Default Self Test as defined in Section 20.12.2.
PAGE 320
20.13 Idle Time Function The drive periodically saves data in logs and S.M.A.R.T. counters in the reserved area of the disks. The information is used by the drive to support various SCSI commands and for the purpose of failure analysis. 20.14 Command Time out Limits The 'Command Time-out Limits' are defined as the time period from the SCSI Arbitration phase through the SCSI Task complete message, associated with a particular command.
PAGE 321
20.14.
PAGE 322
20.15 Recommended Initiator ERP The Drive's design points for error reporting to the system assumes certain system action for the error return codes. These assumptions are: 1. 2. 3. SCSI protocol will be the first priority in reporting errors. The system will maintain a log of all reported errors. System architecture should include all error handling recommendations made in this section. Deviations should have mutual agreement between Drive development and system integration.
PAGE 323
20.15.3 Data Recovery Procedure Statistically, most data error activity is noise related and has nothing to do with defects in the media. It is wrong for the system to assume that every data error reported occurred because of a defect in the media. It is also wrong for the system to assume that every data error that occurred because of a media defect rendered the Drive unusable. Recurring data error activity at the same physical location is an indication of a problem.
PAGE 324
20.15.3.2 Data Error Logging The Drive will report data errors to the initiator that do not require immediate action (successful auto reallocation, successful auto rewrite, or no action needed on this occurrence). The initiator should log these errors in the system error log. No other action is required.
PAGE 325
20.15.4 Non data Error Recovery Procedure The Drive will follow a logical recovery procedure for non data errors. The initiator options for non-data errors are limited to logging the error, retrying the failing command, or replacing the drive. These recovery procedures assume the initiator practices data back-up and logs errors at the system level for interrogation by service personnel. 20.15.4.1 Drive Busy The Drive is busy performing an operation. This is not an error condition.
PAGE 326
20.15.4.4 Drive Not Ready The initiator should do the following: 1. Issue a Start Stop Unit (1B) command. 2. Verify that the drive comes ready within the time specified. 3. If the drive fails to come ready within the specified time, service the drive using the service guidelines specified in Section 20.15.1 "Drive Service Strategy". 4. Retry the failing command. a. If the failing command completes with Good Status, log the error as recovered. b.
PAGE 327
mode to prevent writing data off track. Recovery of this condition is either a power cycle or successful completion of the Send Diagnostic (1D). Service the drive using the recommended service guidelines specified in Section 20.15.1 "Drive Service Strategy", if the power cycle or the Send Diagnostic (1D) command fail to complete successfully. 3.
PAGE 328
- Abort command sense, then service the drive using the service guideline recommended in Section 20.15.1 "Drive Service Strategy". - Sense Key = B (Aborted Command) and an Additional Sense Code of 47 can be an initiator or Drive caused abort condition. The initiator should follow the above procedure for initiator caused abort conditions if the Drive detected the SCSI bus parity error.
PAGE 329
20.15.4.12 Self Initiated Reset The Drive will initiate a self reset when the condition of the Drive cannot be determined. The internal reset will terminate any outstanding commands, release any reserved initiators, and stop the spindle motor. The initiator can recover by 1. Logging the error 2. Retrying the failing command. If the failing command completes with: - Good Status, return to normal processing - Self initiated reset sense, service the drive according the guidelines recommended in Section 20.
PAGE 330
20.15.4.15 Microcode Error The microcode from the interface is validated before the device operates using that microcode. When the validation detects incorrect or incomplete data, the Drive enters degraded mode. If the initiator attempted to load microcode using the Write Buffer (3B) retry the Write Buffer (3B). If the command completes with - Good Status - return to normal processing Check Condition Status - service the drive using the service guidelines recommended in Section 20.15.
PAGE 331
21 Firmware Security This chapter provides information on HGST encryption-specific HDD firmware and features. reader is familiar with the referenced specifications and industry standards. 21.1 It is assumed that the Referenced Specifications and Standards 21.1.1 TCG Specifications This section references 3 separate TCG specifications, which are available on the TCG website: (http://www.trustedcomputinggroup.org/): 1. TCG Core Specification, Version 1.0, Revision 0.
PAGE 332
• [SP800-38F] Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping, NIST, 2012 December • [SP800-57] Recommendation for Key Management – Part I General (Revision 3), NIST, 2012 July • [SP800-90A] Recommendation for Random Number Generation Using Deterministic Random Bit Generators, NIST, 2012 Jan • [SP800-131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths, NIST, 2011 Jan • [SP800-132] Recommendation for Password-Based Key
PAGE 333
21.1.4 Department of Defense DoD 5220.22-M, "National Industrial Security Program Operating Manual", 2/28/2006 http://www.dtic.mil/whs/directives/corres/pdf/522022m.pdf DoD 5220.22-M Supplement 1, “National Industrial Security Program Operating Manual Supplement”, 02/1995 http://www.dtic.mil/whs/directives/corres/pdf/522022MSup1.pdf 21.1.5 RSA Laboratories Standards 1. RSA-PSS - http://www.rsa.com/rsalabs/node.asp?id=2146 2. RSA PKCS #5 v2.0 Password-Based Cryptography Standard ftp://ftp.rsasecurity.
PAGE 334
21.4 21.4.1 Encryption Algorithms Advanced Encryption Standard (AES) Support AES encryption is implemented in hardware, with support for ECB or XTS mode for 128 bit or 256 bit keys. A single key is active at any one time within the AES hardware engine. Firmware is responsible for reading the keys from the hardware and also for determining which key is attached to a given LBA range; the hardware can only detect if the LBA has been encrypted or not.
PAGE 335
21.4.2.1 T10 End-To-End Data Protection AES encryption is performed after T10 end-to-end data protection data has been added, so that the T10 information is encrypted along with the customer data. 21.4.3 Deterministic Random Bit Generation (DRBG) Pseudo-random number generation is implemented with a certified NIST SP800-90A DRBG. The DRBG uses AES as a primitive for both entropy mixing and entropy output.
PAGE 336
21.5 TCG SSC Tables Two copies of all TCG SCC tables and data structures are stored in the RID; one is used as a primary copy and the other as a backup copy. The backup copy is used in the event the primary copy becomes corrupted. Each time a write is executed to any TCG table, both the primary and backup copies of the tables are updated and saved in the RID. In the case of a corrupted copy, the good copy is always used to restore the corrupted copy to the correct state.
PAGE 337
21.5.2 K_AES_256 Table The K_AES_256 table has 64 rows, one row for each band that can be allocated by the user. The first row is for the “global range”, also known as Band 0. This table was implemented without the “Name”, “Common Name”, and “Key” Columns. Table 285 HGST Implementation of K_AES_256 Table UID (8 byte hex) MODE 00 00 08 06 00 00 00 01 23 00 00 08 06 00 00 00 02 23 .. .. 00 00 08 06 00 00 00 06 23 The mode is specified in the TCG Enterprise SSC as a “Vendor Unique” (VU) entry.
PAGE 338
21.5.4 Locking Info Table As specified in the TCG Enterprise SSC, this table has only 1 row. The “Vendor Unique” entries are specified in the table below. Encryption Support is initialized to Encryption Support=23 (media encryption mode) in manufacturing. Table 287 HGST Implementation of Locking Info Table NAME Version Encrypt Support 0 0 23 21.5.5 Max Ranges Max ReEncryptions 0 Keys Available Cfg 0 0 Locking SP Locking Table The “Vendor Unique” (VU) values for this table are shown below.
PAGE 339
21.6 Firmware Download and Signing The HGST Firmware signing and download for encryption drives is meant to provide a mechanism for secure updates through the Host interface. Firmware is downloaded to the drive through the host interface, and the signature is verified using a public key installed in the reserved area during manufacturing, before it is loaded to RAM or installed in the reserved area on the HDD.
PAGE 340
Table 290 PSID Addition to Admin SP C_PIN table UID Name Common Name PIN CharSet TryLimit Tries Persistence 00 00 00 0B 00 01 FF 01 C_PIN_PSID PhysicalDriveOwner VU Null VU VU FALSE HGST Ultrastar C15K600 Hard Disk Drive Specification 340
PAGE 341
Table 291 Additions to AdminSP Access Control Table InvokingID AdminSPObj 00 00 02 05 00 00 00 01 PSID 00 00 00 09 00 01 FF 01 PSID 00 00 00 09 00 01 FF 01 MethodID ACL GetACLACL Revert 00 00 00 06 00 00 02 02 ACE_SP_SID_ACE_SP_PSID 00 00 00 08 00 01 00 E0 ACE_Anybody 00 00 00 08 00 00 00 01 Get 00 00 00 06 00 00 00 06 Anybody 00 00 00 08 00 00 00 01 Anybody 00 00 00 08 00 00 00 01 Set 00 00 00 06 00 00 00 07 ACE_Makers_Set_Enabled 00 00 00 08 0003 00 01 Get 00 00 00 06 00 00 00 06 ACE_C_PIN_G
PAGE 342
21.8 Ports The ports capability is an HGST feature which is not a requirement under TCG Enterprise SSC. In order to use the ports capabilities on encryption drives, the user must successfully authenticate. Once a user successfully authenticates, they may change the state of any of the ports at any time during an active session to either the locked or unlocked state. The functionality and definition of these ports is shown below in a table. The feature does make use of the TCG structures and tables.
PAGE 343
Table 294 Modified Admin SP ACE Table UID Name Cmn Name Boolean Expression Row Start Row End Column Start Column End 00 00 00 08 00 00 00 01 Anybody “” 00 00 00 09 00 00 00 01 Null Null ‘’’’ ‘’’’ 00 00 00 08 00 00 00 03 Makers ‘’’’ 00 00 00 09 00 00 00 03 Null Null ‘’’’ ‘’’’ 00 00 00 08 00 00 02 01 SID “” 00 00 00 09 00 00 00 06 Null Null ‘’’’ ‘’’’ 00 00 00 08 00 00 8C 03 SID_SetSelf “” 00 00 00 09 00 00 00 06 Null Null “PIN” “PIN” 00 00 00 08 00 00 8C 04 MSID_Get “
PAGE 344
VU VU VU 00 00 00 09 00 00 00 03 (Makers Authority object) 00 00 00 06 00 00 00 06 (Get) Anyboby-GetAnbody Authority Object 00 00 00 08 00 00 00 03 (Makers) None Null Null 00 00 00 08 00 00 00 03 (Makers) VU 00 00 00 09 00 00 00 06 (SID Authority object) 00 00 00 06 00 00 00 06 (Get) SID-Get-SID Authority Object 00 00 00 08 00 00 02 01 (SID) None Null Null 00 00 00 08 00 00 02 01 (SID) HGST Ultrastar C15K600 Hard Disk Drive Specification 344
PAGE 345
Table 296 Modified Admin SP Access Control Table (part 2 of 2) Row UID Number Log Invoking ID Method ID Common Name ACL VU 00 00 00 0B 00 00 00 00 (C_PIN table) 00 00 00 06 00 00 00 08 (Next) Makers-Next-C_ PIN table 00 00 00 08 00 00 00 02 (Makers) VU 00 00 00 0B 00 00 00 01 (SID C_PIN object) 00 00 00 06 00 00 00 07 (Set) SID_Set Self-Set-SID_C_ PIN object 00 00 00 08 00 00 8C 03 (SID_SetSelf) VU 00 00 00 0B 00 00 84 02 (MSID C_PIN object) 00 00 00 06 00 00 00 06 (Get) MSID_Get-GetMSID C
PAGE 346
21.9 MSID The MSID is set for each drive at the time of manufacturing to the serial number concatenated 4 times, to create a 32 byte password. Thus, as an example, if the serial number of a drive is abcd1234, the MSID would then be set to abcd1234abcd1234abcd1234abcd1234. In TCG use cases such as “erase” or “repurpose”, this will be the MSID that is restored to the drive.
PAGE 347
21.14 Locked and Unlocked Behavior 21.14.1 T10 SCSI commands The table below describes how basic T10 SCSI commands behave on encryption drives in the locked and unlocked states.
PAGE 348
Table 298 T10 SCSI Commands Behavior Table (part 2 of 2) Command SEND DIAGNOSTIC (1D) SET DEVICE IDENTIFIER (A4/06) START STOP UNIT (1B) SYNCHRONIZE CACHE (10) - (35) SYNCHRONIZE CACHE (16) - (91) TEST UNIT READY (00) VERIFY (2F) VERIFY (12) - (AF) VERIFY (16) - (8F) VERIFY (32) - (7F/0A) WRITE (6) - (0A) WRITE (10) - (2A) WRITE (12) - (AA) WRITE (16) - (8A) WRITE (32) - (7F/0B) WRITE AND VERIFY (10) - (2E) WRITE AND VERIFY (12) - (AE) WRITE AND VERIFY (16) - (8E) WRITE AND VERIFY (32) - (7F/0C) WRITE BUFFE
PAGE 349
21.14.2 TCG SSC Commands The table below describes how the required TCG Enterprise SSC commands behave on encryption drives in the locked and unlocked states. The TCG SSC requires the implementation of the Base, Admin, Locking, and Crypto Templates. As noted, the Crypto template was not implemented. In addition the SSC does not require any Admin Template tables or methods, so they are not mentioned in the table below.
PAGE 350
Table 302 TCG Enterprise SSC Commands Behavior -4 Command Description Base Template Mandatory Set Sets a value in a table Get ParamCheck LRC Next Authenticate GatACL Gets (reads) a value in a table unlocked N/A - table operations. N/A - table Not related to operations. Not bands/data on drive. related to bands/data on drive. N/A - table operations. N/A - table Not related to operations. Not bands/data on drive. related to bands/data on drive.
PAGE 351
21.15 Error Codes All error codes are compliant with the TCG Core specification and SIIF, except in the following case: • The maximum sessions allowed at any single time is 1. When a session is active and a new session is requested, the drive answers the host with SP_BUSY, instead of NO_SESSIONS_AVAILABLE. 21.16 Customer Specific Requirements This specification does not cover customer-specific requirements.
PAGE 352
22 SCSI Sense Data 22.1 SCSI Sense Data Format Introduction Sense data is returned as CHECK CONDITION status and as parameter data in response to the REQUEST SENSE command. The sense data returned by the drive can be in either fixed or descriptor format 22.1.1 Sense Data Format Format of sense data returned as a CHECK_CONDITION_STATUS is based on the value of the D_SENSE bit in the Control mode page (See section 18.10.9 "Mode Page 0A").
PAGE 353
22.2 Fixed Format Sense Data Table 296 following table shows the format of fixed format of the sense data returned by the drive.
PAGE 354
22.2.1 Valid (Bit 7 of byte 0) 0 The Information Bytes (byte 3 through 6) are not defined. 1 The Information Bytes (byte 3 through 6) contain a valid logical block address. 22.2.2 Response Code (Bit 6 - 0 of byte 0) 70h Current Error. See section 22.1.3 "Sense Data Response Code" for more details. 71h Deferred Error. See section 22.1.3 "Sense Data Response Code" for more details. 22.2.
PAGE 355
22.2.4 Sense Key (Bit 3 - 0 of byte 2) The sense key provides generic categories in which error and exception conditions can be reported. Initiators would typically use sense keys for high level error recovery procedures. 0h 1h 2h 3h 4h 5h 6h 7h 8h 9h Ah Bh Ch-Dh Eh Fh No Sense There is no sense key information to be reported for the logical unit. Recovered Error The last command completed successfully with some recovery action performed by the drive.
PAGE 356
22.2.5 Information Bytes (Byte 3 through 6) This field is only valid when VALID bit is one. - ILI = 0: This field contains the unsigned LBA associated with the sense key. The LBA reported will be within the LBA range of the command as defined in the CDB. Note: An LBA other than the command LBA may be reported on the Reassign Block (07h) command. Note: When the value that need to be stored in the Information field is greater than 0xFFFFFFFF (e.g.
PAGE 357
22.2.8 Additional Sense Code/Qualifier (Byte 12 and 13) The following table shows the description of the combination of Sense Key / Sense Code / Qualifier.
PAGE 358
2A05 SMART: Background Media Scan Failure (Recovered Sense) 3A05 SMART: Background Media Scan Failure (Unit Attention) 0 5D 21 Milli-Actuator Error 1A21 SMART: Milli-Actuator Error (No Sense) 2A21 SMART: Milli-Actuator Error (Recovered Sense) 3A21 SMART: Milli-Actuator Error (Unit Attention) 0 5D 22 Extreme Over-Temperature Warning 1A22 SMART: Extreme Over-Temperature Warning (No Sense) 2A22 SMART: Extreme Over-Temperature Warning (Recovered Sense) 3A22 SMART: Extreme Over-Temperature Warning (Unit A
PAGE 359
2A4A SMART: Write Error Rate Warning (Recovered Sense) 3A4A SMART: Write Error Rate Warning (Unit Attention) 0 5D 63 Seek Error Rate Warning 1A43 SMART: Seek Error Rate Warning (No Sense) 2A43 SMART: Seek Error Rate Warning (Recovered Sense) 3A43 SMART: Seek Error Rate Warning (Unit Attention) 0 5D 64 Spare Sector Availability Warning 1A14 SMART: Spare Sector Availability Warning (No Sense) 2A14 SMART: Spare Sector Availability Warning (Recovered Sense) 3A14 SMART: Spare Sector Availability Warning (
PAGE 360
1835 CMD: Power Mode Idle_A By Command 0 5E 04 Standby_Z Condition activated by Command 1838 CMD: Power Mode Standby_Z By Command 0 5E 05 Idle_B Condition activated by timer 1832 CMD: Power Mode Idle_B By Timer 0 5E 06 Idle_B Condition activated by Command 1836 CMD: Power Mode Idle_B By Command 0 5E 07 Idle_C Condition activated by timer 1833 CMD: Power Mode Idle_C By Timer 0 5E 08 Idle_C Condition activated by Command 1837 CMD: Power Mode Idle_C By Command 0 5E 09 Standby_Y Condition
PAGE 361
1737 Media: Recovered Post Write Abort Error 1739 Media: Recovered Post PES Check Write Abort Error 17E0 Media: Recovered Write Splice Error 1ECE Media: Recovered R/W Abort Due to Vibration Condition (Other) 1ED0 Media: Recovered R/W Abort Due to Vibration Condition (Estimator) 1ED2 Media: Recovered R/W Abort Due to Vibration Condition (Predictor) 1ED4 Media: Recovered R/W Abort Due to Vibration Condition (PES Error) 1ED6 Media: Recovered R/W Abort Off Track Write Error 1ED8 Media: Recovered R/W Abort RRO F
PAGE 362
1EF6 Media: Recovered R/W Abort Aggressive Error 1EF8 Media: Recovered R/W Abort SVGA Limit Error 1EFA Media: Recovered R/W Abort Gray Code Error 1EFC Media: Recovered R/W Abort Burst Error 1EFE Media: Recovered R/W Abort No STM Error 1 09 00 Track Following Error 1421 Servo: Recovered Track following error 1423 Servo: Recovered Track follow timeout 1 0C 01 Recovered Write Error with Auto Reallocation - Auto Reallocated D703 Media: Auto Reallocated Write Error 1 0C 03 Recovered Write Error - Reco
PAGE 363
1770 Media: Recovered SID Timeout Error 177C Media: Recovered Servo Area Timeout 17B2 Media: Recovered Abort Window Error 17EE Media: Recovered Sector Number Cylinder Error 1 16 00 Data Synchronization Mark Error 165C Channel: Recovered Mode Overlap Read Fault Error 1735 Channel: Recovered No Sync Detected Error 173B Media: Recovered Data Address Mark Error 17AA Media: Recovered Read Overrun Error 1 16 01 Data Sync Error - Data Rewritten E70E Media: Recovered Data Address Mark Error - Rewritten F70E
PAGE 364
172C Media: Recovered Data 172E Media: Recovered Error on Last Data Read 176C Media: Recovered MEDC Correctable Error 1782 Media: Recovered Force Soft Error 1784 Media: Recovered Channel Sector Marginal Error 17A5 Media: Recovered LBA ECC Last Data Read Error 17E6 Media: Recovered NRZ Sector Marginal Error 1 17 06 Recovered Data Without LDPC - Data Auto-Reallocated D705 Media: Error With OTF Correction - Reassigned 1 17 07 Recovered Data Without LDPC - Recommend Reassignment E706 Media: Error With OT
PAGE 365
F70A Media: Number of Zones Too Large 1 18 05 Recovered Data - Recommend Reassignment E70B Media: Error With Offline Correction - Recommend Reassign F70B Media: Max Head Number Too Large 1 18 06 Recovered Data With LDPC - Recommend Rewrite E70C Media: Error With Offline Correction - Recommend Rewrite F70C Media: Invalid RDD List Type 1 18 07 Recovered Data With LDPC - Data Rewritten E70D Media: Error With Offline Correction - Rewritten 1 1C 00 Defect List Format Not Supported 1746 Media: Reco
PAGE 366
1305 Motor: Recovered No feedback detected error 1307 Motor: Recovered Settle timeout 1309 Motor: Recovered Gross speed error 130B Motor: Recovered 12V OK error 130D Motor: Recovered Speed error 1311 Motor: Recovered Internal 12V not OK timeout 1313 Motor: Recovered Inductive Sense measurement timeout 1315 Motor: Recovered Spin Sense speed error 1319 Motor: Recovered Target speed error 131D Motor: Recovered Over current error 1321 Motor: Recovered Negative regulator fault 1323 Motor: Recovered Module overte
PAGE 367
140D Servo: Recovered Invalid 12 volts 140F Servo: Recovered Invalid harmonic requested 1411 Servo: Recovered Gain BEMF Calibration error 1413 Servo: Recovered VOFF BEMF calibration error 1415 Servo: Recovered Invalid temperature 1417 Servo: Recovered Truncated rezero 1419 Servo: Recovered Heads not loaded 1425 Servo: Recovered KT Seek out of range 1427 Servo: Recovered DAC Offset calibration error 1429 Servo: Recovered Load speed error 142D Servo: Recovered ADC Calibration error 142F Servo: Recovered ADC O
PAGE 368
1447 Servo: Recovered Load/Unload state error 1449 Servo: Recovered TFCR out-of-range error 144B Servo: Recovered Measure GMR Timeout 144D Servo: Recovered Coil Resistance Measurement Failure 145F Servo: Recovered WCS Hang Error 1461 Servo: Recovered DFT Timeout Error 1463 Servo: Recovered SDM Timeout Error 1465 Servo: Recovered RRO Write Error 1467 Servo: Recovered Velocity Error 1469 Servo: Recovered Start SID Incorrect Error 146B Servo: Recovered End Sid Incorrect Error 146D Servo: Recovered Measure GMR
PAGE 369
1496 Servo: Recovered DTID Inhibit Error 1498 Servo: Recovered DTID Unlock Error 149A Servo: Recovered SHARP Pulse TFC Entry Error 149C Servo: Recovered Heads Not Loaded FFSULI 149E Servo: Recovered Load Abort FFSULI 1606 AE: Recovered AE Last Data Read Error 1609 AE: Recovered TFC Short Error 160B AE: Recovered Shorted MR Element Error 1610 AE: Recovered ECS Shorted Fault 1612 AE: Recovered ECS Open Fault 1614 AE: Recovered ECS Fault 1616 Channel: Recovered Channel Error 161A AE: Recovered Open MR Element
PAGE 370
1644 AE: Recovered Latch Fault Error 1648 Channel: Recovered Reset Flag Error 164A Channel: Recovered Gate Command Queue Underflow Error 164C Channel: Recovered Sector Size Fault Error 164E Channel: Recovered Last Split Fault Error 1650 Channel: Recovered Servo-Servo Overlap Error 1652 Channel: Recovered Read Gate Fault Error 1654 Channel: Recovered RWBI Out Fault Error 1656 Channel: Recovered No Write Clock Error 1658 Channel: Recovered No NRZ Clock Error 165A Channel: Recovered Calibration Block Fault Err
PAGE 371
1676 Channel: Recovered Pfault Read Error 1678 Channel: Recovered Pfault Write Error 167A Channel: Recovered Last Data Fault Error 167C Channel: Recovered WRPO Fault Error 1680 Channel: Recovered PLLFloor Error 1682 Channel: Recovered Losslock Error 1684 Channel: Recovered VGA Floor Error 1686 Channel: Recovered Buffer EVGA Floor Error 1688 Channel: Recovered TA Detector Error 168A Channel: Recovered NPLD Error 168C Channel: Recovered ZGR Flag Error 168E Channel: Recovered DPLL Freq Flag Error 1690 Channel:
PAGE 372
16A8 Channel: Recovered RLL Parameter Error 16AA Channel: Recovered FIFO Underflow Error 16AC Channel: Recovered FIFO Overflow Error 16AE Channel: Recovered Iterative Decoder Error 16B0 Channel: Recovered Iterative Read Error 16B2 Channel: Recovered Encoder Overflow Error 16B4 Channel: Recovered Encoder Underflow Error 16B6 Channel: Recovered Encoder RAM CRC Error 16B8 Channel: Recovered Interface Fault 16BA Channel: Recovered QMM EVDump Parse Error 16BC Channel: Recovered DiBit Timeout Error 16BE Channel:
PAGE 373
16D6 Channel: Recovered ITI Fault TS Transfer All Error 16D8 Channel: Recovered ITI Data Fault Error 16DC Channel: Recovered Data Jam Fault Error 16DE Channel: Recovered Code-Word Out of Order Error 16E0 Channel: Recovered RLL Initialization Timeout Error 16E7 Channel: Recovered Mode Overlap Write Error 16E9 Channel: Recovered Ready Fault Error 16EB Channel: Recovered Sychronous Abort Done Error 16ED Channel: Recovered NRZ Clear Fault Error 16EF Channel: Recovered Collision Fault Error 16F1 Channel: Recover
PAGE 374
176E Media: Correctable Channel Ready Error 1786 Media: Recovered LLI Underrun Error 178C Media: Recovered FFSULI Timeout 1792 Media: Recovered MEDC Write Data Not Ready Error 1794 Media: Recovered DMA Timeout Error 1798 Media: Recovered ID Not Found Error 179C Media: Recovered Channel Read Timeout Error 17B4 Media: Recovered Shock Sensor Error 17C0 Media: Recovered End Sector Check Error 17C2 Media: Recovered Read CRC Error 17C4 Media: Recovered DRAM ECC Error 17C6 Medio: Recovered DRAM ECC LBA Error 17D4
PAGE 375
17F0 Media: Recovered Read Transfer Length Error 17F2 Media: Recovered DS RDC Burst Error 17F4 Media: Recovered SV RDC Burst Error 17F6 Media: Recovered Channel AE WG Error 1 44 0B Vendor Unique - Internal Target Failure 130F Motor: Recovered Spindle Current error 1317 Motor: Recovered Spin Sense timeout 131F Motor: Recovered System clock watchdog error 1329 Motor: Recovered VCM DAC watchdog error 132B Motor: Recovered Module mid-die overtemp fault 132D Motor: Recovered Module Vcmp hi-side overtemp fault
PAGE 376
1347 Motor: Recovered Predriver Reg UV error 1349 Motor: Recovered Predriver Under Voltage 12 Volt Supply error 134B Motor: Recovered Predriver Under Voltage 5 Volt Supply error 134D Motor: Recovered Predriver Over Voltage 12 Volt Supply error 134F Motor: Recovered Precriver Under Voltage 1.8 Volt Supply error 1351 Motor: Recovered Predriver Under Voltage 0.9 Volt Supply error 1353 Motor: Recovered Predriver Under Voltage 1.
PAGE 377
145D Servo: Recovered SHARP Other Rate Error 1 5D 01 Self Test Error 1A85 Self-Test: Recovery Error 2A85 Self-Test: Servo Error 4A85 Self-Test: Command Timeout Error FA85 Self-Test: Unrecoverable Error 1 5D 14 Self Test GLIST Error Threshold Reached 2A83 Self-Test: GLIST Error Count Threshold Reached Sense Key = Not Ready 2 04 00 Logical Unit Not Ready - Start Spindle Motor Fail F501 Host Interface: Logical unit not ready 2 04 01 Logical Unit Is In The Process of Becoming Ready F502 Host Inte
PAGE 378
2 04 0D Not Ready - Session opened F508 Host Interface: Not Ready - Session opened 2 04 11 Not Ready - Notify (Enable Spin-up) Required F553 Host Interface: LUN Not ready, Notify (Enable Spinup) required (SAS) 2 04 1B Host Interface Not Ready - Sanitize In Progress F50B Host Interface: Not Ready - Sanitize in progress 2 04 F0 Vendor Unique - Logical Unit Not Ready F133 BATS error: Vendor ID mismatch F54C Host Interface: LUN Not Ready - Super Certify in Progress 2 31 00 Medium Format Corru
PAGE 379
FED5 Media: Unrecovered R/W Abort Due to Vibration Condition (PES Error) FED7 Media: Unrecovered R/W Abort Off Track Write Error FED9 Media: Unrecovered R/W Abort RRO Field Misread Error FEDB Media: Unrecovered R/W Abort RRO Field Missing Error FEDD Media: Unrecovered R/W Abort Idle Seek Error FEDF Media: Unrecovered R/W Abort Seek Timeout Error FEE1 Media: Unrecovered R/W Abort Estimator Error FEE3 Media: Unrecovered R/W Abort Predictor Error FEE5 Media: Unrecovered R/W Abort PES Error FEE7 Media: Unrecove
PAGE 380
F7AC Media: Unrecovered Super Certification Log Write Error 3 0A 02 Unrecovered Super Certification Log Read Error F7AD Media: Unrecovered Super Certification Log Read Error 3 11 00 Unrecovered Read Error F67F Channel: Unrecovered Forced Channel Fault Error F702 Too many notches F71F Media: Unrecovered Read Latency Error F727 Media: Unrecovered Internal Write Catch Error F72D Media: Unrecovered Uncorrectable Read Data error F72F Media: Unrecovered Error on Last Data Read F730 Media: Recommend targete
PAGE 381
F756 Media: Unrecovered DST Slot Size Error F757 Media: Unrecovered P-list Full Error F758 Media: Unrecovered Invalid NFZ Table Error F75E Media: Unrecovered Maximum Servo Cylinder Number Too Small Error F76D Media: Unrecovered MEDC Uncorrectable Error F783 Medoa: Unrecovered Force Soft Error F785 Media: Unrecovered Channel Sector Marginal Error F7A6 Media: Unrecovered LBA ECC Last Data Read Error F7A7 Media: Unrecovered Committed Write Hard Error F7CE Media: Unrecovered Offline Already TAR Error F7E7 Media
PAGE 382
3 15 03 Unrecovered Sector Error F7AF Media: Unrecovered Sector Missing Error F7B0 Media: Unrecovered Sector Overflow 3 16 00 Data Synchronization Mark Error F65D Channel: Unrecovered Mode Overlap Read Fault Error F736 Channel: Unrecovered No Sync Detected Error F73C Media: Unrecovered Data Address Mark Error F7AB Media: Unrecovered Read Overrun Error 3 19 02 Defect List Error in Primary List F74B Media: Unrecovered Primary Defect List Error 3 19 03 Defect List Error in Grown List F74C Media:
PAGE 383
FF0A IndSys: Drive Not Loaded - Corrupt Rid FF0B IndSys: Drive Not Loaded - Rid Num Objects Mismatch FF0C IndSys: Drive Not Loaded - Rid Version Mismatch FF0D IndMgr: Drive Not Loaded - Rid Version Mismatch FF0E IndSys: Drive Not Loaded - Layout Rid Version Mismatch FF0F IndSys: Drive Not Loaded - W2C Rid Version Mismatch FF10 IndSys: Drive Not Loaded - Layout Manager Restore Failed FF11 IndSys: Drive Not Loaded - W2C Manager Restore Failed FF13 IndSys: Drive Not Loaded - DMM Format Failed FF14 IndSys: Driv
PAGE 384
FF20 IndSys: Drive Not Loaded - EPD Flash Entry Invalid FF21 LayoutMgr: All Flash Entries Erased FF41 LayoutMgr: Format Capacity Not Met 1F42 DlMgr: DLMGR Generic Fail FF43 IndSys: Drive Not Loaded - Metadata ATI FF44 IndSys: Drive Loaded - Replay Fail FF45 IndSys: W2C Return Not Written Failed FF50 IndMgr: IM Demand Split Too Deep Failure FF51 IndMgr: Allocate Failed Delta Group FF52 IndMgr: Allocate Failed Split Spec FF53 IndMgr: Allocate Failed Split Delta FF54 IndMgr: Allocate Failed Unsplit Delta Group
PAGE 385
F75F Media: Unrecovered SAT No Buffer Overflow Error 3 40 01 Unrecovered SAT Buffer Overflow Error F760 Media: Unrecovered SAT Buffer Overflow Error 3 40 02 Unrecovered SAT No Buffer Overflow With ECS Fault F78E Media: Unrecovered SAT No Buffer Overflow With ECS Fault 3 40 03 Unrecovered SAT Buffer Overflow With ECS Fault F78F Media: Unrecovered SAT Buffer Overflow With ECS Fault 3 5D 01 Self Test Unrecoverable Error Threshold Exceeded FA81 Self-Test: Unrecoverable Error Count Threshold Excee
PAGE 386
F205 G-list full - can't reassign any more sectors F206 No spares available 4 3E 03 Self-test Failed F481 Servo: Unrecovered Self-Test Failed F75D Media: Unrecovered Self-Test Failed Error 4 3E 04 Unrecovered Self-Test Hard-Cache Test Fail F762 Media: Unrecovered Self-Test Hard-Cache Test Fail 4 3E 05 Unrecovered Self-Test OTF-Cache Fail F763 Media: Unrecovered Self-Test OTF-Cache Fail 4 40 80 Diagnostic Failure F101 BATS error: Reserved Area - Invalid request F102 BATS error: Reserved Area -
PAGE 387
F123 BATS error: Reserved map index too large F125 BATS error: Invalid RID/FID F12B BATS error: Reserved area - invalid model F12D Format Reserved: FAT Size Exceeded Error F12E Format Reserved: Insufficient DIRS Good Error F12F Format Reserved: Insufficient FATS Good Error F131 Flash timeout F137 Flash ECC error F139 Format Reserved: Resize RID/FID Error F13B BATS error: SW Target broken F13C BATS error: NCDE DRAM failure F140 Format Reserved: Too many Defects Error F142 ATA Diagnostic Code: No Error F143 A
PAGE 388
4 40 81 DRAM Failure F12A DRAM test error 4 40 90 Diagnostic Failure F118 BATS#2 error: Seek test error 4 40 91 Diagnostic Failure F13E BATS#2 error: TCG Test Failed 4 40 A0 Diagnostic Failure F119 BATS#2 error: Read/write test error F11B BATS#2 error: CRC test error F11C BATS#2 error: XOR test error F136 BATS#2 error: End-To-End Data Protection error F13F BATS#2 error: Read/Write Test Compare Failed 4 44 00 Internal Target Failure F203 Sanity: Sanity Check Failure F208 Mode Page Structur
PAGE 389
F221 MFG: General Align Tables Missing F230 SEC_MGR: AES Hardware Error F231 SEC_MGR: BDE Unwrap Error F240 SEC_MGR: PRNG Seed Error F241 SEC_MGR: PRNG General Error F302 Motor: Unrecovered internal error F304 Motor: Unrecovered Open Loop Commutation failure F306 Motor: Unrecovered No feedback detected error F308 Motor: Unrecovered Settle timeout F30A Motor: Unrecovered Gross speed error F30C Motor: Unrecovered 12V OK error F30E Motor: Unrecovered Speed error F312 Motor: Unrecovered Internal 12V not OK time
PAGE 390
F368 Motor: Unrecovered Predriver BEMF Gain Calibration Error F36A Motor: Unrecovered Predriver BEMF Unload Calibration Error F402 Servo: Unrecovered Requested rezero head does not exist F404 Servo: Unrecovered Back EMF movement in progress F406 Servo: Unrecovered Back EMF timeout error F408 Servo: Unrecovered ADC conversion timeout F40A Servo: Unrecovered Load/unload calibration error F40C Servo: Unrecovered Invalid 5 volts F40E Servo: Unrecovered Invalid 12 volts F410 Servo: Unrecovered Invalid harmonic r
PAGE 391
F438 Servo: Unrecovered First Cylinder error F43A Servo: Unrecovered Valid Cylinder error F43C Servo: Unrecovered ADC Saturation error F43E Servo: Unrecovered Latch Break timeout F440 Servo: Unrecovered MR Resistance out of range error F442 Servo: Unrecovered VCM Retract error F444 Servo: Unrecovered Load Retry error F446 Servo: Unrecovered DFT Sharp error F448 Servo: Unrecovered Load/Unload state error F44A Servo: Unrecovered TFCR out-of-range error F44C Servo: Unrecovered Measure GMR Timeout F44E Servo: U
PAGE 392
F476 Servo: Unrecoverd Excessive Velocity Error F477 Servo: Unrecovered Invalid SDM CDB Error F478 Servo: Unrecovered Invalid SDM Descriptor Error F479 Servo: Unrecovered Invalid DFT Descriptor Error F47A Servo: Unrecovered SDM or DFT Allocation Error F47B Servo: Unrecovered SDM OR DFT Transfer Error F47C Servo: Unrecovered SDM Physical Paremeter Error F47E Servo: Unrecovered RROF SDM Timeout Error F480 Servo: Unrecovered RROF Over Limit Error F483 Servo: Unrecovered Measure Asymetry SDM Failure F484 Servo:
PAGE 393
F495 Servo: Unrecovered TFCR Open/Short F497 Servo: Unrecovered DTID Inhibit Error F499 Servo: Unrecovered DTID Unlock Error F49B Servo: Unrecovered SHARP Pulse TFC Entry Error F49D Servo: Unrecovered Heads Not Loaded FFSULI F49F Servo: Unrecovered Load Abort FFSULI F603 Channel/AE: Unrecovered Internal Target Failure F604 Channel/AE: Unrecovered Internal Calibration Error F605 Channel/AE: Unrecovered Internal MR Calibration Error F607 Channel/AE: Unrecovered data with PPM or precomp load F60A AE: TFC Short
PAGE 394
F627 AE: Unrecovered Power Supply Error F629 AE: Unrecovered Open Write Head Error F62B AE: Unrecovered Write Transition Error F631 AE: Unrecovered SPE Low In Write Fault F633 Channel: Unrecovered Write Synth Unlock error F637 AE: Unrecovered Short Write Head Error F63D AE: Unrecovered TFC Open Error F642 AE: Unrecovered Software Readback Error F643 AE: Unrecovered Readback Error F645 AE: Unrecovered Latch Fault Error F649 Channel: Unrecovered Reset Flag Error F64B Channel: Unrecovered Gate Command Queue Un
PAGE 395
F665 Channel: Unrecovered Write Gate Fault Error F667 Channel: Unrecovered Buffer Overflow Write Error F669 Channel: Unrecovered Buffer Underflow Write Error F66B Channel: Unrecovered Write Parity Error F66D Channel: Unrecovered Buffer Overflow Read Error F66F Channel: Unrecovered CTG Wedge Slip Fault Read Error F671 Channel: Unrecovered CTG Packet Late Fault Error F673 Channel: Unrecovered Baseline Instability Count Count Late Error F675 Channel: Unrecovered Preamp Count Fault Error F677 Channel: Unrecover
PAGE 396
F695 Channel: Unrecovered Flaw Signal Sync Error F697 Channel: Unrecovered ACQ Flag Error F699 Channel: Unrecovered No Clock Error F69B Channel: Unrecovered PLL Losslock Error F69D Channel: Unrecovered ESNR Timeout Error F69F Channel: Unrecovered ADC Sample Not Ready Error F6A0 AE: Unrecovered Fuse Load Fail Error F6A1 AE: Unrecovered Configuration Error F6A3 Channel: Unrecovered Auto RST NRZ-Clock Error F6A5 Channel: Unrecovered Write CRC Fault Error F6A7 Channel: Unrecovered Read Synthesizer Loss of Lock
PAGE 397
F6C1 Channel: Unrecovered Data Jam Error F6C3 Channel: Unrecovered Code-Word Out Of Order Error F6C5 Channel: Unrecovered Read RLL Buffer CRC Flag Error F6C7 Channel: Unrecovered Write RLL Buffer CRC Flag Error F6C9 Channel: Unrecovered CTG No SAM Detected Fault Error F6CB Channel: Unrecovered ITI Adjust Preload Fault Track Error F6CD Channel: Unrecovered WTG SRV Fault Error F6CF Channel: Unrecovered CTG Engine Not Ready Fault Error F6D1 Channel: Unrecovered LLI Abort Fault Error F6D3 Channel: Unrecovered R
PAGE 398
F6E8 Channel: Unrecovered Mode Overlap Write Error F6EA Channel: Unrecovered Ready Fault Error F6EC Channel: Unrecovered Sychronous Abort Done Error F6EE Channel: Unrecovered NRZ Clear Fault Error F6F0 Channel: Unrecovered Collision Fault Error F6F2 Channel: Unrecovered Read Synthesizer Precharge Fail Fault Error F6F4 Channel: Unrecovered Servo Synthesizer Precharge Fail Fault Error F6F6 Channel: Unrecovered Read Synthesizer Loss of Lock Error F6F8 Channel: Unrecovered Fragment Number Fault Error F6FA Chann
PAGE 399
F76F Media: Uncorrectable Channel Ready Error F787 Media: Unrecovered LLI Underrun Error F78D Media: Unrecovered FFSULI Timeout F793 Media: Unrecovered MEDC Write Data Not Ready error F795 Media: Unrecovered DMA Timeout Error F799 Media: Unrecoverd ID Not Found Error F79D Media: Unrecovered Channel Read Timeout Error F7B5 Media: Unrecovered Shock Sensor Error F7C1 Media: Unrecovered End Sector Check Error F7C3 Media: Unrecovered Read CRC Error F7C5 Media: Unrecovered DRAM ECC Error F7C7 Media: Unrecovered D
PAGE 400
F7ED Media: Unrecovered LBA FIFO Error F7F1 Media: Unrecovered Read Transfer Length Error F7F3 Media: Unrecovered DS RDC Burst Error F7F5 Media: Unrecovered SV RDC Burst Error F7F7 Media: Unrecovered Channel AE WG Error FCxx Media: Unrecovered Unable to Read RID or FID Number xx 4 44 0B Vendor Unique - Internal Target Failure F310 Motor: Unrecovered Spindle Current error F318 Motor: Unrecovered Spin Sense timeout F320 Motor: Unrecovered System clock watchdog error F32A Motor: Unrecovered VCM DAC watchdog
PAGE 401
F344 Motor: Unrecovered Predriver NREG UV error F346 Motor: Unrecovered Predriver Ext NPOR error F348 Motor: Unrecovered Predriver Reg UV error F34A Motor: Unrecovered Predriver Under Voltage 12 Volt Supply error F34C Motor: Unrecovered Predriver Under Voltage 5 Volt Supply error F34E Motor: Unrecovered Predriver Over Voltage 12 Volt Supply error F350 Motor: Unrecovered Precriver Under Voltage 1.8 Volt Supply error F352 Motor: Unrecovered Predriver Under Voltage 0.
PAGE 402
F452 Servo: Unrecovered SHARP Parity Rate Error F456 Servo: Unrecovered SHARP Decode Rate Error F45A Servo: Unrecovered SHARP Timeout Rate Error F45E Servo: Unrecovered SHART Other Rate Error 4 44 FA Vendor Unique - Internal Target Failure F450 Servo: Unrecovered SHARP Parity Error F454 Servo: Unrecovered SHARP Decode Error F458 Servo: Unrecovered SHARP Timeout Error F45C Servo: Unrecovered SHARP Other Error 4 81 00 Vendor Unique - Internal Logic Error F549 Host Interface: LA Check error F54D Host In
PAGE 403
5 20 00 Invalid Command Operation Code F821 CMD: Unrecovered Invalid Opcode in CDB Error 5 21 00 Logical Block Address out of Range F822 CMD: Unrecovered LBA Out Of Range Error 5 22 00 Unsafe Format F82A CMD: Unsafe Format 5 24 00 Invalid Field in CDB F823 CMD: Unrecovered Invalid Field In CDB Error 5 25 00 Logical Unit Not Supported F824 CMD: Unrecovered Invalid LUN Error 5 26 00 Invalid Field in Parameter List F579 Host Interface: Data Checksum Error F825 CMD: Unrecovered Invalid Fi
PAGE 404
F828 CMD: Unrecovered Invalid Release of Persistent Reservation Error 5 2A 03 Reservation Conflict F536 Host Interface: Reservation conflict 5 2C 00 Illegal Request Sequence Error F511 Host Interface: Illegal Request Sequence Error 5 49 00 Invalid Message Error F512 Host Interface: Invalid Message 5 55 04 Insufficient Registration Resources F567 Host Interface: Insufficient registration resources Sense Key = Unit Attention 6 28 00 Not Ready To Ready Transition (Format completed) F514 Host
PAGE 405
F51C Host Interface: Mode parameters changed 6 2A 02 Log Parameters Changed F51D Host Interface: Log parameters changed 6 2A 03 Reservations Preempted F51E Host Interface: Reservations pre-empted 6 2A 04 Reservations Released F51F Host Interface: Reservations released 6 2A 05 Registrations Released F520 Host Interface: Registrations pre-empted 6 2A 09 Capacity Data Changed F524 Host Interface: Capacity Data Changed 6 2F 00 Commands Cleared by Another Initiator F521 Host Interface: Com
PAGE 406
Sense Key = Aborted Command B 0E 01 Information Unit Too Short F561 Host Interface: Information unit too short (SAS) B 0E 02 Information Unit Too Long F562 Host Interface: Information unit too long (SAS) B 10 01 Aborted Command – End-to-End Guard Check F568 Host Interface: End-to-End Data Protection Guard check F7BD Media: Unrecovered Guard Check Error B 10 02 Aborted Command – End-to-End Application Tag Check F569 Host Interface: End-to-End Data Protection Application Tag check F7BB Media: U
PAGE 407
F570 Host Interface: Host interface Synchronous CRC error F57A Host Interface: Synchronous CRC Error on Write F57B Host Interface: Synchronous CRC LBA Error F62F Channel: Unrecovered Channel NRZ Clear Timeout Error F741 Media: OCT Timeout Not Dispatched F742 Media: OCT Timeout In Recovery F743 Media: OCT Timeout Executing F75C Media: Unrecovered Internal Media Access Timeout Error F772 Media: Unrecovered DASH starting timeout F773 Media: Unrecovered ID table timeout F774 Media: Unrecovered Servo timeout F77
PAGE 408
B 4B 00 Data Phase Error F53E Host Interface: Data phase error B 4B 02 Too Much Write Data F560 Host Interface: Too much write data (SAS) B 4B 03 ACK/NAK Timeout F551 Host Interface: ACK NAK Timeout (SAS) F57D Host Interface: Break Received (SAS only) B 4B 04 NAK Received F550 Host Interface: NAK rcvd (SAS) B 4B 05 Data Offset Error F552 Host Interface: Bad parameter offset (SAS) B 4B 06 Initiator Response Timeout F555 Host Interface: Initiator Response Timeout (SAS) B 4E 00 Overl
PAGE 409
22.2.9 FRU: Field Replaceable Unit (Byte 14) The FRU (Field Replaceable Unit) field value will always be zero. Note: The FRU field may be used to store vendor specific information in certain firmware builds. 22.2.10 Sense Key Specific (Byte 15 through 17) The definition of this field is determined by the value of the sense key field. 22.2.10.1 Sense Key Specific - Illegal Request (Sense Key = 5h) Error field pointer is returned.
PAGE 410
22.2.10.2 Sense Key Specific -Recovered (Sense Key = 1h) or Medium (Sense Key = 3h) or Hardware (Sense Key = 4h) Hardware (Sense Key = 4h) or Medium Error (Sense Key = 3h) Actual Retry Count is reported. Table 310 Actual Retry Count Bit Byte 7 15 6 5 4 SKSV 2 1 0 Reserved 16 Secondary Step 17 SKSV 3 ERP Type Actual Retry Count Sense-key specific valid 0 Actual Retry Count is not valid. 1 Actual Retry Count is valid.
PAGE 411
22.2.10.3 Not Ready (Sense key = 2h) These fields are defined for the Format unit (04h) command with the Immediate bit set to one and the Send Diagnostic (1Dh) command with Background self-test function. Progress indication is returned. Table 312 Progress Indication Bit Byte 7 15 16 17 6 5 4 SKSV 3 2 1 0 Reserved (MSB) Progress Indication (LSB) 22.2.11 Reserved (Byte 18 through 19) SKSV Progress Indication Sense-key specific valid 0 Progress Indication is not valid.
PAGE 412
22.2.13 Physical Error Record (Product Specific Information) 24 thru 29) (Byte  ILI = 1 - This field contains zeros.  ILI = 0 - These bytes contain the physical location of the error in cylinder, head, and sector. Bytes 24, 25, and 26 are cylinder high, middle and low bytes respectively, of the cylinder number. Byte 27 is the head number. Bytes 28 and 29 are the high and low bytes, respectively of the sector number. If the head is undetermined, bytes 24, 25, and 26 are set to 0FFFFFFh.
PAGE 413
22.3 Descriptor Format Sense Data The descriptor format sense data for response codes 72h (current errors) and 73h (deferred errors) is defined below. Table 314 Descriptor Format Sense Data Bit Byte 7 0 6 5 4 Reserved= 0 1 3 2 1 0 Response Code (72h or 73h) Reserved Sense Key 2 Additional Sense Code 3 Additional Sense Code Qualifier 4-6 Reserved 7 Additional Sense Length (n-7) 8-m Sense Data Descriptor m...x . x -n . . . . . . . . #1 . . Sense Data Descriptor . .
PAGE 414
The Descriptor Type identifies the type of a sense data descriptor.
PAGE 415
22.3.2 Sense Data Descriptor Definitions 22.3.2.1 Information Sense Data Descriptor (Byte 8 - 19) The Information Sense Data Descriptor is stored in bytes 8 through 19 of the descriptor format sense data.
PAGE 416
22.3.2.2 Command-specific Sense Data Descriptor (Byte 20 - 31) The Command-specific Sense Data Descriptor is stored in bytes 20 through 31 of the descriptor format sense data. Format of the format of Command-specific Sense Data Descriptor is shown in Table 310.
PAGE 417
22.3.2.4 Field Replaceable Unit (FRU) Sense Data Descriptor (Byte 40 - 43) The Field Replaceable Unit (FRU) Sense Data Descriptor is stored in bytes 40 through 43 of descriptor format sense data. Format of Field Replaceable Unit (FRU) Sense Data Descriptor is shown in Table 312.
PAGE 418
22.3.2.6 Vendor Unique Unit Error Sense Data Descriptor 48 – 51) (Byte The Vendor Unique Unit Error Code Sense Data Descriptor is stored in bytes 48 through 51 of descriptor format sense data. Format of the Vendor Unique Unit Error Code Sense Data Descriptor is shown in Table 314.
PAGE 419
23 Appendix. UEC list Following is the list of Unit Error Codes and associated descriptions. The Unit Error Codes are returned by the target in sense data bytes 20-21. The list of Unit Error Codes and descriptions does not have a direct correlation to the error descriptions and Sense Key/Code/Qualifier descriptions in Section 20 "Additional information". These codes are used internally by HGST and may change without notice. How to find a specific UEC The second hex digit indicates the grouping, e.g.
PAGE 420
F123 BATS error: Reserved map index too large F124 Bring-up error F125 BATS error: Invalid RID/FID F126 BATS error: Code checksum error F127 BATS error: Invalid header F12A DRAM test error F12B BATS error: Reserved area - invalid model F12D Format Reserved: FAT Size Exceeded Error F12E Format Reserved: Insufficient DIRS Good Error F12F Format Reserved: Insufficient FATS Good Error F130 BATS error: Incorrect Customer Code F131 Flash timeout F132 GEM FH track read error F133 BATS er
PAGE 421
F149 BATS#2 error: Security: AES Error F14A BATS#2 error: Security: RSA Error F14B BATS#2 error: Security: DRGB Error F14C BATS#2 error: Security: SHA256 Error F14D BATS#2 error: Security: HMAC Error F14E BATS#2 error: Security: Hardware AES Error 1201 Sanity: Error In UEC Class 1202 Sanity: Error In UEC Cause F203 Sanity: Sanity Check Failure F204 Reassign reserved area media error F205 G-list full - can't reassign any more sectors F206 No spares available F208 Mode Page Structure
PAGE 422
F304 Motor: Unrecovered Open Loop Commutation failure 1305 Motor: Recovered No feedback detected error F306 Motor: Unrecovered No feedback detected error 1307 Motor: Recovered Settle timeout F308 Motor: Unrecovered Settle timeout 1309 Motor: Recovered Gross speed error F30A Motor: Unrecovered Gross speed error 130B Motor: Recovered 12V OK error F30C Motor: Unrecovered 12V OK error 130D Motor: Recovered Speed error F30E Motor: Unrecovered Speed error 130F Motor: Recovered Spindle Curre
PAGE 423
F324 Motor: Unrecovered Module overtemp error 1325 Motor: Recovered 12V or 5V OK error F326 Motor: Unrecovered 12V or 5V OK error 1327 Motor: Recovered unknown error F328 Motor: Unrecovered unknown error 1329 Motor: Recovered VCM DAC watchdog error F32A Motor: Unrecovered VCM DAC watchdog error 132B Motor: Recovered Module mid-die overtemp fault F32C Motor: Unrecovered Module mid-die overtemp fault 132D Motor: Recovered Module Vcmp hi-side overtemp fault F32E Motor: Unrecovered Module V
PAGE 424
1343 Motor: Recovered Predriver NREG UV error F344 Motor: Unrecovered Predriver NREG UV error 1345 Motor: Recovered Predriver Ext NPOR error F346 Motor: Unrecovered Predriver Ext NPOR error 1347 Motor: Recovered Predriver Reg UV error F348 Motor: Unrecovered Predriver Reg UV error 1349 Motor: Recovered Predriver Under Voltage 12 Volt Supply error F34A Motor: Unrecovered Predriver Under Voltage 12 Volt Supply error 134B Motor: Recovered Predriver Under Voltage 5 Volt Supply error F34C Moto
PAGE 425
1361 Motor: Recovered Predriver Error in Utilizing External Power Supply F362 1363 Motor: Unrecovered Predriver Error in Utilizing External Power Supply Motor: Recovered Predriver Regulator Supply Fault F364 Motor: Unrecovered Predriver Regulator Supply Fault 1365 Motor: Recovered Predriver Voltage Offset Calibration Error F366 Motor: Unrecovered Predriver Voltage Offset Calibration Error 1367 Motor: Recovered Predriver BEMF Gain Calibration Error F368 Motor: Unrecovered Predriver BEMF Gain Cal
PAGE 426
1415 Servo: Recovered Invalid temperature F416 Servo: Unrecovered Invalid temperature 1417 Servo: Recovered Truncated rezero F418 Servo: Unrecovered Truncated rezero 1419 Servo: Recovered Heads not loaded F41A Servo: Unrecovered Heads not loaded 141B Servo: Recovered Current error F41C Servo: Unrecovered Current error 141D Servo: Recovered Seek timeout F41E Servo: Unrecovered Seek timeout 141F Servo: Recovered Seek error F420 Servo: Unrecovered Seek error 1421 Servo: Recovered Track
PAGE 427
F434 Servo: Unrecovered Balancer Resistance error 1435 Servo: Recovered Balancer Resistance Limit error F436 Servo: Unrecovered Balancer Resistance Limit error 1437 Servo: Recovered First Cylinder error F438 Servo: Unrecovered First Cylinder error 1439 Servo: Recovered Valid Cylinder error F43A Servo: Unrecovered Valid Cylinder error 143B Servo: Recovered ADC Saturation error F43C Servo: Unrecovered ADC Saturation error 143D Servo: Recovered Latch Break timeout F43E Servo: Unrecovered L
PAGE 428
1453 Servo: Recovered SHARP Decode Error F454 Servo: Unrecovered SHARP Decode Error 1455 Servo: Recovered SHARP Decode Rate Error F456 Servo: Unrecovered SHARP Decode Rate Error 1457 Servo: Recovered SHARP Timeout Error F458 Servo: Unrecovered SHARP Timeout Error 1459 Servo: Recovered SHARP Timeout Rate Error F45A Servo: Unrecovered SHARP Timeout Rate Error 145B Servo: Recovered SHARP Other Error F45C Servo: Unrecovered SHARP Other Error 145D Servo: Recovered SHARP Other Rate Error F45
PAGE 429
F472 Servo: Unrecoverd Emergency Brake Timeout Error 1473 Servo: Recovered Excessive Current Error F474 Servo: Unrecoverd Excessive Current Error 1475 Servo: Recovered Excessive Velocity Error F476 Servo: Unrecoverd Excessive Velocity Error F477 Servo: Unrecovered Invalid SDM CDB Error F478 Servo: Unrecovered Invalid SDM Descriptor Error F479 Servo: Unrecovered Invalid DFT Descriptor Error F47A Servo: Unrecovered SDM or DFT Allocation Error F47B Servo: Unrecovered SDM OR DFT Transfer Erro
PAGE 430
F491 Servo: Unrecovered Tilt Numerical Error F492 Servo: Unrecovered Milli Table Load Error F493 Servo: Unrecovered TFCR DAC Out of Range F494 Servo: Unrecovered MRR DAC Out of Range F495 Servo: Unrecovered TFCR Open/Short 1496 Servo: Recovered DTID Inhibit Error F497 Servo: Unrecovered DTID Inhibit Error 1498 Servo: Recovered DTID Unlock Error F499 Servo: Unrecovered DTID Unlock Error 149A Servo: Recovered SHARP Pulse TFC Entry Error F49B Servo: Unrecovered SHARP Pulse TFC Entry Error
PAGE 431
F516 Host Interface: Power on reset F517 Host Interface: SAS Hard Reset (SAS) F518 Host Interface: LUN Reset (SAS) F519 Host Interface: Self initiated reset F51C Host Interface: Mode parameters changed F51D Host Interface: Log parameters changed F51E Host Interface: Reservations pre-empted F51F Host Interface: Reservations released F520 Host Interface: Registrations pre-empted F521 Host Interface: Commands cleared by another initiator F522 Host Interface: Microcode changed F524 Host I
PAGE 432
F554 Host Interface: I_T_Nexus Loss Occurred (SAS) F555 Host Interface: Initiator Response Timeout (SAS) F560 Host Interface: Too much write data (SAS) F561 Host Interface: Information unit too short (SAS) F562 Host Interface: Information unit too long (SAS) F565 Host Interface: Not Ready - in Dell DEFT F567 Host Interface: Insufficient registration resources F568 Host Interface: End-to-End Data Protection Guard check F569 Host Interface: End-to-End Data Protection Application Tag check F5
PAGE 433
F60E Init: RRClk Dead Error F60F Init: RRClk Unlock Error 1610 AE: Recovered ECS Shorted Fault F611 AE: Unrecovered ECS Shorted Fault 1612 AE: Recovered ECS Open Fault F613 AE: Unrecovered ECS Open Fault 1614 AE: Recovered ECS Fault F615 AE: Unrecovered ECS Fault 1616 Channel: Recovered Channel Error F617 Channel: Unrecovered Channel Error 161A AE: Recovered Open MR Element Error F61B AE: Unrecovered Open MR Element Error 161C AE: Recovered IC Over Temperature Error F61D AE: Unrec
PAGE 434
163C AE: Recovered TFC Open Error F63D AE: Unrecovered TFC Open Error F642 AE: Unrecovered Software Readback Error F643 AE: Unrecovered Readback Error 1644 AE: Recovered Latch Fault Error F645 AE: Unrecovered Latch Fault Error 1648 Channel: Recovered Reset Flag Error F649 Channel: Unrecovered Reset Flag Error 164A Channel: Recovered Gate Command Queue Underflow Error F64B Channel: Unrecovered Gate Command Queue Underflow Error 164C Channel: Recovered Sector Size Fault Error F64D Chann
PAGE 435
F661 Channel: Unrecovered Ending Write Splice Fault Error 1662 Channel: Recovered Write Gate Overlap Fault Error F663 Channel: Unrecovered Write Gate Overlap Fault Error 1664 Channel: Recovered Write Gate Fault Error F665 Channel: Unrecovered Write Gate Fault Error 1666 Channel: Recovered Buffer Overflow Write Error F667 Channel: Unrecovered Buffer Overflow Write Error 1668 Channel: Recovered Buffer Underflow Write Error F669 Channel: Unrecovered Buffer Underflow Write Error 166A Channel:
PAGE 436
1680 Channel: Recovered PLLFloor Error F681 Channel: Unrecovered PLLFloor Error 1682 Channel: Recovered Losslock Error F683 Channel: Unrecovered Losslock Error 1684 Channel: Recovered VGA Floor Error F685 Channel: Unrecovered VGA Floor Error 1686 Channel: Recovered Buffer EVGA Floor Error F687 Channel: Unrecovered Buffer EVGA Floor Error 1688 Channel: Recovered TA Detector Error F689 Channel: Unrecovered TA Detector Error 168A Channel: Recovered NPLD Error F68B Channel: Unrecovered NP
PAGE 437
F69F Channel: Unrecovered ADC Sample Not Ready Error F6A0 AE: Unrecovered Fuse Load Fail Error F6A1 AE: Unrecovered Configuration Error 16A2 Channel: Recovered Auto RST NRZ-Clock Error F6A3 Channel: Unrecovered Auto RST NRZ-Clock Error 16A4 Channel: Recovered Write CRC Fault Error F6A5 Channel: Unrecovered Write CRC Fault Error 16A6 Channel: Recovered Read Synthesizer Loss of Lock Error F6A7 Channel: Unrecovered Read Synthesizer Loss of Lock Error 16A8 Channel: Recovered RLL Parameter Err
PAGE 438
16BE Channel: Recovered MXP Write Fault F6BF Channel: Unrecovered MXP Write Fault 16C0 Channel: Recovered Data Jam Error F6C1 Channel: Unrecovered Data Jam Error 16C2 Channel: Recovered Code-Word Out Of Order Error F6C3 Channel: Unrecovered Code-Word Out Of Order Error 16C4 Channel: Recovered Read RLL Buffer CRC Flag Error F6C5 Channel: Unrecovered Read RLL Buffer CRC Flag Error 16C6 Channel: Recovered Write RLL Buffer CRC Flag Error F6C7 Channel: Unrecovered Write RLL Buffer CRC Flag Err
PAGE 439
F6DD Channel: Unrecovered Data Jam Fault Error 16DE Channel: Recovered Code-Word Out of Order Error F6DF Channel: Unrecovered Code-Word Out of Order Error 16E0 Channel: Recovered RLL Initialization Timeout Error F6E1 Channel: Unrecovered RLL Initialization Timeout Error F6E2 Channel: Unrecovered AEQ Timeout Error F6E3 Channel: Unrecovered AEQ NLD Initialization Error F6E4 Channel: Unrecovered ADC Calibration Timeout Error F6E5 Channel: Unrecovered ADC Buffer Calibration Timeout Error F6E6
PAGE 440
F6FC Channel: Unrecovered RTM Configuration Error F6FD Channel: Unrecovered RTM Failure Error F6FE Channel: Unrecovered RTM Timeout Error F701 Format corrupted F702 Too many notches D703 Media: Auto Reallocated Write Error 1704 Media: Recovered Write Error - Recommend reassign D705 Media: Error With OTF Correction - Reassigned E706 Media: Error With OTF Correction - Recommend Reassign E707 Media: Error With OTF Correction - Recommend Rewrite E708 Media: Error With OTF Correction - Rewri
PAGE 441
F715 Media: Unrecovered Sector Overflow Error 1716 Media: Recovered Write Overrun Error F717 Media: Unrecovered Write Overrun Error 171C Media: Recovered DRAM CRC Error F71D Media: Unrecovered DRAM CRC Error 171E Media: Recovered Read Latency Error F71F Media: Unrecovered Read Latency Error F720 Media: RC Dump Overflow Error F721 Media: Format Configuration Invalid 1726 Media: Recovered Internal Write Catch Error F727 Media: Unrecovered Internal Write Catch Error 172C Media: Recovered
PAGE 442
F740 Media: Defect SID Table Full Error F741 Media: OCT Timeout Not Dispatched F742 Media: OCT Timeout In Recovery F743 Media: OCT Timeout Executing 1744 Media: Recovered Sudden Stop Error F745 Media: Unrecovered Sudden Stop Error 1746 Media: Recovered Defect List Format Not Supported Error 1747 Media: Recovered Primary Defect List Not Found Error 1748 Media: Recovered Grown Defect List Not Found Error 1749 Media: Recovered Partial Defect List Transferred Error F74A Media: Unrecovered A
PAGE 443
F75F Media: Unrecovered SAT No Buffer Overflow Error F760 Media: Unrecovered SAT Buffer Overflow Error F762 Media: Unrecovered Self-Test Hard-Cache Test Fail F763 Media: Unrecovered Self-Test OTF-Cache Fail F764 Media: Unrecovered Merge G-List Failed - No P-List Exists 1766 Channel: Recovered XTS LOAD Timeout Error F767 Channel: Unrecovered XTS LOAD Timeout Error 1768 Media: Recovered Key Seed ID Mismatch Error F769 Media: Unrecovered Key Seed ID Mismatch Error 176A Media: Recovered No NR
PAGE 444
1784 Media: Recovered Channel Sector Marginal Error F785 Media: Unrecovered Channel Sector Marginal Error 1786 Media: Recovered LLI Underrun Error F787 Media: Unrecovered LLI Underrun Error 178C Media: Recovered FFSULI Timeout F78D Media: Unrecovered FFSULI Timeout F78E Media: Unrecovered SAT No Buffer Overflow With ECS Fault F78F Media: Unrecovered SAT Buffer Overflow With ECS Fault 1792 Media: Recovered MEDC Write Data Not Ready Error F793 Media: Unrecovered MEDC Write Data Not Ready er
PAGE 445
17B4 Media: Recovered Shock Sensor Error F7B5 Media: Unrecovered Shock Sensor Error 17B8 Media: Recovered Reference Tag Error F7B9 Media: Unrecovered Reference Tag error 17BA Media: Recovered Application Tag Error F7BB Media: Unrecovered Application Tag Error 17BC Media: Recovered Gaurd Check Error F7BD Media: Unrecovered Guard Check Error 17C0 Media: Recovered End Sector Check Error F7C1 Media: Unrecovered End Sector Check Error 17C2 Media: Recovered Read CRC Error F7C3 Media: Unreco
PAGE 446
F7DD Media: Unrecovered Parity EDC SRAM Error 17DE Media: Recovered REQ/ACK Handshake Error F7DF Media: Unrecovered REQ/ACK Handshake Error 17E0 Media: Recovered Write Splice Error F7E1 Media: Unrecovered Write Splice Error 17E2 Media: Recovered Read Parity Error F7E3 Media: Unrecovered Read Parity Error 17E4 Media: Recovered EPO Error F7E5 Media: Unrecovered EPO Error 17E6 Media: Recovered NRZ Sector Marginal Error F7E7 Media: Unrecovered NRZ Sector Marginal Error 17E8 Media: Recover
PAGE 447
F820 CMD: Unrecovered Parameter List Length Error F821 CMD: Unrecovered Invalid Opcode in CDB Error F822 CMD: Unrecovered LBA Out Of Range Error F823 CMD: Unrecovered Invalid Field In CDB Error F824 CMD: Unrecovered Invalid LUN Error F825 CMD: Unrecovered Invalid Field In Parameter List Error F826 CMD: Unrecovered Unsupported Log Page Error F827 CMD: Unrecovered Access Denied Error F828 CMD: Unrecovered Invalid Release of Persistent Reservation Error F829 CMD: Invalid Tx Setting for Combo
PAGE 448
3A04 SMART: Background Pre-Scan Failure (Unit Attention) 1A05 SMART: Background Media Scan Failure (No Sense) 2A05 SMART: Background Media Scan Failure (Recovered Sense) 3A05 SMART: Background Media Scan Failure (Unit Attention) 1A14 SMART: Spare Sector Availability Warning (No Sense) 2A14 SMART: Spare Sector Availability Warning (Recovered Sense) 3A14 SMART: Spare Sector Availability Warning (Unit Attention) 1A21 SMART: Milli-Actuator Error (No Sense) 2A21 SMART: Milli-Actuator Error (Reco
PAGE 449
FA81 Self-Test: Unrecoverable Error Count Threshold Exceeded 2A83 Self-Test: GLIST Error Count Threshold Reached 1A85 Self-Test: Recovery Error 2A85 Self-Test: Servo Error 4A85 Self-Test: Command Timeout Error FA85 Self-Test: Unrecoverable Error 1AFF SMART: Test Warning Threshold Reached (No Sense) 2AFF SMART: Test Warning Threshold Reached (Recovered Sense) 3AFF SMART: Test Warning Threshold Reached (Unit Attention) FCxx Media: Unrecovered Unable to Read RID or FID Number xx 1ECE Media
PAGE 450
1EE0 Media: Recovered R/W Abort Estimator Error FEE1 Media: Unrecovered R/W Abort Estimator Error 1EE2 Media: Recovered R/W Abort Predictor Error FEE3 Media: Unrecovered R/W Abort Predictor Error 1EE4 Media: Recovered R/W Abort PES Error FEE5 Media: Unrecovered R/W Abort PES Error 1EE6 Media: Recovered R/W Abort Seek Start Error FEE7 Media: Unrecovered R/W Abort Seek Start Error 1EE8 Media: Recovered R/W Abort PES Reset Error FEE9 Media: Unrecovered R/W Abort PES Reset Error 1EEA Media:
PAGE 451
FEFF Media: Unrecovered R/W Abort No STM Error FF01 IndSys: Drive Not Loaded FF02 IndSys: Drive Not Loaded - Format Invalid FF03 IndSys: Indirection System Not Online FF04 IndSys: Drive Not Loaded - Old Version Mismatch FF05 IndSys: Drive Not Loaded - Heap Pointer Mismatch FF06 IndSys: Drive Not Loaded - Heap size Mismatch FF07 IndSys: Drive Not Loaded - Rid Heap Size Mismatch FF08 IndSys: Drive Not Loaded - Heap Version Mismatch FF09 IndSys: Drive Not Loaded - Incompatible Rid FF0A Ind
PAGE 452
FF1E IndSys: Drive Loaded - Context Sequence ID Mismatch FF1F IndSys: Drive Loaded - Replay EPO Spec Failed FF20 IndSys: Drive Not Loaded - EPD Flash Entry Invalid FF21 LayoutMgr: All Flash Entries Erased 1F40 IndSys: LOM Generic Fail FF41 LayoutMgr: Format Capacity Not Met 1F42 DlMgr: DLMGR Generic Fail FF43 IndSys: Drive Not Loaded - Metadata ATI FF44 IndSys: Drive Loaded - Replay Fail FF45 IndSys: W2C Return Not Written Failed FF50 IndMgr: IM Demand Split Too Deep Failure FF51 IndM
PAGE 453
Abbreviations, 90 Active Notch, 181 Additional information, 301, 420 Additional Sense Length (Byte 7), 357 Alternate Tracks per Logical Unit, 170 Alternate Tracks per Zone, 170 Appendix, 420 Automatic Read Reallocation Enabled, 163 Automatic Rewrite/Reallocate, 314 Automatic Write Reallocation Enabled, 163 Block Descriptor, 159 block format, 96, 97 buffer overrun, 150 buffer underrun, 150 Byte ordering conventions, 90 bytes from index format, 97 Command Information Unit, 78 Command Processing During Executi
PAGE 454
REZERO UNIT (01), 252, 253 SAS Attachment, 61, 332, 353, 420 SAS OOB, 66 SAS OOB (Out of Band), 66 SAS Speed Negotiation, 67, 69 SCSI Control Byte, 90 SCSI Protocol, 301 SCSI Status Byte, 300 SCSI Status Byte Reporting, 301 Sectors per Track, 171 seek counter, 149 seeks, 150 Segmented Caching, 316 SEND DIAGNOSTIC (1D), 136, 255 sense data, 316 Sense Data, 316 Service Action, 197, 200 Size Enable, 174, 178 START STOP UNIT (1B), 262 Storage time, 38 Summary, 203 SYNCHRONIZE CACHE (35), 265 Termination of I/O
PAGE 455
© Copyright HGST, a Western Digital company HGST, a Western Digital company 3403 Yerba Buena Road San Jose, CA 95135 Produced in the United States Tel: 800-801-4618 Fax: 408-717-5000 25 February 2014 All rights reserved Ultrastar™ is a trademark of HGST. HGST trademarks are authorized for use in countries and jurisdictions in which HGST has the right to use, market and advertise the brands. HGST shall not be liable to third parties for unauthorized use of HGST trademarks.