Product Manual: Ultrastar He8 OEM Specification - SAS

HGST Japan

Hard disk drive specifications HGST Ultrastar He

HGST Hard Disk Drive Specification 1 Hard disk drive specifications. HGST Ultrastar . He. 8. 3.5 inch . Serial Attached SCSI. hard disk drive. Model: HUH728080AL5200/1/4/5

Product Manual: Ultrastar He8 OEM Specification - SAS

References in this publication to HGST-branded products, programs, or services do not imply that they will be made available in all countries.

✖
PDF product-manual-ultrastar-he8-sas 
Hard disk drive specifications
HGST Ultrastar He8

3.5 inch Serial Attached SCSI hard disk drive

Model:

HUH728080AL5200/1/4/5 HUH728080AL4200/1/4/5 HUH728060AL5200/1/4/5 HUH728060AL4200/1/4/5

Revision 1.8

20 December 2016

HGST Hard Disk Drive Specification 1

Publication Disclaimer Information
One MB is equal to one million bytes, one GB is equal to one billion bytes and one TB equals 1,000GB (one trillion bytes) when referring to storage capacity. Accessible capacity will vary from the stated capacity due to formatting and partitioning of the drive, the computer's operating system, and other factors. The following paragraph does not apply to any jurisdiction where such provisions are inconsistent with local law: THIS PUBLICATION IS PROVIDED "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. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. There may be improvements or changes in any products or programs described in this publication at any time. It is possible that this publication may contain reference to, or information about, HGST products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Western Digital Corporation intends to announce such HGST products, programming, or services in your country. Technical information about this product is available by contacting your local HGST product representative or on the Internet at: support.hgst.com. Western Digital Corporation may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. © 2016 Western Digital Corporation or its affiliates. Ultrastar and the HGST logo are registered trademarks or trademarks of Western Digital Corporation or its affiliates in the U.S. and/or other countries. Other trademarks are the property of their respective owners. References in this publication to HGST-branded products, programs, or services do not imply that they will be made available in all countries. Product specifications provided are sample specifications and do not constitute a warranty. Actual specifications for unique part numbers may vary. Please visit the Support section of our website, support.hgst.com, for additional information on product specifications. Pictures shown may vary from actual products.
HGST Hard Disk Drive Specification 2

Table of contents
Introduction ........................................................................................................................................ 18 Glossary............................................................................................................................................... 18 General caution .................................................................................................................................. 19 References ........................................................................................................................................... 19
Part 1. Functional specification ....................................................................................................................... 21
Control Electronics ............................................................................................................................. 22 Head disk assembly............................................................................................................................ 22 Actuator............................................................................................................................................... 22
Default logical drive parameters....................................................................................................... 23 Data sheet ........................................................................................................................................... 25 World Wide Name Assignment .......................................................................................................... 25 Drive organization .............................................................................................................................. 26
Drive Format .................................................................................................................................... 26 Cylinder allocation ........................................................................................................................... 26 Performance characteristics .............................................................................................................. 26 Command overhead ......................................................................................................................... 26 Mechanical positioning .................................................................................................................... 27 Drive ready time .............................................................................................................................. 27 Operating modes .............................................................................................................................. 28
Shipped format ................................................................................................................................... 29
Electrical interface ............................................................................................................................. 30 Connector location ........................................................................................................................... 30 29 pin Serial Attached SCSI (SAS) Connector Definition............................................................. 31 Voltage and Ground Signals ........................................................................................................... 32 Ready LED output ........................................................................................................................... 32
Environment ....................................................................................................................................... 33 Temperature and humidity ............................................................................................................. 33 Corrosion test ................................................................................................................................... 34 Atmospheric condition ..................................................................................................................... 34
DC power requirements ..................................................................................................................... 35 Input voltage .................................................................................................................................... 35 Power supply current (typical1) ...................................................................................................... 36 Power supply generated ripple at drive power connector ............................................................. 37 Power Consumption Efficiency ....................................................................................................... 37
Reliability............................................................................................................................................ 38 Data integrity ................................................................................................................................... 38 Cable noise interference .................................................................................................................. 38 Load/Unload ..................................................................................................................................... 38 Start/stop cycles ............................................................................................................................... 38 Preventive maintenance .................................................................................................................. 38 Data reliability ................................................................................................................................. 38
HGST Hard Disk Drive Specification 3

Required Power-Off Sequence......................................................................................................... 38 Mechanical specifications .................................................................................................................. 39
Physical dimensions......................................................................................................................... 39 Connector locations.......................................................................................................................... 41 Drive mounting ................................................................................................................................ 41 Heads unload and actuator lock ..................................................................................................... 41 Vibration and shock............................................................................................................................ 42 Operating vibration ......................................................................................................................... 42 Nonoperating vibration ................................................................................................................... 43 Operating shock ............................................................................................................................... 43 Nonoperating shock ......................................................................................................................... 43 Nonoperating Rotational shock....................................................................................................... 44 Acoustics.............................................................................................................................................. 45 Identification labels............................................................................................................................ 45 Safety................................................................................................................................................... 46 UL and CSA standard conformity................................................................................................... 46 German Safety Mark ....................................................................................................................... 46 Flammability .................................................................................................................................... 46 Safe handling.................................................................................................................................... 46 Substance restriction requirements ............................................................................................... 46 Secondary circuit protection............................................................................................................ 46 Electromagnetic compatibility........................................................................................................... 47 CE Mark ........................................................................................................................................... 47 C-Tick Mark...................................................................................................................................... 47 BSMI Mark....................................................................................................................................... 47 KC Mark ........................................................................................................................................... 47
Part 2. Interface specification .......................................................................................................................... 48
General ................................................................................................................................................ 49 SAS Features ...................................................................................................................................... 49 SAS Names and Identifiers ............................................................................................................... 51 PHY Layer .......................................................................................................................................... 53
Link Reset Sequence........................................................................................................................ 53 Hard Reset........................................................................................................................................ 53 SAS OOB (Out of Band) .................................................................................................................. 54 SAS Speed Negotiation.................................................................................................................... 54 PHY Error Handling........................................................................................................................ 55 Link Layer........................................................................................................................................... 56 Address Frames ............................................................................................................................... 56 Link Layer Error Handling ............................................................................................................. 59 Transport Layer.................................................................................................................................. 61 Command Information Unit............................................................................................................ 62 TASK Information Units ................................................................................................................. 63 XFER_RDY Information Units ....................................................................................................... 64 DATA Information Units ................................................................................................................. 64 RESPONSE Information Units ...................................................................................................... 65 Sequences of SSP Information Units.............................................................................................. 67 Transport Layer Error Handling .................................................................................................... 68
SCSI Control Byte .............................................................................................................................. 71 Abbreviations ...................................................................................................................................... 71 Byte ordering conventions ................................................................................................................. 71
HGST Hard Disk Drive Specification 4

FORMAT UNIT (04) ........................................................................................................................... 72 Parameter List Header.................................................................................................................... 74 Initialization Pattern ....................................................................................................................... 76 Defect Descriptor.............................................................................................................................. 77
INQUIRY (12) ..................................................................................................................................... 80 Inquiry Data ..................................................................................................................................... 81
LOG SELECT (4C) ............................................................................................................................. 98 LOG SENSE (4D) ............................................................................................................................. 101
Log Page Parameters..................................................................................................................... 102 Log Sense Page 0............................................................................................................................ 103 Log Sense Page 2............................................................................................................................ 104 Log Sense Page 3............................................................................................................................ 105 Log Sense Page 5............................................................................................................................ 106 Log Sense Page 6............................................................................................................................ 107 Log Sense Page D........................................................................................................................... 107 Log Sense Page E ........................................................................................................................... 108 Log Sense Page F ........................................................................................................................... 109 Log Sense Page 10...........................................................................................................................110 Log Sense Page 15...........................................................................................................................112 Log Sense Page 18...........................................................................................................................114 Log Sense Page 19h - General Statistics and Performance.........................................................118 Log Sense Page 1A ......................................................................................................................... 120 Log Sense Page 2F ......................................................................................................................... 121 Log Sense Page 30.......................................................................................................................... 122 Log Sense Page 37.......................................................................................................................... 125 MODE SELECT (15) ........................................................................................................................ 126 MODE SELECT (55) ........................................................................................................................ 127 MODE SENSE (1A).......................................................................................................................... 128 Mode Parameter List ..................................................................................................................... 130 Mode Page 00 (Vendor Unique Parameters) ................................................................................ 133 Mode Page 01 (Read/Write Error Recovery Parameters)............................................................ 135 Mode Page 02 (Disconnect/Reconnect Parameters)..................................................................... 139 Mode Page 03 (Format Device Parameters) ................................................................................ 140 Mode Page 04 (Rigid Disk Drive Geometry Parameters) ........................................................... 142 Mode Page 07 (Verify Error Recovery Parameters)..................................................................... 143 Mode Page 08 (Caching Parameters) ........................................................................................... 144 Mode Page 0A (Control Mode Page Parameters)......................................................................... 146 Mode Page 0C (Notch Parameters)............................................................................................... 150 Mode Page 18h ............................................................................................................................... 151 Mode Page 19h (Port Control Parameters) .................................................................................. 152 Mode Page 1A (Power Control) ..................................................................................................... 158 Mode Page 1C (Informational Exceptions Control) ..................................................................... 161 MODE SENSE (5A).......................................................................................................................... 164 PERSISTENT RESERVE IN (5E)................................................................................................... 165 Service Action ................................................................................................................................. 165 Parameter data for Read Keys...................................................................................................... 166 Parameter Data for Read Reservations ....................................................................................... 167 PERSISTENT RESERVE OUT (5F) ............................................................................................... 168 Service Action ................................................................................................................................. 168 Type................................................................................................................................................. 169 Parameter list ................................................................................................................................ 170 Summary ........................................................................................................................................ 171 PRE-FETCH (34).............................................................................................................................. 172 PRE-FETCH (90).............................................................................................................................. 173
HGST Hard Disk Drive Specification 5

READ (6) - (08) ................................................................................................................................. 174 READ (10) - (28) ............................................................................................................................... 175 READ (12) - (A8) ............................................................................................................................... 177 READ (16) - (88) ............................................................................................................................... 178 READ (32) - (7F/09) .......................................................................................................................... 179 READ BUFFER (3C) ........................................................................................................................ 180
Combined Header And Data (Mode 00000b)................................................................................ 180 Read Data (Mode 00010b) ............................................................................................................. 181 Descriptor (Mode 00011b).............................................................................................................. 181 Read Data from Echo Buffer (Mode 01010b) ............................................................................... 181 Echo Buffer Descriptor (Mode 01011b)......................................................................................... 182 Expander Communications and Echo Buffer (Mode 11010b) ..................................................... 182 Error History (Mode 11100b)......................................................................................................... 182 READ CAPACITY (10) - (25) ........................................................................................................... 184 Returned Data Format .................................................................................................................. 184 READ CAPACITY (16) (9E/10)........................................................................................................ 185 Returned Data Format .................................................................................................................. 185 READ DEFECT DATA (37).............................................................................................................. 186 Defect List Header ......................................................................................................................... 187 Defect List Descriptor.................................................................................................................... 187 Bytes from Index Format (100b)................................................................................................... 187 Physical Sector Format (101b) ...................................................................................................... 187 READ DEFECT DATA (B7) ............................................................................................................. 189 Defect List Header ......................................................................................................................... 189 Defect List Descriptor.................................................................................................................... 189 Bytes from Index Format (100b)................................................................................................... 190 Physical Sector Format (101b) ...................................................................................................... 190 READ LONG (3E) ............................................................................................................................ 191 READ LONG (9E) ............................................................................................................................ 192 REASSIGN BLOCKS (07) ............................................................................................................... 193 RECEIVE DIAGNOSTICS RESULTS (1C).................................................................................... 194 Receive Diagnostic Results Page 0 ............................................................................................... 194 Receive Diagnostic Results Page 40 ............................................................................................. 195 LEASE (17) ....................................................................................................................................... 196 RELEASE (57) .................................................................................................................................. 197 REPORT DEVICE IDENTIFIER (A3/05)....................................................................................... 198 REPORT LUNS (A0) ........................................................................................................................ 199 REPORT SUPPORTED OPERATION CODES (A3/0C)................................................................ 200 All_commands parameter data format......................................................................................... 202 One_command parameter data format ........................................................................................ 203 Command timeouts descriptor format.......................................................................................... 204 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D)..................................... 205 REPORT TIMESTAMP (A3/0F) ...................................................................................................... 207 Device clocks and timestamps....................................................................................................... 208 REQUEST SENSE (03).................................................................................................................... 209 RESERVE (16) .................................................................................................................................. 210 RESERVE (56) ...................................................................................................................................211 REZERO UNIT (01) ......................................................................................................................... 212 SANITIZE (48).................................................................................................................................. 213 Sanitize (48) Service Action Codes................................................................................................ 214 SECURITY PROTOCOL IN (A2) .................................................................................................... 215 SECURITY PROTOCOL OUT (B5) ................................................................................................ 216 SEND DIAGNOSTIC (1D) ............................................................................................................... 217 Send Diagnostic Page 0 ................................................................................................................. 218
HGST Hard Disk Drive Specification 6

Send Diagnostic Page 3F ............................................................................................................... 218 Send Diagnostic Page 40 ............................................................................................................... 220 SET DEVICE IDENTIFIER (A4/06) ............................................................................................... 221 SET TIMESTAMP (A4/0F) .............................................................................................................. 222 START STOP UNIT (1B) ................................................................................................................. 223 SYNCHRONIZE CACHE (10) - (35) ............................................................................................... 225 SYNCHRONIZE CACHE (16) - (91) ............................................................................................... 226 TEST UNIT READY (00) ................................................................................................................. 227 VERIFY (10) - (2F) ........................................................................................................................... 228 VERIFY (12) - (AF)........................................................................................................................... 230 VERIFY (16) - (8F) ........................................................................................................................... 231 VERIFY (32) - (7F/0A)...................................................................................................................... 232 WRITE (6) - (0A) ............................................................................................................................... 233 WRITE (10) - (2A)............................................................................................................................. 234 WRITE (12) - (AA) ............................................................................................................................ 236 WRITE (16) - (8A)............................................................................................................................. 237 WRITE (32) - (7F/0B) ....................................................................................................................... 238 WRITE AND VERIFY (10) - (2E) .................................................................................................... 239 WRITE AND VERIFY (12) - (AE).................................................................................................... 240 WRITE AND VERIFY (16) - (8E) .................................................................................................... 241 WRITE AND VERIFY (32) - (7F/0C)............................................................................................... 242 WRITE BUFFER (3B)...................................................................................................................... 243 Combined Header And Data (Mode 00000b)................................................................................ 243 Write Data (Mode 00010b) ............................................................................................................ 244 Download Microcode (Mode 00100b) ............................................................................................ 244 Download Microcode and Save (Mode 00101b) -Single Binary File........................................... 245 Download Microcode and Save (Mode 00111b) - Multiple Binary Files..................................... 245 Write Data to Echo Buffer (Mode 01010b) ................................................................................... 245 Download Microcode with Offsets, Select Activation Events, Save, and Defer Activate (Mode 01101b)............................................................................................................................................ 246 Download Microcode with Offsets, Save, and Defer Activate (Mode 01110b) ........................... 246 Activate Deferred Microcode Mode (Mode 01111b)...................................................................... 246 Enable Expander Communications Protocol (Mode 11010b)...................................................... 246 WRITE LONG (10) (3F)................................................................................................................. 247 WRITE LONG (16) - (9F) ................................................................................................................. 248 WRITE SAME (10) - (41) ................................................................................................................. 249 WRITE SAME (16) - (93) ................................................................................................................. 250 WRITE SAME (32) - (7F/0D) ........................................................................................................... 251
SCSI Protocol .................................................................................................................................... 253 Priority of SCSI Status Byte Reporting ....................................................................................... 253 Invalid LUN Processing ................................................................................................................ 253 Overlapped Commands ................................................................................................................. 254 Command Processing During Execution of Active I/O Process .................................................. 254 Unit Attention Condition............................................................................................................... 255 Command Processing During Startup and Format Operations ................................................. 256 Internal Error Condition ............................................................................................................... 256 Deferred Error Condition .............................................................................................................. 257 Degraded Mode .............................................................................................................................. 257 Command Processing while Reserved .......................................................................................... 260
Priority Commands .......................................................................................................................... 261 Command Queuing........................................................................................................................... 261
HGST Hard Disk Drive Specification 7

Queue Depth................................................................................................................................... 261 Queue Full Status .......................................................................................................................... 261 Termination of I/O Processes......................................................................................................... 261 Command Reordering ...................................................................................................................... 262 Concurrent I/O Process .................................................................................................................... 262 Write Cache....................................................................................................................................... 262 Automatic Rewrite/Reallocate ......................................................................................................... 263 Segmented Caching .......................................................................................................................... 264 Overview ......................................................................................................................................... 264 Read Ahead..................................................................................................................................... 264 Multiple Initiator Systems............................................................................................................... 264 Sense Data...................................................................................................................................... 264 Mode Pages..................................................................................................................................... 264 Multiple Initiator Environment ...................................................................................................... 264 Initiator Sense Data ...................................................................................................................... 264 Initiator Mode Select/Mode Sense Parameters............................................................................ 264 Reset .................................................................................................................................................. 265 Initiator Sense Data ...................................................................................................................... 265 Reset Actions .................................................................................................................................. 265 Diagnostics........................................................................................................................................ 266 Power on Diagnostics..................................................................................................................... 266 Self-test via SEND DIAGNOSTIC Command ............................................................................. 266 Idle Time Function ........................................................................................................................... 269 Command Time out Limits .............................................................................................................. 269 Reassignment Time ....................................................................................................................... 269 Format Time................................................................................................................................... 269 Start/Stop Unit Time ..................................................................................................................... 269 Medium Access Command Time ................................................................................................... 269 Time-out Limits for Other Commands ......................................................................................... 270 Recommended Initiator ERP ........................................................................................................... 271 Drive Service Strategy................................................................................................................... 271 Recommendations for System Error Log ..................................................................................... 271 Data Recovery Procedure .............................................................................................................. 272 Non data Error Recovery Procedure............................................................................................. 273 RAID Rebuild Assist......................................................................................................................... 279 Rebuild Assist diagnostic page...................................................................................................... 279
Referenced Specifications and Standards....................................................................................... 281 TCG Specifications......................................................................................................................... 281 Federal Information Processing Standards (FIPS) ..................................................................... 281 National Institute of Standards and Technology (NIST) ............................................................ 281 Department of Defense .................................................................................................................. 282 RSA Laboratories Standards......................................................................................................... 282 Other Standards............................................................................................................................. 282
Implementation Exceptions............................................................................................................. 282 Implementation Features and Details Outside of TCG Specifications ........................................ 282 Encryption Algorithms ..................................................................................................................... 283
Advanced Encryption Standard (AES) Support .......................................................................... 283 `Level 0 Discovery' Vendor Specific Data...................................................................................... 283 Deterministic Random Bit Generation (DRBG) .......................................................................... 284 Key Wrap ........................................................................................................................................ 284 Key Erasure.................................................................................................................................... 284 TCG SSC Tables ............................................................................................................................... 285 `Admin SP' C_PIN and `Locking SP' C_PIN Tables ..................................................................... 285
HGST Hard Disk Drive Specification 8

K_AES_256 Table........................................................................................................................... 285 `Locking SP' Access Control Table................................................................................................. 286 `Locking Info' Table ........................................................................................................................ 286 `Locking SP' Locking Table ............................................................................................................ 286 Firmware Download and Signing.................................................................................................... 287 Revert Feature.................................................................................................................................. 287 Ports .................................................................................................................................................. 288 MSID ................................................................................................................................................. 291 Logging .............................................................................................................................................. 291 Number of Sessions .......................................................................................................................... 291 Number of Bands.............................................................................................................................. 291 Number of COMIDs.......................................................................................................................... 291 Locked and Unlocked Behavior ....................................................................................................... 292 T10 SCSI Commands..................................................................................................................... 292 TCG SSC Commands ..................................................................................................................... 294 Error Codes ....................................................................................................................................... 296 Customer Specific Requirements .................................................................................................... 296 FIPS140 Cryptographic Officer Instructions ................................................................................. 297 Physical Security............................................................................................................................ 297 Security Protocol Parameters ....................................................................................................... 297 Certified Models, Hardware Versions and Firmware Versions .................................................. 302 Cryptographic Module Acceptance and Provisioning .................................................................. 302 Zeroization of the Cryptographic Module..................................................................................... 302
SCSI Sense Data Format Introduction........................................................................................... 303 Sense Data Format ........................................................................................................................ 303 Sense Data Length......................................................................................................................... 303 Sense Data Response Code............................................................................................................ 303
Fixed Format Sense Data ................................................................................................................ 304 Valid (Bit 7 of byte 0) ..................................................................................................................... 304 Response Code (Bit 6 - 0 of byte 0) ............................................................................................... 304 ILI: Incorrect Length Indicator (Bit 5 of byte 2).......................................................................... 305 Sense Key (Bit 3 - 0 of byte 2) ....................................................................................................... 305 Information Bytes (Byte 3 through 6) .......................................................................................... 306 Additional Sense Length (Byte 7) ................................................................................................. 306 Command Specific Information (Byte 8 through 11)................................................................... 306 Additional Sense Code/Qualifier (Byte 12 and 13) ...................................................................... 307 FRU: Field Replaceable Unit (Byte 14) ........................................................................................ 330 Sense Key Specific (Byte 15 through 17)...................................................................................... 330 Reserved (Byte 18 through 19)...................................................................................................... 332 Vendor unique error information (Byte 20 through 23) .............................................................. 332 Physical Error Record (Product Specific Information) (Byte 24 through 29) ............................ 332
Descriptor Format Sense Data ........................................................................................................ 333 Order of Sense Descriptors............................................................................................................ 334 Sense Data Descriptor Definitions ............................................................................................... 335
HGST Hard Disk Drive Specification 9

List of tables
Table 1 Type and Model# ............................................................................................................................... 18 Table 2 Formatted capacity ........................................................................................................................... 24 Table 3 Mechanical positioning performance (Sector format of 4k bytes/sector) ...................................... 25 Table 4 World Wide Name Assignment ........................................................................................................ 25 Table 5 Command overhead .......................................................................................................................... 26 Table 6 Average seek time ............................................................................................................................. 27 Table 7 Single Track Seek Time .................................................................................................................... 27 Table 8 Latency Time ..................................................................................................................................... 27 Table 9 Drive ready time................................................................................................................................ 27 Table 10 Mode transition times ..................................................................................................................... 28 Table 11 29-pin Connector Signal Definition................................................................................................ 31 Table 12 Temperature and humidity ............................................................................................................ 33 Table 13 Input voltage.................................................................................................................................... 35 Table 14 SAS power consumption ................................................................................................................. 36 Table 15 Power supply generated ripple at drive power connector ............................................................ 37 Table 16 Power consumption efficiency ........................................................................................................ 37 Table 17 Physical Dimensions ....................................................................................................................... 40 Table 18 Random vibration PSD profile break points (operating).............................................................. 42 Table 19 Random vibration (Rotational) PSD profile break points ............................................................ 42 Table 20 Random vibration PSD profile break points (nonoperating) ....................................................... 43 Table 21 Sinusoidal shock wave .................................................................................................................... 43 Table 22 Rotational Shock ............................................................................................................................. 44 Table 23 Sound power levels.......................................................................................................................... 45 Table 24 Names and Identifiers .................................................................................................................... 51 Table 25 SAS Address Format ....................................................................................................................... 51 Table 26 IEEE Registered Name Format ..................................................................................................... 51 Table 27 Name Address Authority field ........................................................................................................ 52 Table 28 SAS Speed Negotiation ................................................................................................................... 54 Table 29 Supported Settings Bit Priorities................................................................................................... 55 Table 30 PHY Layer Error Handling ............................................................................................................ 55 Table 31 Address Frame Format ................................................................................................................... 56 Table 32 Frame Type: ..................................................................................................................................... 56 Table 33 Identify Address Frame .................................................................................................................. 57 Table 34 Reason Field .................................................................................................................................... 58 Table 35 Open Address Frame Format ......................................................................................................... 58 Table 36 Link Layer Error Handling (part 1 of 2) ....................................................................................... 59 Table 37 Link Layer Error Handling (part 2 of 2) ....................................................................................... 60 Table 38 SAS Frame Format ......................................................................................................................... 61 Table 39 FRAME TYPE Field........................................................................................................................ 61 Table 40 COMMAND Information Unit ....................................................................................................... 62 Table 41 Task Attribute Field ........................................................................................................................ 62 Table 42 TASK Information Unit .................................................................................................................. 63 Table 43 TASK MANAGEMENT FUNCTION Field ................................................................................... 63 Table 44 Additional Response Information Argument for Query Async Event ......................................... 64 Table 45 UADE DEPTH Field ....................................................................................................................... 64 Table 46 XFER_RDY Information Units ...................................................................................................... 64 Table 47 Data Information Unit .................................................................................................................... 64 Table 48 Response Information Unit ............................................................................................................ 65 Table 49 RETRY DELAY TIMER Field (part 1 of 2).................................................................................... 65 Table 50 RETRY DELAY TIMER Field (part 2 of 2).................................................................................... 65 Table 51 DATAPRES Field ............................................................................................................................ 66
HGST Hard Disk Drive Specification 10

Table 52 RESPONSE Data ............................................................................................................................ 66 Table 53 RESPONSE Codes .......................................................................................................................... 66 Table 54 Transport Layer Error Handling ................................................................................................... 68 Table 55 SCSI Commands Supported (part 1 of 2) ...................................................................................... 69 Table 56 SCSI Commands Supported (part 2 of 2) ...................................................................................... 70 Table 57 SCSI Control Byte ........................................................................................................................... 71 Table 58 FORMAT UNIT ............................................................................................................................... 72 Table 59 Format of the Short Parameter List Header ................................................................................ 74 Table 60 Format of the Long Parameter List Header ................................................................................. 74 Table 61 Format of the Long Parameter List Header ................................................................................. 74 Table 62 Data Format with Protection field ................................................................................................. 75 Table 63 Initialization Pattern Descriptor ................................................................................................... 76 Table 64 Defect Descriptor - Block Format (for n + 1 defects) .................................................................... 77 Table 65 Defect Descriptor - Bytes from Index Format (for n = 1 defects)................................................. 78 Table 66 Defect Descriptor - Physical Sector Format (for n + 1 defects).................................................... 78 Table 67 INQUIRY (12) .................................................................................................................................. 80 Table 68 Page Code descriptions ................................................................................................................... 80 Table 69 Inquiry Data- EVPD = 0 ................................................................................................................. 81 Table 70 Inquiry Data - EVPD = 1 (Page Code = 00h) ................................................................................ 83 Table 71 Inquiry Data - EVPD = 1 (Page Code = 03h) ................................................................................ 84 Table 72 Inquiry Data - EVPD = 1 (Page Code = 80h) ................................................................................ 85 Table 73 Inquiry Data Format - EVPD = 1, (Page Code - 83h) ................................................................... 86 Table 74 Inquiry Data Format - EVPD = 1, (Page Code - 86h) ................................................................... 88 Table 75 Inquiry Data Format - EVPD = 1, (Page Code - 87h) ................................................................... 89 Table 76 Inquiry Data Format - EVPD = 1, (Page Code - 88h) ................................................................... 90 Table 77 Inquiry Data Format - EVPD = 1, (Page Code - 8Ah) .................................................................. 91 Table 78 Inquiry Data - EVPD = 1 (Page Code = 90h) ................................................................................ 92 Table 79 Protocol-specific logical unit information descriptor .................................................................... 92 Table 80 Protocol Specific Port Information VPD page to SAS SSP........................................................... 93 Table 81 Port Information Descriptor for SAS SSP ..................................................................................... 93 Table 82 SAS PHY Information Descriptor for SAS SSP ............................................................................ 93 Table 83 Inquiry Data - EVPD = 1 (Page Code = B0h) ................................................................................ 94 Table 84 Inquiry Data - EVPD = 1 (Page Code = B1h) ................................................................................ 95 Table 85 Inquiry Data - EVPD = 1 (Page Code = B2h) ................................................................................ 96 Table 86 Inquiry Data - EVPD = 1 (Page Code = D1h)................................................................................ 96 Table 87 Inquiry Data - EVPD = 1 (Page Code = D2h)................................................................................ 97 Table 88 Log Select (4C)................................................................................................................................. 98 Table 89 Log Sense (4D)............................................................................................................................... 101 Table 90 Log Sense Page 0 ........................................................................................................................... 103 Table 91 Log Sense Page 2 ........................................................................................................................... 104 Table 92 Log Sense Page 3 ........................................................................................................................... 105 Table 93 Log Sense Page 5 ........................................................................................................................... 106 Table 94 Log Sense Page 6 ........................................................................................................................... 107 Table 95 Log Sense Page D .......................................................................................................................... 107 Table 96 Log Sense Page E .......................................................................................................................... 108 Table 97 Log Sense Page F .......................................................................................................................... 109 Table 98 Log Sense Page F, Application Client Log ................................................................................... 109 Table 99 Log Sense Page 10..........................................................................................................................110 Table 100 Log Sense Page 10, self-test results............................................................................................110 Table 101 Log Sense Page 10, self-test results............................................................................................111 Table 102 Log Sense Page 10, Extended Segment Number ....................................................................... 111 Table 103 Log Sense Page 15........................................................................................................................112 Table 104 BMS Status Parameter structure ...............................................................................................112 Table 105 BMS Status...................................................................................................................................112
HGST Hard Disk Drive Specification 11

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 Table 156 Table 157 Table 158 Table 159

Medium Scan Parameter structure ............................................................................................113 Reassign Status............................................................................................................................113 Log Sense Page 18........................................................................................................................114 SAS Log Descriptor (part 1 of 3) .................................................................................................114 SAS Log Descriptor (part 2 of 3) .................................................................................................115 SAS Log Descriptor (part 3 of 3)..................................................................................................116 Log Sense Page 19h - General Statistics and Performance ......................................................118 Time Interval Descriptor .............................................................................................................119 Log Sense Page 1A ...................................................................................................................... 120 Log Sense Page 2F....................................................................................................................... 121 Log Sense Page 30 ....................................................................................................................... 122 Log Sense Page 37 ....................................................................................................................... 125 Mode Select (15)........................................................................................................................... 126 Mode Select (55)........................................................................................................................... 127 Mode Sense (1A) .......................................................................................................................... 128 Page Code Usage ......................................................................................................................... 129 Mode parameter header (6) ........................................................................................................ 130 Mode parameter header (10) ...................................................................................................... 130 Short LBA Mode Parameter Block Descriptor .......................................................................... 131 Long LBA Mode Parameter Block Descriptor ........................................................................... 131 Mode Parameter Page Format ................................................................................................... 132 Mode Parameter Page Format ................................................................................................... 132 Vendor Unique Parameters - Page 00........................................................................................ 133 Mode Page 01 (Vendor Unique Parameters) ............................................................................. 135 Mode Page 02 (Disconnect/Reconnect Parameters) .................................................................. 139 Mode Page 03 (Format Device Parameters).............................................................................. 140 Mode Page 04 (Rigid Disk Drive Geometry Parameters)......................................................... 142 Mode Page 07 (Verify Error Recovery Parameters) .................................................................. 143 Page 08 (Caching Parameters) ................................................................................................... 144 Page 0A (Control Mode Page Parameters) ................................................................................ 146 Control Extension Subpage ........................................................................................................ 148 Application Tag mode page:........................................................................................................ 149 Application Tag descriptor format ............................................................................................. 149 Page 0C (Notch Parameters) ...................................................................................................... 150 Page 18h (Protocol-Specific Logical Unit mode page) .............................................................. 151 Short (Port Control Parameters) Short Format........................................................................ 152 Long Format of Port Control Page............................................................................................. 153 PHY Control and Discover (Subpage 1)..................................................................................... 154 SAS PHY Mode Descriptor ......................................................................................................... 155 Shared Port Control (Subpage 2) ............................................................................................... 157 Subpage 3..................................................................................................................................... 157 PHY Mode Descriptor (0 and 1) ................................................................................................. 158 Page 1A (Power Control)............................................................................................................. 158 PM_BG_PRECEDENCE field .................................................................................................... 160 Page 1C (Informational Exceptions Control) ............................................................................ 161 Background Control (Subpage 01h) ........................................................................................... 163 Mode Sense (5A) .......................................................................................................................... 164 Persistent Reserve In (5E).......................................................................................................... 165 PERSISTENT RESERVE IN, Service Action Codes ................................................................ 165 PERSISTENT RESERVE IN, parameter data for Read Keys................................................. 166 PERSISTENT RESERVE IN, parameter data for Read Reservations ................................... 167 PERSISTENT RESERVE IN, Read Reservation Descriptor ................................................... 167 PERSISTENT RESERVE OUT (5F).......................................................................................... 168 PERSISTENT RESERVE OUT, Service Action Code............................................................... 168

HGST Hard Disk Drive Specification 12

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 Table 210 Table 211 Table 212 Table 213

PERSISTENT RESERVE OUT, Type Code .............................................................................. 169 Parameter List ............................................................................................................................ 170 PERSISTENT RESERVE OUT, Service Action, Parameters .................................................. 171 APTPL and information held by a drive.................................................................................... 171 PRE-FETCH (34)......................................................................................................................... 172 PRE-FETCH (90)......................................................................................................................... 173 READ (6) - (08) ............................................................................................................................ 174 READ (10) - (28) .......................................................................................................................... 175 READ (12) - (A8).......................................................................................................................... 177 READ (16) - (88) .......................................................................................................................... 178 READ (32) - (7F/09)..................................................................................................................... 179 READ BUFFER (3C)................................................................................................................... 180 Read Buffer Header .................................................................................................................... 180 Read Buffer Description ............................................................................................................. 181 Echo Buffer Descriptor ............................................................................................................... 182 Error History Buffer ID Field .................................................................................................... 182 Error History Directory .............................................................................................................. 183 Error History Directory Entry ................................................................................................... 183 READ CAPACITY (10) - (25) ...................................................................................................... 184 Format of READ CAPACITY command reply........................................................................... 184 Read Capacity (16) (9E/10) ......................................................................................................... 185 Returned Data Format ............................................................................................................... 185 Protection Type (P_TYPE) field ................................................................................................. 185 Logical Blocks per Physical Block Exponent field .................................................................... 185 READ DEFECT DATA (37) ........................................................................................................ 186 Defect List Format ...................................................................................................................... 186 Defect List Header ...................................................................................................................... 187 Defect List Descriptor ................................................................................................................. 187 Defect Descriptors of Bytes from Index Format ....................................................................... 187 Defect Descriptors of Physical Sector Format........................................................................... 187 READ DEFECT DATA (B7)........................................................................................................ 189 Unit Defect List Header ............................................................................................................. 189 Defect List Descriptor ................................................................................................................. 189 Defect Descriptors of Bytes from Index Format ....................................................................... 190 Defect Descriptors of Physical Sector Format........................................................................... 190 READ LONG (3E) ....................................................................................................................... 191 READ LONG (9E) ....................................................................................................................... 192 REASSIGN BLOCKS (07) .......................................................................................................... 193 Format of Reassign Blocks Parameter List data ...................................................................... 193 RECEIVE DIAGNOSTIC RESULTS (1C)................................................................................. 194 Receive Diagnostic Results page 0 ............................................................................................. 194 Receive Diagnostic Results page 40........................................................................................... 195 Translated address ...................................................................................................................... 195 RELEASE (17)............................................................................................................................. 196 RELEASE (57)............................................................................................................................. 197 REPORT DEVICE IDENTIFIER (A3/05) ................................................................................. 198 Report Device Identifier parameter list .................................................................................... 198 REPORT LUNS (A0)................................................................................................................... 199 LUN Reporting parameter list format....................................................................................... 199 REPORT SUPPORTED OPERATION CODES (A3/0C) .......................................................... 200 Reporting Options ....................................................................................................................... 201 All_command parameter data format........................................................................................ 202 Command Descriptor format...................................................................................................... 202 One_command parameter data format...................................................................................... 203

HGST Hard Disk Drive Specification 13

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 Table 264 Table 265 Table 266 Table 267

One_command parameter support field .................................................................................... 203 Command timeouts descriptor format....................................................................................... 204 Command timeouts descriptor Command Specific Field usage .............................................. 204 Report Supported Task Management Functions (A3/0D) ........................................................ 205 Report Supported Task Management Functions - returned parameter data......................... 205 REPORT TIMESTAMP (A3/0F) ................................................................................................. 207 REPORT TIMESTAMP return parameter data ....................................................................... 207 Timestamp Origin value ............................................................................................................. 208 REQUEST SENSE (03) .............................................................................................................. 209 Sense Data Format and Length ................................................................................................. 209 RESERVE (16)............................................................................................................................. 210 RESERVE (56)..............................................................................................................................211 REZERO UNIT (01) .................................................................................................................... 212 SANITIZE (48) ............................................................................................................................ 213 SANITIZE Service Action Codes ................................................................................................ 214 Parameter List Format for Overwrite Service Action .............................................................. 214 SECURITY PROTOCOL IN (A2) ............................................................................................... 215 SECURITY PROTOCOL field in SECURITY PROTOCOL IN command .............................. 215 SECURITY PROTOCOL OUT (B5) ........................................................................................... 216 SECURITY PROTOCOL field in SECURITY PROTOCOL OUT command .......................... 216 SEND DIAGNOSTIC (1D).......................................................................................................... 217 SEND DIAGNOSTIC Function Code (1D) ................................................................................ 217 Diagnostic page 0 ........................................................................................................................ 218 Diagnostic page 3F ...................................................................................................................... 218 Phy Test Function ....................................................................................................................... 218 Phy Test Pattern ......................................................................................................................... 219 Phy Test Pattern SSC Code ........................................................................................................ 219 Phy Test Pattern Dwords Control .............................................................................................. 219 Diagnostic Page 40 ...................................................................................................................... 220 Address to translate .................................................................................................................... 220 SET DEVICE IDENTIFIER (A4/06).......................................................................................... 221 SET DEVICE IDENTIFIER, Parameter List ........................................................................... 221 SET TIMESTAMP (A4/0F) ......................................................................................................... 222 SET TIMESTAMP parameter list.............................................................................................. 222 START STOP UNIT (1B) ............................................................................................................ 223 Power Conditions ........................................................................................................................ 223 SYNCHRONIZE CACHE (10) - (35) .......................................................................................... 225 Synchronize Cache (16) - (91) ..................................................................................................... 226 TEST UNIT READY (00)............................................................................................................ 227 VERIFY (10) - (2F) ...................................................................................................................... 228 Byte Check ................................................................................................................................... 228 VERIFY (12) - (AF) ..................................................................................................................... 230 VERIFY (16) - (8F) ...................................................................................................................... 231 VERIFY (32) - 7F/0A).................................................................................................................. 232 WRITE (6) - (0A).......................................................................................................................... 233 WRITE (10) - (2A)........................................................................................................................ 234 WRITE (12) - (AA) ....................................................................................................................... 236 WRITE (16) - (8A)........................................................................................................................ 237 WRITE (32) - (7F/0B) .................................................................................................................. 238 WRITE AND VERIFY (10) - (2E) ............................................................................................... 239 Byte Check ................................................................................................................................... 239 WRITE and VERIFY (12) - (AE) ................................................................................................ 240 WRITE and VERIFY (16) - (8E)................................................................................................. 241 WRITE and VERIFY (32) - (7F/0C) ........................................................................................... 242

HGST Hard Disk Drive Specification 14

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 Table 318 Table 319 Table 320 Table 321

WRITE BUFFER (3B)................................................................................................................. 243 Write Buffer Header.................................................................................................................... 243 Mode Specific Field ..................................................................................................................... 246 WRITE LONG (3F) ..................................................................................................................... 247 WRITE LONG (9F) ..................................................................................................................... 248 WRITE SAME (41) ...................................................................................................................... 249 WRITE SAME (16) - (93) ............................................................................................................ 250 WRITE SAME (32) - (7F/0D) ...................................................................................................... 251 SCSI Status Byte. Format of the SCSI STATUS byte.............................................................. 252 Spindle Motor Degraded Mode - Disable Auto Start ................................................................ 257 Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up............................................. 258 Spindle Motor Degraded Mode - Spindle Start Failure ........................................................... 258 Spindle Motor Degraded Mode - Spindle Stopped by Command............................................. 259 Self Configuration Failure Degraded Mode .............................................................................. 259 Format Command Failure Degraded Mode .............................................................................. 260 Sense data combinations with auto/recommend rewrite/reallocate ........................................ 263 Short and Extended Self-Test Description ................................................................................ 268 Log Only Errors........................................................................................................................... 272 Rebuild Assist input diagnostic page......................................................................................... 279 Rebuild Assist output diagnostic page....................................................................................... 280 Persistent Reserve In (5E).......................................................................................................... 283 HGST Default Values for `Admin SP' C_PIN & `Locking SP' C_PIN ...................................... 285 HGST Implementation of K_AES_256 Table ............................................................................ 285 HGST Implementation of `Locking SP' Access Control Table .................................................. 286 HGST Implementation of `Locking Info' Table.......................................................................... 286 HGST Implementation of `Locking SP' Locking Table ............................................................. 286 PSID Authority Added to `Admin SP' Authority Table ............................................................. 287 PSID Addition to `Admin SP' C_PIN table ................................................................................ 287 Additions to `Admin SP' Access Control Table .......................................................................... 288 Ports Functionality ..................................................................................................................... 288 Ports Table ................................................................................................................................... 288 Modified `Admin SP' ACE Table ................................................................................................. 289 Modified `Admin SP' Access Control Table (part 1 of 2) ........................................................... 289 Modified `Admin SP' Access Control Table (part 2 of 2) ........................................................... 290 T10 SCSI Commands Behavior Table (part 1 of 2)................................................................... 292 T10 SCSI Commands Behavior Table (part 2 of 2)................................................................... 293 TCG Enterprise SSC Commands Behavior -1 .......................................................................... 294 TCG Enterprise SSC Commands Behavior -2 .......................................................................... 294 TCG Enterprise SSC Commands Behavior -3 .......................................................................... 294 TCG Enterprise SSC Commands Behavior -4 .......................................................................... 295 TCG Enterprise SSC Commands Behavior -5 .......................................................................... 295 SECURITY PROTOCOL SPECIFIC Field for SECURITY PROTOCOL IN Protocol 00h .... 297 Supported Security Protocols SECURITY PROTOCOL IN Parameter Data ............................... 298 Certificate Data SECURITY PROTOCOL IN Parameter Data ..................................................... 298 Security Compliance Information SECURITY PROTOCOL IN Parameter Data ................. 299 Compliance Descriptor Format .................................................................................................. 300 COMPLIANCE DESCRIPTOR TYPE Field ............................................................................. 300 FIPS 140 Compliance Descriptor ............................................................................................... 301 RELATED STANDARD Field .................................................................................................... 301 Sense data response codes .......................................................................................................... 303 Fixed Format Sense Data ........................................................................................................... 304 Incorrect Length Indicator ......................................................................................................... 305 Information Bytes (Byte 3 through 6) ....................................................................................... 306 Sense Code/Qualifier................................................................................................................... 307

HGST Hard Disk Drive Specification 15

Table 322 Table 323 Table 324 Table 325 Table 326 Table 327 Table 328 Table 329 Table 330 Table 331 Table 332 Table 333 Table 334 Table 335 Table 336 Table 337 Table 338

Field Pointer Bytes ..................................................................................................................... 330 Actual Retry Count ..................................................................................................................... 331 Recovery Type.............................................................................................................................. 331 Progress Indication ..................................................................................................................... 332 Log Only Errors........................................................................................................................... 332 Descriptor Format Sense Data................................................................................................... 333 Sense Data Descriptor Format................................................................................................... 333 Supported Descriptor Types ....................................................................................................... 333 Sense Data Descriptor List......................................................................................................... 334 Information Sense Data Descriptor Format ............................................................................. 335 Command-specific Sense Data Descriptor Format................................................................... 336 Information Sense Data Descriptor Format ............................................................................. 336 Field Replaceable Unit Sense Data Descriptor Format ........................................................... 337 Block Command Sense Data Descriptor Format ...................................................................... 337 Vendor Unique Unit Error Code Sense Data Descriptor ......................................................... 338 Vendor Unique Physical Error Record Sense Data Descriptor................................................ 338 Unit Error Codes ......................................................................................................................... 339

HGST Hard Disk Drive Specification 16

List of figures
Figure 1 PList physical format ...................................................................................................................... 29 Figure 2 Connector location ........................................................................................................................... 30 Figure 3 SAS Connector ................................................................................................................................. 31 Figure 4 Limits of temperature and altitude ............................................................................................... 33 Figure 5 Limits of temperature and humidity ............................................................................................. 34 Figure 6 Top and side views and mechanical dimensions ........................................................................... 39 Figure 7 Bottom and side views with mounting hole locations .................................................................. 40 Figure 8 Connector locations ......................................................................................................................... 41 Figure 9 Link Reset Sequence ....................................................................................................................... 53 Figure 10 SSP Information Unit Sequences................................................................................................. 67
HGST Hard Disk Drive Specification 17

General

Introduction
This document describes the specifications of the Ultrastar He8 an HGST 3.5-inch 7200-rpm Serial Attached SCSI interface hard disk drive with the following model numbers:

Capacity Type

Interface Format

512e
8TB US7SSJ800
4Kn Serial Attached
SCSI 512e
6TB US7SSJ600
4Kn

Table 1 Type and Model#

Model#
HUH728080AL5200 HUH728080AL5201 HUH728080AL5204 HUH728080AL5205 HUH728080AL4200 HUH728080AL4201 HUH728080AL4204 HUH728080AL4205 HUH728060AL5200 HUH728060AL5201 HUH728060AL5204 HUH728060AL5205 HUH728060AL4200 HUH728060AL4201 HUH728060AL4204 HUH728060AL4205

Description
Instant Secure Erase TCG(Trusted Computing Group) Secure Erase (Overwrite only)
TCG w/ FIPS Instant Secure Erase TCG(Trusted Computing Group) Secure Erase (Overwrite only)
TCG w/ FIPS Instant Secure Erase TCG(Trusted Computing Group) Secure Erase (Overwrite only)
TCG w/ FIPS Instant Secure Erase TCG(Trusted Computing Group) Secure Erase (Overwrite only)
TCG w/ FIPS

Glossary

ESD Kbpi Ktpi Gbps Mbps MB/s TB GB MB KB S.M.A.R.T.

Electrostatic Discharge 1,000 bits per inch 1,000 tracks per inch 1,000,000,000 bits per second 1,000,000 bits per second 1,000,000 bytes per second 1,000,000,000,000 bytes (for Drive Capacity) 1,000,000,000 bytes (for Drive Capacity) 1,048,576 bytes (for Memory Size) 1,024 bytes (for Memory Size) Self-Monitoring Analysis and Reporting Technology

HGST Hard Disk Drive Specification 18

General caution
The drive can be damaged by shock or ESD (Electrostatic Discharge). Any damage sustained by the drive after removal from the shipping package and opening the ESD protective bag are the responsibility of the user.
References
 SAS Compliance : "Serial Attached Serial SCSI-3 (SAS-3)"  SAS Protocol
 This drive supports Serial SCSI Protocol (SSP)  STP (Tunneled SATA) and SMP (Management protocol) protocols are NOT supported
HGST Hard Disk Drive Specification 19

General features
 Data capacities of 8TB/6TB  Spindle speeds of 7200 RPM  Fluid Dynamic Bearing motor  Dual Stage Actuator  Closed-loop actuator servo  Automatic Actuator lock  Write Cache  Advanced Power Management (APM)  S.M.A.R.T. (Self Monitoring and Analysis Reporting Technology)  Adaptive zone formatting  RVS(Rotational Vibration Safeguard)  Sector Buffer size of 128MB  Seek time of 8.5 ms in read operation (without Command Overhead)  Segmented buffer implementation  Automatic Error Recovery procedures for read and write commands  Automatic defect reallocation  Media cache technology  SAS Interface 12/6/3/1.5Gbps  Supports dual-ported operations  Supports full duplex operations  Variable sector size (512, 520, 528) bytes/sector and (4096,4112,4160,4224) bytes/sector  Back to back write  Self diagnostics at power on  64 bit addressing feature  SAS-3 compliant  ANSI T10 Protection Information (End-to-End)  Support TCG Enterprise_A SSC Encryption (specific model only)  FIPS-2 Support
HGST Hard Disk Drive Specification 20

Part 1. Functional specification
HGST Hard Disk Drive Specification 21

Fixed disk subsystem description
Control Electronics
The drive is electronically controlled by a microprocessor, several logic modules, digital/analog modules, and various drivers and receivers. The control electronics performs the following major functions:
 Controls and interprets all interface signals between the host controller and the drive.  Controls read write accessing of the disk media, including defect management and error recovery.  Controls starting, stopping, and monitoring of the spindle.  Conducts a power-up sequence and calibrates the servo.  Analyzes servo signals to provide closed loop control. These include position error signal and estimated
velocity.  Monitors the actuator position and determines the target track for a seek operation.  Controls the voice coil motor driver to align the actuator in a desired position.  Constantly monitors error conditions of the servo and takes corresponding action if an error occurs.  Monitors various timers such as head settle and servo failure.  Performs self-checkout (diagnostics).
Head disk assembly
The head disk assembly (HDA) is assembled in a clean room environment and contains the disks and actuator assembly. Helium is constantly circulated and filtered when the drive is operational. No venting of the HDA is accomplished, as HDA is hermetically sealed. The spindle is driven directly by an in-hub, brushless, sensorless DC drive motor. Dynamic braking is used to quickly stop the spindle.
Actuator
The read/write heads are mounted in the actuator. The actuator is a swing-arm assembly driven by a voice coil motor. A closed-loop positioning servo controls the movement of the actuator. An embedded servo pattern supplies feedback to the positioning servo to keep the read/write heads centered over the desired track. The actuator assembly is balanced to allow vertical or horizontal mounting without adjustment. When the drive is powered off, the actuator automatically moves the head to the actuator ramp outside of the disk where it parks.
HGST Hard Disk Drive Specification 22

Drive characteristics

This section describes the characteristics of the drive.

Default logical drive parameters

The default of the logical drive parameters in Identify Device data is as shown below.

Description Physical Layout Label capacity Bytes per Sector Number of Heads Number of disks Logical Layout1 Bytes per Sector Number of Sectors Total Logical Data Bytes

8TB 4,096
14 7
512 15,628,053,168 8,001,563,222,016

8TB model
8TB 4,160
14 7
520 15,362,376,264 7,988,435,657,280

8TB 4,224
14 7
528 15,081,071,304 7,962,805,648,512

Description Physical Layout Label capacity Bytes per Sector Number of Heads Number of disks Logical Layout1 Bytes per Sector Number of Sectors Total Logical Data Bytes

6TB 4,096
11 7
512 11,721,045,168 6,001,175,126,016

6TB+ Model
6TB 4,160
11 7
520 11,721,045,168 6,094,943,487,360

6TB 4,224
11 7
528 11,310,808,584 5,972,106,932,352

HGST Hard Disk Drive Specification 23

Description Physical Layout Label capacity Bytes per Sector Number of Heads Number of disks Logical Layout1 Bytes per Sector Number of Sectors Total Logical Data Bytes

8TB 4,096
14 7
4096 1,953,506,646 8,001,563,222,016

8TB model

8TB 4,112
14 7

8TB 4,160
14 7

4112 1,945,692,616 8,000,688,036,992

4160 1,920,297,033 7,988,435,657,280

8TB 4,224
14 7
4224 1,885,133,913 7,962,805,648,512

Description Physical Layout Label capacity Bytes per Sector Number of Heads Number of disks Logical Layout1 Bytes per Sector Number of Sectors Total Logical Data Bytes

6TB 4,096
11 7
4096 1,465,130,646 6,001,175,126,016

Table 2 Formatted capacity

6TB+ Model

6TB 4,112
11 7

6TB 4,160
11 7

4112 1,459,270,120 6,000,518,733,440

4160 1,465,130,646 6,094,943,487,360

6TB 4,224
11 7
4224 1,413,851,073 5,972,106,932,352

Notes: 1 Logical layout: Logical layout is an imaginary drive parameter (that is, the number of heads) which is used to access the drive from the system interface. The Logical layout to Physical layout (that is, the actual Head and Sectors) translation is done automatically in the drive. The default setting can be obtained by issuing an IDENTIFY DEVICE command

HGST Hard Disk Drive Specification 24

Data sheet

Description
Max Data transfer rate (Mbps) Interface transfer rate (MB/s) Typ Sustained transfer rate (MB/s) Data buffer size (MB) Rotational speed (RPM) Configurable number of buffer segment Number Recording density- max (Kbpi) Track density (Ktpi) Areal density - max (Gbits/in2)

8TB Model 1,924 1,200
205 128 7,200 2048 max 1,745 380 664

Table 3 Mechanical positioning performance (Sector format of 4k bytes/sector)

World Wide Name Assignment

Description Organization Manufacturing Site Product Block Assignment

8TB model
HGST Thailand
China Ultrastar He8-8 Thailand:23Bh
China:3B4h

Table 4 World Wide Name Assignment

6TB model
HGST Thailand
China Ultrastar He8-6 Thailand:23Ch
China:3B5h

6TB Model 1,833 1,200
199 128 7,200 2048 max 1,666 380 501

HGST Hard Disk Drive Specification 25

Drive organization
Drive Format
Upon shipment from HGST manufacturing the drive satisfies the sector continuity in the physical format by means of the defect flagging strategy described in Section 5 on page 14 in order to provide the maximum performance to users.
Cylinder allocation
Physical cylinder is calculated from the starting data track of 0. It is not relevant to logical CHS. Depending on the capacity some of the inner zone cylinders are not allocated. Data cylinder This cylinder contains the user data which can be sent and retrieved via read/write commands and a spare area for reassigned data. Spare cylinder The spare cylinder is used by HGST manufacturing and includes data sent from a defect location.

Performance characteristics

Drive performance is characterized by the following parameters:
 Command overhead  Mechanical positioning
- Seek time - Latency  Data transfer speed  Buffering operation (Look ahead/Write cache)
All the above parameters contribute to drive performance. There are other parameters that contribute to the performance of the actual system. This specification defines the characteristics of the drive, not the characteristics of the system throughput which depends on the system and the application.
Command overhead

Command overhead is defined as the time required
 from the time H->D Reg FIS w/ command bit is sent by host  to the time
 PIO Set Up FIS is sent by device(PIO Read/Write)  DATA FIS is sent by device(DMA Read)  DMA Activate FIS is sent by device(DMA Write)  DMA Set Up FIS is sent by device(NCQ Read/Write)  Seek Start (Read cache not hit or Seek) The table below gives average command overhead.

Command type (Drive is in quiescent state) Read (Cache not hit) Read (Cache hit) Write Seek

Typical time (ms)
0.2 0.2 0.5 0.2

Typical time for NCQ command (ms) 0.2 0.2 0.5 not applicable

Table 5 Command overhead

HGST Hard Disk Drive Specification 26

Mechanical positioning

Average seek time (without command overhead, including settling)

Command Type Read Write

Typical (ms) 8.5 9.0

Max (ms) 10.0 11.0

Table 6 Average seek time

The terms "Typical" and "Max" are used throughout this specification with the following meanings:

Typical. The average of the drive population tested at nominal environmental and voltage conditions.

Max.

The maximum value measured on any one drive over the full range of the environmental and voltage conditions. (See Section 6.2, "Environment" and Section 6.3, "DC Power Requirements")

Single track seek time (without command overhead, including settling)

Common to all models and all seek modes

Function Read Write

Typical (ms) 0.25 0.35

Table 7 Single Track Seek Time

Average latency

Max (ms) 0.35 0.45

Rotational speed 7200 RPM

Time for a revolution (ms)
8.3

Table 8 Latency Time

Drive ready time

Average latency (ms)
4.16

Power on to ready

Typical (sec) 20

Maximum (sec) 30

Table 9 Drive ready time

Ready

The condition in which the drive is able to perform a media access command (such as read, write) immediately

Power on This includes the time required for the internal self diagnostics.

HGST Hard Disk Drive Specification 27

Operating modes

Operating mode descriptions

Spin-up

Start up time period from spindle stop or power down

Seek

Seek operation mode

Write

Write operation mode

Read

Read operation mode

Idle_A

Spindle motor is working normally. Servo system is sleeping or waking up. Commands can be received and processed immediately

Idle_B

Spindle rotation at 7200 RPM with heads unloaded

Idle_C/Standby_Y Spindle rotation at Low RPM with heads unloaded

Standby_Z

Actuator is unloaded and spindle motor is stopped. Commands can be received immediately

Note: Upon power down or spindle stop a head locking mechanism will secure the heads in the OD parking position.

Mode transition times

Mode transition times are shown below.

From

To

Standby Z Idle A Idle B Idle A Idle C

Idle A Standby Z Idle A Idle B Idle A

Table 10 Mode transition times

RPM
0 -> 7200 7200 -> 0
7,200 7,200 6300 -> 7200

Typical Transition time (sec)
15 Immediately
1 0.7 4

Max Transition time (sec)
30 Immediately
30 30 30

HGST Hard Disk Drive Specification 28

Defect flagging strategy
Media defects are remapped to the next available sector during the Format Process in manufacturing. The mapping from LBA to the physical locations is calculated by an internally maintained table.
Shipped format
 Data areas are optimally used.  No extra sector is wasted as a spare throughout user data areas.  All pushes generated by defects are absorbed by the spare tracks of the inner zone.

N N+1 defect N+2 defect N+3

skip

skip

Figure 1 PList physical format
Defects are skipped without any constraint, such as track or cylinder boundary. The calculation from LBA to physical is done automatically by internal table.

HGST Hard Disk Drive Specification 29

Specification
Electrical interface Connector location
Refer to the following illustration to see the location of the connectors.
Figure 2 Connector location
Signal Connector
The drive uses the standard 29 pin Serial Attached SCSI (SAS) connector which conforms to the mechanical requirements of SFF 8660. The connector is expected to be used in an environment which uses a common connector structure for racking disk drives in a cabinet. The connector allows for plugging a drive directly into a backplane by providing the necessary electrical connection. Mechanical stability and device retention must be provided by a mechanism outside the drive.
HGST Hard Disk Drive Specification 30

29 pin Serial Attached SCSI (SAS) Connector Definition
Diagram of top and bottom of connector showing pinouts.

Figure 3 SAS Connector

Pin No. S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 S12 S13 S14 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15

Signal GND RP+ RPGND TPTP+ GND GND RS+ RSGND TSTS+ GND Vendor Spec Vendor Spec POWER DISABLE GND GND GND +5V-Charge +5V +5V GND READY LED GND +12V=Charge +12V +12V

Description GND for SAS Primary Port SAS Primary Port Receive (Positive) signal SAS Primary Port Receive (Negative) signal GND for SAS Primary Port SAS Primary Port Transmit (Negative) signal SAS Primary Port Transmit (Positive) signal GND for SAS Primary Port GND for SAS Secondary Port SAS Secondary Port Receive (Positive) signal SAS Secondary Port Receive (Negative) signal GND for SAS Secondary Port SAS Secondary Port Transmit (Negative) signal SAS Secondary Port Transmit (Positive) signal GND for SAS Secondary Port NOT USED (Pins P1-P3 tied internally) NOT USED (Pins P1-P3 tied internally) POWER DISABLE GROUND GROUND GROUND Pre-charge pin for +5V +5V power supply input +5V power supply input GROUND READY LED output GROUND Pre-charge pin for +12V +12V power supply input +12V power supply input

Table 11 29-pin Connector Signal Definition

HGST Hard Disk Drive Specification 31

Voltage and Ground Signals
The 12V and 5V contacts provide all of the voltages required by the drive. The two voltages share a common ground plane to which all of the ground contacts are connected.
Ready LED output
The drive provides an open-drain driver with 15mA of current sink capability to the Ready LED Output signal. The cathode of the LED should be connected to this signal. The LED and the current-limiting resistor must be provided by the enclosure
HGST Hard Disk Drive Specification 32

Environment

Temperature and humidity

Operating conditions
Temperature Relative humidity Maximum wet bulb temperature Maximum temperature gradient Altitude Non-Op conditions
Temperature Relative humidity Maximum wet bulb temperature Maximum temperature gradient Altitude

5 to 60°C 8 to 90% non-condensing 29.4°C non-condensing 20°C/Hour ­300 to 3,048 m
-40 to 70°C (Storage 0 to 70°C) 5 to 95% non-condensing 35°C non-condensing 30°C/Hour ­300 to 12,000 m (Inside dashed-dotted line of Figure 4)

Table 12 Temperature and humidity

Notes: 1. The system is responsible for providing sufficient ventilation to maintain a surface temperature below 65°C at the
center of the top cover of the drive.
2. Non condensing conditions should be maintained at any time.
3. Maximum storage period within shipping package is one year.

Altitude (m)

13000 12000

-40degC/12000m

11000

10000

9000

8000

7000

6000

5000

4000

3000

2000

1000

0

-1000

-40degC/-300m

-2000 -50 -40 -30

Altitude specification

40degC/12000m

Non-Operating

5degC/3048m

70degC/3048m 60degC/3048m

-20 -10

Operating

60degC/-300m

5degC/-300m

70degC/-300m

0 10 20 30 40 50 60 70 80 Temperature (degC)

Figure 4 Limits of temperature and altitude

HGST Hard Disk Drive Specification 33

Figure 5 Limits of temperature and humidity
Corrosion test
The drive shows no sign of corrosion inside and outside of the hard disk assembly and is functional after being subjected to seven days at 50°C with 90% relative humidity.
Atmospheric condition
Environments that contain elevated levels of corrosives (e.g. hydrogen sulfide, sulfur oxides, or hydrochloric acid) should be avoided. Care must be taken to avoid using any compound/material in a way that creates an elevated level of corrosive materials in the atmosphere surrounding the disk drive. Care must also be taken to avoid use of any organometallic (e.g. organosilicon or organotin) compound/material in a way that creates elevated vapor levels of these compounds/materials in the atmosphere surrounding the disk drive.
HGST Hard Disk Drive Specification 34

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

Input voltage
+5 Volts Supply +12 Volts Supply

During run and spin up
5V ± 5% 12V ± 5%

Absolute max spike voltage
­0.3 to 5.5V ­0.3 to 15.0V

Supply rise time
0 to 200ms 0 to 400ms

Table 13 Input voltage

Caution : To avoid damage to the drive electronics, power supply voltage spikes must not exceed specifications.

HGST Hard Disk Drive Specification 35

Power supply current (typical1)
Table 14 SAS power consumption HGST Hard Disk Drive Specification 36

Power supply generated ripple at drive power connector

+5V DC +12V DC

Maximum (mV pp) 200 250

MHz 0-10 0-10

Table 15 Power supply generated ripple at drive power connector

During drive start up and seeking 12-volt ripple is generated by the drive (referred to as dynamic loading). If the power of several drives is daisy chained together, the power supply ripple plus the dynamic loading of the other drives must remain within the above regulation tolerance. A common supply with separate power leads to each drive is a more desirable method of power distribution.

To prevent external electrical noise from interfering with the performance of the drive, the drive must be held by four screws in a user system frame which has no electrical level difference at the four screws position and has less than ±300 millivolts peak to peak level difference to the ground of the drive power connector.

Power Consumption Efficiency

Power Consumption Efficiency at Idle

W/TB W/GB

0.71 (8TB) 0.00071 (8TB)

Table 16 Power consumption efficiency

HGST Hard Disk Drive Specification 37

Reliability
Data integrity
No more than one sector is lost at Power loss condition during the write operation when the write cache option is disabled. If the write cache option is active, the data in write cache will be lost. To prevent the loss of customer data, it is recommended that the last write access before power off be issued after setting the write cache off.
Cable noise interference
To avoid any degradation of performance throughput or error rate when the interface cable is routed on top or comes in contact with the HDA assembly, the drive must be grounded electrically to the system frame by four screws. The common mode noise or voltage level difference between the system frame and power cable ground or AT interface cable ground should be in the allowable level specified in the power requirement section.
Load/Unload
The product supports a minimum of 600,000 normal load/unloads in a 40° C environment. Load/unload is invoked by transition of the HDD's power mode. (Chapter 4.5.4 "Operating modes")
Idle <-> unload idle Idle <-> Low rpm idle
Start/stop cycles
The drive withstands a minimum of 50,000 start/stop cycles in a 40° C environment and a minimum of 10,000 start/stop cycles in extreme temperature or humidity within the operating range.
Preventive maintenance
None
Data reliability
Probability of not recovering data is 1 in 1015 bits read. LDPC on the fly/ offline data correction
 600 bit LDPC  This implementation recovers maximum 330 bits single burst error by on the fly correction and maximum
450 bits single burst error by offline correction
Required Power-Off Sequence
The required BIOS sequence for removing power from the drive is as follows: Step 1: Issue one of the following commands. STOP UNIT Note: Do not use the Flush Cache command for the power off sequence because this command does not invoke Unload Step 2: Wait until the Command Complete status is returned. In a typical case 350 ms are required for the command to finish completion; however, the BIOS time out value needs to be 30 seconds considering error recovery time. Step 3: Terminate power to HDD.
HGST Hard Disk Drive Specification 38

Mechanical specifications Physical dimensions
Figure 6 Top and side views and mechanical dimensions All dimensions are in millimeters.
HGST Hard Disk Drive Specification 39

Figure 7 Bottom and side views with mounting hole locations All dimensions in the above figure are in millimeters. The following table shows the physical dimensions of the drive.

Height (mm) 26.1 MAX

Width (mm) 101.6 ± 0.25

Length (mm) 147 MAX

Table 17 Physical Dimensions

Weight (grams) 650 MAX

HGST Hard Disk Drive Specification 40

Connector locations
SAS
Figure 8 Connector locations
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. For reliable operation, the drive must be mounted in the system securely enough to prevent excessive motion or vibration of the drive during seek operation or spindle rotation, using appropriate screws or equivalent mounting hardware. The recommended mounting screw torque is 0.6 - 1.0 Nm (6-10 Kgf.cm). The recommended mounting screw depth is 3.8 mm maximum for bottom and 6.1 mm maximum for horizontal mounting. Drive level vibration test and shock test are to be conducted with the drive mounted to the table using the bottom four screws.
Heads unload and actuator lock
Heads are moved out from disks (unload) to protect the disk data during shipping, moving, or storage. Upon power down, the heads are automatically unloaded from disk area and the locking mechanism of the head actuator will secure the heads in unload position.
HGST Hard Disk Drive Specification 41

Vibration and shock

All vibration and shock measurements recorded in this section are made with a drive that has no mounting attachments for the systems. The input power for the measurements is applied to the normal drive mounting points.
Operating vibration

Random vibration (Linear)

The test is 30 minutes of random vibration using the power spectral density (PSD) levels shown below in each of three mutually perpendicular axes. The disk drive will operate without non-recoverable errors when subjected to the below random vibration levels.

Frequency

5 Hz

17 Hz

45 Hz

48 Hz

62 Hz

65 Hz

150 Hz

200 Hz

500 Hz

RMS (m/sec2)

[(m/sec2)2/Hz]

1.9 x 10E­3

1.1 x 10E­1

1.1 x 10E­1

7.7 x 10E­1

7.7 x 10E­1

9.6 x 10E­2

9.6 x 10E­2

4.8 x 10E­2

4.8 x 10E-2

6.57

Table 18 Random vibration PSD profile break points (operating) The overall RMS (root mean square) level is 6.57 m/sec2 (0.67 G).

Swept sine vibration (Linear)

The drive will meet the criteria shown below while operating in the specified conditions:
 No errors occur with 4.9 m/sec2 (0.5 G) 0 to peak, 5 to 300 to 5 Hz sine wave, 0.5 oct/min sweep rate with 3minute dwells at two major resonances
 No data loss occurs with 9.8 m/sec2 (1 G) 0 to peak, 5 to 300 to 5 Hz sine wave, 0.5 oct/min sweep rate with 3-minute dwells at two major resonances
Random vibration (Rotational)

The drive will meet the criteria shown below while operating in the specified conditions:  Less than 20% Performance degradation  The overall RMS (Root Mean Square) level of vibration is 12.5Rad/sec^2. PSD profile is shown below.

Frequency [(Rad/s2) 2/Hz]

20 Hz
1.90E -02

100 Hz
1.90E -02

200 Hz 800 Hz 1000 Hz

1.87E 1.87E 5.33E

-01

-01

-02

1500 Hz
7.70E -03

1700 Hz
4.00E -03

2000 Hz
4.00E -03

RMS (Rad/s2)
12.5

Table 19 Random vibration (Rotational) PSD profile break points

HGST Hard Disk Drive Specification 42

Nonoperating vibration

The drive does not sustain permanent damage or loss of previously recorded data after being subjected to the environment described below

Random vibration

The test consists of a random vibration applied for each of three mutually perpendicular axes with the time duration of 10 minutes per axis. The PSD levels for the test simulate the shipping and relocation environment shown below. The overall RMS (Root Mean Square) level of vibration is 10.2 m/sec2 (1.04 G).

Frequency [(m/sec2)2/Hz]

2 Hz 0.096

4 Hz 2.89

8 Hz 2.89

40 Hz 0.289

55 Hz 0.962

70 Hz 0.962

200 Hz 0.096

Table 20 Random vibration PSD profile break points (nonoperating)

Swept sine vibration

 19.6 m/sec2 (2 G) (Zero to peak), 5 to 500 to 5 Hz sine wave  0.5 oct/min sweep rate  3 minutes dwell at two major resonances

Operating shock

The drive meets the following criteria while operating in the conditions described below. The shock test consists of 10 shock inputs in each axis and direction for total of 60. There must be a delay between shock pulses long enough to allow the drive to complete all necessary error recovery procedures.
 No error occurs with a 98.1 m/sec2 (10 G) half-sine shock pulse of 11 ms duration.
 No data loss occurs with a 294 m/sec2 (30 G) half-sine shock pulse of 4 ms duration.
 No data loss occurs with a 686 m/sec2 (70 G) half-sine shock pulse of 2 ms duration.

Nonoperating shock

The drive will operate without non-recoverable errors after being subjected to shock pulses with the following characteristics.

Trapezoidal shock wave

 Approximate square (trapezoidal) pulse shape  Approximate rise and fall time of pulse is1 ms  Average acceleration level is 490 m/sec2 (50 G). (Average response curve value during the time following the
1 ms rise time and before the 1 ms fall with a time "duration of 11 ms")  Minimum velocity change is 4.23 m/sec

Sinusoidal shock wave

The shape is approximately half-sine pulse. The figure below shows the maximum acceleration level and duration.

Acceleration level (m/sec2) 2940(300G) 1470(150G)

Duration (ms) 1 11

Table 21 Sinusoidal shock wave

HGST Hard Disk Drive Specification 43

Nonoperating Rotational shock

All shock inputs shall be applied around the actuator pivot axis.

Duration 1 ms 2 ms
Table 22 Rotational Shock

Rad/sec2 30,000 20,000

HGST Hard Disk Drive Specification 44

Acoustics

The upper limit criteria of the octave sound power levels are given in Bels relative to one picowatt and are shown in the following table. The sound power emission levels are measured in accordance with ISO 7779.

Mode Idle
Operating

7200rpm (Typical / Max) 2.0 / 2.5 3.6 / 4.0

Table 23 Sound power levels

Mode definition: Idle mode.

The drive is powered on, disks spinning, track following, unit ready to receive and respond to interface commands.

Operating mode. Continuous random cylinder selection and seek operation of the actuator with a dwell time at each cylinder. The seek rate for the drive is to be calculated as shown below:

 Dwell time = 0.5 x 60/RPM

 Seek rate = 0.4 / (Average seek time + Dwell time)

Identification labels
The following labels are affixed to every drive shipped from the drive manufacturing location in accordance with the appropriate hard disk drive assembly drawing:
 A label containing the HGST logo, the HGST part number, and the statement "Made by HGST Japan, Ltd." or HGST Japan approved equivalent
 A label containing the drive model number, the manufacturing date code, the formatted capacity, the place of manufacture, UL/CSA/TUV/CE/C-Tick mark logos and WEEE/China RoHS logos
 A bar code label containing the drive serial number  A label containing the jumper pin description  A user designed label per agreement
The above labels may be integrated with other labels.

HGST Hard Disk Drive Specification 45

Safety UL and CSA standard conformity
The product is qualified per UL60950-1Second Edition and CAN/CSA-C22.2 No.60950-1-07 Second Edition, for use in Information Technology Equipment including Electric Business Equipment. The UL recognition or the CSA certification is maintained for the product life. The UL and C-UL recognition mark or the CSA monogram for CSA certification appear on the drive.
German Safety Mark
The product is approved by TUV on Test requirement: EN60950-12006+A11 but the GS mark is not applicable to internal devices such as this product.
Flammability
The printed circuit boards used in this product are made of material with the UL recognized flammability rating of V1 or better. The flammability rating is marked or etched on the board. All other parts not considered electrical components are made of material with the UL recognized flammability rating of V-2 minimum basically.
Safe handling
The product is conditioned for safe handling in regards to sharp edges and corners.
Substance restriction requirements
The product complies with the Directive 2002/95/EC of the European Parliament on the restrictions of the use of the certain hazardous substances in electrical and electronic equipment (RoHS) and with Halogen free requirements based on the electronics industry standard, IEC 61249-2-21 (http://www.iec.ch/). FIPS models do not comply with IEC 61249-2-21.
Secondary circuit protection
Spindle/VCM driver module includes 12 V over current protection circuit.
HGST Hard Disk Drive Specification 46

Electromagnetic compatibility
When installed in a suitable enclosure and exercised with a random accessing routine at maximum data rate, the drive meets the following worldwide EMC requirements:
 United States Federal Communications Commission (FCC) Rules and Regulations (Class B), Part 15. (A 6 dB buffer shall be maintained on the emission requirements).
 European Economic Community (EEC) directive number 76/889 related to the control of radio frequency interference and the Verband Deutscher Elektrotechniker (VDE) requirements of Germany (GOP).Spectrum Management Agency (SMA) EMC requirements of Australia. The SMA has approved C-Tick Marking for HGST Japan.
CE Mark
The product is declared to be in conformity with requirements of the following EC directives under the sole responsibility of HGST Japan, Ltd: Council Directive 2004/108/EC on the approximation of laws of the Member States relating to electromagnetic compatibility.
C-Tick Mark
The product complies with the following Australian EMC standard: Limits and methods of measurement of radio disturbance characteristics of information technology, AS/NZS 3548 : 1995 Class B.
BSMI Mark
The product complies with the Taiwan EMC standard "Limits and methods of measurement of radio disturbance characteristics of information technology equipment, CNS 13438 Class B."
KC Mark
The product complies with the Korea EMC standard. The regulation for certification of information and communication equipment is based on "Telecommunications Basic Act" and "Radio Waves Act" Korea EMC requirement are based technically on CISPR22 measurement standards and limits. KC standards are likewise based on IEC standards.
HGST Hard Disk Drive Specification 47

Part 2. Interface specification
HGST Hard Disk Drive Specification 48

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.
General
This section introduces some of the terminology that is used in describing Serial Attached SCSI (i.e. SAS). SAS is logically a bi-directional, point to point serial data channel that leverages the SCSI protocol set. Nodes are physically connected via a port. Ports may be connected point-to-point via SAS expanders, to form a complex switching network, referred to as a SAS domain. SAS is defined in terms of a hierarchy of functions or 'protocol layers'. This discussion will focus in on the aspects of SAS that are relevant to this product.
· SCSI Application Layer - Clause 10 · SSP Transport Layer (Serial SCSI Protocol) - Clause 9 · SAS Port Layer - Clause 8 · SSP Link Layer - Clause 7 · SAS PHY Layer - Clause 6 · SAS Physical Layer - Clause 5 All layers are defined in the following ANSI standard. · "SAS Protocol Layer - 2 (SPL-3)" In addition, this drive claims compliance with the following ANSI standards. · SCSI Architecture Model (SAM-5) · SCSI Block Commands (SBC-3)
SAS Features
The following SAS features are supported by the drive. · SAS Compliance - "Serial Attached SCSI - 3 (SAS-3)"
· SAS Protocol - This drive supports Serial SCSI Protocol (SSP). - STP (Tunneled SATA) and SMPs (Management protocols) are NOT supported.
HGST Hard Disk Drive Specification 49

· 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 Gbps), G2 (3.0 Gbps), G3 (6.0 Gbps), and G4 (12.0 Gbps) supported - Largely automated OOB and speed negotiation sequences - Optional support for the hot-plug timeout in hardware
· Partial support for Disconnect/Reconnect Mode Page (0x02) - Maximum Connect Time Limit - SUPPORTED - Bus Inactivity Time Limit - NOT SUPPORTED - Maximum Burst Size - SUPPORTED - First Burst Size - NOT SUPPORTED
· Others... - Connection Rate Matching - Hard Reset primitive sequence detection and validation in hardware - Support for NOTIFY (Power Loss Expected) - Hashed WWN validation in hardware - Extended CDB support
HGST Hard Disk Drive Specification 50

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.

Object Port Identifier Port Name Device Name PHY Identifier

SAS Implementation SAS address Not defined SAS address PHY identifier

Table 24 Names and Identifiers Where the SAS address format is defined by ANSI as follows:

Byte/Bit 7 0 1 2 3 4 5 6 7

6

5

4

3

2

1

0

NAA (5h)

(MSB)

IEEE Company ID

(LSB)

(MSB)

Vendor Specific Identifier

(LSB)

Table 25 SAS Address Format
The SAS device name is a unique SAS address worldwide name. This device name is reported through the SCSI Vital Products Data. Each of the two SAS ports also has a unique SAS address worldwide name. These port identifiers are reported in the IDENTIFY address frame and are used as source and destination addresses in the OPEN address frame. They are also reported through the SCSI Vital Products Data. Since this drive is one device with two ports it has three SAS addresses. All SAS addresses are in 64-bit IEEE Registered Name format, as illustrated in Table 26.

Bit

63-60

59-36

35-24

0101 OUI in Canonical Form Block Assignment

23-2 S/N

1-0 Object

Table 26 IEEE Registered Name Format

HGST Hard Disk Drive Specification 51

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.

Table 27 Name Address Authority field

HGST Hard Disk Drive Specification 52

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.
Link Reset Sequence

The Link Reset sequences for SAS are defined in the SPL-3 ANSI specification with a general overview shown below. As shown in the diagram, a PHY Reset sequence, consists of an OOB sequence, followed by speed negotiation. Link Reset sequences will always include a PHY Reset sequence, followed by an Identification sequence. Inclusion of a Hard Reset sequence is optional. If Hard Reset is performed, it will be preceded by a PHY Reset sequence, and followed by PHY Reset and an Identification sequence.

SAS

Time

Link Reset sequence

Phy Reset sequence

OOB sequence

Speed Negotiation sequence

Identification sequence

SAS w/Hard Reset

Time

Link Reset sequence with hard error Phy Reset sequence Hard Reset sequence Phy Reset sequence Identification sequence

Figure 9 Link Reset Sequence
Hard Reset
A Hard Reset sequence on a port will not affect the other port, but the outstanding commands on the other port will be aborted due to the LUN reset associated with the Hard Reset. The effect of a Hard Reset will be similar to a Power on Reset, and will result in the re-initialization of all drive resources. The first command issued from every initiator on the port that received the Hard Reset will result in a CHECK CONDITION with a sense key of UNIT ATTENTION and an additional sense code of SCSI BUS RESET OCCURRED. The first command issued from every initiator on the other port will result in a CHECK CONDITION and an additional sense code of BUS DEVICE RESET OCCURRED.
A Hard Reset sequence will never be issued by the drive. A link reset will be initiated by the drive on the affected port upon completion of Hard Reset processing.

HGST Hard Disk Drive Specification 53

SAS OOB (Out of Band)

Out of Band (OOB) signals are low-speed signal patterns detected by the PHY that do not appear in normal data streams. They consist of defined amounts of idle time followed by defined amounts of burst time. During the idle time, D.C. idle is transmitted. During the burst time, ALIGN (0) primitives are transmitted repeatedly. The signals are differentiated by the length of idle time between the burst times.
As a SAS compliant device, the drive uses three OOB signals: COMINIT/COMRESET and COMWAKE and COMSAS.OOB operations are beyond the scope of this specification. Please refer to the ANSI SPL-3 specification for more details.
The drive will initiate OOB by sending COMINITs, under the following conditions:
- POR - Loss of sync - Identify timeout
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). The drive's PHY capabilities are defined in table below:

PHY Capabilities:

Byte /Bit 0
1 2 3

7
Start =1b
G1 Without SSC=1b

6
TX SSC Type = 0b
G1 With SSC=1b

5

4

Reserved

G2 Without G2 With

SSC=1b

SSC=1b

Reserved

Reserved

3

2

1

Requested Logical Link Rate = 0h

G3 Without G3 With G4 Without SSC=1b SSC=1b SSC=1b

Parity

Table 28 SAS Speed Negotiation

 Start is set to 1 to indicate the beginning of the PHY capabilities  TX SSC Type is set to 1 to indicate that PHY's transmitter uses center-spreading-SSC when SSC is enabled  TX SSC Type is set to 0 to indicate that PHY's transmitter uses down-spreading-SSC when SSC is enabled  Requested Logical Link Rate field is set to 0 to indicate that drive does not support multiplexing  G1 Without SSC is set to 1 to indicate that drive supports G1 (1.5 Gbps) without SSC  G2 Without SSC is set to 1 to indicate that drive supports G2 (3.0 Gbps) without SSC  G3 Without SSC is set to 1 to indicate that drive supports G3 (6.0 Gbps) without SSC  G4 Without SSC is set to 1 to indicate that drive supports G4 (12.0 Gbps) without SSC  G1 With SSC set to 1 to indicate that drive supports G1 (1.5 Gbps) with SSC  G2 With SSC set to 1 to indicate that drive supports G2 (3.0 Gbps) with SSC  G3 With SSC set to 1 to indicate that drive supports G3 (6.0 Gbps) with SSC  G4 With SSC is set to 1 to indicate that drive supports G4 (12.0 Gbps) with SSC  Parity is set to 1 for even parity of the total number of SNW-3 PHY capabilities, including Start bit.
Training is based on the highest untried commonly supported settings on the exchanged SNW-3 supported settings bits. If a Train-SNW is invalid and there are additional, untried, commonly supported settings exchanged during SNW-3, then a new Train-SNW will be performed based on the next highest untried, commonly supported settings. Table 29 Supported Settings Bit Priorities defines the priority of the supported settings bits.

HGST Hard Disk Drive Specification 54

Priority Highest
... ... ... ... ... ...

Bit G4 With SSC bit G4 Without SSC bit G3 With SSC bit G3 Without SSC bit G2 With SSC bit G2 Without SSC bit
G1 With SSC bit G1 Without SSC bit

Lowest

Table 29 Supported Settings Bit Priorities

PHY Error Handling

This section defines the PHY layer error handling of the drive.

Error

Error Handling Procedure

Link Reset

After POR or Hard Reset, the drive initiates link reset by transmitting exactly 1 COMINIT. For other resets, the drive does not initiate Link Reset.

COMINIT Timeout

If COMINIT or COMSAS is not received before the "Hot Plug Timeout" period expires, the drive continues to transmit DC zero and wait for COMINIT/COMSAS. Firmware is notified. This is not considered an error.

COMSAS Timeout

If COMINIT is detected, COMSAS is transmitted, and COMSAS is not received before the COMSAS Detect Timeout timer expires, firmware is notified and the drive continues to transmit DC zero and wait for COMINIT.

Speed Negotiation Errors

If speed negotiation fails with no match, or if the drive fails retrying the matched link rate, firmware is notified and the drive continues to transmit DC zero and wait for COMINIT. If the match link rate retry fails, the PHY Reset Problem counter is incremented (Log Page 0x18).

Loss of Sync

If the drive loses Dword sync long enough for the loss of sync timer to expire, firmware is notified and the drive transmits a COMINIT to initiate a new link reset. The loss of Dword sync counter is incremented (Log Page 0x18).

Disparity/Invalid Dword Error If a disparity error or an invalid Dword is detected by the drive, the Invalid Dword Count is incremented (Log Page 0x18). The Running Disparity Error Count in Log Page 0x18 is not used

Table 30 PHY Layer Error Handling

HGST Hard Disk Drive Specification 55

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.
Address Frames
Address frames are used for the identification sequence and for connection requests and are only sent outside connections. The Address Frame format is defined below:

Bit

Byte

7

6

5

4

3

2

1

0

0

RSVD

Device Type

Address Frame Type

1-27

Frame Type Dependent bytes

28-31

CRC

Table 31 Address Frame Format

 Address Frame Type indicates the type of address frame and is defined in Table 32. This field determines the definition of the frame type dependent bytes.

Value

Address Frame Type Description

0000b

IDENTIFY: Identification Sequence

0001b

OPEN: Connection Request

Others

Reserved

Table 32 Frame Type:

HGST Hard Disk Drive Specification 56

Identify Address Frame

The Identify Address Frame format is used for the identification sequence. The Identify Address Frame is sent after the PHY reset sequence completes. The Identify Address Frame format is defined as follows:

Bit

Byte

7

6

5

4

3

2

1

0

0

RSVD

Device Type = 1h

Address Frame Type = 0

1

Reserved

Reason

2

Reserved

SSP

STP

SMP

Initiator Port Initiator Port Initiator Port

RSVD

3

Reserved

SSP

STP

SMP

Target Port Target Port Target Port

RSVD

4-11

Device Name

12-19

SAS Address

20

PHY Identifier

21

Persistent Capable

Power Capable

Slumber Capable

Partial Capable

Inside ZPSDS Persistent

Requested Inside ZPSDS

Break_Reply Capable=1b

22

Pwr_DIS Capable

23-27

Reserved

28-31

CRC

Table 33 Identify Address Frame
 Device Type is set to 001b to indicate that this drive is an "End Device"  Address Frame Type is set to 00b to indicate that this is an IDENTIFY  Reason indicates the reason for link reset sequence as defined in Table 34  Initiator Port bits is set to 000b since this device is a target device only  Target Port bits is set to 100b since this device is a SSP target device only  Device Name contains Target Device Identifier  SAS Address contains the port identifier of the SAS port transmitting this frame  PHY Identifier contains the PHY identifier of the PHY transmitting this frame  Persistent Capable is set to 0b to indicate the drive does not support persistent connections  Power Capable is set to 00b to indicate drive does not issue PWR_REQ or PWR_DONE, and does not respond
to PWR_GRANT  Slumber Capable is set to 0b to indicate drive does not support slumber power PHY mode  Partial Capable is set to 0b to indicate drive does not support partial power PHY mode  Inside ZPSDS Persistent: set to 0b since this is an "End Device"  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 Hard Disk Drive Specification 57

Value

Address Frame Type Description

00b

Power on

01b 02b

OPEN: Connection Request
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

Table 34 Reason Field
Open Address Frame

The Open Address Frame format is used for the identification sequence. The Open Address Frame is sent after the PHY reset sequence completes. The Open Address Frame format is defined as follows:

Byte 7

Bit

6

5

4

3

2

1

0

0

Initiator Port=0

Protocol = 1

Address Frame Type = 1

1

Features = 0

Connection Rate = 8h, 9h, Ah, or Bh

2-3

Initiator Connection Tag

4-11

Destination SAS Address

12-19

Source SAS Address

20

Source Zone Group

21

Pathway Blocked Count

22-23

Arbitration Wait Time

24-27

More Compatible Features

28-31

CRC

Table 35 Open Address Frame Format
 Initiator Port is set to zero when the drive is the source port acting as a SAS target  Protocol is set to 001b to indicate SSP Protocol  Features is set to zero and ignored by the drive per SPL-3  Connection Rate is set to 8h (1.5Gbps), 9h (3Gbps), Ah (6Gbps), or Bh (12Gbps), depending on requested link
rate. Rate matching is supported by the drive, therefore if the link to the drive is 3.0Gbps, and the Connection Rate is 1.5Gbps, the drive will insert ALIGNs between Dwords, to match the Connection Rate.  Initiator Connection Tag 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).  Source Zone Group is set to zero and ignored by the drive per SPL-3

HGST Hard Disk Drive Specification 58

 Pathway Blocked Count indicates the number of times the port has retried this connection request due to receiving OPEN_REJECT (PATHWAY BLOCKED). The drive will not increment the PATHWAY BLOCKED COUNT value past FFh.
 Arbitration Wait Time indicates how long the port transmitting the OPEN address frame has been waiting for a connection request to be accepted. For values from 0000h to 7FFFh, the Arbitration Wait Time timer increments in one microsecond steps. For values from 8000h to FFFFh, the Arbitration Wait Time timer increments in one millisecond step.
 More Compatible Features is set to zero and ignored by the drive per SPL-3.
Link Layer Error Handling
This section defines the Link layer error handling of the drive.

Error

Error Handling Procedure

IDENTIFY Timeout If IDENTIFY is not received before the IDENTIFY timer expires (1ms), firmware is notified and the drive transmits a COMINIT to initiate a new link reset.

BREAK Received

If BREAK is received while the drive has ACK/NAK balance, BREAK or BREAK_REPLY is transmitted and a new connection may be opened if the drive still has frames to transmit. Firmware is not notified. If BREAK is received while the drive does NOT have ACK/NAK balance, BREAK or BREAK_REPLY is transmitted and the current command is aborted and will return Check Condition status with sense data indicating an ACK/NAK timeout.

NAK and ACK/ NAK Timeout

If a NAK is received on a RESPONSE frame, the RESPONSE frame is retransmitted with the RETRANSMIT bit set to one. If an ACK or NAK is not received for a RESPONSE frame within 1ms, the RESPONSE frame will be retransmitted with the RETRANSMIT bit set to one. The drive will retry sending a RESPONSE frame once.

Bad Frame CRC

If a frame fails the CRC check, the frame is NAKed by the drive and discarded. This is a link layer function. The command associated with a NAKed DATA or XFER_RDY frame is aborted with check condition status and sense data corresponding to DATA_PHASE_ERROR is returned. COMMAND frames that fail the CRC check are NAKed and discarded.

Table 36 Link Layer Error Handling (part 1 of 2)

HGST Hard Disk Drive Specification 59

Error

Error Handling Procedure

OPEN_REJECT Credit Timeout

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. The drive will retry at the connection at a lower rate, and if a connection eventually fails for this session at 1.5Gbps, the command is internally aborted.  OPEN_REJECT ­ (PATHWAY_BLOCKED) ­ handled the same as OPEN_REJECT(RETRY)  OPEN_REJECT(BAD_DESTINATION) ­ handled the same as OPEN_REJECT(RETRY)
OPEN_REJECT ­ Non-Retry-able Variations ­ If these are received, the command is internally aborted by the drive
 OPEN_REJECT(BAD_DESTINATION)  OPEN_REJECT(WRONG_DESTINATION)  OPEN_REJECT(PROTOCOL_NOT_SUPPORTED)
If credit is not received before the credit timer expires, DONE(CREDIT_TIMEOUT) is sent to the Initiator.

DONE Timeout

If credit is extended and the DONE timer expires, BREAK is sent by hardware to tear down the connection.

CREDIT_BLOCKED If CREDIT BLOCKED is received and the drive has frames to send in the current connection, DONE(CREDIT_TIMEOUT) is returned. Otherwise, DONE(NORMAL) is returned.

OPEN Frame Checking Reserved fields in the OPEN frame are not checked.  The Dest Address field is checked, and if it doesn't match OPEN_REJECT(WRONG_DESTINATION) is returned.  The Protocol field is checked and if it isn't set to SSP OPEN_REJECT(PROTOCOL_NOT_SUPPORTED) is returned.  If the Link Rate exceeds the physical link rate on that port, OPEN_REJECT(LINK_RATE_NOT_SUPPORTED) is returned.  The Initiator bit is not checked.

OPEN Response If AIP or OPEN_ACCEPT is not received before the OPEN Response timer expires, the

Timeout

hardware transmits BREAK.

CLOSE Timeout

If CLOSE is not received before the CLOSE timer expires, the hardware transmits BREAK.

PHY Not Ready

If Link Reset occurs outside of a connection, commands can execute normally across the link reset. If a link reset occurs inside of a connection, the behavior is similar to BREAK in that it is treated as an abruptly closed connection. In cases where the command cannot be continued normally (e.g. a frame is corrupted by OOB signals, or we do not have ACK/NAK balance), the command is terminated with CHECK CONDITION status with sense data corresponding to ACK/NAK TIMEOUT.

Table 37 Link Layer Error Handling (part 2 of 2)

HGST Hard Disk Drive Specification 60

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

The Transport layer defines the frame format as follows.

Byte
0 1-3 4 5-7 8-9
10
11 12-15 16-17 18-19 20-23 24-m
(n-3)-n

7

6

5

Reserved

Bit

4

3

2

Frame Type

Hashed Destination Address

Reserved

Hashed Source Address

Reserved

TLR Control = 00b

Retry Data Frames =0b

Reserved

Reserved

Tag

Target Port Transfer Tag

Data Offset

Information Unit

Fill Bytes (if needed)

CRC

1

0

Retransmit

RSVD

# of fill bytes

Table 38 SAS Frame Format FRAME TYPE field, which defines the format of the INFORMATION UNIT field as follows:

Code 01h 05h 06h 07h 16h f0-ffh all others

Name of Frame DATA
XFER_RDY COMMAND RESPONSE
TASK

Information Unit

Originator

Data

Initiator or Target

Data Transfer Ready

Target

Command

Initiator

Response

Target

Task Management Function

Initiator

Vendor Specific

Reserved

IU Size (bytes) 1-1024 12 28-284 24-1024 28

Table 39 FRAME TYPE Field

 Hashed Destination SAS Address contains the hashed value of the destination SAS address
 Hashed Source SAS Address contains the hashed value of the source SAS address
 TLR Control is not supported
 Retry Data Frames is not supported
 Changing Data Pointer is not supported
 Number of Fill Bytes indicates the number of fill bytes between the INFORMATION UNIT field and the CRC field. The Retransmit bit is set to one for RESPONSE frames when attempting to retransmit this frame due to receiving an error during the initial transmission. It shall be set to zero for all other frame types. The Number of Fill Bytes field shall be set to zero for all frame types except DATA frames

HGST Hard Disk Drive Specification 61

 Tag field contains a value that allows the SSP port to establish a context for commands and task management functions
 Target Port Transfer Tag is set and used by the drive. The initiator should echo this field in outbound data IU.
 Information Unit contains the information unit, the format of which is defined by the FRAME TYPE field.
 Fill bytes shall be included after the INFORMATION UNIT field so the CRC field is aligned on a four byte boundary.

Command Information Unit
The COMMAND frame is sent by an SSP initiator port to request that a command be processed by the drive.

Byte 7

Bit

6

5

4

3

2

1

0

0-7

Logical Unit Number

8

Reserved

9

Disable First Burst=0

Reserved

Task Attribute

10

Reserved

11

Additional CDB Length (in Dwords)

Reserved

12-27

CDB

28-n

Additional CDB Bytes

Table 40 COMMAND Information Unit  Logical Unit Number contains the address of the logical unit. The drive only supports a LUN of 0's.  Disable First Burst is not supported by the drive Task Attribute is defined as follows:

Value 000b

Attribute Simple_Q

001b

Head_of_Q

010b 100b 101b

Ordered_Q ACA_Q (not supported)
Reserved

Table 41 Task Attribute Field  Additional CDB Length contains the length in Dwords (four bytes) of the ADDITIONAL CDB field.  CDB and Additional CDB Bytes together contain the CDB.

HGST Hard Disk Drive Specification 62

TASK Information Units

Bit

Byte

7

6

5

4

3

2

1

0

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

Table 42 TASK Information Unit

 Logical Unit Number field contains the address of the logical unit. The drive only supports a LUN of 0's.  Task Management Function field is defined as follows:

Value 01h 02h 04h
08h
10h

Function ABORT TASK: The drive shall perform the ABORT TASK associated with the value of the TAG OF TASK TO BE MANAGED field
ABORT TASK SET: The drive shall perform the ABORT TASK SET by aborting all outstanding tasks for the Initiator that sent the TMF.
CLEAR TASK SET: This TMF causes the drive to abort all tasks in the task set. The action is equivalent to receiving a series of Abort Task requests from all Initiators.
A unit attention condition shall be generated for all other Initiators with tasks in the task set. The Additional Sense Code shall be Commands cleared by another Initiator.
LUN RESET: The LUN RESET causes the Target to execute a hard reset. This means: 1. Abort all tasks for all Initiators on either both ports. 2. Release any device reservation on either port. 3. Set a Unit Attention condition for all Initiators.
I_T NEXUS RESET: The I_T NEXUS RESET causes the drive to abort all outstanding tasks for the Initiator that sent the TMF. In addition, a Unit Attention is set for the initiator that sent the TMF, indicating I_T NEXUS LOSS. This TMF does not affect task sets for other initiators.

40h

CLEAR ACA (not supported)

80h QUERY TASK: The drive shall return a response of FUNCTION SUCCEEDED if the specified task

exists, or FUNCTION COMPLETE if the specified task does not exist.

81h QUERY TASK SET: The drive shall return a response of FUNCTION SUCCEEDED if there is any task exist, or FUNCTION COMPLETE if there is no task exist.

82h others

QUERY ASYNCHRONOUS EVENT (formerly QUERY UNIT ATTENTION): The drive shall return a response of FUNCTION SUCCEEDED if there is a unit attention or a deferred error pending, or FUNCTION COMPLETE if there is no unit attention or no deferred error pending.
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.

Table 43 TASK MANAGEMENT FUNCTION Field

HGST Hard Disk Drive Specification 63

 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

Byte 7

6

5

Bit

4

3

2

1

0

0

Reserved

UADE Depth

Sense Key

1

Additional Sense Code

2

Additional Sense Code Qualifier

Table 44 Additional Response Information Argument for Query Async Event
 UADE Depth is the number of pending unit attention conditions or deferred errors. It is defined as in  Sense Key is the value of the SENSE KEY field in the highest-priority pending unit attention condition or
deferred error.  Additional Sense Code is the value of the ADDITIONAL SENSE CODE field in the highest-priority pending unit
attention condition or deferred error.  Additional Sense Code Qualifier is the value of the ADDITIONAL SENSE CODE QUALIFIER field in the
highest-priority pending unit attention condition or deferred error

Code 00b 01b 10b 11b

Description The combined number of unit attention conditions and deferred errors is unknown The combined number of unit attention conditions and deferred errors is one The combined number of unit attention conditions and deferred errors is greater than one Reserved

Table 45 UADE DEPTH Field

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.

Bit

Byte

7

6

5

4

3

2

1

0

0 - 3

Requested Offset

4 - 7

Write Data Length

8 - 11

Reserved

Table 46 XFER_RDY Information Units
 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.
 Write Data Length contains the number of bytes of write data the Initiator may transmit to the drive (using

DATA Information Units

The DATA frame is sent by the drive to the Initiator (in bound data) or by the Initiator to the drive (out bound data).

Byte

Bit

7

6 5 4 3 2

1

0

0 - (n-1)

Data

Table 47 Data Information Unit

HGST Hard Disk Drive Specification 64

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

Byte 0-7 8-9

7 MSB

10 11 12 - 15 16 - 19 20 - 23 24 - (24+m) (24+m) -(23+m+n)

Bit

6

5

4

3

2

Reserved

Retry Delay Timer

Reserved Status
Reserved Sense Data Length (n bytes) Response Data Length (m bytes)
Response Data Sense Data

1

0

LSB DataPres

Table 48 Response Information Unit

Retry Delay Timer contains the retry delay timer code which is defined as follows:

Status Code BUSY
QUEUE FULL GOOD

Retry Delay Timer Code
0000h 0001h-FFEFh
FFF0h-FFFDh FFEFh FFFFh 0000h
0001h-FFEFh
FFF0h-FFFFh 0000h-FFFFh

Description
Same as normal busy The number of 100 milliseconds increments which Initiator should wait before sending another command to drive
Reserved Initiator should stop sending commands to drive
Drive is not able to accept the command Same as normal busy
Initiator should wait before sending another command to the drive until: a) At least the number of 100 milliseconds increments indicated in the RETRY DELAY TIMER CODE field have elapsed; or b) A command addressed to the drive completes. Reserved Reserved

Table 49 RETRY DELAY TIMER Field (part 1 of 2)

Status Code
CHECK CONDITION CONDITION MET RESERVATION CONFLICT ACA ACTIVE TASK ABORT

Retry Delay Timer Code
0000h-FFFFh 0000h-FFFFh 0000h-FFFFh
0000h-FFFFh 0000h-FFFFh

Description
Reserved Reserved Reserved
Reserved Reserved

Table 50 RETRY DELAY TIMER Field (part 2 of 2)

HGST Hard Disk Drive Specification 65

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.

Value 00b 01b 10b 11b

DATAPRES Description NO DATA: no data present RESPONSE_DATA: response data present SENSE_DATA: sense data present
Reserved

Table 51 DATAPRES Field

Bit Byte
7 6 5 4 3 2 1 0

0 - 2

Reserved

3

Response Code

Table 52 RESPONSE Data

Response Codes are defined as follows:

Value 00b 02b 04b 05b 08b 09b others

DATAPRES Description Task Management Function complete
Invalid Frame Task Management Function not supported
Task Management Function failed Task Management Function succeeded
Invalid LUN Reserved

Table 53 RESPONSE Codes

HGST Hard Disk Drive Specification 66

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.

Initiator

Target

Initiator

Target

Command IU

Command IU

Data IU (s)

Xfr_Rdy IU Data IU (s)

Response IU

Read Type Command

Time

IU Sequence

Time

Figure 10 SSP Information Unit Sequences

Response IU

Write Type Command

Time

IU Sequence

Time

HGST Hard Disk Drive Specification 67

Transport Layer Error Handling
This section defines the Transport layer error handling by the drive.

Error

Error Handling Procedure

SSP Header Field Checking Reserved fields in SSP frames are not checked.

Data Offset Error

If a DATA frame with an invalid Data Offset is received, the command associated with the DATA frame is aborted with Check Condition status and sense data corresponding to a DATA OFFSET ERROR is returned

I_T NEXUS Loss Timeout

If a connection cannot be established to an Initiator before the I_T NEXUS LOSS timer expires (Mode Page 0x19), all commands from the Initiator are internally aborted. The first new command received from the affected Initiator results in a CHECK CONDITION with sense data corresponding to I_T NEXUS LOSS OCCURRED.

Initiator Response Timeout

If DATA frames corresponding to an outstanding XFER_RDY frame are not received before the Initiator Response timer expires (Mode Page 0x19), the command is aborted with CHECK CONDITION status and sense data corresponding to INITIATOR RESPONSE TIMEOUT is returned for the affected command.

Data Overflow

If more data is received than requested via an XFER_RDY frame, the affected command is aborted with CHECK CONDITION status with sense data corresponding to TOO MUCH WRITE DATA is returned.

Invalid Target Port Transfer Tag

If a DATA frame is received and the TPTT is not set to the value used in the corresponding XFER_RDY frame, the frame is discarded. If a COMMAND or TASK frame is received with the TPTT set to a value other than 0xFFFF, a RESPONSE frame with RESPONSE_DATA set to INVALID FRAME is returned.

Invalid Frame Length

If a DATA frame is received with zero bytes of payload data, the frame is discarded. This is not considered an error. If a COMMAND/TASK frame that is too short is received, RESPONSE data corresponding to INVALID FRAME is returned. The additional CDB length field of a COMMAND frame is not checked for correctness. If a DATA frame is received with a payload greater than 1024 bytes, the frame is discarded and the command is aborted with CHECK CONDITION status and sense data corresponding to DATA_PHASE_ERROR is returned.

Table 54 Transport Layer Error Handling

HGST Hard Disk Drive Specification 68

SCSI Command Set

Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory

Type M M O O O O O O O O O O M M O O O O M O O O O O O O M O O O O O M M

Code 04h 12h 4Ch 4Dh 15h 55h 1Ah 5Ah 5Eh 5Fh 34h 90h 08h 28h A8h 88h 7Fh/09h 3Ch 25h 9Eh/10h 37h B7h 3Eh 9Eh 07h 1Ch 17h 57h A3h/05h A0h A3h/0Ch A3h/0Dh 03h 16h

Description FORMAT UNIT (04) INQUIRY (12) LOG SELECT (4C) LOG SENSE (4D) MODE SELECT (15) MODE SELECT (55) MODE SENSE (1A) MODE SENSE (5A) PERSISTENT RESERVE IN (5E), PERSISTENT RESERVE OUT (5F) PRE-FETCH (34) PRE-FETCH (90) READ (6) - (08) READ (10) - (28) READ (12) - (A8) READ (16) - (88) READ (32) - (7F/09) READ BUFFER (3C) READ CAPACITY (10) - (25) READ CAPACITY (16) (9E/10) READ DEFECT DATA (37) READ DEFECT DATA (B7) READ LONG (3E),page 207 READ LONG (9E),page 208 REASSIGN BLOCKS (07) RECEIVE DIAGNOSTICS RESULTS (1C) RELEASE (17) RELEASE (57) REPORT DEVICE IDENTIFIER (A3/05) REPORT LUNS (A0) REPORT SUPPORTED OPERATION CODES (A3/0C) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D) REQUEST SENSE (03) RESERVE (16)

Table 55 SCSI Commands Supported (part 1 of 2)

HGST Hard Disk Drive Specification 69

Type O O O O O M O O O O M O O O O M M O O O O O O O O O O O O O

Code 56h 01h 48h A2h B5h 1Dh A4h/06h 1Bh 35h 91h 00h 2Fh AFh AFh 7Fh/0Ah 0Ah 2Ah AAh 8Ah 7Fh/0Bh 2Eh AEh 8Eh 7Fh/0Ch 3Bh 3Fh 9Fh 41h 93h 7Fh/0Dh

Description RESERVE (56) REZERO UNIT (01) SANITIZE (48) SECURITY PROTOCOL IN (A2) SECURITY PROTOCOL OUT (B5) 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 (10) - (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 BUFFER (3B) WRITE LONG (10) (3F) WRITE LONG (16) (9F) WRITE SAME (10) - (41) WRITE SAME (16) - (93) WRITE SAME (32) - (7F/0D)

Table 56 SCSI Commands Supported (part 2 of 2)

HGST Hard Disk Drive Specification 70

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.

Bit

7

6

5

4

3

2

1

0

VU = 0

Reserved = 0

Table 57 SCSI Control Byte Note: * - The drive ignores the link bit and flag bit in the CDB.

Abbreviations

These abbreviations are used throughout the following sections:

LUN VU LBA RSVD MSB LSB

Logical Unit Number. An encoded three bit identifier for the logical unit. Vendor Unique bits Logical Block Address Reserved Most Significant Byte Least Significant Byte

Byte ordering conventions
In this specification, where it is not explicitly stated, all multi-byte values are stored with the most significant byte first. For example, in a 4 byte field, byte 0 will contain the MSB and byte 3 the LSB.

HGST Hard Disk Drive Specification 71

FORMAT UNIT (04)

Byte
0
1
2 3-4 5

7

6

FMTPINFO

VU = 0

Bit

5

4

3

Command Code = 04h

LONG LIST=0

FMTDATA CMPLIST

VU = 0

Obsolete = 0

Reserved = 0

2

1

0

Defect List Format

FFMT

FLAG

LINK

Table 58 FORMAT UNIT

- 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).
- FmtData set to one specifies that a Data Out phase follows the Command phase. The Data Out phase consists of a Parameter List header, optionally followed by an Initialization Pattern Descriptor, optionally followed by a Defect List. If FmtData=0, the following defaults are assumed: DPRY=0, DCRT=1, STPF=1, IP=0, DSP=0, Immed=0.
- CmpLst
- Set to one specifies that the Grown Defect List (GList) existing prior to the issuance of the Format Unit command be discarded. If provided, the DList then becomes the GList. Following these operations, the Drive will be formatted with the PList and GList.
- Set to zero specifies that the GList existing prior to the issuance of the Format Unit command is retained. If provided, the DList is combined with the GList to become the new GList. Following these operations, the Drive will be formatted with the PList and GList.
Note: The drive manages two internal defect lists and one external. The Plist is created at time of manufacture. The Glist is built after manufacture by the Initiators' use of the REASSIGN BLOCK command and the Automatic Reallocate functions. The Dlist is an external list. It is supplied by the Initiator in the Data Out phase of the FORMAT UNIT command.
- Defect List Format specifies the format of the defect descriptor transferred to the Target when FmtData bit is set to one. The Target supports the following three defect descriptor formats for the FORMAT UNIT command:

Format 000b 100b 101b

Description Block format Bytes From Index format Physical Sector format

If the FmtData bit is set to zero, this field must also be zero. Otherwise the command will complete with a CHECK CONDITION with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.

- FFMT specifies the scope of the format command.

FFMT

Description

00b

Perform defect management and initialize media to the new format.

01b

Perform defect management but do not initialize the media. May result in any medium error on read before write.

Change block size only. May only be used on transitions of physically compatible size such as

10b

between 512 + end-to-end protection and 520. May result in end-to-end protection errors on

read before write.

11b

Reserved

Notes: It is recommended that the MODE SELECT command be issued prior to the FORMAT UNIT command to specify parameters that affect the formatting process.

HGST Hard Disk Drive Specification 72

The Block Length parameter of the Mode Select Parameter List's Block Descriptor is used during formatting and is saved following a successful format operation. If a MODE SELECT command has not been issued since the last reset or start-up (bring-up) sequence, then the Block Length from the previous format operation is used. Subsequent to receiving a FORMAT UNIT command, the Target responds to commands as follows:
- All commands except REQUEST SENSE and INQUIRY return Check Condition status, while the format operation is an active I/O process.
- When tagged queuing is enabled (DQue = 0), all commands except REQUEST SENSE and INQUIRY return Queue Full status, while the FORMAT UNIT command is a queued I/O process.
- When tagged queuing is disabled (DQue = 1), all commands except REQUEST SENSE and INQUIRY return Busy status, while the FORMAT UNIT command is a queued I/O process
- If a REQUEST SENSE command is received while a format operation is an active I/O process, the Target returns Good status. The sense key is set to Not ready and the additional sense code and qualifier is set to Format In Progress.
- If an INQUIRY command is received while a format operation is an active I/O process, the Target returns Good status and Inquiry data as requested.
The format operation must complete successfully for the Drive to be usable. If the command is interrupted by a reset, power down, or an unrecoverable error, the Drive enters a degraded mode of operation in which reading and writing are prohibited. To exit the degraded mode, another FORMAT UNIT command must be sent by the Initiator and completed successfully by the Target. The FORMAT UNIT command sets the Unit Attention Condition for all Initiators except the one that issued the FORMAT UNIT command.
HGST Hard Disk Drive Specification 73

Parameter List Header

Following is the format of the Parameter List Header sent during the data out phase when FmtData is set to one.

Byte
0 1

7 FOV

2 -3

4-n (n+1) - m

Bit

6

5

4

3

2

1

0

Reserved = 0

Protection Field Usage

DPRY DCRT STPF =1 IP Obsolete Immed Vendor-specific

(MSB) List Length(LSB)

Defect

Initialization Pattern Descriptor

Defect Descriptor

Table 59 Format of the Short Parameter List Header

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved = 0

Protection Field Usage

1

FOV DPRY DCRT STPF =1 IP Obsolete Immed Vendor-specific

2

Reserved

3

P_I_INFORMATION = 0

PROTECTION INTERVAL EXPONENT = 0

4

(MSB)

...

7

DEFECT LIST LENGTH

(LSB)

8-n

Initialization Pattern Descriptor

(n+1) - m

Defect Descriptor

Table 60 Format of the Long Parameter List Header
- Protection Field Usage: in combination with the format protection information (FMTPINFO) field in the CDB specifies whether or not the drive enables or disables the use of protection information:

FMTPINFO 00h 01h 10h 11h
11h

Protection Field Usage
000h
xxxh
000h 000h
001h

Description
The drive will be formatted to type 0 protection Check Condition status will be returned with the sense key set to Illegal Request and the additional sense code set to Invalid Field in the CDB. The drive will be formatted to type 1 protection The drive will be formatted to type 2 protection Type 3 protection is not supported - Check Condition status will be returned with the sense key set to Illegal Request and the additional sense code set to Invalid Field in the Parameter List

Table 61 Format of the Long Parameter List Header
All other combinations of FMTPINFO and Protection Field Usage will result in Check Condition status to be returned with the sense key set to Illegal Request and the additional sense code set to Invalid Field in the Parameter List.

HGST Hard Disk Drive Specification 74

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). See format of data below. When protection information is written during a FORMAT UNIT command, protection information shall be written with a default value of all 0xFF's. Following a successful format, the PROT_EN bit in the READ CAPACITY (16) parameter data will indicate that protection information is enabled and the P_TYPE field in the READ CAPACITY (16) parameter data will indicate the protection type.

Bit

Byte

7

6

5

4

3

2

1

0

0... n

User Data

n... n+1

Logical Block Guard

n+2... n+3

Logical Block Application Tag

n+4... n+7

Logical Block Reference Tag

Table 62 Data Format with Protection field
- The Logical Block Guard field contains a CRC that covers the preceding user data. This field is generated/checked per the SBC standard.
The Logical Block Application Tag field may be modified by the initiator if the ATO bit is set to zero in mode page 0x0A. If the ATO bit is set to one, then the initiator shall not modify the Logical Block Application Tag field. This field is generated/checked per the SBC standard.
- The Logical Block Reference Tag field is generated/checked depending on protection types. With Type 1 protection, the Logical Block Reference Tag in the first logical block of the data transfer shall contain the least significant four bytes of the LBA contained in the Logical Block Address field of the command. Subsequent blocks shall contain the previous logical block reference tag plus one. With Type 2 protection, the Logical Block Reference Tag in the first logical block of the data transfer shall contain the value in the Expected Initial Logical Block Reference Tag field of the command. Subsequent blocks shall contain the previous logical block reference tag plus one.
- FOV (Format Options Valid) bit set to zero indicates that the Target should use its default settings for the DPRY (0), DCRT (1), STPF (1), IP (0), and DSP (1) bits. These bits must all be set to zero in the Parameter List Header when FOV=0, or the command will be terminated with Check Condition status, sense key of Illegal Request, and additional sense code of Invalid Field in Parameter List. FOV=1 indicates that the values set in DPRY, DCRT, STPF, IP, and DSP will be defined as specified below.
- DPRY (Disable Primary) bit set to zero indicates that the Target does not use portions of the medium identified as defective in the primary defect Plist for Initiator addressable logical blocks. If the Target cannot locate the Plist or it cannot determine whether a Plist exists, the Target terminates the FORMAT UNIT command as described for STPF=1. A DPRY bit set to one indicates that the Target does not use the Plist to identify defective areas of the medium. The Plist is not deleted. DPRY must be set to 0 when DCRT is set to 0.
- DCRT (Disable Certification) bit set to zero indicates that the Target performs a medium certification operation and generates a Certification List (Clist), and adds the Clist to the Glist. DPRY must be set to 0 when DCRT is set to 0. A DCRT bit of one indicates that the Target does not generate a Clist or perform a certification process.
Note: Since the DCRT bit is part of the Data Out phase that follows the FORMAT command, the FCERT bit in Mode Page 0 is provided to control certification when the FORMAT command is issued with no Data Out phase. If a FORMAT command is issued with a Data Out phase then FCERT is ignored.
- STPF (Stop Format) bit must be set to one. If one or both of the following conditions occurs, the Target terminates the FORMAT UNIT command with Check Condition status. The sense key is set to Medium Error and the additional sense code is set to Defect List Not Found if the first condition occurred or to Defect List Error if the second condition occurred.
- The Target cannot locate a required Dlist nor determine that the list exists.

HGST Hard Disk Drive Specification 75

- The Target encounters an unrecoverable error while accessing a required Dlist. - IP (Initialization Pattern) bit set to zero specifies that an initialization pattern descriptor is not included and all
customer data will be initialized to zeroes. An IP bit of one specifies that an Initialization Pattern Descriptor is included in the FORMAT UNIT parameter list following the parameter list header.
Initialization Pattern

Bit

Byte

7

6

5

4

3

2

1

0

0

IP Modifier = 0

SI

Reserved = 0

1

Initialization Pattern Type = 0 or 1

2 - 3

Initialization Pattern Length (n-3)

4

Initialization Pattern

...

...

n

Initialization Pattern

Table 63 Initialization Pattern Descriptor

- IP Modifier must be set to 0, indicating that the drive will not modify the initialization pattern.
- SI (Security Initialize) bit set to 1 specifies that all customer data sectors, including those that have been previously reassigned, will be initialized. SI set to 0 specifies that only the current customer accessible sectors will be formatted.
- Initialization Pattern Type - Type of 0 will use a default initialization pattern. - Type of 1 specifies that the Initialization Pattern specified shall be repeated as required to fill each logical block.
- Initialization Pattern Length specifies the number of bytes that follow in the Initialization Pattern field, and must be less than or equal to the current block size, and non-zero. - If Initialization Pattern Type is 0 and the Initialization Pattern Length is not set to 0, Check Condition status will be returned, with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter List - If Initialization Pattern Type is 1 and the Initialization Pattern Length is set to 0, Check Condition status will be returned, with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter List.
- DSP (Disable Saving Parameters) bit when 0 indicates the target is to save all the current MODE SELECT savable parameters during the format operation. When the bit is 1, the target is not to save the current MODE SELECT savable parameters.
- Immed (Immediate) bit set to 0 requests that status be returned at the end of the format operation. An immediate bit set to 1 requests that status be returned immediately following CDB validation and transfer of data in the Data Out phase. If the format operation, with the immediate bit set to 1, terminates in error, DEFERRED ERROR SENSE data is generated.
- P_I_INFORMATION field shall be set to 0. For a type 1 protection information request, if the PROTECTION INTERVAL EXPONENT field is not set to 0, then the device server shall 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.
- For a type 2 protection or a type 3 protection format request, the protection interval exponent determines the length of user data to be sent before protection information is transferred (i.e., the protection information interval). The protection information interval is calculated as follows: protection information interval = logical block length ÷ 2(protection interval exponent) where: logical block length is the length in bytes of a logical block as specified in the mode parameter block descriptor protection interval exponent is the contents of the PROTECTION INTERVAL EXPONENT field.
- A protection interval exponent value of 3 is supported for 4096 byte logical blocks (512 bytes per protection information interval). A protection interval exponent value of 0 is supported for all supported logical block sizes. If these conditions are not met, then the device server shall terminate the command with CHECK

HGST Hard Disk Drive Specification 76

CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN PARAMETER LIST.
- Defect List Length field specifies the total length in bytes of the defect descriptors that follow (not including the Initialization Pattern Descriptor, if any). Up to 1024 defect descriptors are allowed. The Defect List Length must be equal to four times the number of defect descriptors for BLOCK format, or eight times the number of defect descriptors for BYTES FROM INDEX and PHYSICAL SECTOR formats. Otherwise the command is terminated with Check Condition status with the sense key set to Illegal Request and the additional sense code set to Invalid Field in Parameter List.

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.

Block Format - 000b

Format of the Dlist sent during the data out phase when Dlist Format is Block format (000b) and FmtData is set to

one.

Byte

7

6

5

Bit

4

3

2

1

0

(MSB)

0 - 3

Defective Logical Block Address

(LSB)

4n 4n+1 4n+2 4n+3

(MSB)

Defective Logical Block Address n

(LSB)

Table 64 Defect Descriptor - Block Format (for n + 1 defects)

The Block format of the Dlist is the LBA of each defective sector.

Note: If a Defective LBA entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and DPRY = 1, then the entry is not added to the Glist.

HGST Hard Disk Drive Specification 77

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.

Byte

7

6

0 - 2

(MSB)

3 4 - 7

(MSB)

8n 8n + 1 8n + 2 8n + 3 8n + 4 8n + 5 8n + 6 8n + 7

(MSB) (MSB)

Bit

5

4

3

2

Cylinder Number of Defect

Head Number of Defect Defect Bytes from Index

Cylinder Number of Defect n Head Number of Defect n Defect (n) Bytes from Index

1

0

(LSB)

(LSB) (LSB)

(LSB)

Table 65 Defect Descriptor - Bytes from Index Format (for n = 1 defects)

Each defect descriptor for the Bytes from Index format specifies that the sector containing this byte be marked defective. The defect descriptor is comprised of the cylinder number of the defect, the head number of the defect, and the number of the defect byte relative to index.

Note: If a Byte from Index entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and DPRY = 1, then the entry is not added to the Glist.

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.

Byte

7

6

0

(MSB)

1

2

3

4 5 6 7 8n 8n + 1 8n + 2

(MSB) (MSB)

8n + 3

8n + 4 8n + 5 8n + 6 8n + 7

(MSB)

Bit

5

4

3

2

Cylinder Number of Defect

Head Number of Defect

Defect Sector Number

Cylinder Number of Defect n Head Number of Defect n Defect (n) Sector Number

Table 66 Defect Descriptor - Physical Sector Format (for n + 1 defects)

1

0

(LSB)

(LSB) (LSB)

(LSB)

HGST Hard Disk Drive Specification 78

Each defect descriptor for the Physical Sector format specifies a defective sector. The defect descriptor is comprised of the cylinder number of the defect, the head number of the defect, and the defect's sector number. Note: If a Physical Sector entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and DPRY = 1, then the entry is not added to the Glist.
HGST Hard Disk Drive Specification 79

INQUIRY (12)

Bit

Byte

7

6

5

4

3

2

1

0

0

Operation Code = 12h

1

Reserved = 0

CmdDt =0 EVPD

2

Page Code

3 - 4

Allocation Length

5

VU = 0

Reserved = 0

FLAG

LINK

Table 67 INQUIRY (12)
The INQUIRY command requests the parameters of the Target to be sent to the Initiator. An EVPD bit of 1 specifies that the target return the vital product data page identified by the Page Code field in the CDB the available VPD pages are defined in the addendum provided for each different drive model in the section entitled Inquiry Data Format. The Page Code specifies which page of vital product data information the drive shall return.

EVPD

PAGE CODE

Description

0

0

The Target returns the standard INQUIRY data.

0

Non Zero

The drive returns Check Condition status with the sense key of Illegal Request and the additional sense code of Invalid Field in CDB.

1

Non Zero The drive returns the vital product data of page code requested.

Table 68 Page Code descriptions
Allocation Length specifies the number of bytes that the Initiator has allocated for INQUIRY data to be returned. An allocation length of zero implies that no data is to be returned. The Target will terminate the DATA IN phase when all available INQUIRY data has been transferred or when allocation length bytes have been transferred, whichever is less.
Note: If an INQUIRY command is received from an Initiator with a pending unit attention condition (before the target reports Check Condition status), the Target processes the INQUIRY command. The unit attention condition is not cleared by this action.
Note: The INQUIRY command is a Priority command and is not queued.
Note: The inquiry data is set at the time of manufacture and will not change, with the following exceptions:
- Product Revision Level (EVPD=0) can be changed when microcode is downloaded with the Write Buffer command.
- The information returned for EVPD=1, Page Code = 3 is not fixed.
Note: The inquiry data returned when media is not available will not be complete.
Byte 0 of the returned data on an INQUIRY command is the same no matter which page(s) is (are) returned. This description is to be used for all the following page definitions. The Peripheral Qualifier field of zero (0) indicates that the peripheral device is currently connected to this logical unit. A Peripheral Device Type field of zero (0) indicates that this device is a Direct Access Storage Device (DASD).

HGST Hard Disk Drive Specification 80

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.
Inquiry Data Format - EVPD = 0, Page Code = 0

Byte

7

6

Bit

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

RMB = 0

Reserved=0

2

Version = 6

3

Obsolete Obsolete Norm ACA=0 HiSup = 1

Response Data Format = 2

4

Additional Length = 159 (9Fh)

5

SCCS=0 ACC=0

TPGS=00b

3PC=0

Reserved = 0

Protect=1

6

Obsolete EncSer = 0

Port

MultiP=1

Obsolete

RSVD = 0

7

Obsolete Obsolete RSVD = 0 RSVD = 0 Obsolete Obsolete CmdQue= 1 RSVD = 0

8-15

Vendor ID = "HGST " (ASCII)

16-31

Product ID (ASCII)

32-35

Product Revision Level (ASCII)

36-43

Unit Serial Number (ASCII)

44-95

Reserved = 0

96-145

Copyright Notice (ASCII)

146-163

Reserved=0

Table 69 Inquiry Data- EVPD = 0
- Qualifier is set to 0 to indicate that the LUN specified is currently supported. Qualifier is set to 011b when the LUN specified is not present1
- Peripheral Device Type is set to 0 to indicate that the device is a Direct-Access Peripheral Device. - Removal Media Bit (RMB) is always set to 0 to indicate no removal media exists. - Version indicates the level of the ANSI standard that the product supports. The drive supports ANSI SPC-4. - NormACA (Normal ACA) field of 0 indicates the device server does not support setting the NACA bit to 1 in the
Control Byte of the CDB as defined in the SAM. - HiSup bit of 1 indicates that the drive uses the hierarchical addressing model to assign LUNs to logical units. - Response Data Format is set to 2 to indicate that the INQUIRY Data Format as specified in the ANSI SCSI
version 2 is supported by the Target. - Additional Length indicates the number of bytes of INQUIRY information that follows.

1If an INVALID LUN is specified, a Check Condition status will be returned for all commands except INQUIRY and REQUEST SENSE.

HGST Hard Disk Drive Specification 81

- SCCS bit of 0 indicates that the device does not contain an embedded storage array controller component. - ACC bit of 0 indicates that no access controls coordinator may be addressed through this logical unit. - TGPS field of 0 indicates that the device does not support asymmetric logical unit access. - 3PC bit of 0 indicates that the device does not support third-party copy commands. - Protect bit of 1 indicates that the drive supports protection information - EncSer (Enclosure Services) bit of 0 indicates that the Target does not contain an embedded enclosure
services component. - Port bit of 0 indicates that the drive received the Inquiry command on port A, while a Port bit of 1 indicates that
the drive received the Inquiry command on port B. - MultiP (MultiPort) bit of 1 indicates that the Target has multiple ports and implements multi-port requirements. - CmdQue is set to 1 to indicate that the drive supports command queuing. - Vendor ID is HGST padded with ASCII blanks. - Product ID is specified - Product Revision Level indicates the level of microcode. - Unit Serial Number contains the drive serial number.
HGST Hard Disk Drive Specification 82

Inquiry Data Format - EVPD = 1 - Page Code = 00h

Byte
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Bit

7

6

5

4

3

2

1

0

Qualifier = 0

Peripheral Device Type = 0

Page Code = 00h

Reserved = 0

Page Length = 0Fh

Supported Page Code - 00h

Supported Page Code - 03h

Supported Page Code - 80h

Supported Page Code - 83h

Supported Page Code = 86h

Supported Page Code = 87h

Supported Page Code = 88h

Supported Page Code ­ 8Ah

Supported Page Code ­ 90h

Supported Page Code ­ 91h

Supported Page Code ­ B0h

Supported Page Code ­ B1h

Supported Page Code ­ B2h

Supported Page Code ­ D1h

Supported Page Code ­ D2h

Table 70 Inquiry Data - EVPD = 1 (Page Code = 00h)

- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 to indicate that the device is Direct Access. - Page Code is set to 0, and this field contains the same value as in the page code field of the INQUIRY
command descriptor block. - Page length specifies the length of the following page data. - Supported Page Code field contains the Page Codes supported by the Target. The list is in ascending order.

HGST Hard Disk Drive Specification 83

Inquiry Data Format - EVPD = 1, Page Code - 03h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = 03h

2

Reserved = 0

3

Page Length = 188 (BCh)

4

ASCII Fields Length = 00h

5-7

Reserved = 0

8-23

Reserved = 0

24-35

ASCII uCode Identifier

36-39

ASCII Servo P/N

40-41

Major Version

42-43

Minor Version

44-47

User Count

48-51

Build Number

52-83

Build Date String

84-91

Product ID

92-99

Interface ID

100-107

Code Type

108-119

User Name

120-135

Machine Name

136-167

Directory Name

168-171

Operating State

172-175

Functional Mode

176-179

Degraded Reason

180-183

Broken Reason

184-187

Code Mode

188-191

Flash Code Revision Level

Table 71 Inquiry Data - EVPD = 1 (Page Code = 03h)

- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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). If the
allocation length of the CDB is too small to transfer all the data, the Page Length field is not adjusted to reflect the truncation. - ASCII uCode Identifier contains the drive's microcode identifier. The field is alphanumeric (ASCII), left aligned, and the unused bytes are ASCII spaces (20h). - ASCII Servo P/N contains the part number of the Servo microcode installed on the drive. This field is hex numeric ASCII (i.e., the characters will be in the set 0...9, A...F). - Major Version and Minor Version are version numbers of the code loaded on the drive. - User Count is the number of times the code has been built since the master build. - Build Number is the master build version number. - Build Date String is the date the code on the drive was built, in an extended string format. - Product ID is the name of the product this code is for. - Interface ID is the interface type and serial interface speed (e.g. SAS 6Gbps or FCAL 4Gbps) of the code. - Code Type is the intended use of the code. (e.g. local, released, test)

HGST Hard Disk Drive Specification 84

- User Name is the username of the person who built this version of the code. - Machine Name is the workstation on which this version of the code was built. - Directory Name is the last 32 characters of the directory from where this code was built. - Operating State is the drive operating state. The least significant bit contains the following:

0 = OM_BROKEN 1 = OM_DEGRADED 2 = OM_INACCESSIBL 3 = OM_STARTING 4 = OM_SPINNING 5 = OM_NORMAL 6 = OM_POWERSAVE 7 = OM_STOPPED 8 = OM_NOTIFY 10 = OM_WAKEUP
11 = OM_NOTIFY_WAKEUP

We have detected a hardware failure. We have a soft failure; i.e., incomplete format. Motor is still spinning. Drive is good but motor is stopped. Motor is starting. Motor is started but reserved area is not loaded yet. Drive is spinning and ready to read/write. Drive is ready but has entered power save mode. Drive has come ready but now has been stopped. Drive is good but NOTIFY has not arrived (SAS) Similar to OM_STARTING, but LUN BECOMING READY during spinup is not reported Similar to OM_NOTIFY, but next transition is to OM_WAKEUP

- Functional Mode is the drive functional mode. The least significant byte (0x0000000n) contains the following:

- Degraded Reason (UECType) is why the file is in a degraded mode; i.e., how to exit this mode.

0 = OM_NORMAL_MODE Not in special or recovery mode.

1 = OM_SPECIAL_CMD

Special command mode on.

- Broken Reason (UECType) is why the drive believes the hardware is broken.

- Code Mode is the type of code the drive is running. The least significant bit contains the following:

0 = OM_FLASH

Drive is running flash code

1 = OM_FLASH_OVERLAY Drive is running flash overlay code

2 = OM_DISK

Drive is running code that has been loaded from disk

3 = OM_TRANSIENT

Drive is running code that has been downloaded but not saved

- Flash Code Revision Level is the revision level of the code in flash.

Inquiry Data Format - EVPD = 1, Page Code - 80h

Byte
0 1 2 3

Bit

7

6

5

4

3

2

1

0

Qualifier = 0

Peripheral Device Type = 0

Page Code = 80h

Reserved = 0

Page Length = 16 (10h)

Table 72 Inquiry Data - EVPD = 1 (Page Code = 80h)
- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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 16, and this field specifies the length of the following page data. - Serial Number gives the drive serial number, right aligned.

HGST Hard Disk Drive Specification 85

Inquiry Data - EVPD = 1 (Page Code = 83h)

Byte
0 1 2 3 4 5 6 7
8-15

Bit

7

6

5

4

3

2

1

Qualifier = 0

Peripheral Device Type = 0

Page Code = 83h

Reserved = 0 Page Length = 72 (48h)

Protocol Identifier = 0h

Code Set = 1

PIV=0 RSVD

Association=0 Reserved = 0

Identifier Type = 3

Identifier Length = 8

(MSB)

LUN (World Wide ID)

16

Protocol Identifier = 6h

Code Set = 1

17 PIV=1 RSVD Association = 1

Identifier Type = 3

18

Reserved = 0

19

Identifier Length = 8

(MSB) 20-27

Target Port Identifier (World Wide ID)

28 29 30 31
32-35

Protocol Identifier = 6h

Code Set = 1

PIV=1 RSVD Association = 1

Identifier Type = 4

Reserved = 0

Identifier Length = 4

(MSB)

Relative Port Identifier

36

Protocol Identifier = 6h

Code Set = 1

37 PIV=1 RSVD Association = 2

Identifier Type = 3

38

Reserved = 0

39

Identifier Length = 8

(MSB) 40-47

Target Device Name Identifier (World Wide ID)

48 49 50 51 52-55
56-71

Protocol Identifier = 0h

Code Set = 3

PIV=0 RSVD

Association=2 Reserved = 0

Identifier Type = 8

Identifier Length =24 (18h)

"naa" (ASCII)

(MSB)

Target Device Name Identifier (World Wide ID) in ASCII

72-75

Reserved = 0

Table 73 Inquiry Data Format - EVPD = 1, (Page Code - 83h)

0
(LSB) (LSB) (LSB) (LSB) (LSB)

HGST Hard Disk Drive Specification 86

- Protocol Identifier is valid only when PIV=1. Protocol Identifier = 0 indicates Fibre Channel devices. Protocol Identifier = 6 specifies SAS devices
- Code Set specifies the data type for the identifier field. Code Set = 1 indicates binary data, Code Set = 3 indicates ASCII.
- PIV (Protocol Identifier Valid) set to 0 indicates that the Protocol Identifier field should be ignored. PIV set to 1 indicates that the Protocol Identifier field contains a valid value.
- Association specifies the entity with which the Identifier field is associated: 0h for LUN, 1h for Target or Relative Port, or 2h for Target Device.
- Identifier Type specifies the format and assignment authority for the identifier: 3h indicates NAA format of the WWID for LUN, Target Port and Target Device; 4h indicates Relative Port; 8h indicates SCSI name string.
- Identifier fields contain the actual Identifier Descriptor: - The LUN, Target Port and Target Device Name Identifiers are defined in the NAA IEE WWID format where: - Worldwide ID is a 64-bit unique identification for each drive. The format is:5000CCAh xxxh yyb n where: - xxx is the 12-bit block assignment defined for each model and manufacturing site - n is the 22-bit drive unique serial number - yy is the 2-bit port/node ID select - The Relative Port Identifier indicates the port which received the Inquiry command:0000 0001h for the Primary Port, or 0000 0002h for the Secondary Port.
HGST Hard Disk Drive Specification 87

Inquiry Data Format - EVPD = 1, Page Code - 86h

Bit

Byte

7

6

5

4

3

2

1

0

Peripheral Qualifier

Peripheral Device Type

1

Page Code = 86h

2-3 (MSB)

Page Length (003Ch)

4

Activate Microcode

SPT

GRD_CHK APP_CHK

5

Reserved

UASK_SUP Group_Sup Prior_Sup HEADSUP ORDSUP

0
(LSB) REF_CHK SIMPSUP

6

Reserved

WU_SUP CRD_SUP NV_SUP V_SUP

7

Reserved

P_I_I_SUP

Reserved

LUICLR

8

Reserved

R_SUP

Reserved

CBCS

9

Reserved

Multi I_T Nexus Microcode Download

10-11

(MSB) Extended Self-Test Completion Minutes(LSB)

12 POA_SUP HRA_SUP VSA_SUP

Reserved

13

Maximum Supported Sense Data Length

14-63

Reserved

Table 74 Inquiry Data Format - EVPD = 1, (Page Code - 86h)

- Activate Microcode field is set to 01b to indicate that the device server 1) activates the microcode before completion of the final command in the WRITE BUFFER sequence; and 2) establishes a unit attention condition for the initiator port associated with every I_T nexus, except the I_T nexus on which the WRITE BUFFER command was received, with the additional sense code set to MICROCODE HAS BEEN CHANGED.
- SPT (Supported Protection Type) field is set to 001b to indicate that the drive supports type 1 and type 2 protection.
- GRD_CHK (Guard Check) is set to 1 to indicate that the drive checks the Logical Block Guard Tag field in the protection information, if any.
- APP_CHK (Application Tag Check) bit is set to 1 to indicate that the drive checks the Logical Block Application Tag field in the protection information, if any.
- REF_CHK (Reference Tag Check) bit is set to 1 to indicate that the drive checks the Logical Block Reference Tag field in the protection information, if any.
- UASK_SUP (Unit Attention Condition Sense Key Specific Data Supported) bit is set to 0 to indicate that the device server does not return sense-key specific data for the UNIT ATTENTION sense key.
- GROUP_SUP (Group Supported) bit is set to 0 to indicate that the grouping function is not supported. - PRIOR_SUP (Priority Supported) bit is set to 0 to indicate that task priority is not supported. - HEADSUP (Head of Queue Supported), ORDSUP (Ordered Supported), and SIMPSUP (Simple Supported)
are set to 1 to indicate support for Head of Queue, Ordered and Simple task attributes. - WU_SUP is set to 1 to indicate that setting the WR_UNCOR bit to 1 in the Write Long command is supported. - CRD_SUP is set to 1 to indicate that setting the COR_DIS bit to 1 in the Write Long command is supported. - NV_SUP (Non-volatile Supported) is set to 0 to indicate that non-volatile cache features are not supported. - V_SUP (Volatile Supported) is set to 1 to indicated support of a volatile cache. - P_I_I_SUP (Protection Information Interval Supported) bit is set to 0 to indicate that the logical unit does not
support protection information intervals. - R_SUP (Referrals Supported) bit is set to 0 to indicate that the device server does not support referrals. - POA_SUP (Power On Activation Supported) bit is set to 1 to indicate that the device server supports a WRITE

HGST Hard Disk Drive Specification 88

BUFFER command with the MODE field set to 0Dh and the PO_ACT bit set to 1. - HRA_SUP (Hard Reset Activation Supported) bit is set to 0 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 1. - VRA_SUP (Vendor Specific Activation Supported) bit is set to 0 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 1. - Maximum Supported Sense Data Length field indicates the maximum length in bytes of sense data that the
device server is capable of returning in the same I_T_L_Q nexus transaction as the status.
Inquiry Data Format - EVPD = 1, Page Code - 87h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = 87h

2-3

Page Length = 0004h

4

Reserved=0

Policy Page Code = 3Fh

5

Policy Subpage Code = FFh

6

MILUS=1

Reserved = 0

Mode PagePolicy = 0

7

Reserved = 0

Table 75 Inquiry Data Format - EVPD = 1, (Page Code - 87h)
- Policy Page Code set to 3Fh and Policy Subpage Code set to FFh indicate that the descriptor applies to all mode pages and subpages
- MILUS (Multiple Logical Units Share) set to 1 indicates the policy is shared by multiple logical units. - Mode Page Policy set to 00b indicates that all mode pages and subpages are shared.

HGST Hard Disk Drive Specification 89

Inquiry Data Format - EVPD = 1, Page Code - 88h

Byte
0 1 2-3 4-5 6-7 8-9 10-11 12-13 14-15 16 17 18 19
20-27

Bit

7

6

5

4

3

2

1

Qualifier = 0

Peripheral Device Type = 0

Page Code = 88h

Page Length = 48 (0030h)

Reserved=0

Primary Relative Port = 0001h

Reserved = 0

Initiator Port Transport ID Length = 0

Reserved = 0

Primary Target Port Descriptors Length = 0Ch

Protocol Identifier

Code Set = 1

PIV=1 RSVD Association = 1

Identifier Type = 3

Reserved = 0

Identifier Length = 8

(MSB)

Primary Target Port Identifier (World Wide ID)

28-29 30-31 32-33 34-35 36-37 38-39
40 41 42 43
44-51

Reserved = 0

Secondary Relative Port = 0002h

Reserved = 0

Initiator Port Transport ID Length = 0

Reserved = 0

Secondary Target Port Descriptors Length = 0Ch

Protocol Identifier

Code Set = 1

PIV=1 RSVD

Association = 1

Identifier Type = 3

Reserved = 0

Identifier Length = 8

(MSB)

Secondary Target Port Identifier (World Wide ID)

0 (LSB) (LSB)

Table 76 Inquiry Data Format - EVPD = 1, (Page Code - 88h)
- Protocol Identifier is valid only when PIV=1.Protocol Identifier = 0 indicates Fibre Channel devices. Protocol Identifier = 6 indicates SAS devices
- Code Set specifies the data type for the identifier field. Code Set = 1 indicates binary data - PIV (Protocol Identifier Valid) set to 1 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. - Identifier fields contain the actual Identifier Descriptor.
- The Target Port Identifiers are defined in the NAA IEE WWID format where:
World Wide ID is a 64-bit unique identification for each drive. The format is: 5000CCAh
xxxh n yyb where xxx is the 12-bit block assignment defined for each model and manufacturing site, n is the 22bit drive unique serial number, and yy is the 2-bit port/node ID

HGST Hard Disk Drive Specification 90

Inquiry Data Format - EVPD = 1, Page Code - 8Ah

Byte
0 1 2-3 4 5 6-7 8-9 10-11 12-13 14-15 16-17

Bit

7

6

5

4

3

2

1

0

Qualifier = 0

Peripheral Device Type = 0

Page Code = 8Ah

Page Length = 14 (000Eh)

Reserved=0

STANDBY_Y STANDBY_Z

Reserved=0

IDLE_C

IDLE_B

IDLE_A

Stopped Condition Recovery Time

Standby_Z Condition Recovery Time

Standby_Y Condition Recovery Time

Idle_A Condition Recovery Time

Idle_B Condition Recovery Time

Idle_C Condition Recovery Time

Table 77 Inquiry Data Format - EVPD = 1, (Page Code - 8Ah)

- Qualifier field is set to 0 to indicate that the LUN specified in the Command Block is currently supported.
- Peripheral Device Type is set to 0 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 14, and this field specifies the length of the following page data.
- If set to 1, a power condition support bit (STANDBY_Y, STANDBY_Z, IDLE_C, IDLE_B, IDLE_A) indicates that the associated power condition may be entered with START STOP UNIT command and the associated power condition may be entered with a power condition timer if the timer is supported and enabled.
- The recovery time fields indicate the time, in one millisecond increments, that the logical unit takes to transition from the associated power condition to the active power condition. This time does not include the processing time for the command that caused this transition to occur. A value of 0 indicates that the recovery time is not specified. A value of FFFFh indicates that the recovery time is more than 65.534 seconds.

HGST Hard Disk Drive Specification 91

Inquiry Data - EVPD = 1, Page Code - 90h

Bit

Byte

7

6

5

4

3

2

1

0

0

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

1

Page Code = 90h

Table 78 Inquiry Data - EVPD = 1 (Page Code = 90h)

- Qualifier field is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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. - Protocol-specific logical unit information descriptor 0 field is defined in Table 79 - Protocol-specific logical unit information descriptor 1 field is defined in Table 79

Bit

Byte

7

6

5

4

3

2

1

0

0-1

Relative Port Identifier

2

Reserved

Protocol Identifier = 6h

3-5

Reserved

6-7 8 9-11

Descriptor Length (0004h) Reserved
Reserved

TLR CONTROL SUPPORTED = 0h

Table 79 Protocol-specific logical unit information descriptor

- Relative Port Identifier is set to 1 for Port A (Primary Port) or 2 for Port B (Secondary Port). - Protocol Identifier is set to 6 to specify that this is a SAS SSP Descriptor. - TLR Control Supported field specifies support of the TLR CONTROL field in the SAS SSP frame header. This
field is set to 0 to indicate that the drive does not support Transport Layer Retries

HGST Hard Disk Drive Specification 92

Inquiry Data - EVPD = 1, Page Code - 91h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = 91h

2-3

Page Length = 24 (0018h)

4-15

Port Information Descriptor 0

16-27

Port Information Descriptor 1

Table 80 Protocol Specific Port Information VPD page to SAS SSP
- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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.
Port Information Descriptor 0 is defined in Table 81 Port Information Descriptor 1 is defined in Table 81

Byte 7
0-1 2 3 4-5 6-7 8-11

Bit

6

5

4

3

2

1

0

Relative Port Identifier

Reserved

Protocol Identifier (6h)

Reserved

PWR_D_S

Reserved

Descriptor Length (0004h)

SAS PHY Information Descriptor 0

Table 81 Port Information Descriptor for SAS SSP
- Relative Port Identifier is set to 1 for Port A (Primary Port) or 2 for Port B (Secondary Port). - Protocol Identifier is set to 6 to specify that this is a SAS SSP Descriptor. - PWR_D_S, Power Disable Supported, is set to 1 to specify that the POWER DISABLE signal is supported. - SAS PHY Information Descriptor 0 is defined in Table 82 SAS PHY Information Descriptor for SAS SSP

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

1

PHY Identifier

3

Reserved

SSP Persistent Capable

Table 82 SAS PHY Information Descriptor for SAS SSP

- PHY Identifier is set to 0 for Port A (Primary Port) or 1 for Port B (Secondary Port). - SSP Persistent Capable is set to 0 indicates that the PHY does not support persistent connections

HGST Hard Disk Drive Specification 93

Inquiry Data Format - EVPD = 1, Page Code - B0h

Byte 7

Bit

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = B0h

2-3

Page Length = 60 (003Ch)

4

Reserved

WSNZ=0

5

Maximum Compare and Write Length = 0

6-7

Optimal Transfer Length Granularity = 0

8-11

Maximum Transfer Length = 0

12-15

Optimal Transfer Length = 0

16-19 20-23

Maximum Prefetch XDRead XDWrite Transfer Length = 0 Maximum Unmap LBA Count = 0

24-27

Maximum Unmap Block Descriptor Count = 0

28-31

Optimal Unmap Granularity = 0

32-35 UGAVALID=0

Unmap Granularity Alignment = 0

36-43

Maximum Write Same Length = 0

44-63

Reserved

Table 83 Inquiry Data - EVPD = 1 (Page Code = B0h)
- Qualifier: set to 0 to indicate that the LUN specified in the Command Block is currently supported.
- Peripheral Device Type: set to 0 to indicate that the device is Direct Access.
- Page Code: set to the value of the page code field in the CDB.
- Page Length: This field is set to 60 (3Ch), and specifies the length of the following page data.
- WSNZ - Write Same No Zero: set to 0 which indicates the device server supports a value of 0 in the NUMBER OF LOGICAL BLOCKS field in the WRITE SAME command CDB.
- Maximum Compare and Write Length: set to 0 which indicates the device server does not support the COMPARE AND WRITE command.
- Optimal Transfer Length Granularity: set to 0 to indicate that the device server does not report optimal transfer length granularity.
- Maximum Transfer Length: set to 0 which indicates there is no reported limit on the maximum transfer length in logical blocks that the device server accepts for a single request using any of the following supported media access commands: PREFETCH, READ, VERIFY, WRITE, WRITE AND VERIFY.
- Optimal Transfer Length: set to 0 which indicates there is no reported value for the optimal transfer length in logical blocks for any of the following supported media access commands: PREFETCH, READ, VERIFY, WRITE, WRITE AND VERIFY.
- Maximum Prefetch XDRead XDWrite Transfer Length: indicates the maximum transfer length in logical blocks that the device server accepts for a single PRE-FETCH command. It is set to 0 to be less than or equal to the Maximum Transfer Length (above).
- Maximum Unmap LBA Count: set to 0000_0000h to indicate that the device server does not implement the UNMAP command.
- Maximum Unmap Block Descriptor Count: set to 0000_0000h to indicate that the device server does not

HGST Hard Disk Drive Specification 94

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 1 indicates that the UNMAP GRANULARITY
ALIGNMENT field is not valid. - Unmap Granularity Alignment: set to 0 and is not valid. - Maximum Write Same Length: set to 0 which indicates that there is no reported limit on the number of logical
blocks that may be requested for a single WRITE SAME command.
Inquiry Data Format - EVPD = 1, Page Code - B1h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = B1h

2-3

Page Length = 60 (003Ch)

4-5

Medium Rotation Rate 7200 (1C20h)

6

Reserved

7

WABEREQ

WACEREQ

Nominal Form Factor = 2h

8-63

Reserved

Table 84 Inquiry Data - EVPD = 1 (Page Code = B1h)
- Qualifier field is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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 60, and this field specifies the length of the following page data. - Medium Rotation Rate field is set to 7200. - Nominal Form Factor field is set to 2h. - WACEREQ If Crypto Erase is supported then set WACEREQ to 01b indicating.

HGST Hard Disk Drive Specification 95

Inquiry Data Format - EVPD = 1, Page Code - B2h

Byte

7

6

Bit

5

4 3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = B2h

2-3

Page Length = 4 (0004h)

4

Threshold Exponent = 0

5

LBPU=0 LBPWS= 0 LBPWS10=0 Reserved LBPRZ=0 ANC_SUP=0 DP=0

6

Reserved

Provisioning Type = 0

7

Reserved

Table 85 Inquiry Data - EVPD = 1 (Page Code = B2h)
- Threshold Exponent: set to 0 which indicates that the logical unit does not support logical block provisioning thresholds
- LBPU: set to 0 to indicate that the device does not support the UNMAP command. - LBPWS: set to 0 to indicate that the device does not support the WRITE SAME(16) command to unmap LBAs. - LBPWS10: set to 0 to indicate that the device does not support the WRITE SAME(10) command to unmap
LBAs. - LBPRZ: set to 0 to indicate that, for an unmapped LBA specified by a read operation, the device server may
send user data with all bits set to any value to the Data-In Buffer - ANC_SUP: set to 0 to indicate that the device does not support anchored LBAs. - DP: set to 0 to indicate no Provisioning Group Descriptor is present - Provisioning Type: set to 0 to indicate the logical unit is fully provisioned
Inquiry Data Format - EVPD = 1, Page Code - D1h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = D1h

2

Reserved = 0

3

Page Length = 80 (50h)

4-19

ASCII Media Disk Definition

20-35

ASCII Motor Serial Number

36-51

ASCII Flex Assembly Serial Number

52-67

ASCII Actuator Serial Number

68-83

ASCII Device Enclosure Serial Number

Table 86 Inquiry Data - EVPD = 1 (Page Code = D1h)

- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 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 80, and this field specifies the length of the following page data.
Note: If the media is not available, bytes 0 through 3 are valid. All the other fields are ASCII blanks (20h). Note: All ASCII fields are alphanumeric, left aligned, and padded on the right with ASCII blanks (20h).

HGST Hard Disk Drive Specification 96

Inquiry Data Format - EVPD = 1, Page Code - D2h

Bit

Byte

7

6

5

4

3

2

1

0

0

Qualifier = 0

Peripheral Device Type = 0

1

Page Code = D2h

2

Reserved = 0

3

Page Length = 52 (34h)

4

HDC Version Length = 16 (10h)

5 - 20

ASCII HDC Version

21

Card Serial Number Length = 16 (10h)

22 - 37

ASCII Card Serial Number

38

Card Assembly Part Number Length = 16 (10h)

Table 87 Inquiry Data - EVPD = 1 (Page Code = D2h)

- Qualifier is set to 0 to indicate that the LUN specified in the Command Block is currently supported. - Peripheral Device Type is set to 0 to indicate that the device is Direct Access. - Page Code is set to the value of the page code field in the CDB. - Page Length is set to 52, and this field specifies the length of the following page data.
Note: If the media is not available, bytes 0 through 3 are valid. All the other fields are ASCII blanks (20h). Note: All ASCII fields are alphanumeric, left aligned, and padded on the right with ASCII blanks (20h).

HGST Hard Disk Drive Specification 97

LOG SELECT (4C)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 4Ch

1

Reserved = 0

Reserved = 0

PCR SP

2

PC

Page Code

3

SubPage Code = 0

4-6

Reserved = 0

7 (MSB) 8

Parameter List Length = 0

(LSB)

9

Reserved = 0

FLAG LINK

Table 88 Log Select (4C)
The LOG SELECT command provides a means for the Initiator to clear statistical information maintained by the drive and reported via the LOG SENSE command.
- PCR The Parameter Code Reset determines whether the Log Sense parameters will be cleared and unit attention posted for all other Initiators. A value of 1 indicates that the parameters be cleared, while a value of 0 (except when PC = 11b) indicates that the parameters not be cleared. Parameter list length must be 0 when PCR is 1.The PC field is ignored for list parameters, i.e. when the Format and Linking (F&L) field contains 01b or 11b.
- SP The Save Parameters bit value of 0 indicates that the page parameters not be saved. A value of 1 indicates that the page parameters that are savable be saved after they have been changed. SP bit MUST be 1 if parameter list length is greater than 0. Otherwise it will result in a Check Condition status being returned. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB.
- PC The Page Control field defines the type of parameters to be selected. The PC field set to 11b (and PCR is then a don't care) indicates that the Default Cumulative values are set to their default values of 0. If the PC field is set to 01b and PCR is set to 1, the Current Cumulative values are also set to their default values of 0.
Parameter List Length MUST be 0 when PC = 11b. Otherwise the command is terminated and a Check Condition status is returned. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB.
- Page Code field identifies which page is being selected. This field must be set to the values indicated in Page 0. If the Page Code value is invalid a Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
· If page code field is set to 0, then the selection applies to all log parameters in all valid log pages.
· If page code field is set to a non zero, then the selection applies to all log parameters specified by this field.
- SubPage Code This field specifies the subpage to select. This field is not supported and must be set to 0.
- Parameter List Length The Parameter List Length field specifies the length in bytes of the parameter list that shall be located in the DATA OUT buffer. A parameter list length 0 indicates that no pages shall be transferred.
· If the PARAMETER LIST LENGTH field is set to 0, then the PCR bit, the SP bit, and the PC fields apply to the page (pages) addressed by the page code field.
· If the PARAMETER LIST LENGTH field is set to non zero, and the if PAGE CODE field is non-zero or the SUBPAGE CODE field is non-zero, then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.

HGST Hard Disk Drive Specification 98

Note: A specified length greater than 0x00FF will result in a Check Condition status being returned. A length that results in log data being truncated will generate a Check Condition status.
Note: For page 0Fh, the maximum parameter list length supported is 4004h (4 bytes for the header and 100h bytes for each of the 40h parameters that are supported). The Parameter List Length must be an integral of the number of parameters plus the 4 byte header. (Ex: Parameter length =104h for one parameter, 204h for 2 parameters,... 4004h for all 40h parameters).
The drive allows updates to the current cumulative values only. A value of 0 is acceptable and is not considered an error. The drive updates only pages 0Eh, the Start/Stop Cycle page and 0Fh, the Application Client page. For other pages the parameters are ignored. If the data out buffer contains multiple pages then the application client should send the pages in ascending order. If the data out buffer contains multiple log parameters within a page, all log parameters within the page should be sent and they should be sent in ascending order by parameter code value. The drive shall return Check Condition status if the application client sends pages out of order, parameter codes out of order or missing parameter code. The sense key shall be set to Illegal Request and additional sense code set to Invalid Field in Parameter List. If one or more fields of the CDB are not set correctly the command will be terminated with a Check Condition status. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB. To indicate that parameters have changed, the Target generates a unit attention condition for all Initiators except the one that issued the LOG SELECT command. The following list contains all individual page parameters (counters) that are set to their default value of 0 by the LOG SELECT command (when PCR=1).
- Page 02h parameters: (Counters for write errors) - Write errors recovered without delay - Write errors recovered with possible delays - LBAs with write fault error - Reserved=0 - Total errors recovered - Number of times recovery invoked - Total write byte count - LBAs with hard error
- Page 03h parameters: (Counters for read errors) - Read errors recovered without delay - Read errors recovered with possible delays - LBAs with LDPC detected error - Reserved=0 - Total errors recovered - Number of times recovery invoked - Total read byte count - LBAs with hard error.
- Page 05h parameters: (Counters for Verify Errors) - Errors recovered without delay - Errors recovered with possible delays - LBAs with LDPC detected error - Reserved=0 - Total errors recovered - Number of times recovery invoked - Total bytes verified - LBAs with hard error.
- Page 06h parameters: (Counters for non medium errors, seek and other hardware type failures) - Non-Medium Error Counter
- Page 15h parameters: (Background Medium Scan information) - BMS Status parameter - all Medium Scan parameters
- Page 18h parameters (SAS PHY Error counts - only cleared for the port which receives the Log Select) - Invalid DWORD Count - Running Disparity Error Count - Loss of DWORD Synchronization Count
HGST Hard Disk Drive Specification 99

- PHY Reset Problem Count - Page 30h parameters:
- Zero Seeks counter - Seeks > = to 2/3 counter - Seeks > = 1/3 and < 2/3 counter - Seeks > = 1/6 and < 1/3 counter - Seeks > = 1/12 and < 1/6 counter - Seeks > 0 and < 1/12 counter - Overrun Counter - Under run Counter - Device Cache Full Read Hits - Device Cache Partial Read Hits - Device Cache Write Hits - Device Cache Fast Writes - Device Cache Misses on Reads - Page 37h parameters: - Media EXC - Hardware EXC - Total Read Commands - Total Write Commands
HGST Hard Disk Drive Specification 100

LOG SENSE (4D)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 4Dh

1

Reserved = 0

Reserved = 0

PPC=0 SP

2

PC

Page Code

3

Subpage Code

4

Reserved

5

(MSB)

6

Parameter Pointer

(LSB)

7

(MSB)

8

Allocation Length

(LSB)

9

Reserved = 0

FLAG LINK

Table 89 Log Sense (4D)

The LOG SENSE command allows the Initiator to retrieve the statistical data regarding the drive.
- PPC (Parameter Pointer Control) bit must be set to 0. This specifies that the drive start transferring data starting from the field specified in the parameter pointer field for the number of bytes specified by the allocation length. If the PPC bit is set to 1, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
- SP (Save Parameters) bit set to 0 specifies that the drive does not save any log parameters. If it is set to 1, all page parameters that are savable (those pages denoted by a DS = 0 in the parameter header control byte) are saved.
- PC (Page Control) field defines the type of parameters to be selected. This field must be set to 01b to specify the current cumulative values. Any other value in this field will cause the command to end with a Check Condition status with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
- Page Code field identifies which page is being requested. This field must be set to the values indicated in Page 0. If the Page Code value is invalid a Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
- SubPage Code This field specifies the subpage to select.
- Parameter Pointer field specifies the beginning parameter code for the data transfer.
- Allocation Length field specifies the maximum number of bytes the Initiator has allocated for returned Log Sense Data. No bytes are transferred if the length is 0. This condition is not considered an error. The Target terminates the Data in phase when all available Log Sense data has been transferred or when the number of bytes equals the allocation length, whichever is less.

HGST Hard Disk Drive Specification 101

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

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.

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

Page code = 0

1

Reserved

2-3

Page Length = 0010h(Number of Pages Supported)

4

First supported page 00h

5

Second supported page 02h

6

Third supported page 03h

7

Fourth supported page 05h

8

Fifth supported page 06h

9

Sixth supported page 0Dh

10

Seventh supported page 0Eh

11

Eighth supported page 0Fh

12

Ninth supported page 10h

13

Tenth supported page 15h

14

Eleventh supported page 18h

15

Twelfth supported page 19h

16

Thirteenth supported page 1Ah

17

Fourteenth supported page 2Fh

18

Fifteenth supported Page Code =30h

19

Sixteenth supported Page Code = 37h

Table 90 Log Sense Page 0

HGST Hard Disk Drive Specification 103

Log Sense Page 2

This page contains counters for write errors.

Byte
0 1 2-3 4-5 6 7 8-15 16-17 18 19 20-27 28-29 30 31 32-39 40-41 42 43 44-51 52-53 54 55 56-63 64-65 66 67 68-75 76-77 78 79 80-87

7

6

Reserved

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

Bit

5

4

3

2

Page code = 02h

Reserved

Page Length = 54h

Parameter Code = 0000h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered without delay

Parameter Code = 0001h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered with possible delays

Parameter Code = 0002h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Reserved = 0

Parameter Code = 0003h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Total errors recovered

Parameter Code = 0004h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Times recovery invoked

Parameter Code = 0005h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Total bytes written

Parameter Code = 0006h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Count of hard errors

1

0

F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b

Table 91 Log Sense Page 2
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 sectors written.

HGST Hard Disk Drive Specification 104

Log Sense Page 3

This page contains counters for read errors.

Byte
0 1 2-3 4-5 6 7 8-15 16-17 18 19 20-27 28-29 30 31 32-39 40-41 42 43 44-51 52-53 54 55 56-63 64-65 66 67 68-75 76-77 78 79 80-87

7

6

Reserved

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

Bit

5

4

3

2

Page code = 03h

Reserved

Page Length = 54h

Parameter Code = 0000h

TSD=0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered without delay

Parameter Code = 0001h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered with possible delays

Parameter Code = 0002h

TSD=0 ETC = 0

TMC = 0

Parameter Length = 08h

Reserved = 0

Parameter Code = 0003h

TSD=0 ETC = 0

TMC = 0

Parameter Length = 08h

Total errors recovered

Parameter Code = 0004h

TSD=0 ETC = 0

TMC = 0

Parameter Length = 08h

Times recovery invoked

Parameter Code = 0005h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Total bytes read

Parameter Code = 0006h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Count of hard errors

1

0

F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b

Table 92 Log Sense Page 3
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 sectors read. LDPC-on-the-fly correction is not included in any counters.

HGST Hard Disk Drive Specification 105

Log Sense Page 5

This page contains counters for verify errors.

Byte
0 1 2-3 4-5 6 7 8-15 16-17 18 19 20-27 28-29 30 31 32-39 40-41 42 43 44-51 52-53 54 55. 56-63 64-65 66 67 68-75 76-77 78 79 80-87

7

6

Reserved

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

DU = 0 DS = 0

Bit

5

4

3

2

Page code = 05h

Reserved

Page Length = 54h

Parameter Code = 0000h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered without delay

Parameter Code = 0001h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Errors recovered with possible delays

Parameter Code = 0002h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Reserved = 0

Parameter Code = 0003h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Total errors recovered

Parameter Code = 0004h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Times recovery invoked

Parameter Code = 0005h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Total Bytes Verified

Parameter Code = 0006h

TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Count of hard errors

1

0

F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b F&L = 00b

Table 93 Log Sense Page 5
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 sectors verified. LDPC-on-the-fly correction is not included in any counters.

HGST Hard Disk Drive Specification 106

Log Sense Page 6

This page contains counters for non-medium errors. This includes seek errors and other hardware type failures.

Byte
0 1 2-3 4-5 6 7 8-15

Bit

7

6

5

4

3

2

Reserved

Page code = 06h

Reserved

Page Length = 0Ch

Parameter Code = 00h

DU = 0 DS = 0 TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Error count

1

0

F&L = 00b

Table 94 Log Sense Page 6

Log Sense Page D

This page contains temperature information.

Byte
0 1 2-3 4-5 6 7 8 9 10-11 12 13 14 15

Bit

7

6

5

4

3

2

Reserved

Page code = 0Dh

Reserved

Page Length = 0Ch

Parameter Code = 0000h

DU = 0 DS = 1 TSD = 0 ETC = 0

TMC = 0

Parameter Length = 02h

Reserved

Temperature (degrees Celsius)

Parameter Code 0001h

DU = 0 DS = 1 TSD = 0 ETC = 0

TMC = 0

Parameter Length = 02h

Reserved

Reference Temperature (degrees Celsius)

1

0

F&L = 00b

F&L = 00b

Table 95 Log Sense Page D

HGST Hard Disk Drive Specification 107

Log Sense Page E

This page contains the start-stop cycle information.

Byte
0 1 2-3 4-5 6 7 8-11 12-13 14-15 16 17 18-21 22-23 24-25 26 27 28-31 32-33 34 35 36-39 40-41 42 43 44-47 48-49 50 51 52-55

Bit

7

6

5

4

3

2

1

0

Reserved

Page code = 0Eh

Reserved

Page Length = 34h

Parameter Code = 0001h

DU=0 DS=1 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 06h

Year of Manufacture (4 ASCII characters)

Week of Manufacture (2 ASCII characters)

Parameter Code 0002h

DU=0 DS=0 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 06h

Accounting Date Year (4 ASCII characters)

Accounting Date Week (2 ASCII characters)

Parameter Code 0003h

DU=0 DS=1 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 04h

Specified cycle count over device lifetime

Parameter Code 0004h

DU=0 DS=1 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 04h

Accumulated start-stop cycles (4 byte binary number)

Parameter Code 0005h

DU=0 DS=1 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 04h

Specified load unload count over device lifetime

Parameter Code 0006h

DU=0 DS=1 TSD=0 ETC=0

TMC = 0

F&L = 00b

Parameter Length = 04h

Accumulated load unload cycles (4 byte binary number)

Table 96 Log Sense Page E
The week and year that the device was manufactured shall be set in the parameter field defined by parameter code 0001h. The date of manufacture cannot be saved using the LOG SELECT command. The data is expected in numeric ASCII characters (30-39h) in the form YYYYWW. The accounting date specified by parameter code 0002h is a parameter that can be saved using the LOG SELECT command.

HGST Hard Disk Drive Specification 108

Log Sense Page F
This page contains the Application Client Log.

Byte

Bit

7

6

5

4

3

2

1

0

0

Reserved

Page code = 0Fh

1

Reserved

2-3

Page length = 4000h

Application client log parameter

4-259

1st application client log parameter

16132-16387

64th application client log parameter

Table 97 Log Sense Page F The following table describes the application client log parameter structure.

Bit

Byte

7

6

5

4

3

2

1

0

0-1

Parameter code

2

DU = 1 DS = 0 TSD = 0 ETC = 0

TMC = 0

F&L = 00b

3

Parameter length = FCh

4-

First parameter byte

255

Last parameter byte

Table 98 Log Sense Page F, Application Client Log
Parameter code 0000h through 003Fh are supported. The values stored in the parameter bytes represent data sent to the device in a previous LOG SELECT command.

HGST Hard Disk Drive Specification 109

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.

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

Page code = 10h

1

Reserved

2-3

Page Length = 190h

4-23

1st self-test results log parameter

384- 403

20th self-test results log parameter

Table 99 Log Sense Page 10 The following table describes the self-test results log parameter structure

Bit

Byte

7

6

5

4

3

2

1

0

0-1

Parameter code

2

DU = 0 DS = 0 TSD = 0 ETC = 0

TMC = 0

F&L = 11b

3

Parameter Length = 10h

4

Function Code

RSVD

Self-Test Results Value

5

Extended Segment Number

6-7

Timestamp

8-15

LBA of First Failure

16

Reserved

Sense Key

17

Additional Sense Code

18

Additional Sense Code Qualifier

19

Vendor specific

Table 100 Log Sense Page 10, self-test results
- Parameter Code identifies the log parameter for the log page. The parameter code field for the results of the most recent test will be 0001h. The parameter for the next most recent will be 0002h.
- Function Code contains the content of the Function Code field in the SEND DIAGNOSTIC command that initiated this self-test.
- Self-Test Results Value is described in the table below.

HGST Hard Disk Drive Specification 110

Value 0h

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

4h

The self-test completed with a test element that failed and it is not known which test element failed.

5h

The first segment of the self-test failed.

6h

The second segment of the self-test failed.

Table 101 Log Sense Page 10, self-test results

- Extended Segment Number This field identifies the number of the segment that failed during self-test. If no segment failed, this field will be 00h.

Extended Segment Number

Short Self-Test

Extended Self-Test

1h

Drive Ready Test

2h

Drive Diagnostics

3h

SMART

4h

Low Level Format check

5h

Physical Head Check

6h

Random Verify

7h

- Verify First 300 MB - Verify Last 100 MB

Verify all LBAs

8h

Recheck SMART

Table 102 Log Sense Page 10, Extended Segment Number
- Timestamp This field contains the total accumulated power-on hours of the Target at the time the self-test completed.
- LBA of first failure This field contains the LBA of the first logical block address where a self-test error occurred. If no errors occurred during the self-test or the error is not related to a LBA then the field will be FFFFFFFFFFFFFFFFh.
- Sense Key, Additional Sense Code and Additional Sense Code Qualifier These fields will contain the additional information relating to the error or exception conditions during self-test.
See Section 8.44 "SEND DIAGNOSTIC (1D)", for detailed listing of operations carried out by SEND DIAGNOSTIC command and Power on Diagnostics.

HGST Hard Disk Drive Specification 111

Log Sense Page 15

This page contains information about Background Medium Scan operations.

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

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

Table 103 Log Sense Page 15

The following table describes the BMS Status Parameter structure.

Byte
0-1 2 3 4-7 8 9 10-11 12-13 14-15

7 DU=0

Bit

6

5

4

3

2

1

0

Parameter Code = 0000h

DS=0 TSD=0 ETC=0

TMC=0

F&L = 11b

Page Length = 0Ch

Power On Minutes

Reserved = 0

BMS Status

Number of Background Scans Performed

Medium Scan Progress

Number of Background Medium Scans Performed

Table 104 BMS Status Parameter structure - Power On Minutes indicates the total power on minutes at the time the log page is requested - BMS Status is described in the following table

BMS Status 00h 01h 02h
03h-04h 05h 06h 07h 08h
09h - FFh

Description No scans active Background medium scan is active The device server performed automatic read reassignment for the LBA Not supported Background scan halted due to medium formatted without P-List Background scan halted due to a vendor-specific cause Background scan halted due to temperature out of range Scan suspended until BMS Interval Timer expires Reserved

Table 105 BMS Status

- The Number of Background Scans Performed field indicates the total number of back ground scans (i.e. total number of Background Medium Scans PLUS number of Background Prescan) that have been performed over the life of the drive.

HGST Hard Disk Drive Specification 112

- Medium Scan Progress is a percent complete indication of the medium scan. The returned value is a numerator that has 65,536(1 00 00h) as its denominator.
- Number of Background Medium Scans Performed field indicates the number of background medium scans that have been performed over the life of the drive.
The following table describes the Medium Scan Parameter structure.

Byte
0-1 2 3 4-7 8 9 10 11
12-13
14-15
16-23

7 DU=0
(MSB) (MSB)

Bit

6

5

4

3

2

1

0

Parameter Code = 0001h - 0800h

DS=0 TSD=0 ETC=0

TMC=0

F&L = 11b

Page Length = 14h

Power On Minutes

Reassign Status

Sense Key

Additional Sense Code

Additional Sense Code Qualifier

Head

(MSB)

Cylinder

Cylinder

(LSB)

Sector LBA

(LSB)

Table 106 Medium Scan Parameter structure

- Power On Minutes indicates the total power on minutes at the time the error was detected. - Reassign Status is set as shown below. Reassignment during the background scan is not supported.

Reassign Status 0h
1h 02h-4h
5h
6h 7h ­ Fh

Description
No reassignment needed This value is not reported, if LOWIR bit is set to 1 in Background Control Mode Page. Reassignment pending receipt of Reassign command or write command (if auto write reallocation is allowed) from the initiator Not supported Error was detected by BGMS, and was successfully rewritten. This value is not reported, if LOWIR bit is set to 1 in Background Control Mode Page. Error was detected by BGMS, and was successfully reassigned by Application Client. Contains valid data. Reserved

Table 107 Reassign Status

Additional Sense Code and Additional Sense Code Qualifier provide details about the error detected.

HGST Hard Disk Drive Specification 113

Log Sense Page 18

This page contains protocol-specific log parameters.

Bit

Byte

7

6

5

4

3

2

1

0

0

Page code = 18h

1

SubPage Code (00h)

(MSB) 2-3
4-111 112-219

Page Length (D8h)

(LSB)

Protocol-specific log parameters

First Protocol-specific log parameter - Primary Port

Last Protocol-specific log parameters - Secondary Port

Table 108 Log Sense Page 18

Byte
0-1 2 3

Bit

7

6

5

4

3

2

1

0

(MSB)

Parameter Code (0001h for primary port; 0002h for secondary

(LSB)

DU (=0) Obsolete TSD (=0) ETC (=0)

TMC (00b)

Format and Linking

Parameter Length (68h)

4

Reserved

Protocol IDENTIFIER (6h)

5

Reserved

6

Generation Code

7

8

9

10

11

12

Reserved

13

Number of PHYs (01h)

Reserved

PHY IDENTIFIER (00h)

Reserved

SAS PHY Log Descriptor Length (60h)

Attached Device Type

Attached Reason

Reason

Negotiated Physical Link Rate

Table 109 SAS Log Descriptor (part 1 of 3)

HGST Hard Disk Drive Specification 114

Byte

7

6

5

4

Bit

3

2

1

0

14

Reserved

Attached SSP Attached STP Attached SMP Initiator Port Initiator Port Initiator Port

Reserved

15

Reserved

Attached SSP Attached STP Attached SMP Target Port Target Port 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)

32

Attached PHY Identifier (the PHY identifier received in the incoming IDENTIFY)

33-39

Reserved

(MSB) 40-43
(MSB) 44-47

Invalid Dword Count Running Disparity Error Count

(LSB) (LSB)

(MSB) 48-51

Loss of Dword Synchronization

(LSB)

(MSB) 52-55
56-57

PHY Reset Problem Reserved

(LSB)

58

PHY event Descriptor Length (0Ch)

59

Number of Event Descriptors (04h)

60-62

Reserved

63

Phy Event Source (01h) (Invalid Dword Count)

(MSB) 64-67

PHY Event

(LSB)

(MSB) 68-71

Peak Value Detector Threshold (00h)

(LSB)

Table 110 SAS Log Descriptor (part 2 of 3)

HGST Hard Disk Drive Specification 115

Bit

Byte

7

6

5

4

3

2

1

0

72-74

Reserved

75

PHY Event Source (02h) (Running Disparity Error Count)

(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 Value Detector Threshold (00h)

(LSB)

Table 111 SAS Log Descriptor (part 3 of 3)
 Attached Device Type is set to the value received by this PHY during an Identify Sequence.  Attached Reason indicates the value of the REASON field in the last received IDENTIFY address frame (see
Table 34) during the identification sequence if the PHY is a physical PHY and a SAS PHY or expander PHY is attached. If the PHY is a physical PHY and a SATA PHY is attached, then the ATTACHED REASON field shall be set to 0h after the initial Register ­ Device to Host FIS has been received. If the PHY is a virtual PHY, then the ATTACHED REASON field shall be set to 0h.  Reason indicates the reason for the last link reset sequence as reported in the last transmitted IDENTIFY address frame (see Table 33). If the PHY is a physical PHY and a SATA PHY is attached, then the REASON field indicates the reason for the link reset sequence. For Reason field, refer Table 34.  Negotiated PHY Link Rate: set to the link rate negotiated during last Link Reset Sequence.
- set to 8h when the PHY is enabled and the negotiated speed is 1.5G
- set to 9h when the PHY is enabled and the negotiated speed is 3.0G
- set to Ah when the PHY is enabled and the negotiated speed is 6.0G
- set to Bh when the PHY is enabled and the negotiated speed is 12.0G

HGST Hard Disk Drive Specification 116

 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). The GENERATION CODE field is also contained in the Protocol-Specific Port log page and may be used to correlate PHY settings across mode page and log page accesses.
 Attached Reason indicates the value of the REASON field received in the IDENTIFY address frame.  Attached Initiator Port set to the value received by this PHY during an Identify Sequence.  Attached Target Port set to the value received by this PHY during an Identify Sequence.  SAS ADDRESS contains the SAS address transmitted by this PHY during an Identify Sequence.  Attached SAS ADDRESS contains the SAS address received by this PHY during an Identify Sequence.  Attached PHY Identifier contains the SAS PHY Identifier received by this PHY during an Identify Sequence.  Invalid Dword Count indicates the number of invalid Dwords that have been received outside of PHY reset
sequences. The count stops at the maximum value.  Running Disparity Error Count increments by one when the port has acquired Dword synchronization and
detects a transmission word containing a running disparity error at the receiver. When the port has lost Dword synchronization, the Running Disparity Error Count is not incremented. The count stops at the maximum value.  Loss of Dword Synchronication indicates the number of times the PHY has lost Dword synchronization and restarted the link reset sequence of PHY reset sequences. The count stops at the maximum value.  PHY Reset Problem indicates the number of times the PHY reset sequence has failed due to a failure to gain Dword sync in the retry speed match speed negotiation. The count stops at the maximum value.  PHY Event Descriptor Length indicates the number of bytes in the PHY event descriptor, which is 0Ch.  Number of Event Descriptors indicates the number of PHY event descriptors in the PHY event descriptor list, which is 04h.  Event Source (01h) - Invalid Dword Count. The "PHY Event" field following this event source contains the number of invalid Dwords detected by the PHY since power on. The "Peak Value Detector Threshold" is set to 00000000h to indicate this is a counter and not a peak value detector.  Event Source (02h) - Running Disparity Error Count. The "PHY Event" field following this event source contains the number of disparity errors detected by the PHY since power on. The "Peak Value Detector Threshold" is set to 00000000h to indicate this is a counter and not a peak value detector.  Event Source (03h) - Loss of Dword Synchronization Count. The "Phy Event" field following this event source contains the number of times the receiver has lost Dword synchronization since power on. The "Peak Value Detector Threshold" is set to 00000000h to indicate this is a counter and not a peak value detector.  Event Source (04h) - PHY Reset Problem Count. The "PHY Event" field following this event source contains the number of times the PHY has encountered a PHY reset problem condition since power on. The "Peak Value Detector Threshold" is set to 00000000h to indicate this is a counter and not a peak value detector.
HGST Hard Disk Drive Specification 117

Log Sense Page 19h - General Statistics and Performance

Bit

Byte

7

6

5

4

3

2

1

0

0

DS = 0 SPF = 0

Page Code = 19h

1

Sub Page Code = 00h

2-3

Page Length = 005Ch

4-5

Parameter Code = 0001h

6 7 8-15

DU = 0 Obsolete TSD = 0 ETC = 0

TMC = 0

Parameter Length = 40h

Number of Read Commands

Format and Linking = 10b

16-23

Number of Write Commands

24-31

Number of Logical Blocks Received

32-39

Number of Logical Blocks Transmitted

40-47

Read Command Processing Intervals

48-55

Write Command Processing Intervals

56-63

Weighted Number of Read Commands plus Write Commands

64-71 72-73
74 75 76-83 84-85 86 87 88-95

Weighted Read Command Processing plus Write Command Processing

Parameter Code = 0002h

DU = 0 Obsolete TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Format and Linking = 10b

Idle Time Intervals

Parameter Code = 0003h

DU = 0 Obsolete TSD = 0 ETC = 0

TMC = 0

Parameter Length = 08h

Format and Linking = 11b

Time Interval Descriptor

Table 112 Log Sense Page 19h - General Statistics and Performance
Number of Read Commands indicates the number of read commands received by the logical unit. Number of Write Commands indicates the number of write commands received by the logical unit. Number of Logical Blocks Received indicates the number of logical blocks received by any SCSI target port for the logical unit as a result of write commands. Number of Logical Blocks Transmitted indicates the number of logical blocks transmitted by any SCSI target port for the logical unit as a result of read commands. Read Command Processing Interval is not supported and is set to 0. Write Command Processing Interval is not supported and is set to 0. Weighted Number of Read Commands Plus Write Commands is not supported and is set to 0. Weighted Read Command Processing Plus Write Command Processing is not supported and is set to 0.
HGST Hard Disk Drive Specification 118

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.

Bit

Byte

7

6

5

4

3

2

1

0

0-3

Exponent

4-7

Integer

Table 113 Time Interval Descriptor
Exponent contains the negative power of 10 exponent to multiply with the Integer field. Integer, when multiplied by the exponent, contains the value that represents one time interval. The Exponent and Integer are set to the equivalent of 50ms (5x10-2 seconds).

HGST Hard Disk Drive Specification 119

Log Sense Page 1A

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

Page code = 1Ah

1

Sub Page Code (00h)

2-3

Page Length (30h)

4-5

Parameter Code 0001h

6

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

7

Parameter Length = 4

8-11

Accumulated Transitions to Active State

12-13

Parameter Code 0002h

14

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

15

Parameter Length = 4

16-19

Accumulated Transitions to Idle_A

20-21

Parameter Code 0003h

22

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

23

Parameter Length = 4

24-27

Accumulated Transitions to Idle_B

28-29

Parameter Code 0004h

30

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

31

Parameter Length = 4

32-35

Accumulated Transitions to Idle_C

36-37

Parameter Code 0008h

38

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

39

Parameter Length = 4

40-43

Accumulated Transitions to Standby_Z

44-45

Parameter Code 0009h

46

DU Obsolete TSD

ETC

TMC

TMC FMT & Linking FMT & Linking

47

Parameter Length = 4

48-51

Accumulated Transitions to Standby_Y

Table 114 Log Sense Page 1A

HGST Hard Disk Drive Specification 120

Log Sense Page 2F
This page contains SMART Status and Temperature Reading.

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

Page code = 2Fh

1

Reserved

2-3

Page Length = 8

4-5

Parameter Code = 0000h

6

DU = 0 DS = 0 TSD = 0 ETC = 0

TMC = 0

F&L = 11b

7

Parameter Length = 04h

8

SMART Sense Code Byte

9

SMART Sense Qualifier

10

Most Recent Temperature Reading

11

Vendor HDA Temperature Trip Point

12-13

Parameter Code = 0001h

14

DU = 0 DS = 0 TSD = 0 ETC = 0

TMC = 0

F&L = 11b

15

Parameter Length = 03h

16

Internal Environment status Current Value

17

Internal Environment status Worst Value

18

Internal Environment status Threshold Value

Table 115 Log Sense Page 2F

HGST Hard Disk Drive Specification 121

Log Sense Page 30
This page contains Performance Counters.

Bit

Byte

7

6

5

4

3

2

1

0

0

Reserved

Page code = 30h

1

Reserved

2-3

Page Length = 0030h

4-5

Parameter Code = 0000h

6

DU = 0 DS = 0 TSD = 0 ETC = 0

TMC = 0

F&L = 00b

7

Parameter Length = 2Ch

8-9

Zero Seeks

10-11

Seeks > = to 2/3

12-13

Seeks > = 1/3 and < 2/3

14-15

Seeks > = 1/6 and < 1/3

16-17

Seeks > = 1/12 and < 1/6

18-19

Seeks > 0 and < 1/12

20-23

Reserved = 0

24-25

Overrun Counter

26-27

Under run Counter

28-31

Device Cache Full Read Hits

32-35

Device Cache Partial Read Hits

36-39

Device Cache Write Hits

40-43

Device Cache Fast Writes

44-47

Device Cache Read Misses

48-51

Reserved = 0

Table 116 Log Sense Page 30
Page 30h returns performance counter information. This includes seek counters and buffer overrun/under run counters. The appropriate seek counter is incremented once during execution of Pre-Fetch, Read, Verify, Write, Write and Verify, Write Same, and Seek commands. Buffer Overrun conditions are detected during Read commands. Buffer Under run conditions are detected during Verify with ByteChk=1, Write, Write and Verify, and Write Same commands. Only one seek counter is incremented for each of these commands and the counter is incremented only once per command. The length of the initial seek that is required to access the first Logical Block specified for the SCSI

HGST Hard Disk Drive Specification 122

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. The seek operations that occur in Idle Time Functions are not directly entered into page 30 seek counters but they change the length of the following seek. This is because after the Idle Time Function is completed, the heads will not necessarily be in the same position as they were at the completion of the previous command. A buffer overrun or under run condition occurs when the Initiator does not transfer data to or from the Target data buffer fast enough to keep up with reading or writing the media. The buffer overrun counter is incremented during operations that require a Data In phase when a buffer full condition prevents the continued transfer of data from the media to the data buffer. The buffer under run counter is incremented during operations that require a Data Out phase when a buffer empty condition prevents the start or continuation of a data transfer from the data buffer to the media (or a data transfer from the media for a Verify command with BytChk=1). Buffer Overrun conditions are detected during the following SCSI commands:
- READ (6) - READ (10)
Buffer Under Run conditions are detected during the following SCSI commands: - VERIFY WITH BytChk=1 - VERIFY (16) WITH BytChk=1 - WRITE (6) - WRITE (10) - WRITE AND VERIFY - WRITE AND VERIFY (16) - WRITE SAME - WRITE SAME (16) - ZERO SEEKS The number of times no seek was required. The operation may have resulted in a head switch.
- SEEKS >= 2/3 DISK The number of seeks equal to or greater than 2/3 of the disk.
- SEEKS >= 1/3 AND < 2/3 DISK The number of seeks equal to or greater than 1/3 and less than 2/3 of the disk.
- SEEKS >= 1/6 AND < 1/3 DISK The number of seeks equal to or greater than 1/6 and less than 1/3 of the disk.
- SEEKS >= 1/12 AND < 1/6 DISK The number of seeks equal to or greater than 1/12 and less than 1/6 of the disk.
- SEEKS > 0 AND < 1/12 DISK The number of seeks less than 1/12 of the disk.
- OVERRUN COUNTER The number of times that data was available to be transferred from the media but the device buffer still contained data that had not been retrieved by the Initiator. Consequently, the disk had to take additional revolutions until the buffer was available to accept data.
- UNDER RUN COUNTER The number of times that the drive was ready to transfer data to its disk (on a write), but its buffer was empty (i.e., had not been filled by the Initiator), thus the disk was forced to take extra revolutions.
HGST Hard Disk Drive Specification 123

- 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.
- DEVICE CACHE WRITE HITS The number of times that the data associated with a write operation replaces, or is combined with, existing data in the device write cache, thereby eliminating a write operation.
- DEVICE CACHE FAST WRITES The number of times that space was available in the device write cache for the data associated with a write operation and a response was returned immediately.
- DEVICE CACHE READ MISSES The number of times that none of the data requested by the read operation was obtained from the read cache.
The statistics reported by this page are lost on a self-initiated reset or when the Drive is powered off. Even though the DS field equals 0, the parameters on this page are not savable.
HGST Hard Disk Drive Specification 124

Log Sense Page 37

This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.

Byte
0 1 2-3 4-5 6 7
8 - 11

7

6

Reserved

DU=0 (MSB)

DS=0

Bit

5

4

3

2

Page code = 37h

Reserved

Page Length = 0030h (48)

Parameter Code = 0000h

TSD=0 ETC=0

TMC = 0

Parameter Length = 2Ch

Power on Hours (hours only)

(MSB) 12 - 19

Total Bytes Read

(MSB) 20 - 27

Total Bytes Written

28 29 - 30

(MSB)

Max Drive Temp (degrees Celsius) GList Size

31 32 33 - 40 41 - 48 49 50-51

MED EXC

Number of Information Exceptions

HDW EXC

Reserved = 0

Total Read Commands

Total Write Commands

Reserved = 0

Flash Correction Count

1

0

F&L = 00b (LSB) (LSB) (LSB) (LSB)

Table 117 Log Sense Page 37
The Power on Hours field specifies the total time the drive has been powered on in hours only. The Max. Drive Temperature field specifies the maximum temperature, in degrees Celsius, the drive has ever reached. The Glist Size field gives the total number of LBAs that have been reassigned on the drive. The Number of Information Exceptions field gives the number of Information Exceptions during the life of the drive and not the number of Information Exceptions that have been reported. The number of reported Information Exceptions may be less due to the settings of Mode Page 0x1C.NOTE: This field does not include occurrences of any Information Exception Warnings. If set, the Media Exception and Hardware Exception bits indicate that an Information Exception has occurred during the life of the drive. These flags are set during an Information Exception that may or may not coincide with the reporting of an Information Exceptions as mentioned above. Total Read Commands counter is incremented for each Read (6) and Read (10) command received. Total Write Commands counter is incremented for each Write (6), Write (10), Write Verify and Write Verify (16) command received. Flash Correction Count is incremented each time ECC correction is applied to data stored in Flash ROM.

HGST Hard Disk Drive Specification 125

MODE SELECT (15)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 15h

1

Reserved = 0

PF=1

Reserved = 0

SP

2 3

Reserved = 0

4

Parameter List Length

5

VU = 0

Reserved = 0

FLAG LINK

Table 118 Mode Select (15)
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. There is a single set of Mode Page parameters shared by all Initiators.
- PF Page Format bit value of one indicates that the data sent by the Initiator after the Mode Select Header and the Block Descriptor, if any, complies with the Page Format. The Target ignores this field since it only accepts mode parameters in the Page Format.
- SP Save Pages. This indicates:
0 The drive shall not save the pages sent during the Data Out phase but will use them for all following commands until the power is removed, a reset is received, or a new MODE SELECT command is received.
1 The drive will save the data in the reserved area of the disk. It will be used for all the following commands until another MODE SELECT command is issued. This information is maintained over a power cycle or reset of the drive.
- Parameter List Length This specifies the number of bytes to be sent from the Initiator. A parameter list length of zero suppresses data transfer and is not considered an error.
The MODE SELECT parameter list contains a 4-byte header followed by zero or one block descriptor followed by zero or more pages. The pages that are valid with this command are defined in the addendum under the heading Mode Select Data, as they vary with the drive model.
Application Note The Initiator should issue a MODE SENSE command requesting all Changeable values (see PCF field in byte two of the CDB in) prior to issuing a MODE SELECT command. This is necessary to find out which pages are implemented by the drive and the length of those pages. In the Pages of the MODE SENSE command the drive will return the number of bytes supported for each Page. The Page Length set by the Initiator in the MODE SELECT command must be the same value as returned by the drive in MODE SENSE Page Length. If not, the drive will return Check Condition status with sense key of Illegal Request.
Note: If an Initiator sends a MODE SELECT command that changes any parameters that apply to other Initiators, the drive shall generate a unit attention condition for all Initiators except for the one that issued the MODE SELECT command. The drive shall set the additional sense code to Parameters Changed (2Ah).

HGST Hard Disk Drive Specification 126

MODE SELECT (55)

Byte
0 1

Bit

7

6

5

4

3

2

1

0

Command Code = 55h

Reserved = 0

PF=1

Reserved = 0

SP

2-6

Reserved = 0

(MSB) 7-8

Parameter List Length

(LSB)

9

VU = 0

Reserved = 0

FLAG LINK

Table 119 Mode Select (55)
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.

HGST Hard Disk Drive Specification 127

MODE SENSE (1A)

Byte
0 1 2 3 4 5

Bit

7

6

5

4

3

2

1

0

Command Code = 1Ah

Reserved= 0

RSVD DBD

Reserved = 0

PCF

Page Code

Subpage Code

Allocation Length

VU = 0

Reserved = 0

FLAG LINK

Table 120 Mode Sense (1A)
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. If the DBD bit is set to 1, the Target will not return a Block Descriptor.
Allocation Length indicates the maximum number of bytes that the Initiator has set aside for the DATA IN phase. A value of zero is not considered an error. If the allocation length is smaller than the amount available, that portion of the data up to the allocation length will be sent. This may result in only a portion of a multi-byte field being sent.
Page Control Field: PCF (Page Control Field) defines the type of Page Parameter values to be returned.
PCF Meaning
- 0 0 Report current values. The drive returns the current values under which the logical unit is presently configured for the page code specified. The current values returned are
1. Initially following power-up but before the media is accessed, the default values become current. Once the media can be accessed, the saved values are read from the Reserved Area and become current.
2. The parameters set in the last successful MODE SELECT command.
3. The saved values if a MODE SELECT command has not been executed since the last power-on, hard RESET condition, or TARGET RESET message.
Following the completion of start-up, execution of the MODE SELECT command can modify the current values.
Note: Those parameters associated with format are not considered current and are not saved until the successful completion of a FORMAT UNIT command. In addition, the current values take on the saved values after a reset if the parameters were saved. If the Page Code is 3Fh, then all pages implemented by the Target are returned to the Initiator with fields and bit values set to current values.
If the Page Code is not 3Fh, the page defined by the Page Code, if supported by the Target, is returned with fields and bits set to current values.
Note: The drive will not process the MODE SELECT command until the completion of spin-up. Therefore, the Initiator cannot modify the current values prior to the saved values being read in.
- 0 1 Report changeable value. The drive returns the changeable values for the page code specified. The page requested is returned containing information that indicates which fields are changeable. All bits of parameters that are changeable shall be set to one. Parameters that are defined by the drive shall be set to zero. If any part of a field is changeable, all bits in that field shall be set to one.
Note: For a value field such as the buffer ratios of page 2 the bit field will not indicate the range of supported values but rather that the field is supported.
- 1 0 Report default value. The drive returns the default values for the page code specified. The parameters not supported by the drive are set to zero.

HGST Hard Disk Drive Specification 128

- 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 Code 00h - 1Ch
3Fh

Description Return specific page, if supported. Return all supported pages.

Table 121 Page Code Usage
If a Page Code of 3Fh is used, MODE SENSE returns the pages in ascending order with one exception. Page 0 is always returned last in response to a MODE SENSE command. If an unsupported page is selected, the command is terminated with a CHECKCONDITION status and available sense of ILLEGAL REQUEST/INVALID FIELD IN CDB. Subpage Code: This field specifies the subpage to return, and may be set to a specific page, or to FFh for all supported subpages.

HGST Hard Disk Drive Specification 129

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

The header used for the 6-byte CDB is defined below.

Byte

7

6

5

Bit

4

3

2

1

0

0

Mode Data Length

1

Medium Type = 0

2

WP=0 Reserved=0 DPOFUA = 1

Reserved = 0

3

Block Descriptor Length (= 0 or 8)

Table 122 Mode parameter header (6)

The header used for the 10-byte CDB is defined below.

Byte 0 - 1

7 (MSB)

2 3 4 5
6 - 7

WP=0 (MSB)

6

5

Bit

4

3

2

1

0

Mode Data Length

Reserved=0

Medium Type = 0 DPOFUA =1 Reserved = 0
Reserved = 0

(LSB)
Reserved = 0 Long LBA

Block Descriptor Length

(LSB)

Table 123 Mode parameter header (10)

- Mode Data Length. When using the MODE SENSE command, the mode data length field specifies the length in bytes of the following data that is available to be transferred. The mode data length does not include the length byte itself. When using the MODE SELECT command, this field is reserved.
- Medium Type field is always set to zero in the drive (Default Medium Type).
- WP. When used with the MODE SELECT command, the Write Protect (WP) bit is reserved. When used with the MODE SENSE command, a Write Protect (WP) bit of zero indicates that the medium is write enabled.
- DPOFUA bit value of 1 indicates that the Target supports the FUA and DPO bits in the Read and Write Commands.
- LONGLBA bit value of 0 indicates that any following Block Descriptor uses the Short LBA Block Descriptor format. A LONGLBA bit value of 1 indicates that any following Block Descriptor uses the Long LBA Block Descriptor format
- Block Descriptor Length specifies the length in bytes of the block descriptor. Values of 0, 8, and 16 are 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.

HGST Hard Disk Drive Specification 130

Block Descriptor

Byte

7

6

(MSB) 0 - 3

4 5 - 7

(MSB)

Bit

5

4

3

2

Number of Blocks

Reserved = 0

Block Length

1

0

(LSB)

(LSB)

Table 124 Short LBA Mode Parameter Block Descriptor

Byte

7

6

(MSB) 0 - 7

8-11 12-15

(MSB)

Bit

5

4

3

2

Number of Blocks

Reserved = 0

Block Length

1

0

(LSB)

(LSB)

Table 125 Long LBA Mode Parameter Block Descriptor
The Block descriptor provides formatting information about the Number of Blocks (user addressable) to format at the specified Block Length. - Number of Blocks, when used with the MODE SELECT command, indicates the number of blocks to format
- Zero to indicate not to change available blocks
- 0xFFFFFFFF (Short LBA) or 0xFFFFFFFFFFFFFFFF (Long LBA) to indicate all available blocks
- The exact number of blocks in the data area of the drive, which can be obtained with the MODE SENSE
- The number of blocks less than exact one, in order to CLIP the number of blocks Any other value is invalid and causes the command to fail with Check Condition status. When returned by the MODE SENSE command, the field contains the exact number of blocks.
- Block Length field reflects the number of bytes of user data per sector (not including any protection information). When used with the MODE SELECT command, the Block Length field must contain a value from 512, 520, 528 or zero for all models and 4096, 4112, 4160, 4224 for models which support format with 4k nominal block sizes. Otherwise the drive will terminate the command with Check Condition status.
A FORMAT UNIT command is required to cause these parameters to become current only if the block length parameter is different from the current block length.

HGST Hard Disk Drive Specification 131

Page Descriptor

Byte 0

PS

SPF

Page Code

Byte 1

Page Length

Byte 2-n

Mode Parameters

Table 126 Mode Parameter Page Format
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. When using the MODE SELECT command, the PS bit is reserved (zero). SPF (Sub-Page Format) is set to zero to indicate the short page format is used. The bit is set to one to indicate the long format is used, supporting sub-pages. The drive supports the following mode page codes:

Page

Description

PS

00

Vendor Unique Parameters

1

01

Read-Write Error Recovery Parameters

1

02

Disconnect/Reconnect Control Parameters

1

03

Format Device Parameters

0

04

Rigid Disk Geometry Parameters

0

07

Verify Error Recovery Parameters

1

08

Caching Parameters

1

0A

Control Mode Page

1

0C

Notch Parameters

1

19

Port Control Page

1

1A

Power Control Parameters

1

1C

Informational Exceptions Control

1

Table 127 Mode Parameter Page Format
The page length field specifies the length in bytes of the mode parameters that follow. If the Initiator does not set this value to the value that is returned for the page by the MODE SENSE command, the drive will terminate the command with Check Condition status.

HGST Hard Disk Drive Specification 132

Mode Page 00 (Vendor Unique Parameters)

Byte 7

Bit

6

5

4

3

2

1

Default 0

0

PS

0

Page Code = 00h

80h

1

Page Length = 0Eh

0Eh

2

Reserved

3

Reserved VGMDE

MRG Reserved

Reserved

Ignored

00h

RRNDE Reserved 00h

4

Reserved

00h

5

Reserved

FDD

Reserved

CAEN Ignored

02h

6

IGRA AVERP

Reserved

OCT (high nibble)

00h

7

Overall Command Timer (low byte)

00h

8

Reserved

00h

9

Temperature Threshold

00h

10

Command Aging Limit (Hi byte)

00h

11

Command Aging Limit (Low byte)

30h

12

Read Reporting Threshold

16h

13

Write Reporting Threshold

14h

14

DRRT

Ignored

FFMT

Ignored

00h

15

Ignored Reserved FCERT Ignored Reserved Ignored

Reserved

00h

Table 128 Vendor Unique Parameters - Page 00
Fields marked in the table as 'Ignored' are not used or checked by the drive. They will be initialized to zero but can be set as desired for compatibility with older drives.
- MRG (Merge Glist into Plist) bit is set to 1 for merging the Glist entries into the Plist during FORMAT UNIT command.
- VGMDE (Veggie Mode) bit set to 1 will cause the drive to execute random self-seeks. To enable this mode, the initiator must perform the mode select to set the bit while the drive is spinning, then Stop Unit, then Start Unit. VGMDE set to 0 disables the self-seeks (normal operation).
- RRNDE (Report Recovered Non Data Errors) bit controls the reporting of recovered Non Data Errors when the PER bit is set. If RRNDE is set, recovered Non Data Errors are reported. If the RRNDE bit is not set, then recovered Non Data Errors are not reported.
- FDD (Format Degraded Disable) controls the reporting of Format Degraded sense data for Test Unit Ready commands when the drive is in a format degraded state. When the FDD bit is one, Format Degraded sense data will not be reported for a Test Unit Ready command. When the FDD bit is zero, Format Degraded sense data will be reported for Test Unit Ready commands when the drive is in a format degraded state. This bit does not affect the reporting of Format Degraded conditions for any media access commands.
- CAEN (Command Aging Enable) When set this bit causes the Command Age Limit timer to be used to avoid commands waiting in the command queue for an indefinite period. When commands have been in the queue for a period of time greater than the timer limit they will be reordered to be executed on a first come first served basis. When this bit is reset, commands are always executed based on the queue reordering rules.

HGST Hard Disk Drive Specification 133

- 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. If IGRA is set to one and RC is set to zero, or if IGRA is set to zero, reassigned LBAs will be processed normally.
- AVERP (AV ERP Mode) bit is set to one in order to specify maximum retry counts during Read DRP. When AVERP bit is set to one, the maximum retry counts for read operations is specified by Read Retry Count (Mode Page 1 Byte 3). AVERP bit is set to zero to specify that the drive shall process read DRP up to the default maximum retry count when Read Retry Count is set to a non-zero value.
- OCT(Overall Command Timer) controls the maximum command execution time, from receipt by the drive until status is returned. If the command is unable to complete in the specified amount of time, it will be aborted with Check Condition status, Aborted Command sense key. The Overall Command Timer does not alter the behavior of the Command Aging Limit or Recovery Time Limit. Each unit of this timer is 50 milliseconds. Setting the value to zero disable the feature.
- Temperature Threshold Temperature Threshold specifies the threshold value in degrees Celsius for the thermal sensor Information Exception Warning; the reporting of which is controlled by Mode Page 0x1C. A value of 0 selects the default value (85 degrees Celsius).
- Command Aging Limit This value controls the maximum time a command should wait in the command queue when the CAEN bit is set. Each unit of this timer is 50ms.
- Read Reporting Threshold specifies the recovery step that must be exceeded to report recovered data errors during read operations when PER=1.For example, if the Read Reporting Threshold is set to 22, recovered read errors will be reported starting at recovery step 23
- Write Reporting Threshold specifies the recovery step that must be exceeded to report recovered data errors during write operations when PER=1.For example, if the Write Reporting Threshold is set to 20, recovered write errors will be reported starting at recovery step 21.
- DRRT (Disable Restore Reassign Target) bit disables the reading and restoration of the target LBA during a Reassign Blocks command. If the DRRT bit is zero, the reassign command attempts to restore the target LBA's data. If the data cannot be restored, the target LBA is reassigned and written with a data pattern of all 00s. If the DRRT bit is one, no attempt is made to restore the target LBA.
- FFMT (Fast Format Enable) bit allows the formatting of the drive without any writes to the customer media. All format operations are allowed including changing block sizes and manipulating defects. The drive will operate normally after a fast format with the following caveat: since no data is written to any customer data blocks as a result of a Fast Format operation, there is a possibility that a read attempt to any particular block (without having previously written to that block) will result in an unrecoverable data error. This will most likely happen if the block size is changed as every LBA will contain data of an incorrect length and apparently an incorrect starting point. It is also possible to generate an uncorrectable data error without changing block sizes if the defect list is shortened and previously bad blocks become visible in the customer address space. Of course ALL DATA ON THE DRIVE WILL BE LOST as the result of any format operation and so any attempt to read blocks which have not been written to will result in unpredictable behavior.
- FCERT (Format Certification) bit determines whether the certification step will be performed during a Format Unit command. FCERT bit set to 0 disables certification. FCERT bit set to 1 enables the certification step.
HGST Hard Disk Drive Specification 134

Mode Page 01 (Read/Write Error Recovery Parameters)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS

0

Page Code = 01h

81h

1

Page Length = 0Ah

0Ah

2

AWRE ARRE TB

RC EER=0 PER DTE DCR=0 C0h

3

Read Retry Count

01h

4

Obsolete = 0

00h

5

Obsolete = 0

00h

6

Obsolete = 0

00h

7

Reserved

00h

8

Write Retry Count

01h

9

Reserved

00h

10

(MSB)

11

Recovery Time Limit

00h (LSB)

Table 129 Mode Page 01 (Vendor Unique Parameters)
The Read-Write recovery parameters that will be used during any command that performs a read or write operation to the medium are as follows:
- AWRE Automatic Write Reallocation Enabled bit, set to one indicates that the drive shall perform automatic reallocation of defective data blocks during write operations. AWRE bit set to zero is ignored.
- ARRE Automatic Read Reallocation Enabled bit, set to one indicates that the drive shall perform automatic reallocation of defective data blocks during read operations. ARRE bit, set to zero is ignored.
- TB Transfer Block bit, set to one indicates that a data block that is not recovered within the recovery limits specified shall be transferred to the Initiator before Check Condition status is returned. A TB bit set to zero indicates that such a data block shall not be transferred to the Initiator. Data blocks that can be recovered within the recovery limits are always transferred regardless of the value of the bit.
- RC Read Continuous bit, set to one requests the Target to transfer the entire requested length of data without adding delays that would increase or ensure data integrity. This implies that the Target may send erroneous data. This bit has priority over all other error control bits (PER, DTE, DCR, TB). RC set to zero indicates normal interpretation of PER, DTE, DCR, and TB values. The RC bit setting is used by the Target when reporting errors associated with the transfer of the Initiator's data for the Read commands interpretation of PER, DTE, DCR, and TB values. The RC bit applies only to READ commands.
Note: The Target implementation of the RC option is to disable error detection of the data fields but continue normal error detection and recovery for errors occurring in the servo field. If a servo field failure occurs, normal DRP could result in considerable recovery action, including proceeding through all levels of DRP.
- EER an Enable Early Recovery bit, must be set to zero, indicating that the drive shall use an error recovery procedure that minimizes the risk of misdetection or miscorrection during the data transfer. Data shall not be fabricated.
- PER Post Error bit, is set to one to indicate that the drive reports recovered errors.
- DTE (Data Terminate on Error) bit set to one specifies that data transfer will be halted when the first recovered

HGST Hard Disk Drive Specification 135

error is encountered. PER must be set to one when DTE is set to one. DTE set to zero will cause data transfer 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.

- Write Retry Count sets a limit on the amount of DRP passes in which the Target attempts to recover write errors. A value of zero disables all data recovery procedures.

- Recovery Time Limit indicates the period in 1 millisecond increments for the maximum recovery time of a single LBA. The value must be from 40 ms to 65535 ms (65.5 seconds).The granularity of the timer is 50ms. If an LBA is not able to be recovered within the limit, a Check Condition will be returned. The Recovery Time Limit will not be applied to Writes when WCE=1. A value of zero disables the timer.

- The following summarizes valid modes of operation. If an illegal mode is set, the MODE SELECT command will complete successfully but the action of the drive when an error occurs is undefined.

PERDTEDCRTB 0 0 0 0
0 0 0 1

DESCRIPTION

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. The drive then creates the Check Condition status with the appropriate sense key.

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.

0 0 1 0
0 0 1 1
0 1 0 0 0 1 0 1 0 1 1 0 0 1 1 1

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 transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

Retries are attempted but no error correction (LDPC) is applied. Recovered data (if any) 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. The drive then creates the Check Condition status with the appropriate sense key.

Retries are attempted but no error correction (LDPC) is applied. Recovered data (if any) 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 transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

Illegal Request-DTE must be zero when PER is zero.

Illegal Request-DTE must be zero when PER is zero.

Illegal Request-DTE must be zero when PER is zero.

Illegal Request-DTE must be zero when PER is zero.

HGST Hard Disk Drive Specification 136

1 0 0 0 1 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0

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.

no err

The transfer length is exhausted.

soft err hard err

The transfer length is exhausted. Transferred data includes blocks containing recovered errors. The information byte in the sense data will contain the LBA of the last recovered error.
Data transfer stops when an unrecoverable error is encountered. The unrecoverable block is not transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

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.

no err

The transfer length is exhausted.

soft err

The transfer length is exhausted. Transferred data includes blocks containing recovered errors. The information byte in the sense data will contain the LBA of the last recovered error.

hard err

Data transfer stops when an unrecoverable error is encountered. The unrecoverable block is not transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

The highest level error is reported at the end of transfer. Retries are attempted but LDPC is not applied. 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 hard err

The transfer length is exhausted. Transferred data includes blocks containing recovered errors. The information byte in the sense data will contain the LBA of the last recovered error.
Data transfer stops when an unrecoverable error is encountered. The unrecoverable block is not transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

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.

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 not returned to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

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.

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 not returned to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

HGST Hard Disk Drive Specification 137

1 0 1 1 1 1 1 0 1 1 1 1

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.

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. The drive then creates the Check Condition status with

the appropriate sense key.

The highest level error is reported at the end of transfer. Retries are attempted but LDPC is not applied. Recovered data 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 recovered error block is returned to the initiator. 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 not returned to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.

The highest level error is reported at the end of transfer. Retries are attempted but LDPC in not applied. 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. The drive then creates the Check Condition status with

the appropriate sense key.

HGST Hard Disk Drive Specification 138

Mode Page 02 (Disconnect/Reconnect Parameters)

Byte

7

6

0

PS

0

1

2

3

(MSB) 4-5

6-7
(MSB) 8-9

Bit

5

4

3

2

1

Page Code = 02h

Page Length = 0Eh

Read Buffer Full Ratio

Write Buffer Empty Ratio

Bus Inactivity Time Limit

Disconnect Time Limit = 0

Maximum Connect Time Limit

Default 0
82h 0Eh 00h 00h
00h (LSB)
00h
00h (LSB)

(MSB) 10-11

Maximum Burst Size

00h (LSB) A0h

12-13

Reserved = 0

00h

14-15

First Burst Size = 0

00h

Table 130 Mode Page 02 (Disconnect/Reconnect Parameters)

The disconnect/reconnect page provides the Initiator with the means to tune the performance of the SAS Link. The drive uses the disconnect/reconnect parameters to control when it attempts to regain control of the link during READ (operation code 08h and 28h) and WRITE (0Ah, 2Ah and 2E).
- Read Buffer Full Ratio is the numerator of a fraction whose denominator is 256. The fraction indicates how full the drive data buffer should be before attempting to re-arbitrate for the link. If the ratio is set to 0h, the target will calculate and use an optimal ratio based on the negotiated transfer rate.
- Bus Inactivity Time Limit specifies the maximum time that the SAS target port is permitted to maintain a connection without transferring a frame to the initiator port, specified in 100 microsecond increments. When this value is exceeded, the target port will prepare to close the connection by transmitting DONE.A value of zero indicates that there is no bus inactivity time limit.
- Disconnect Time Limit is not supported.
- Write Buffer Empty Ratio is the numerator of a fraction whose denominator is 256. The fraction indicates how empty the drive data buffer should be before attempting to re-arbitrate for the link. If the ratio is set to 0h, the target will calculate and use an optimal ratio based on the negotiated transfer rate. Both the Read Buffer Full Ratio and the Write Buffer Empty Ratio pertain to the current active notch. For each active notch as defined in page 0Ch there are separate Read Buffer Full Ratios and Write Buffer Empty Ratios. When the active notch is set to zero, the values are applied in mode page 0Ch across all notches.
- Maximum Connect Time Limit specifies the maximum amount of time the drive will keep a SAS connection open. The time is specified in 100 microsecond increments. The default value of zero indicates no time limit. A maximum value of FFFFh specifies a connection time limit of 6.55 seconds. When this time expires, the drive will prepare to close the connection.
- Maximum Burst Size field indicates the maximum amount of data that the target port shall transfer during a single data transfer operation. This value is expressed in increments of 512 bytes. A value of zero specifies there is no limit on the amount of data transferred per data transfer operation.
- First Burst Size is not supported.

HGST Hard Disk Drive Specification 139

Mode Page 03 (Format Device Parameters)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS

0

Page Code = 03h

03h

1

Page Length = 16h

16h

(MSB) 2-3

Tracks per Zone

xxh (LSB) xxh

(MSB) 4-5

Alternate Sectors per Zone = 0

00h (LSB) 00h

(MSB) 6-7

Alternate Tracks per Zone = 0

00h (LSB) 00h

(MSB) 8-9

Alternate Tracks per Logical Unit = 0

00h (LSB) 00h

(MSB) 10-11

Sectors Per Track

xxh (LSB) xxh

(MSB) 12-13

Data Bytes per Physical Sector

xxh (LSB) xxh

(MSB) 14-15

Interleave = 0001h or 0000h

00h (LSB) 01h

(MSB) 16-17

Track Skew Factor

xxh (LSB) xxh

(MSB) 18-19

Cylinder Skew Factor

xxh (LSB) xxh

20

SSEC HSEC RMB SURF

RESERVED = 0

40h

21-23

Reserved = 0

00h

Table 131 Mode Page 03 (Format Device Parameters)
The format device page contains parameters that specify the medium format. This page contains no changeable parameters.

HGST Hard Disk Drive Specification 140

- 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. - Track Skew Factor indicates the number of physical sectors between the last block of one track and the first
block on the next sequential track of the same cylinder. This field is a function of the active notch. - Cylinder Skew Factor indicates the number of physical sectors between the last block of one cylinder and the
first block on the next sequential cylinder. This field is a function of the active notch. - SSEC = Zero indicates that the drive does not support soft sector formatting. - HSEC = One indicates that the drive supports hard sector formatting. - RMB = Zero indicates that the media does not support removable Fixed Disk. - SURF = Zero indicates that progressive addresses are assigned to all logical blocks in a cylinder prior to
allocating addresses within the next cylinder.
HGST Hard Disk Drive Specification 141

Mode Page 04 (Rigid Disk Drive Geometry Parameters)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS

0

Page Code = 04h

04h

1

Page Length = 16h

16h

(MSB) 2-4

Number of Cylinders

xxh (LSB) xxh

5

Number of heads

xxh

(MSB) 6-8

Starting Cylinder Write Pre compensation = 0

00h 00h (LSB)

9-11

(MSB)

Starting Cylinder Reduced Write Current = 0

00h 00h (LSB)

(MSB) 12-13

Drive Step Rate = 0 (Not used)

00h (LSB) 00h

(MSB) 14-16

Landing Zone Cylinder = 0 (Not used)

00h (LSB) 00h

17

RESERVED = 0

RPL = 0

00h

18

Rotational Offset = 0 (Not used)

00h

19

RESERVED = 0

00h

(MSB) 20-21

Medium Rotation Rate in RPM

1Ch (LSB) 20h

22-23

Reserved = 0

00h

Table 132 Mode Page 04 (Rigid Disk Drive Geometry Parameters) The rigid disk drive geometric page specifies various parameters for the drive. - RPL = 0, Indicates that the drive does not support spindle synchronization.

HGST Hard Disk Drive Specification 142

Mode Page 07 (Verify Error Recovery Parameters)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS

0

Page Code = 07h

87h

1

Page Length = 0Ah

0Ah

2

Reserved = 0

EER=0 PER DTE DCR=0 00h

3

Verify Retry Count

01h

4

Obsolete =0

00h

5 - 9 10-11

(MSB)

Reserved = 0 Verify Recovery Time Limit

00h
00h (LSB)

Table 133 Mode Page 07 (Verify Error Recovery Parameters)
The Verify recovery parameters are used by the Target when recovering from and reporting errors associated with the verification of the Initiator's Data for the following commands:
- VERIFY
- WRITE AND VERIFY - the verify portion of the command only.
- EER This bit is 0 since the Target does not support early recovery.
- PER (post error) bit is set to one to indicate that the drive reports recovered errors. The PER and DTE bit settings in mode page 7 override those of mode page 1 during VERIFY and the Verify portion of WRITE AND VERIFY
- DTE (Data Terminate on Error) bit set to one specifies that data transfer will be halted when the first recovered error is encountered. PER must be set to one when DTE is set to one. DTE set to zero will cause data transfer to continue when recovered errors are encountered
- DCR - Reserved
- Verify Retry Count sets a limit on the amount of verify recovery procedure (VRP) passes the Target attempts when recovering verify errors. The Verify Retry Count of one causes the Target to attempt up to one VRP pass per command when a medium error occurs during a verify operation. Only values of 0h and 01h are valid. The value of 0h disables all recovery.
- Verify Recovery Time Limit indicates the period in 1 millisecond increments for the maximum recovery time of a single LBA during the verify operation. The value must be from 40 ms to 65535 ms (65.5 seconds). The granularity of the timer is 50ms. If an LBA is not able to be recovered within the limit, a Check Condition will be returned.

HGST Hard Disk Drive Specification 143

Mode Page 08 (Caching Parameters)

Byte 0 1 2 3 4-5
6-7
8-9 10-11
12 13 14-15 16 17-19

Bit

Default

7

6

5

4

3

2

1

0

PS

0

Page Code = 08h

88h

Page Length = 12h

12h

IC ABPF CAP DISC SIZE WCE MF RCD 04h

Demand Read Retention Priority

Write Retention Priority

00h

(MSB)

Disable Pre-fetch Transfer Length

FFh (LSB)

(MSB)

Minimum Pre-fetch

00h (LSB)

(MSB)

Minimum Pre-fetch

FFh (LSB)

Maximum Pre-fetch Ceiling

FFh

FSW LBCSS DRA

Reserved = 0

00h

Number of Cache Segments

08h

(MSB)

Cache Segment Size

00h (LSB)

Reserved = 0

00h

(MSB)

Non Cache Segment Size

00h (LSB)

Table 134 Page 08 (Caching Parameters)
The caching parameters page defines parameters that affect the use of the cache.
- IC (Initiator Control) bit of one specifies that the drive will honor the following parameters to control cache segmentation and pre-fetch: SIZE, FSW, LBCSS, Number of Cache Segments, Cache Segment Size. The drive will never pre-fetch less data than specified by ABPF, MF, Demand Read Retention Priority, Write Retention Priority, Disable Pre-fetch Transfer Length, Minimum Pre-fetch, Maximum Pre-fetch, and Maximum Pre-fetch Ceiling, but may pre-fetch more based on internal cache algorithms. When the IC bit is set to zero, all the parameters listed above are ignored, and an internal caching algorithm is used.
- ABPF (Abort Pre-fetch) bit of one, with DRA set to zero, causes the drive to abort the pre-fetch upon receipt of a new command. ABPF set to one takes precedence over Minimum Pre-fetch. When ABPF is zero, with DRA set to zero, the termination of any active pre-fetch is dependent upon the other parameters in this page.
- CAP (Caching Analysis Permitted) is not supported and is ignored. The IC bit can be used to enable or disable adaptive caching.
- DISC (Discontinuity) is not supported and is ignored. Pre-fetch operations will continue across cylinders, within the limits of other caching parameters on this page.
- SIZE (Size Enable) bit when set to one indicates that the Cache Segment Size is to be used to control caching segmentation. When SIZE is set to zero, the Initiator requests that the Number of Cache Segments is to be used to control caching segmentation.
- WCE (Write Cache Enable) bit when set at zero indicates that the drive must issue Good status for WRITE (6) or WRITE (10) command only after successfully writing the data to the media. When the WCE bit is set to one, the drive may issue Good status for a WRITE (6) or WRITE (10) command after successfully receiving the data but

HGST Hard Disk Drive Specification 144

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. - RCD (Read Cache Disable) bit set at zero indicates that the drive may return some or all of the data requested by a READ (6) or READ (10) command by accessing the data buffer, not the media. An RCD bit set at one indicates that the Target does not return any of the data requested by a READ (6) or READ (10) command by accessing the data buffer. All of the data requested is read from the media instead. - Demand Read Retention Priority is not supported. - Write Retention Priority is not supported. - Disable Pre-fetch Transfer Length is used to prevent read-ahead after Read commands that are longer than the specified number of blocks. If this parameter is set to zero, a read-ahead is not performed. - Minimum Pre-fetch specifies the minimum number of LBAs that the drive should after each READ command. A value of zero indicates that read ahead should be terminated immediately after a new command arrives, except when the new command is on the current head and track. - Maximum Pre-fetch specifies the maximum number of LBAs to read ahead after a Read command. - Maximum Pre-fetch Ceiling specifies the maximum number of blocks the drive should attempt to read ahead. This field is ignored. - FSW (Force Sequential Write) is not supported and is ignored. All logical blocks will be written in sequential order. - LBCSS (Logical Block Cache Segment Size) bit when set to one indicates that the Cache Segment Size field units shall be interpreted as logical blocks. When it is set to zero, the Cache Segment Size field units shall be interpreted as bytes. - DRA (Disable Read Ahead) bit when set to one request that the Target not read into the buffer any logical block beyond the addressed logical block(s). When it is set at zero, the Target may continue to read logical blocks into the buffer beyond the addressed logical block(s). - Number of Cache Segments field is used to select the number of data buffer cache segments. This parameter is valid only when the SIZE bit is set at zero. It is ignored when SIZE is set at one. - Cache Segment Size field indicates the requested segment size in Bytes or Blocks, depending upon the value of the LBCSS bit. The Cache Segment Size field is valid only when the SIZE bit is one. It is ignored when SIZE is set at zero. - Non Cache Segment Size is not supported and is ignored.
HGST Hard Disk Drive Specification 145

Mode Page 0A (Control Mode Page Parameters)

Byte 7

6

5

Bit

4

3

2

Default

1

0

0

PS

0

Page Code = 0Ah

8Ah

1

Page Length = 0Ah

0Ah

2

TST=0

TMFonly=0 DPICZ D_Sense GLTSD=0 RLEC=0 04h

3

Queue Algorithm Modifier

RSVD=0

4

RSVD=0 RAC=0 UA_INTLCK_CTRL=0 SWP=0

QErr

DQue 00h

Obsolete

00h

5

ATO TAS=0 ATMPE RWWP RSVD=0

00h

6-7

Obsolete=0

00h

8-9

(MSB) Busy Timeout Period(LSB)

00h

10-11

(MSB)Extended Self-test Routine Completion Time(LSB)

XXh

Table 135 Page 0A (Control Mode Page Parameters)
Following are parameter options for Page 0A.
- DPICZ, Disable Protection Information Check if protect field is Zero, bit set to zero indicates that checking of protection information bytes is enabled. A DPICZ bit set to one indicates that checking of protection information is disabled on commands with:
- The RDPROTECT field (see SBC-3) set to zero;
- The VRPROTECT field (see SBC-3) set to zero; or
- The ORPROTECT field (see SBC-3) set to zero. - D_Sense, Descriptor Sense Data, bit controls the format in which the drive returns sense data for
CHECK_CONDITION status:
- Setting the D_SENSE bit to 0 specifies that the drive shall return fixed format sense data for CHECK_CONDITION.
- Setting the D_SENSE bit to 1 specifies that the drive shall return descriptor format sense data for CHECK_CONDITION
- Queue Algorithm Modifier specifies restrictions on the algorithm used for reordering commands that are tagged with the SIMPLE message.
- 0h: Restricted reordering. The Target shall reorder the actual execution sequence of the queued commands from each Initiator such that data integrity is maintained for that Initiator.
- 1h: Unrestricted reordering allowed. The Target may reorder the actual execution sequence of the queued commands in any manner it selects. Any data integrity exposures related to command sequence order are explicitly handled by the Initiator through the selection of appropriate commands and queue tag messages.
- 2h-7h: RESERVED.
- 8: Command reordering is disabled
- 9-Fh: RESERVED
- QErr (Queue Error Management) The queue error management (QERR) field specifies how the device server shall handle blocked tasks when another task receives a Check Condition status.
- 00b: Specifies that all tasks from all Initiators are blocked from execution when a Continent Allegiance (CA condition) is pending. Those blocked tasks are allowed to resume execution in a normal fashion after the CA condition is cleared.

HGST Hard Disk Drive Specification 146

- 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. The sense key will be set to Unit Attention and the additional sense code will be set to Commands Cleared by Another Initiator.
- 10b: Reserved - 11b: Blocked tasks in the task set belonging to the Initiator to which a Check Condition status is sent shall
be aborted when the status is sent. - DQue (Disable Queuing) bit set at zero specifies that tagged queuing shall be enabled if the Target supports
tagged queuing. A DQue bit set at one specifies that tagged queuing shall be disabled. Command queuing is always enabled on the drive, therefore this bit is ignored. - ATO (Application Tag Owner) bit set to one specifies that the contents of the Logical Block Application Tag field in the protection information, if any, shall not be modified by the drive. An ATO bit set to zero specifies that the contents of the Logical Block Application Tag field in the protection information, if any, may be modified by the drive. If the ATO bit is set to zero, the drive will ignore the contents of the Logical Block Application Tag field in the protection information. - ATMPE (Application Tag Mode Page Enabled) bit set to zero specifies that the Application Tag mode page (see SBC-3) is disabled and the contents of logical block application tags are not defined by this standard. An ATMPE bit set to one specifies that the Application Tag mode page is enabled. If: - the ATMPE is set to one; - the ATO bit is set to one; - the value in the DPICZ bit allows protection information checking for the specified command; and - the APP_CHK bit is set to one in the Extended Inquiry VPD page; - then: - knowledge of the value of the Application Tag shall come from the values in the Application Tag mode page
as specified by the DPICZ bit. - RWWP (Reject Write Without Protection) bit set to zero specifies that write commands without protection
information (see SBC-3) shall be processed. A RWWP bit set to one specifies that write commands without protection information received by a device server that has been formatted with protection information shall be terminated with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN CDB - Busy Timeout Period is ignored - Extended Self-test Routine Completion Time specifies the time in seconds that the device server requires to complete an extended self-test provided the device server is not interrupted by subsequent commands and no errors occur during processing of the self-test. A value of FFFFh indicates that the extended self-test takes 65,535 seconds or longer. See also the EXTENDED SELF-TEST COMPLETION MINUTES field in the Extended INQUIRY Data VPD page.
HGST Hard Disk Drive Specification 147

Control Extension Subpage 01h

Bit

Byte

7

6

5

4

3

2

1

Default 0

0

PS=1 SPF=1

Page Code = 0Ah

CAh

1

Subpage Code = 1

01h

2-3

Page Length = 001Ch

001Ch

4

Reserved = 0

TCMOS=0 SCSIP=0 IALUAE = 0 00h

5

Reserved = 0

Initial Priority = 0

00h

6

Maximum Sense Data Length

00h

7-31

Reserved = 0

00h

Table 136 Control Extension Subpage
- TCMOS (Timestamp Changeable By Methods Outside This Standard): set to zero to specify that the timestamp shall not be changed by any method except those defined by this standard.
- SCSIP (SCSI Precedence): set to zero to specify that methods outside this standard may change the timestamp and that the SET TIMESTAMP command is illegal.
- IALUAE (Implicit Asymmetric Logical Unit Access Enabled): set to zero to specify that implicitly managed transitions between primary target port asymmetric access states are disallowed and indicates that implicitly managed transitions between primary target port asymmetric access states are disallowed or not supported.
- Initial Command Priority: set to zero to indicate that the device server does not support priorities with the SET PRIORITY command.
- Maximum Sense Data Length: specifies the maximum number of bytes of sense data the device server shall return in the same I_T_L_Q nexus transaction as the status. A Maximum Sense Data Length field set to zero specifies that there is no limit. The device server shall not return more sense data bytes in the same I_T_L_Q nexus transaction as the status than the smaller of the length indicated by the: - Maximum Sense Data length field; and - Maximum Supported Sense Data Length field in the Extended INQUIRY VPD page (Page 86h).

HGST Hard Disk Drive Specification 148

Control Extension Subpage 02h

Bit

Byte

7

6

5

4

3

2

1

0

0

PS SPF=1

Page Code = 0Ah

1

Subpage Code = 02h

2-3

Page Length = n-4

4-15

Reserved = 0

16-39

Application Tag descriptor [first]

...

...

(n-24)-n

Application Tag descriptor [last]

Table 137 Application Tag mode page:

Bit

Byte

7

6

5

4

3

2

1

0

0

Last

Reserved = 0

1-5

Reserved = 0

6-7

Logical Block Application Tag

8-15

Logical Block Address

16-23

Logical Block Count

Table 138 Application Tag descriptor format
- A LAST bit set to one specifies that this Application Tag descriptor is the last valid Application Tag descriptor in the Application Tag mode page. A LAST bit set to zero specifies that the Application Tag descriptor is not the last valid Application Tag descriptor in the Application Tag mode page.
- The LOGICAL BLOCK APPLICATION TAG field specifies the value to be compared with the LOGICAL LOCK APPLICATION TAG field associated with data read or written to the LBA.
- The LOGICAL BLOCK ADDRESS field contains the starting LBA for this Application Tag descriptor. The LOGICAL BLOCK ADDRESS field in the first Application Tag descriptor shall be set to 0000_0000_0000_0000h. For subsequent Application Tag descriptors, the contents of the LOGICAL BLOCK ADDRESS field shall contain the sum of the values in: a) The LOGICAL BLOCK ADDRESS field in the previous Application Tag descriptor; and b) The LOGICAL BLOCK COUNT field in the previous Application Tag descriptor.
The sum of the LOGICAL BLOCK ADDRESS field in the Application Tag descriptor with the LAST bit set to one and the LOGICAL BLOCK COUNT field in the Application Tag descriptor with the LAST bit set to one shall equal the RETURNED LOGICAL BLOCK ADDRESS field in the READ CAPACITY (16) parameter data (see 8.23 "READ CAPACITY (16)"). If an invalid combination of the LAST bit, LOGICAL BLOCK APPLICATION TAG field, and LOGICAL BLOCK ADDRESS field are sent by the application client, then the device server shall terminate the MODE SELECT command(see SPC-4) with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the 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.

HGST Hard Disk Drive Specification 149

Mode Page 0C (Notch Parameters)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS

0

Page Code = 0Ch

8Ch

1

Page Length = 16h

16h

2

ND=1 LPN=0

Reserved = 0

80h

3

Reserved = 0

00h

(MSB) 4-5

Maximum Number of Notches

XXh (LSB) XXh

(MSB) 6-7

Active Notch

00h (LSB) 00h

(MSB) 8-11

Starting Boundary

XXh (LSB) XXh

(MSB) 12-15

Ending Boundary

XXh (LSB) XXh

(MSB) 16-23

Pages Notched

(LSB)

0000h 0000h 0000h 100Ch

Table 139 Page 0C (Notch Parameters)
The notch page contains parameters for direct-access devices that implement a variable number of blocks per cylinder. Each section of the logical unit with a different number of blocks per cylinder is referred as a notch. The only field that is changeable is the Active Notch field.
- ND = One meaning that this device is a notched drive. - LPN = Zero meaning that the notches are based upon physical parameters of the drive (cylinder #), not logical
parameters. - Maximum Number of Notches is the number of notches the drive can support. This value is drive model
dependent. - Active Notch indicates to which notch subsequent MODE SELECT/SENSE command parameters pertain. A
value of 0 is used for parameter values which apply to all notches. Values from 1 to the maximum value depending on the model specify the notch number, where notch 1 is the outermost notch. Following mode parameters are based on the current active notch: - Mode Page 2
- Read Buffer Full Ratio
- Write Buffer Empty Ratio

HGST Hard Disk Drive Specification 150

- 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. The first three bytes are the cylinder
number and the last byte is the head. The value sent in this field is ignored. - Pages Notched is a bit map of the mode page codes that indicates which pages contain parameters that may
be different for different notches. The most significant bit of this field corresponds to page code 3Fh and the least significant bit corresponds to page code 00h. If a bit is one, then the corresponding mode page contains parameters that may be different for different notches. If a bit is zero, then the corresponding mode page contains parameters that are constant for all notches.
Mode Page 18h

Byte
0 1 2 3

Bit

7

6

5

4

3

2

1

0

PS=0 SPF=0

Page Code = 18h

Page Length = 6h

Reserved

Transport Layer Retries=0 Protocol Identifier = 6h

Reserved = 0

Default
18h 6h 6h 00h

4-7

Reserved

00h

Table 140 Page 18h (Protocol-Specific Logical Unit mode page)
This page defined protocol-specific parameters that affect the logical unit.
- Transport Layer Retries is unchangeable and set to zero. The drive does not support Transport Layer Retries as defined in SAS 1.1.

HGST Hard Disk Drive Specification 151

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.
Short Format of Port Control Page

Byte

7

6

Bit

5

4

3

2

1

0

0

PS

SPF=0

Page Code = 19h

1

Page Length = 0Eh

2

Reserved Continue AWT

Broadcast Asynchronous
Event

Ready LED Meaning

Protocol Identifier = 6h

Default 99h 0Eh 06h

3

Reserved

00h

(MSB) 4-5
(MSB) 6-7
(MSB) 8-9

I_T Nexus Loss Timer Initiator Response Timeout
Reject to Open Limit

07h-D0h (LSB)
07h-D0h (LSB)
0000h (LSB)

10-15

Reserved

00h

Table 141 Short (Port Control Parameters) Short Format
 PS Parameters Savable is set to 1, indicating the parameters are saveable
 SPF shall be set to zero for access to the short format mode page
 Continue AWT bit set to one specifies that the SAS port shall not stop the Arbitration Wait Time timer and set the Arbitration Wait Time timer to zero when the SAS port receives an OPEN_REJECT (RETRY). A CONTINUE AWT bit set to zero specifies that the SAS port shall stop the Arbitration Wait Time timer and set the Arbitration Wait Time timer to zero when it receives an OPEN_REJECT (RETRY).
 Broadcast Asynchronous Event bit set to one specifies that the device server shall enable origination of Broadcast (Asynchronous Event). A BROADCAST ASYNCHRONOUS EVENT bit set to zero specifies that the device server shall disable origination of Broadcast (Asynchronous Event).
 Ready LED Meaning specifies the READY LED signal behavior. In general, when the bit is 0, and the drive is in a ready state, the LED is usually on, but flashes on and off when commands are processed. When the bit is 1, the LED is usually off, but flashes on and off when commands are processed. For additional implementation specifics, see the SAS standards.
 Protocol Identifier has a value of 6h indicating this is a SAS SSP specific mode page
 I_T Nexus Loss Time contains the time (in milliseconds) that our SSP target port shall retry connection requests to an SSP initiator port that are rejected with responses indicating the SSP initiator port may no longer be present before recognizing an I_T nexus loss. A value of 0 indicates a vendor specific amount of time and defaults to a 2 second time period. A value of FFFFh indicates an unlimited period. The default value of 7D0h, specifies a 2 second time period.

HGST Hard Disk Drive Specification 152

 Initiator Response Timeout contains the time in milliseconds that the SSP target port shall wait for the receipt of a Data frame after sending the XFER_RDY frame requesting data. When the INITIATOR RESPONSE 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.
 Reject to Open Limit contains the minimum time in 10 µs increments that the target port shall wait to establish a connection request with an initiator port on an I_T nexus after receiving an OPEN_REJECT (RETRY), OPEN_REJECT (CONTINUE 0), or OPEN_REJECT (CONTINUE 1). This value may be rounded as defined in SPC-4. A REJECT TO OPEN LIMIT field set to 0000h indicates that the minimum time is vendor specific. This minimum time is enforced by the transport layer.
Long Format of Port Control Page

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS SPF=1

Page Code = 19h

D9h

1

Subpage Code

...

(MSB) 2-3

Page Length (n-3)

0000h (LSB)

4

Reserved

00h

5

Reserved

Protocol Identifier = 6h

06h

6

...

Protocol Specific Mode Parameters

n

...

Table 142 Long Format of Port Control Page
The drive maintains an independent set of port control mode page parameters for each SAS initiator port.
 SPF field shall be set to one for access to the long format mode page.  Subpage Code indicates which subpage is being accessed. The drive supports the following subpage codes.
If the Subpage Code is not supported, the drive returns a CHECK CONDITION status, the sense key is set to ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN PARAMETER LIST. - 01h: PHY Control and Discover Subpage - 02h: Shared Port Control subpage - FFh: All supported subpages.  Page Length specifies the length in bytes of the subpage parameters after the Page Length.
 Protocol Identifier has a value of 6h indicating this is a SAS SSP specific mode page.

HGST Hard Disk Drive Specification 153

PHY Control and Discover (Subpage 1)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS SPF=1

Page Code = 19h

D9h

1

Subpage Code = 1

01h

(MSB) 2-3

Page Length = 0064h

0064h (LSB)

4

Reserved

00h

5

Reserved

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

...

Table 143 PHY Control and Discover (Subpage 1)
The PHY Control and Discover subpage contains PHY-specific parameters. MODE SENSE command returns the current settings for the initiator.
 Protocol Identifier has a value of 6h indicating this is a SAS SSP specific mode page.  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). The GENERATION CODE field is also contained in the Protocol-Specific Port log page and may be used to correlate PHY settings across mode page and log page accesses.  Number of PHYS is set to 2, to represent the dual ported drive (one PHY per port)  SAS PHY Mode Descriptor are defined in Table 144. There are two SAS PHY Mode Descriptor fields, one per port.

HGST Hard Disk Drive Specification 154

Byte 0 1
2-3

7 (MSB)

4

Reserved

5

6

Bit

6

5

4

3

2

1

0

Reserved

PHY Identifier

Attached Device Type Reason
Reserved

Reserved

(LSB)

Attached Reason Negotiated Logical Link Rate

Attached SSP
Initiator Port

Attached STP
Initiator Port

Attached SMP
Initiator Port

Reserved

Attached Attached Attached

7

Reserved

SSP Target

STP Target

STP Target

Reserved

Port

Port

Port

8-15

(MSB)

SAS Address

(LSB)

(MSB) 16-23

24

Attached

25

Persistent

Capable

Attached Power Capable

Attached SAS Address

(LSB)

Attached PHY Identifier

Attached Slumber Capable

Attached Partial Capable

Attached Inside ZPSDS
Persistent

Attached Requested
Inside ZPSDS

Attached Break_Reply
Capable

26-31
32 33
34-41

(MSB)

Reserved

(LSB)

Programmed Minimum Physical Link Rate Programmed Maximum Physical Link Rate

Hardware Minimum Physical Link Rate Hardware Maximum Physical Link Rate

(MSB)

Reserved

(LSB)

(MSB) 42-43
(MSB) 44-47

Vendor specific Reserved

(LSB) (LSB)

Table 144 SAS PHY Mode Descriptor
 PHY Identifier indicates the unique PHY Identifier for the PHY associated with the other data in this SAS PHY Mode Descriptor Page.

HGST Hard Disk Drive Specification 155

 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 33.
 Attached Device Type indicates the value of the DEVICE TYPE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 Attached SAS Address indicates the value of the attached SAS address in the last received IDENTIFY address frame associated with the PHY Identifier list in this SAS PHY Mode Descriptor. See Table 33.
 Attached PHY Identifier: indicated the value of the attached PHY Identifier field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 SAS Address contains the unique Port Identifier for the Port associated with the PHY Identifier listed in this SAS PHY Mode Descriptor
 Hardware Minimum Physical Link Rate is the minimum link rate supported by the Port associated with the PHY Identifier listed in this SAS PHY Mode Descriptor.
 Hardware Maximum Physical Link Rate is the maximum link rate supported by the Port associated with the PHY Identifier listed in this SAS PHY Mode Descriptor.
 Programmed Minimum Physical Link Rate is the current minimum link rate used during speed negotiation by the Port associated with the PHY Identifier listed in this SAS PHY Mode Descriptor.
 Programmed Maximum Physical Link Rate is the current maximum link rate used during speed negotiation by the Port associated with the PHY Identifier listed in this SAS PHY Mode Descriptor.
 Attached Persistent Capable indicates the value of the PERSISTENT CAPABLE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33
 Attached Power Capable indicates the value of the POWER CAPABLE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33 Identify Address FrameTable 33.
 Attached Slumber Capable indicates the value of the SLUMBER CAPABLE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 Attached Partial Capable indicates the value of the PARTIAL CAPABLE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 Attached Inside ZPSDS Persistent indicates the value of the INSIDE ZPSDS PERSISTENT field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 Attached Requested Inside ZPSDS indicates the value of the REQUESTED INSIDE ZPSDS field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
 Attached Break_Reply Capable indicates the value of the BREAK_REPLY CAPABLE field in the last received IDENTIFY address frame associated with the PHY Identifier listed in this SAS PHY Mode Descriptor. See Table 33.
HGST Hard Disk Drive Specification 156

Shared Port Control (Subpage 2)

Byte
0 1 2-3 4 5 6-7 8-15

Bit

7

6

5

4

3

2

1

0

PS SPF=1

Page Code = 19h

Subpage Code = 2

Page Length = 000Ch

Reserved = 0

Reserved

Protocol Identifier = 6

Power Loss Timeout

Reserved

Default
D9h 02h 000Ch 00h 06h 0000h 00h

Table 145 Shared Port Control (Subpage 2)
 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. A POWER LOSS TIMEOUT field set to 0000h specifies that the maximum time is vendor-specific and automatically defaults to 2 seconds.

Enhanced PHY Control Mode Page (Subpage 3)

Byte
0 1 2-3 4 5 6 7 8-27 28-47

Bit

7

6

5

4

3

2

1

0

PS SPF=1

Page Code 19h

Subpage Code = 3

Page Length = 002Ch

Reserved

Reserved

Protocol Identifier = 6

Generation Code

Number of PHYs = 02h

SAS PHY Mode Descriptor 0

SAS PHY Mode Descriptor 1

Default
D9h 03h 002Ch 00h 06h 00h 02h
---

Table 146 Subpage 3

 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 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). The GENERATION CODE field is also contained in the Protocol-Specific Port log page and may be used to correlate PHY settings across mode page and log page accesses.

HGST Hard Disk Drive Specification 157

Byte
0 1 2-3 4-7 8-11 12-15 16-17 18

7

6

5

Reserved

Bit

4

3

2

1

0

Reserved

PHY Identifier

Descriptor Length (0010h)

Programmed PHY Capabilities

Current PHY Capabilities

Attached PHY Capabilities

Reserved

Negotiated SSC

Negotiated Physical Link Rate

19

Reserved

Enable Enable Hardware Mixing Slumber=0 Partial=0 Supported='0'

Table 147 PHY Mode Descriptor (0 and 1)  PHY Capabilities are defined under the "SAS Speed Negotiation"

Mode Page 1A (Power Control)

Byte
0 1 2 3 4-7 8-11 12-15 16-19 20-23 24-38 39

Bit

Default

7

6

5

4

3

2

1

0

PS

SPF (0b)

Page Code = 1Ah

9Ah

Page Length = 26h

26h

PM_BG_PRECEDENCE

Reserved = 0

Standby_Y 00h

Reserved = 0

Idle_C Idle_B Idle_A Standby_Z 06h

Idle_A Condition Timer

14h

Standby_Z Condition Timer

00h

Idle_B Condition Timer

1770h

Idle_C Condition Timer

00h

Standby_Y Condition Timer

00h

Reserved

00h

CCF_IDLE

CCF_STANDBY CCF_STOPPED

Reserved

58h

Table 148 Page 1A (Power Control)
- If the STANDBY_Y bit is set to one, then the standby_y condition timer is enabled. If the STANDBY_Y bit is set to zero, then the device shall ignore the standby_y condition timer.
- If the IDLE_C bit is set to one, then the idle_c condition timer is enabled. If the IDLE_C bit is set to zero, then the device shall ignore the idle_c condition timer.
- If the IDLE_B bit is set to one, then the idle_b condition timer is enabled. If the IDLE_B bit is set to zero, then the device shall ignore the idle_b condition timer.
- If the IDLE_A bit is set to one, then the idle_a condition timer is enabled. If the IDLE_A bit is set to zero, then the device shall ignore the idle_c condition timer.

HGST Hard Disk Drive Specification 158

- If the STANDBY_Z bit is set to one, then the standby_z condition timer is enabled. If the STANDBY_Z bit is set to zero, then the device shall ignore the standby_z condition timer.
- The IDLE_A Condition Timer field specifies the initial value, in 100 millisecond increments, for the idle_a power condition timer. The minimum allowable inactivity time for idle_a is 1 second. Any value less than this is accepted, but will automatically default to 1 second.
- The STANDBY_Z Condition Timer field specifies the initial value, in 100 millisecond increments, for the standby_z power condition timer. The minimum allowable inactivity time for standby_z is 2 minutes. Any value less than this is accepted, but will automatically default to two minutes. In addition, a limit of 60 timer initiated head unloads per 24 hour period is enforced.
- The IDLE_B Condition Timer field specifies the initial value, in 100 millisecond increments, for the idle_b power condition timer. The minimum allowable inactivity time for idle_b is 2 minutes. Any value less than this is accepted, but will automatically default to two minutes. In addition, a limit 60 timer initiated head unloads per 24 hour period is enforced.
- The IDLE_C Condition Timer field specifies the initial value, in 100 millisecond increments, for the idle_c power condition timer. The minimum allowable inactivity time for idle_c is 2 minutes. Any value less than this is accepted, but will automatically default to two minutes. In addition, a limit of 60 timer initiated head unloads per 24 hour period is enforced.
- The STANDBY_Y Condition Timer field specifies the initial value, in 100 millisecond increments, for the standby_y power condition timer. The minimum allowable inactivity time for standby_y is 2 minutes. Any value less than this is accepted, but will automatically default to two minutes. In addition, a limit60 timer initiated head unloads per 24 hour period is enforced.
- The PM_BG_PRECEDENCE field (see Table 149) specifies the interactions between background functions and 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. 10b: Returning CHECK CONDITION status if transition was from a standby power condition is enabled, 11b: reserved
- CCF Stopped CHECK CONDITION if stopped, 00b: restricted. 01b: Returning CHECK CONDITION status if transition was from a stopped power condition is disabled. 10b: Returning CHECK CONDITION status if transition was from a stopped power condition is enabled, 11b: reserved
HGST Hard Disk Drive Specification 159

Code 00h
01b

Vendor Specific
Vendor Specific ­ Background operations take precedence over maintaining low power conditions (same as 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 required to perform the background function, when: a) a timer associated with a background scan operation expires, and that function is enabled or b) an event occurs to initiate a device specific background function, and that function is enabled; 2) the logical unit shall perform the background function(s) based on the definitions in this standard and other command standards (e.g., if the device server receives a command while performing a background function, then the logical unit shall suspend the function to process the command); 3) if more than one condition is met to initiate a background function, then: a) all initiated background functions shall be performed; and b) the order of performing the functions is vendor specific; and 4) when all initiated background functions have been completed, the device server shall check to see if any power condition timers have expired. If any power condition timer has expired, then the logical unit shall change to the power condition associated with the highest priority timer that has expired; or b) if the logical unit is performing a background function, and a power condition timer expires, then the logical unit shall perform all initiated background functions before the logical unit changes to a power condition associated with a timer has expired

Maintaining low power conditions take precedence over performing background functions as follows:

a) if the logical unit is in a low power condition, then the logical unit shall not change from that power

condition to perform a background function;

b) the device server may perform any initiated and enabled background function based on the

definitions in this standard or other command standards, if all of the following are true:

A) a condition is met to initiate a background function;

B) that background function is enabled;

C) the logical unit changes to a power condition in which the background function may be performed

10b

(e.g., the device server processes a medium access command causing the logical unit to change its

power condition to continue processing that command); and

D) all outstanding application client requests have been completed;

or

c) if the logical unit is performing a background function, and a power condition timer expires that

causes a change to a power condition in which the logical unit is unable to continue performing the

background function, then the logical unit shall:

A) suspend the background function; and

B) change to the power condition associated with the timer that expired.

11b Reserved = 0

Table 149 PM_BG_PRECEDENCE field

HGST Hard Disk Drive Specification 160

Mode Page 1C (Informational Exceptions Control)

Byte 7

Bit

6

5

4

3

2

1

Default 0

0

PS

0

Page Code = 1Ch

9Ch

1

Page Length = 0Ah

0Ah

2

PERF RSVD

EBF

EWASC DEXCPT TEST

EBACK ERR

LOGERR

10h

3

Reserved = 0

Method of Reporting

03h

(MSB) 4-7
(MSB) 8-11

Interval Timer Report Count

00h
00h
00h (LSB)
00h
00h (LSB)

Table 150 Page 1C (Informational Exceptions Control)
- PERF (Performance) bit is not supported and is ignored. Informational Exception operations will not cause performance delays.
- EBF (Enable Background Function) bit is not supported and is ignored. Background functions are always enabled.
- EWASC (Enable Warning ASC) bit of zero indicates that Temperature Warnings will not be reported. An EWASC bit of one allows Temperature Warnings to be reported, if the temperature inside the disk enclosure exceeds the threshold set in Mode Page 00h.The Method of Reporting field controls the reporting method. EWASC is independent of DEXCPT.
- DEXCPT (Disable Exception Control) bit of zero indicates information exception operations are enabled. The reporting of information exception conditions when the DEXCPT bit is set to zero is determined from the Method of Reporting field. A DEXCPT bit of one indicates the Target disabled all information exception operations.
- TEST bit of one instructs the drive to generate false drive notifications at the next interval time, (as determined by the INTERVAL TIMER field), if the DEXCPT is zero. The Method of Reporting and Report Count would apply. The false drive failure is reported as sense qualifier 5DFFh. The TEST bit of zero instructs the drive to stop generating any false drive notifications.
- Enable Background Error (EBACKERR) bit of zero disables reporting of background self-test errors and background scan errors via Information Exceptions Control. An EBACKERR bit of one enables reporting of these background errors as Information Exception Warnings. The method of reporting these errors is determined from the MRIE field.
- LOGERR (Log Errors) is not used and ignored internally by the Target.
- Method of Reporting Informational Exceptions indicates the methods used by the Target to report informational exception conditions.
-

HGST Hard Disk Drive Specification 161

Code 0h 1h 2h 3h
4h
5h
6h
7h-Fh

Description
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. The command that has the Check Condition is not executed before the informational exception condition is reported.
Conditionally generate recovered error: This method instructs the Target to report informational exception conditions, dependent on the value of the PER bit of the error recovery parameters mode page, by returning a Check Condition status on any command. The sense key is set to Recovered Error and the additional sense code indicates the cause of the informational exception condition. The command that has the Check Condition completes without error before any informational exception condition is reported.
Unconditionally generate recovered error: This method instructs the Target to report informational exception conditions, regardless of the value of the PER bit of the error recovery parameters mode page, by returning a Check Condition status on any command. The sense key is set to Recovered Error and the additional sense code indicates the cause of the informational exception condition. The command that has the Check Condition completes without error before any informational exception condition is reported.
Generate no sense: 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 No Sense and the additional sense code indicates the cause of the informational exception condition. The command that has the Check Condition completes without error before any informational exception condition is reported.
Only report informational exception condition on request: This method instructs the Target to preserve the informational exception(s) information. To find out about information exception conditions the Application Client polls the Target by issuing an unsolicited Request Sense command. The sense key is set to No Sense and the additional sense code indicates the cause of the informational exception condition.
Reserved.

- Interval Timer field indicates the period in 100 millisecond increments for reporting that an informational exception condition has occurred. The target shall not report informational exception conditions more frequently than the time specified by the Interval Timer field and as soon as possible after the time interval has elapsed. After the informational exception condition has been reported the interval timer is restarted. A value of zero or 0xFFFFFFFF in the Interval Timer field indicates that the target only reports the informational exception condition one time and will override the value set in the Report Count Field.
- Report Count Field indicates the number of times the Target reports an informational exception condition. The Report Count of ZERO indicates no limits on the number of times the Target reports an informational exception condition.

HGST Hard Disk Drive Specification 162

Background Control (Subpage 01h)

Bit

Byte

Default

7

6

5

4

3

2

1

0

0

PS SPF=1

Page Code = 1Ch

DCh

1

Subpage Code = 01h

01h

2-3

Page Length = 0Ch

000Ch

4

Reserved = 0

S_L_Full LOWIR EN_BMS 01h

5

Reserved = 0

EN_PS 00h

6-7

Background Medium Scan Interval Time

00A8h

8-9

Background Pre-Scan Time Limit

0000h

10-11

Minimum Idle Time Before Background Scan

0000h

12-13

Maximum Time To Suspend Background Scan (Ignored)

0000h

14-15

Reserved = 0

0000h

Table 151 Background Control (Subpage 01h)
- Suspend on Log Full (S_L_FULL) bit set to zero allows background scans to continue if the results log (Log Sense Page 15h) is full.S_L_FULL bit set to one will cause background scans to suspend when the log is full.
- Log Only When Intervention Required (LOWIR) bit set to zero allows logging of all medium errors in the results log (Log Sense Page 15h).When the LOWIR bit is set to one, only unrecovered medium errors will be logged.
- EN_BMS (Enable Background Medium Scan) bit set to zero specifies that the background medium scan is disabled. EN_BMS bit set to one specifies that background medium scan operations are enabled. If a background medium scan is in progress when the EN_BMS bit is changed from one to zero, then the medium scan shall be suspended until the EN_BMS bit is set to one, at which time the medium scan shall resume from the suspended location.
- EN_PS (Enable Pre-Scan) bit set to zero specifies that the pre-scan is disabled. If a pre-scan operation is in progress when EN_PS is changed from a one to a zero, then pre-scan is halted. An EN_PS bit set to one specifies that a pre-scan operation is started after the next power-on cycle. Once this pre-scan has completed, another pre-scan shall not occur unless the EN_PS bit is set to zero, then set to one, and another power-on cycle occurs.
- Background Medium Scan Interval Time specifies the minimum time, in hours, between the start of one background medium scan operation and the start of the next background medium scan operation.
- Background Pre-Scan Time Limit specifies the maximum time, in hours, for a pre-scan operation to complete. If the pre-scan operation does not complete within the specified time, then it is halted. A value of zero specifies an unlimited time limit.
- Minimum Idle Time Before Background Scan specifies the minimum time, in milliseconds, that the drive must be idle before resuming a background media scan or pre-scan. A value of zero will be treated as the default value of 1.0 second. Any value less than 100 milliseconds will be treated as 100 milliseconds. The internal timer granularity is 50 milliseconds.
- Maximum Time To Suspend Background Scan (Ignored).

HGST Hard Disk Drive Specification 163

MODE SENSE (5A)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 5Ah

1

Reserved = 0

LLBAA DBD

Reserved = 0

2

PCF

Page Code

3

Subpage code

4-6

Reserved = 0

7-8 (MSB)

Allocation Length

(LSB)

9

VU = 0

Reserved = 0

FLAG LINK

Table 152 Mode Sense (5A)
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. - Long LBA Accepted (LLBAA) bit set to zero ensures that if a Block Descriptor is present it must be a Short LBA
Block Descriptor. If the LLBAA bit is set to one, the Long LBA Block Descriptor may be used.

HGST Hard Disk Drive Specification 164

PERSISTENT RESERVE IN (5E)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 5Eh

1

Reserved = 0

Service Action

2-6

Reserved = 0

(MSB) 7-8

Allocation Length

(LSB)

9

VU = 0

Reserved = 0

FLAG LINK

Table 153 Persistent Reserve In (5E)
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).
The Allocation Length indicates how much space has been allocated for the returned parameter data. If the length is not sufficient to contain all parameter data, the first portion of the data will be returned. If the remainder of the data is required, the initiator should send a new PERSISTENT RESERVE IN command and an Allocation Length large enough to contain all data.
Service Action
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.

Code Name

Descriptions

00h

Read Keys

Reads all registered Reservation Keys

01h

Read Reservations Reads all current persistent reservations

02h

Report Capabilities

Returns capability information

03h

Read Full Status

Reads complete information about all registrations and the persistent reservation, if any

04h-1Fh Reserved

Reserved

Table 154 PERSISTENT RESERVE IN, Service Action Codes

HGST Hard Disk Drive Specification 165

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)

8-15

(MSB)

First reservation key

(LSB)

:

(MSB) (n-7) - n

Last reservation key

(LSB)

Table 155 PERSISTENT RESERVE IN, parameter data for Read Keys
Generation is a counter that increments when PERSISTENT RESERVE OUT command with "Register" or "Preempt and Clear" completes successfully. Generation is set to 0 as part of the power on reset process and hard reset process. The Generation field contains a 32-bit counter that the Target shall increment every time a PERSISTENT RESERVE OUT command requests a Register, a Clear, a Preempt, or a Preempt and Abort service action. The counter shall not be incremented by a PERSISTENT RESERVE IN command, by a PERSISTENT RESERVE OUT command that performs a Reserve or Release service action, or by a PERSISTENT RESERVE OUT command that is not performed due to an error or reservation conflict. Regardless of the APTPL value the generation value shall be set to 0 as part of the power on reset process. The Additional Length field contains a count of the number of bytes in the reservation key list. If the allocation length specified by the PERSISTENT RESERVE IN command is not sufficient to contain the entire parameter list, then only the bytes from 0 to the maximum allowed allocation length shall be sent to the Initiator. The incremental remaining bytes shall be truncated, although the Additional Length field shall still contain the actual number of bytes in the reservation key list without consideration of any truncation resulting from an insufficient allocation length. This shall not be considered an error. The Reservation Key list contains the 8-byte reservation keys for all Initiators that have registered through all ports with the Target.

HGST Hard Disk Drive Specification 166

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)

Table 156 PERSISTENT RESERVE IN, parameter data for Read Reservations
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). If the Allocation length specified by the PERSISTENT RESERVE IN command is not sufficient to contain the entire parameter list, then only the bytes from 0 to the maximum allowed allocation length shall be sent to the Initiator. The remaining bytes shall be truncated, although the Additional Length field shall still contain the actual number of bytes of the Reservation Descriptor(s) and shall not be affected by the truncation. This shall not be considered an error. The format of the Reservation Descriptors is defined in the Persistent Reserve in Reservation Descriptor table. There shall be a Reservation Descriptor for the persistent reservation, if any, present in the Target having a persistent reservation.

Bit

Byte

7

6

5

4

3

2

1

0

(MSB) 0-7

Reservation key

(LSB)

8-11

(MSB)

Scope-specific address

(LSB)

12

Reserved

13

Scope=0

Type

14-15

(MSB)

Extent Length=0

(LSB)

Table 157 PERSISTENT RESERVE IN, Read Reservation Descriptor
The Scope of each persistent reservation created by a PERSISTENT RESERVE OUT command will be returned. See the PERSISTENT RESERVE OUT command section for details.

HGST Hard Disk Drive Specification 167

PERSISTENT RESERVE OUT (5F)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 5Fh

1

Reserved = 0

Service Action

2

Scope=0

Type

3-6

Reserved = 0

7-8

Parameter List Length = 18h

9

VU = 0

Reserved = 0

FLAG LINK

Table 158 PERSISTENT RESERVE OUT (5F)
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. This command is used in conjunction with the PERSISTENT RESERVE IN command, and should not be used with the RESERVE and RELEASE commands.
Note: If a PERSISTENT RESERVE OUT command is received when a RESERVE is active for the drive, the command will be rejected with Reservation Conflict status.
Parameter List Length must be 18h. If not, Check Condition status will be returned, with sense key of Illegal Request and additional sense code of Parameter List Length Error.
Service Action
The following service action codes are supported.

Code

Name

Description

00h Register

Register a reservation key

01h Reserve

Create a persistent reservation using a reservation key

02h Release

Release a persistent reservation

03h Clear

Clear all reservation keys and all persistent reservations

04h Preempt

Preempt persistent reservations from another Initiator

05h Preempt and Abort

Preempt persistent reservations from another Initiator and clear the task set for the preempted Initiator

06h Register and Ignore existing key Register a reservation key

07h-1Fh Reserved

Reserved

Table 159 PERSISTENT RESERVE OUT, Service Action Code

HGST Hard Disk Drive Specification 168

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.

Code

Name

Description

0h

Reserved

Reserved

Reads Shared: Any initiator may execute commands that transfer from the

1h

Write Exclusive

media. Writes Exclusive: Only the initiator with the reservation may execute commands that transfer data to the media; Reservation Conflict status will be

returned to other initiators.

2h

Reserved

Reserved

Reads Exclusive: Only the initiator with the reservation may execute commands

that transfer data from the media; Reservation Conflict status will be returned to

3h

Exclusive Access

other initiators. Writes Exclusive: Only the initiator with the reservation may execute commands

that transfer data to the media; Reservation Conflict status will be returned to

other initiators.

4h

Reserved

Reserved

5h

Write Exclusive Registrants Only

Reads Shard: Any initiator may execute commands that transfer from media. Writes Exclusive: Only registered initiators may execute commands that transfer data to the media; Reservation Conflict status will be returned to other initiators.

Reads Exclusive: Only registered initiators may execute commands that

transfer data from the media; Reservation Conflict status will be returned to other

6h

Exclusive Access initiators. Registrants Only Writes Exclusive: Only registered initiators may execute commands that

transfer data to the media; Reservation Conflict status will be returned to other

initiators.

7h-Fh

Reserved

Reserved

Table 160 PERSISTENT RESERVE OUT, Type Code
The RESPONSE frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data).

HGST Hard Disk Drive Specification 169

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.

Bit

Byte

7

6

5

4

3

2

1

(MSB)

0-7

Reservation Key

8-15

(MSB)

Service Action Reservation Key

0 (LSB) (LSB)

(MSB) 16-19

Reserved = 0

(LSB)

20

Reserved = 0

SPEC_I_P ALL_TG_PT Reserved = 0 APTPL

21-23

Reserved = 0

Table 161 Parameter List
Reservation Key contains an 8-byte value provided by the initiator, and identifies the initiator that issued the PERSISTENT RESERVE OUT command. The Reservation Key must match the registered reservation key for the initiator for all service actions except REGISTER and REGISTER AND IGNORE EXISTING KEY.
Service Action Reservation Key contents vary based on the service action. For REGISTER and REGISTER AND IGNORE EXISTING KEY, the Service Action Reservation Key must contain the new reservation key to be registered. For PREEMPT and PREEMPT AND ABORT, the field contains the reservation key of the persistent reservation that is being preempted. This field is ignored for all other service actions.
If the Specify Initiator Ports (SPEC_I_PT) bit is set to zero, the device server shall apply the registration only to the I_T nexus that sent the PERSISTENT RESERVE OUT command. If the SPEC_I_PT bit is set to one for any service action except the REGISTER service action, then the command shall be terminated with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST. If the SPEC_I_PT bit is set to one for the REGISTER service action, the additional parameter data (see table XXX) shall include a list of transport IDs and the device server shall also apply the registration to the I_T nexus for each initiator port specified by a Transport ID. If a registration fails for any initiator port (e.g., if the logical unit does not have enough resources available to hold the registration information), no registrations shall be made, and the command shall be terminated with CHECK CONDITION status. For Transport IDs, The All Target Ports (ALL_TG_PT) bit is valid only for the REGISTER service action and the REGISTER AND IGNORE EXISTING KEY service action, and shall be ignored for all other service actions. Support for the ALL_TG_PT bit is optional. If the device server receives a REGISTER service action or a REGISTER AND IGNORE EXISTING KEY service action with the ALL_TG_PT bit set to one, it shall create the specified registration on all target ports in the SCSI target device known to the device server (i.e., as if the same registration request had been received individually through each target port). If the device server receives a REGISTER service action or a REGISTER AND IGNORE EXISTING KEY service action with the ALL_TG_PT bit set to zero, it shall apply the registration only to the target port through which the PERSISTENT RESERVE OUT command was received.
APTPL (Activate Persist Through Power Loss) bit is valid only for REGISTER and REGISTER AND IGNORE EXISTING KEY, and is ignored for all other service actions. If the last valid APTPL bit value received is zero, power loss will cause all persistent reservations to be released, and all reservation keys to be removed. If the last valid APTPL bit value received is one, any persistent reservation and all reservation keys for all initiators will be retained across 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).

HGST Hard Disk Drive Specification 170

Summary

Service Action
(0) Register (1) Reserve (2) Release (5) Preempt and Abort

Scope Type ignore apply apply apply

Rsv Key verify verify verify verify

Parameters SvcAct S-spec RsvKey addr
save ignore ignore ignore ignore ignore save Ignore

Extent length ignore ignore ignore ignore

APTPL
apply ignore ignore ignore

Generation counter
+ 1 ----+ 1

Table 162 PERSISTENT RESERVE OUT, Service Action, Parameters

Scope, Type

The Scope and the Type are applied in the process for the Reserve, Release, and Preempted and Clear service action but they are ignored in the process for the Register service action because they are not used.

Reservation Key

The Reservation Key is verified in each service action process. If the Initiator that registered a key is different from the Initiator requesting PERSISTENT RESERVE OUT command, the drive returns a Reservation Conflict status.

Service Action Reservation Key

On Register service action, the drive saves the key specified in the Service Action Reservation Key field as a key of Initiator requesting PERSISTENT RESERVE OUT command. On Preempt and Clear service action, the reservation that has a key specified in the Service Action Reservation Key field is preempted. On other service actions, this field is ignored.

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.

Information held by the drive
Registration Persistent Reservation Generation counter

The last valid APTPL value 0
all keys are set to 0 all are removed set to 0

Information held by the drive
1 retained retained set to 0

Table 163 APTPL and information held by a drive

Generation counter

The drive increments the Generation counter when Register service action or Preempt and Clear service action complete successfully.

HGST Hard Disk Drive Specification 171

PRE-FETCH (34)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 34h

1

Reserved = 0

Reserved = 0

Immed = 0 Obsolete

(MSB) 2-5

Logical Block Address

(LSB)

6

Reserved = 0

(MSB) 7-8

Transfer Length

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 164 PRE-FETCH (34)
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. A transfer length of zero indicates that blocks are to be transferred into the cache until the segment is filled or until the last block on the media.
- Immed (Immediate) must be zero. An immediate bit of zero indicates that the status shall not be returned until the operation has completed.
If the Immed bit is set to one, the drive returns a Check Condition status. The sense key shall be set to Illegal Request and the additional sense code shall be set to Invalid Field in CDB.

HGST Hard Disk Drive Specification 172

PRE-FETCH (90)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 90h

1

Reserved = 0

Reserved = 0

Immed = 0 Reserved = 0

(MSB) 2-9

Logical Block Address

(LSB)

10-13

Transfer Length

14

Restricted For MMC-4

Reserved = 0

GROUP NUMBER = 0

15

VU = 0

Reserved = 0

FLAG

LINK

Table 165 PRE-FETCH (90)
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. A transfer length of zero indicates that blocks are to be transferred into the cache until the segment is filled or until the last block on the media.
- Immed (Immediate) must be zero. An immediate bit of zero indicates that the status shall not be returned until the operation has completed.
If the Immed bit is set to one, the drive returns a Check Condition status. The sense key shall be set to Illegal Request and the additional sense code shall be set to Invalid Field in CDB6) - (08)

HGST Hard Disk Drive Specification 173

READ (6) - (08)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 08h

1

Reserved = 0

(MSB) LBA

2-3

Logical Block Address

(LSB)

4

Transfer Length

5

VU = 0

Reserved = 0

FLAG LINK

Table 166 READ (6) - (08)
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. - Transfer length field specifies the number of blocks to be transferred. A value of zero implies 256 blocks are to
be transferred.
Note: Error recovery procedure (ERP) handles errors. The error recovery parameters specified by the MODE SELECT command control ERPs. If the drive is formatted with protection information, no protection information will be transmitted or checked.

HGST Hard Disk Drive Specification 174

READ (10) - (28)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 28h

1

RDPROTECT

DPO

FUA RSVD=0 FUA_NV

Obsolete

(MSB) 2-5

Logical Block Address

(LSB)

6

Reserved = 0

(MSB) 7-8

Transfer Length

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 167 READ (10) - (28)
The READ (10) command requests the drive to transfer data to the Initiator. The larger LBA and Transfer Length fields permit greater quantities of data to be requested per command than with the READ command and are required to access the full LBA range of the larger capacity drives. - FUA_NV (Force Unit Access Non-Volatile Cache) may be set to 0 or 1, but is ignored since NV_SUP=0 in
Inquiry Page 86h. - Transfer length The number of contiguous blocks to be transferred. If the transfer length is zero, the seek
occurs, but no data is transferred. This condition is not considered an error. If read ahead is enabled, a read ahead is started after the seek completes. - DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified 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 read by this command are not likely to be read again in the near future. - FUA (Force Unit Access) bit of one indicates that the data is read from the media and not from the cache. A FUA bit of zero allows the data to be read from either the media or the cache. - RDPROTECT defines the manner in which protection information read from disk shall be checked during processing of the command. Protection information is stored on disk, and may be transmitted to the drive's internal data buffer and to the initiator with the user data. If the drive is not formatted with protection information, RDPROTECT 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.
RDPROTECT=000b Protection information is not transmitted to the initiator and is not checked.
RDPROTECT=001b
- Protection information is transmitted to the initiator with the user data - Logical Block Guard is checked - Logical Block Application Tag is checked (applies to READ(32) command only) - Logical Block Reference Tag is checked
RDPROTECT=010b
HGST Hard Disk Drive Specification 175

- 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 checked RDPROTECT=100b - Protection information is transmitted to the initiator with the user data - Logical Block Guard is checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not checked RDPROTECT=101b, 110b, 111b These values are reserved. Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. If a check of the protection information fails, Check Condition status will be returned with sense key of Aborted Command and additional sense code indicating which protection field check failed. Refer to the ANSI T10 standards for additional details of protection information. If the transfer length is zero, no data is transferred. The CDB is validated and protocol checked and, if no problems are found, Good status is returned immediately. This condition is not considered an error.
HGST Hard Disk Drive Specification 176

READ (12) - (A8)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = A8h

1

RDPROTECT

DPO

FUA RSVD = 0 FUA_NV RSVD = 0

2 - 5

(MSB)

Logical Block Address

(LSB)

(MSB) 6-9

Transfer Length

(LSB)

10

Reserved = 0

11

VU = 0

Reserved = 0

FLAG

LINK

Table 168 READ (12) - (A8)
The READ (12) command causes the drive to transfer data to the initiator. See the READ (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 177

READ (16) - (88)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 88h

1

RDPROTECT

DPO

FUA

RSVD=0 FUA_NV RSVD=0

2 - 9

(MSB)

Logical Block Address

(LSB)

10-13

(MSB)

Transfer Length

(LSB)

14

Restricted For MMC-4

Reserved = 0

GROUP NUMBER = 0

15

VU = 0

Reserved = 0

FLAG

LINK

Table 169 READ (16) - (88)
The READ (16) command causes the drive to transfer data to the initiator. See the READ (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 178

READ (32) - (7F/09)

Byte
0 1 2-5 6 7 8 - 9 10 11
12-19

7

6

5

VU = 0

Reserved = 0

RDPROTECT (MSB)

Bit

4

3

2

1

0

Command Code = 7Fh

Reserved = 0

FLAG

LINK

Reserved = 0

Group Number = 0

Additional CDB Length = 18h

Service Action = 0009h

DPO

FUA

RSVD=0 FUA_NV RSVD=0

Reserved = 0

Logical Block Address

(LSB)

(MSB) 20-23

Expected Initial Logical Block Reference Tag

(LSB)

24-25

(MSB)

Logical Block Application Tag

(LSB)

26-27

(MSB)

Logical Block Application Tag Mask

(LSB)

28-31

(MSB)

Transfer Length

(LSB)

Table 170 READ (32) - (7F/09)
The READ command requests that the drive transfer data from disk to the initiator. Each logical block transferred includes user data and may include protection information, based on the RDPROTECT field and the drive format. If the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data), then this command will be processed normally. Expected Initial Logical Block Reference Tag should be same as lower 4byte LBA of read LBA. Any other protection types will result in Check Condition status to be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code
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. 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

HGST Hard Disk Drive Specification 179

READ BUFFER (3C)

Bit

Byte

7

6

5

4

3

2

1

0

Command Code = 3Ch

1

Reserved = 0

Mode

2

Buffer ID = 0

(MSB) 3-5

Buffer Offset

0 (LSB)

(MSB) 6-8

9

VU = 0

Allocation Length Reserved = 0

FLAG

(LSB) LINK

Table 171 READ BUFFER (3C)

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.

The function of this command and the meaning of fields within the command descriptor block depend on the contents of the mode field.

MOD 00000 00010 00011 01010 01011 11010 11100 All others

Description Read Combined Header and Data Read Data Descriptor Read Data from Echo Buffer Echo Buffer Descriptor Enable Expander Communications Protocol and Echo Buffer Error History Not supported

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. The 4-byte READ BUFFER header (see figure below) is followed by data bytes from the data buffer of the drive.

Byte

7

6

0

(MSB)

1-3

Bit

5

4

3

2

RSVD = 0

Buffer Capacity

1

0

(LSB)

Table 172 Read Buffer Header
The buffer capacity specifies the total number of data bytes that are available in the data buffer of the drive. This number is not reduced to reflect the allocation length nor is it reduced to reflect the actual number of bytes written using the WRITE BUFFER command. Following the READ BUFFER header the drive will transfer data from its data buffer.

HGST Hard Disk Drive Specification 180

Read Data (Mode 00010b)

In this mode, the DATA IN phase contains buffer data.
- Buffer ID field must be set to zero, indicating the data transfer buffer. If another value is specified, the results may be unpredictable.
- Buffer Offset specifies the offset of the memory space specified by the Buffer ID. The Initiator should conform to the offset boundary requirements returned in the READ BUFFER descriptor. If the value exceeds the buffer specified, the command is terminated with Check Condition status. The drive shall set sense key to Illegal Request and additional sense code to Illegal Field in CDB.
- Allocation Length The drive terminates the DATA IN phase when allocation length bytes of data have been transferred or when the header and all available data have been transferred to the Initiator, whichever is less.
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. The drive transfers the allocation length or four bytes of READ BUFFER descriptor, whichever is less. The allocation length of zero indicates no data is transferred. The allocation length of greater than zero and less than four (size of the Descriptor) is an invalid request and will cause the command to be terminated with Check Condition status. The drive shall set sense key to Illegal Request and additional sense code to Illegal Field in CDB.
The READ BUFFER descriptor is defined in the figure below.

Byte

7

6

0

(MSB)

1-3

Bit

5

4

3

2

Offset Boundary = 0x09

Buffer Capacity

1

0

(LSB)

Table 173 Read Buffer Description
The value contained in the Buffer Offset field of subsequent WRITE BUFFER and READ BUFFER commands should be a multiple of two to the power of the offset boundary. The offset boundary is always set to nine, which indicates Sector Boundaries.
Read Data from Echo Buffer (Mode 01010b)

In this mode the drive transfers data from the echo buffer. The echo buffer will transfer the same data as when the WRITE BUFFER command was issued with the mode field set to echo buffer. WRITE BUFFER command with the mode field set to echo buffer should be sent prior to the READ BUFFER command; otherwise the READ BUFFER command will be terminated with Check Condition status and Illegal Request. In this mode Read Buffer transfers the specified amount of data or the amount previously written with a Write Buffer using mode 1010b from the echo buffer, whichever is less. Issuing a Read Buffer mode 1010b before a Write Buffer mode 1010b will cause indeterminate data to be returned. The most significant two bytes of the Allocation Length are ignored. The specified amount of data transferred should not be larger than the echo buffer capacity. The echo buffer capacity may be determined by using Read Buffer mode 1011b. Any additional data transferred over and above the echo buffer capacity is regarded as indeterminate. The Buffer ID and Buffer Offset fields are ignored in this mode.
Note: The echo buffer is a separate buffer from the data buffer used with other read buffer modes. It is intended to be used for domain validation purposes.

HGST Hard Disk Drive Specification 181

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.

Byte 7
0 1 2 3

6

5

Reserved = 0

Bit

4

3

Reserved = 0

Reserved = 0

(MSB)

Buffer Capacity

2

1

0

EBOS=0

Buffer Capacity

(LSB)

Table 174 Echo Buffer Descriptor - EBOS (Echo Buffer Overwritten Supported) bit of zero indicates that the echo buffer is shared by all Initiators. - Buffer Capacity field returns the size of the echo buffer in byte aligned to a 4-byte boundary.

Expander Communications and Echo Buffer (Mode 11010b)

Receipt of a READ BUFFER command with this mode (11010b) causes a communicative expander to enter the expanded communication protocol mode. SCSI target devices that receive a READ BUFFER command with this mode shall process it as if it were a READ BUFFER command with mode 01010b (see 17.17.4 Read Data from Echo Buffer).

Error History (Mode 11100b)

The Buffer ID field specifies the action that the device server shall perform, and the parameter data, if any, that the device server shall return.

Code

Description

00h 01h
02h
03h 04h to 0Fh 10h to EFh F0h to FDh
FEh FFh

Return error history directory Return error history directory and create new error history snapshot Return error history directory and establish new error history I_T Nexus Return error history directory, establish new error history I_T Nexus, and create new error history snapshot Reserved
Return error history
Reserved Clear error history I_T Nexus Clear error history I_T Nexus and release error history snapshot

Buffer Offset 0000h 0000h
0000h
0000h
0000h to FFFFh
Ignored Ignored

Error History I_T Nexus
Constrained Yes Yes
No
No Yes Yes Yes Yes Yes

Table 175 Error History Buffer ID Field

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_T nexus that is different than that
I_T nexus; and d) an error history snapshot exists.

The Buffer Offset field specifies the byte offset from the start of the buffer specified by the Buffer ID field from which the drive will return data. The application client should conform to the offset boundary requirements indicated in the Read Buffer descriptor. If the buffer offset is not one of those shown in the table above or the drive is unable to

HGST Hard Disk Drive Specification 182

accept the specified buffer offset, then the drive shall terminate the Read Buffer command with Check Condition status, with the sense key set to Illegal Request, and the additional sense code set to Invalid Field In CDB.

Whenever allowed by established error history I_T nexus constraints, if any, all error history directory device server actions return an error history directory.

Byte 0-7

7 (MSB)

Bit

6

5

4

3

2

1

T10 Vendor Identification = "HGST "(ASCII)

8 9 10-29
30-31

(MSB)

Reserved

Version EHS_Retrieved
Reserved

EHS_Sourse

Directory Length (n-31)

32-39 -
(n-7)-n

Error History Directory List Error history directory entry [first]
(see Table 177)
Error history directory entry [last] (see Table 177)

0 (LSB) CLR_SUP
(LSB)

Table 176 Error History Directory

The error history directory list contains an error history directory entry for each supported buffer ID in the range of 00h to EFh.

Bit

Byte

7

6

5

4

3

2

1

0

Supported Buffer ID

1-3

Reserved

(MSB) 4-7

Maximum Available Length

0 (LSB)

Table 177 Error History Directory Entry

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

Unless an error is encountered, the drive will return parameter data that contains error history in a vendor specific format from the error history snapshot from the specified buffer at the specified buffer offset.

If the drive receives a READ BUFFER command with the Mode field set to 1Ch from the established error history I_T nexus and the Buffer ID field is set to a value that the error history directory shows as not supported, then the drive will 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 CDB.

If the value in the Buffer Offset field is not supported, the device server shall 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 CDB.

The amount of error history in the specified buffer shall be less than or equal to the number of bytes indicated by the Maximum Available Length field in the error history directory.

HGST Hard Disk Drive Specification 183

READ CAPACITY (10) - (25)

Byte
0 1

Bit

7

6

5

4

3

2

1

Command Code = 25h

Reserved = 0

Reserved = 0

0 Obsolete

2-5

Obsolete

6-7

Reserved = 0

8

Reserved = 0

Obsolete

9

VU = 0

Reserved = 0

FLAG

LINK

Table 178 READ CAPACITY (10) - (25) The READ CAPACITY command returns the last LBA of the drive.
Returned Data Format
The data returned to the Initiator in response to the READ CAPACITY command is described here. The data is returned in the DATA IN phase.

Bit

Byte

7

6

5

4

3

2

1

0

(MSB) 0-3

Maximum Logical Block Address

(LSB)

(MSB) 4-7

Block Length

(LSB)

Table 179 Format of READ CAPACITY command reply - Block Length specifies the length in bytes of each block of user data (not including protection information).

HGST Hard Disk Drive Specification 184

READ CAPACITY (16) (9E/10)

Byte

Bit

7

6

5

4

3

2

1

0

0

Command Code = 9Eh

1

Reserved = 0

Service Action = 10h

2-9

Obsolete

(MSB) 10-13

Allocation Length

(LSB)

14

Reserved = 0

Obsolete

15

VU = 0

Reserved = 0

FLAG

Link

Table 180 Read Capacity (16) (9E/10)
The READ CAPACITY (16) (9E/10) command returns information regarding the capacity of the drive. This command is processed like the standard READ CAPACITY (25) command.

Returned Data Format

The following data is returned to the initiator in the DATA OUT phase.

Byte 0 - 7

7 (MSB)

(MSB) 8 - 11

12 13 14 - 31

Bit

6

5

4

3

2

1

0

Maximum Logical Address

(LSB)

Reserved = 0 P_I_Exponent

Block Length

(LSB)

P-Type

Prot-EN

Logical Blocks per Physical Block Exp

Reserved = 0

Table 181 Returned Data Format
The protection type (P_TYPE) field and the protection enable (PROT_EN) bit indicate the drive's current type of protection.

Prot-EN 0b 1b 1b

P-Type 000b 000b 001b

Description The drive is formatted to type 0 protection The drive is formatted to type 1 protection The drive is formatted to type 2 protection

Table 182 Protection Type (P_TYPE) field

Code 0
n>0

Description One or more physical blocks per logical block 2n logical blocks per physical block

Table 183 Logical Blocks per Physical Block Exponent field The number of physical blocks per logical block is not reported.

HGST Hard Disk Drive Specification 185

READ DEFECT DATA (37)

Byte
0 1 2 3-6

Bit

7

6

5

4

3

2

1

0

Command Code = 37h

Reserved = 0

Reserved = 0

0

Reserved = 0

Plist

Glist

Defect List Format

Reserved = 0

(MSB) 7-8

Allocation Length

(LSB)

9

VU = 0

Reserved = 0

FLAG LINK

Table 184 READ DEFECT DATA (37)
The READ DEFECT DATA command requests that the Target transfer the medium defect data to the Initiator. If the Target is unable to access any medium defect data it will return a Check Condition status with the appropriate sense key. The sense key will be set to either Medium Error (03h) if a medium error occurred or No Sense (00h) if the list does not exist and the additional sense code will be set to Defect List Error (19h).
- Plist bit set to one indicates that the Target returns the Plist. A Plist bit of zero indicates that the Target shall not return the Plist of defects.
- Glist bit set to one indicates that the Target returns the Glist. A Glist bit of zero indicates that the Target shall not return the Glist.
Note: With both bits set to one Plist and Glist the Target will return both the primary and grown defect lists. With both bits set to zero, the Target will return only a 4-byte Defect List Header.
- Defect List format field is used by the Initiator to indicate the preferred format for the defect list.
- The Defect List Format of '100 (Bytes from Index Format)' and '101 (Physical Sector Format)' are supported. If the requested format is not supported by the drive, it will return the defect list in its default format '101' and then terminate the command with Check Condition status. The sense key will be set to Recovered Error (01h) and the additional sense code will be set to Defect List Not Found (1Ch).
The drive sends defect list (Defect Descriptors) in an 8-byte Absolute Block Address (ABA) format that follows a four byte Defect List Header. The Target will transfer all of the Read Defect Data up to the number of bytes allocated by the Initiator.

Preferred Defect List Format Block (000b)
Bytes from Index (100b) Physical Sector (101b) Vendor Unique (110b)
Reserved (001b) Reserved (010b) Reserved (011b) Reserved (111b)

Returned Defect List Format Physical Sector Bytes from Index Physical Sector Physical Sector

Table 185 Defect List Format
Note: The drive will terminate the Data in phase when the Allocation Length has been transferred or when all 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.

HGST Hard Disk Drive Specification 186

Defect List Header

Byte
0 1 2-3

7

6

5

Reserved = 0 (MSB)

Bit

4

3

Defect List Header

Reserved = 0

Plist Glist

Defect List length

Table 186 Defect List Header
Defect List Descriptor

2

1

0

Defect List Format (LSB)

Bit

Byte

7

6

5

4

3

2

1

0

Defect List Descriptor

0-7

Defect Descriptor 0

.

8n - (8n+7)

Defect Descriptor n

Table 187 Defect List Descriptor

Bytes from Index Format (100b)

Byte 0-2 3 4-7

(MSB) (MSB)

Defect Descriptors Cylinder Number of Defect
Head Number of Defect Defect Bytes from Index

Table 188 Defect Descriptors of Bytes from Index Format
Defect Bytes from Index is gotten using the following equation: Bytes from Index = (Physical Sector Number) * N Where: N = Bytes per sector
Physical Sector Format (101b)

(LSB) (LSB)

Byte 0-2 3 4-7

(MSB) (MSB)

Defect Descriptors Cylinder Number of Defect
Head Number of Defect Defective Sector Number

(LSB) (LSB)

Table 189 Defect Descriptors of Physical Sector Format

The Defect List Format field specifies the format of the defect list data returned by the Target. The Defect List Length field specifies the length in bytes of the defect descriptors that follow. The Defect List Length is equal to eight times the number of defect descriptors. Normally the Target will set the Defect List Length field to the amount of space needed to contain the entire defect

HGST Hard Disk Drive Specification 187

list. However, the Target is capable of building a defect list with a length such that the entire list cannot be transferred using the maximum allocation length. If the defect list grows beyond 8191 entries, the defect data cannot be transferred with an allocation length of 0FFFFh. The Target will transfer a partial defect list and return Check Condition status with the sense key set to Recovered Error and the additional sense code set to Partial Defect List Transferred. The defect list length will be set to 0FFF8h, indicating the maximum number of defect descriptors that can be transferred. Defects beyond this number cannot be read by the Initiator.
HGST Hard Disk Drive Specification 188

READ DEFECT DATA (B7)

Byte
0 1 2-5
6-9

7

6

5

Reserved = 0

(MSB)

Bit

4

3

Command Code = B7h

Plist

Glist

Reserved = 0

Allocation Length

10

11

VU = 0

Reserved = 0 Reserved = 0

Table 190 READ DEFECT DATA (B7)

(See Section 8.24 "READ DEFECT DATA (37)")

Defect List Header

2

1

0

Defect List Format

FLAG

(LSB) LINK

Byte

7

6

5

0

1

Reserved = 0

2-3

(MSB) 4-7

Bit

4

3

Defect List Header

Reserved = 0

Plist

Glist

Reserved = 0

Defect List length

2

1

0

Defect List Format

(LSB)

Table 191 Unit Defect List Header

(See Defect List Header for Read Defect Data (37) in Section 8.24.1 "Defect List Header".)

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

Table 192 Defect List Descriptor

(See Defect List Descriptor for Read Defect Data (37) in Section 8.24.2 "Defect List Descriptor".)

HGST Hard Disk Drive Specification 189

Bytes from Index Format (100b)

Byte 0-2

(MSB)

Defect Descriptors Cylinder Number of Defect

3
(MSB) 4-7

Head Number of Defect Defect Bytes from Index

Table 193 Defect Descriptors of Bytes from Index Format
Defect Bytes from Index is derived using the following equation: Bytes from Index = (Physical Sector Number) + N where N = Bytes per sector.
Physical Sector Format (101b)

Byte 0-2

(MSB)

Defect Descriptors Cylinder Number of Defect

3
(MSB) 4-7

Head Number of Defect Defective Sector Number

Table 194 Defect Descriptors of Physical Sector Format

(LSB) (LSB)
(LSB) (LSB)

HGST Hard Disk Drive Specification 190

READ LONG (3E)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 3Eh

1

Reserved = 0

Correct = 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

Table 195 READ LONG (3E)
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.
- Correct transferred bit of zero causes correction to be attempted, data will be returned without reporting media errors regardless of the drives ability to successfully make corrections. When this bit is set the drive will return media errors if correction is not successful.
- Logical Block Address field specifies the logical block at which the read operation shall occur.
- Byte Transfer Length field must specify exactly the number of bytes of data that are available for transfer. If a non-zero byte transfer length does not match the available data length, the Target terminates the command with Check Condition status, the sense key is set to Illegal Request, and an additional sense code set to Invalid Field in CDB. The valid and ILI bits are set to one and the information field is set to the difference of the requested length minus the actual length in bytes. Negative values are indicated by two's complement notation.
The transfer length is calculated as follows:
transfer length = logical block size + 18 The data read by this command is neither read from nor retained in the cache. Data returned by this command cannot be corrupted and transferred on a subsequent WRITE LONG command to create recoverable media errors.

HGST Hard Disk Drive Specification 191

READ LONG (9E)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 9Eh

1

Reserved = 0

Service Action (11h)

(MSB) 2-9

Logical Block Address

(LSB)

10-11

Reserved = 0

12-13

(MSB)

Byte Transfer Length

(LSB)

14

Reserved = 0

PBLOCK CORRCT

15

VU = 0

Reserved = 0

FLAG

LINK

Table 196 READ LONG (9E)
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. - Correct transferred bit of zero causes correction to be attempted, data will be returned without reporting media
errors regardless of the drives ability to successfully make corrections. When this bit is set the drive will return media errors if correction is not successful. - Logical Block Address field specifies the logical block at which the read operation shall occur. - Byte Transfer Length field must specify exactly the number of bytes of data that are available for transfer. If a non-zero byte transfer length does not match the available data length, the Target terminates the command with Check Condition status, the sense key is set to Illegal Request, and an additional sense code set to Invalid Field in CDB. The valid and ILI bits are set to one and the information field is set to the difference of the requested length minus the actual length in bytes. Negative values are indicated by two's complement notation.
The transfer length is calculated as follows:
transfer length = logical block size + 18
The data read by this command is neither read from nor retained in the cache. Data returned by this command cannot be corrupted and transferred on a subsequent WRITE LONG command to create recoverable media errors.

HGST Hard Disk Drive Specification 192

REASSIGN BLOCKS (07)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 07h

1

Reserved = 0

LONGLBA Reserved = 0

2-4

Reserved = 0

5

VU = 0

Reserved = 0

FLAG

LINK

Table 197 REASSIGN BLOCKS (07)
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. One to four blocks may be specified for relocation per REASSIGN BLOCKS command. Reassignment is complete upon the completion of the REASSIGN BLOCKS command. At this time, the defective logical block address has been added to the Glist. All data is preserved during a reassign command except for the target LBA data. The Mode Page 0h DRRT (Disable Restore Reassign Target) bit determines if the reassign blocks command will attempt to recover the Target LBA data. If the Target cannot recover the data at the Target LBA then the Initiator will have to restore the data after the REASSIGN BLOCKS command completes successfully. If the reassignment begins to move data and is interrupted or fails to complete successfully, the Target enters a degraded mode of operation. In this mode data can be read but writing to the drive is prohibited. Upon successful completion of this command, the location of the physical sectors reassigned during the command are added to the Glist. The reassigned sectors are marked defective and cannot be accessed again until after a format operation discards the Glist.
- LONGLBA bit of zero indicates that LBAs in the provided defect list are 4-bytes. A LONGLBA bit of one indicates that the LBAs in the provided defect list are 8-bytes
Following is the format of the data sent by the Initiator during the DATA OUT phase.

Bit

Byte

7

6

5

4

3

2

1

0-1

Reserved = 0

(MSB) 2-3

Defect List Length

(LSB)

4-n

Defect LBA List

Table 198 Format of Reassign Blocks Parameter List data
- Defect List Length is the total number of bytes in the Defective LBA List (n - 4). - Defect LBA List is a list of zero to eight Logical Block Addresses to be reassigned. The number of bytes
describing each LBA is determined by the LONGLBA field in the command block.

HGST Hard Disk Drive Specification 193

RECEIVE DIAGNOSTICS RESULTS (1C)

Byte
0 1 2
3 4
5

Bit

7

6

5

4

3

2

Command Code = 1Ch

Reserved = 0

Reserved = 0

Page Code

(MSB)

Allocation Length

VU = 0

Reserved = 0

1

0

PCV

FLAG

(LSB) LINK

Table 199 RECEIVE DIAGNOSTIC RESULTS (1C)
The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTIC command be sent to the Initiator.
- PCV (Page Code Valid) bit of zero indicates that the most recent SEND DIAGNOSTIC command shall define the data returned by this command. PCV bit of one indicates that the contents of the Page Code field shall define the data returned by this command.
- Allocation Length specifies the amount of data to be returned to the Initiator. This value may be zero and this is not considered an error. The Target terminates the Data in phase when all available data has been transferred or when the number of bytes transferred equals the Parameter List Length.

Receive Diagnostic Results Page 0

This page contains a list of supported pages.

Bit

Byte

7

6

5

4

3

2

1

0

0

Page Code = 0

1

Reserved = 0

2-3

Page Length = 04h

4

(Supported Pages) Page = 0h

5

CJTPAT page = 3Fh

6

Translate address page = 40h

7

Rebuild assist = 42h

Table 200 Receive Diagnostic Results page 0 The supported diagnostic page returns a list of supported pages in ascending order.

HGST Hard Disk Drive Specification 194

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.

Byte
0 1 2-3 4 5 6-13

Bit

7

6

5

4

3

2

1

0

Page Code = 40h

Reserved = 0

Page Length

Reserved = 0

Supplied Format

RA

ALTS ALTT

Reserved=0

Translate Format

Translated Address

Table 201 Receive Diagnostic Results page 40
- Page Length is set to 02h if the address is in a Reserved Area (RA =1). Otherwise, Page Length is set to 0Ah.
- Supplied Format is the value supplied by the SEND DIAGNOSTIC command; it may be 1of the 3 following values: - 000b Short Block format - 011b Long Block format - 100b Bytes From Index format - 101b Physical Sector format
- Translate Format is the value supplied by the SEND DIAGNOSTIC command and specifies the format in which the address has been translated into List. If the Supplied Format is the Short Block or Long Block format, the Translate Format must be either Bytes from Index or Physical Sector format. If the Supplied Format is the Bytes from Index or Physical Sector format, the Translate Format must be Long Block format. Otherwise the Target will terminate the command with Check Condition status.
- RA (Reserved Area) is set to one if the translated block is an inaccessible sector, which could reflect a defect, an unused sector on a spare cylinder, or a sector beyond the Maximum Customer LBA.
- ALTS (Alternate Sector) is set to one if the translated block is a sector in a spare cylinder that points to a reassigned customer sector.
- ALTT (Alternate Track) is not used.
- Translated Address contains the address in the Translate Format. For a physical format it is as follows:

Bit

Byte

7

6

5

4

3

2

1

0

6-8

Cylinder Number

9

Head Number

10-13

Sector Number or Bytes from Index

Table 202 Translated address

HGST Hard Disk Drive Specification 195

LEASE (17)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 17h

1

Reserved = 0

3rdPty=0

3rd Party ID

Ext=0

2

Reservation Identification

3-4

Reserved = 0

5

VU = 0

Reserved = 0

FLAG LINK

Table 203 RELEASE (17)
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. If the 3rdPty bit is not zero, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
- 3rd Party ID is ignored. - Extents must be 0. Extension is not supported by the drive. - Reservation Identification field is ignored.

HGST Hard Disk Drive Specification 196

RELEASE (57)

Byte

7

6

5

Bit

4

3

2

1

0

0

Command Code = 57h

1

Reserved = 0

3rdPty=0

Reserved = 0

Ext = 0

2

Reservation Identification

3

3rd Party Device ID

4-8

Reserved = 0

9

VU = 0

Reserved = 0

FLAG LINK

Table 204 RELEASE (57)
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. If the 3rdPty bit is not zero, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
- 3rd Party ID is ignored. - Extent must be 0. Extension is not supported by the drive. - Reservation Identification field is ignored.

HGST Hard Disk Drive Specification 197

REPORT DEVICE IDENTIFIER (A3/05)

Byte 0 1 2 3
4-5
6-9
10 11

7

6

5

Reserved = 0

(MSB) (MSB)

VU = 0

Bit

4

3

2

1

Command Code = A3h

Service Action = 05h

Reserved = 0

Reserved = 0

LUN=0

Allocation Length
Reserved = 0 Reserved = 0

FLAG

0
(LSB) (LSB) LINK

Table 205 REPORT DEVICE IDENTIFIER (A3/05)
The REPORT DEVICE IDENTIFIER command requests that the device server send device identification information to the application client. The LUN contains the logical unit number parameter. This parameter is expected to be zero. Other value for this parameter will cause the command to terminate with a CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST, and the additional sense code is set to INVALID FIELD IN CDB. The ALLOCATION LENGTH field indicates how much space has been reserved for the returned parameter data. If the length is not sufficient to contain all the parameter data, the first portion of the data is returned. This is not considered an error. The actual length of the parameter data is available in the IDENTIFIER LENGTH field in the parameter data. If the remainder of the parameter data is required, the application client should send a new REPORT DEVICE IDENTIFIER command with an ALLOCATION LENGTH field large enough to contain all the data. The REPORT DEVICE IDENTIFIER parameter list contains a 4-byte field that contains the length in bytes of the parameter list and the logical unit's identifier.

Byte

7

6

(MSB)

0-3

4-n

Bit

5

4

3

2

Identifier Length = n - 3

Identifier

1

0

(LSB)

Table 206 Report Device Identifier parameter list
The IDENTIFIER LENGTH field specifies the length in bytes of the IDENTIFIER field. If the ALLOCATION LENGTH field in the CDB is too small to transfer all of the identifier, the length is not adjusted to reflect the truncation. The 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. The execution of a REPORT DEVICE IDENTIFIER requires the enabling of a nonvolatile memory within the logical unit. If the nonvolatile memory is not ready, the device server returns Check Condition status rather than wait for the device to become ready. The sense key is set to Not Ready and the additional sense data is set as described in the TEST UNIT READY command. This information should allow the application client to determine the action required to cause the device server to become ready.

HGST Hard Disk Drive Specification 198

REPORT LUNS (A0)

Byte

7

6

0

1-5

(MSB) 6-9

10

11

VU = 0

Bit

5

4

3

2

Command Code = A0h

Reserved

Allocation Length

Reserved Reserved = 0

1

0

FLAG

(LSB) LINK

Table 207 REPORT LUNS (A0)
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. If the Allocation Length is less than 16 bytes, the Target will return a Check Condition status with sense key of Illegal Request and additional sense code of Invalid Field in CDB. If the Allocation Length is not sufficient to contain the LUN values for all configured logical units, the Target shall report as many LUN values as will fit in the specified Allocation Length. This is not considered an error. The REPORT LUNS command will send the LUN list in the subsequent Data Out Phase. The format of the LUN list is shown in the following table.

Byte

7

6

(MSB)

0-3

4-7 8-15

(MSB)

Bit

5

4

3

2

LUN List Length = 8

Reserved

LUN = 0

1

0

(LSB)

(LSB)

Table 208 LUN Reporting parameter list format

The LUN list length shall contain the length in bytes of the LUN list that is available to be transferred. This product only supports one LUN. Therefore, the LUN list length must be set to 8. The only supported LUN is zero.

HGST Hard Disk Drive Specification 199

REPORT SUPPORTED OPERATION CODES (A3/0C)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = A3h

1

Reserved = 0

Service Action = 0Ch

2

RCTD

Reserved = 0

Reporting Options

3

Requested Operation Code

4-5

Requested Service Action

6-9

Allocation Length

10

Reserved = 0

11

VU = 0

Reserved

FLAG LINK

Table 209 REPORT SUPPORTED OPERATION CODES (A3/0C)
The REPORT SUPPORTED OPERATION CODES command requests information on commands that the drive supports. The initiator may request a list of all operation codes and service actions supported, or the command support data for a specific command. RCTD: A return command timeouts descriptor (RCTD) bit set to one specifies that the command timeouts descriptor shall be included in each command descriptor (see section 8.34.1) that is returned or in the one_command parameter data (see section 8.34.2) that is returned. A RCTD bit set to zero specifies that the command timeouts descriptor shall not be included in any parameter data returned.
Reporting Options specifies the information to be returned in the parameter data.

HGST Hard Disk Drive Specification 200

Reporting Options Description

000b

A list of all operation codes and service actions supported by the drive will be returned in the all_commands parameter data format. The Requested Operation Code field and Requested Service Action field will be ignored.

001b

The command support data for the operation code specified in the Requested Operation Code field will be returned in the one_command parameter data format. The Requested Service Action field will be ignored. If the Requested Operation Code field specifies an operation code that has service actions, Check Condition status will be reported with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.

010b

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. If the Requested Operation Code field specifies an operation code that does not have service actions, Check Condition status will be reported with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.

011b

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. If: a) the operation code specified by the Request Operation Code field specifies an operation code for which the device server does not implement service actions, the Requested Service Action field is set to 00h, and the command is supported; or b) the operation code specified by the Requested Operation Code field specifies an operation code for which the device server implements service actions and the value in the Requested Service Action field is supported, then the command support data shall indicate that the command is supported (i.e., the Support field is set to 011b or 101b). Otherwise, the command support data shall indicate that the command is not supported (i.e., the Support field is set to 001b).

100b-111b

Reserved

Table 210 Reporting Options
Requested Operation Code specifies the operation code of the command to be returned in the one_command parameter data format. Requested Service Action specifies the service action of the command to be returned in the one_command parameter data format. Allocation Length specifies the number of bytes that have been allocated for the returned parameter data. If the length is not sufficient to contain all the parameter data, the first portion of the data shall be returned. The actual length of the parameter data may be determined from the Additional Length field in the parameter data.

HGST Hard Disk Drive Specification 201

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

Bit

Byte

7

6

5

4

3

2

1

0

0-3

Command Data Length (n-3)

4

Command Descriptor 0

N

Command Descriptor X

Table 211 All_command parameter data format Each Command Descriptor contains information about a single supported command CDB.

Bit

Byte

7

6

5

4

3

2

1

0

0-3

Operation Code

1

Reserved = 0

2-3

Service Action

4

Reserved = 0

5

Reserved = 0

CTDP

Serva ctv

6-7

CDB Length

8-19

Command Timeouts Descriptor, if any (see 8.34.3 "Command timeouts descriptor format")

Table 212 Command Descriptor format
Operation Code contains the operation code of a supported command.
Service Action contains a supported service action of the supported operation. If the operation code does not have a service action, the Service Action field will be set to zero.
CTDP: A command timeouts descriptor present bit set to one indicates that the command timeouts descriptor (see 8.34.3 "Command timeouts descriptor format") is included in this command descriptor. A CTDP bit set to zero indicates that the command timeouts descriptor is not included in this command descriptor.
Servactv set to zero indicates the operation code does not have service actions and the Service Action field should be ignored. SERVACTV set to one indicates the operation code field has service actions and the contents of the Service Action field are valid.
CDB Length contains the length of the command CDB in bytes.

HGST Hard Disk Drive Specification 202

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.

Byte

Bit

7

6

5

4

3

2

1

0

0

Reserved = 0

1

CTDP

Reserved = 0

Support

2-3

CDB Size (n-3)

4-n

CDB Usage Data

n+1 - n+12

Command Timeouts Descriptor, if any (see 8.34.3 "Command timeouts descriptor format")

Table 213 One_command parameter data format

CTDP: A command timeouts descriptor present bit set to one indicates that the command timeouts descriptor is included in this command descriptor. (see section 8.34.3 "Command timeouts descriptor format") A CTDP bit set to zero indicates that the command timeouts descriptor is not included in this command descriptor.
The Support field is defined in the table below.

Recording Option Description

000b
001b 010b 011b 100b 101b 110b-111b

Data about the requested command is not currently available. All data after byte 1 is not valid. A subsequent request for command support data may be successful.
The requested command is not supported. All data after byte 1 is not valid. Reserved. The requested command is supported in conformance with the standard. Reserved The requested command is supported in a vendor specific manner. Reserved.

Table 214 One_command parameter support field

CDB Size contains the size of the CDB Usage Data field in the parameter data, and the number of bytes in the CDB for the command requested.
CDB Usage Data contains information about the CDB for the command requested. The first byte of the CDB Usage Data field contains the operation code for the command. If the command contains a service action, then that service action code is returned in the same location as the Service Action field of the command CDB. All other bytes of the CDB Usage Data field contain a usage map for bits in the CDB for the command requested.
The bits in the usage map have a one-for-one correspondence to the CDB for the command requested. If the drive evaluates a bit in the CDB, the usage map will contain a one in the corresponding bit position. The usage map will contain a zero in the corresponding bit position for any field treated as ignored or reserved.

HGST Hard Disk Drive Specification 203

Command timeouts descriptor format

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., prior commands with the IMMED bit set to one in the CDB, concurrent commands from the same or different I_T nexuses, manual unloads, power-on self tests, prior aborted commands, commands that force cache synchronization, delays in the service delivery subsystem).
For commands that cause a change in power condition (Idle/Standby Powersave Modes), values returned in the command timeouts descriptor do not include the power condition transition time (e.g., the time to spinup rotating media).
Values returned in the command timeouts descriptor should not be used to compare products.

Bit

Byte

7

6

5

4

3

2

1

0

0 - 1

Descriptor Length (0Ah)

2

Reserved = 0

3

Command Specific

4- 7

Nominal Command Processing Time-out

8 - 11

Recommended Command Time-out

Table 215 Command timeouts descriptor format

The DESCRIPTOR LENGTH field indicates the number of bytes that follow in the command timeouts descriptor. The COMMAND SPECIFIC field contains time-out information (see Table 216) that is specific to one or more commands.

If no command specific time-out information is defined by this or the applicable command standard, the COMMAND SPECIFIC field is reserved.

Command

Reference

WRITE BUFFER

See Section 8.34.3.2 "WRITE BUFFER: command timeouts descriptor COMMAND SPECIFIC field usage"

Table 216 Command timeouts descriptor Command Specific Field usage

WRITE BUFFER: command timeouts descriptor COMMAND SPECIFIC field usage

For the WRITE BUFFER command, the COMMAND SPECIFIC field usage is reserved for all modes except the following:
- Download microcode mode (04h); - Download microcode and save mode (05h); - Download microcode with offsets mode (06h); - Download microcode with offsets and save mode (07h); - Download microcode with offsets and defer activation mode (0Eh) only if the microcode is activated by an
event other than an activate deferred microcode mode; and - Activate deferred microcode mode (0Fh).
If the command timeouts descriptor describes one of the WRITE BUFFER modes listed in this sub clause, then the
COMMAND SPECIFIC field indicates the maximum time, in one second increments, that access to the SCSI device is limited or not possible through any SCSI ports associated with a logical unit that processes a WRITE BUFFER command that specifies one of the named modes. A value of zero in the COMMAND SPECIFIC field indicates that the no maximum time is indicated.

HGST Hard Disk Drive Specification 204

REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D)

Byte
0 1 2-5 6-9 10 11

Bit

7

6

5

4

3

2

1

0

Command Code = A3h

Reserved = 0

Service Action = 0Dh

Reserved = 0

Allocation Length

Reserved = 0

VU = 0

Reserved = 0

Flag

Link

Table 217 Report Supported Task Management Functions (A3/0D)

The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command requests information on task management functions supported by the drive.
Allocation Length specifies the number of bytes that have been allocated for the returned parameter data. The allocation length must be at least four. If the allocation length is less than four, Check Condition Status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB.
The format of the returned parameter data is shown below.

Bit

Byte

7

6

5

4

3

2

1

0

0

ATS ATSS CACAS CTSS LURS QTS TRS WAKES

1

Reserved

QUAS QTSS ITNRS

2

Reserved

3

Reserved

Table 218 Report Supported Task Management Functions - returned parameter data

ATS (Abort Task) bit set to one indicates that ABORT TASK is supported. An ATS bit of zero indicates that ABORT TASK is not supported. ATSS (Abort Task Set) bit set to one indicates that ABORT TASK SET is supported. An ATSS bit of zero indicates that ABORT TASK SET is not supported. CACAS (Clear ACA) bit set to one indicates that CLEAR ACA is supported. A CACAS bit of zero indicates that CLEAR ACA is not supported. CTSS (Clear Task Set) bit set to one indicates that CLEAR TASK SET is supported. A CTSS bit of zero indicates that CLEAR TASK SET is not supported. LURS (Logical Unit Reset) bit set to one indicates that LOGICAL UNIT RESET is supported. An LUR bit of zero indicates that LOGICAL UNIT RESET is not supported. QTS (Query Task) bit set to one indicates that QUERY TASK is supported. A QTS bit of zero indicates that QUERY TASK is not supported. 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. A QUAS bit set to zero indicates the QUERY UNIT ATTENTION task management function is not supported.
A QUERY TASK SET supported (QTSS) bit set to one indicates the QUERY TASK SET task management function
(see SAM-4) is supported by the logical unit. A QTSS bit set to zero indicates the QUERY TASK SET task

HGST Hard Disk Drive Specification 205

management function is not supported. An I_T NEXUS RESET supported (ITNRS) bit set to one indicates the I_T NEXUS RESET task management function (see SAM-4) is supported by the logical unit. An ITNRS bit set to zero indicates the I_T NEXUS RESET task management function is not supported.
HGST Hard Disk Drive Specification 206

REPORT TIMESTAMP (A3/0F)

Byte 0 1 2-5
6-9
10 11

7 (MSB)

Bit

6

5

4

3

2

1

0

Command Code = A3h

Reserved = 0

Service Action = 0Fh

Reserved = 0

Allocation Length
Reserved = 0 Control

(LSB)

Table 219 REPORT TIMESTAMP (A3/0F)

The REPORT TIMESTAMP command requests that the device server return the current value of a device clock.
- Allocation Length specifies the number of bytes that have been allocated for the returned parameter data. If the length is not sufficient to contain all the parameter data, the first portion of the data shall be returned. The actual length of the parameter data may be determined from the Additional Length field in the parameter data.
- Control is defined by SAM-5.

Byte 0-1

7 (MSB)

2 3
(MSB) 4-9

3

Bit

6

5

4

3

2

1

0

Timestamp Parameter Data Length = 000Ah

(LSB)

Reserved = 0

Timestamp Origin = 0Fh

Reserved = 0

Timestamp Reserved = 0

(LSB)

Table 220 REPORT TIMESTAMP return parameter data
The Timestamp Parameter Data Length field indicates the number of bytes of parameter data that follow. The contents of the Timestamp Parameter Data Length field are not altered based on the allocation length. The Timestamp Origin field indicates the most recent event that initialized the returned device clock using the values. The Timestamp field contains the current value of a device clock.

HGST Hard Disk Drive Specification 207

Device clocks and timestamps

A timestamp may be included in data logged or recorded by a device server based on the contents of a device clock saturating counter described in this sub clause. Device clocks may be managed with:
a. The REPORT TIMESTAMP command b. The SET TIMESTAMP command c. The Control Extension mode page
The device clock is initialized by: a. Power on reset or hard reset that sets the device clock to zero b. The SET TIMESTAMP command
After the device clock is initialized, the device server will increment it by one every millisecond. The device clock is not affected by an I_T nexus loss or a logical unit reset.

Code 000b 001b 010b 100b to 111b

Description Device clock initialized to zero at power on or as the result of a hard reset Reserved Device clock initialized by the SET TIMESTAMP command Reserved

Table 221 Timestamp Origin value

HGST Hard Disk Drive Specification 208

REQUEST SENSE (03)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 03h

1

Reserved = 0

DESC

2-3

Reserved = 0

4

Allocation Length

5

VU = 0

Reserved = 0

FLAG LINK

Table 222 REQUEST SENSE (03) 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. Such relationship is shown in the table below. (See 12. SCSI Sense Data for more details).

DESC Bit Sense Data Format

0b

Fixed format

1b

Descriptor format

Length of Sense Data Returned
The number of bytes in the Allocation Length or 32 bytes, whichever is less
The number of bytes in the Allocation Length or a fixed "descriptor sense data size", whichever is less. The "descriptor sense data size" is either 40 or 60 bytes, depending on the drive firmware build.

Table 223 Sense Data Format and Length
If REQUEST SENSE command with an invalid LUN is received, the drive returns Good status and reports a sense key of Illegal Request and an additional sense code of Logical Unit Not Supported. If the drive has no sense data available to return, it will return a sense key of No Sense and an additional sense code of No Additional Sense Information.
Separate sense data is maintained by the device for each Initiator. Therefore, there is no requirement for an Initiator to expeditiously clear a Check Condition as this will not affect other initiators in a multi-Initiator system.

HGST Hard Disk Drive Specification 209

RESERVE (16)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 16h

1

Reserved = 0

3rdPty=0

3rd Party ID

Ext=0

2

Reservation Identification

(MSB) 3-4

Extent List Length = 0

(LSB)

5

VU = 0

Reserved = 0

FLAG LINK

Table 224 RESERVE (16)
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. If Ext bit is set to one, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB. The Reservation Identification and Extent List Length fields are ignored. The Reserve command requests that the entire LUN be reserved for the Initiator until
- the reservation is superseded by another valid Reserve command from the Initiator that made the reservation.
- the reservation is released by a RELEASE command from the same Initiator.
- a hard Reset condition occurs.
- a Target Reset message is received from any Initiator.
- a power off/on cycle occurs.
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
3rd Party ID is ignored. Only the Initiator that issued the Reserve command for a LUN may release the LUN, regardless of the 3rdPty option. This Initiator may also release the LUN by issuing another RESERVE command. This superseding RESERVE command releases the previous reservation when the new reservation is granted. Reservation queuing is not supported by the drive. If a LUN is reserved and a RESERVE command is issued from a different Initiator, the Target responds with a RESERVATION CONFLICT.

HGST Hard Disk Drive Specification 210

RESERVE (56)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 56h

1

Reserved = 0

3rdPty=0

Reserved

Ext=0

2

Reservation Identification

3

Third Pay Device ID

4-6

Reserved = 0

(MSB) 7-8

Extent List Length = 0

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 225 RESERVE (56)
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. If Ext bit is set to one, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB. The Reservation Identification and Extent List Length fields are ignored. The Reserve command requests that the entire LUN be reserved for the Initiator until
- the reservation is superseded by another valid Reserve command from the Initiator that made the reservation.
- the reservation is released by a RELEASE command from the same Initiator.
- a hard Reset condition occurs.
- a Target Reset message is received from any Initiator.
- a power off/on cycle occurs.
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
3rd Party ID is ignored. Only the Initiator that issued the Reserve command for a LUN may release the LUN, regardless of the 3rdPty option. This Initiator may also release the LUN by issuing another RESERVE command. This superseding RESERVE command releases the previous reservation when the new reservation is granted. Reservation queuing is not supported by the drive. If a LUN is reserved and a RESERVE command is issued from a different Initiator, the Target responds with a RESERVATION CONFLICT.

HGST Hard Disk Drive Specification 211

REZERO UNIT (01)

Bit

Byte

7

6

5

4

3

2

1

0

Command Code = 01h

1

Reserved = 0

Reserved = 0

2-4

Reserved = 0

5

VU = 0

Reserved = 0

FLAG

Table 226 REZERO UNIT (01) The REZERO UNIT command requests that the Target seek LBA 0.

0 LINK

HGST Hard Disk Drive Specification 212

SANITIZE (48)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 48h

1

Immed RSVD AUSE

Service Action

2-6

Reserved

7-8

Parameter List Length

9

VU = 0

Reserved

FLAG LINK

Table 227 SANITIZE (48)
 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.
 AUSE bit can be set to 1 to allow EXIT FAILURE MODE service action on a subsequent SANITIZE. If AUSE is set to 0, and the sanitize fails, a subsequent SANITIZE with EXIT FAILURE MODE will be rejected.
 Parameter List Length field specifies the length in bytes of the parameter data that is available to be transferred from the application client's Data-Out Buffer. When the Service Action is set to Overwrite (01) the Parameter List Length specifies the length of the Overwrite service action parameter list. If the Service Action is any other value than Overwrite (01), then the Parameter List Length must be 0. If not, 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.
 VU stands for Vendor Unique.  FLAG* If Link is zero, Flag must also be zero. If Link is one, Flag may also be one. Typically this bit is used to
cause an interrupt in the Initiator between linked commands.  LINK* is set to one to indicate that the Initiator desires an automatic link to the next command upon successful
completion of the current command.
Note: * - The drive ignores the link bit and flag bit in the CDB.

HGST Hard Disk Drive Specification 213

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.

Code 00h 01h 02h 03h 04h-1Eh 1Fh

Name Reserved Overwrite Reserved Cryptographic Erase Reserved Exit Failure Mode

Descriptions Returns Check Condition
Causes the device server to alter information by writing a data pattern to the medium one or more times
Returns Check Condition
Alters the drive internal encryption key to make user data/information unreadable
Returns Check Condition
If a prior Sanitize operation was issued with AUSE = 1 and it failed, this will take the drive out of degraded mode, Sanitize Failed state.

Table 228 SANITIZE Service Action Codes

Bit

Byte

7

6

5

4

3

2

1

0

0

Invert

Test

Overwrite Count

1

Reserved

2

(MSB)

3

Initialization Pattern Length (n - 3)

(LSB)

4

...

Initialization Pattern

n

Table 229 Parameter List Format for Overwrite Service Action
· Invert bit set to zero indicates that the initialization pattern and protection information bytes, if any, are written as specified in the Initialization Pattern field on each overwrite pass. If the Invert bit is set to one, then the initialization pattern and protection information bytes, if any, shall be inverted (i.e., each bit XORed with one) between consecutive overwrite passes.
· Overwrite Count field specifies the number of overwrite passes to be performed. The value of 00h is reserved. · Initialization Pattern Length field specifies the length in bytes of the Initialization Pattern field. The Initialization
Pattern Length field shall be greater than zero and shall not exceed the logical block length. If the Initialization Pattern Length field is set to zero or a value greater than the logical block length, then the device server shall 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. The protection information, if any, shall be set to FFFF_FFFF_FFFF_FFFFh

HGST Hard Disk Drive Specification 214

SECURITY PROTOCOL IN (A2)

Byte 7

Bit

6

5

4

3

2

1

0

0

Command Code = A2h

1

SECURITY PROTOCOL

2-3

SECURITY PROTOCOL SPECIFIC

4

INC_512

Reserved

5

Reserved

(MSB) 6-9

ALLOCATION LENGTH

(LSB)

10

Reserved

11

CONTROL

Table 230 SECURITY PROTOCOL IN (A2)
The SECURITY PROTOCOL IN command requests the device server to return security protocol information or the results of one or more SECURITY PROTOCOL OUT commands.
 The SECURITY PROTOCOL field specifies which security protocol is being used.

Code 00h 01h to 06h 07h to FFh

Description Security protocol information Defined by TCG Reserved

Table 231 SECURITY PROTOCOL field in SECURITY PROTOCOL IN command
 The contents of the SECURITY PROTOCOL SPECIFIC field are defined by the SECURITY PROTOCOL field.
 INC_512, a 512 increment bit set to 1 specifies that the ALLOCATION LENGTH field expresses the maximum number of bytes available to receive data in increments of 512 bytes (e.g., a value of one means 512 bytes, two means 1 024 bytes, etc.). Pad bytes may or may not be appended to meet this length. Pad bytes shall have a value of 00h. An INC_512 bit set to 0 specifies that the ALLOCATION LENGTH field expresses the maximum number of bytes available to receive data in increments of one byte.
Indications of data overrun or underrun and the mechanism, if any, for processing retries are defined by the protocol specified by the SECURITY PROTOCOL field.
 The CONTROL byte is defined in SAM-5. Any association between a previous SECURITY PROTOCOL OUT command and the data transferred by a SECURITY PROTOCOL IN command depends on the protocol specified by the SECURITY PROTOCOL field. If the device server has no data to transfer (e.g., the results for any previous SECURITY PROTOCOL OUT commands are not yet available), then the device server may transfer data indicating it has no other data to transfer. The format of the data transferred depends on the protocol specified by the SECURITY PROTOCOL field.
The device server shall retain data resulting from a SECURITY PROTOCOL OUT command, if any, until one of the following events is processed:
a) transfer of the data via a SECURITY PROTOCOL IN command from the same I_T_L nexus as defined by the protocol specified by the SECURITY PROTOCOL field;
b) logical unit reset (see SAM-5); or
I_T nexus loss (see SAM-5) associated with the I_T nexus that sent the SECURITY PROTOCOL OUT command.

HGST Hard Disk Drive Specification 215

SECURITY PROTOCOL OUT (B5)

Byte 7

Bit

6

5

4

3

2

1

0

0

Command Code = B5h

1

SECURITY PROTOCOL

2-3

SECURITY PROTOCOL SPECIFIC

4

INC_512

Reserved

5

Reserved

(MSB) 6-9

TRANSFER LENGTH

(LSB)

10

Reserved

11

CONTROL

Table 232 SECURITY PROTOCOL OUT (B5)
The SECURITY PROTOCOL OUT command requests the device server to process the specified parameter list using the specified security protocol. Depending on the protocol specified by the SECURITY PROTOCOL field, the application client may use the SECURITY PROTOCOL IN command to retrieve data that results from the processing of one or more SECURITY PROTOCOL OUT commands.
 The SECURITY PROTOCOL field specifies which security protocol is being used.

Code 00h 01h to 06h 07h to FFh

Description Reserved Defined by TCG Reserved

Table 233 SECURITY PROTOCOL field in SECURITY PROTOCOL OUT command
 The contents of the SECURITY PROTOCOL SPECIFIC field are defined by the SECURITY PROTOCOL field.
 INC_512, a 512 Increment bit set to 1 specifies that the TRANSFER LENGTH field expresses the number of bytes to be transferred in increments of 512 bytes (e.g., a value of one means 512 bytes, two means 1,024 bytes, etc.). Pad bytes shall be appended as needed to meet this requirement. Pad bytes shall have a value of 00h. An INC_512 bit set to 0 specifies that the TRANSFER LENGTH field indicates the number of bytes to be transferred.
 The CONTROL byte is defined in SAM-5
Any association between a SECURITY PROTOCOL OUT command and a subsequent SECURITY PROTOCOL IN command is defined by the protocol specified by the SECURITY PROTOCOL field. Each protocol shall define whether:
a) the device server shall complete the command with GOOD status as soon as it determines the data has been correctly received. An indication that the data has been processed is obtained by sending a SECURITY PROTOCOL IN command and receiving the results in the associated data transfer; or
b) the device server shall complete the command with GOOD status only after the data has been successfully processed and an associated SECURITY PROTOCOL IN command is not required.
The format of the data transferred depends on the protocol specified by the SECURITY PROTOCOL field.

HGST Hard Disk Drive Specification 216

SEND DIAGNOSTIC (1D)

Byte 0 1 2
3-4
5

7

6

5

Function Code

(MSB)

VU = 0

Bit

4

3

Command Code = 1Dh

PF

RSVD =0

Reserved = 0

2 SlfTst

Parameter List Length

Reserved = 0

1 Dev0fl
FLAG

0 Unt0fl
(LSB) LINK

Table 234 SEND DIAGNOSTIC (1D)

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.
- PF (Page Format) bit set to one indicates the data sent by the Initiator conform to the page structure as specified in SCSI standard. This bit is ignored by the Target if the SlfTst bit is set.
- SlfTst set to one indicates that the device performs its default self-test. If SlfTst is one, the Function code field is ignored. If SlfTst is set to zero, the action to perform is specified in Function code field.

Value Function name 000b NA

001b 010b 011b

Background Short self-test Background extended self-test NA

100b Abort background self-test

101b Foreground short self-test

110b Foreground extended self-test 111b

Description 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. The device server starts its short self-test routine in background mode. The device server starts its extended self-test routine in background mode. Reserved. Abort the current self-test in the background mode. This value is only valid if a previous SEND DIAGNOSTIC command specified a background self-test function and that function has not been completed. The device server starts its short self-test routine in the foreground mode. This self-test will complete in two minutes or less. The device server starts its extended self-test routine in the foreground mode .The completion time for this test is reported in Mode Page 0Ah (refer to section 8.10.9 "Mode Page 0A (Control Mode Page Parameters)"). Reserved.

Table 235 SEND DIAGNOSTIC Function Code (1D)

- DevOfl is ignored by the Target for compatibility. - UntOfl is ignored by the Target for compatibility. - Parameter List Length must be 0 when the SlfTst bit is one. Otherwise, Check Condition status will be
generated with a sense key of Illegal Request and additional sense of Invalid Field in CDB. If the SlfTst bit is zero, it should be set to the length of the page to be transferred in the DATA OUT phase of the command. If it does not match the expected length of the page a Check Condition status will be also generated with a sense key of Illegal Request and additional sense of Invalid Field in CDB.
If the motor is not running at the correct speed when the command is received, it is rejected by a Check Condition status with a Not Ready sense key. If a fault is detected during the default or foreground self-test, a Check Condition is reported as an end status. If a fault is detected during the background self-test, it is logged in the log page for later retrieval by a LOG SENSE command. See Section 10.12 Diagnostics for a detailed listing of operations carried out by the SEND DIAGNOSTIC command and Power on Diagnostics.

HGST Hard Disk Drive Specification 217

Send Diagnostic Page 0

This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS command.

Byte

7

6

5

Bit

4

3

2

1

0

0

Page Code = 0

1

Reserved = 0

2 - 3

Page Length = 0

Table 236 Diagnostic page 0

Send Diagnostic Page 3F

Byte
0 1 2 - 3 4 5 6
7
8 ­ 10 11
12 ­ 19 20 ­ 31

7 Rsvd=0

Bit

6

5

4

3

2

1

0

Page Code = 3F

Reserved = 0

Protocol Identifier = 6

Page Length = 1Ch Phy Identifier

Phy Test Function

Phy Test Pattern

Phy Test Pattern SATA = 0

Phy Test Pattern SSC

Phy Test Pattern Physical Link Rate

Reserved = 0

Phy Test Pattern Dwords Control

Phy Test Pattern Dwords

Reserved = 0

Table 237 Diagnostic page 3F

- Phy Identifier specifies the selected phy that is to perform or to stop performing a phy test function. If the phy does not exist, 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 specifies the phy test function to be performed. If an unsupported function is requested, 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 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 00h
01h 02h-FDh
FEh FFh

Description 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. If the selected phy is not performing a phy test function, then this function as no effect on the selected phy.
If the selected phy is not performing a phy test function, the selected phy will be set to transmit the phy test pattern specified by the Phy Test Pattern field at the physical link rate specified by the Phy Test Pattern Physical
Unsupported
Analog Loopback - If the selected phy is not performing a phy test function, the selected phy will be set to retransmit the data pattern received by the phy receiver without retime
Retime Loopback- If the selected phy is not performing a phy test function, the selected phy will be set to retransmit the retimed data pattern received by the phy receiver

Table 238 Phy Test Function

HGST Hard Disk Drive Specification 218

Phy Test Pattern 00h 01h 02h
03h-0Fh 10h 11h 13h 12h
14h - 3Fh 40h
41h ­ Efh F0h
F1h-FFh

Description Reserved JTPAT CJTPAT Reserved TRAIN TRAIN_DONE SCRAMBLE_0 IDLE Reserved TWO_DWORDS Reserved PRBS7 (DC un-balanced version) Reserved

Table 239 Phy Test Pattern

- Phy Test Pattern Physical Link Rate specifies the physical link rate at which the phy test pattern shall be transmitted. Supported values are 8h for 1.5 Gbps, 9h for 3.0 Gbps, and Ah for 6.0 Gbps. 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 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. If an unsupported SSC modulation type 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 Pattern SSC Code 00h 01h 10h 11h

Description No SSC Center-spreading SSC (Not supported) Down-spreading SSC Reserved

Table 240 Phy Test Pattern SSC Code
- Phy Test Pattern Dwords Control controls whether the bytes in the Phy Test Pattern Dwords field are sent as control characters or data characters.

Phy Test Pattern Dwords Control

Description

00h

Each byte in the Phy Test Pattern Dwords field shall be sent as a data character (i.e., Dxx.y) without scrambling.

08h

The fifth byte in the Phy Test Pattern Dwords field shall be sent as a control character (i.e., Kxx.y). Each other byte shall be sent as a data character without scrambling.

80h

The first byte in the Phy Test Pattern Dwords field shall be sent as a control character. Each other byte shall be sent as a data character without scrambling.

88h

The first and fifth bytes in the Phy Test Pattern Dwords field shall be sent as a control character. Each other byte shall be sent as a data character without scrambling.

All others

Reserved

Table 241 Phy Test Pattern Dwords Control

- Phy Test Pattern Dwords contains the two Dwords that are sent during a TWO_DWORDS test pattern.

HGST Hard Disk Drive Specification 219

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. The data translation will be performed upon receipt of the RECEIVE DIAGNOSTICS command.

Byte 7
0 1 2-3 4 5 6-13

Bit

6

5

4

3

Page Code = 40h

Reserved = 0

Page Length = 0Ah

Reserved = 0

Reserved = 0

Address to Translate

2

1

0

Supplied Format Translate Format

Table 242 Diagnostic Page 40
Supplied Format may take one of the following three values: It specifies the format in which the address has been supplied.

000b Short Block format
011b Long Block format
100b Bytes From Index format
101b Physical Sector format
- Translate Format specifies the format that the address should be translated into. If the Supplied Format is the Short Block format or Long Block format, the Translate format must be either Bytes From Index or Physical Sector format. If the Supplied Format is the Bytes From Index or Physical Sector format, the Translate Format must be Long Block format. If either of the format fields is invalid or they specify the same format, the command will terminate with Check Condition status with a sense code of Illegal Request and Illegal Field in Parameter List.
- Address to Translate contains the address to translate. If the Short Block format is specified, the first four bytes of the field (bytes 6 to 9) contain the LBA and the remainder must be zero. If the Long Block format is specified, byte 6 to 13 contain the 64-bit LBA. For the physical format the address must be specified as follows.

Bit

Byte

7

6

5

4

3

2

1

0

6-8

Cylinder Number

9

Head Number

10-13

Sector Number or Bytes from Index

Table 243 Address to translate

HGST Hard Disk Drive Specification 220

SET DEVICE IDENTIFIER (A4/06)

Byte
0 1 2 3 4-5
6-9
10 11

7

6

5

Reserved = 0

(MSB) VU = 0

Bit

4

3

2

1

0

Command Code = A4h

Service Action = 06h

Reserved = 0

Reserved = 0

Restricted = 0

Parameter List Length
Reserved = 0 Reserved = 0

FLAG

(LSB) LINK

Table 244 SET DEVICE IDENTIFIER (A4/06)
The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the SET DEVICE IDENTIFIER parameter list. On successful completion of a SET DEVICE IDENTIFIER command a unit attention is generated for all Initiators except the one that issued the service action. When reporting the unit attention condition the additional sense code is set to Device Identifier Changed.
- Parameter List Length field specifies the length in bytes of the Identifier that is transferred from the host system to the Target. The maximum value for this field is 512 bytes. A parameter list length of zero indicates that no data is transferred, and that subsequent REPORT DEVICE IDENTIFIER commands return an Identifier length of zero.
The SET DEVICE IDENTIFIER parameter list contains the identifier to be set by the addressed logical unit.

Byte

7

6

5

Bit

4

3

2

1

0

0-n

Identifier

Table 245 SET DEVICE IDENTIFIER, Parameter List
The IDENTIFIER field is a vendor specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands.

HGST Hard Disk Drive Specification 221

SET TIMESTAMP (A4/0F)

Byte 0 1 2-5
6-9
10 11

7 (MSB)

Bit

6

5

4

3

2

1

0

Command Code = A4h

Reserved = 0

Service Action = 0Fh

Reserved = 0

Parameter List Length
Reserved = 0 Control

(LSB)

Table 246 SET TIMESTAMP (A4/0F)
The SET TIMESTAMP command requests that the device server initialize a device clock if the SCSIP bit is set to one in the Control Extension mode page. If the SCSIP bit is set to zero, the device server shall terminate the SET TIMESTAMP command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
- Parameter List Length field specifies the length in bytes of the SET TIMESTAMP parameters that shall be transferred from the application client to the device server. A parameter list length of zero specifies that no data shall be transferred, and that no change shall be made to a device clock.
- Control is defined by SAM-5.

Byte

7

6

0-3

(MSB) 4-9

10-11

Bit

5

4

3

2

Reserved = 0

Timestamp

Reserved = 0

1

0

(LSB)

Table 247 SET TIMESTAMP parameter list

The Timestamp field specifies the value to which a device clock shall be initialized. The timestamp should be the number of milliseconds that have elapsed since midnight, 1 January 1970 UT. If the most significant byte in the Timestamp field is greater than F0h, the device server shall 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.
On successful completion of a SET TIMESTAMP command the device server shall establish a unit attention condition for the initiator port associated with every I_T nexus except the I_T nexus on which the SET TIMESTAMP command was received (see SAM-5), with the additional sense code set to TIMESTAMP CHANGED.

HGST Hard Disk Drive Specification 222

START STOP UNIT (1B)

Byte
0 1 2 3 4 5

7

6

5

Reserved = 0 Power Condition VU = 0

Bit

4

3

2

1

0

Command Code = 1Bh Reserved = 0

Immed

Reserved = 0

Power Condition Modifier

Reserved=0 Reserved = 0

LoEj= 0 FLAG

Start LINK

Table 248 START STOP UNIT (1B)

The START STOP UNIT command is used to spin up or stop the spindle motor. - 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 after a spin-up.

- Power Conditions and Power Condition Modifier fields are used to specify that the logical unit be placed into a power condition or to adjust a timer as defined in Table 249, if this field is set to a value other than 0h, then the START bit shall be ignored.

Power Condition
Code 0h 1h 2h 2h 2h 3h 3h 4h 5h 6h 7h
8h - 9h Ah Ah Ah Bh Bh
all Others

Name
START_VALID ACTIVE IDLE_A IDLE_B IDLE_C
STANDBY_Z STANDBY_Y
Reserved Obsolete Reserved LU_CONTROL Reserved FORCE_IDLE_A FORCE_IDLE_B FORCE_IDLE_C FORCE_STANDBY_Z FORCE_STANDBY_Y Reserved

Power Condition Modifier
0h 0h 0h 1h 2h 0h 1h 0h 0h-Fh 0h 0h 0h 0h 1h 2h 0h 1h 0h

Description
Process the START bit Place the device into the active power condition Place the device into the idle-a power condition Place the device into the idle-b power condition Place the device into the idle-c power condition Place the device into the standby_Z power condition Place the device into the standby_Y power condition Reserved Obsolete Reserved Transfer control of power conditions to the logical unit Reserved Force the idle_a condition timer to zero. Force the idle_b condition timer to zero. Force the idle_c condition timer to zero. Force the standby_z condition timer to zero. Force the standby_y condition timer to zero. Reserved

Table 249 Power Conditions

If the START STOP UNIT command is processed with the POWER CONDITION field set to ACTIVE, IDLE, or STANDBY, then:
the logical unit shall transition to the specified power condition; and the device server shall disable the idle condition timer if it is active and disable the standby condition timer if it is active until another START STOP UNIT command is processed that returns control of the power condition to the logical unit, or a logical unit reset occurs.

HGST Hard Disk Drive Specification 223

if under initiator control, the two minute floor and 60 head unloads per 24 hour period limits do not apply as they do when under logical unit/timer control If the START STOP UNIT command is processed with the POWER CONDITION field set to LU_CONTROL, then the device server shall initialize and start all of the idle condition timers and standby condition timers that are supported and enabled. If the START STOP UNIT command is processed with the POWER CONDITION field set to LU_CONTROL, then the device server shall enable the idle condition timer if it is active and disable the standby condition timer if it is active. 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. The device server shall 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 CDB. It is not an error to specify that the logical unit transition to its current power condition. See 8.10.13 " Mode Page 1A (Power Control)" for more information on idle and standby power conditions. - LoEj is not supported by the drive and must be set to 0. - Start bit is to specify: Note: Once the drive has become ready (after a power on), the START STOP UNIT command can be used without any errors regardless of the state of the motor: stopped or spinning. 0 Stop the spindle 1 Stop the spindle
HGST Hard Disk Drive Specification 224

SYNCHRONIZE CACHE (10) - (35)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 35h

1

Reserved = 0

Reserved = 0

Immed = 0 Obsolete

(MSB) 2-5

Logical Block Address

(LSB)

6

Reserved = 0

(MSB) 7-8

Number of Blocks

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 250 SYNCHRONIZE CACHE (10) - (35)
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.
- Immed (immediate) must be zero. An immediate bit of zero indicates that the status shall not be returned until the operation has completed. If the Immed bit is set to one, the drive returns a Check Condition status. The sense key shall be set to Illegal Request and the additional sense code shall be set to Invalid Field in CDB.
- Number of Blocks specifies the total number of contiguous logical blocks within the range. Number of Blocks of zero indicates that all remaining logical blocks on the logical unit shall be within the range.

HGST Hard Disk Drive Specification 225

SYNCHRONIZE CACHE (16) - (91)

Byte
0 1 2-9 10-13 14 15

7

6

VU = 0

Bit

5

4

3

2

Command Code = 91h

Reserved = 0

Logical Block Address

Number of Blocks

Reserved = 0

Reserved = 0

1

0

Immed = 0 Rsvd=0

FLAG

LINK

Table 251 Synchronize Cache (16) - (91)
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.

HGST Hard Disk Drive Specification 226

TEST UNIT READY (00)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 00h

1

Reserved = 0

Reserved = 0

2-4

Reserved = 0

5

VU = 0

Reserved = 0

FLAG

LINK

Table 252 TEST UNIT READY (00)
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. If the spindle motor is not spinning at the correct speed, Check Condition status is returned with sense key of Not Ready. If the motor is spinning at the correct speed, the drive accepts normal media access commands. The TEST UNIT READY command is not intended as a diagnostic. No self diagnostic is performed by the device as a result of this command. The TEST UNIT READY command has special significance for power sequencing using the UNIT START command with an immediate bit of one. In this mode the UNIT START command returns Task Complete status before the completion of motor spin-up and expects the initiator to issue TEST UNIT READY commands to determine when the motor has reached the proper speed.
Note: The spindle automatically starts in automatic spin-up mode. The drive does not execute any commands other than TEST UNIT READY, INQUIRY, or REQUEST SENSE command until the Power On sequence is complete. The drive will return Check Condition status with Not Ready sense key and In Process of Becoming Ready sense code for all other commands during the Power On period.

HGST Hard Disk Drive Specification 227

VERIFY (10) - (2F)

Byte 0 1 2-5 6 7-8 9

7

6

5

VRPROTECT (MSB)

(MSB) VU = 0

Bit

4

3

Command Code = 2Fh

DPO

RSVD = 0

Logical Block Address

Reserved = 0

Verification Length

Reserved = 0

2

1

ByteChk

FLAG

0 RSVD = 0
(LSB)
(LSB) LINK

Table 253 VERIFY (10) - (2F)
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.

ByteChk

Function

00b

Indicates that the data is read from the disk and verified using LDPC. If an LDPC error is detected in

the verify process, Check Condition status is returned with sense key set to Medium Error.

01b

Indicates that a byte-by-byte comparison is performed between the data on the disk and data

transferred from the initiator during the data-out phase. The number of logical blocks transferred

must equal the Verification Length field. If the comparison is unsuccessful, the command is

terminated with Check Condition status and the sense key is set to Miscompare.

10b

Not defined

11b

Indicates that a byte-by-byte comparison is performed between the data on the disk and data

transferred from the initiator during the data-out phase. The number of logical blocks transferred

must equal one. All blocks specified by the Verification Length will be compared against the single

block of data transferred by the initiator. If the comparison is unsuccessful, the command is

terminated with Check Condition status and the sense key is set to Miscompare.

Table 254 Byte Check

- DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified 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 read by this command are not likely to be read again in the near future.

If caching is enabled, the command performs an implied FUA and an implied Synchronize Cache before starting the VERIFY. This ensures that the medium, not the cache, is being verified. The command stops on Check Condition and reports the LBA in error. The command must be reissued, starting with the next LBA, to verify the remainder of the Drive. 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. Protection information is stored on disk, and may be validated using the drive's internal checking algorithms, and also byte-by-byte compared using data from the initiator when ByteChk=1.

HGST Hard Disk Drive Specification 228

If the drive is not formatted with protection information, VRPROTECT 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. VRPROTECT=000b If the drive is not formatted with protection information, only user data is verified. If the drive is formatted with protection information:
- Logical Block Guard is checked - Logical Block Application Tag is checked (applies to VERIFY(32) command only) - Logical Block Reference Tag is checked VRPROTECT=001b - Logical Block Guard is checked - Logical Block Application Tag is checked (applies to VERIFY(32) command only) - Logical Block Reference Tag is checked VRPROTECT=010b - Logical Block Guard is not checked - Logical Block Application Tag is checked (applies to VERIFY(32) command only) - Logical Block Reference Tag is checked VRPROTECT=011b - Logical Block Guard is not checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not checked VRPROTECT=100b - Logical Block Guard is checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not checked VRPROTECT=101b, 110b, 111b These values are reserved. Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. If a check of the protection information fails, Check Condition status will be returned with sense key of Aborted Command and additional sense code indicating which protection field check failed. If ByteChk=1, the drive's internal checking of protection information is done only when VRPROTECT=000b and the drive is formatted with protection information If ByteChk=1, and VRPROTECT is not set to 000b, checking of protection information is performed on the fields described above as a byte-by-byte comparison against the data transferred to the drive by the initiator during the Data Out phase. Refer to the ANSI T10 standards for additional details of protection information.
HGST Hard Disk Drive Specification 229

VERIFY (12) - (AF)

Bit

Byte

7

6

5

4

3

2

1

0

0

1

VRPROTECT

(MSB) 2-5

Command Code = AFh

DPO

FUA

ByteChk

Logical Block Address

Reserved = 0 (LSB)

6 - 9

(MSB)

Verification Length

(LSB)

10

Reserved = 0

11

VU = 0

Reserved = 0

FLAG

LINK

Table 255 VERIFY (12) - (AF)
The VERIFY (12) command causes the drive to verify data written on the media. See the VERIFY(10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 230

VERIFY (16) - (8F)

Bit

Byte

7

6

5

4

3

2

1

0

0

1

VRPROTECT

(MSB) 2-9

Command Code = 08Fh

DPO

RSVD = 0

Logical Block Address

ByteChk

RSVD = 0 (LSB)

10-13

(MSB)

Verification Length

(LSB)

14

Reserved = 0

15

VU = 0

Reserved = 0

FLAG

LINK

Table 256 VERIFY (16) - (8F)
The VERIFY command requests that the drive verify the data written on the media. See the VERIFY (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 231

VERIFY (32) - (7F/0A)

Byte
0 1 2-5 6 7 8-9 10 11
12-19

7

6

5

VU = 0 Reserved = 0

RDPROTECT (MSB)

Bit

4

3

2

1

Command Code = 07Fh

Reserved = 0

FLAG

Reserved = 0

Group Number = 0

Additional CDB Length = 18h

Service Action = 000Ah

DPO RSVD = 0

ByteChk

Reserved = 0

0 LINK
Reserved=0

Logical Block Address

(LSB)

20-23

(MSB)

Expected Initial Logical Block Reference Tag

(LSB)

24-25

(MSB)

Expected Logical Block Application Tag

(LSB)

26-27

(MSB)

Logical Block Application Tag Mask

(LSB)

28-31

(MSB)

Verification Length

(LSB)

Table 257 VERIFY (32) - 7F/0A)
The VERIFY command requests that the verify the data written on the media. Each logical block includes user data and may include protection information, based on the VPROTECT field and the drive format.
If the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data), then this command will be processed normally. Any other protection types will result in Check Condition status to be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code
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. 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.

HGST Hard Disk Drive Specification 232

WRITE (6) - (0A)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 0Ah

1

Reserved = 0

(MSB)

LBA

2-3

Logical Block Address

(LSB)

4

Transfer Length

5

VU = 0

Reserved = 0

FLAG LINK

Table 258 WRITE (6) - (0A)
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 8.16 "READ (6) - (08)" for the parameters.

HGST Hard Disk Drive Specification 233

WRITE (10) - (2A)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 2Ah

1

WRPROTECT

DPO

FUA

Rsvd=0 FUA_NV Obsolete

(MSB) 2-5

Logical Block Address

(LSB)

6

Reserved = 0

(MSB) 7-8

Transfer Length

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 259 WRITE (10) - (2A)
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.
- Transfer Length is the number of contiguous blocks to be transferred. If the transfer length is zero, the seek occurs, but no data is transferred. This condition is not considered an error.
- DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified in the Mode Select Page 8 Caching Parameters. A DPO bit of zero indicates that 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 in the near future.
- FUA (Force Unit Access) bit of one indicates that the Target must write the data to the media before returning Good status. A FUA bit of zero indicates that the Target may return Good status prior to writing the data to the media.
- FUA_NV (Force Unit Access Non-Volatile Cache) may be set to 0 or 1, but is ignored since NV_SUP=0 in Inquiry Page 86h.
If a WRITE (6) command is received after protection information is enabled, the drive will set the protection information as follows as it writes each block to disk:
- the Logical Block Guard field is set to a properly generated CRC - the Logical Block Reference Tag field is set to:
- the least significant four bytes of the LBA, if the drive is formatted with type 1 protection (PROT_EN=1 and P_TYPE=000b in the READ CAPACITY (16) parameter data); or
- FFFFFFFFh, if the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data)
- the Logical Block Application Tag field is set to
- FFFFh, if the ATO bit is set to one in Mode Page 0Ah; or
- Any value, if the ATO bit is set to zero

HGST Hard Disk Drive Specification 234

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. WRPROTECT=000b Protection information is not transmitted to the drive. If the drive is formatted with protection information, the drive will write protection information to disk based on its internal algorithms. WRPROTECT=001b
- Protection information is transmitted to the drive with the user data - Logical Block Guard is checked - Logical Block Application Tag is checked (applies to WRITE (32) command only) - Logical Block Reference Tag is checked WRPROTECT=010b - Protection information is transmitted to the drive with the user data - Logical Block Guard is not checked - Logical Block Application Tag is checked (applies to WRITE (32) command only) - Logical Block Reference Tag is checked WRPROTECT=011b - Protection information is transmitted to the drive with the user data - Logical Block Guard is not checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not checked WRPROTECT=100b - Protection information is transmitted to the drive with the user data - Logical Block Guard is checked - Logical Block Application Tag is not checked - Logical Block Reference Tag is not checked WRPROTECT=101b, 110b, 111b These values are reserved. Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. If a check of the protection information fails, Check Condition status will be returned with sense key of Aborted Command and additional sense code indicating which protection field check failed. Refer to the ANSI T10 standards for additional details of protection information.
HGST Hard Disk Drive Specification 235

WRITE (12) - (AA)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = AAh

1

WRPROTECT

DPO

FUA Rsvd=0 FUA_NV Rsvd=0

(MSB) 2-5

Logical Block Address

(LSB)

(MSB) 6-9

Transfer Length

(LSB)

10

Reserved=0

11

VU = 0

Reserved = 0

FLAG

LINK

Table 260 WRITE (12) - (AA)
The WRITE (12) command causes the drive to write data from the initiator to the media. See the WRITE (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 236

WRITE (16) - (8A)

Byte

7

6

5

Bit

4

3

2

1

0

0

Command Code = 8Ah

1

WRPROTECT

DPO

FUA Rsvd=0 FUA_NV Rsvd=0

(MSB) 2-9
(MSB) 10-13
14

Logical Block Address Transfer Length Reserved = 0

(LSB) (LSB)

15

VU = 0

Reserved = 0

FLAG

LINK

Table 261 WRITE (16) - (8A)
The WRITE (16) command causes the drive to write data from the initiator to the media. See the WRITE (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 237

WRITE (32) - (7F/0B)

Bit

Byte

7

6

5

4

3

2

1

0

0 1 2-5
7 8-9 10 11 12-19
20-23
24-25
26-27
28-31

VU = 0 Reserved = 0
WRPROTECT (MSB)

Command Code = 07Fh

Reserved = 0

FLAG

Reserved = 0

Group Number = 0

Additional CDB Length = 18h

Service Action = 000Bh

DPO

FUA

Rsvd=0

FUA_NV

Reserved = 0

Logical Block Address

(MSB)

Expected Initial Logical Block Reference Tag

(MSB)

Expected Logical Block Application Tag

(MSB)

Logical Block Application Tag Mask

(MSB)

Transfer Length

LINK
Rsvd=0 (LSB) (LSB) (LSB) (LSB) (LSB)

Table 262 WRITE (32) - (7F/0B)

The WRITE command requests that the drive write data transferred from the initiator to disk. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the drive format. Each logical block written includes user data and, if the drive is formatted with protection information enabled, protection information. If the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data), then this command will be processed normally. Any other protection types will result in Check Condition status to be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code

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

HGST Hard Disk Drive Specification 238

WRITE AND VERIFY (10) - (2E)

Byte 0 1 2-5 6 7-8 9

7

6

5

WRPROTECT (MSB)

(MSB) VU = 0

Bit

4

3

Command Code = 2Eh

DPO

RSVD = 0

2

1

ByteChk

Logical Block Address

Reserved = 0

Transfer Length

Reserved = 0

FLAG

0 Obsolete
(LSB)
(LSB) LINK

Table 263 WRITE AND VERIFY (10) - (2E)

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. If caching is enabled, an implied FUA (Force Unit Access) and an implied Synchronize Cache are performed before starting the operation. This insures that data from the disk, not the cache, is verified.
- See the WRITE (10) command description for the definition of the WRPROTECT field.
- Transfer Length is the number of contiguous blocks to transferred. If the transfer length is zero, the seek occurs, but no data is transferred. This condition is not considered an error.
If caching is enabled, the command performs an implied FUA and an implied Synchronize Cache before starting the operation. This insures that the medium, not the cache, is being verified.

ByteChk Function

00b

Indicates that the data is read from the disk and verified using LDPC. If an LDPC error is detected

in the verify process, Check Condition status is returned with sense key set to Medium Error.

01b

Indicates that a byte-by-byte comparison is performed between the data on the disk and data

transferred from the initiator during the data-out phase. The number of logical blocks transferred

must equal the Verification Length field. If the comparison is unsuccessful, the command is

terminated with Check Condition status and the sense key is set to Miscompare.

10b

Not defined

11b

Indicates that a byte-by-byte comparison is performed between the data on the disk and data

transferred from the initiator during the data-out phase. The number of logical blocks transferred

must equal one. All blocks specified by the Verification Length will be compared against the

single block of data transferred by the initiator. If the comparison is unsuccessful, the command

is terminated with Check Condition status and the sense key is set to Miscompare.

Table 264 Byte Check

- DPO (Disable Page Out) bit of one indicates that the data written by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified 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.

HGST Hard Disk Drive Specification 239

WRITE AND VERIFY (12) - (AE)

Bit

Byte

7

6

5

4

3

2

1

0

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

Reserved = 0

11

VU = 0

Reserved = 0

FLAG

LINK

Table 265 WRITE and VERIFY (12) - (AE)
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. See the WRITE AND VERIFY (10) description for the definitions of the fields in this command.

HGST Hard Disk Drive Specification 240

WRITE AND VERIFY (16) - (8E)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 8Eh

1

WRPROTECT

DPO RSVD = 0

ByteChk

Obsolete

(MSB) 2-9

Logical Block Address

(LSB)

10-13

(MSB)

Transfer Length

(LSB)

14

Reserved = 0

15

VU = 0

Reserved = 0

FLAG

LINK

Table 266 WRITE and VERIFY (16) - (8E)
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.

HGST Hard Disk Drive Specification 241

WRITE AND VERIFY (32) - (7F/0C)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 7Fh

1

VU = 0

Reserved = 0

FLAG

LINK

2-5

Reserved = 0

6

Reserved = 0

Group Number = 0

7

Additional CDB Length = 18h

8-9

Service Action = 000Ch

10

WRPROTECT

DPO RSVD = 0

ByteChk

Reserved=0

11

Reserved = 0

12-19

Logical Block Address

20-23

Expected Initial Logical Block Reference Tag

24-25

Expected Logical Block Application

26-27

Logical Block Application Tag Mask

28-31

Transfer Length

Table 267 WRITE and VERIFY (32) - (7F/0C)
The WRITE AND VERIFY command requests that the drive write the data transferred from the initiator to disk and then verify that the data is correctly written.
If the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data), then this command will be processed normally. Any other protection types will result in Check Condition status to be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code
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. 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.

HGST Hard Disk Drive Specification 242

WRITE BUFFER (3B)

Byte
0 1 2 3-5 6-8 9

7

6

5

Mode Specific

VU = 0

Bit

4

3

2

Command Code = 3Bh

Mode

Buffer ID

Buffer Offset

Parameter List Length

Reserved = 0

1 FLAG

0 LINK

Table 268 WRITE BUFFER (3B)

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. Additional modes are provided for downloading microcode and saving microcode.
This command will cause the entire cache to be emptied.
The function of this command and the meaning of fields within the command descriptor block depend on the contents of the mode field.
If any values other than shown above are specified, Check Condition status is returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.

MOD 00000 00010 00100 00101 00111 01010 01101

Description Write combined header and data Data Download Microcode Download Microcode and Save - single binary file Download Microcode and Save - multiple binary files Write Data to Echo Buffer Download microcode with offsets, select activation events, save, and defer activate

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. 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. Parameter List Length specifies the number of bytes that shall be transferred during the DATA OUT phase. This number includes four bytes of header, so the data length to be stored in the drive buffer is transfer length minus four. If the length exceeds the buffer size, the command is terminated with Check Condition status. And the drive shall set sense key to Illegal Request and additional sense code to Illegal Field in CDB. A Parameter List Length of less than four (size of header) indicates no data is transferred. The 4-byte header consists of all reserved bytes.

Bit

Byte

7

6

5

4

3

2

1

0

0-3

Reserved = 0

Table 269 Write Buffer Header

HGST Hard Disk Drive Specification 243

Write Data (Mode 00010b)
In this mode, the DATA OUT phase contains buffer data. 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 specifies the offset of the memory space specified by the Buffer ID. The initiator should conform to the offset boundary requirements returned in the READ BUFFER descriptor. If the value exceeds the buffer specified, 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. Parameter List Length specifies the Parameter List Length. It must be
- less than the capacity of the buffer size after adding the Buffer Offset value and - on a sector boundary A Parameter List Length of zero indicates no data is to be transferred and command status is returned. If an invalid value is specified, 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.
Download Microcode (Mode 00100b)
NOTE: It is not expected that a customer will ever issue this format of the command. In this mode, the microcode is transferred to the control memory space of the drive. When downloaded, the drive will operate with the newly downloaded code immediately until the next power cycle. Buffer ID field is used to indicate which portion of the microcode image is being downloaded. The following Buffer IDs are supported by the Target:
- 00h: Main Microprocessor Code - nnh: ID of Vendor Unique Reserved Area Any unsupported value for the Buffer ID will cause the command to terminate 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. 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. If an invalid value is specified, 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. This process generates a unit attention condition for MICROCODE HAS BEEN CHANGED for all Initiators except the one which sent the WRITE BUFFER command. Upon the completion of the WRITE BUFFER command the new microcode is immediately ready for operation. Note: The Download Microcode mode described in this specification is to indicate that the drive will accept a command with this mode, though it is not expected that a user will ever issue such a command. To use the write buffer command with this mode, a special microcode version is required from development. If such a microcode is released from development, then it will include appropriate instructions on the function of new microcode and its effect on the drive operations after download.
HGST Hard Disk Drive Specification 244

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

Download Microcode with Offsets, Select Activation Events, Save, and Defer Activate (Mode 01101b)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER commands, saved to nonvolatile storage, and considered deferred. The deferred microcode shall be activated and no longer considered deferred if a WRITE BUFFER command with the activate deferred microcode mode (0Fh) is processed
The Mode Specific field specifies additional events that shall be used to activate the deferred microcode.

7 PO_ACT

Bit

7

7

PO_ACT PO_ACT

7 PO_ACT

Table 270 Mode Specific Field
If the power on activate (PO_ACT) bit is set to one, then deferred microcode shall be activated and no longer considered deferred if a power on occurs. If the PO_ACT bit is set to zero, then deferred microcode shall not be activated if a power on occurs. The hard reset activate (HR_ACT) bit is not supported. The vendor specific event activate (VSE_ACT) bit is not supported. The supported activation events are reported in the POA_SUP bit, HRA_SUP bit, and VSA_SUP bit in the Extended Inquiry VPD page. If the Mode Specific field specifies an activation event that is not supported (e.g., if the PO_ACT bit is set to one and the POA_SUP bit is set to zero), then the drive will 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 CDB.

Download Microcode with Offsets, Save, and Defer Activate (Mode 01110b)

In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER commands, saved to nonvolatile storage, and considered deferred. The deferred microcode shall be activated and no longer considered deferred when one of the following occurs:
a) a power on; b) a WRITE BUFFER command with the activate deferred microcode mode (0Fh) is processed. c) a Self Initiated Reset occurs.

Activate Deferred Microcode Mode (Mode 01111b)

In this mode, deferred microcode that has been saved using the download microcode with offsets, save, and defer activate mode, if any, shall be activated and no longer considered deferred. The BUFFER ID field, the BUFFER OFFSET field, and PARAMETER LIST LENGTH field shall be ignored in this mode.

Enable Expander Communications Protocol (Mode 11010b)

In this mode the drive behavior is the same as Write Data to Echo Buffer (Mode 0101b).

HGST Hard Disk Drive Specification 246

WRITE LONG (10) (3F)

Byte 0 1 2-5 6 7-8 9

7
COR_DIS (MSB)

6 WR_UNCOR

Bit

5

4

3

2

Command Code = 3Bh

PBLOCK=0

Reserved = 0

Logical Block Address

(MSB)

Reserved = 0 Byte Transfer Length

VU = 0

Reserved = 0

1

0

Obsolete

(LSB)

FLAG

(LSB) LINK

Table 271 WRITE LONG (3F)
The WRITE LONG command requests the drive to write one block of data transferred from the Initiator. The transfer data must include
- User Data - 18 bytes of MEDC data
All WRITE LONG commands will behave as if the WR_UNCOR bit was set with the exception of having the COR_DIS bit set. COR_DIS bit behavior will take precedence if both WR_UNCOR and COR_DIS bits are set
Parameters are - COR_DIS - correction disabled, bit 7 in byte 1. When this bit is set to one, the drive will mark the LBA as a
pseudo unrecovered error with correction disabled. A subsequent read to this LBA would: a) Perform no error recovery on the block; perform no automatic reallocation of the affected logical blocks,
including any automatic reallocation enabled by the Read-Write Error Recovery mode page; b) Not consider errors on the affected logical blocks to be informational exception conditions as defined in the
Information Exceptions Control mode page (see SPC-4); c) not log errors on the affected logical blocks in the Error Counter log pages d) 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.

- WR_UNCOR - write uncorrectable, bit 6 in byte 1. If the COR_DIS bit is not set, the drive will behave in the following manor regardless of the state of this bit. The drive will create a pseudo unrecovered error with correction enabled. On following read commands to the LBA, the drive will: a) use our normal recovery procedures (which will end in a hard error); b) perform no automatic reallocation of the affected logical blocks, including any automatic reallocation enabled by the Read-Write Error Recovery mode page; c) consider errors on the affected logical blocks to be informational exception conditions as defined in the Information Exceptions Control mode page (see SPC-4); d) log errors on the affected logical blocks in the Error Counter log pages 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. This field must specify the exact number of bytes of data available for transfer. If a nonzero byte transfer length does not match the available data length, the Target terminates the command with Check Condition status, then the sense key is set to Illegal Request, and an additional sense code is set to Invalid Field in CDB. The valid and ILI bits are set to one and the information field is set to the difference of the requested length minus the actual length in bytes. Negative values are indicated by two's complement notation.

HGST Hard Disk Drive Specification 247

WRITE LONG (16) - (9F)

Byte 0 1 2-9

7

6

COR_DIS WR_UNCOR (MSB)

Bit

5

4

3

2

1

Command Code = 9Fh

PBLOCK=0

Service Action (11h)

Logical Block Address

10-11 12-13

(MSB)

Reserved = 0 Byte Transfer Length

14

15

VU = 0

Table 272 WRITE LONG (9F) Refer to 8.65 Write Long (10) for field definitions.

Reserved = 0 Reserved = 0

FLAG

0
(LSB) (LSB) LINK

HGST Hard Disk Drive Specification 248

WRITE SAME (10) - (41)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 41h

1

WRPROTECT

Reserved = 0 PBDATA=0 LBDATA=0 Obsolete

(MSB) 2-5

Logical Block Address

(LSB)

6

Reserved = 0

(MSB) 7-8

Number of Blocks

(LSB)

9

VU = 0

Reserved = 0

FLAG

LINK

Table 273 WRITE SAME (41)
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. This command is useful for writing large data areas without sending all of the data over the SCSI bus.
- See the WRITE (10) command description for the definition of the WRPROTECT field. - Logical Block Address specifies the address at which the write begins. The Number of Blocks specifies the
number of contiguous blocks to be written. If the number is zero, all of the remaining blocks on the specified Logical Unit are written. - Number of Blocks specifies the number of contiguous blocks to be written. If the number is zero, all of the remaining blocks on the specified logical unit are written. - RelAdr (Relative Block Address) is not supported and must be set to be zero.
The data for this command is not retained in the cache.

HGST Hard Disk Drive Specification 249

WRITE SAME (16) - (93)

Bit

Byte

7

6

5

4

3

2

1

0

0

Command Code = 93h

1

WRPROTECT

Reserved = 0 PBDATA=0 LBDATA=0 Obsolete

(MSB) 2-9

Logical Block Address

(LSB)

(MSB) 10-13

Number of Blocks

(LSB)

14

Reserved = 0

15

VU = 0

Reserved = 0

FLAG

LINK

Table 274 WRITE SAME (16) - (93)
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. This command is useful for writing large data areas without sending all of the data over the SCSI bus. See the WRITE (10) command description for the definition of the WRPROTECT field.

HGST Hard Disk Drive Specification 250

WRITE SAME (32) - (7F/0D)

Bit Byte

7

6

5

4

3

2

1

0

0

Command Code = 7Fh

1

VU = 0

Reserved = 0

FLAG

LINK

2-5

Reserved = 0

6

Reserved = 0

Group Number = 0

7

Additional CDB Length = 18h

8-9

Service Action = 000Dh

10

WRPROTECT

Reserved = 0 PBDATA=0 LBDATA=0 Reserved =0

11 12-19 20-23 24-25 26-27 28-31

(MSB) (MSB) (MSB) (MSB) (MSB)

Reserved = 0 Logical Block Address Expected Initial Logical Block Reference Tag Expected Logical Block Application Tag Logical Block Application Tag Mask
Number of Blocks

(LSB) (LSB) (LSB) (LSB) (LSB)

Table 275 WRITE SAME (32) - (7F/0D)

The WRITE SAME command requests that the drive write a single block of data transferred from the initiator to disk for a number of sequential logical blocks. This command is useful for writing large data areas with the same data, without sending all of the data over the interface. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the drive format. Each logical block written includes user data and, if the drive is formatted with protection information enabled, protection information.

If the drive is formatted with type 2 protection (PROT_EN=1 and P_TYPE=001b in the READ CAPACITY (16) parameter data), then this command will be processed normally. Any other protection types will result in Check Condition status to be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code

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

HGST Hard Disk Drive Specification 251

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.

Bit

7

6

5

4

3

2

1

0

Reserved = 0

Status Code

RSVD

Table 276 SCSI Status Byte. Format of the SCSI STATUS byte.

STATUS BYTE Description

00h

GOOD

The command has been successfully completed.

02h

CHECK CONDITION

An error, exception, or abnormal condition has been detected. The sense data is set by the

drive. The REQUEST SENSE command should be issued to determine the nature of the

condition.

04h

CONDITION MET

This status is returned when an unlinked PRE-FETCH command has been successfully

completed.

08h

BUSY

This condition is returned when disconnect privilege is not granted while the drive is BUSY

processing the other command for the other initiator. The normal initiator recovery action is to

issue the command at a later time or to reissue the command and grant the disconnect

privilege.

10h

INTERMEDIATE

Not supported.

14h

INTERMEDIATE CONDITION MET

Not supported.

18h

RESERVATION CONFLICT

This status is returned whenever an SCSI device attempts to access the drive, but it has been

reserved by another initiator.

28h

QUEUE FULL

This status indicates that the target's command queue is full. If a tagged command queuing

feature is enabled and there is no room on the command queue, this status is returned when

the initiator sends a command. For this status, sense data are not valid.

HGST Hard Disk Drive Specification 252

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.
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.
Priority of SCSI Status Byte Reporting
After establishing the I_T_L nexus or I_T_L_Q nexus the Target must first determine whether command execution is allowed. Execution is deferred until a later time if the command must be added to the command queue. Execution may also be prevented by an internal Target condition that requires the reporting of a Check Condition, Queue Full, Busy, or Reservation Conflict Status. There are several different internal conditions to be active at the same time. The order in which the Target checks for each of these conditions determines their priority (highest priority first) as follows:
1. Check Condition status for invalid Logical Unit Number. (See Section 10.1.2 "Invalid LUN Processing") 2. Check Condition status for Incorrect Initiator Connection (See Section 10.1.3 "Overlapped Commands") 3. Check Condition status for Unit Attention Condition (See Section 10.1.5 "Unit Attention Condition") 4. Busy Status or Queue Full Status (See 10.1.4 "Command Processing During Execution of Active I/O
Process") 5. Check Condition status for Deferred Error Condition (See Section 10.1.8 "Deferred Error Condition") 6. Check Condition status during Startup and Format operations (See Section 10.1.6 "Command Processing
During Startup and Format Operations") 7. Reservation Conflict status (See Section 10.1.10 "Command Processing while Reserved") 8. Check Condition status for invalid command op code 9. Check Condition status for invalid command descriptor block
The highest priority internal condition that prevents command execution is reported by the Target provided there is no bus error. For all Check Conditions Sense data is built by the target provided a valid LUN address is known. Sense data is cleared by the Target upon receipt of any subsequent command to the LUN from the initiator receiving the Check Condition.
Invalid LUN Processing
Any value other than zero is invalid. The target's response to an invalid LUN varies with the command, as follows:
Inquiry: Execute the command, return the INQUIRY data that indicates unknown device type (byte 0 = 7Fh), and return GOOD status. All other bytes are valid (see 8.5 "INQUIRY (12)"). Request Sense: Execute the command, return the sense data with the Sense Key set to Illegal Request and the Additional Sense Code and Additional Sense Code Qualifier set to LOGICAL UNIT NOT SUPPORTED, and return GOOD status (see also 8.36 "REQUEST SENSE (03)"). All Others: Do not execute the command and return CHECK CONDITION status, along with the auto-sense data with the Sense Key set to Illegal Request and the Additional Sense Code and Additional Sense Code Qualifier set to LOGICAL UNIT NOT SUPPORTED. In all cases, the target's response to the command for an invalid LUN does not affect the current execution of a command on the valid LUN for this initiator or any other initiator.
HGST Hard Disk Drive Specification 253

Overlapped Commands
The drive does not perform any overlapped command checking.
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 10.1.1 "Priority of SCSI Status Byte Reporting"). If an active I/O process exists when the target receives a new command, then the target determines if:
- the command is permitted to execute - the command is added to the queue - Queue Full status is to be returned - Busy status is to be returned If an active I/O process exists when the target receives a new command, then the target determines how the new command should be handled based on the following rules: - Check Condition status is returned with sense key set to Logical Unit Not Ready if: - the startup operation or a format operation is active. See Command Processing During Execution of Active I/O
Process for the exact conditions which cause this response. Note: If a Unit Attention is pending when this condition exists, the sense key is set to Unit Attention rather than Logical Unit Not Ready since Unit Attention has a higher reporting priority (see 10.1.4 "Command Processing During Execution of Active I/O Process")
- The command is permitted to execute if: - the command is a priority command (see Concurrent I/O Process the conditions to execute concurrently are
met (see 10.1.1 "Priority of SCSI Status Byte Reporting") - The command is added to the queue if: - any I/O process already exists at the target, and - this is not an incorrect initiator connection. - Queue Full status is returned if: - the command would otherwise be added to the queue (according to the rules described above), but all slots in
the queue are full, or the command would otherwise be added to the queue (according to the rules described above), but all of the available queue slots not reserved for use by another initiator are full, or a Format Unit command was previously queued but has not yet begun execution, or the target is in a Degraded Mode (see "Degraded Mode") and a Start Unit command was previously queued but has not yet begun execution. - Busy status is never returned on SCSI or FCAL. BUSY status is returned on SAS if more than 64 unique Initiators send frames to the drive since the last POR. In that case, BUSY status in only returned for Initiators above and beyond the first 64.
HGST Hard Disk Drive Specification 254

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. The Additional Sense Code and Additional Sense Code Qualifier reported is MODE PARAMETERS CHANGED. The unit attention condition is generated if any of the current page parameters are set by the MODE SELECT command. The target does not check to see that the old parameters are different from the new parameters. For example: If the initiator issues a MODE SENSE command with a page code to report the current values followed by a MODE SELECT command with the same parameter list, a unit attention condition is generated despite the fact that the current parameters were not changed from their previous value. However, if the target detects an illegal parameter or error condition prior to modifying the current parameters, a unit attention condition is not generated since the parameters were not set. The unit attention condition is also not generated if the MODE SELECT command parameter list does not include any pages and only the header or header/block descriptor is present.
- FORMAT UNIT command has been executed In this case, a unit attention condition is generated for all initiators except the one that issued the FORMAT UNIT command. The Additional Sense Code and Additional Sense Code Qualifier reported is NOT READY TO READY TRANSITION, (MEDIUM MAY HAVE CHANGED). This indicates that the block descriptor parameters from the last MODE SELECT command have been used and are now considered current values.
- WRITE BUFFER command to download microcode has been executed In this case, a unit attention condition is generated for all initiators except the one that issued the WRITE BUFFER command. The Additional Sense Code and Additional Sense Code Qualifier reported is MICROCODE HAS BEEN CHANGED.
- Commands Cleared by another initiator This unit attention condition is generated after an initiator sends a Clear Task Set Task Management function. The unit attention condition is generated for all other initiators with I/O processes that were either active or queued for the logical unit. The Additional Sense Code and Additional Sense Code Qualifier reported is COMMANDS CLEARED BY ANOTHER INITIATOR.
- LOG SELECT command with PCR bit has cleared parameters. In this case, a unit attention condition is generated for all initiators except the one that issued the LOG SELECT command. The additional sense code and additional sense code qualifier reported is Log Select Parameters Changed.
- The registration or reservation made by a Persistent Reserve Out command was cleared by another initiator. In this case, a unit attention condition is generated for the initiator that held the cleared registration or reservation.
- A Predictive Failure Analysis threshold has been reached and the Method of Reporting field of mode page 1Ch is 2h.
- The unit attention condition persists for each initiator until that initiator clears the condition from the logical unit as described below. Several commands are handled as special cases during a unit attention condition these cases are also discussed below.
HGST Hard Disk Drive Specification 255

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

Execute the command, return GOOD status, and preserve the unit attention condition.

Report Luns

Same as above

Request Sense

Execute the command, return any pending sense data, return GOOD status, and preserve the unit attention condition. If there is not any pending sense data, the sense data associated with the highest priority unit attention condition is returned and the highest priority unit attention condition is cleared for this initiator.

All Others

Do not execute the command, return a CHECK CONDITION status, clear the highest priority unit attention condition for this initiator and return the associated sense data.

More than one unit attention condition may be generated for an initiator before that initiator clears the unit attention condition.

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.

The Additional Sense Code Qualifier that is returned depends on type of I/O processes that are active:

For the START/UNIT STOP and the Auto-start operation, the qualifier returned is LOGICAL UNIT IS IN PROCESS OF BECOMING READY. For the FORMAT UNIT command, the qualifier returned is LOGICAL UNIT NOT READY, FORMAT IN PROGRESS, and the Sense key specific bytes are set to return the progress indication.

REPORT LUNS

The drive sends REPORT LUNS data and appropriate status.

ALL OTHER

The drive terminates the command with CHECK CONDITION status. The Sense data generated is described in Request Sense above.

Internal Error Condition

The Target generates an Internal Error condition for all Initiators when an internally initiated operation ends with an unrecoverable error, that is, the startup sequence for Auto Start enabled terminates after the SCSI bus has been enabled and prior to completion of the bring-up sequence. An Internal Error condition causes Sense data to be generated and saved for all Initiators. The Error Code field of the Sense is set for a Current Error (70h or 72h) and the Sense Key is set to HARDWARE ERROR. Recovered errors are not reported. The Internal Error condition persists for each Initiator until that Initiator clears the condition from the logical unit as described below. Several commands are handled as special cases during an Internal Error condition. These cases are also discussed. If the Target receives a command from an Initiator while an Internal Error condition exists for that Initiator, the response of the Target varies with the command as follows:

INQUIRY REQUEST SENSE

The drive executes the command with GOOD status and does not clear the Internal Error condition.
The drive executes the command, returns the sense data generated by the Internal Error condition, returns Good Status, and clears the Internal Error condition for that Initiator.

ALL OTHER

The drive terminates the command with a CHECK CONDITION status and clears the Internal Error condition.

HGST Hard Disk Drive Specification 256

Deferred Error Condition

Error code (71h or 73h) of sense data indicates that the Check Condition status returned is the result of an error or exception condition that occurred during execution of a previous command for which Good status has already been returned. The drive creates an Deferred Error condition when
- Execution of a Format Unit command with the immediate bit of one ends with an error.
- Execution of a Write command with WCE (Write Cache Enable) bit of one ends with an error.

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. There are 3 conditions in the Degraded Mode:
- Spindle Motor Degrade which is caused by one of the following conditions: - Spindle Motor was started (by POR or Unit Start command) and the Target is under Self Configuration. - Spindle Motor Failed to start. - Spindle Motor was stopped by Unit Stop command after the Target successfully completed the Self Configuration.
- Self Configuration Failure Degraded which is caused by one of the following conditions: - RAM Code, Configuration Sector Read Failure - RAM Code, Configuration Sector Revision Mismatch
- Format Command Failure Degraded. This condition is caused when Format Unit command failed or was interrupted abnormally (Mode Page 0, byte 5, bit 4 FDD controls Format Degraded mode)
Response to SCSI Command in Degraded Mode - Disable Auto Start

The tables on the following pages show the degraded mode status with acceptable commands and additional sense codes

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Start Stop Unit (Start)

Response
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required)
Executed
Executed and Check Condition is returned with Sense Key 05h (Illegal Request) ASC/ASCQ 2400h (Invalid Field in CDB)
Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required)
Executed - Success: Good Status is returned. Motor Degraded Mode is cleared - Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail) - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail)
Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM Code NOT load)

Start Stop Unit (Stop) Executed. Good Status is returned. Motor Degraded Mode is NOT cleared

Other Commands

Not Executed. Check Condition Status is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required)

Table 277 Spindle Motor Degraded Mode - Disable Auto Start

HGST Hard Disk Drive Specification 257

Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Start Stop Unit (Start)
Other Commands

Response
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 0401h (In Process of Becoming Ready)
Executed
Executed and Check Condition is returned with Sense Key 05h (Illegal Request) ASC/ASCQ 2400h (Invalid Field in CDB)
Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0401h (In Process of Becoming Ready)
Executed - Success: Good Status is returned. Motor Degraded Mode is cleared - Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail) - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail)
Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM Code NOT load)
Not Executed. Check Condition Status is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0401h (In Process of Becoming Ready)

Table 278 Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up

Response to SCSI Command in Degraded Mode - Spindle Start Failure

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Start Stop Unit (Start)
Start Stop Unit (Stop) Other Commands

Response Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail) Executed Executed and Check Condition is returned with Sense Key 05h (Illegal Request) ASC/ASCQ 2400h (Invalid Field in CDB) Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail) Executed
- Success: Good Status is returned. Motor Degraded Mode is cleared - Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 0400h (Start Spindle Motor Fail) - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 4080h (Diag Fail- Bring up Fail) Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM Code NOT load)
Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
Not Executed. Check Condition Status is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail)

Table 279 Spindle Motor Degraded Mode - Spindle Start Failure

HGST Hard Disk Drive Specification 258

Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Start Stop Unit (Start)
Start Stop Unit (Stop) Other Commands

Response
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required)
Executed Executed Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required) Executed
- Success: Good Status is returned. Motor Degraded Mode is cleared - Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 0400h (Start Spindle Motor Fail) - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 4080h (Diag Fail- Bring up Fail) Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load) Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
Not Executed. Check Condition Status is returned with Sense Key 02h (Not Ready) ASC/ASCQ 0402h (Initialize Command Required)

Table 280 Spindle Motor Degraded Mode - Spindle Stopped by Command

Self Configuration Failure Degraded Mode

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Start Stop Unit (Start)
Write Buffer (Download and Save)
Other Commands

Response
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail) Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load)
Executed
Executed and Check Condition is returned with Sense Key 05h (Illegal Request) ASC/ASCQ 2400h (Invalid Field in CDB)
Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail) Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load)
Executed - Success: Good Status is returned. Motor Degraded Mode is cleared - Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail) - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail)
Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load)
Executed. - Success: Good Status is returned. Motor Degraded Mode is cleared - Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail)
Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load)
Not Executed. Check Condition Status is returned with Sense Key 02h (Not Ready) ASC/ASCQ 4080h (Diag Fail- Bring up Fail) Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM code NOT load)

Table 281 Self Configuration Failure Degraded Mode

HGST Hard Disk Drive Specification 259

Format Command Failure Degraded Mode

Command (w/Option) Request Sense Inquiry (EVPD=0) Inquiry (EVPD=1) Test Unit Ready
Format Unit
Other Commands (read and write)

Response
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ 3100h (Format Corrupted) Sense Key 03h (Medium Error) ASC/ASCQ 3100h (Format Corrupted)
Executed
Executed
Executed and Check Condition is returned with Sense Key 02h (Not Ready) ASC/ASCQ 3100h (Format Corrupted)
Executed - Success: Good Status is returned. Format Degraded Mode is cleared - Failure: Check Condition Status is returned and Format Degraded Mode is NOT
cleared.
Not Executed. Check Condition Status is returned with Sense Key 03h (Medium Error) ASC/ASCQ 3100h (Format Corrupted) Non-read/write commands will execute so the drive is as responsive as possible and for restoring normal operation.

Table 282 Format Command Failure Degraded Mode

Note: Mode Page 0 byte 5 bit 4 (FDD) = 0

Note: See also Section 10.1.9 "Degraded Mode" and Section 8.4 "FORMAT UNIT (04)".

Command Processing while Reserved

A logical unit is reserved after successful execution of the Reserve command. Each time a Reserve command is executed successfully, the Target records the SCSI ID of the Initiator that made the reservation and the SCSI ID of the Initiator that is to receive the reservation. This information is needed to determine whether subsequent commands should be permitted or if the Reservation Conflict Status should be reported. The Initiator that made the reservation is the Initiator that issued the Reserve command. The Initiator to receive the reservation may be either the same or a different Initiator (third-party reservation). If the logical unit is reserved when a new command is received, the Target examines the command opcode and the SCSI ID of the issuing Initiator to determine whether a Reservation Conflict Status should be returned based on the following rules:
If the issuing Initiator is the one that made the reservation and also the one to receive the reservation, then all commands are permitted.
If the issuing Initiator is neither the one that made the reservation nor the one to receive the reservation, then
- A Request Sense or Inquiry command is permitted. - A Release command is permitted but is ignored.
- Any other command results in a Reservation Conflict Status.
If the issuing Initiator is the one that made the reservation but is not the one to receive the reservation, then
- An Inquiry, Request Sense, Reserve, or Release command is permitted. - Any other command results in a Reservation Conflict Status.
If the issuing Initiator is not the one that made the reservation but is the one to receive the reservation, then
- 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 10.1.1 "Priority of SCSI Status Byte Reporting"

HGST Hard Disk Drive Specification 260

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.
Command Queuing
When the initiator specifies that the drive shall disable command queuing, the initiator must send only untagged commands. When the initiator specifies that the target shall enable command queuing, the initiator may send either tagged or untagged command, but shall not use both at the same time. The following commands are never queued.
- Priority Commands (i.e.: Request Sense and Inquiry) - Commands for an invalid LUN.
Queue Depth
Any initiator can queue at least one command at any time irrespective of the actions of any other initiators in the system. A single initiator may queue up to 128 commands, if no other initiator has more than one command in the queue, although at times this maximum may be reduced as the drive can reserve command blocks for internal use.
Queue Full Status
The drive will respond with QUEUE FULL status to a SCSI command when all queue slots are utilized. The SCSI command is not placed in the command queue under this condition.
Termination of I/O Processes
Normal termination of I/O processes occurs when the target returns SCSI status. I/O processes may also be terminated by the following:
- An ABORT TASK terminates the specified I/O process from the issuing initiator - An ABORT TASK SET terminates all I/O processes from the issuing initiator - A CLEAR TASK SET, TARGET RESET or reset terminates all I/O processes from all initiators
HGST Hard Disk Drive Specification 261

Command Reordering
Command reordering is supported when enabled by the Queue Algorithm Modifier in mode page 0A (see 8.10.9 "Mode Page 0A (Control Mode Page Parameters)".
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.
- WRITE commands when another WRITE command is an active I/O process - READ commands when another READ command is an active I/O process When a concurrent command ends in CHECK CONDITION status, the QErr bit on the Mode Page 0Ah will determine how other active I/O processes from the same initiator for that drive will be handled.
Write Cache
If the WCE (Write cache enable) bit is 1, the drive returns Good Status and closes the connection immediately after receiving the data of the last sector before actually writing the data onto the media. If the drive detects an error after it returns a Good Status, the drive sets a Deferred Error (Error Code of sense data = 71h) and a following command will be returned with Check Condition and the Contingent allegiance condition is established. Under the Contingent allegiance condition all queued processes including commands from other initiators are suspended.
HGST Hard Disk Drive Specification 262

Automatic Rewrite/Reallocate

The target supports Auto Reallocate for READ, WRITE, WRITE VERIFY, and VERIFY. Automatic Reallocate operates from within the read/write command. When an automatic reallocation occurs, the read or write command takes longer to complete. This operation is sometimes referred to as auto-reassignment due to its similarity to the operation performed by the reassign command. Following is a description of the target behavior for each setting of ARRE. ARRE setting affects all data errors. (No Sector Found, Data Sync Byte Errors and Data LDPC Errors.)

ARRE=1: ARRE=0:

An error site determined to need rewriting or reallocation during a read is automatically reallocated as a pending defect prior to the sending of the status. It will not be identified by a read defect data command. It will be rewritten or reallocated on the next write prior to the sending of the status. If it is reallocated it will be identified in a read defect data command.
Behaves the same as ARRE=1.

The target will automatically rewrite/reallocate for the following commands. - Read - Verify - Verify portion of Write and Verify

For all other commands the ARRE setting is ignored and the target will not automatically rewrite/ reallocate Following is a description of the target behavior for each setting of AWRE. AWRE setting affects only No Sector Found Errors on writes.

AWRE=1: AWRE=0:

An error site determined to need reassignment during a write is automatically reallocated at the conclusion of the write and prior to sending the status. The site will be automatically reallocated only if the write recovery succeeded at the conclusion of the write.
Behaves the same as AWRE=1

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. The sense data combinations with auto/recommend rewrite/reallocate are listed below.

Key Code Qual Description

1

17 01 Recovered Data with retries

1

17 06 Recovered Data without LDPC - Auto Reallocated

1

17 09 Recovered Data without LDPC - Data Rewritten

1

18 00 Recovered Data with LDPC

1

18 02 Recovered Data with LDPC - Auto Reallocated

1

18 07 Recovered Data with LDPC - Data Rewritten

Table 283 Sense data combinations with auto/recommend rewrite/reallocate

HGST Hard Disk Drive Specification 263

Segmented Caching
Overview
Segmented Caching divides the data buffer into several smaller buffers. Each buffer is used as Read/ Write/ReadAhead buffer.
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. The Read Ahead function works when RCD (the read cache disable) bit of read cache page (page 08h) is set to zero. The drive initiates the Read ahead function when the following conditions exist:
- RCD is 0 - Read, Verify and Write and Verify is received. - The consecutive LBA of the requested LBA is not available in the buffer If SCSI reset or target reset message is received, all contents of segmented buffer is flushed. Even if an error occurs during the Read ahead, the error will not be reported to the Initiator. The data read before the error occurred will be stored as valid data by the Read Ahead function.
Multiple Initiator Systems
This section describes how the target behaves in a multiple initiator system. Up to 64 initiators may be supported at any one time.
Sense Data
A separate sense data area is reserved for each initiator. Each area is maintained independently. This allows a command from one initiator to complete with a CHECK CONDITION status and generate sense data without being affected by a subsequent command from a different initiator. There is no requirement for the first initiator to send a REQUEST SENSE command to retrieve the Sense Data prior to the execution of a command from a different initiator.
Mode Pages
A single set of Mode pages is maintained. This includes both current and saved parameters. If a MODE SELECT command is executed that updates the current parameters, a unit attention condition is generated for all initiators except the one that issued the command. See 10.1.5 "Unit Attention Condition" for more information.
Multiple Initiator Environment
Initiator Sense Data
Separate sense data is reserved for each I-T-L. Each sense data is maintained independent of commands from other initiators.
Initiator Mode Select/Mode Sense Parameters
A single shared copy of the Mode Select/Mode Sense parameters is maintained by the drive. This includes both the current and saved parameters.
HGST Hard Disk Drive Specification 264

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.

Initiator Sense Data

There are four sources of resets detected by the target:

Reset Name

Reset Source

Power-On Reset Self-Initiated reset

This is the signal generated by the hardware at initial power-on
This is a software-generated reset that occurs when a catastrophic error is detected by the microcode.

Hard Reset

This is the Hard Reset performed during a Link Reset Sequence.

LUN Reset

This is a LUN RESET TMF (08h) sent in a TASK IU.

Reset Actions

The action taken by the drive following a reset is dependent on the source of the reset.

Power-On reset and Self-Initiated reset

These two reset conditions cause the following to be performed in the order shown: - A power-up sequence - A startup sequence is necessary to put the drive in a ready state
These reset conditions cause the following actions:
- If the reset occurs during the power-up sequence, the power-up sequence is re-started. - If the auto-start option is enabled and a start-up sequence has not yet completed, the start-up sequence is
restarted. Note: The power-up sequence is not re-run, since it has already completed. - If the reset occurs while a physical sector is being written, the WRITE operation is disabled at the end of the
current sector. The media is not corrupted if power is maintained to the end of the current sector.

HGST Hard Disk Drive Specification 265

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.
Power on Diagnostics
At power on time the following tests are executed: 1. Validation of ROM and EEPROM 2. RAM test for internal RAM 3. Test and Initialize HDC registers 4. RAM test for Sector Buffer 5. Start Spindle Motor (if enabled) 6. Calibration of Actuator 7. Read/Write test for all Heads 8. Validation of RAM code and data table (RDM, Log, Mode Page) from the Reserved Area
If Auto spin up is disabled, steps 5 - 8 will be executed by the first START STOP UNIT command which has the Start bit set. Faults detected before successful completion of the HDC section could prevent the drive from responding to a selection. Faults detected after the successful completion of the HDC test section will be reported as CHECK CONDITION status to the Initiator on the first command issued after a fault is detected (except for the INQUIRY, REPORT LUNS and REQUEST SENSE commands). The INQUIRY, REPORT LUNS and REQUEST SENSE commands will always be responded with a GOOD status. Detecting a fault during power on will not terminate execution of the tests nor will it terminate the power on process.
Self-test via SEND DIAGNOSTIC Command
Default Self-test
The default self-test is invoked by the SlfTst bit in the SEND DIAGNOSTIC command. The response is simply a GOOD status if the test is successful or a CHECK CONDITION status if the test fails. The following tests are performed by the default self-test (in the order defined):
1. Spin check is to check if the spindle motor is running at the correct speed. 2. Write, Read and Compare test is a disk read/write test. It writes data to a predefined location in the
reserved area and then reads it back and validates the content. All heads are tested. 3. Seek test is a servo test. It validates seeks to 256 random locations out of the full volume.
Short and Extended Self-tests
There are two other types of self-tests that may be invoked using the Function Code field in the SEND DIAGNOSTIC command: a short self-test and an extended self-test. The tests performed in the short and extended self-tests are described later. The time required by a logical unit to complete its extended self- test is specified in the Extended self-test Completion Time field in the Control Mode Page. A value of FFFFh indicates that the extended self-test takes 65,535 seconds or longer. See also the EXTENDED SELF-TEST COMPLETION MINUTES field in the Extended INQUIRY Data VPD page. The results of self-test can be retrieved via the LOG SENSE command for Log Page 10.
HGST Hard Disk Drive Specification 266

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. While performing a selftest in the foreground mode, the drive will respond to all commands except INQUIRY, REPORT LUNS, and REQUEST SENSE with a CHECK CONDITION status, a sense key of NOT READY and an additional sense code of LOGICAL UNIT NOT READY - SELF-TEST IN PROGRESS.
If the drive is performing a self-test in the foreground mode and a test error occurs, the drive will update the self-test results log page and report CHECK CONDITION status with a sense key of HARDWARE ERROR and an additional sense code of LOGICAL UNIT FAILED SELF-TEST. The application client may obtain additional information about the failure by reading the self-test results log page.
An application client may terminate a self-test that is being performed in the foreground mode using an ABORT TASK, ABORT TASK SET, or CLEAR TASK SET task management function. If the drive receives an ABORT TASK, ABORT TASK SET, or CLEAR TASK SET task management function while performing a self-test in the foreground mode, it will abort the self-test and update the self-test results log page.
Background mode When the drive receives a SEND DIAGNOSTIC command specifying a self-test to be performed in the background mode, the drive will return status for that command as soon as the command descriptor block has been validated. After returning status for the SEND DIAGNOSTIC command specifying a self- test to be performed in the background mode, the drive will initialize the self-test results log page as follows. The Function Code from the SEND DIAGNOSTIC command will be placed in the Function Code field in the log page. The self-test Results field shall be set to 0Fh. After the self-test results log page is initialized, the drive will begin the first self-test segment.
While the device server is performing a self-test in the background mode, it shall terminate with a CHECK CONDITION status any SEND DIAGNOSTIC command it receives that meets one of the following criteria:
a. The SlfTst bit is one
b. The Function Code field contains a value other than 000b or 100b.
When terminating the SEND DIAGNOSTIC command, the sense key shall be set to NOT READY and the additional sense code shall be set to LOGICAL UNIT NOT READY, SELF-TEST in PROGRESS. While performing a self-test in the background mode, the drive will suspend the self- test to service any other command other than SEND DIAGNOSTIC (with Function Code field set to 100b) WRITE BUFFER (with the mode set to any download microcode option), FORMAT UNIT and START UNIT STOP command. Suspension of the self-test to service the command will occur within 2 seconds. If SEND DIAGNOSTIC (with Function Code field set to 100b), WRITE BUFFER (with the mode set to any download microcode option), FORMAT UNIT or START UNIT STOP command is received, the drive will abort the self-test, update the self-test log, and service the command within two seconds after the command descriptor block has been validated.
An application client may terminate a self-test that is being performed in the background mode by issuing a SEND DIAGNOSTIC command with the Function Code field set to 100b (Abort background self-test function).
Elements common to foreground and background self-test modes The Progress Indication field returned in response to a REQUEST SENSE command may be used by the application client at any time during execution of a self-test to poll the progress of the test. While executing a selftest unless an error has occurred, the drive will respond to a REQUEST SENSE command by returning a sense key of NOT READY and an additional sense code of LOGICAL UNIT NOT READY - SELF-TEST IN PROGRESS with the sense key specific bytes set for progress indication.
The application client may obtain information about the twenty most recently completed self-tests by reading the self-test results log page. This is the only method for an application client to obtain information about self-tests performed in the background mode. The default self-test results are not logged in the log page.
Tests performed in the Short and Extended Self-test The following table defines the tests performed in the short and extended self test. They are defined by their segment number which is also used to report Self-Test Results, in Log Sense Page 10. Note that the only
HGST Hard Disk Drive Specification 267

difference between the Short and the Extended tests, is the sequential verify test in segment 7h. Also note that either of these tests can be run in foreground or background mode as previously described.

Segment Short Self-Test Number

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 10.12.2.1 "Default Self-test"

3h

SMART

Perform SMART testing and check results to ensure that SMART threshold criteria are not exceeded

4h

Low Level Format check

Check to insure that the media is currently not in the MEDIA FORMAT CORRUPTED state.

5h

Physical Head Check

Write/Read test on each head in a predefined location in the drive's Reserved Area of the disk.

6h

Random Verify

Perform 4000 random verify operations and insure no uncorrectable errors.

7h

- Verify First 300MB Verify all LBA's Sequential verify operation. Ensure that no

- Verify Last 100 MB

uncorrectable errors occur within the verify range.

8h

Recheck SMART

Same as segment 4h.

Table 284 Short and Extended Self-Test Description
Background Medium Scan
For a related function, see Mode Page 1C (Informational Exceptions Control).

HGST Hard Disk Drive Specification 268

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.
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. The following times are for environments where Automatic Reallocation is disabled and there are no queued commands.
Reassignment Time
The drive should be allowed a minimum of 5 seconds to complete a "Reassign Blocks" command.
Format Time
Approximately 13.5 / 10 hours should be allowed for 8000 / 6000 GB capacity drives to complete a "Format Unit" command when certification is disabled. Allow 27 / 20 hours for 8000 / 6000 GB capacity drives when certification is enabled. If "Fast Format" is enabled via the FFMT bit in mode page 00h, allow 1 minute for completion.
Start/Stop Unit Time
The drive should be allowed a minimum of 30 seconds to complete a "Start Stop Unit" command (with Immed bit = 0). Initiators should also use this time to allow startup sequences initiated by auto start ups and "Start Stop Unit" commands (with Immed bit = 1) to complete and place the drive in a "ready for use" state. Note: A time-out of one minute or more is recommended but NOT required. The larger system time-out limit allows the system to take advantage of the extensive ERP/DRP that the drive may attempt in order to successfully complete the startup sequence. Note: For SAS devices a NOTIFY (Enable Spinup) primitive is required prior to actually starting to spin up the spindle motor (regardless of whether a Start Stop Command with the Start bit set, was received or not).
Medium Access Command Time
The time-out limit for medium access commands that transfer user data or non-user data or both should be a minimum of 30 seconds. These commands are
Pre-Fetch Read Read Defect Data Seek Send Diagnostic (Function Code = 0) Read Long Reassign Blocks Write Write and Verify Write Buffer Write Same Verify Note: The 30-second limit assumes the absence of bus contention and data transfers of 64 blocks or less. This time should be adjusted for anticipated bus contention and if longer user data transfers are requested.
HGST Hard Disk Drive Specification 269

Time-out Limits for Other Commands
The drive should be allowed a minimum of 30 seconds to complete these commands: Inquiry Log Select Log Sense Mode Select Mode Sense Persistent Reserve In/Out Read Buffer Read Capacity Read Long Release Request Sense Reserve Set/Report Device Identifier Start/Stop Unit (with Immed bit = 1) Synchronize Cache Test Unit Ready Writer Long
The command time-out for a command that is not located at the head of the command queue should be increased by the sum of command time-outs for all of the commands that are performed before it is.
HGST Hard Disk Drive Specification 270

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. SCSI protocol will be the first priority in reporting errors. 2. The system will maintain a log of all reported errors. 3. System architecture should include all error handling recommendations made in this section. Deviations
should have mutual agreement between Drive development and system integration. This section is directed toward documenting the assumptions made by the Drive that the system is expected to implement. The two error classes that the system should be concerned with are DATA and NON-DATA errors. Data errors are those errors that deal with the handling of data to and from the MEDIA and are identified by the Additional Sense Code contained in the sense data. The Additional Sense Codes for data errors are as follows:
- OC - Write error - 11 - Unrecovered read error - 14 - No record found - 16 - Data Synchronization mark error - 17 - Recovered read error without LDPC correction - 18 - Recovered read error with LDPC correction Typically, data errors do not include positioning of the heads or the data path though the electronics. Non data errors are those errors that do not have a direct relationship with transferring data to and from the media. Non data errors can include data handling if the media is not associated with the error (that is, interface error). The system action assumed for each class of error is outlined here.
Drive Service Strategy
The Drive service strategy is defined so the customer will be able to use the system as soon after a failure is detected as possible. The first priority is to replace the entire drive to make the system operational with minimal service time. The service representative should:
1. Back up all the customer data on this drive if possible 2. Replace the complete drive 3. Restore the customer data 4. Return the drive to customer service
Recommendations for System Error Log
The system error log should contain information about the Drive error that will allow recovery actions. The system error logs should contain all the error information returned in the sense data. At a minimum, the following information about each error occurrence should be logged.
- Valid bit and error code (Sense byte 0) - Sense Key (Sense byte 2) - Information bytes (Sense bytes 3 through 6) - Command specific information (Sense bytes 8 through 11) - Additional Sense Code (Sense byte 12) - Additional Sense Code Qualifier (Sense byte 13) - Field Replaceable Unit (Sense byte 14) - Sense Key Specific (Sense bytes 15, 16, and 17) - Vender Unique error information (Sense bytes 20 through 23)
HGST Hard Disk Drive Specification 271

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. The problem can be due to a media defect or magnetic damage. A media defect is physical damage to the recording capability of the media while magnetic damage is a defect in the bit pattern written to the media. In both cases, the error can be corrected without replacing the unit. The physical sector may require relocation. The Drive determines the need to reassign a sector. The Mode Select Page 1 option bit ARRE (See Section 8.10.3 "Mode Page 01 (Read/Write Error Recovery Parameters)") set active allows the Drive to relocate recovered read data errors. Non recovered data errors or the ARRE bit being inactive will have additional sense codes returned to recommend reassignment of sectors. The need to reassign a sector should be infrequent. Sites not meeting error rate criteria are removed from use during SAT (Surface Analysis Test) in Drive manufacturing. With the exception of some early life SAT escapes (sites that were marginally missed during SAT), reassigning defective sectors should be rare. Frequent sector reassignment may be an (early) indication of another type of failure. Sector reassignments are monitored as part of the predictive failure analysis. When a threshold is exceeded, the Drive will notify the initiator that a scheduled service action is required. Drive soft error rates are based on extraneous random faults that are not predictable. Media defects discovered after the Drive completes manufacturing final test need to be relocated so that soft error rates are not influenced by predictable known error sites. Failure of the system to properly relocate defective media sites can have a direct influence on system throughput and drive error rates.

Reassign a Physical Sector

The Drive determines the need to reassign physical sectors based on error activity. Once a physical sector requires reassignment, the Drive will reassign the physical sector.
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.

Key Code Qual Description

1

16 00 Data Synchronization Mark Error

1

17 01 Recovered Data with Retries

1

17 06 Recovered Data without LDPC - Auto Reallocated

1

17 09 Recovered Data without LDPC - Data Rewritten

1

18 00 Recovered Data with LDPC

1

18 02 Recovered Data with LDPC - Auto Reallocated

1

18 07 Recovered Data with LDPC - Data Rewritten

Table 285 Log Only Errors

Reassign Blocks Recovery

The Drive provides the capability to remove media defects without reducing capacity. Recovery from a failed reassignment consists of the following actions:
- Updating the defect descriptor to remove the LBA's that have been successfully reassigned and then retry the Reassign Blocks command. The LBA contained in the Command Specific Information field of the Sense Data is the LBA in the first defect descriptor that was not reassigned because of the failure. If the command failed because of an unrecoverable read error other than those specified in the defect descriptor, add this LBA to the defect descriptor and retry the command. Refer to Section 8.28 "REASSIGN BLOCKS (07)", for additional information.
- If the retried Reassign Blocks (07) command completes successfully, returning to normal processing. - If the retried Reassign Blocks (07) command fails, servicing the drive using the service guidelines
recommended in Section 10.15.1 "Drive Service Strategy".

HGST Hard Disk Drive Specification 272

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.
Drive Busy
The Drive is busy performing an operation. This is not an error condition. The initiator can test for completion of the operation by issuing Test Unit Ready (00) (or media access) commands.
- If the Test Unit Ready (00) (or media access) command completes with Check Condition Status then issue a Request Sense (03)
- If the specified recovery procedure for the sense data is for a condition other than drive busy, follow the recovery procedure for the condition reported.
- If the specified recovery procedure for the sense data is for a drive busy condition, then continue re-issuing the Test Unit Ready (00) and Request Sense commands for the duration of a media access time-out or until the drive returns Good Status.
- If the drive has been busy for longer than the limit specified in Section 10.14, "Command Time out Limits" then service the drive using the service guidelines recommended in Section 10.15.1 "Drive Service Strategy" Otherwise return to normal processing.
- If the Test Unit Ready (00) (or media access) command completes with Good Status, then return to normal processing.
Unrecovered Drive Error
The initiator should retry the failing command. 1. If the retry of the failing command completes with Good Status or recovered Sense Key, follow the recovery procedure in Section 10.15.4.3 "Recovered Drive Error". 2. If the retry of the failing command completes with hardware error sense, verify there is no outside cause (e.g., power supply) for the failure, then retry the failing command. a. If the retry of the failing command completes with Good Status, follow the recovery procedure in next Section 10.15.4.3 "Recovered Drive Error". b. If the retry of the failing command completes with Recovered sense or Hardware error sense, then service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy".
Recovered Drive Error
The Initiator should log the error as soft with the recovery level.
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 10.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. If the failing command completes with Not Ready sense, verify there is no outside cause (for example, the power supply). Then service the drive using the service guidelines specified in Section 10.15.1 "Drive Service Strategy".
HGST Hard Disk Drive Specification 273

No Defect Spare
Three conditions can cause this error: 1. When the Reassign Blocks (07) command is issued and there are no spares available for the Drive to use for the relocation requested. 2. When the Glist is full and the sector to be reassigned cannot be added. 3. During a format operation, there was not enough space available to fulfill the spare requirement (Dlist is too large).
Service the Drive following Section 10.15.1 "Drive Service Strategy".
Degraded Mode
Refer to Section 10.1.9 "Degraded Mode", for the definition of this state. There are three causes for entering degraded mode. In all cases the Sense Key is Not Ready. The causes are the following:
1. Sense Code/Qualifier of Logical Unit Not Ready, initializing command required. The spindle motor not spinning or not at the proper speed. This may not be an error condition. The initiator should issue a Unit start (1B) command to start the spindle motor. If the Drive fails to come ready in the time specified in Section 10.14, "Command Time out Limits" service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy".
2. Sense Code/Qualifier of Diagnostic Failure. Failure of a Send Diagnostic self test, a start up sequence, or other internal target failures.
- Failure of a send diagnostic self test or a start up sequence.
This failure is the result of the diagnostics that are executed during power on or when the Send Diagnostic (1D) command is executed detecting a failure. As with the RAM code not loaded and the configuration data not loaded, the recovery is either a power cycle or issuing the Send Diagnostic (1D) command with the self test bit set active. Recovery for a failed Send Diagnostic (1D) is achieved in one of the following ways:
- Executing the Send Diagnostic (1D) command
- Power cycling the drive
If the failure repeats, service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy".
Recovery for a failed power up sequence is achieved in one of the following ways:
- Issuing a Unit start (1B) command
- Power cycling the drive.
If the failure repeats, service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy".
- Internal target failures
The drive periodically adjusts the track following for each head to compensate for expansion and contraction of the disks due to temperature changes. If one of these adjustments fails, the drive will enter a degraded 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 10.15.1 "Drive Service Strategy", if the power cycle or the Send Diagnostic (1D) command fail to complete successfully.
3. Sense Code/Qualifier of Format Command Failed Format Unit (04), Sense Code/Qualifier of Medium Format Corrupted Reassign Failed Reassign Blocks (07) command, or an automatic reallocation failed or was abnormally terminated.
Recovery from a failed Format Unit (04) is achieved by retrying the command. If the command fails a second time, service the drive following the procedure defined in Section 10.15.1 "Drive Service Strategy". If the above defined recovery procedures fail to clear the degraded mode condition, the Drive should be replaced. Follow the procedure in Section 10.15.1 "Drive Service Strategy", when replacing the drive.
HGST Hard Disk Drive Specification 274

Reserved Area Hard Error
Sectors found defective in the reserved area of the disk cannot be reassigned after the Drive leaves the factory. The data in the reserved area is not directly accessible by the initiator. For this reason, the reserved area has back up copies of all data. A data error must occur in both copies of the data record before the Drive considers a reserved area read error. When this happens, the integrity of the drive is questionable. Service the Drive using Section 10.15.1 "Drive Service Strategy".
Interface Protocol
For all interface protocol errors, the initiator should complete the following steps: 1. Correct the parameter that caused the Illegal Request 2. Retry the failing command 3. If the first retry of the failing command completes with - Good Status, log the error as recovered - Check Condition Status with sense data for an Illegal Request, verify there is no outside cause (for example, the power supply) for the failure - Other, follow the recommendations for the error condition reported. Retry the failing command. If this retry of the failing command completes with · Good Status, log the error as recovered · Check Condition Status with sense data for an Illegal Request, service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy". · Other, follow the recommendations for the error condition reported.
Aborted Command
The initiator should determine the cause from the Additional Sense Code (byte 12): - Sense Key = B (Aborted Command) with Additional Sense Codes of 1B, 25, 43, 49, and 4E are initiator caused abort conditions. The initiator should correct the condition that caused the abort and retry the failing command. - Sense Key = B (Aborted Command) with Additional Sense Code of 44 or 48 are drive caused abort conditions. The initiator should: 1. Retry the failing command. 2. If the retry of the failing command completes with - Good Status, log the error as recovered. - Abort Command Sense, verify there is no outside cause (e.g. power supply) for the failure. 3. Retry the failing command. 4. If the retry of the failing command completes with - Good Status, log the error as recovered. - Abort command sense, then service the drive using the service guideline recommended in Section 10.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. The initiator should follow the above procedure for Drive caused abort conditions if the initiator detected the SCSI bus parity error.
HGST Hard Disk Drive Specification 275

Unit Attention Condition
Unit Attention Conditions are not errors. They alert the initiator that the drive had an action that may have changed an initiator controlled state in the drive. These conditions are the following: Not Ready to Ready Transition Not ready to ready transition, unit formatted. This Unit Attention Condition will not be reported to the initiator that issued the Format Unit (04).
Reset Reset - This means the drive was reset by either a power-on reset, Hard Reset, LUN Reset TMF or an internal reset. Mode Parameters Changed A Mode Select (15) command successfully completed. This means that the mode parameters that are the current value may have changed. The parameters may or may not have changed but the command to change the parameters successfully completed. The Drive does not actually compare the old current and the new current parameters to determine if the parameters changed. This Unit Attention Condition will not be reported to the initiator that issued the Mode Select (15). Microcode Has Changed Write Buffer (3B) to download microcode has successfully completed. This means that the microcode that controls the Drive has been changed. The code may or may not be the same as the code currently being executed. The Drive does not compare old level code with new code. Commands Cleared by Another Initiator Tagged commands cleared by a clear queue message. This means that the command queue has been cleared. The Unit Attention Condition is not reported to the initiator that issued the clear queue message. Unit Attention Condition is reported to all initiators that had commands active or queued. Reissue any outstanding command. Log Select Parameters Changed A Log Select (4C) command successfully completed. This means that the Log Select command cleared statistical information successfully (See Section 8.6 "LOG SELECT (4C)"). Unit Attention Condition is reported to all initiators excluding the initiator that issued the Log Select command. Device Identifier Changed A Set Device Identifier (A4) command successfully completed. This means that the Set Device Identifier information field has been updated. (See 8.45 "SET DEVICE IDENTIFIER (A4/06)") A Unit Attention Condition is reported to all initiators excluding the initiator that issued the Set Device Identifier command.
Components Mismatch
The compatibility test is performed at a power cycle. The compatibility test verifies the microcode version of the electronics. When the Drive detects the microcode version mismatch, the most likely cause is the result of incorrect parts used during a service action. If the error reported is Key/code/qualifier 4/40/80, Diagnostic failure, bring-up fail, the initiator should do the following:
1. Retry Power cycle 2. Check the send diagnostic end status. If the status is
- GOOD, Return to normal processing - Check Condition Status, issue a Request Sense (03) and follow the recommendations for the sense data
returned unless the sense data is for a component mismatch. If the sense data is for component mismatch, service the drive using the service guideline recommended in Section 10.15.1 "Drive Service Strategy".
HGST Hard Disk Drive Specification 276

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 10.15.1
"Drive Service Strategy". - Other, follow the recommendations for the error reported.
Defect List Recovery
This is not an error condition. The initiator either requested a defect list in a format (block or vendor specific) that the Drive does not support or the requested defect list(s) exceed the maximum list length that can be returned. If the Sense Key/Code/Qualifier are: 1/1F/00, the requested list(s) exceed the maximum length that can be supported. The initiator should request one list at a time. If a single list exceeds the maximum returnable length, this may be an indication of a marginally operational drive. Service the drive following the service guidelines in Section 10.15.1 "Drive Service Strategy". 1/1C/01 or 1/1C/02, the requested defect list is not in the format that the Drive supports. The requested defect list is returned in the physical (cylinder, sector, head) format. This is the default format. There is no initiator action required for this condition.
Miscompare Recovery
A Miscompare can occur on a Verify (2F) command or a Write and Verify (2E) with the byte check (BytChk) bit active. Recovery for a Miscompare error is different for the two commands. Verify Command The initiator should do the following:
1. Verify that the data sent to the drive is the correct data for the byte-by-byte compare. 2. Read the data from the media with a Read (08) or Read (28) command and verify that the data from the
media is the expected data for the byte-by-byte compare. - If all data are correct, this is an indication that the data may have been read from the media incorrectly
without an error detected. Service the drive using the procedure specified in Section 10.15.1 "Drive Service Strategy". - If all data are not correct, this is an indication that the data on the media is not the data the initiator expected. Rewrite the correct data to the media. Write and Verify Command The drive uses the same data in the data buffer to write then read and compare. A Miscompare error on the Write and Verify (2E) command is an indication that the drive cannot reliably write or read the media. Service the drive using the procedures specified in Section 10.15.1 "Drive Service Strategy".
HGST Hard Disk Drive Specification 277

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 10.15.1
"Drive Service Strategy". If the check sum error occurred during normal processing, the initiator may attempt to load microcode before deciding to service the drive using the service guidelines recommended in Section 10.15.1 "Drive Service Strategy". To load new microcode, the initiator should issue a Write Buffer (3B) command with the download and save option. If the Write Buffer (3B) command completes with
- Good Status, return to normal processing. Retry the failing command. If the task complete with - Good Status - Continue normal processing. - Check Condition Status for check sum error - Service the drive using the service guidelines recommended in Section 10.15.1 "Drive Service Strategy". - Check Condition Status for any other error - follow the recommended recovery procedure for the error reported.
- Check Condition Status for Check sum error, service the drive using the service guidelines recommended in Section 10.15.1 "Drive Service Strategy".
- Check Condition Status for any other error, follow the recommendations for the returned sense data.
Predictive Failure Analysis
The Drive performs error log analysis and will alert the initiator of a potential failure. The initiator should determine if this device is the only device with error activity. If this drive is the only drive attached to the initiator with error activity, service the drive using the procedures specified in Section 10.15.1 "Drive Service Strategy". Note: Service for this drive can be deferred. The longer service is deferred, the more probable a failure can occur that will require immediate service. If more than this drive is experiencing error activity, the drive is probably not at fault. Locate and service the outside source causing error activity on this drive.
HGST Hard Disk Drive Specification 278

RAID Rebuild Assist

A rebuild operation is performed when some or all of the LBAs on a logical unit have become unreadable in a storage array controller and a new logical unit is being initialized to replace the failed logical unit. The data for the new logical unit may be constructed by reading the data from remaining logical units and using that data to reconstruct the data to be written to the replacement logical unit. The rebuild assist mode allows the storage array controller controlling the rebuild process to determine which logical blocks on the failed logical unit are unreadable without having to read every LBA to determine the unreadable logical blocks (i.e., the read command is terminated with CHECK CONDITION status and the failed LBA is reported in the sense data). The storage array controller then may reconstruct the failed logical blocks. The remaining logical blocks may be copied to the replacement logical unit.
The application client should issue sequential read commands to read the available data from the failed logical unit. If a read command does not encounter an unrecoverable LBA, then the read command should complete without error. The rebuild assist mode allows reporting of an unrecovered read error or write error that is predicted (i.e., predicted unrecovered error). Predicted unrecovered errors may be determined by the device server when rebuild assist mode in enabled.
The rebuild assist mode also allows reporting of an unrecovered read error or write error that is unpredicted (i.e., unpredicted unrecovered error). Unpredicted unrecovered errors are any unrecovered error that is not predicted when the rebuild assist mode is enabled.
If the device server encounters predicted unrecoverable LBAs on a read command, then: A) The sense key is set to ABORTED COMMAND B) The additional sense code is set to MULTIPLE READ ERRORS C) The INFORMATION field is set to the LBA of the first unrecoverable logical block D) The COMMAND-SPECIFIC INFORMATION field is set to the LBA of the last unrecovered logical block in a sequence of contiguous unrecovered logical blocks that started with the LBA specified in the INFORMATION field.
Rebuild Assist diagnostic page

The Rebuild Assist diagnostic page provides: A) A method to put the logical unit in the rebuild assist mode. B) A method to put the logical unit in a simulated failure mode in conjunction with the rebuild assist mode.
Rebuild Assist input diagnostic page

An application client may send a RECEIVE DIAGNOSTIC RESULTS command to retrieve information about a rebuild assist mode that may be enabled.

Bit

Byte

7

6

5

4

3

2

1

0

0

PAGE CODE (42h)

1

Reserved

2

(MSB)

PAGE LENGTH (4 + 2n)

3

(LSB)

4

Reserved

ENABLED

5

Reserved

6

Reserved

7

PHYSICAL ELEMENT LENGTH (n)

8

(MSB)

PHYSICAL ELEMENT MASK

7 + n

(LSB)

8 + n (MSB)

DISABLED PHYSICAL ELEMENT

7 + 2n

(LSB)

Table 286 Rebuild Assist input diagnostic page

HGST Hard Disk Drive Specification 279

Rebuild Assist output diagnostic page

An application client may send a SEND DIAGNOSTIC command to: A) Enable rebuild assist mode. B) Enable rebuild assist mode with disabling of physical elements (i.e., to simulate predicted failure of physical elements) C) Disable rebuild assist mode.

Byte

7

6

0

1

2

(MSB)

3

4

5

6

7

8

(MSB)

7 + n

8 + n (MSB)

7 + 2n

Bit

5

4

3

2

1

PAGE CODE (42h)

Reserved

PAGE LENGTH (4 + 2n)

Reserved Reserved Reserved
PHYSICAL ELEMENT LENGTH (n) PHYSICAL ELEMENT MASK

DISABLED PHYSICAL ELEMENT

0
(LSB) ENABLED
(LSB) (LSB)

Table 287 Rebuild Assist output diagnostic page

HGST Hard Disk Drive Specification 280

Firmware Security
This chapter provides information on HGST encryption-specific HDD firmware and features. It is assumed that the reader is familiar with the referenced specifications and industry standards.
Referenced Specifications and Standards
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 2.00, Revision 1.00 (4/20/2009) - The TCG Core Specification is the general specification for trusted computing that encompasses all classes of devices, including storage
2. TCG Storage Interface Interactions Specification (SIIF), Version 1.0, 1/27/2009 - Specifies the interaction between the HDD and the SCSI/ATA protocols
3. TCG Storage Security Subsystem Class (SSC): Enterprise, Version 1.00, rev 3.00 (1/10/2011) - A Security Subsystem Class defines minimum acceptable Core Specification capabilities of a storage device in a specific class (in our case ­ enterprise). - Storage devices in specific classes may have a subset of the capabilities that are defined in the core specification
4. TCG Storage Security Subsystem Class: Opal Specification, Version 2.00 Final Revision 1.00 (February 24, 2012)
Federal Information Processing Standards (FIPS)
This section references the following Federal Information Processing Standards, published by the US National Institute of Standards (NIST), which are available on the NIST website (http://www.itl.nist.gov/fipspubs/ ):
1. FIPS 197, Advanced Encryption Standard (AES), 2001 November 26. http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf
2. FIPS 180-3, Secure Hash Standard (SHS) http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf
3. FIPS 140-2, Security Requirements for Cryptographic Modules ­ 01 May 25 (Supersedes FIPS PUB 140-1, 1994 January 11) http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf
National Institute of Standards and Technology (NIST)
This section references the following NIST publications, available on the NIST website (http://www.nist.gov/index.html)
 [AES] Advanced Encryption Standard, FIPS PUB 197, NIST, 2001, November  [DSS] Digital Signature Standard, FIPS PUB 186-3, NIST, 2006, March  [FIPS140] Security Requirements for Cryptographic Modules, FIPS PUB 140-2, NIST, 2002 December  [HMAC] The Keyed-Hash Message Authentication Code, FIPS PUB 198-1, 2007 June  [SHA] Secure Hash Standard (SHS), FIPS PUB 180-3, NIST, 2007 June  [SP800-38E] Recommendation for Block Cipher Modes of Operation: The XTS-AES Mode for Confidentiality
on Storage Devices, SP800-38E, NIST, 2010 January  [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
HGST Hard Disk Drive Specification 281

 [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 Derivation, NIST, 2010 December
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
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.com/pub/pkcs/pkcs-
5v2/pkcs5v2-0.doc
Other Standards
T10 SCSI Standard. (T10 homepage - http://www.t10.org/index.html)
Implementation Exceptions
The following is a list that describes non-compliance with the TCG Enterprise SSC specification:  The SSC specification requires support for 1024 bands, but the implementation supports up to 6 bands.  The K_AES_256 table was implemented with only the UID and MODE columns.  Only one active session is permitted at a time. If a new session is requested when a session is already active, the drive answers the host with SP_BUSY, instead of NO_SESSIONS_AVAILABLE  Bands must be 4K aligned. This means Band start (Range start) and Band size (Range size) must be 4K aligned.
Implementation Features and Details Outside of TCG Specifications
The following features are outside of the TCG specifications. 1. Ports 2. Firmware signing
The following implementation details are outside of the TCG SSC specification. a. The SSC Specification states "The TPer SHALL implement the ParamCheck Longitudinal Redundancy Check (LRC) for Get and Set method calls on a PIN value". If the LRC check is erroneously applied to a value other than a PIN we ignore it, therefore no error is generated. b. When handling a "TCG cmd followed by a R/W cmd", all reads and writes that follow a TCG command will be processed in the normal way. No special handling or error messages will be sent to the host. It is up to the host to understand the possible outcomes of TCG commands and r/w command ordering and plan accordingly. c. CRC checking is disabled in all cases, so the drive will return data to the host. If the user successfully authenticates, then unencrypted data is returned to the host. If the user is unable to authenticate, encrypted data is returned to the host. d. The TPer replies with SP_BUSY for requests beyond 1 session.
HGST Hard Disk Drive Specification 282

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. The TCG protocol does not allow for a user to choose or switch between AES algorithms, so it is up to the vendor to choose which AES algorithm is used in their implementation. The HGST TCG SSC implementation in firmware supports AES 256-XTS only.

`Level 0 Discovery' Vendor Specific Data

This section refers to section 10.2.14 of the TCG Storage Security Subsystem Class document (see the Specifications section of this document). This Vendor Specific section is documented below.

Byte
16 17 18 19 20 21 22 23-47

7
RSVD RSVD
0

6
MB_s MB_e
0

Bit

5

4

3

2

Version (set to 0)

Vendor Specific State Information

Reserved

0

0

Diag_s Dload_s

Reserved

0

0

Diag_s Dload_e

0

0

0

0

Reserved

1
Locking_s Locking_e
0

0
FDE_s FDE_e inFIPS

Table 288 Persistent Reserve In (5E)
FDE_s/FDE_e - Full disk encryption is Supported (equivalent to Media Encryption in Locking Feature Descriptor Enterprise SSC 10.2.14) / Full disk encryption is Enabled on one or more band.
Locking_s/Locking_e - LBA band locking is supported - locking object exists in the locking SP of the device (equivalent to Locking Enabled in Locking Feature Descriptor Enterprise SSC 10.2.14) / The locking object for a band has either ReadLocked or WriteLocked attribute set (equivalent to Locked in Locking Feature Descriptor Enterprise SSC 10.2.14).
Dload_s/Dload_e - support for Admin SP Firmware download port / Firmware download port via Admin SP is locked. Diag_s/Diag_e - Support for Admin SP vendor specific Diagnostic port / Diagnostics port via Admin SP is locked.
MB_s/MB_e - Multiple encrypting bands supported / multiple encrypting bands enabled. This bit shall be set to 1 if more than one band exists in addition to the global band and is defined with at least one LBA.
inFIPS ­ This bit is set when FIPS mode has been configured.

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.

HGST Hard Disk Drive Specification 283

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. DRBG state is kept private to ensure that the keys that are generated by the device are unpredictable. The entropy source of the DRBG is servo subsystem noise. It has been verified to NIST SP800-90B.
Key Wrap
The NIST SP800-38F key wrap algorithm is used to encrypt a key with another key (KEK= Key Encryption Key). For any band i, the KEK_i is derived from PIN_i and salt_i using the NIST 800-132 algorithm. The KEK_i is then used to wrap a band's encryption key.
Key Erasure
Cryptographic erase procedure  Erase and overwrite wrapped key material with 0x00.  Erase and store the new wrapped key material.
HGST Hard Disk Drive Specification 284

TCG SSC Tables

Two copies of all TCG SSC 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. If both copies of the tables become corrupted during operation, the tables will be reinitialized to default values automatically, and this will result in a key mismatch error when a read is attempted.
The default values in the TCG tables created at the time of manufacturing are per the TCG SSC specification. The following tables contain VU (Vendor Unique) entries, which are set at the time of manufacturing.
 `Admin SP' C_PIN table  `Locking SP' C_PIN table  K_AES_256 table  `Locking SP' Locking Access Control table  `Locking Info' Table  `Locking SP' Locking Table
The VU entries for these tables are specified below. In addition, explanation of default values is given for non-VU entries that require it.
`Admin SP' C_PIN and `Locking SP' C_PIN Tables

Per TCG SSC specification, the PIN is set to the MSID at manufacturing time. HGST has specified the MSID to be the serial number of the drive concatenated 4x. Try Limit is set to 0, meaning that there is no limit. Tries is set 0, meaning that there have been no fail attempts. Persistence is set to 0, meaning the "Tries" value does not persist through power cycles (The "Tries" value is reset to 0 after successful attempt or a power cycle).

PIN SID MSID
PSID

Try Limit 0 0 0

Tries 0 0 0

Persistence 0 0 0

Table 289 HGST Default Values for `Admin SP' C_PIN & `Locking SP' C_PIN

K_AES_256 Table

The K_AES_256 table has 6 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.

UID (8 byte hex) 00 00 08 06 00 00 00 01 00 00 08 06 00 00 00 02
.. 00 00 08 06 00 00 00 06

MODE 23 23 .. 23

Table 290 HGST Implementation of K_AES_256 Table
The mode is specified in the TCG Enterprise SSC as a "Vendor Unique" (VU) entry. HGST initializes it in manufacturing to mode=23 (media encryption mode, per TCG specification) for all 6 entries.

HGST Hard Disk Drive Specification 285

`Locking SP' Access Control Table

The TCG Enterprise SSC defines the values for Row Number and UID as "Vendor Unique" (VU). HGST has defined them to be the row number in the table, with a range of 0-459. The range is calculated using the following formula:
number_of_rows = (#Supported Bands * 7) +12, where
 #Supported Bands = 6 (The implementation supports 6 bands)  The number 7 comes from the fact that each band has 7 UID/method combinations  The number 12 comes from the following 12 methods that must be included in the table.
1. ThisSP / Authenticate 2. Authority Table/Next 3. Anybody Authority Object/ Get 4. Band Masters Authority Object/ Get 5. Erase Master Auth. Object / Get 6. C_PIN table / Next 7. Erase Master C_PIN Object/ Set 8. Locking Info Table / Get 9. Locking Table / Next 10. DataStore / Get 11. DataStore / Set 12. ThisSP / Random

Row Number

UID

0

0

1

1

...

...

53

53

Table 291 HGST Implementation of `Locking SP' Access Control Table

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

NAME Version

0

0

Encrypt Support
23

Max Ranges 6

Max ReEncryptions
0

Table 292 HGST Implementation of `Locking Info' Table

Keys Available Cfg
0

`Locking SP' Locking Table

The "Vendor Unique" (VU) values for this table are shown below.

Next Key

ReEncrypt State

ReEncrypt Request

Adv Key Mode

Verf

Mode

Cont On Reset

Last ReEncrypt LBA

00 00 00 00

00 00 00 00h

0

0

0

0

0

0

-

-

-

-

-

-

-

00 00 00 00

00 00 00 05h

0

0

0

0

0

0

Last Re Enc Stat
0 -
0

General Status
0 -
0

Table 293 HGST Implementation of `Locking SP' Locking Table
In the ActiveKey column, the Enterprise SSC allows for byte 3 to be defined as either 05 or 06. The HGST implementation uses 06.

HGST Hard Disk Drive Specification 286

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.
Signature verification uses the RSA-PSS (Probabilistic Signature Scheme) signature verification algorithm with EMSA-SHA256 as padding function. The firmware was designed and implemented with the intention of meeting the signing requirements under FIPS 140-2.
All HGST firmware packages will be signed, but only encryption enabled drives will verify the signature. If the signature cannot be successfully verified on encryption drives, the firmware cannot be downloaded onto the HGST encryption drives. Failures to authenticate the firmware image will result in Check Condition with KCQ 5/26/9a (FRU 0). The act of issuing a firmware download to the drive will result in an implicit close of all open sessions at the security layer.

Revert Feature
HGST has extended TCG Enterprise to include the TCG Opal Revert method. Revert enables the customer, as needed by organizational policy, to overwrite existing TCG settings to the default values that were written during manufacturing.
Revert introduces a new TCG authority, PSID, to the Admin SP. During manufacturing, the PSID is hashed, and the digest is stored in a reserved area inside the drive. Also during manufacturing, the PSID is printed, in plaintext, on the drive's physical, external label. The PSID PIN cannot be accessed via the drive's interface, and it cannot be changed.
Below is the procedure to execute Revert:  Start Session on the Admin SP  Authenticate to the PSID authority  Execute the Revert Method  Successful completion of Revert automatically ends the TCG session
Notes for Revert include:  Revert execution that encounters an error does not close the TCG session  Reset of the drive during Revert will cause the subsequent power up sequence to be extended while Revert finishes its work

UID

Name Common Name

IsClass Class Enabled Operation Credential

00 00 00 09 00 01 FF 01

PSID

PhysicalDriveOwner F

Null T

Password C_PIN_PSID

Table 294 PSID Authority Added to `Admin SP' Authority Table

UID

Name

Common Name

PIN CharSet TryLimit Tries Persistence

00 00 00 09 00 01 FF 01

C_PIN_PSID PhysicalDriveOwner VU

Null

0

0

FALSE

Table 295 PSID Addition to `Admin SP' C_PIN table

HGST Hard Disk Drive Specification 287

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 C_PIN_PSID 00 00 00 0B 00 01 FF 01

MethodID
Revert 00 00 00 06 00 00 02 02 Get 00 00 00 06 00 00 00 06 Set 00 00 00 06 00 00 00 07 Get 00 00 00 06 00 00 00 06

ACL
ACE_SP_SID_ACE_SP_PSID 00 00 00 08 00 01 00 E0 Anybody 00 00 00 08 00 00 00 01 ACE_Makers_Set_Enabled 00 00 00 08 0003 00 01 ACE_C_PIN_Get_PSID_NoPIN_UID 00 00 00 80 00 01 00 E1

Table 296 Additions to `Admin SP' Access Control Table

New ACE table entries related to Revert are illustrated in Table 294.

GetACLACL
ACE_Anybody 00 00 00 08 00 00 00 01 Anybody 00 00 00 08 00 00 00 01 Anybody 00 00 00 08 00 00 00 01 Anybody 00 00 00 08 00 00 00 01

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 exception of having to authenticate, is anyone can use the Get Firmware Download Port Values command without authenticating. The functionality and definition of these ports is shown below in a table.
The feature does make use of the TCG structures and tables. An additional table, the ports table, has been implemented, and additional entries were made to the Admin SP ACE table and the Admin SP AccessControl Table. The ports table and the modified TCG SSC tables are shown below

Port Name Firmware Download
Diagnostics

Description This port has 2 valid states: locked and unlocked. On encryption drives, the download port is unlocked initially, Lock On Reset is "Null". Code can be downloaded onto the drive after the signature is successfully verified. If the signature cannot be verified successfully, no firmware can be downloaded to the drive. The user can change the state of the firmware download port only after authentication. On non-encryption drives, this port will be set to unlocked at the factory, and the state cannot be changed by the user. Firmware will be downloaded to the non-encryption drive through this port without verification of the signature.
This port has 2 valid states: locked and unlocked. This port allows HGST access to modify any TCG table or key. In order to open this port both the SID and the Maker authorities need to be authenticated. The purpose of this port is to aid HGST in debugging

Table 297 Ports Functionality

UID

Name

00 01 00 02 00 01 00 02 Firmware_Dload_Port

00 01 00 02 00 01 00 01

Diagnostic_Port

Table 298 Ports Table

LockOnReset Null
PowerCycle

PortLocked FALSE TRUE

HGST Hard Disk Drive Specification 288

UID
00 00 00 08 00 00 00 01 00 00 00 08 00 00 00 03 00 00 00 08 00 00 02 01 00 00 00 08 00 00 8C 03 00 00 00 08 00 00 8C 04 00 00 00 08 00 00 8C 05
00 00 00 08 00 00 8C 06
00 00 00 08 00 00 8C 07
00 00 00 08 00 00 8C 08 00 00 00 08 00 00 8C 09 00 00 00 80 00 01 00 E1 00 00 00 08 00 01 00 E0 00 00 00 09 00 01 FF 01

Name Anybody Makers SID SID_SetSelf MSID_Get SID_Set Makers
SID_Makers_SetDiag
SID_Makers_GetDiag
SID_SetPort SID_GetPort ACE_C_PIN_Get_PSID_ NoPIN ACE_SP_PSID ACE_Makers_Set_Enabled

Cmn Name

Boolean Expression

"" 00 00 00 09 00 00 00 01

`''' 00 00 00 09 00 00 00 03

"" 00 00 00 09 00 00 00 06

"" 00 00 00 09 00 00 00 06

"" 00 00 00 09 00 00 00 01

"" 00 00 00 09 00 00 00 06

00 00 00 09 00 00 00 06

""

And

00 00 00 09 00 00 00 03

00 00 00 09 00 00 00 06

""

And

00 00 00 09 00 00 00 03

"" 00 00 00 09 00 00 00 06

"" 00 00 00 09 00 00 00 06

"" 00 00 00 09 00 00 00 01

"" 00 00 00 09 00 01 FF 01

"" 00 00 00 09 00 00 00 06

Table 299 Modified `Admin SP' ACE Table

Row Start Null Null Null Null Null Null
Null
Null
Null Null Null Null Null

Row End Null Null Null Null Null Null

Column Start Column End

`''' `''' `''' "PIN" "PIN" "Enabled"

`''' `''' `''' "PIN" "PIN" "Enabled"

Null "PortLocked" "PortLocked"

Null "PortLocked" "PortLocked"

Null "PortLocked" "PortLocked"

Null "LockOnReset" "PortLocked"

Null

""

""

Null

""

""

Null

""

""

The last 3 lines of the table are additional entries required for Revert. The 2 lines of the table are the additional entries required to implement the firmware download port.

Row Number
VU VU
VU
VU
VU

UID

Invoking ID

Method ID Common Name

00 00 00 00

00 00 00 06

Anybody

VU

00 00 00 01

00 00 00 0C Authenticate

(This SP)

(Authenticate)

Admin SP

00 00 00 09

00 00 00 06

VU

00 00 00 00

00 00 00 08

(Authority table)

(Next)

Makers-NextAuthority table

00 00 00 09

VU

00 00 00 01 (Anybody Authority

object)

00 00 00 06 00 00 00 06
(Get)

Anybody-GetAnybody Authority
Object

VU

00 00 00 09 00 00 00 03 (Makers Authority
object)

00 00 00 06 00 00 00 06
(Get)

Anybody-GetAnybody Authority
Object

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

ACL
00 00 00 08 00 00 00 01 (Anybody) 00 00 00 08 00 00 00 03
(Makers)
00 00 00 08 00 00 00 01 (Anybody)
00 00 00 08 00 00 00 03
(Makers)
00 00 00 08 00 00 02 01
(SID)

Table 300 Modified `Admin SP' Access Control Table (part 1 of 2)

Log None None None

Add ACE ACL Null
Null
Null

Remove ACE ACL
Null
Null

Method ID
00 00 00 06 00 00 00 0C (Authenticate) 00 00 00 08 00 00 00 03
(Makers)

00 00 00 08

Null

00 00 00 01

(Anybody)

None

Null

00 00 00 08

Null

00 00 00 03

(Makers)

None

Null

00 00 00 08

Null

00 00 02 01

(SID)

HGST Hard Disk Drive Specification 289

Row Number

UID

Invoking ID

Method ID

Common Name

ACL

Log

Add ACE Remove ACL ACE ACL

Method ID

VU

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)

None

Null

VU

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-SetSID_C_ PIN object

00 00 00 08 00 00 8C 03 (SID_SetSelf)

None

Null

VU

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_PIN object

00 00 00 08 00 00 8C 04 (MSID_Get)

None

Null

00 00 00 09

00 00 00 03 00 00 00 06 SID_SetMakers- 00 00 00 08

VU VU

(Makers

00 00 00 07

Set-Makers

00 00 8C 05 None

Nul

Authority

(Set)

Authority Object (SID_SetMakers)

object)

00 00 00 00 00 00 00 06

00 00 00 08 00

VU VU 00 00 00 01 00 00 06 01 Anybody-Random 00 00 01

None

Nul

(ThisSP)

(Random)

(Anybody)

VU

VU

00 01 00 02 00 01 00 02

00 00 00 06 00 00 00 07

SID_Set_Dload

SID_SetPort

None

Nul

00 00 00 08

Null

00 00 00 02

(Makers)

00 00 00 08

Null

00 00 02 01

(SID)

00 00 00 08

Null

00 00 02 01

(SID)

00 00 00 08

Nul

00 00 02 01

(SID)

00 00 00 08

Nul

00 00 00 01

(Anybody)

00 00 00 08

Nul

00 00 02 01 (SID)

VU

VU

00 01 00 02 00 00 00 06 00 01 00 02 00 00 00 06

SID_GetDload

SID_GetPort None

Nul

00 00 00 08

Nul

00 00 02 01

(SID)

VU

VU

00 01 00 02 00 01 00 01

00 00 00 06 00 00 00 07

SID_Makers_ SetDiag

SID_Makers_Set Diag

None

Nul

00 00 00 08

Nul

00 00 02 01

(SID)

VU

VU

00 01 00 02 00 01 00 02

00 00 00 06 00 00 00 06

SID_Makers_ SetDiag

SID_Makers_Set Diag

None

Nul

00 00 00 08

Nul

00 00 02 01

(SID)

Table 301 Modified `Admin SP' Access Control Table (part 2 of 2)

The last 2 lines of the table are the additional entries required to implement the firmware download port.

HGST Hard Disk Drive Specification 290

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. HGST serial numbers are unique and are generated according to the following general rules:
 Maximum length of the serial number is 8 characters  Serial numbers do not contain the characters "I" or "O".
Logging
HGST logging functions will not record any sensitive data such as customer plain text data, passwords, encryption keys or wrapping keys.
Number of Sessions
The HGST implementation supports 1 active session at a time. In the case when a session is active and a new session is requested, the drive answers the host with SP_BUSY. This covers the following 2 scenarios.
 If an SP is in session and an attempt is made to start a second session with the same SP.  If an SP is in session and an attempt is made to start a second session with a different SP.
Number of Bands
The Enterprise SSC specification calls for support of up to 1024 bands. The HGST implementation supports a maximum of 6 bands. Bands must be 4K aligned. This means Band start (Range start) and Band size (Range size) must be 4K aligned.
Number of COMIDs
The HGST Enterprise SSC implementation supports 2 COMIDs, the minimum requirement in the Enterprise SSC specification. Only 1 COMID can be in use at any time.
HGST Hard Disk Drive Specification 291

Locked and Unlocked Behavior

T10 SCSI Commands

The table below describes how basic T10 SCSI commands behave on encryption drives in the locked and unlocked states.

Command FORMAT UNIT (04)
INQUIRY (12) LOG SELECT (4C) LOG SENSE (4D) MODE SELECT (15) MODE SELECT (55) MODE SENSE (1A) MODE SENSE (5A) PERSISTENT RESERVE IN (5E) PERSISTENT RESERVE IN (5F) PRE-FETCH (34) PRE-FETCH (90) READ (6) - (08) READ (10) - (28) READ (12) - (A8) READ (16) - (88) READ (32) - (7F/09) READ BUFFER (3C) READ CAPACITY (10) - (25) READ CAPACITY (16) (9E/10) READ DEFECT DATA (37) READ DEFECT DATA (B7) READ LONG (3E) READ LONG (9E) REASSIGN BLOCKS (07) RECEIVE DIAGNOSTICS RESULTS (1C) RELEASE (17) RELEASE (57) REPORT DEVICE IDENTIFIER (A3/05) REPORT LUNS (A0) REPORT SUPPORTED OPERATION CODES (A3/0C) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D) REQUEST SENSE (03) RESERVE (16) RESERVE (56) REZERO UNIT (01)

Unlocked OEM
OEM OEM OEM OEM OEM OEM OEM
OEM
OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM
OEM OEM OEM
OEM OEM
OEM
OEM OEM OEM OEM

Locked Command can't be executed when locked. Must unlock with MSID or password, before formatting. OEM OEM OEM-no access to customer data, will get some log information. OEM OEM OEM OEM
OEM
OEM MSID only - limits DRAM accessibility. This is a read function. MSID only - limits DRAM accessibility. This is a read function. Ent_A authorized only Ent_A authorized only Ent_A authorized only Ent_A authorized only Ent_A authorized only OEM. Sensitive data cannot be snap shorted from DRAM. OEM OEM OEM OEM Ent_A authorized only Ent_A authorized only Command access denied if the effective range is locked. OEM
OEM OEM OEM
OEM OEM
OEM
OEM OEM OEM OEM

Table 302 T10 SCSI Commands Behavior Table (part 1 of 2)

HGST Hard Disk Drive Specification 292

Command
SANITIZE (48)
SECURITY PROTOCOL IN (A2) SECURITY PROTOCOL OUT (B5) 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 BUFFER (3B) (T10)
WRITE BUFFER (3B) (For FW download)
WRITE LONG (10) - (3F) WRITE LONG (16) - (9F) WRITE SAME (10) - (41) WRITE SAME (16) - (93) WRITE SAME (32) - (7F/0D)

Unlocked
OEM
OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM OEM (write DRAM on to drive) FW is signed and downloaded OEM OEM OEM OEM OEM

Locked Command cannot be executed when any band is locked. All bands must be unlocked before executing SANITIZE command. Per TCG spec. Contains TCG payload. Per TCG spec. Contains TCG payload. Customer specific. OEM OEM OEM OEM OEM Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. Command access denied if the effective range is locked. OEM
OEM. The write buffer command only functions to write to the buffer.
Per TCG and T10 specification. Ent_A authorized only. Per TCG and T10 specification. Ent_A authorized only. Ent_A authorized only Ent_A authorized only Ent_A authorized only

Table 303 T10 SCSI Commands Behavior Table (part 2 of 2)

HGST Hard Disk Drive Specification 293

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 Enterprise requires the implementation of the Base, Admin, Locking, and Crypto Templates.

Command Session
Management
Properties Start Session Syc Session Close Session

Description There are two types of sessions: 1) Read-Only session 2) Read-Write session. The SSC requires us to support Read-Write sessions. ReadOnly session is not allowed. A session is always initiated by the host. See the "Write" parameter in the Start Session method description @ TCG Core 5.2.3.1, and see SSC requirement in SSC 6.2.1.2.
Returns session properties to host. Start a session
Response to say session successfully started. End (Close) a session

Table 304 TCG Enterprise SSC Commands Behavior -1

unlocked
N/A N/A N/A N/A

Locked
N/A N/A N/A N/A

Command Discovery
Level 0 Level 1
Level 2

Description
Allows the host to discover a TCG drive, its properties, and table values. Discovery request sent by host as IF-RCV command. Security Protocol = 0x01, COMID=0x0001 Request basic TPER capabilities via properties using host messaging.
TCG methods retrieve table cell values.

Table 305 TCG Enterprise SSC Commands Behavior -2

unlocked

Locked

N/A

N/A

Uses properties
method. See methods
below.

Uses properties method.
See methods below.

Command

Description

unlocked

Cryptographic Template Random

This is the only required method in the crypto template for SSC. It is a random
number generator in software.

N/A - Not related to bands/data on drive. Authentication required.

Locked
N/A - Not related to bands/data on drive. Authentication required.

Table 306 TCG Enterprise SSC Commands Behavior -3

HGST Hard Disk Drive Specification 294

Command

Description

Base Template Mandatory

Set

Sets a value in a table

unlocked

Locked

N/A - table operations. N/A - table operations.

Not related to

Not related to

bands/data on drive. bands/data on drive.

Get

Gets (reads) a value in a table

N/A - table operations. N/A - table operations.

Not related to

Not related to

bands/data on drive. bands/data on drive.

ParamCheck LRC Next
Authenticate GatACL

TPer implements param check LRC

N/A

N/A

(longitudinal Redundancy Check) on get/set

method calls on PIN value

Iterates over all the rows of a table. Method N/A - table operations. N/A ­ table operations.

requires user to specify "where" (row in table) Not related to

Not related to

and a "count". If where not specified, 1st row bands/data on drive. bands/data on drive.

in table is used. For count not specified,

default is number of last row in table. Returns

0 or more row number/uidref pairs currently in

use in table, per parameters specified.

Authenticate an authority within a session

Must be authorized. Must be authorized.

(session must have successfully begun).

Returns contents of access controls

N/A - table operations. N/A ­ table operations.

association's ACL stored in Method Table.

Not to do with

Not related to

The result is a list of UIDREFS to ACE objects. bands/data on drive. bands/data on drive.

Table 307 TCG Enterprise SSC Commands Behavior -4

Command
Locking Template
Erase

Mandatory

Description

Cryptographically erases user data in a specified LBA range and resets the access control (locking) of that LBA range

Table 308 TCG Enterprise SSC Commands Behavior -5

unlocked
Can erase if authorized.

Locked Generates error.

HGST Hard Disk Drive Specification 295

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.
Customer Specific Requirements
This specification does not cover customer-specific requirements. Customer-specific requirements are submitted by the customer to HGST in the form of a customer-specification document.
HGST Hard Disk Drive Specification 296

FIPS140 Cryptographic Officer Instructions
These instructions, to the Cryptographic Officer of FIPS140 models, are of paramount importance for the correct deployment and operation of the drive. The Cryptographic Officer is a trusted operator in the delivery and operation of the drive. Cryptographic Officers shall faithfully execute these instructions or intended security policies can fail.
The Security Policy may be downloaded from the NIST/CMVP website. The FIPS140 model numbers, firmware versions and hardware versions are also posted there:
( http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm )

Physical Security

Verify that the drive has not been tampered with by inspecting the tamper evidence labels as described in the Security Policy.
Security Protocol Parameters

Security Protocol Information Description

Overview

The security protocol information security protocol (i.e., the SECURITY PROTOCOL field set to 00h in a SECURITY PROTOCOL IN command) returns security protocol related information. A SECURITY PROTOCOL IN command in which the SECURITY PROTOCOL field is set to 00h is not associated with a previous SECURITY PROTOCOL OUT command and shall be processed without regard for whether a SECURITY PROTOCOL OUT command has been processed.
If the SECURITY PROTOCOL IN command is supported, the SECURITY PROTOCOL field set to 00h shall be supported as defined in this standard.
CDB Description

If the SECURITY PROTOCOL field is set to 00h in a SECURITY PROTOCOL IN command, the contents of the SECURITY PROTOCOL SPECIFIC field are defined in the table.

Type M M O

Code 0000h 0001h 0002h

Description Supported security protocol list Certificate data Security compliance information

Table 309 SECURITY PROTOCOL SPECIFIC Field for SECURITY PROTOCOL IN Protocol 00h

All other CDB fields for SECURITY PROTOCOL IN command shall meet the requirements stated in 8.42 SECURITY PROTOCOL IN (A2).
Each time a SECURITY PROTOCOL IN command with the SECURITY PROTOCOL field set to 00h is received, the device server shall transfer the data defined in 11.17.2.1 Security Protocol Information Description starting with byte 0.

HGST Hard Disk Drive Specification 297

Supported Security Protocols List Description

If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0000h in a SECURITY PROTOCOL IN command, then the parameter data shall have the format shown in the table.

Byte
0-5 6-7

Bit

7

6

5

4

3

2

1

0

Reserved

SUPPORTED SECURITY PROTOCOL LIST LENGTH (m-7)

8 ... m m+1 ... N

Supported security protocol list SUPPORTED SECURITY PROTOCOL (00h) [first]
... SUPPORTED SECURITY PROTOCOL [last]
Pad bytes (if any)

Table 310 Supported Security Protocols SECURITY PROTOCOL IN Parameter Data

 The SUPPORTED SECURITY PROTOCOL LIST LENGTH field indicates the total length, in bytes, of the supported security protocol list that follows.
 Each SUPPORTED SECURITY PROTOCOL field in the supported security protocols list shall contain one of the security protocol values (see Table 230 SECURITY PROTOCOL IN (A2) and Table 232 SECURITY PROTOCOL OUT (B5)) supported by the logical unit. The values shall be listed in ascending order starting with 00h.
 Pad bytes may be appended so the total data length conforms to the ALLOCATION LENGTH field requirements (see 8.42 SECURITY PROTOCOL IN (A2)). Pad bytes shall have a value of 00h.

Certificate Data Description

Certificate Overview

If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0001h in a SECURITY PROTOCOL IN command, then the parameter data shall have the format shown:

Bit

Byte

7

6

5

4

3

2

1

0

0 - 1

Reserved

2 - 3

CERTIFICATE LENGTH (m-3)

4 - m

CERTIFICATE

m+1

Pad bytes (if any)

Table 311 Certificate Data SECURITY PROTOCOL IN Parameter Data
 CERTIFICATE LENGTH field indicates the total length, in bytes, of the certificate or certificates that follow. The length may include more than one certificate. If the device server doesn't have a certificate to transfer, the CERTIFICATE LENGTH field shall be set to 0000h.
 CERTIFICATE is either an X.509 Public Key Certificate (see 11.17.2.1.4.2) or an X.509 Attribute Certificate (see 11.17.2.1.4.3) depending on the capabilities of the logical unit.
 Pad bytes may be appended so the total data length conforms to the ALLOCATION LENGTH field requirements (see Table 230 SECURITY PROTOCOL IN (A2)). Pad bytes shall have a value of 00h.

HGST Hard Disk Drive Specification 298

Public Key Certificate Description

RFC 5280 defines the certificate syntax for certificates consistent with X.509v3 Public Key Certificate Specification.

Attribute Certificate Description

RFC 3281 defines the certificate syntax for certificates consistent with X.509v2 Attribute Certificate Specification.

Security Compliance Information Description

Security Compliance Information Overview

The security compliance information parameter data contains information about security standards that apply to this SCSI target device.
If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0002h in a SECURITY PROTOCOL IN command, then the parameter data shall have the format shown:

Byte 0 - 3

Bit

7

6

5

4

3

2

1

0

SECURITY COMPLIANCE INFORMATION LENGTH (m-3)

4 ... n m+1 ... N

Compliance descriptors Compliance descriptor [first] ... Compliance descriptor [last]
Pad bytes (if any)

Table 312 Security Compliance Information SECURITY PROTOCOL IN Parameter Data
 The SECURITY COMPLIANCE INFORMATION LENGTH field indicates the total length, in bytes, of the compliance descriptors that follow.
 Each Compliance descriptor (see 11.17.2.1.5.2) contains information about a security standard that applies to this SCSI target device. Compliance descriptors may be returned in any order.
 Pad bytes may be appended so the total data length conforms to the ALLOCATION LENGTH field requirements (see Table 230 SECURITY PROTOCOL IN (A2)). Pad bytes shall have a value of 00h.

HGST Hard Disk Drive Specification 299

Compliance Descriptor Overview

The format of a compliance descriptor in the security compliance information SECURITY PROTOCOL IN parameter data is shown in table.

Bit

Byte

7

6

5

4

3

2

1

0

0 - 1

COMPLIANCE DESCRIPTOR TYPE

2 - 3

Reserved

4 - 7

COMPLIANCE DESCRIPTOR LENGTH (n-3)

8 - n

Descriptor specific information

Table 313 Compliance Descriptor Format
 The COMPLIANCE DESCRIPTOR TYPE field indicates the format of the descriptor specific information. The security compliance information SECURITY PROTOCOL IN parameter data may contain more than one compliance descriptor with the same value in the COMPLIANCE DESCRIPTOR TYPE field.

Code

Description

0001h

Security requirements for cryptographic modules

All others Reserved

Related Standards
FIPS 140-2 FIPS 140-3

Reference 11.17.2.1.5.3

Table 314 COMPLIANCE DESCRIPTOR TYPE Field
 The COMPLIANCE DESCRIPTOR LENGTH field indicates the number of bytes that follow in the compliance descriptor.
 The contents of the Descriptor specific information depend on the value in the COMPLIANCE DESCRIPTOR TYPE field.

HGST Hard Disk Drive Specification 300

FIPS 140 Compliance Descriptor

The FIPS 140 compliance descriptor contains information that may be used to locate information about a FIPS 140 certificate associated with the SCSI target device. The SCSI target device may or may not be operating in the mode specified by that certificate.

Bit

Byte

7

6

5

4

3

2

1

0

0-1

COMPLIANCE DESCRIPTOR TYPE (0001h)

2-3

Reserved

4-7

COMPLIANCE DESCRIPTOR LENGTH (0000 0208h)

8

RELATED STANDARD

9

OVERALL SECURITY LEVEL

10-15

Reserved

16-143

COMPLIANCE DESCRIPTOR HARDWARE VERSION

144-271

COMPLIANCE DESCRIPTOR VERSION

272-527

COMPLIANCE DESCRIPTOR MODULE NAME

Table 315 FIPS 140 Compliance Descriptor
 The COMPLIANCE DESCRIPTOR TYPE field and COMPLIANCE DESCRIPTOR LENGTH field are defined in 11.17.2.1.5.2 and shall be set as shown in Table 315 for the FIPS 140 compliance descriptor.
 The RELATED STANDARD field (see Table 317) is an ASCII data field that indicates the related standard described by this compliance descriptor.

Code 32h 33h All others

Related Standards FIPS 140-2 FIPS 140-3 Reserved

Table 316 RELATED STANDARD Field
 The OVERALL SECURITY LEVEL field is an ASCII data field that indicates the FIPS 140 overall security level that is reported by NIST or CSEC.
 The COMPLIANCE DESCRIPTOR HARDWARE VERSION field is null terminated, null padded data that indicates the version number of the firmware or software in the module, as reported by NIST or CSEC. The value in the COMPLIANCE DESCRIPTOR VERSION field is not related to the PRODUCT REVISION LEVEL field of standard INQUIRY data.
The COMPLIANCE DESCRIPTOR MODULE NAME field is null terminated, null padded data that indicates the name or identifier of the cryptographic module, as reported by NIST or CSEC.

HGST Hard Disk Drive Specification 301

Certified Models, Hardware Versions and Firmware Versions
Use the INQUIRY command to read the model number and the firmware version from the device. Verify that these have been certified by comparing against the values published in the Security Policy or on the CMVP website Module Validation Lists:
Cryptographic Module Acceptance and Provisioning
Initialize cryptographic services by executing the following TCG methods: 1. StartSession and SyncSession using the 'AdminSP'. 2. Get 'MSID'. 3. Authenticate 'SID with MSID'; FAILURE indicates the Cryptographic Module has been tampered. 4. Set 'SID PIN' to your organizational value. 5. Set 'Makers.Enabled = FALSE' (required to enter FIPS mode). 6. Set `Firmware_Dload_Port.PortLocked = TRUE' 7. Set `Firmware_Dload_Port.LocOnReset = PowerCycle' 8. EndSession. 9. StartSession and SyncSession on the 'LockingSP'. 10. Authenticate 'EraseMaster with MSID'; FAILURE indicates the Cryptographic Module has been tampered. 11. Set 'EraseMaster PIN' to a new value. 12. Authenticate 'BandMaster0 with MSID'; FAILURE indicates the Cryptographic Module has been tampered. 13. Set 'BandMaster0 PIN' to a new value. 14. Repeat Steps [12-13] for each Band supported by the SED 15. EndSession. 16. Reset the SED to clear the authentication values established during initialization.
Zeroization of the Cryptographic Module
The TCG Revert method overwrites all security parameters to factory defaults, 1. StartSession and SyncSession on 'AdminSP'. 2. Authenticate 'PSID'. 3. Execute the TCG Revert method. 4. EndSession.
Reset the drive and clear the authentication values established during zeroization.
HGST Hard Disk Drive Specification 302

SCSI Sense Data

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
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 8.10.9 "Mode Page 0A"). The REQUEST SENSE command may be used to request either the fixed format sense data or the descriptor format sense data (See section 8.36 "REPORT TIMESTAMP (A3/0F)").

Sense Data Length

Length of the sense data returned as part of CHECK_CONDITION status is determined by the sense data format: a) Length of fixed format sense data is always 32 byte. b) Length of descriptor format sense data is 60 byte (Generic Configuration) For REQUEST SENSE command, length of the sense data is the number of bytes in the command's Allocation Length or the sense data length described above, whichever is less.

Sense Data Response Code

The first byte of all sense data contains the RESPONSE CODE field that indicates the error type and format of the sense data. Table 317 "Sense data response codes." shows the RESPONSE CODE values which may be returned by the drive

Response Code 70h 71h 72h 73h

Error Type Current Deferred Current Deferred

Sense Data Format Fixed Fixed
Descriptor Descriptor

Table 317 Sense data response codes

Current Error: This indicates an error for the current command.

Deferred Error:

This indicates that the error is for a previous command that has already returned a good status. Such commands are associated with the immediate bit or write caching. Format unit (04h) command is an example of a command that may return a deferred error.

HGST Hard Disk Drive Specification 303

Fixed Format Sense Data

Table 318 following table shows the format of fixed format of the sense data returned by the drive.

Bit

Byte

7

6

5

4

3

2

1

0

0

Valid

Response Code (70h or 71h)

1

RSVD = 0

2

0

ILI

0

Sense Key

(MSB) 3-6

Information Bytes

(LSB)

7

Additional Sense Length

8-11

(MSB)

Command Specific Information

(LSB)

12

Additional Sense Code

13

Additional Sense Code Qualifier

14

15

SKSV

FRU = 0 Sense-Key Specific Bits

16-17

Sense-Key Specific Bytes

18-19

Reserved = 0

20-23

Vendor unique Error information

24-29

Command Specific Information

30-31

Reserved = 0

Table 318 Fixed Format Sense Data

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.

Response Code (Bit 6 - 0 of byte 0)
70h Current Error. See section 12.1.3 "Sense Data Response Code" for more details. 71h Deferred Error. See section 12.1.3 "Sense Data Response Code" for more details.

HGST Hard Disk Drive Specification 304

ILI: Incorrect Length Indicator (Bit 5 of byte 2)

The ILI bit is valid for the Read Long (3Eh) command and Write Long (3Fh) command only. ILI set to one and Valid Bit set to one indicates that the requested logical block length does not match the logical block length of the data on the medium for a Read Long or Write Long command. The Information field contains residue information about the error. ILI set to zero indicates there is no incorrect length condition.
0 No Incorrect Length condition.
1 Incorrect Length Indicated.

Valid
x 1

ILI

Command = Read Long or Write Long

Description

0

x

No incorrect length condition

1

yes

Requested Logical block Length does not match the logical block

length of the data on the disk

Table 319 Incorrect Length Indicator

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. More detailed information is available in the Additional Sense Code and Additional Sense Code Qualifier.
Not Ready The logical unit addressed cannot be addressed. More detailed information is available in the Additional Sense Code and Additional Sense Code Qualifier.
Medium Error The command terminated with an unrecoverable error condition caused by a flaw in the media or an error in the recorded data. More detailed information is contained in the Additional Sense Code and Additional Sense Code Qualifier.
Hardware Error The drive detected an unrecoverable hardware error while performing a command or during a diagnostic test. More detailed information is contained in the Additional Sense Code and Additional Sense Code Qualifier.
Illegal Request There was an illegal parameter in the command descriptor block or additional parameter supplied as data. If an invalid parameter is found in the CDB, then the command is terminated without altering the medium. If an invalid parameter is found in parameters supplied as data, then the drive might have altered the medium.
Unit Attention Indicates that the drive entered in the 'Unit Attention Condition'. (See Section 10.1.5 "Unit Attention Condition") Data Protect Not used Vendor Specific Not used Aborted command The drive aborted the command. Not Implemented Miscompare Reserved

HGST Hard Disk Drive Specification 305

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. an LBA greater than 2TB) the VALID bit will always be set to 0. To retrieve such information in such cases, the drive must be configured to return sense data in descriptor format. See section 8.10.9 "Mode Page 0A" for details
- ILI = 1: This field contains the difference (residue) of the requested length in bytes. Negative values are indicated by two's complement notation.

Valid 0 1 1

ILI Description x 0x00000000 - (not used/invalid) 0 LBA 1 Residue of the requested length in bytes

Table 320 Information Bytes (Byte 3 through 6)

Additional Sense Length (Byte 7)

Indicates the remaining number of bytes in the sense data. (It is always set to 18h.)

Command Specific Information (Byte 8 through 11)

This field is unused and will be set to zero.

HGST Hard Disk Drive Specification 306

Additional Sense Code/Qualifier (Byte 12 and 13)
The following table shows the description of the combination of Sense Key / Sense Code / Qualifier.
Table 321 Sense Code/Qualifier
Valid Sense Key, Code , Qualifier Combinations Used by the Drive Key Code Qual Description
Sense Key = No Sense 00 00 00 No Additional Sense Information
0000 No Error Sense Key = No Sense
0 0B 01 SMART Temperature Warning 1A02 SMART: Temperature Warning (No Sense) 2A02 SMART: Temperature Warning (Recovered Sense) 3A02 SMART: Temperature Warning (Unit Attention)
0 0B 03 SMART Background Self-Test Failure 1A03 SMART: Background Self-Test Failure (No Sense) 2A03 SMART: Background Self-Test Failure (Recovered Sense) 3A03 SMART: Background Self-Test Failure (Unit Attention)
0 0B 04 SMART Background Pre-Scan Failure 1A04 SMART: Background Pre-Scan Failure (No Sense) 2A04 SMART: Background Pre-Scan Failure (Recovered Sense) 3A04 SMART: Background Pre-Scan Failure (Unit Attention)
0 0B 05 Background Media Scan Failure Warning 1A05 SMART: Background Media Scan Failure (No Sense) 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 Attention)
0 5D 50 Load/Unload cycle Count Warning 1A50 SMART: Load/Unload Cycle Count Warning (No Sense) 2A50 SMART: Load/Unload Cycle Count Warning (Recovered Sense) 3A50 SMART: Load/Unload Cycle Count Warning (Unit Attention)
0 5D 5B Spinup Retry Count Warning 1A5B SMART: Spinup Retry Count Warning (No Sense) 2A5B SMART: Spinup Retry Count Warning (Recovered Sense) 3A5B SMART: Spinup Retry Count Warning (Unit Attention)
0 5D 62 Read/Write Error Rate Warning 1A32 SMART: Read Error Rate Warning (No Sense) 2A32 SMART: Read Error Rate Warning (Recovered Sense) 3A32 SMART: Read Error Rate Warning (Unit Attention) 1A4A SMART: Write Error Rate Warning (No Sense) 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)
HGST Hard Disk Drive Specification 307

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 (Unit Attention)
0 5D 66 Spinup Time Warning 1A56 SMART: Spinup Time Warning (No Sense) 2A56 SMART: Spinup Time Warning (Recovered Sense) 3A56 SMART: Spinup Time Warning (Unit Attention)
0 5D FD Internal Environment Status Error 1AFD SMART: Internal Environment Status Error(No Sense) 2AFD SMART: Internal Environment Status Error(Recovered Sense) 3AFD SMART: Internal Environment Status Error(Unit Attention)
0 5D FF Test Warning Threshold Reached 1AFF SMART: Test Warning Threshold Reached (No Sense) 2AFF SMART: Test Warning Threshold Reached (Recovered Sense) 3AFF SMART: Test Warning Threshold Reached (Unit Attention)
0 5E 01 Idle_A Condition activated by timer 1831 CMD: Power Mode Idle_A By Timer
0 5E 02 Standby_Z Condition activated by timer 1834 CMD: Power Mode Standby_Z By Timer
0 5E 03 Idle_A Condition activated by Command 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 activated by timer 1839 CMD: Power Mode Standby_Y By Timer
0 5E 0A Standby_Y Condition activated by Command 183A CMD: Power Mode Standby_Y By Command Sense Key = Recovered Error
1 02 00 No Seek Complete 141B Servo: Recovered Current error 141D Servo: Recovered Seek timeout 141F Servo: Recovered Seek error 142B Servo: Recovered RRO Calibration timeout 14A0 Servo: Recovered IDLEA Grab Error 14A2 Servo: Recovered IDLEA Seek Error 14A4 Servo: Recovered AVEDAC Error 14A6 Servo: Recovered IDLEA Exit Timeout Error 14A8 Servo: Recovered IDLEA Long Seek Error 14AA Servo: Recovered IDLEA SID ACQ error
HGST Hard Disk Drive Specification 308

1 03 00 Peripheral Device Write Fault 1733 Media: Recovered Read Write Abort Error 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 Field Misread Error 1EDA Media: Recovered R/W Abort RRO Field Missing Error 1EDC Media: Recovered R/W Abort Idle Seek Error 1EDE Media: Recovered R/W Abort Seek Timeout Error 1EE0 Media: Recovered R/W Abort Estimator Error 1EE2 Media: Recovered R/W Abort Predictor Error 1EE4 Media: Recovered R/W Abort PES Error 1EE6 Media: Recovered R/W Abort Seek Start Error 1EE8 Media: Recovered R/W Abort PES Reset Error 1EEA Media: Recovered R/W Abort SID Unlock Error 1EEC Media: Recovered R/W Abort WCS Error 1EEE Media: Recovered R/W Abort Hard Reset Error 1EF0 Media: Recovered R/W Abort Shock Error 1EF2 Media: Recovered R/W Abort Unlock Macro Error 1EF4 Media: Recovered R/W Abort Sharp Error 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 - Recommend Reassignment 1704 Media: Recovered Write Error - Recommend reassign
1 10 01 Recovered Guard Check Error 17BC Media: Recovered Guard Check Error
1 10 02 Recovered Application Tag Error 17BA Media: Recovered Application Tag Error
1 10 03 Recovered Reference Tag Error 17B8 Media: Recovered Reference Tag Error
1 11 14 Recovered LBA Write Correctable Error 17CB Media: Recovered LBA Write Correctable Error
1 15 00 Random Positioning Error 1714 Media: Recovered Sector Overflow Error 173D Media: Recovered Sector Miss Error 1770 Media: Recovered SID Timeout Error 1778 Media: Recovered Mini Mode Timeout 177C Media: Recovered Servo Area Timeout 1780 Media: Recovered DLC SID Delay Timeout 17B2 Media: Recovered Abort Window Error 17EE Media: Recovered Sector Number Cylinder Error
HGST Hard Disk Drive Specification 309

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
1 16 02 Data Sync Error - Recommend Rewrite E70F Media: Recovered Data Address Mark Error - Recommend Rewrite
1 16 03 Data Sync Error - Auto Reallocated D710 Media: Recovered Data Address Mark Error - Reassigned
1 16 04 Data Sync Error - Recommend Reassignment E711 Media: Recovered Data Address Mark Error - Recommend Reassign
1 17 01 Recovered Data with Retries 1718 Media: Recovered Sync Mark Retry Timeout 171E Media: Recovered Read Latency Error 1726 Media: Recovered Internal Write Catch Error 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 OTF Correction - Recommend Reassign
1 17 08 Recovered Data Without LDPC - Recommend Rewrite E707 Media: Error With OTF Correction - Recommend Rewrite
1 17 09 Recovered Data Without LDPC - Data Rewritten E708 Media: Error With OTF Correction - Rewritten
1 18 00 Recovered Data With LDPC 1709 Media: Recovered Error With Offline Correction 17AE Media: Recovered ECC Correctable Error
1 18 01 Recovered Data - Forced Channel Fault 167E Channel: Recovered Forced Channel Fault Error
1 18 02 Recovered Data - Data Auto-Reallocated D70A Media: Error With Offline Correction - Reassigned
1 18 05 Recovered Data - Recommend Reassignment E70B Media: Error With Offline Correction - Recommend Reassign
1 18 06 Recovered Data With LDPC - Recommend Rewrite E70C Media: Error With Offline Correction - Recommend Rewrite
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: Recovered Defect List Format Not Supported Error
1 1C 01 Primary Defect List Not Found. Requested Format Not Supported 1747 Media: Recovered Primary Defect List Not Found Error
1 1C 02 Grown Defect List Not Found. Requested Format Not Supported 1748 Media: Recovered Grown Defect List Not Found Error
1 1F 00 Partial Defect List Transfer 1749 Media: Recovered Partial Defect List Transferred Error
HGST Hard Disk Drive Specification 310

1 44 00 Internal Target Failure F132 GEM FH track read error 1201 Sanity: Error In UEC Class 1202 Sanity: Error In UEC Cause 1301 Motor: Recovered internal error 1303 Motor: Recovered Open Loop Commutation failure 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 overtemp error 1325 Motor: Recovered 12V or 5V OK error 1327 Motor: Recovered unknown error 1365 Motor: Recovered Predriver Voltage Offset Calibration Error 1367 Motor: Recovered Predriver BEMF Gain Calibration Error 1369 Motor: Recovered Predriver BEMF Unload Calibration Error 136F Motor: Recovered IDCS Calibration Measurement 1 Error 1371 Motor: Recovered IDCS Calibration Measurement 2 Error 1373 Motor: Recovered IDCS Calibration Saturation Error 1375 Motor: Recovered IDCS Calibration Adjustment Error 1401 Servo: Recovered Requested rezero head does not exist 1403 Servo: Recovered Back EMF movement in progress 1405 Servo: Recovered Back EMF timeout error 1407 Servo: Recovered ADC conversion timeout 1409 Servo: Recovered Load/unload calibration error 140B Servo: Recovered Invalid 5 volts 140D Servo: Recovered Invalid 12 volts 140F Servo: Recovered Invalid harmonic requested 1411 Servo: Recovered Gain BEMF Calibration error 1413 Servo: Recovered VOFF BEMF calibration error 1415 Servo: Recovered Invalid temperature 1417 Servo: Recovered Truncated rezero 1419 Servo: Recovered Heads not loaded 1425 Servo: Recovered KT Seek out of range 1427 Servo: Recovered DAC Offset calibration error 1429 Servo: Recovered Load speed error 142D Servo: Recovered ADC Calibration error 142F Servo: Recovered ADC Offset error 1431 Servo: Recovered ADC Limit error 1433 Servo: Recovered Balancer Resistance error 1435 Servo: Recovered Balancer Resistance Limit error 1437 Servo: Recovered First Cylinder error 1439 Servo: Recovered Valid Cylinder error 143B Servo: Recovered ADC Saturation error 143D Servo: Recovered Latch Break timeout 143F Servo: Recovered MR Resistance out of range error 1441 Servo: Recovered VCM Retract error 1443 Servo: Recovered Load Retry error 1445 Servo: Recovered DFT Sharp error 1447 Servo: Recovered Load/Unload state error
HGST Hard Disk Drive Specification 311

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 SDM Failure 146F Servo: Recovered VCM Free Speed Error 1471 Servo: Recovered Emergency Brake Timeout Error 1473 Servo: Recovered Excessive Current Error 1475 Servo: Recovered Excessive Velocity Error 147D Servo: Recovered RROF SDM Timeout Error 147F Servo: Recovered RROF Over Limit Error 1482 Servo: Recovered Measure Asymmetry SDM Failure 1486 Servo: Recovered Milli-Calibration Error 148C Servo: Recovered Measure Qsamp SDM Failure 148E Servo: Recovered Tilt Calibration Error 1490 Servo: Recovered Tilt Numerical Error 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 14AC Servo: Recovered ODCS Detect error 14AE Servo: Recovered Unexpected Motion error 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 Error 161C AE: Recovered IC Over Temperature Error 161E AE: Recovered IP Clock Count Error 1620 AE: Recovered DLC SVCLK Error 1622 AE: Recovered Write Data BLS Error 1626 AE: Recovered Power Supply Error 1628 AE: Recovered Open Write Head Error 162A AE: Recovered Write Transition Error 162E Channel: Recovered Channel NRZ Clear Timeout Error 1630 AE: Recovered SPE Low In Write Fault 1636 AE: Recovered Short Write Head Error 163C AE: Recovered TFC Open Error 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
HGST Hard Disk Drive Specification 312

1658 Channel: Recovered No NRZ Clock Error 165A Channel: Recovered Calibration Block Fault Error 165E Channel: Recovered Gate Command Queue Overflow Error 1660 Channel: Recovered Ending Write Splice Fault Error 1662 Channel: Recovered Write Gate Overlap Fault Error 1664 Channel: Recovered Write Gate Fault Error 1666 Channel: Recovered Buffer Overflow Write Error 1668 Channel: Recovered Buffer Underflow Write Error 166A Channel: Recovered Write Parity Error 166C Channel: Recovered Buffer Overflow Read Error 166E Channel: Recovered CTG Wedge Slip Fault Error 1670 Channel: Recovered CTG Packet Late Fault Error 1672 Channel: Recovered Baseline Instability Count Late Error 1674 Channel: Recovered Preamp Count Fault Error 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: Recovered Massive Drop Out Detection Error 1692 Channel: Recovered CTG Parameter Out of Bounds Error 1694 Channel: Recovered Flaw Signal Sync Error 1696 Channel: Recovered ACQ Flag Error 1698 Channel: Recovered No Clock Error 169A Channel: Recovered PLL Losslock Error 169C Channel: Recovered ESNR Timeout Error 169E Channel: Recovered ADC Sample Not Ready Error 16A2 Channel: Recovered Auto RST NRZ-Clock Error 16A4 Channel: Recovered Write CRC Fault Error 16A6 Channel: Recovered Read Synthesizer Loss of Lock Error 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: Recovered MXP Write Fault 16C0 Channel: Recovered Data Jam Error 16C2 Channel: Recovered Code-Word Out Of Order Error 16C4 Channel: Recovered Read RLL Buffer CRC Flag Error 16C6 Channel: Recovered Write RLL Buffer CRC Flag Error 16C8 Channel: Recovered CTG No SAM Detected Fault Error 16CA Channel: Recovered ITI Adjust Preload Fault Track Error 16CC Channel: Recovered WTG SRV Fault Error 16CE Channel: Recovered CTG Engine Not Ready Fault Error
HGST Hard Disk Drive Specification 313

16D0 Channel: Recovered LLI Abort Fault Error 16D2 Channel: Recovered Retry Fault Error 16D4 Channel: Recovered WTG Timeout Fault Error 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 Synchronous Abort Done Error 16ED Channel: Recovered NRZ Clear Fault Error 16EF Channel: Recovered Collision Fault Error 16F1 Channel: Recovered Read Synthesizer Precharge Fail Fault Error 16F3 Channel: Recovered Servo Synthesizer Precharge Fail Fault Error 16F5 Channel: Recovered Read Synthesizer Loss of Lock Error 16F7 Channel: Recovered Fragment Number Fault Error 16F9 Channel: Recovered Preamble Quality Monitor Fault Error 1712 Media: Recovered LBA MEDC Error 1716 Media: Recovered Write Overrun Error 171C Media: Recovered DRAM CRC Error 1731 Media: Recovered Write Fault 1744 Media: Recovered Sudden Stop Error 1759 Media: Recovered Unknown Error 1766 Channel: Recovered XTS LOAD Timeout Error 176A Media: Recovered No NRZ Clock Error 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 Media: Recovered DRAM ECC LBA Error 17D4 Media: Recovered Parity PTR FIFO Error 17D6 Media: Recovered Parity LBA FIFO Error 17D8 Media: Recovered Parity Uncorrectable FIFO Error 17DA Media: Recovered Status Uncorrectable FIFO Error 17DC Media: Recovered Parity EDC SRAM Error 17DE Media: Recovered REQ/ACK Handshake Error 17E2 Media: Recovered Read Parity Error 17E4 Media: Recovered EPO Error 17E8 Media: Recovered AE Access Inhibit Error 17EA Media: Recovered PTR FIFO Error 17EC Media: Recovered LBA FIFO Error 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
HGST Hard Disk Drive Specification 314

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 132F Motor: Recovered Module Vcmn hi-side overtemp fault 1331 Motor: Recovered Invalid standby RPM request 1333 Motor: Recovered Invalid spin state request 1335 Motor: Recovered Hardware retract timeout 1337 Motor: Recovered thermal limit exceeded 1339 Motor: Recovered Predriver fault 133B Motor: Recovered Predriver Watchdog Fsys error 133D Motor: Recovered Predriver Watchdog DAC error 133F Motor: Recovered Predriver Speed Low error 1341 Motor: Recovered Predriver UV Vboost error 1343 Motor: Recovered Predriver NREG UV error 1345 Motor: Recovered Predriver Ext NPOR error 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.5 Volt Supply error 1355 Motor: Recovered Predriver Shock Detected error 1357 Motor: Recovered Predriver Over Temperature error 1359 Motor: Recovered Predriver Under Voltage 3.3 Volt Supply error 135B Motor: Recovered Predriver Under Voltage 5 and 12 Volt Supply error 135D Motor: Recovered Predriver Error in Enabling Power Saving Mode 135F Motor: Recovered Predriver Fault in Auto Retract 1361 Motor: Recovered Predriver Error in Utilizing External Power Supply 1363 Motor: Recovered Predriver Regulator Supply Fault 136B Motor: Recovered Predriver VCM Short Error 136D Motor: Recovered Predriver NREG disable error
1 44 F9 Vendor Unique - Internal Target Failure 144F Servo: Recovered SHARP Parity Error 1451 Servo: Recovered SHARP Parity Rate Error 1453 Servo: Recovered SHARP Decode Error 1455 Servo: Recovered SHARP Decode Rate Error 1457 Servo: Recovered SHARP Timeout Error 1459 Servo: Recovered SHARP Timeout Rate Error 145B Servo: Recovered SHARP Other Error 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 Interface: Logical unit becoming ready
HGST Hard Disk Drive Specification 315

2 04 02 Logical Unit Not Ready, initializing command required F124 Bring-up error F503 Host Interface: Logical unit not ready - initializing command required
2 04 03 Logical Unit Not Ready, Manual Intervention Required F572 Host Interface: LUN not ready; manual intervention required
2 04 04 Logical Unit Not Ready, Format In Progress F504 Host Interface: Not ready - format in progress
2 04 09 Not Ready - Self-test In Progress F505 Host Interface: Not ready - self-test in progress
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
2 31 00 Medium Format Corrupted - Reassign Failed F506 Host Interface: Reassign failed
2 31 01 Format Command Failed F507 Host Interface: Format failed Sense Key = Medium Error
3 03 00 Medium Error - Write Fault F734 Media: Unrecovered Read Write Abort Error F738 Media: Unrecovered Post Write Abort F73A Media: Unrecovered Post PES Check Write Abort Error F797 Media: SAT Write Abort F7E1 Media: Unrecovered Write Splice Error FECF Media: Unrecovered R/W Abort Due to Vibration Condition (Other) FED1 Media: Unrecovered R/W Abort Due to Vibration Condition (Estimator) FED3 Media: Unrecovered R/W Abort Due to Vibration Condition (Predictor) 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: Unrecovered R/W Abort Seek Start Error FEE9 Media: Unrecovered R/W Abort PES Reset Error FEEB Media: Unrecovered R/W Abort SID Unlock Error FEED Media: Unrecovered R/W Abort WCS Error FEEF Media: Unrecovered R/W Abort Hard Reset Error FEF1 Media: Unrecovered R/W Abort Shock Error FEF3 Media: Unrecovered R/W Abort Unlock Macro Error FEF5 Media: Unrecovered R/W Abort Sharp Error FEF7 Media: Unrecovered R/W Abort Aggressive Error FEF9 Media: Unrecovered R/W Abort SVGA Limit Error FEFB Media: Unrecovered R/W Abort Gray Code Error FEFD Media: Unrecovered R/W Abort Burst Error FEFF Media: Unrecovered R/W Abort No STM Error
HGST Hard Disk Drive Specification 316

3 11 00 Unrecovered Read Error F67F Channel: Unrecovered Forced Channel Fault Error F702 Too many notches F719 Media: Unrecovered Sync Mark Retry Timeout 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 targeted scan F73F Media: NFZ Table Full F740 Media: Defect SID Table Full Error F74A Media: Unrecovered Alternate Track Table Full Error F74D Media: Unrecovered Too Many Heads Error F74E Media: Unrecovered Skew Table Size Error F74F Media: Unrecovered Too Many Zones Error F750 Media: Unrecovered Too Many SIDs Error F751 Media: Unrecovered Alternate Track Table Full Error F752 Media: Unrecovered Drive Capacity Too Small F753 Media: Unrecovered G-list Full (Format command) F754 Media: Unrecovered G-list Full (2) (Format command) F755 Media: Unrecovered Pointer Repeat Size Error 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 Media: 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: Unrecovered NRZ Sector Marginal Error
3 11 14 Unrecovered LBA Error F7A8 Media: Unrecovered Committed Write Correction Disabled Error F7A9 Media: Unrecovered Committed Write Uncorrectable Error F7CA Media: Unrecovered LBA Correction Disabled Error F7CC Media: Unrecovered LBA Write Uncorrectable Error
3 15 00 Random Positioning Error F715 Media: Unrecovered Sector Overflow Error F73E Media: Unrecovered Sector Miss Error F771 Media: Unrecovered SID Timeout Error F779 Media: Unrecovered Mini Mode Timeout F77D Media: Unrecovered Servo Area Timeout F781 Media: Unrecovered DLC SID Delay Timeout F7B3 Media: Unrecovered Abort Window Error F7EF Media: Unrecovered Sector Number Cylinder Error
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
HGST Hard Disk Drive Specification 317

3 19 03 Defect List Error in Grown List F74C Media: Unrecovered Grown Defect List Error
3 31 00 Medium Format Corrupted Reassign Failed F701 Format corrupted 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 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: Drive Not Loaded - IM Format Failed FF1A IndSys: Drive Not Loaded - Metadata First Primary FF1B IndSys: Drive Loaded - Metadata First Primary and Secondary FF1C IndSys: Drive Loaded - IBA Out of Range FF1D IndSys: Drive Loaded - Context Load Failed FF1E IndSys: Drive Loaded - Context Sequence ID Mismatch FF1F IndSys: Drive Loaded - Replay EPO Spec Failed
3 31 01 Indirection System Failure FF12 IndSys: Drive Not Loaded - Layout Failed FF15 IndSys: Drive Not Loaded - Pseudo Write Failed FF16 IndSys: Drive Not Loaded - Full drop Failed FF17 IndSys: Drive Not Loaded - EPO Format Failed FF18 IndSys: Drive Not Loaded - Set IM Valid Failed FF19 IndSys: Drive Not Loaded - Bring Online failed FF20 IndSys: Drive Not Loaded - EPD Flash Entry Invalid FF21 LayoutMgr: All Flash Entries Erased FF22 IndSys: Drive Loaded - Replay Failed FF41 LayoutMgr: Format Capacity Not Met 1F42 DlMgr: DLMGR Generic Fail FF43 IndSys: Drive Not Loaded - Metadata ATI FF44 IndSys: Drive Loaded - Replay Fail 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 FF55 IndMgr: Generic Insert Exception Failed FF60 EpoMgr: Flash Read RS Syndrome Gen Timeout FF61 EpoMgr: Uncorrectable Flash RS ECC Error FF62 EpoMgr: Correctable EPO Timeout FF63 EpoMgr: ARM FPS Engine and Not Spinning
3 31 03 Sanitize Command failed F50C Host Interface: Sanitize Command failed
3 32 01 LOM Generic Failure - ShowStop 1F40 IndSys: LOM Generic Fail
HGST Hard Disk Drive Specification 318

3 40 00 Unrecovered SAT No Buffer Overflow Error F720 Media: RC Dump Overflow Error F721 Media: Format Configuration Invalid 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 Exceeded
3 81 00 Vendor Unique - Internal Logic Error F75B Media: Unrecovered Too Many Sectors Error Sense Key = Hardware Error
4 02 00 No Seek Complete F41C Servo: Unrecovered Current error F41E Servo: Unrecovered Seek timeout F420 Servo: Unrecovered Seek error F42C Servo: Unrecovered RRO Calibration timeout F4A1 Servo: Unrecovered IDLEA Grab Error F4A3 Servo: Unrecovered IDLEA Seek Error F4A5 Servo: Unrecovered AVEDAC Error F4A7 Servo: Unrecovered IDLEA Exit Timeout Error 14A9 Servo: Unrecovered IDLEA Long Seek Error F4AB Servo: Unrecovered IDLEA SID ACQ Error
4 09 00 Track Following Error F422 Servo: Unrecovered Track following error F424 Servo: Unrecovered Track follow timeout
4 31 00 Medium Format Corrupted - Reassign Failed F204 Reassign reserved area media error
4 32 00 No Defect Spare Location Available 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
HGST Hard Disk Drive Specification 319

4 40 80 Diagnostic Failure F101 BATS error: Reserved Area - Invalid request F102 BATS error: Reserved Area - Broken F103 BATS error: Reserved Area - Invalid version F104 BATS error: Reserved Area - Invalid checksum F105 BATS error: Reserved Area - Invalid eyecatcher F106 BATS error: Reserved Area - Invalid main header checksum F107 BATS error: Reserved Area - Invalid read length F108 BATS error: Reserved Area - Address boundary error 1109 BATS error: Reserved Area - Error reading first copy F10D BATS error: Reserved Area - Write fix hard error F111 BATS error: RAM code load error F112 BATS error: RAM code check F11D BATS error: Incorrect Disk Code 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 ATA Diagnostic Code: Formatter Error F144 ATA Diagnostic Code: Sector Buffer Error F147 ATA Diagnostic Code: Read/Write Test Error F148 BATS error: Still broken after clear 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
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
HGST Hard Disk Drive Specification 320

4 44 00 Internal Target Failure F203 Sanity: Sanity Check Failure F208 Mode Page Structure Mismatch F209 Miscompare of SBA in the P-List F20A Error Clearing Reset State F20B DSLT: Invalid number of splits F20C DSLT: Invalid relaxed format F20D DSLT: First Fragment too large F20E DSLT: Invalid end offset F20F DSLT: Cycle not complete F220 MFG: Consistency Check failed 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 timeout F314 Motor: Unrecovered Inductive Sense speed error F316 Motor: Unrecovered Spin Sense speed error F31A Motor: Unrecovered Target speed error F31C Motor: Unrecovered Power driver version error F31E Motor: Unrecovered Over current error F322 Motor: Unrecovered Negative regulator fault F324 Motor: Unrecovered Module overtemp error F326 Motor: Unrecovered 12V or 5V OK error F328 Motor: Unrecovered unknown error F366 Motor: Unrecovered Predriver Voltage Offset Calibration Error F368 Motor: Unrecovered Predriver BEMF Gain Calibration Error F36A Motor: Unrecovered Predriver BEMF Unload Calibration Error F370 Motor: Unrecovered IDCS Calibration Measurement 1 Error F372 Motor: Unrecovered IDCS Calibration Measurement 2 Error F374 Motor: Unrecovered IDCS Calibration Saturation Error F376 Motor: Unrecovered IDCS Calibration Adjustment 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 requested F412 Servo: Unrecovered Gain BEMF Calibration error F414 Servo: Unrecovered VOFF BEMF calibration error F416 Servo: Unrecovered Invalid temperature F418 Servo: Unrecovered Truncated rezero F41A Servo: Unrecovered Heads not loaded F426 Servo: Unrecovered KT Seek out of range F428 Servo: Unrecovered DAC Offset calibration error F42A Servo: Unrecovered Load speed error F42E Servo: Unrecovered ADC Calibration error
HGST Hard Disk Drive Specification 321

F430 Servo: Unrecovered ADC Offset error F432 Servo: Unrecovered ADC Limit error F434 Servo: Unrecovered Balancer Resistance error F436 Servo: Unrecovered Balancer Resistance Limit error 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: Unrecovered Coil Resistance Measurement Failure F460 Servo: Unrecovered WCS Hang Error F462 Servo: Unrecovered DFT Timeout Error F464 Servo: Unrecovered SDM Timeout Error F466 Servo: Unrecovered RRO Write Error F468 Servo: Unrecovered Velocity Error F46A Servo: Unrecovered Start SID Incorrect Error F46C Servo: Unrecovered End Sid Incorrect Error F46E Servo: Unrecovered Measure GMR SDM Failure F470 Servo: Unrecovered VCM Free Speed Error F472 Servo: Unrecovered Emergency Brake Timeout Error F474 Servo: Unrecovered Excessive Current Error F476 Servo: Unrecovered 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 Parameter Error F47E Servo: Unrecovered RROF SDM Timeout Error F480 Servo: Unrecovered RROF Over Limit Error F483 Servo: Unrecovered Measure Asymmetry SDM Failure F484 Servo: Unrecovered Measure Overwrite SDM Failure F485 Servo: Unrecovered TFC Utility SDM Failure F487 Servo: Unrecovered Milli-Calibration Error F488 Servo: Unrecovered SIDSAT Timeout Error F489 Servo: Unrecovered SDM Load-And-Drop-Anchor Error F48A Servo: Unrecovered Filter Table Full Error F48B Servo: Unrecovered Filter Table Invalid Error F48D Servo: Unrecovered Measure Qsamp SDM Failure F48F Servo: Unrecovered Tilt Calibration Error 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 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 F4AD Servo: Unrecovered ODCS Detect error
HGST Hard Disk Drive Specification 322

F4AF Servo: Unrecovered Unexpected Motion error 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 Error F60C AE: Unrecovered Shorted MR Element Error F60D Unsupported Read Channel Command Error F60E Init: RRClk Dead Error F60F Init: RRClk Unlock Error F611 AE: Unrecovered ECS Shorted Fault F613 AE: Unrecovered ECS Open Fault F615 AE: Unrecovered ECS Fault F617 Channel: Unrecovered Channel Error F619 Init: SVCLK Unlock Error F61B AE: Unrecovered Open MR Element Error F61D AE: Unrecovered IC Over Temperature Error F61F AE: Unrecovered IP Clock Count Error F621 AE: Unrecovered DLC SVCLK Error F623 AE: Unrecovered Write Data BLS Error 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 Underflow Error F64D Channel: Unrecovered Sector Size Fault Error F64F Channel: Unrecovered Last Split Fault Error F651 Channel: Unrecovered Servo-Servo Overlap Error F653 Channel: Unrecovered Read Gate Fault Error F655 Channel: Unrecovered RWBI Out Fault Error F657 Channel: Unrecovered No Write Clock Error F659 Channel: Unrecovered No NRZ Clock Error F65B Channel: Unrecovered Calibration Block Fault Error F65F Channel: Unrecovered Gate Command Queue OverflowError F661 Channel: Unrecovered Ending Write Splice Fault Error F663 Channel: Unrecovered Write Gate Overlap Fault Error 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 Late Error F675 Channel: Unrecovered Preamp Count Fault Error F677 Channel: Unrecovered Pfault Read Error F679 Channel: Unrecovered Pfault Write Error F67B Channel: Unrecovered Last Data Fault Error F67D Channel: Unrecovered WRPO Fault Error F681 Channel: Unrecovered PLLFloor Error
HGST Hard Disk Drive Specification 323

F683 Channel: Unrecovered Losslock Error F685 Channel: Unrecovered VGA Floor Error F687 Channel: Unrecovered Buffer EVGA Floor Error F689 Channel: Unrecovered TA Detector Error F68B Channel: Unrecovered NPLD Error F68D Channel: Unrecovered ZGR Flag Error F68F Channel: Recovered DPLL Freq Flag Error F691 Channel: Unrecovered Massive Drop Out Detection Error F693 Channel: Unrecovered CTG Parameter Out of Bounds Flag Error 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 Error F6A9 Channel: Unrecovered RLL Parameter Error F6AB Channel: Unrecovered FIFO Underflow Error F6AD Channel: Unrecovered FIFO Overflow Error F6AF Channel: Unrecovered Iterative Decoder Error F6B1 Channel: Unrecovered Iterative Read Error F6B3 Channel: Unrecovered Encoder Overflow Error F6B5 Channel: Unrecovered Encoder Underflow Error F6B7 Channel: Unrecovered Encoder RAM CRC Error F6B9 Channel: Unrecovered Interface Fault F6BB Channel: Unrecovered QMM EVDump Parse Error F6BD Channel: Unrecovered DiBit Timeout Error F6BF Channel: Unrecovered MXP Write Fault 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 Retry Fault Error F6D5 Channel: Unrecovered WTG Timeout Fault Error F6D7 Channel: Unrecovered ITI Fault TS Transfer All Error F6D9 Channel: Unrecovered ITI Data Fault Error F6DA Channel: Unrecovered Insufficient TFC Preheat Error F6DB Channel: Unrecovered AE And FAEP Do Not Match F6DD Channel: Unrecovered Data Jam Fault Error F6DF Channel: Unrecovered Code-Word Out of Order 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 Channel: Unrecovered Power Sequencing Timeout Error F6E8 Channel: Unrecovered Mode Overlap Write Error F6EA Channel: Unrecovered Ready Fault Error
HGST Hard Disk Drive Specification 324

F6EC Channel: Unrecovered Synchronous 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 Channel: Unrecovered Preamble Quality Monitor Fault Error F6FB Channel: Unrecovered Stop For RTM Error F6FC Channel: Unrecovered RTM Configuration Error F6FD Channel: Unrecovered RTM Failure Error F6FE Channel: Unrecovered RTM Timeout Error F713 Media: Unrecovered LBA MEDC Error F717 Media: Unrecovered Write Overrun Error F71D Media: Unrecovered DRAM CRC Error F732 Media: Unrecovered Write Fault F745 Media: Unrecovered Sudden Stop Error F75A Media: Unrecovered Unknown Error F764 Media: Unrecovered Merge G-List Failed - No P-List Exists F767 Channel: Unrecovered XTS LOAD Timeout Error F76B Media: Unrecovered No NRZ Clock Error 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: Unrecovered 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 DRAM ECC LBA Error F7CD Media: Unrecovered LBA Encryption Error F7D5 Media: Unrecovered Parity PTR FIFO Error F7D7 Media: Unrecovered Parity LBA FIFO Error F7D9 Media: Unrecovered Parity Uncorrectable FIFO Error F7DB Media: Unrecovered Status Uncorrectable FIFO Error F7DD Media: Unrecovered Parity EDC SRAM Error F7DF Media: Unrecovered REQ/ACK Handshake Error F7E3 Media: Unrecovered Read Parity Error F7E5 Media: Unrecovered EPO Error F7E9 Media: Unrecovered AE Access Inhibit Error F7EB Media: Unrecovered PTR FIFO Error 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
HGST Hard Disk Drive Specification 325

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 error F32C Motor: Unrecovered Module mid-die overtemp fault F32E Motor: Unrecovered Module Vcmp hi-side overtemp fault F330 Motor: Recovered Module Vcmn hi-side overtemp fault F332 Motor: Unrecovered Invalid standby RPM request F334 Motor: Unrecovered Invalid spin state request F336 Motor: Unrecovered Hardware retract timeout F338 Motor: Unrecovered thermal limit exceeded F33A Motor: Unrecovered Predriver fault F33C Motor: Unrecovered Predriver Watchdog Fsys error F33E Motor: Unrecovered Predriver Watchdog DAC error F340 Motor: Unrecovered Predriver Speed Low error F342 Motor: Unrecovered Predriver UV Vboost error 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 Predriver Under Voltage 1.8 Volt Supply error F352 Motor: Unrecovered Predriver Under Voltage 0.9 Volt Supply error F354 Motor: Unrecovered Predriver Under Voltage 1.5 Volt Supply error F356 Motor: Unrecovered Predriver Shock Detected error F358 Motor: Unrecovered Predriver Over Temperature error F35A Motor: Unrecovered Predriver Under Voltage 3.3 Volt Supply error F35C Motor: Unrecovered Predriver Under Voltage 5 and 12 Volt Supply error F35E Motor: Unrecovered Predriver Error in Enabling Power Saving Mode F360 Motor: Unrecovered Predriver Fault in Auto Retract F362 Motor: Unrecovered Predriver Error in Utilizing External Power Supply F364 Motor: Unrecovered Predriver Regulator Supply Fault F36C Motor: Unrecovered Predriver VCM Short Error F36E Motor: Unrecovered Predriver NREG disable error
4 44 F2 Vendor Unique - Internal Target Failure F134 Head Health Check data compare error
4 44 F6 Vendor Unique - Internal Target Failure F135 Head Health Check unrecovered media error F141 BATS#2 error Read/Write Test Compare Failed
4 44 F9 Vendor Unique - Internal Target Failure 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 F602 Channel/AE: Unrecovered Internal Logic Error
4 85 00 Vendor Unique - Internal Key Seed Error 1768 Media: Recovered Key Seed ID Mismatch Error F769 Media: Unrecovered Key Seed ID Mismatch Error
HGST Hard Disk Drive Specification 326

Sense Key = Illegal Request 5 00 16 Operation in Progress
F81F CMD: Operation in Progress 5 15 00 PHY Test In Progress Error
F50D Host Interface: Phy Test Function in Progress 5 1A 00 Parameter List Length Error
F820 CMD: Unrecovered Parameter List Length Error 5 20 00 Invalid Command Operation Code
F81E CMD: Reassign Not Allowed 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 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 Field In Parameter List Error F826 CMD: Unrecovered Unsupported Log Page Error F829 CMD: Invalid Tx Setting for Combo Chip Error 5 26 02 Parameter Value Invalid F120 BATS error: Code Compatibility Failure F126 BATS error: Code checksum error F127 BATS error: Invalid header F130 BATS error: Incorrect Customer Code F13D BATS error: Invalid Code Signature F830 CMD: Unrecovered Sequence Error 5 26 04 Invalid Release of Active Persistent Reservation 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 Interface: Not ready to ready transition 6 29 01 Unit Attention - POR Occurred
F516 Host Interface: Power on reset 6 29 02 Unit Attention - SCSI Bus Reset Occurred
F517 Host Interface: SAS Hard Reset (SAS) 6 29 03 Unit Attention - Bus Device Reset Occurred
F518 Host Interface: LUN Reset (SAS) 6 29 04 Unit Attention - Self Initiated Reset Occurred
F519 Host Interface: Self initiated reset 6 29 07 I_T Nexus Loss Occurred
F554 Host Interface: I_T_Nexus Loss Occurred (SAS) 6 2A 01 Mode Parameters Changed
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
HGST Hard Disk Drive Specification 327

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 2A 10 Timestamp Changed F525 Host Interface: Timestamp Changed
6 2F 00 Commands Cleared by Another Initiator F521 Host Interface: Commands cleared by another initiator
6 2F 01 Commands Cleared by Power Loss Notification F573 Host Interface: Commands cleared due to power failure event (SAS)
6 3F 01 Microcode has been changed F522 Host Interface: Microcode changed
6 3F 05 Device Identifier Changed F537 Host Interface: Device identifier changed Sense Key = Access Denied
7 20 02 Access Denied F509 Host Interface: In Self-Test - Band locked F827 CMD: Unrecovered Access Denied Error 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: Unrecovered Application Tag Error
B 10 03 Aborted Command ­ End-to-End Reference Tag Check F56A Host Interface: End-to-End Data Protection Reference Tag check F7B9 Media: Unrecovered Reference Tag error
B 3F 0F Aborted Command - Echo Buffer Overwritten F544 Host Interface: Echo buffer overwritten
B 44 00 Internal Target Failure F52D Host Interface: Buffer CRC error on read F52E Host Interface: Internal target failure F54A Host Interface: Xfer Ready credit exceeded F54B Host Interface: Transfer length error F56B Host Interface: ECC error in DRAM customer data area F56C Host Interface: Uncorrectable DRAM ECC error 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 F775 Media: Unrecovered Buffers timeout F776 Media: Unrecovered DASH done timeout F777 Media: Unrecovered DASH unknown timeout
HGST Hard Disk Drive Specification 328

F77A Media: BUFCNT Timeout Error F77B Media: Unrecovered Abort EOS fail F77E Media: Write Error Recovery Timeout F77F Media: Read Error Recovery Timeout F7D0 Media: Unrecovered Pre-load Timeout Error F813 CMD: Insufficient Buffer Space Error F815 CMD: Aborted From Internal TMF Error B 47 01 Data Phase CRC Error F54E Host Interface: Data Phase CRC Error 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 Overlapped Commands Attempted F534 Host Interface: Overlapped command attempted B 4F 00 Command Aborted Due To OOB F53F Host Interface: Abort by OOB (SAS)
Sense Key = Miscompare E 1D 00 Miscompare During Verify Operation
F535 Host Interface: Miscompare during verify
HGST Hard Disk Drive Specification 329

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.
Sense Key Specific (Byte 15 through 17)
The definition of this field is determined by the value of the sense key field.
Sense Key Specific - Illegal Request (Sense Key = 5h)
Error field pointer is returned.

Bit

Byte

7

6

5

4

3

2

1

0

15

SKSV C/D

Reserved

BPV

Bit Pointer

16

(MSB)

17

Field Pointer

(LSB)

Table 322 Field Pointer Bytes

SKSV C/D
BPV Bit Pointer Field Pointer

Sense-key specific valid

0

Sense-key specific field is not valid.

1

Sense-key specific field is valid.

Command/Data

0

Indicates that the illegal parameter was in the data parameters sent by the initiator

during DATA OUT phase

1

Indicates that the illegal parameter was in the command descriptor block.

Bit Pointer Valid

0

Bit pointer field is not valid.

1

Bit pointer field is significant.

Indicates which bit of the byte number reported in Field Pointer is the bit in error. When a multiple bit field is in error, the pointer points to the most significant bit of the field.

Indicates which bytes of the command descriptor block or of the parameter data were in error. Bytes are numbered starting from zero, as shown in the tables describing the commands and parameters. When a multiple byte field id is in error, the pointer points to the most significant byte of that field.

HGST Hard Disk Drive Specification 330

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.

Bit

Byte

7

6

5

4

3

2

1

0

15

SKSV

Reserved

16

Secondary Step

ERP Type

17

Actual Retry Count

Table 323 Actual Retry Count

SKSV

Sense-key specific valid

0 Actual Retry Count is not valid.

1 Actual Retry Count is valid.

Actual Retry Count Number of retry steps used in attempting to recover from the error condition.

Secondary Step

Secondary error recovery step (valid for servo errors only).

ERP Type

Error recovery table branch for this error. Valid values are shown in the table below.

Recovery Type Read Verify Write Seek Read, Sync Byte branch Read, Thermal Asperity branch Read, Minus Mod branch Verify, Sync Byte branch Verify, Thermal Asperity branch Verify, Minus Mod branch Table 324 Recovery Type

ERP Type 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09

HGST Hard Disk Drive Specification 331

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.

Byte

7

6

15

SKSV

16

(MSB)

17

Bit

5

4

3

2

Reserved

Progress Indication

1

0

(LSB)

Table 325 Progress Indication

Reserved (Byte 18 through 19)

SKSV Progress Indication

Sense-key specific valid 0 Progress Indication is not valid. 1 Progress Indication is valid. Indicates a percent complete in which the returned value is the numerator that has 10000h as its denominator.

Reserved fields are filled with zero.

Vendor unique error information (Byte 20 through 23)

This field gives detailed information about the error. It contains a unique code which describes where the error was detected and which piece of hardware or microcode detected the error depending on current operation.
Physical Error Record (Product Specific Information) (Byte 24 through 29)

 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. If the head number is undetermined, byte 27 is set to 0FFh. If cylinder, head, and sector have no relevance the error, bytes 24 through 29 will all be set to 0FFFFFFFFFFFFh for Valid = 0 and ILI = 0. This Physical Error Record field is valid for Sense Key 1, 3 and 4 only.

Valid 1
1
1 0

ILI Description 0 Cylinder Number (bytes 24-26)
Head number (byte 27) Sector Number (bytes 28-29)
0 Cylinder Number (bytes 24-26) Head number (byte 27) Sector Number (bytes 28-29)
1 0x000000000000 x 0x000000000000 - (not used/invalid)

Table 326 Log Only Errors

HGST Hard Disk Drive Specification 332

Descriptor Format Sense Data

The descriptor format sense data for response codes 72h (current errors) and 73h (deferred errors) is defined below.

Byte 7

Bit

6

5

4

3

2

1

0

0

Reserved= 0

Response Code (72h or 73h)

1

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 # 1

m...x

. . . . . . . . . . . . .

x -n

Sense Data Descriptor # K

Table 327 Descriptor Format Sense Data

The Sense Key definitions is the same as fixed format sense data. Response Code: 72h Current Error. See section 12.1.3 "Sense Data Response Code" for more details. 73h Deferred Error. See section 12.1.3 "Sense Data Response Code" for more details.

The Additional Sense Code/Qualifier definitions is the same as fixed format sense data.
The Value of the Additional Sense Length indicates the remaining number of bytes in the sense data
Sense data descriptors (Byte 8 through n) provide specific sense information. The general format of a sense data descriptor is shown below:

Bit

Byte

7

6

5

4

3

2

1

0

0

Descriptor Type

1

Additional Length (n-1)

2-n

Sense Data Descriptor Specific

Table 328 Sense Data Descriptor Format

The Descriptor Type identifies the type of a sense data descriptor. (Supported types are listed below)

Type Code 00h 01h 02h 03h 05h 80h 81h

Description Information Sense Data Descriptor Command-specific Sense Data Descriptor Sense Key Specific Sense Data Descriptor Field Replaceable Unit Sense Descriptor Block Command Sense Data Descriptor Vendor Unique Unit Error Code Sense Data Descriptor Vendor Unique Physical Error Record Sense Data Descriptor

Table 329 Supported Descriptor Types

The ADDITIONAL LENGTH field indicates the number of sense data descriptor specific bytes that follow in the sense data descriptor.

HGST Hard Disk Drive Specification 333

Order of Sense Descriptors

The drive may return up to 7 sense data descriptors in byte 8 through byte 59 of the sense data, up to the number of sense data bytes allowed (see Table 330). The sense descriptors returned will always be in the order shown in the table below, regardless of whether a descriptor contains valid information or not.

Byte 7

Bit

6

5

4

3

2

1

0

0-7 8-19

Common Headers Information Sense Data Descriptor

20-31

Command-specific Sense Data Descriptor

32-39

Sense Key Specific Sense Data Descriptor

40-43

Field Replaceable Unit (FRU) Sense Data Descriptor

44-47

Block Command Sense Data Descriptor

48-51 52-59

Vendor Unique Unit Error Code Sense Data Descriptor Vendor Unique Physical Error Record Sense Data Descriptor

Table 330 Sense Data Descriptor List

HGST Hard Disk Drive Specification 334

Sense Data Descriptor Definitions
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. Format of the Information Sense Data Descriptor is shown in Table 331

Byte 7

Bit

6

5

4

3

2

1

0

0

Descriptor Type (00h)

1

Additional Length (0Ah)

2

VALID

Reserved

3

Reserved

4-11

Information

Table 331 Information Sense Data Descriptor Format

ILI = 0 (or if the descriptor is not present): The Information 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.

Descriptor Type

Set to 00h for Information Sense Data Descriptor.

Additional Length Set to 0Ah for Information Sense Data Descriptor.

VALID

This bit is set to 1 when content of the Information field is valid, and set to 0 if the Information field is invalid.

Information

This field contains an LBA or other information depending on the value of the ILI bit in the Block Command Sense Descriptor (See section 12.3.2.5 "Block Command Sense Descriptor").

Note: An LBA other than the command LBA may be reported on the Reassign Block (07h) command.
- ILI = 1: The Information field contains the difference (residue) of the requested length in bytes. Negative values are indicated by two's complement notation

HGST Hard Disk Drive Specification 335

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

Bit

Byte

7

6

5

4

3

2

1

0

0

Descriptor Type (01h)

1

Additional Length (0Ah)

2

Reserved

3

Reserved

4-11

Command-Specific Information

Table 332 Command-specific Sense Data Descriptor Format

Descriptor Type

Set to 01h for Command-specific Sense Data Descriptor.

Additional Length

Set to 0Ah for Command-specific Sense Data Descriptor.

Command-specific Information

The value of this field is set the same ways as Command Specific Information field in fixed format sense data (See section 12.2.7 "Command Specific Information (Byte 8 through 11)")

Sense Key Specific Sense Data Descriptor (Byte 32 - 39)

The Sense-key Specific Sense Data Descriptor is stored in bytes 32 through 39 of the descriptor format sense data. Format of Sense-key Specific Sense Data Descriptor is shown in Table 333.

Bit

Byte

7

6

5

4

3

2

1

0

0

Descriptor Type (02h)

1

Additional Length (06h)

2

Reserved

3

Reserved

0

Descriptor Type (02h)

4

SKSV

Sense Key Specific Bits

5-6

Sense Key Specific Bytes

7

Reserved

Table 333 Information Sense Data Descriptor Format

Fields in byte 4 through 5 (including the SKSV bit, Sense-Key Specific Bits, and Sense-Key Specific Bytes):

Descriptor Type

Set to 02h for Command-specific Sense Data Descriptor.

Additional Length Set to 06h for Command-specific Sense Data Descriptor.

These fields are set the same ways as byte 15 - 17 in fixed format sense data (See section 12.2.10 "Sense Key Specific (Byte 15 through 17)" for details).

HGST Hard Disk Drive Specification 336

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

Byte 7

Bit

6

5

4

3

2

1

0

0

Descriptor Type (03h)

1

Additional Length (02h)

2

Reserved

3

Field Replaceable Unit Code

Table 334 Field Replaceable Unit Sense Data Descriptor Format

Descriptor Type

Set to 03h for Field Replaceable Unit Sense Data Descriptor.

Additional Length

Set to 02h for Field Replaceable Unit Sense Data Descriptor.

Command-specific Information

This field is set the same way as the Field Replaceable Unit Code of fixed format sense data. (See section 12.2.9 "FRU: Field Replaceable Unit (Byte 14)" for details).

Block Command Sense Descriptor (Byte 44 - 47)

The Block Command Sense Data Descriptor is stored in bytes 44 through 47 of descriptor format sense data. Format of the Block Command Sense Data Descriptor is shown in Table 335.

Byte 7

Bit

6

5

4

3

2

1

0

0

Descriptor Type (05h)

1

Additional Length (02h)

2

Reserved

3

Reserved=0

ILI

Reserved=0

Table 335 Block Command Sense Data Descriptor Format

Descriptor Type Set to 05h for Block Command Sense Data Descriptor.

Additional Length Set to 02h for Block Command Sense Data Descriptor.

ILI:

Value of the ILI bit is set to indicate what type of value is stored in the Information field of the

Information Sense Data Descriptor (see section 12.3.2.1 "Information Sense Data Descriptor

(Byte 8 - 19)" for details):

HGST Hard Disk Drive Specification 337

Vendor Unique Unit Error Sense Data Descriptor (Byte 48 ­ 51)
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 336.

Byte 7

Bit

6

5

4

3

2

1

0

0

Descriptor Type (80h)

1

Additional Length (02h)

2-3

Unit Error Code (UEC)

Table 336 Vendor Unique Unit Error Code Sense Data Descriptor

Descriptor Type Set to 80h for Vendor Unique Unit Error Code Sense Data Descriptor.

Additional Length Set to 02h for Vendor Unique Unit Error Code Sense Data Descriptor.

Unit Error Code:

This field contains the same value as the Vendor Unique Error Information field in fixed format sense data which gives detailed information about the error (See section 12.2.12 "Vendor unique error information (Byte 20 through 23)"). It contains a unique code which describes where the error was detected and which piece of hardware or microcode detected the error depending on current operation

Vendor Unique Physical Error Record Sense Data Descriptor (Byte 52-59)
The Vendor Unique Physical Error Record Sense Data Descriptor is stored in bytes 52 through 59 of descriptor format sense data. Format of the Vendor Unique Physical Error Record Sense Data Descriptor is shown in Table 336.

Byte 7

Bit

6

5

4

3

2

1

0

0

Descriptor Type (81h)

1

Additional Length (06h)

2-7

Physical Error Record

Table 337 Vendor Unique Physical Error Record Sense Data Descriptor

Descriptor Type Set to 81h for Vendor Unique Unit Physical Error Record Sense Data Descriptor.

Additional Length Set to 06h for Vendor Unique Unit Physical Error Record Sense Data Descriptor.

Unit Error Code:

This field is set the same way as the Physical Error Record in fixed format sense data. (See section 12.2.13 "Physical Error Record (Product Specific Information) (Byte 24 through 29)" for details).

HGST Hard Disk Drive Specification 338

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 10 "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. interface, media, servo, etc. types of errors. The table is sorted without regard to the first hex digit; instead, sorting is by the least significant three hex digits.

Table 338 Unit Error Codes

UEC 0000

No Error

Description

F101 F102 F103 F104 F105 F106 F107 F108 1109 F10D F111 F112 F118 F119 F11B F11C F11D F120 F123 F124 F125 F126 F127 F12A F12B F12D F12E F12F F130 F131 F132 F133 F134 F135

BATS error: Reserved Area - Invalid request BATS error: Reserved Area - Broken BATS error: Reserved Area - Invalid version BATS error: Reserved Area - Invalid checksum BATS error: Reserved Area - Invalid eyecatcher BATS error: Reserved Area - Invalid main header checksum BATS error: Reserved Area - Invalid read length BATS error: Reserved Area - Address boundary error BATS error: Reserved Area - Error reading first copy BATS error: Reserved Area - Write fix hard error BATS error: RAM code load error BATS error: RAM code check BATS#2 error: Seek test error BATS#2 error: Read/write test error BATS#2 error: CRC test error BATS#2 error: XOR test error BATS error: Incorrect Disk Code BATS error: Code Compatibility Failure BATS error: Reserved map index too large Bring-up error BATS error: Invalid RID/FID BATS error: Code checksum error BATS error: Invalid header DRAM test error BATS error: Reserved area - invalid model Format Reserved: FAT Size Exceeded Error Format Reserved: Insufficient DIRS Good Error Format Reserved: Insufficient FATS Good Error BATS error: Incorrect Customer Code Flash timeout GEM FH track read error BATS error: Vendor ID mismatch Head Health Check data compare error Head Health Check unrecovered media error
HGST Hard Disk Drive Specification 339

F136 F137 F139 F13B F13C F13D F13E F13F F140 F141 F142 F143 F144 F147 F148 F149 F14A F14B F14C F14D F14E 1201 1202 F203 F204 F205 F206 F208 F209 F20A F20B F20C F20D F20E F20F F220 F221 F230 F231 F240 F241 F310 1311 F312 1313 F314 1315 F316 1317

BATS#2 error: End-To-End Data Protection error Flash ECC error Format Reserved: Resize RID/FID Error BATS error: SW Target broken BATS error: NCDE DRAM failure BATS error: Invalid Code Signature BATS#2 error: TCG Test Failed BATS#2 error: Read/Write Test Compare Failed Format Reserved: Too many Defects Error BATS#2 error Read/Write Test Compare Failed ATA Diagnostic Code: No Error ATA Diagnostic Code: Formatter Error ATA Diagnostic Code: Sector Buffer Error ATA Diagnostic Code: Read/Write Test Error BATS error: Still broken after clear BATS#2 error: Security: AES Error BATS#2 error: Security: RSA Error BATS#2 error: Security: DRGB Error BATS#2 error: Security: SHA256 Error BATS#2 error: Security: HMAC Error BATS#2 error: Security: Hardware AES Error Sanity: Error In UEC Class Sanity: Error In UEC Cause Sanity: Sanity Check Failure Reassign reserved area media error G-list full - can't reassign any more sectors No spares available Mode Page Structure Mismatch Miscompare of SBA in the P-List Error Clearing Reset State DSLT: Invalid number of splits DSLT: Invalid relaxed format DSLT: First Fragment too large DSLT: Invalid end offset DSLT: Cycle not complete MFG: Consistency Check failed MFG: General Align Tables Missing SEC_MGR: AES Hardware Error SEC_MGR: BDE Unwrap Error SEC_MGR: PRNG Seed Error SEC_MGR: PRNG General Error Motor: Unrecovered Spindle Current error Motor: Recovered Internal 12V not OK timeout Motor: Unrecovered Internal 12V not OK timeout Motor: Recovered Inductive Sense measurement timeout Motor: Unrecovered Inductive Sense speed error Motor: Recovered Spin Sense speed error Motor: Unrecovered Spin Sense speed error Motor: Recovered Spin Sense timeout
HGST Hard Disk Drive Specification 340

F318 1319 F31A F31C 131D F31E 131F F320 1321 F322 1323 F324 1325 F326 1327 F328 1329 F32A 132B F32C 132D F32E 132F F330 1331 F332 1333 F334 1335 F336 1337 F338 1339 F33A 133B F33C 133D F33E 133F F340 1341 F342 1343 F344 1345 F346 1347 F348 1349

Motor: Unrecovered Spin Sense timeout Motor: Recovered Target speed error Motor: Unrecovered Target speed error Motor: Unrecovered Power driver version error Motor: Recovered Over current error Motor: Unrecovered Over current error Motor: Recovered System clock watchdog error Motor: Unrecovered System clock watchdog error Motor: Recovered Negative regulator fault Motor: Unrecovered Negative regulator fault Motor: Recovered Module overtemp error Motor: Unrecovered Module overtemp error Motor: Recovered 12V or 5V OK error Motor: Unrecovered 12V or 5V OK error Motor: Recovered unknown error Motor: Unrecovered unknown error Motor: Recovered VCM DAC watchdog error Motor: Unrecovered VCM DAC watchdog error Motor: Recovered Module mid-die overtemp fault Motor: Unrecovered Module mid-die overtemp fault Motor: Recovered Module Vcmp hi-side overtemp fault Motor: Unrecovered Module Vcmp hi-side overtemp fault Motor: Recovered Module Vcmn hi-side overtemp fault Motor: Recovered Module Vcmn hi-side overtemp fault Motor: Recovered Invalid standby RPM request Motor: Unrecovered Invalid standby RPM request Motor: Recovered Invalid spin state request Motor: Unrecovered Invalid spin state request Motor: Recovered Hardware retract timeout Motor: Unrecovered Hardware retract timeout Motor: Recovered thermal limit exceeded Motor: Unrecovered thermal limit exceeded Motor: Recovered Predriver fault Motor: Unrecovered Predriver fault Motor: Recovered Predriver Watchdog Fsys error Motor: Unrecovered Predriver Watchdog Fsys error Motor: Recovered Predriver Watchdog DAC error Motor: Unrecovered Predriver Watchdog DAC error Motor: Recovered Predriver Speed Low error Motor: Unrecovered Predriver Speed Low error Motor: Recovered Predriver UV Vboost error Motor: Unrecovered Predriver UV Vboost error Motor: Recovered Predriver NREG UV error Motor: Unrecovered Predriver NREG UV error Motor: Recovered Predriver Ext NPOR error Motor: Unrecovered Predriver Ext NPOR error Motor: Recovered Predriver Reg UV error Motor: Unrecovered Predriver Reg UV error Motor: Recovered Predriver Under Voltage 12 Volt Supply error
HGST Hard Disk Drive Specification 341

F34A 134B F34C 134D F34E 134F F350 1351 F352 1353 F354 1355 F356 1357 F358 1359 F35A 135B F35C 135D F35E 135F F360 1361 F362 1363 F364 1365 F366 1367 F368 1369 F36A 136B F36C 136D F36E 136F F370 1371 F372 1373 F374 1375 F376 1401 F402 1403 F404

Motor: Unrecovered Predriver Under Voltage 12 Volt Supply error Motor: Recovered Predriver Under Voltage 5 Volt Supply error Motor: Unrecovered Predriver Under Voltage 5 Volt Supply error Motor: Recovered Predriver Over Voltage 12 Volt Supply error Motor: Unrecovered Predriver Over Voltage 12 Volt Supply error Motor: Recovered Predriver Under Voltage 1.8 Volt Supply error Motor: Unrecovered Predriver Under Voltage 1.8 Volt Supply error Motor: Recovered Predriver Under Voltage 0.9 Volt Supply error Motor: Unrecovered Predriver Under Voltage 0.9 Volt Supply error Motor: Recovered Predriver Under Voltage 1.5 Volt Supply error Motor: Unrecovered Predriver Under Voltage 1.5 Volt Supply error Motor: Recovered Predriver Shock Detected error Motor: Unrecovered Predriver Shock Detected error Motor: Recovered Predriver Over Temperature error Motor: Unrecovered Predriver Over Temperature error Motor: Recovered Predriver Under Voltage 3.3 Volt Supply error Motor: Unrecovered Predriver Under Voltage 3.3 Volt Supply error Motor: Recovered Predriver Under Voltage 5 and 12 Volt Supply error Motor: Unrecovered Predriver Under Voltage 5 and 12 Volt Supply error Motor: Recovered Predriver Error in Enabling Power Saving Mode Motor: Unrecovered Predriver Error in Enabling Power Saving Mode Motor: Recovered Predriver Fault in Auto Retract Motor: Unrecovered Predriver Fault in Auto Retract Motor: Recovered Predriver Error in Utilizing External Power Supply Motor: Unrecovered Predriver Error in Utilizing External Power Supply Motor: Recovered Predriver Regulator Supply Fault Motor: Unrecovered Predriver Regulator Supply Fault Motor: Recovered Predriver Voltage Offset Calibration Error Motor: Unrecovered Predriver Voltage Offset Calibration Error Motor: Recovered Predriver BEMF Gain Calibration Error Motor: Unrecovered Predriver BEMF Gain Calibration Error Motor: Recovered Predriver BEMF Unload Calibration Error Motor: Unrecovered Predriver BEMF Unload Calibration Error Motor: Recovered Predriver VCM Short Error Motor: Unrecovered Predriver VCM Short Error Motor: Recovered Predriver NREG disable error Motor: Unrecovered Predriver NREG disable error Motor: Recovered IDCS Calibration Measurement 1 Error Motor: Unrecovered IDCS Calibration Measurement 1 Error Motor: Recovered IDCS Calibration Measurement 2 Error Motor: Unrecovered IDCS Calibration Measurement 2 Error Motor: Recovered IDCS Calibration Saturation Error Motor: Unrecovered IDCS Calibration Saturation Error Motor: Recovered IDCS Calibration Adjustment Error Motor: Unrecovered IDCS Calibration Adjustment Error Servo: Recovered Requested rezero head does not exist Servo: Unrecovered Requested rezero head does not exist Servo: Recovered Back EMF movement in progress Servo: Unrecovered Back EMF movement in progress
HGST Hard Disk Drive Specification 342

1405 F406 1407 F408 1409 F40A 140B F40C 140D F40E 140F F410 1411 F412 1413 F414 1415 F416 1417 F418 1419 F41A 141B F41C 141D F41E 141F F420 1421 F422 1423 F424 1425 F426 1427 F428 1429 F42A 142B F42C 142D F42E 142F F430 1431 F432 1433 F434 1435

Servo: Recovered Back EMF timeout error Servo: Unrecovered Back EMF timeout error Servo: Recovered ADC conversion timeout Servo: Unrecovered ADC conversion timeout Servo: Recovered Load/unload calibration error Servo: Unrecovered Load/unload calibration error Servo: Recovered Invalid 5 volts Servo: Unrecovered Invalid 5 volts Servo: Recovered Invalid 12 volts Servo: Unrecovered Invalid 12 volts Servo: Recovered Invalid harmonic requested Servo: Unrecovered Invalid harmonic requested Servo: Recovered Gain BEMF Calibration error Servo: Unrecovered Gain BEMF Calibration error Servo: Recovered VOFF BEMF calibration error Servo: Unrecovered VOFF BEMF calibration error Servo: Recovered Invalid temperature Servo: Unrecovered Invalid temperature Servo: Recovered Truncated rezero Servo: Unrecovered Truncated rezero Servo: Recovered Heads not loaded Servo: Unrecovered Heads not loaded Servo: Recovered Current error Servo: Unrecovered Current error Servo: Recovered Seek timeout Servo: Unrecovered Seek timeout Servo: Recovered Seek error Servo: Unrecovered Seek error Servo: Recovered Track following error Servo: Unrecovered Track following error Servo: Recovered Track follow timeout Servo: Unrecovered Track follow timeout Servo: Recovered KT Seek out of range Servo: Unrecovered KT Seek out of range Servo: Recovered DAC Offset calibration error Servo: Unrecovered DAC Offset calibration error Servo: Recovered Load speed error Servo: Unrecovered Load speed error Servo: Recovered RRO Calibration timeout Servo: Unrecovered RRO Calibration timeout Servo: Recovered ADC Calibration error Servo: Unrecovered ADC Calibration error Servo: Recovered ADC Offset error Servo: Unrecovered ADC Offset error Servo: Recovered ADC Limit error Servo: Unrecovered ADC Limit error Servo: Recovered Balancer Resistance error Servo: Unrecovered Balancer Resistance error Servo: Recovered Balancer Resistance Limit error
HGST Hard Disk Drive Specification 343

F436 1437 F438 1439 F43A 143B F43C 143D F43E 143F F440 1441 F442 1443 F444 1445 F446 1447 F448 1449 F44A 144B F44C 144D F44E 144F F450 1451 F452 1453 F454 1455 F456 1457 F458 1459 F45A 145B F45C 145D F45E 145F F460 1461 F462 1463 F464 1465 F466

Servo: Unrecovered Balancer Resistance Limit error Servo: Recovered First Cylinder error Servo: Unrecovered First Cylinder error Servo: Recovered Valid Cylinder error Servo: Unrecovered Valid Cylinder error Servo: Recovered ADC Saturation error Servo: Unrecovered ADC Saturation error Servo: Recovered Latch Break timeout Servo: Unrecovered Latch Break timeout Servo: Recovered MR Resistance out of range error Servo: Unrecovered MR Resistance out of range error Servo: Recovered VCM Retract error Servo: Unrecovered VCM Retract error Servo: Recovered Load Retry error Servo: Unrecovered Load Retry error Servo: Recovered DFT Sharp error Servo: Unrecovered DFT Sharp error Servo: Recovered Load/Unload state error Servo: Unrecovered Load/Unload state error Servo: Recovered TFCR out-of-range error Servo: Unrecovered TFCR out-of-range error Servo: Recovered Measure GMR Timeout Servo: Unrecovered Measure GMR Timeout Servo: Recovered Coil Resistance Measurement Failure Servo: Unrecovered Coil Resistance Measurement Failure Servo: Recovered SHARP Parity Error Servo: Unrecovered SHARP Parity Error Servo: Recovered SHARP Parity Rate Error Servo: Unrecovered SHARP Parity Rate Error Servo: Recovered SHARP Decode Error Servo: Unrecovered SHARP Decode Error Servo: Recovered SHARP Decode Rate Error Servo: Unrecovered SHARP Decode Rate Error Servo: Recovered SHARP Timeout Error Servo: Unrecovered SHARP Timeout Error Servo: Recovered SHARP Timeout Rate Error Servo: Unrecovered SHARP Timeout Rate Error Servo: Recovered SHARP Other Error Servo: Unrecovered SHARP Other Error Servo: Recovered SHARP Other Rate Error Servo: Unrecovered SHART Other Rate Error Servo: Recovered WCS Hang Error Servo: Unrecovered WCS Hang Error Servo: Recovered DFT Timeout Error Servo: Unrecovered DFT Timeout Error Servo: Recovered SDM Timeout Error Servo: Unrecovered SDM Timeout Error Servo: Recovered RRO Write Error Servo: Unrecovered RRO Write Error
HGST Hard Disk Drive Specification 344

1467 F468 1469 F46A 146B F46C 146D F46E 146F F470 1471 F472 1473 F474 1475 F476 F477 F478 F479 F491 F492 F493 F494 F495 1496 F497 1498 F499 149A F49B 149C F49D 149E F49F 14A0 F4A1 14A2 F4A3 14A4 F4A5 14A6 F4A7 14A8 14A9 F501 F502 F503 F504 F505

Servo: Recovered Velocity Error Servo: Unrecovered Velocity Error Servo: Recovered Start SID Incorrect Error Servo: Unrecovered Start SID Incorrect Error Servo: Recovered End Sid Incorrect Error Servo: Unrecovered End Sid Incorrect Error Servo: Recovered Measure GMR SDM Failure Servo: Unrecovered Measure GMR SDM Failure Servo: Recovered VCM Free Speed Error Servo: Unrecovered VCM Free Speed Error Servo: Recovered Emergency Brake Timeout Error Servo: Unrecovered Emergency Brake Timeout Error Servo: Recovered Excessive Current Error Servo: Unrecovered Excessive Current Error Servo: Recovered Excessive Velocity Error Servo: Unrecovered Excessive Velocity Error Servo: Unrecovered Invalid SDM CDB Error Servo: Unrecovered Invalid SDM Descriptor Error Servo: Unrecovered Invalid DFT Descriptor Error Servo: Unrecovered Tilt Numerical Error Servo: Unrecovered Milli Table Load Error Servo: Unrecovered TFCR DAC Out of Range Servo: Unrecovered MRR DAC Out of Range Servo: Unrecovered TFCR Open/Short Servo: Recovered DTID Inhibit Error Servo: Unrecovered DTID Inhibit Error Servo: Recovered DTID Unlock Error Servo: Unrecovered DTID Unlock Error Servo: Recovered SHARP Pulse TFC Entry Error Servo: Unrecovered SHARP Pulse TFC Entry Error Servo: Recovered Heads Not Loaded FFSULI Servo: Unrecovered Heads Not Loaded FFSULI Servo: Recovered Load Abort FFSULI Servo: Unrecovered Load Abort FFSULI Servo: Recovered IDLEA Grab Error Servo: Unrecovered IDLEA Grab Error Servo: Recovered IDLEA Seek Error Servo: Unrecovered IDLEA Seek Error Servo: Recovered AVEDAC Error Servo: Unrecovered AVEDAC Error Servo: Recovered IDLEA Exit Timeout Error Servo: Unrecovered IDLEA Exit Timeout Error Servo: Recovered IDLEA Long Seek Error Servo: Unrecovered IDLEA Long Seek Error Host Interface: Logical unit not ready Host Interface: Logical unit becoming ready Host Interface: Logical unit not ready - initializing command required Host Interface: Not ready - format in progress Host Interface: Not ready - self-test in progress
HGST Hard Disk Drive Specification 345

F506 F507 F508 F509 F50B F50C F50D F511 F512 F514 F516 F517 F518 F519 F51C F51D F51E F51F F520 F521 F522 F524 F525 F52D F52E F534 F535 F536 F537 F53E F53F F544 F54A F54B F54E F550 F551 F552 F553 F554 F555 F560 F561 F562 F567 F568 F569 F56A F56B

Host Interface: Reassign failed Host Interface: Format failed Host Interface: Not Ready - Session opened Host Interface: In Self-Test - Band locked Host Interface: Not Ready - Sanitize in progress Host Interface: Sanitize Command failed Host Interface: Phy Test Function in Progress Host Interface: Illegal Request Sequence Error Host Interface: Invalid Message Host Interface: Not ready to ready transition Host Interface: Power on reset Host Interface: SAS Hard Reset (SAS) Host Interface: LUN Reset (SAS) Host Interface: Self initiated reset Host Interface: Mode parameters changed Host Interface: Log parameters changed Host Interface: Reservations pre-empted Host Interface: Reservations released Host Interface: Registrations pre-empted Host Interface: Commands cleared by another initiator Host Interface: Microcode changed Host Interface: Capacity Data Changed Host Interface: Timestamp Changed Host Interface: Buffer CRC error on read Host Interface: Internal target failure Host Interface: Overlapped command attempted Host Interface: Miscompare during verify Host Interface: Reservation conflict Host Interface: Device identifier changed Host Interface: Data phase error Host Interface: Abort by OOB (SAS) Host Interface: Echo buffer overwritten Host Interface: Xfer Ready credit exceeded Host Interface: Transfer length error Host Interface: Data Phase CRC Error Host Interface: NAK rcvd (SAS) Host Interface: ACK NAK Timeout (SAS) Host Interface: Bad parameter offset (SAS) Host Interface: LUN Not ready, Notify (Enable Spinup) required (SAS) Host Interface: I_T_Nexus Loss Occurred (SAS) Host Interface: Initiator Response Timeout (SAS) Host Interface: Too much write data (SAS) Host Interface: Information unit too short (SAS) Host Interface: Information unit too long (SAS) Host Interface: Insufficient registration resources Host Interface: End-to-End Data Protection Guard check Host Interface: End-to-End Data Protection Application Tag check Host Interface: End-to-End Data Protection Reference Tag check Host Interface: ECC error in DRAM customer data area
HGST Hard Disk Drive Specification 346

F56C F570 F572 F573 F579 F57A F57B F57D F602 F603 F604 F605 1606 F607 1609 F60A 160B F60C F60D F60E F60F 1610 F611 1612 F613 1614 F615 1616 F617 F619 161A F61B 161C F61D 161E F61F 1620 F621 1622 F623 1626 F627 1628 F629 162A F62B 162E F62F 1630

Host Interface: Uncorrectable DRAM ECC error Host Interface: Host interface Synchronous CRC error Host Interface: LUN not ready; manual intervention required Host Interface: Commands cleared due to power failure event (SAS) Host Interface: Data Checksum Error Host Interface: Synchronous CRC Error on Write Host Interface: Synchronous CRC LBA Error Host Interface: Break Received (SAS only) Channel/AE: Unrecovered Internal Logic Error Channel/AE: Unrecovered Internal Target Failure Channel/AE: Unrecovered Internal Calibration Error Channel/AE: Unrecovered Internal MR Calibration Error AE: Recovered AE Last Data Read Error Channel/AE: Unrecovered data with PPM or precomp load AE: Recovered TFC Short Error AE: TFC Short Error AE: Recovered Shorted MR Element Error AE: Unrecovered Shorted MR Element Error Unsupported Read Channel Command Error Init: RRClk Dead Error Init: RRClk Unlock Error AE: Recovered ECS Shorted Fault AE: Unrecovered ECS Shorted Fault AE: Recovered ECS Open Fault AE: Unrecovered ECS Open Fault AE: Recovered ECS Fault AE: Unrecovered ECS Fault Channel: Recovered Channel Error Channel: Unrecovered Channel Error Init: SVCLK Unlock Error AE: Recovered Open MR Element Error AE: Unrecovered Open MR Element Error AE: Recovered IC Over Temperature Error AE: Unrecovered IC Over Temperature Error AE: Recovered IP Clock Count Error AE: Unrecovered IP Clock Count Error AE: Recovered DLC SVCLK Error AE: Unrecovered DLC SVCLK Error AE: Recovered Write Data BLS Error AE: Unrecovered Write Data BLS Error AE: Recovered Power Supply Error AE: Unrecovered Power Supply Error AE: Recovered Open Write Head Error AE: Unrecovered Open Write Head Error AE: Recovered Write Transition Error AE: Unrecovered Write Transition Error Channel: Recovered Channel NRZ Clear Timeout Error Channel: Unrecovered Channel NRZ Clear Timeout Error AE: Recovered SPE Low In Write Fault
HGST Hard Disk Drive Specification 347

F631 F633 1636 F637 163C F63D F642 F643 1644 F645 1648 F649 164A F64B 164C F64D 164E F64F 1650 F651 1652 F653 1654 F655 1656 F657 1658 F659 165A F65B 165C F65D 165E F65F 1660 F661 1662 F663 1664 F665 1666 F667 1668 F669 166A F66B 166C F66D 166E

AE: Unrecovered SPE Low In Write Fault Channel: Unrecovered Write Synth Unlock error AE: Recovered Short Write Head Error AE: Unrecovered Short Write Head Error AE: Recovered TFC Open Error AE: Unrecovered TFC Open Error AE: Unrecovered Software Readback Error AE: Unrecovered Readback Error AE: Recovered Latch Fault Error AE: Unrecovered Latch Fault Error Channel: Recovered Reset Flag Error Channel: Unrecovered Reset Flag Error Channel: Recovered Gate Command Queue Underflow Error Channel: Unrecovered Gate Command Queue Underflow Error Channel: Recovered Sector Size Fault Error Channel: Unrecovered Sector Size Fault Error Channel: Recovered Last Split Fault Error Channel: Unrecovered Last Split Fault Error Channel: Recovered Servo-Servo Overlap Error Channel: Unrecovered Servo-Servo Overlap Error Channel: Recovered Read Gate Fault Error Channel: Unrecovered Read Gate Fault Error Channel: Recovered RWBI Out Fault Error Channel: Unrecovered RWBI Out Fault Error Channel: Recovered No Write Clock Error Channel: Unrecovered No Write Clock Error Channel: Recovered No NRZ Clock Error Channel: Unrecovered No NRZ Clock Error Channel: Recovered Calibration Block Fault Error Channel: Unrecovered Calibration Block Fault Error Channel: Recovered Mode Overlap Read Fault Error Channel: Unrecovered Mode Overlap Read Fault Error Channel: Recovered Gate Command Queue Overflow Error Channel: Unrecovered Gate Command Queue OverflowError Channel: Recovered Ending Write Splice Fault Error Channel: Unrecovered Ending Write Splice Fault Error Channel: Recovered Write Gate Overlap Fault Error Channel: Unrecovered Write Gate Overlap Fault Error Channel: Recovered Write Gate Fault Error Channel: Unrecovered Write Gate Fault Error Channel: Recovered Buffer Overflow Write Error Channel: Unrecovered Buffer Overflow Write Error Channel: Recovered Buffer Underflow Write Error Channel: Unrecovered Buffer Underflow Write Error Channel: Recovered Write Parity Error Channel: Unrecovered Write Parity Error Channel: Recovered Buffer Overflow Read Error Channel: Unrecovered Buffer Overflow Read Error Channel: Recovered CTG Wedge Slip Fault Error
HGST Hard Disk Drive Specification 348

F66F 1670 F671 1672 F673 1674 F675 1676 F677 1678 F679 167A F67B 167C F67D 167E F67F 1680 F681 1682 F683 1684 F685 1686 F687 1688 F689 168A F68B 168C F68D 168E F68F 1690 F691 1692 F693 1694 F695 1696 F697 1698 F699 169A F69B 169C F69D 169E F69F

Channel: Unrecovered CTG Wedge Slip Fault Read Error Channel: Recovered CTG Packet Late Fault Error Channel: Unrecovered CTG Packet Late Fault Error Channel: Recovered Baseline Instability Count Late Error Channel: Unrecovered Baseline Instability Count Late Error Channel: Recovered Preamp Count Fault Error Channel: Unrecovered Preamp Count Fault Error Channel: Recovered Pfault Read Error Channel: Unrecovered Pfault Read Error Channel: Recovered Pfault Write Error Channel: Unrecovered Pfault Write Error Channel: Recovered Last Data Fault Error Channel: Unrecovered Last Data Fault Error Channel: Recovered WRPO Fault Error Channel: Unrecovered WRPO Fault Error Channel: Recovered Forced Channel Fault Error Channel: Unrecovered Forced Channel Fault Error Channel: Recovered PLLFloor Error Channel: Unrecovered PLLFloor Error Channel: Recovered Losslock Error Channel: Unrecovered Losslock Error Channel: Recovered VGA Floor Error Channel: Unrecovered VGA Floor Error Channel: Recovered Buffer EVGA Floor Error Channel: Unrecovered Buffer EVGA Floor Error Channel: Recovered TA Detector Error Channel: Unrecovered TA Detector Error Channel: Recovered NPLD Error Channel: Unrecovered NPLD Error Channel: Recovered ZGR Flag Error Channel: Unrecovered ZGR Flag Error Channel: Recovered DPLL Freq Flag Error Channel: Recovered DPLL Freq Flag Error Channel: Recovered Massive Drop Out Detection Error Channel: Unrecovered Massive Drop Out Detection Error Channel: Recovered CTG Parameter Out of Bounds Error Channel: Unrecovered CTG Parameter Out of Bounds Flag Error Channel: Recovered Flaw Signal Sync Error Channel: Unrecovered Flaw Signal Sync Error Channel: Recovered ACQ Flag Error Channel: Unrecovered ACQ Flag Error Channel: Recovered No Clock Error Channel: Unrecovered No Clock Error Channel: Recovered PLL Losslock Error Channel: Unrecovered PLL Losslock Error Channel: Recovered ESNR Timeout Error Channel: Unrecovered ESNR Timeout Error Channel: Recovered ADC Sample Not Ready Error Channel: Unrecovered ADC Sample Not Ready Error
HGST Hard Disk Drive Specification 349

F6A0 F6A1 16A2 F6A3 16A4 F6A5 16A6 F6A7 16A8 F6A9 16AA F6AB 16AC F6AD 16AE F6AF 16B0 F6B1 16B2 F6B3 16B4 F6B5 16B6 F6B7 16B8 F6B9 16BA F6BB 16BC F6BD 16BE F6BF 16C0 F6C1 16C2 F6C3 16C4 F6C5 16C6 F6C7 16C8 F6C9 16CA F6CB 16CC F6CD 16CE F6CF 16D0

AE: Unrecovered Fuse Load Fail Error AE: Unrecovered Configuration Error Channel: Recovered Auto RST NRZ-Clock Error Channel: Unrecovered Auto RST NRZ-Clock Error Channel: Recovered Write CRC Fault Error Channel: Unrecovered Write CRC Fault Error Channel: Recovered Read Synthesizer Loss of Lock Error Channel: Unrecovered Read Synthesizer Loss of Lock Error Channel: Recovered RLL Parameter Error Channel: Unrecovered RLL Parameter Error Channel: Recovered FIFO Underflow Error Channel: Unrecovered FIFO Underflow Error Channel: Recovered FIFO Overflow Error Channel: Unrecovered FIFO Overflow Error Channel: Recovered Iterative Decoder Error Channel: Unrecovered Iterative Decoder Error Channel: Recovered Iterative Read Error Channel: Unrecovered Iterative Read Error Channel: Recovered Encoder Overflow Error Channel: Unrecovered Encoder Overflow Error Channel: Recovered Encoder Underflow Error Channel: Unrecovered Encoder Underflow Error Channel: Recovered Encoder RAM CRC Error Channel: Unrecovered Encoder RAM CRC Error Channel: Recovered Interface Fault Channel: Unrecovered Interface Fault Channel: Recovered QMM EVDump Parse Error Channel: Unrecovered QMM EVDump Parse Error Channel: Recovered DiBit Timeout Error Channel: Unrecovered DiBit Timeout Error Channel: Recovered MXP Write Fault Channel: Unrecovered MXP Write Fault Channel: Recovered Data Jam Error Channel: Unrecovered Data Jam Error Channel: Recovered Code-Word Out Of Order Error Channel: Unrecovered Code-Word Out Of Order Error Channel: Recovered Read RLL Buffer CRC Flag Error Channel: Unrecovered Read RLL Buffer CRC Flag Error Channel: Recovered Write RLL Buffer CRC Flag Error Channel: Unrecovered Write RLL Buffer CRC Flag Error Channel: Recovered CTG No SAM Detected Fault Error Channel: Unrecovered CTG No SAM Detected Fault Error Channel: Recovered ITI Adjust Preload Fault Track Error Channel: Unrecovered ITI Adjust Preload Fault Track Error Channel: Recovered WTG SRV Fault Error Channel: Unrecovered WTG SRV Fault Error Channel: Recovered CTG Engine Not Ready Fault Error Channel: Unrecovered CTG Engine Not Ready Fault Error Channel: Recovered LLI Abort Fault Error
HGST Hard Disk Drive Specification 350

F6D1 16D2 F6D3 16D4 F6D5 16D6 F6D7 16D8 F6D9 F6DA F6DB 16DC F6DD 16DE F6DF 16E0 F6E1 F6E2 F6E3 F6E4 F6E5 F6E6 16E7 F6E8 16E9 F6EA 16EB F6EC 16ED F6EE 16EF F6F0 16F1 F6F2 16F3 F6F4 16F5 F6F6 16F7 F6F8 16F9 F6FA F6FB F6FC F6FD F6FE

Channel: Unrecovered LLI Abort Fault Error Channel: Recovered Retry Fault Error Channel: Unrecovered Retry Fault Error Channel: Recovered WTG Timeout Fault Error Channel: Unrecovered WTG Timeout Fault Error Channel: Recovered ITI Fault TS Transfer All Error Channel: Unrecovered ITI Fault TS Transfer All Error Channel: Recovered ITI Data Fault Error Channel: Unrecovered ITI Data Fault Error Channel: Unrecovered Insufficient TFC Preheat Error Channel: Unrecovered AE And FAEP Do Not Match Channel: Recovered Data Jam Fault Error Channel: Unrecovered Data Jam Fault Error Channel: Recovered Code-Word Out of Order Error Channel: Unrecovered Code-Word Out of Order Error Channel: Recovered RLL Initialization Timeout Error Channel: Unrecovered RLL Initialization Timeout Error Channel: Unrecovered AEQ Timeout Error Channel: Unrecovered AEQ NLD Initialization Error Channel: Unrecovered ADC Calibration Timeout Error Channel: Unrecovered ADC Buffer Calibration Timeout Error Channel: Unrecovered Power Sequencing Timeout Error Channel: Recovered Mode Overlap Write Error Channel: Unrecovered Mode Overlap Write Error Channel: Recovered Ready Fault Error Channel: Unrecovered Ready Fault Error Channel: Recovered Synchronous Abort Done Error Channel: Unrecovered Synchronous Abort Done Error Channel: Recovered NRZ Clear Fault Error Channel: Unrecovered NRZ Clear Fault Error Channel: Recovered Collision Fault Error Channel: Unrecovered Collision Fault Error Channel: Recovered Read Synthesizer Precharge Fail Fault Error Channel: Unrecovered Read Synthesizer Precharge Fail Fault Error Channel: Recovered Servo Synthesizer Precharge Fail Fault Error Channel: Unrecovered Servo Synthesizer Precharge Fail Fault Error Channel: Recovered Read Synthesizer Loss of Lock Error Channel: Unrecovered Read Synthesizer Loss of Lock Error Channel: Recovered Fragment Number Fault Error Channel: Unrecovered Fragment Number Fault Error Channel: Recovered Preamble Quality Monitor Fault Error Channel: Unrecovered Preamble Quality Monitor Fault Error Channel: Unrecovered Stop For RTM Error Channel: Unrecovered RTM Configuration Error Channel: Unrecovered RTM Failure Error Channel: Unrecovered RTM Timeout Error

HGST Hard Disk Drive Specification 351

F701 F702 D703 1704 D705 E706 E707 E708 1709 D70A E70B E70C E70D E70E E70F D710 E711 1712 F713 1714 F715 1716 F717 1718 F719 171C F71D 171E F71F F720 F721 1726 F727 172C F72D 172E F72F F730 1731 F732 1733 F734 1735 F736 1737 F738 1739 F73A 173B

Format corrupted Too many notches Media: Auto Reallocated Write Error Media: Recovered Write Error - Recommend reassign Media: Error With OTF Correction - Reassigned Media: Error With OTF Correction - Recommend Reassign Media: Error With OTF Correction - Recommend Rewrite Media: Error With OTF Correction - Rewritten Media: Recovered Error With Offline Correction Media: Error With Offline Correction - Reassigned Media: Error With Offline Correction - Recommend Reassign Media: Error With Offline Correction - Recommend Rewrite Media: Error With Offline Correction - Rewritten Media: Recovered Data Address Mark Error - Rewritten Media: Recovered Data Address Mark Error - Recommend Rewrite Media: Recovered Data Address Mark Error - Reassigned Media: Recovered Data Address Mark Error - Recommend Reassign Media: Recovered LBA MEDC Error Media: Unrecovered LBA MEDC Error Media: Recovered Sector Overflow Error Media: Unrecovered Sector Overflow Error Media: Recovered Write Overrun Error Media: Unrecovered Write Overrun Error Media: Recovered Sync Mark Retry Timeout Media: Unrecovered Sync Mark Retry Timeout Media: Recovered DRAM CRC Error Media: Unrecovered DRAM CRC Error Media: Recovered Read Latency Error Media: Unrecovered Read Latency Error Media: RC Dump Overflow Error Media: Format Configuration Invalid Media: Recovered Internal Write Catch Error Media: Unrecovered Internal Write Catch Error Media: Recovered Data Media: Unrecovered Uncorrectable Read Data error Media: Recovered Error on Last Data Read Media: Unrecovered Error on Last Data Read Media: Recommend targeted scan Media: Recovered Write Fault Media: Unrecovered Write Fault Media: Recovered Read Write Abort Error Media: Unrecovered Read Write Abort Error Channel: Recovered No Sync Detected Error Channel: Unrecovered No Sync Detected Error Media: Recovered Post Write Abort Error Media: Unrecovered Post Write Abort Media: Recovered Post PES Check Write Abort Error Media: Unrecovered Post PES Check Write Abort Error Media: Recovered Data Address Mark Error
HGST Hard Disk Drive Specification 352

F73C 173D F73E F73F F740 F741 F742 F743 1744 F745 1746 1747 1748 1749 F74A F74B F74C F74D F74E F74F F750 F751 F752 F753 F754 F755 F756 F757 F758 1759 F75A F75B F75C F75D F75E F75F F760 F762 F763 F764 1766 F767 1768 F769 176A F76B 176C F76D 176E

Media: Unrecovered Data Address Mark Error Media: Recovered Sector Miss Error Media: Unrecovered Sector Miss Error Media: NFZ Table Full Media: Defect SID Table Full Error Media: OCT Timeout Not Dispatched Media: OCT Timeout In Recovery Media: OCT Timeout Executing Media: Recovered Sudden Stop Error Media: Unrecovered Sudden Stop Error Media: Recovered Defect List Format Not Supported Error Media: Recovered Primary Defect List Not Found Error Media: Recovered Grown Defect List Not Found Error Media: Recovered Partial Defect List Transferred Error Media: Unrecovered Alternate Track Table Full Error Media: Unrecovered Primary Defect List Error Media: Unrecovered Grown Defect List Error Media: Unrecovered Too Many Heads Error Media: Unrecovered Skew Table Size Error Media: Unrecovered Too Many Zones Error Media: Unrecovered Too Many SIDs Error Media: Unrecovered Alternate Track Table Full Error Media: Unrecovered Drive Capacity Too Small Media: Unrecovered G-list Full (Format command) Media: Unrecovered G-list Full (2) (Format command) Media: Unrecovered Pointer Repeat Size Error Media: Unrecovered DST Slot Size Error Media: Unrecovered P-list Full Error Media: Unrecovered Invalid NFZ Table Error Media: Recovered Unknown Error Media: Unrecovered Unknown Error Media: Unrecovered Too Many Sectors Error Media: Unrecovered Internal Media Access Timeout Error Media: Unrecovered Self-Test Failed Error Media: Unrecovered Maximum Servo Cylinder Number Too Small Error Media: Unrecovered SAT No Buffer Overflow Error Media: Unrecovered SAT Buffer Overflow Error Media: Unrecovered Self-Test Hard-Cache Test Fail Media: Unrecovered Self-Test OTF-Cache Fail Media: Unrecovered Merge G-List Failed - No P-List Exists Channel: Recovered XTS LOAD Timeout Error Channel: Unrecovered XTS LOAD Timeout Error Media: Recovered Key Seed ID Mismatch Error Media: Unrecovered Key Seed ID Mismatch Error Media: Recovered No NRZ Clock Error Media: Unrecovered No NRZ Clock Error Media: Recovered MEDC Correctable Error Media: Unrecovered MEDC Uncorrectable Error Media: Correctable Channel Ready Error
HGST Hard Disk Drive Specification 353

F76F 1770 F771 F772 F773 F774 F775 F776 F777 1778 F779 F77A F77B 177C F77D F77E F77F 1780 F781 1782 F783 1784 F785 1786 F787 178C F78D F78E F78F 1792 F793 1794 F795 F797 1798 F799 179C F79D 17A5 F7A6 F7A7 F7A8 F7A9 17AA F7AB 17AE F7AF F7B0 17B2

Media: Uncorrectable Channel Ready Error Media: Recovered SID Timeout Error Media: Unrecovered SID Timeout Error Media: Unrecovered DASH starting timeout Media: Unrecovered ID table timeout Media: Unrecovered Servo timeout Media: Unrecovered Buffers timeout Media: Unrecovered DASH done timeout Media: Unrecovered DASH unknown timeout Media: Recovered Mini Mode Timeout Media: Unrecovered Mini Mode Timeout Media: BUFCNT Timeout Error Media: Unrecovered Abort EOS fail Media: Recovered Servo Area Timeout Media: Unrecovered Servo Area Timeout Media: Write Error Recovery Timeout Media: Read Error Recovery Timeout Media: Recovered DLC SID Delay Timeout Media: Unrecovered DLC SID Delay Timeout Media: Recovered Force Soft Error Media: Unrecovered Force Soft Error Media: Recovered Channel Sector Marginal Error Media: Unrecovered Channel Sector Marginal Error Media: Recovered LLI Underrun Error Media: Unrecovered LLI Underrun Error Media: Recovered FFSULI Timeout Media: Unrecovered FFSULI Timeout Media: Unrecovered SAT No Buffer Overflow With ECS Fault Media: Unrecovered SAT Buffer Overflow With ECS Fault Media: Recovered MEDC Write Data Not Ready Error Media: Unrecovered MEDC Write Data Not Ready error Media: Recovered DMA Timeout Error Media: Unrecovered DMA Timeout Error Media: SAT Write Abort Media: Recovered ID Not Found Error Media: Unrecovered ID Not Found Error Media: Recovered Channel Read Timeout Error Media: Unrecovered Channel Read Timeout Error Media: Recovered LBA ECC Last Data Read Error Media: Unrecovered LBA ECC Last Data Read Error Media: Unrecovered Committed Write Hard Error Media: Unrecovered Committed Write Correction Disabled Error Media: Unrecovered Committed Write Uncorrectable Error Media: Recovered Read Overrun Error Media: Unrecovered Read Overrun Error Media: Recovered ECC Correctable Error Media: Unrecovered Sector Missing Error Media: Unrecovered Sector Overflow Media: Recovered Abort Window Error
HGST Hard Disk Drive Specification 354

F7B3 17B4 F7B5 17B8 F7B9 17BA F7BB 17BC F7BD 17C0 F7C1 17C2 F7C3 17C4 F7C5 17C6 F7C7 F7CA 17CB F7CC F7CD F7CE F7D0 17D4 F7D5 17D6 F7D7 17D8 F7D9 17DA F7DB 17DC F7DD 17DE F7DF 17E0 F7E1 17E2 F7E3 17E4 F7E5 17E6 F7E7 17E8 F7E9 17EA F7EB 17EC F7ED

Media: Unrecovered Abort Window Error Media: Recovered Shock Sensor Error Media: Unrecovered Shock Sensor Error Media: Recovered Reference Tag Error Media: Unrecovered Reference Tag error Media: Recovered Application Tag Error Media: Unrecovered Application Tag Error Media: Recovered Guard Check Error Media: Unrecovered Guard Check Error Media: Recovered End Sector Check Error Media: Unrecovered End Sector Check Error Media: Recovered Read CRC Error Media: Unrecovered Read CRC Error Media: Recovered DRAM ECC Error Media: Unrecovered DRAM ECC Error Media: Recovered DRAM ECC LBA Error Media: Unrecovered DRAM ECC LBA Error Media: Unrecovered LBA Correction Disabled Error Media: Recovered LBA Write Correctable Error Media: Unrecovered LBA Write Uncorrectable Error Media: Unrecovered LBA Encryption Error Media: Unrecovered Offline Already TAR Error Media: Unrecovered Pre-load Timeout Error Media: Recovered Parity PTR FIFO Error Media: Unrecovered Parity PTR FIFO Error Media: Recovered Parity LBA FIFO Error Media: Unrecovered Parity LBA FIFO Error Media: Recovered Parity Uncorrectable FIFO Error Media: Unrecovered Parity Uncorrectable FIFO Error Media: Recovered Status Uncorrectable FIFO Error Media: Unrecovered Status Uncorrectable FIFO Error Media: Recovered Parity EDC SRAM Error Media: Unrecovered Parity EDC SRAM Error Media: Recovered REQ/ACK Handshake Error Media: Unrecovered REQ/ACK Handshake Error Media: Recovered Write Splice Error Media: Unrecovered Write Splice Error Media: Recovered Read Parity Error Media: Unrecovered Read Parity Error Media: Recovered EPO Error Media: Unrecovered EPO Error Media: Recovered NRZ Sector Marginal Error Media: Unrecovered NRZ Sector Marginal Error Media: Recovered AE Access Inhibit Error Media: Unrecovered AE Access Inhibit Error Media: Recovered PTR FIFO Error Media: Unrecovered PTR FIFO Error Media: Recovered LBA FIFO Error Media: Unrecovered LBA FIFO Error
HGST Hard Disk Drive Specification 355

17EE F7EF 17F0 F7F1 17F2 F7F3 17F4 F7F5 17F6 F7F7 F813 F815 F81E F81F F820 F821 F822 F823 F824 F825 F826 F827 F828 F829 F830 1831 1832 1833 1834 1835 1836 1837 1838 1839 183A 1A02 2A02 3A02 1A03 2A03 3A03 1A04 2A04 3A04 1A05 2A05 3A05 1A14 2A14

Media: Recovered Sector Number Cylinder Error Media: Unrecovered Sector Number Cylinder Error Media: Recovered Read Transfer Length Error Media: Unrecovered Read Transfer Length Error Media: Recovered DS RDC Burst Error Media: Unrecovered DS RDC Burst Error Media: Recovered SV RDC Burst Error Media: Unrecovered SV RDC Burst Error Media: Recovered Channel AE WG Error Media: Unrecovered Channel AE WG Error CMD: Insufficient Buffer Space Error CMD: Aborted From Internal TMF Error CMD: Reassign Not Allowed CMD: Operation in Progress CMD: Unrecovered Parameter List Length Error CMD: Unrecovered Invalid Opcode in CDB Error CMD: Unrecovered LBA Out Of Range Error CMD: Unrecovered Invalid Field In CDB Error CMD: Unrecovered Invalid LUN Error CMD: Unrecovered Invalid Field In Parameter List Error CMD: Unrecovered Unsupported Log Page Error CMD: Unrecovered Access Denied Error CMD: Unrecovered Invalid Release of Persistent Reservation Error CMD: Invalid Tx Setting for Combo Chip Error CMD: Unrecovered Sequence Error CMD: Power Mode Idle_A By Timer CMD: Power Mode Idle_B By Timer CMD: Power Mode Idle_C By Timer CMD: Power Mode Standby_Z By Timer CMD: Power Mode Idle_A By Command CMD: Power Mode Idle_B By Command CMD: Power Mode Idle_C By Command CMD: Power Mode Standby_Z By Command CMD: Power Mode Standby_Y By Timer CMD: Power Mode Standby_Y By Command SMART: Temperature Warning (No Sense) SMART: Temperature Warning (Recovered Sense) SMART: Temperature Warning (Unit Attention) SMART: Background Self-Test Failure (No Sense) SMART: Background Self-Test Failure (Recovered Sense) SMART: Background Self-Test Failure (Unit Attention) SMART: Background Pre-Scan Failure (No Sense) SMART: Background Pre-Scan Failure (Recovered Sense) SMART: Background Pre-Scan Failure (Unit Attention) SMART: Background Media Scan Failure (No Sense) SMART: Background Media Scan Failure (Recovered Sense) SMART: Background Media Scan Failure (Unit Attention) SMART: Spare Sector Availability Warning (No Sense) SMART: Spare Sector Availability Warning (Recovered Sense)
HGST Hard Disk Drive Specification 356

3A14 1A21 2A21 3A21 1A22 2A22 3A22 1A32 2A32 3A32 1A43 2A43 3A43 1A4A 2A4A 3A4A 1A50 2A50 3A50 1A56 2A56 3A56 1A5B 2A5B 3A5B FA81 2A83 1A85 2A85 4A85 FA85 1AFF 2AFF 3AFF

SMART: Spare Sector Availability Warning (Unit Attention) SMART: Milli-Actuator Error (No Sense) SMART: Milli-Actuator Error (Recovered Sense) SMART: Milli-Actuator Error (Unit Attention) SMART: Extreme Over-Temperature Warning (No Sense) SMART: Extreme Over-Temperature Warning (Recovered Sense) SMART: Extreme Over-Temperature Warning (Unit Attention) SMART: Read Error Rate Warning (No Sense) SMART: Read Error Rate Warning (Recovered Sense) SMART: Read Error Rate Warning (Unit Attention) SMART: Seek Error Rate Warning (No Sense) SMART: Seek Error Rate Warning (Recovered Sense) SMART: Seek Error Rate Warning (Unit Attention) SMART: Write Error Rate Warning (No Sense) SMART: Write Error Rate Warning (Recovered Sense) SMART: Write Error Rate Warning (Unit Attention) SMART: Load/Unload Cycle Count Warning (No Sense) SMART: Load/Unload Cycle Count Warning (Recovered Sense) SMART: Load/Unload Cycle Count Warning (Unit Attention) SMART: Spinup Time Warning (No Sense) SMART: Spinup Time Warning (Recovered Sense) SMART: Spinup Time Warning (Unit Attention) SMART: Spinup Retry Count Warning (No Sense) SMART: Spinup Retry Count Warning (Recovered Sense) SMART: Spinup Retry Count Warning (Unit Attention) Self-Test: Unrecoverable Error Count Threshold Exceeded Self-Test: GLIST Error Count Threshold Reached Self-Test: Recovery Error Self-Test: Servo Error Self-Test: Command Timeout Error Self-Test: Unrecoverable Error SMART: Test Warning Threshold Reached (No Sense) SMART: Test Warning Threshold Reached (Recovered Sense) SMART: Test Warning Threshold Reached (Unit Attention)

FCxx Media: Unrecovered Unable to Read RID or FID Number xx

1ECE FECF 1ED0 FED1 1ED2 FED3 1ED4 FED5 1ED6 FED7 1ED8 FED9

Media: Recovered R/W Abort Due to Vibration Condition (Other) Media: Unrecovered R/W Abort Due to Vibration Condition (Other) Media: Recovered R/W Abort Due to Vibration Condition (Estimator) Media: Unrecovered R/W Abort Due to Vibration Condition (Estimator) Media: Recovered R/W Abort Due to Vibration Condition (Predictor) Media: Unrecovered R/W Abort Due to Vibration Condition (Predictor) Media: Recovered R/W Abort Due to Vibration Condition (PES Error) Media: Unrecovered R/W Abort Due to Vibration Condition (PES Error) Media: Recovered R/W Abort Off Track Write Error Media: Unrecovered R/W Abort Off Track Write Error Media: Recovered R/W Abort RRO Field Misread Error Media: Unrecovered R/W Abort RRO Field Misread Error
HGST Hard Disk Drive Specification 357

1EDA
FEDB
1EDC
FEDD
1EDE
FEDF
1EE0
FEE1
1EE2
FEE3
1EE4
FEE5
1EE6
FEE7 1EE8 FEE9 1EEA FEEB 1EEC FEED 1EEE FEEF 1EF0 FEF1 1EF2 FEF3 1EF4 FEF5 1EF6 FEF7 1EF8 FEF9 1EFA FEFB 1EFC FEFD 1EFE FEFF FF01 FF02 FF03 FF04 FF05 FF06 FF07 FF08 FF09 FF0A FF0B FF0C FF0D FF0E FF0F FF10 FF11

Media: Recovered R/W Abort RRO Field Missing Error
Media: Unrecovered R/W Abort RRO Field Missing Error
Media: Recovered R/W Abort Idle Seek Error
Media: Unrecovered R/W Abort Idle Seek Error
Media: Recovered R/W Abort Seek Timeout Error
Media: Unrecovered R/W Abort Seek Timeout Error
Media: Recovered R/W Abort Estimator Error
Media: Unrecovered R/W Abort Estimator Error
Media: Recovered R/W Abort Predictor Error
Media: Unrecovered R/W Abort Predictor Error
Media: Recovered R/W Abort PES Error
Media: Unrecovered R/W Abort PES Error
Media: Recovered R/W Abort Seek Start Error
Media: Unrecovered R/W Abort Seek Start Error Media: Recovered R/W Abort PES Reset Error Media: Unrecovered R/W Abort PES Reset Error Media: Recovered R/W Abort SID Unlock Error Media: Unrecovered R/W Abort SID Unlock Error Media: Recovered R/W Abort WCS Error Media: Unrecovered R/W Abort WCS Error Media: Recovered R/W Abort Hard Reset Error Media: Unrecovered R/W Abort Hard Reset Error Media: Recovered R/W Abort Shock Error Media: Unrecovered R/W Abort Shock Error Media: Recovered R/W Abort Unlock Macro Error Media: Unrecovered R/W Abort Unlock Macro Error Media: Recovered R/W Abort Sharp Error Media: Unrecovered R/W Abort Sharp Error Media: Recovered R/W Abort Aggressive Error Media: Unrecovered R/W Abort Aggressive Error Media: Recovered R/W Abort SVGA Limit Error Media: Unrecovered R/W Abort SVGA Limit Error Media: Recovered R/W Abort Gray Code Error Media: Unrecovered R/W Abort Gray Code Error Media: Recovered R/W Abort Burst Error Media: Unrecovered R/W Abort Burst Error Media: Recovered R/W Abort No STM Error Media: Unrecovered R/W Abort No STM Error IndSys: Drive Not Loaded IndSys: Drive Not Loaded - Format Invalid IndSys: Indirection System Not Online IndSys: Drive Not Loaded - Old Version Mismatch IndSys: Drive Not Loaded - Heap Pointer Mismatch IndSys: Drive Not Loaded - Heap size Mismatch IndSys: Drive Not Loaded - Rid Heap Size Mismatch IndSys: Drive Not Loaded - Heap Version Mismatch IndSys: Drive Not Loaded - Incompatible Rid IndSys: Drive Not Loaded - Corrupt Rid IndSys: Drive Not Loaded - Rid Num Objects Mismatch IndSys: Drive Not Loaded - Rid Version Mismatch IndMgr: Drive Not Loaded - Rid Version Mismatch IndSys: Drive Not Loaded - Layout Rid Version Mismatch IndSys: Drive Not Loaded - W2C Rid Version Mismatch IndSys: Drive Not Loaded - Layout Manager Restore Failed IndSys: Drive Not Loaded - W2C Manager Restore Failed
HGST Hard Disk Drive Specification 358

FF12 FF13 FF14 FF15 FF16 FF17 FF18 FF19 FF1A FF1B FF1C FF1D FF1E FF1F FF20 FF21 FF22 1F40 FF41 1F42 FF43 FF44 FF50 FF51 FF52 FF53 FF54 FF55 FF60 FF61 FF62 FF63

IndSys: Drive Not Loaded - Layout Failed IndSys: Drive Not Loaded - DMM Format Failed IndSys: Drive Not Loaded - IM Format Failed IndSys: Drive Not Loaded - Pseudo Write Failed IndSys: Drive Not Loaded - Full drop Failed IndSys: Drive Not Loaded - EPO Format Failed IndSys: Drive Not Loaded - Set IM Valid Failed IndSys: Drive Not Loaded - Bring Online failed IndSys: Drive Not Loaded - Metadata First Primary IndSys: Drive Loaded - Metadata First Primary and Secondary IndSys: Drive Loaded - IBA Out of Range IndSys: Drive Loaded - Context Load Failed IndSys: Drive Loaded - Context Sequence ID Mismatch IndSys: Drive Loaded - Replay EPO Spec Failed IndSys: Drive Not Loaded - EPD Flash Entry Invalid LayoutMgr: All Flash Entries Erased IndSys: Drive Loaded - Replay Failed IndSys: LOM Generic Fail LayoutMgr: Format Capacity Not Met DlMgr: DLMGR Generic Fail IndSys: Drive Not Loaded - Metadata ATI IndSys: Drive Loaded - Replay Fail IndMgr: IM Demand Split Too Deep Failure IndMgr: Allocate Failed Delta Group IndMgr: Allocate Failed Split Spec IndMgr: Allocate Failed Split Delta IndMgr: Allocate Failed Unsplit Delta Group IndMgr: Generic Insert Exception Failed EpoMgr: Flash Read RS Syndrome Gen Timeout EpoMgr: Uncorrectable Flash RS ECC Error EpoMgr: Correctable EPO Timeout EpoMgr: ARM FPS Engine and Not Spinning

HGST Hard Disk Drive Specification 359
Microsoft Word 2013