Ultrastar 15K147 (SAS) Specification v1.5
Hard Disk Drive Specification
Ultrastar 15K147 (SAS)
3.5 inch Serial Attached SCSI Hard Disk Drive
Models:
Version 1.5
HUS151414VLS300
HUS151473VLS300
HUS151436VLS300
01 November 2006
Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal of downlevel versions is the responsibility of the document holder.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Hard Disk Drive Specification
Ultrastar 15K147 (SAS)
3.5 inch Serial Attached SCSI Hard Disk
Drive
Models:
HUS151414VLS300
HUS151473VLS300
HUS151436VLS300
Version 1.5
01 November 2006
Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal
of down-level versions is the responsibility of the document holder.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
1st Edition (Rev. 0.1) (1 December 2004) DRAFT
2nd Edition (Rev. 0.2) (4 February 2005) DRAFT
3rd Edition (Rev. 0.3) (01 April 2005) DRAFT
4th Edition (Rev. 0.4) (16 May 2005) DRAFT
5th Edition (Rev. 1.0) (06 June 2005) Revised
6th Edition (Rev. 1.1)(25 August 2005) Revised
7th Edition (Rev. 1.2)(14 September 2005) Revised
8th Edition (Rev 1.3)(16 September 2005) Revised
9th Edition (Rev 1.4)(07 March 2006) Revised
10th Edition (Rev 1.5)(01 November 2006) Final
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent
with local law: HITACHI GLOBAL STORAGE TECHNOLOGIES PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer or express or implied warranties in certain transactions, therefore, this statement
may not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Hitachi may make improvements or changes
in any products or programs described in this publication at any time.
It is possible that this publication may contain reference to, or information about, Hitachi products (machines and programs),
programming, or services that are not announced in your country. Such references or information must not be construed to
mean that Hitachi intends to announce such Hitachi products, programming, or services in your country.
Technical information about this product is available by contacting your local Hitachi Global Storage Technologies representative or on the Internet at http://www.hgst.com
Hitachi Global Storage Technologies may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents.
©Copyright Hitachi Global Storage Technologies
Note to U.S. Government Users —Documentation related to restricted rights —Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with Hitachi Global Storage Technologies.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Table of Contents
1.0 General....................................................................................................1
1.1 Introduction........................................................................................1
1.2 Glossary .............................................................................................1
1.3 Caution...............................................................................................1
2.0 Outline of the Drive ...............................................................................3
3.0 Fixed-disk Subsystem Description .......................................................5
3.1 Control Electronics ............................................................................5
3.2 Head Disk Assembly .........................................................................5
3.3 Actuator .............................................................................................5
4.0 Drive Characteristics .............................................................................7
4.1 Formatted Capacity............................................................................7
4.2 Data Sheet ..........................................................................................7
4.3 Inquiry Information............................................................................7
4.3.1 Product ID.................................................................................7
4.3.2 World Wide ID - Block Assignment ........................................8
4.4 Cylinder allocation.............................................................................9
4.5 Performance characteristics ...............................................................10
4.5.1 Mechanical positioning.............................................................11
4.5.2 Drive ready time .......................................................................13
4.5.3 Spindle stop time ......................................................................13
4.5.4 Data transfer speed....................................................................13
4.5.5 Buffering operation (read ahead/write cache)...........................14
4.5.6 Throughput................................................................................14
5.0 Data Integrity .........................................................................................17
5.1 Equipment Status ...............................................................................17
5.2 Error Recovery Procedure..................................................................17
6.0 Physical Format .....................................................................................19
6.1 Shipped Format (P-List) ....................................................................19
6.2 Reassigned Format (G-List)...............................................................19
7.0 Environment...........................................................................................21
7.1 Temperature and humidity.................................................................21
7.2 Storage requirements .........................................................................22
7.2.1 Packaging..................................................................................22
7.2.2 Storage time ..............................................................................22
7.3 Corrosion test .....................................................................................22
7.4 Cooling requirements.........................................................................23
8.0 Electrical Interface.................................................................................25
8.1 SAS Connector ..................................................................................25
8.1.1 29 pin Serial Attached SCSI (SAS) Connector Definition .......25
8.1.2 Voltage and Ground Signals .....................................................26
9.0 DC Power Requirements.......................................................................27
9.1 Power Supply Current, Average and Peak.........................................28
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
9.2 Ripple Voltage ...................................................................................29
9.3 Power Consumption Efficiency Index ...............................................29
10.0 Reliability..............................................................................................31
10.1 Start/Stop Cycles..............................................................................31
10.2 Data Reliability ................................................................................31
10.3 Seek errors .......................................................................................31
10.4 Failure prediction (PFA/S.M.A.R.T) ...............................................31
10.5 Preventive Maintenance...................................................................31
10.6 Temperature Warning ......................................................................31
11.0 Mechanical Specifications ...................................................................33
11.1 Outline .............................................................................................33
11.2 Mechanical Dimensions...................................................................33
11.3 Interface Connector..........................................................................35
11.4 Mounting Positions and Tappings ...................................................35
11.5 Drive Mounting................................................................................36
11.6 Heads Unload and Actuator Lock....................................................36
11.7 Breather Hole ...................................................................................36
12.0 Vibration and Shock ............................................................................39
12.1 Operating Vibration .........................................................................39
12.1.1 Random Vibration...................................................................39
12.1.2 Swept Sine Vibration .............................................................39
12.2 Non-operating Vibrations ................................................................39
12.2.1 Random Vibration..................................................................39
12.2.2 Swept Sine Vibration .............................................................39
12.3 Operating shock ..............................................................................39
12.4 Non-operating shock.......................................................................40
12.4.1 Half sinewave shock pulse......................................................40
12.4.2 Rotational shock ....................................................................40
13.0 Acoustics ...............................................................................................41
13.1 Sound power levels ..........................................................................41
14.0 Identification ........................................................................................43
14.1 Labels...............................................................................................43
15.0 Electromagnetic Compatibility...........................................................45
16.0 Standards ..............................................................................................47
16.1 UL and C-UL Standard Conformity ................................................47
16.2 European Standards Compliance .....................................................47
16.3 German Safety Mark........................................................................47
16.4 Flammability ....................................................................................47
16.5 Corporate Standards Compliance ....................................................47
17.0 SAS Attachment ...................................................................................49
17.1 General.............................................................................................49
17.2 SAS Features....................................................................................49
17.3 SAS Names and Identifiers..............................................................50
17.4 Spin up .............................................................................................51
17.5 PHY Layer .......................................................................................52
17.5.1 Link Reset Sequence...............................................................52
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
17.5.2 Hard Reset...............................................................................53
17.5.3 SAS OOB (Out of Band) ........................................................53
17.5.4 SAS Speed Negotiation ..........................................................54
17.5.5 PHY Error Handling ...............................................................54
17.6 Link Layer........................................................................................54
17.6.1 Address Frames.......................................................................54
17.6.2 Link Layer Error Handling .....................................................56
17.7 Transport Layer................................................................................59
17.7.1 Command Information Unit....................................................60
17.7.2 TASK Information Units ........................................................61
17.7.3 XFER_RDY Information Units ..............................................62
17.7.4 DATA Information Units........................................................62
17.7.5 RESPONSE Information Units...............................................62
17.7.6 Sequences of SSP Information Units......................................63
17.7.7 Transport Layer Error Handling .............................................64
18.0 SCSI Command Set .............................................................................67
18.1 SCSI Control Byte ...........................................................................69
18.2 Abbreviations...................................................................................69
18.3 Byte ordering conventions ...............................................................69
18.4 FORMAT UNIT (04).......................................................................70
18.4.1 Defect list ................................................................................72
18.4.2 Defect Descriptor ....................................................................73
18.5 INQUIRY (12) .................................................................................76
18.5.1 Inquiry Data ............................................................................77
18.6 LOG SELECT (4C) .........................................................................89
18.7 LOG SENSE (4D) ...........................................................................92
18.7.1 Log Page parameters...............................................................93
18.7.2 Log Sense Page 0 ....................................................................94
18.7.3 Log Sense Page 2 ....................................................................95
18.7.4 Log Sense Page 3 ....................................................................97
18.7.5 Log Sense Page 5 ....................................................................99
18.7.6 Log Sense Page 6 ....................................................................101
18.7.7 Log Sense Page D ...................................................................102
18.7.8 Log Sense Page E ...................................................................103
18.7.9 Log Sense Page F....................................................................104
18.7.10 Log Sense Page 10 ................................................................105
18.7.11 Log Sense Page 15 ................................................................108
18.7.12 Log Sense Page 18 ................................................................110
18.7.13 Log Sense Page 2F................................................................112
18.7.14 Log Sense Page 30 ................................................................113
18.7.15 Log Sense Page 37 ................................................................116
18.8 MODE SELECT (15) ......................................................................118
18.9 MODE SELECT (55) ......................................................................119
18.10 MODE SENSE (1A) ......................................................................120
18.10.1 Mode Parameter List.............................................................121
18.10.2 Mode Page 00 (Vendor Unique Parameters) ........................125
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
18.10.3 ............................................................................................Mode Page 01 (Read/Write
Error Recovery Parameters)...........................................................................127
18.10.4 Mode Page 02 (Disconnect/Reconnect Parameters) .............132
18.10.5 Mode Page 03 (Format Device Parameters) .........................133
18.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters) ....135
18.10.7 Mode Page 07 (Verify Error Recovery Parameters).............136
18.10.8 Mode Page 08 (Caching Parameters)....................................137
18.10.9 Mode Page 0A (Control Mode Page Parameters).................140
18.10.10 Mode Page 0C (Notch Parameters) ....................................142
18.10.11 Mode Page 18h ...................................................................(SAS only)144
18.10.12 Mode Page 19h (Port Control Parameters) .........................145
18.10.13 Mode Page 1A (Power Control) .........................................149
18.10.14 Mode Page 1C (Informational Exceptions Control) ...........150
18.11 MODE SENSE (5A) ......................................................................153
18.12 PERSISTENT RESERVE IN (5E) ................................................155
18.12.1 Service Action.......................................................................155
18.12.2 Parameter data for Read Keys ..............................................156
18.12.3 Parameter Data for Read Reservations .................................157
18.13 PERSISTENT RESERVE OUT (5F) ............................................158
18.13.1 Service Action.......................................................................159
18.13.2 Type ......................................................................................159
18.13.3 Parameter list ........................................................................160
18.13.4 Summary ...............................................................................161
18.14 PRE-FETCH (34) ..........................................................................163
18.15 READ (6) - (08) .............................................................................164
18.16 READ (10) - (28) ...........................................................................165
18.17 READ BUFFER (3C) ....................................................................166
18.17.1 Combined Header And Data (Mode 00000b).......................167
18.17.2 Read Data (Mode 00010b)....................................................167
18.17.3 Descriptor (Mode 00011b)....................................................168
18.17.4 Read Data from Echo Buffer (Mode 01010b) ......................169
18.17.5 Echo Buffer Descriptor (Mode 01011b) ...............................169
18.17.6 Expander Communications and Echo Buffer (Mode 11010b)169
18.18 READ CAPACITY (10) - (25) ......................................................170
18.19 READ CAPACITY (16) (9E/10)...................................................172
18.20 READ DEFECT DATA (37).........................................................173
18.20.1 Defect List Header ................................................................175
18.20.2 Defect List Descriptor...........................................................175
18.20.3 Bytes from Index Format (100b) ..........................................176
18.20.4 Physical Sector Format (101b) .............................................176
18.21 READ DEFECT DATA (B7) ........................................................177
18.21.1 Defect List Header ................................................................177
18.21.2 Defect List Descriptor...........................................................178
18.21.3 Bytes from Index Format (100b) ..........................................178
18.21.4 Physical Sector Format (101b) .............................................178
18.22 READ LONG (3E) ........................................................................179
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
18.23 REASSIGN BLOCKS (07) ...........................................................180
18.24 RECEIVE DIAGNOSTICS RESULTS (1C) ................................182
18.24.1 Receive Diagnostic Results Page 0.......................................183
18.24.2 Receive Diagnostic Results Page 40.....................................184
18.25 RELEASE (17) ..............................................................................186
18.26 RELEASE (57) ..............................................................................187
18.27 REPORT DEVICE IDENTIFIER (A3/0C) ...................................188
18.27.1 All_commands parameter data format..................................189
18.27.2 One_command parameter data format..................................190
18.28 REPORT LUNS (A0) ....................................................................191
18.29 REPORT SUPPORTED TASKS MANAGEMENT FUNCTIONS (A3/0D)192
18.30 REQUEST SENSE (03).................................................................193
18.31 RESERVE (16) ..............................................................................194
18.32 RESERVE (56) ..............................................................................195
18.33 REZERO UNIT (01)......................................................................196
18.34 SEEK (6) - (0B) .............................................................................197
18.35 SEEK (10) - (2B) ...........................................................................197
18.36 SEND DIAGNOSTIC (1D) ...........................................................198
18.36.1 Send Diagnostic Page 0 ........................................................200
18.36.2 Send Diagnostic Page 3F ......................................................200
18.36.3 Send Diagnostic Page 40 ......................................................201
18.37 SET DEVICE IDENTIFIER (A4/06) ............................................203
18.38 START STOP UNIT (1B) .............................................................204
18.39 SYNCHRONIZE CACHE (35) .....................................................205
18.40 TEST UNIT READY (00) .............................................................206
18.41 VERIFY (2F) .................................................................................207
18.42 VERIFY (16) - (8F) .......................................................................208
18.43 WRITE (6) - (0A) ..........................................................................209
18.44 WRITE (10) - (2A) ........................................................................210
18.45 WRITE AND VERIFY (10) - (2E)................................................211
18.46 WRITE AND VERIFY (12) - (AE)...............................................212
18.47 WRITE AND VERIFY (16) - (8E)................................................213
18.48 WRITE BUFFER (3B) ..................................................................214
18.48.1 Combined Header And Data (Mode 00000b).......................214
18.48.2 Write Data (Mode 00010b)...................................................215
18.48.3 Download Microcode (Mode 00100b) .................................216
18.48.4 Download Microcode and Save (Mode 00101b) -Single Binary File216
18.48.5 Download Microprocessor Microcode and Save (Mode 00111b) - Multiple Binary Files
216
18.48.6 Write Data to Echo Buffer (Mode 01010b) ..........................217
18.48.7 Enable Expander Communications Protocol (Mode 11010b)217
18.49 WRITE LONG (3F).......................................................................218
18.50 WRITE SAME (41) .......................................................................219
18.51 WRITE SAME (16) - (93) .............................................................220
19.0 SCSI Status Byte ..................................................................................221
20.0 Additional information........................................................................223
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
20.1 SCSI Protocol ..................................................................................223
20.1.1 Priority of SCSI Status Byte Reporting ..................................223
20.1.2 Invalid LUN Processing..........................................................223
20.1.3 Overlapped Commands...........................................................224
20.1.4 Command Processing During Execution of Active I/O Process224
20.1.5 Unit Attention Condition ........................................................225
20.1.6 Command Processing During Startup and Format Operations227
20.1.7 Internal Error Condition..........................................................227
20.1.8 Deferred Error Condition........................................................227
20.1.9 Degraded Mode.......................................................................228
20.1.10 Command Processing while Reserved..................................235
20.2 Priority Commands ..........................................................................235
20.3 Command Queuing ..........................................................................236
20.3.1 Queue Depth ...........................................................................236
20.3.2 Queue Full Status....................................................................236
20.3.3 Termination of I/O Processes .................................................236
20.4 Command Reordering......................................................................236
20.5 Concurrent I/O Process ....................................................................236
20.6 Write Cache .....................................................................................236
20.7 Automatic Rewrite/Reallocate .........................................................237
20.8 Segmented Caching .........................................................................239
20.8.1 Overview.................................................................................239
20.8.2 Read Ahead.............................................................................239
20.9 Multiple Initiator Systems ...............................................................239
20.9.1 Sense Data...............................................................................239
20.9.2 Mode Pages.............................................................................239
20.10 Multiple Initiator Environment ......................................................239
20.10.1 Initiator Sense Data...............................................................239
20.10.2 Initiator Mode Select/Mode Sense Parameters .....................239
20.11 Reset...............................................................................................240
20.11.1 Reset Sources ........................................................................240
20.11.2 Reset Actions ........................................................................240
20.12 Diagnostics.....................................................................................240
20.12.1 Power on Diagnostics ...........................................................240
20.12.2 Self-test via SEND DIAGNOSTIC Command.....................241
20.13 Idle Time Function.........................................................................244
20.14 Command Time out Limits ...........................................................244
20.14.1 Reassignment Time...............................................................244
20.14.2 Format Time .........................................................................244
20.14.3 Unit Start/Stop Time .............................................................244
20.14.4 Medium Access Command Time .........................................245
20.14.5 Time-out Limits for Other Commands .................................245
20.15 Recommended Initiator ERP .........................................................246
20.15.1 Drive Service Strategy ..........................................................246
20.15.2 Recommendations for System Error Log .............................247
20.15.3 Data Recovery Procedure .....................................................247
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
20.15.4 Nondata Error Recovery Procedure ......................................249
21.0 SCSI Sense Data...................................................................................257
21.1 SCSI Sense Data Format..................................................................257
21.2 Sense Data Description ....................................................................258
21.2.1 Valid (Bit 7 of byte 0).............................................................258
21.2.2 Error Code (Bit 6 - 0 of byte 0) ..............................................258
21.2.3 ILI: Incorrect Length Indicator (Bit 5 of byte 2) ....................258
21.2.4 Sense Key (Bit 3 - 0 of byte 2) ...............................................259
21.2.5 Information Bytes (Byte 3 through 6).....................................260
21.2.6 Additional Sense Length (Byte 7) ..........................................260
21.2.7 Command Specific Information (Byte 8 through 11) .............260
21.2.8 Additional Sense Code/Qualifier (Byte 12 and 13) ................261
21.2.9 RU: Field Replaceable Unit (Byte 14)...................................275
21.2.10 Sense Key Specific (Byte 15 through 17).............................275
21.2.11 Reserved (Byte 18 through 19) .............................................278
21.2.12 Vendor unique error information (Byte 20 through 23) .......278
21.2.13 Physical Error Record (Byte 24 thru 29) ..............................278
21.2.14 Reserved (Byte 30 through 31) .............................................278
22.0 Appendix. UEC list .............................................................................279
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
List of Tables
Table 1. ......................................................................................................................Product ID table...........................................................................................................................................1
Table 2.Formatted Capacity.......................................................................................7
Table 3.Data Sheet .....................................................................................................7
Table 4.Product ID in Inquiry Command ..................................................................7
Table 5.Block assignment of World Wide ID in INQUIRY Command....................8
Table 6.Cylinder allocation........................................................................................9
Table 7.Mechanical positioning performance ...........................................................11
Table 8.Full stroke seek time .....................................................................................12
Table 9.Latency time .................................................................................................12
Table 10.Drive ready time .........................................................................................13
Table 11.Spindle stop time ........................................................................................13
Table 12.Data transfer speed (sector size 512 Byte case)..........................................13
Table 13.Simple sequential access performance (sector size 512 Byte case)............14
Table 14.Random access performance (sector size 512 Byte case)...........................15
Table 15.Operating and non-operating conditions ....................................................21
Table 16.Maximum allowable module surface temperatures ....................................23
Table 17.29-pin Connector Signal Definition............................................................25
Table 18.Input Voltage ..............................................................................................27
Table 19.Power Supply Current of 146, 73, 36 GB Model .......................................28
Table 20.Power Supply Generated Ripple at Drive Power Connector......................29
Table 21.Power Consumption Efficiency Index........................................................29
Table 22.Physical Dimensions...................................................................................33
Table 23.A-weighted sound power levels..................................................................41
Table 24.IEEE Registered Name format ...................................................................51
Table 25.Address Frame Format ...............................................................................55
Table 26.Identify Address Frame ..............................................................................55
Table 27.SAS Frame Format .....................................................................................59
Table 28.COMMAND Information Unit...................................................................60
Table 29.TASK Information Unit..............................................................................61
Table 30.XFER_RDY Information Unit ...................................................................62
Table 31.DATA Information Unit .............................................................................62
Table 32.Response Information Unit.........................................................................62
Table 33.RESPONSE DATA ....................................................................................63
Table 34.SCSI Commands Supported .......................................................................67
Table 35.SCSI Control Byte ......................................................................................69
Table 36.FORMAT UNIT (04) .................................................................................70
Table 37.Format of Defect List Header .....................................................................72
Table 38.Defect Descriptor - Block Format (for n + 1 defects) ................................73
Table 39.Defect Descriptor - Bytes From Index Format (for n = 1 defects) .............74
Table 40.Defect Descriptor - Physical Sector Format (for n + 1 defects) .................75
Table 41.INQUIRY (12)............................................................................................76
Table 42.Page Code descriptions...............................................................................76
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Table 43.Inquiry Data - EVPD = 0 ............................................................................77
Table 44.Inquiry Data - EVPD = 1 (Page Code = 00h).............................................79
Table 45.Inquiry Data - EVPD = 1 (Page Code = 03h).............................................80
Table 46.Inquiry Data - EVPD = 1 (Page Code = 80h).............................................82
Table 47. ....................................................................................................................Inquiry Data EVPD = 1 (Page Code = 83h)................................................................................................83
Table 48.Inquiry Data Format - EVPD = 1, Page Code - 86h ...................................84
Table 49.Inquiry Data Format - EVPD = 1, Page Code - 87h ...................................85
Table 50.Inquiry Data Format - EVPD = 1, Page Code - 88h ...................................86
Table 51.Inquiry Data - EVPD = 1 (Page Code = D1h) ............................................87
Table 52.Inquiry Data - EVPD = 1 (Page Code = D2h) ............................................88
Table 53.Log Select (4C)...........................................................................................89
Table 54.Log Sense (4D) ...........................................................................................92
Table 55.Log Sense Page 0........................................................................................94
Table 56.Log Sense Page 2 (part 1 of 2)....................................................................95
Table 57.Log Sense Page 2 (part 2 of 2)....................................................................96
Table 58.Log Sense Page 3 (part 1 of 2)....................................................................97
Table 59.Log Sense Page 3 (part 2 of 2)....................................................................98
Table 60.Log Sense Page 5 (part 1 of 2)....................................................................99
Table 61.Log Sense Page 5 (part 2 of 2)....................................................................99
Table 62.Log Sense Page 6........................................................................................101
Table 63.Log Sense Page D .......................................................................................102
Table 64.Log Sense Page E .......................................................................................103
Table 65.Log Sense Page F........................................................................................104
Table 66.Log Sense Page F, Application Client Log ................................................104
Table 67.Log Sense Page 10......................................................................................105
Table 68.Log Sense Page 10, self-test results............................................................105
Table 69.Log Sense Page 10, self-test results............................................................106
Table 70.Log Sense Page 10, Extended Segment Number........................................106
Table 71.Log Sense Page 15......................................................................................108
Table 72.Log Sense Page 18......................................................................................110
Table 73.SAS Log Descriptor....................................................................................110
Table 74. Log Sense Page 2F.....................................................................................112
Table 75.Log Sense Page 30......................................................................................113
Table 76.Log Sense Page 37......................................................................................116
Table 77.Mode Select (15).........................................................................................118
Table 78.Mode Select (55).........................................................................................119
Table 79.Mode Sense (1A) ........................................................................................120
Table 80.Page Code Usage ........................................................................................121
Table 81.Mode parameter header (6).........................................................................122
Table 82.Mode parameter header (10).......................................................................122
Table 83.Mode Parameter Block Descriptor .............................................................123
Table 84.Mode Parameter Page Format ....................................................................124
Table 85.Mode Parameter Page Format ....................................................................124
Table 86.Vendor Unique Parameters - Page 00.........................................................125
Table 87.Mode Page 01 (Vendor Unique Parameters) ..............................................127
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Table 88.Mode Page 02 (Disconnect/Reconnect Parameters)...................................132
Table 89.Mode Page 03 (Format Device Parameters) ...............................................133
Table 90.Mode Page 04 (Rigid Disk Drive Geometry Parameters) ..........................135
Table 91.Mode Page 07 (Verify Error Recovery Parameters)...................................136
Table 92.Page 08 (Caching Parameters)....................................................................137
Table 93.Page 0A (Control Mode Page Parameters) .................................................140
Table 94.Page 0C (Notch Parameters).......................................................................142
Table 95.Page 18h (Protocol-Specific Logical Unit mode page) ..............................144
Table 96.Short (Port Control Parameters) Short Format ..........................................145
Table 97.Long Format of Port Control Page .............................................................146
Table 98.PHY Control and Discover (Subpage 1) ....................................................147
Table 99.SAS PHY Mode Descriptor........................................................................148
Table 100.Page 1A (Power Control)..........................................................................149
Table 101.Page 1C (Informational Exceptions Control) ...........................................150
Table 102.Background Control (Subpage 01h) .........................................................152
Table 103.Mode Sense (5A) ......................................................................................153
Table 104.Persistent Reserve In (5E) ........................................................................155
Table 105.PERSISTENT RESERVE IN, Service Action Codes ..............................155
Table 106.PERSISTENT RESERVE IN, parameter data for Read Keys .................156
Table 107.PERSISTENT RESERVE IN, parameter data for Read Reservations.....157
Table 108.PERSISTENT RESERVE IN, Read Reservation Descriptor...................157
Table 109.PERSISTENT RESERVE OUT (5F) .......................................................158
Table 110.PERSISTENT RESERVE OUT, Service Action Code............................159
Table 111.PERSISTENT RESERVE OUT, Type Code ...........................................159
Table 112.Parameter List ...........................................................................................160
Table 113.PERSISTENT RESERVE OUT, Service Action, Parameters .................161
Table 114.APTPL and information held by a drive...................................................162
Table 115.PRE-FETCH (34) .....................................................................................163
Table 116.READ (6) - (08)........................................................................................164
Table 117.READ (10) - (28) .....................................................................................165
Table 118.READ BUFFER (3C) ...............................................................................166
Table 119.Read Buffer Header ..................................................................................167
Table 120.Read Buffer Description ...........................................................................168
Table 121.Echo Buffer Descriptor.............................................................................169
Table 122.READ CAPACITY (10) - (25).................................................................170
Table 123.Format of READ CAPACITY command reply........................................171
Table 124.Read Capcity (16) (9E/10)........................................................................172
Table 125.READ DEFECT DATA (37)....................................................................173
Table 126.Defect List Format ....................................................................................174
Table 127.Defect List Header ....................................................................................175
Table 128.Defect List Descriptor...............................................................................175
Table 129.Defect Descriptors of Bytes from Index Format ......................................176
Table 130.Defect Descriptors of Physical Sector Format..........................................176
Table 131.READ DEFECT DATA (B7) ...................................................................177
Table 132.Defect List Header ....................................................................................177
Table 133.Defect List Descriptor...............................................................................178
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Table 134.Defect Descriptors of Bytes from Index Format ......................................178
Table 135.Defect Descriptors of Physical Sector Format..........................................178
Table 136.READ LONG (3E) ...................................................................................179
Table 137.REASSIGN BLOCKS (07) ......................................................................180
Table 138.Format of Reassign Blocks data ...............................................................181
Table 139.RECEIVE DIAGNOSTIC RESULTS (1C) .............................................182
Table 140.Receive Diagnostic Results page 0...........................................................183
Table 141.Receive Diagnostic Results Page 40.........................................................184
Table 142.Translated address ....................................................................................185
Table 143.RELEASE (17) .........................................................................................186
Table 144.RELEASE (57) .........................................................................................187
Table 145.REPORT DEVICE IDENTIFIER (A3/0C) ..............................................188
Table 146.REPORT LUNS (A0) ...............................................................................191
Table 147.LUN Reporting parameter list format.......................................................191
Table 148.Report Supported Tasks Management Functions (A3/0D) ......................192
Table 149.REQUEST SENSE (03) ...........................................................................193
Table 150.RESERVE (16) .........................................................................................194
Table 151.RESERVE (56) .........................................................................................195
Table 152.REZERO UNIT (01).................................................................................196
Table 153.SEEK (6) - (0B) ........................................................................................197
Table 154.SEEK (10) - (2B) ......................................................................................197
Table 155.SEND DIAGNOSTIC (1D) ......................................................................198
Table 156.SEND DIAGNOSTIC Function Code (1D) .............................................199
Table 157.Diagnostic Page 0 .....................................................................................200
Table 158.Diagnostic Page 3F ...................................................................................200
Table 159.Diagnostic Page 40 ...................................................................................202
Table 160.Address to translate...................................................................................202
Table 161.SET DEVICE IDENTIFIER (A4/06) .......................................................203
Table 162.SET DEVICE IDENTIFIER, Parameter List ...........................................203
Table 163.START STOP UNIT (1B) ........................................................................204
Table 164.SYNCHRONIZE CACHE (35) ................................................................205
Table 165.TEST UNIT READY (00)........................................................................206
Table 166.VERIFY (2F) ............................................................................................207
Table 167.Verify (16) - (8F) ......................................................................................208
Table 168.WRITE (6) - (0A) .....................................................................................209
Table 169.WRITE (10) - (2A) ...................................................................................210
Table 170.WRITE AND VERIFY (10) - (2E) ..........................................................211
Table 171.Write andVerify (12) - (AE) .....................................................................212
Table 172.Write and Verify (16) - (8E) .....................................................................213
Table 173.WRITE BUFFER (3B) .............................................................................214
Table 174.Write Buffer Header .................................................................................215
Table 175.WRITE LONG (3F)..................................................................................218
Table 176.WRITE SAME (41) ..................................................................................219
Table 177.Write Same (16) - (93)..............................................................................220
Table 178.SCSI Status Byte. Format of the SCSI STATUS byte. ...........................221
Table 179.Spindle Motor Degraded Mode - Disable Auto Start ...............................229
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Table 180.Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up ............230
Table 181.Spindle Motor Degraded Mode - Spindle Start Failure............................231
Table 182.Spindle Motor Degraded Mode - Spindle Stopped by Command ............232
Table 183.Self Configuration Failure Degraded Mode ............................................233
Table 184.Format Command Failure Degraded Mode ..............................................234
Table 185.Sense data combinations with auto/recommend rewrite/reallocate..........238
Table 186.Short and Extended Self-Test Description ...............................................243
Table 187.Recommend Reassign Errors....................................................................248
Table 188.Log Only Errors ........................................................................................248
Table 189.Format of Sense Data................................................................................257
Table 190.Field Pointer Bytes ...................................................................................275
Table 191.Actual Retry Count ...................................................................................276
Table 192.Progress Indication ...................................................................................277
Table 193.Unit Error Codes.......................................................................................279
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
1.0 General
1.1 Introduction
This document describes the specifications of the following Hitachi 3.5 inch drives.
Table 1: Product ID table
Product ID
Description
HUS151436VLS300
36 GB
HUS151473VLS300
73 GB
HUS151414VLS300
147 GB
Note: The specifications in this document are subject to change without notice.
1.2 Glossary
Word
Meaning
Kb
Kilobit = 1000 bits
Mb
Megabit = 1,000,000 bits
GB
Gigabyte = 1,000,000,000 bits
MB
Megabyte = 1,000,000 bytes
KB
Kilobyte = 1000 bytes
PFA
Predictive Failure Analysis
S.M.A.R.T.
Self-Monitoring and Reporting Technology
SAS
Serial Attached SCSI
1.3 Caution
This drive can be damaged by ESD (Electric Static Discharge). Any damages incurred to the drive after its removal from the
shipping package and the ESD protective bag are the responsibility of the user.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
1
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
2
2.0 Outline of the Drive
•
Storage capacities of 147 GB, 73 GB, and 36 GB
•
3 Gb/s SAS interface
•
Supports dual-ported operations
•
Supports full duplex (supports full duplex operations) operations
•
Variable sector size (512 - 528 in multiples of four)
•
Tagged Command Queuing support
•
Automatic read/write data transfer
•
3.7 ms seek time in read operation for 146 GB
•
3.6 ms seek time in read operation for 73 GB
•
3.3 ms seek time in read operation for 36 GB
•
Adaptive read ahead algorithm
•
Write Cache
•
Back to back write
•
ECC On The Fly correction
•
Automatic defect reallocation
•
Self diagnostics at power on
•
Closed loop actuator servo
•
High level of integration of the electronics
•
Non head disk contact start/stop
•
15,000 RPM spindle rotation speed
•
Automatic actuator lock
•
PFA (S.M.A.R.T.)
•
Glass substrate disks
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
3
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
4
3.0 Fixed-disk Subsystem Description
3.1 Control Electronics
The drive is electronically controlled by a microprocessor, logic modules, digital/analog modules and various drivers and
receivers. The control electronics perform the following major functions:
• Perform self-checkout (diagnostics)
• Conduct a power-up sequence and calibrate the servo.
• Monitor various timers for head settling, servo failure, etc.
• Analyze servo signals to provide closed-loop control. These include position error signal and estimated velocity.
• Control of the voice coil motor driver to align the actuator onto a desired position
• Monitor the actuator position and determine the target track for a seek operation.
• Constantly monitor error conditions of the servo and take corresponding action if an error occurs.
• Control starting, stopping, and rotating speed of the spindle.
• Control and interpretation of all interface signals between the host controller and the drive
• Control of read/write accessing of the disk media, including defect management and error recovery
3.2 Head Disk Assembly
The head/disk assembly (HDA) is assembled in a clean room environment and contains disks, a spindle motor, actuator assembly, and voice coil motor. Air is constantly circulated and filtered when the drive is operational. Venting of the HDA is accomplished via a breather filter.
The spindle is driven directly by a brushless, sensorless DC drive motor. Dynamic braking is used to stop the spindle quickly.
3.3 Actuator
The read/write heads are mounted in the actuator. The actuator is a swing-arm assembly driven by a voice coil motor. A
closed-loop positioning servo controls the movement of the actuator. An embedded servo data 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.
Heads are moved out from the disks (unloaded) to protect the disk data during shipping, moving, or storage. At power down,
the heads are automatically unloaded from over the disk area and the head actuator locking mechanism will secure the heads in
the unload position.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
5
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
6
4.0 Drive Characteristics
4.1 Formatted Capacity
Table 2: Formatted Capacity
Description
HUS151414VLS300 HUS151473VLS300 HUS151436VLS300
Label capacity
147 GB
73 GB
36 GB
Number of heads
10
5
3
Number of disks
5
3
2
147,015,821,824
73,407,900,160
36,703,949,824
287,140,277
(111D69B5)
143,374,805
(88BB9D5h)
71,687,402
(445DCEAh)
Total data bytes (512
bytes/sector)
Total logical data
blocks
4.2 Data Sheet
Table 3: Data Sheet
Buffer to/from media
764 - 1132 [Mb/sec]
Host to / from buffer (interface transfer rate)
1.5 Gb/s or 3.0Gb/s
Data buffer size
16MB
Number of buffer segments
1 - 256
Rotational speed
15,000 RPM
Recording density
687 [Kbpi] (Max)
Track density
90,000 [TPI] (average)
Areal density
61.8 [Gb/sq. in.]
Data zone
24 for 147GB and 73GB, 20 for 36GB model
4.3 Inquiry Information
4.3.1 Product ID
Product ID in Section 18.5.1.1, “Inquiry Data Format - EVPD = 0, Page Code = 0” on page 77, is as follows:
Table 4: Product ID in Inquiry Command
Product ID
Description
HUS151436VLS300
36 GB
HUS151473VLS300
73 GB
HUS151414VLS300
147 GB
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
7
4.3.2 World Wide ID - Block Assignment
Block Assignment of World Wide ID is as follows:
Table 5: Block assignment of World Wide ID in INQUIRY Command
Manufacturing Site
Singapore
Product
Block Assignment
HUS151414VLS300
001h(1)
HUS151473VLS300
001h(1)
HUS151436VLS300
001h(1)
Note (1) - Additional block assignment will be issued as needed based on actual production volume.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
8
4.4 Cylinder allocation
Table 6: Cylinder allocation
36 GB
73 & 147 GB
Zone
Zone
sectors/trk
cyln/zone
start cyln
end cyln
0
0
840
4960
0
4959
1
1
840
974
4960
5933
2
2
805
1443
5934
7376
3
3
793
1438
7377
8814
4
4
784
954
8815
9768
5
5
770
2020
9769
11788
6
6
770
1046
11789
12834
7
7
760
523
12835
13357
8
8
746
2585
13358
15942
9
9
735
513
15943
16455
10
10
728
1533
16456
17988
11
11
720
1016
17989
19004
12
12
700
3913
19005
22917
13
13
680
1413
22918
24330
14
14
680
938
24331
25268
15
15
672
938
25269
26206
16
16
653
1859
26207
28065
17
17
640
1389
28066
29454
18
18
630
1381
29455
30835
19
19
616
2019
30836
32854
20
606
1615
32855
34469
21
560
1593
34470
36062
22
560
523
36063
36585
23
560
5489
36586
42074
Note: Section 18.10.5, “Mode Page 03 (Format Device Parameters)” on page 133 and Section 18.10.10, “Mode Page 0C
(Notch Parameters)” on page 142 provide methods to determine medium format and zone parameters.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
9
4.5 Performance characteristics
Drive performance is characterized by the following parameters:
•Command overhead
•Mechanical head positioning
-
Seek time
- Latency
•Data transfer speed
•Buffering operation (read ahead/write cache)
Note: All the above parameters contribute to drive performance. There are other parameters that contribute to the performance of the actual system. This specification tries to define the bare drive characteristics, not system throughput, which
depends on the system and the application.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
10
4.5.1 Mechanical positioning
4.5.1.1 Average seek time (including settling)
Table 7: Mechanical positioning performance
Model
Command
147 GB
73 GB
36 GB
Typical (ms)
Max
Read
3.7
3.9
Write
4.1
4.3
Read
3.6
3.8
Write
4.0
4.1
Read
3.3
3.5
Write
3.7
3.8
“Typical” and “Max” are used throughout this document and are defined as follows:
Typical
Average of the drive population tested at nominal environmental and voltage conditions.
Max
Maximum value measured on any one drive over the full range of the environmental and voltage conditions.
(See Section 8.0, “Environment” on page 31 and Section 9.0, “DC power requirements” on page 35 for
ranges.)
The seek time is measured from the start of the actuator’s motion to the start of a reliable read or write operation. “Reliable
read or write” implies that error correction or recovery is not used to correct arrival problems. The average seek time is measured as the weighted average of all possible seek combinations.
Weighted average =
Max
∑ = ( max + 1 – n ) ⋅ ( Tnin + Tnout )
n=1
----------------------------------------------------------------------------------------------( max + 1 ) ⋅ ( max )
Where:
max
n
Tn.in
Tn.out
= Maximum seek length
= Seek length (1 to max)
= Inward measured seek time for an n track seek
= Outward measured seek time for an n track seek
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
11
4.5.1.2 Full stroke seek time
Table 8: Full stroke seek time
Function
Read - 73 GB, 36GB
Read - 147 GB
Write - 73 GB, 36 GB
Write - 147 GB
Typical (ms)
6.6
6.7
6.9
7.0
Max (ms)
6.9
6.9
7.5
7.7
Full stroke seek is measured as the average of 1,000 full stroke seeks with a random head switch from both directions
(inward and outward).
4.5.1.3 Average latency
Table 9: Latency time
Rotation
Time for a revolution (ms)
Average latency (ms)
15,000 RPM
4.0
2.0
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
12
4.5.2 Drive ready time
Table 10: Drive ready time
Model
Typical (sec)
Maximum (sec)
147 GB Model
20.5
29.9
73 GB Model
14.3
29.9
36 GB Model
12.4
29.9
Model
Typical (sec)
Maximum (sec)
147 GB Model
13
20
73 GB Model
9
20
36 GB Model
8
20
4.5.3 Spindle stop time
Table 11: Spindle stop time
The period from power off to complete stop of spindle is categorized as operating and the Operating shock criteria are
applied until complete stop of spindle. Refer to Section 12.3, “Operating shock” on page 49.
4.5.4 Data transfer speed
Table 12: Data transfer speed (sector size 512 Byte case)
Description
•
Typical (MB / Sec)
Read
Write
Disk-buffer transfer
Instantaneous
Measured typical values
Zone
Model
0
0
0
0
All
147 GB
73 GB
36 GB
107.5
93.3
93..3
93.3
107.5
93
93
93
Instantaneous
Measured typical values
19
19
19
19
All
147 GB
73 GB
36 GB
78.8
68.5
68.5
68.5
78.8
68.5
68.5
68.5
Instantaneous
Measured typical values
23
23
23
23
All
147 GB
73 GB
36 GB
71.7
62.3
62.3
--
71.7
62.3
62.3
--
Instantaneous disk-buffer transfer rate is derived by:
(Number of sectors on a track)*512*(revolutions/sec)
Note: The number of sectors per track will vary because of the linear density recording.
•
Sustained disk-buffer transfer rate is defined by considering head/cylinder change time. This gives a local average data
transfer rate. It is derived by.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
13
4.5.5 Buffering operation (read ahead/write cache)
This hard disk drive has a buffer for read ahead.
4.5.6 Throughput
4.5.6.1 Simple sequential access
Table 13: Simple sequential access performance (sector size 512 Byte case)
Operation
Typical (ms)
Read
Write
186
187
185
185
185
185
Maximum (ms)
Read
Write
186
187
186
185
185
185
Zone
0
0
0
Model
147 GB
73 GB
36 GB
Sequential Read / Write
19
19
19
147 GB
73 GB
36 GB
251
250
249
251
250
250
251
250
249
251
250
250
Sequential Read / Write
23
23
23
147 GB
73 GB
36 GB
275
274
--
275
275
--
275
274
--
275
275
--
Sequential Read / Write
The above table gives the time required to read / write for a total of 32,768 consecutive blocks ( 16,777,216 bytes) accessed by
128 READ /WRITE commands. Typical and Max values are given by 100 % and 110% of T respectively, throughout the following performance description.
Note: It is assumed that a host system responds instantaneously.
T = A + B + C + 16,777,216/D
Where:
T = Calculated time
A = Command overhead (no cache hit)
B = Average seek time
C = Average latency
D = Sustained disk-buffer transfer rate
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
14
4.5.6.2 Random access
Table 14: Random access performance (sector size 512 Byte case)
Operation
Random read
Random write
Typical (sec)
24.7
26.3
Maximum (sec)
24.8
26.4
The above table gives the time required to execute a total of 4096 single block READ / WRITE commands which
access a random LBA in unqueued mode.
An approximation for the time is:
T = (A + B + C) * 4096
Where:
T = Calculated time
A = Command overhead (no cache hit)
B = Average seek time
C = Average latency
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
15
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
16
5.0 Data Integrity
The drive retains recorded information under all non-write operations.
No more than one sector can be lost by power down during a write operation while write cache is disabled. If power down
occurs before completion of a data transfer from write cache to disk while write cache is enabled, the data remaining in the
write cache will be lost. To prevent this data loss at power off, the following action is recommended:
•
Confirm successful completion of a SYNCHRONIZE CACHE (35h) command
5.1 Equipment Status
Equipment status is available to the host system any time the drive is not ready to READ, WRITE or SEEK. This status normally exists at power-on time and will be maintained until the following conditions are satisfied:
•
Access recalibration/tuning is complete
•
Spindle speed meets requirements for reliable operations
•
Self-check of drive is complete
Appropriate error status is made available to the host system if any of the following conditions occur after the drive has
become ready:
•
Spindle speed goes outside of requirements for reliable operation
•
“Write fault” is detected
5.2 Error Recovery Procedure
Errors occurring with the drive are handled by the error recovery procedure.
Errors that are uncorrectable after application of the error recovery procedures are reported to the host system as non-recoverable errors.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
17
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
18
6.0 Physical Format
Media defects are remapped to the next available sector during the Format Process in manufacturing. The mapping from Logical Block Address (LBA) to the physical Block locations is calculated using internally maintained tables.
6.1 Shipped Format (P-List)
•
Data areas are optimally used.
•
No extra sector is wasted as a spare throughout user data areas.
•
All pushes generated by defects are absorbed by spare tracks of the inner zone.
P-List Physical Format
Note: Defects are skipped without any constraint, such as track or cylinder boundary. The calculation from LBA to physical
is done automatically by internal table.
6.2 Reassigned Format (G-List)
•
G-List is prepared for 5000 LBAs.
•
Multiple reassignment of the same LBA does not increase the number of G-List entries.
•
A cylinder for spare sectors is prepared every 512 physical cylinders.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
19
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
20
7.0 Environment
7.1 Temperature and humidity
Table 15: Operating and non-operating conditions
Operating conditions
Ambient Temperature
5°C to 55ºC (see note)
Relative humidity
5 to 90%, non-condensing
Maximum wet bulb temperature
29.4ºC, non-condensing
Maximum surface temperature gradient
20ºC/hour
Altitude
-300 to 3,048 m
Shipping conditions
Ambient Temperature
-40°C to 70ºC
Relative humidity
5 to 95%, non-condensing
Maximum wet bulb temperature
35ºC, non-condensing
Maximum surface temperature gradient
30ºC/hour
Altitude
-300 to 12,000 m
Storage conditions
Ambient Temperature
0°C to 65ºC
Relative humidity
5 to 90%, non-condensing
Maximum wet bulb temperature
35ºC, non-condensing
Altitude
-300 to 12,000 m
Note: The system must supply sufficient ventilation to maintain a surface temperature below 60ºC at the center of the drive
top cover. Non-condensing conditions must be maintained at all times. Maximum storage period within shipping package is
one year.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
21
100
36'C/95%
90
31'C/90%
80
WetBuib=35.0'C
Relative Humidity (%)
70
WetBuib=29.4'C
60
Non-operating
50
40
Operating
30
65'C/14%
20
55'C/15%
10
0
-45
-35
-25
-15
-5
5
15
25
35
45
55
65
Temperature ('C)
7.2 Storage requirements
7.2.1 Packaging
The drive or option kit must be heat-sealed in a moisture barrier bag with dessiccant inside the bag supplied by Hitachi Global
Storage Technologies.
7.2.2 Storage time
Cumulative storage time in the package must not exceed one year. If a longer storage time is required, the drive must be
repackaged with new desiccant or moved to a climatically controlled environment.
After the drive is unpackaged, it must not remain inoperative for longer than six months.
7.3 Corrosion test
The hard disk drive shows no signs of corrosion inside or outside of the hard disk assembly and remains functional after being
exposed to a temperature of 50ºC and relative humidity of 90% for seven days.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
22
7.4 Cooling requirements
Drive component temperatures must remain within the limits specified in the following table. Maximum component temperature ratings must not be exceeded under any operating condition. The drive may require forced air cooling to meet specified
operating temperatures.
Table 16: Maximum allowable module surface temperatures
Module name
Location
Maximum allowable surface temperature
MPU/HDC Integration module
1
95ºC
DRAM
2
95ºC
VCM & spindle driver
3
95ºC
Channel module
4
95ºC
Module Locations:
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
23
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
24
8.0 Electrical Interface
8.1 SAS Connector
The drive uses the standard 29 pin Serial Attached SCSI (SAS) connector. 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.
8.1.1 29 pin Serial Attached SCSI (SAS) Connector Definition
Diagram of top and bottom of connector showing pinouts.
Table 17: 29-pin Connector Signal Definition
Pin Number
Signal
Description
S1
GND
GND for SAS Primary Port
S2
RP+
SAS Primary Port Receive
(positive) signal
S3
RP-
SAS Primary Port Receive
(negative) signal
S4
GND
GND for SAS Primary Port
S5
TP-
SAS Primary Port
Transmit(negative) signal
S6
TP+
SAS Primary Port
Transmit(positive) signal
S7
GND
GND for SAS Primary Port
S8
GND
GND for SAS Secondary
Port
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
25
Pin Number
Signal
Description
S9
RS+
SAS Secondary Port
Receive(Positive) signal
S10
RS-
SAS Secondary Port
Receive (negative) signal
S11
GND
GND for SAS Secondary
Port
S12
TS-
SAS Secondary Port
Receive (negative) signal
S13
TS+
SAS Secondary Port
Receive (positive) signal
S14
GND
GND for SAS Secondary
Port
P1
+3.3V
NOT USED (Pins P1-P3
tied internally)
P2
+3.3V
NOT USED (Pins P1-P3
tied internally)
P3
+3.3V
NOT USED (Pins P1-P3
tied internally)
P4
GND
GROUND
P5
GND
GROUND
P6
GND
GROUND
P7
+5V-Charge
Pre-charge pin for +5V
P8
+5V
+5V power supply input
P9
+5V
+5V power supply input
P10
GND
GROUND
P11
READY LED
READY LED output
P12
GND
GROUND
P13
+12V=Charge
Pre-charge pin for +12V
P14
+12V
+12V power supply input
P15
+12V
+12V power supply input
8.1.2 Voltage and Ground Signals
The 12V and 5V contacts provide all of the voltages required by the drive. The two voltages share a common ground plane to
which all of the ground contacts are connected.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
26
9.0 DC Power Requirements
The following voltage specification applies at the drive power connector. Connections to the drive should be made in a safety
extra low voltage (SELV) circuit. There is no power off sequencing requirement.
The power on sequencing requirement is as follows:
If 5V is turned on before 12V, then the sequence delay must be less than 2 seconds.
If 12V is turned on before 5V, there is no time limit.
Failure to power on sequence correctly will prevent motor spin up.
Adequate secondary over-current protection is the responsibility of the system. A 10 A limit is required for safety purposes.
Table 18: Input Voltage
Tolerance
Absolute Max
Spike Voltage
Supply Rise Time
+5 Volts Supply
+/- 5%
5.5 V
0-200 ms
+12 Volts Supply
+/- 5%
15 V
0-400 ms
Note: -8% is acceptable during spin up, but the spin up time is not guaranteed.
CAUTION: To avoid damage to the drive electronics, power supply voltage spikes must not exceed 5.5V.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
27
9.1 Power Supply Current, Average and Peak
Table 19: Power Supply Current of 146, 73, 36 GB Model
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
28
9.2 Ripple Voltage
Table 20: Power Supply Generated Ripple at Drive Power Connector
Maximum (mV pp)
MHz
+5 V DC
250
0-10
+12 V DC
250
0-10
During drive start up and seek, 12 volt ripple is generated by the drive (referred to as dynamic loading). If the power of several
drives is daisy chained, the power supply ripple plus other drive dynamic loading must remain within the regulation tolerance
of +5%. 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 drive's performance, the drive must be held by four screws in a
user system frame that has no electrical level difference at the four screw positions. The drive enclosure must not be used in
the current return path of the drive power supply. The maximum common-mode noise current passing through the drive must
not exceed 20 mA.
9.3 Power Consumption Efficiency Index
Table 21: Power Consumption Efficiency Index
Model
147GB Model 73GB Model
Power Consumption Efficiency Index -Idle Mode (W/GB)
0.08
0.13
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
29
36GB Model
0.25
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
30
10.0 Reliability
10.1 Start/Stop Cycles
The drive is designed to withstand a minimum of 50,000 start/stop cycles at ambient environment.
The drive is designed to withstand a minimum of 10,000 start/stop cycles at the operating environment conditions specified in
“Environment” on page 21.
10.2 Data Reliability
The probability of an uncorrectable data error is 10 in 1x1016 bits read.
ECC implemention:
•
1 symbol = 10 bits
•
1 interleaves
•
15 symbols, On-The-Fly correction
•
Up to 30 symbols (total) Off-Line correction with burst error information
•
LBA seeded 32 bit CRC for ECC miscorrect detection
10.3 Seek errors
A non-recoverable seek/ID miscompare error is defined as a seek operation that cannot be recovered by the error recovery procedure of the drive. The drive reports sense key 04 and sense code 02 for this error.
No drive has more than one non-recoverable seek/ID miscompare error per 100 million seek operations (1 in 1x 108) when
operated at the full range of voltage and environmental conditions.
10.4 Failure prediction (PFA/S.M.A.R.T)
A recoverable equipment error is an error other than a seek/ID miscompare error or read error that is detected and corrected by
the drive error recovery procedure. Examples are Write Fault, Drive Not Ready and internal drive errors.
No drive has more than one recoverable equipment error per 108 READ, 108 WRITE, or 106 SEEK operations when operated
at the full range of voltage and environmental conditions.
Non-recoverable equipment errors indicate a defective drive.
10.5 Preventive Maintenance
None.
10.6 Temperature Warning
Temperature Warning is enabled by setting the EWASC (Enable Warning Additional Sense Code) bit to 1 and setting DEXCPT
(Disable Exception Control) bit to 0 in Mode Page 1C. For mode page settings, refer to Section 18.10.14, “Mode Page 1C
(Informational Exceptions Control)” on page 150. The warning is issued as sense data (Sense Key 01h, Code 0Bh, Qual 01h).
The drive temperature is reported in Log Sense page 2F. Refer to Section 18.7.12, “Log Sense Page 18” on page 110.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
31
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
32
11.0 Mechanical Specifications
11.1 Outline
11.2 Mechanical Dimensions
The drive complies with SFF-8301.
Table 22: Physical Dimensions
Height [mm]
25.8 ± 0.3
Width [mm]
101.6 ± 0.25
Length [mm]
146.0 ± 0.6
Weight [grams - maximum]
147 GB Model
73 GB Model
36 GB Model
758 grams
741 grams
736 grams
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
33
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
34
11.3 Interface Connector
The interface conforms to the specification SFF-8323, 3.5 Drive Form Factor with Serial Connector.
11.4 Mounting Positions and Tappings
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
35
11.5 Drive Mounting
The drive will operate in all axes (6 directions). Performance and error rate will stay within specification limits if the drive is
operated in the other orientations from which it was formatted.
The recommended mounting screw torque is 0.6 - 1.0 Nm (6 - 10 Kgf.cm). The recommended mounting screw depth is 4 mm
maximum for bottom and 4.5 mm maximum for horizontal mounting.
To avoid performance degradation, mount the drive in the system securely enough to prevent excessive motion or vibration of
the drive at seek operation or spindle rotation, using appropriate screws or equivalent mounting hardware. Consult with the
issuer of this specification for actual application if necessary.
Drive level vibration tests and shock tests are to be conducted with the drive mounted to a table using the bottom four screws.
11.6 Heads Unload and Actuator Lock
Heads are moved out from the disks (unload) to protect the disk data during shipping, moving or storage. At power down, the
heads are automatically unloaded from over the disk area and the head actuator locking mechanism will secure the heads in the
unload position.
11.7 Breather Hole
The breather hole must be kept clear and unobstructed at all times. Do not cover the breather hole.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
36
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
37
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
38
12.0 Vibration and Shock
All vibration and shock measurements in this section are made with a drive that has no mounting attachments for the systems.
The input power for the measurements is applied to the normal drive mounting points.
12.1 Operating Vibration
12.1.1 Random Vibration
The drive is designed to operate without unrecoverable errors while being subjected to the vibration levels as defined below.
The assessments are carried out during 30 minutes of random vibration using the power spectral density (PSD) levels as follows.
No Errors:
0.4 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes.
No Data Loss: 1.2 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes.
Note:
The specified levels are measured at the mounting points.
12.1.2 Swept Sine Vibration
The drive will meet the criterion while operating in the respective conditions as described below.
No errors:
0.5 G 0-peak, 5-400-5 Hz sine wave, 0.5 octave/minute sweep rate
No data loss:
0.75 G 0-peak, 5-400-5 Hz sine wave, 0.5 octave/minute sweep rate
1.0 G 0-peak, 5-300-5 Hz sine wave, 0.5 octave/minute sweep rate
12.2 Non-operating Vibrations
The drive will not sustain permanent damage or loss of recorded data after being subjected to the environments as described
below.
12.2.1 Random Vibration
The test consists of a random vibration applied for each of the three mutually perpendicular axes at a time duration of ten minutes per axis.
1.04 G RMS, 5-500 Hz, flat PSD profile
12.2.2 Swept Sine Vibration
The test consists of a swept sine vibration applied for each of the three mutually perpendicular axes.
2.0G 0-peak, 5-500-5 Hz sine wave, 0.5 octave/minute sweep rate
12.3 Operating shock
The drive will meet the criterion while operating in the respective conditions as described below.
No data loss:
15G, 11 ms duration, half sinewave shock pulse
No data loss:
30G, 2 ms duration, half sinewave shock pulse
The shock pulses of each level are applied to the drive, ten pulses for each direction and for all three mutually perpendicular
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
39
axes. There must be a minimum of thirty seconds delay between shock pulses. The input level is applied to a base plate where
the drive is attached using four mounting screws.
12.4 Non-operating shock
The drive will not sustain permanent damage or loss of recorded data after being subjected to the environments as described
below.
12.4.1 Half sinewave shock pulse
80 G, 11 ms duration, half sinewave pulse
250 G, 2 ms duration, half sinewave pulse
The shocks are applied in each direction of the drive for the three mutually perpendicular axes, one axis at a time. The input
level is applied to a base plate where the drive is attached using four mounting screws.
12.4.2 Rotational shock
30,000 radians /second2, 1 ms duration
20,000 radians /second2, 2 ms duration
The shock input is applied around the axis of the actuator pivot. The shock input does not displace the heads from the actuator
latched position.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
40
13.0 Acoustics
13.1 Sound power levels
The upper limit criteria of A-weighted sound power levels are given in Bel, relative to one pico watt, and are shown in the
following table. The measurement method is in accordance with ISO-7779.
Table 23: A-weighted sound power levels
A-weighted sound power level (Bel)
Model
Mode
Typical
Maximum
Idle
3.5
3.8
Operating
4.6
5.0
Idle
3.5
3.8
Operating
4.6
5.0
Idle
3.5
3.8
Operating
4.6
5.0
147 GB
73 GB
36 GB
Background power levels of the acoustic test chamber for each octave band are to be recorded. Sound power levels are measured with the drive supported by spacers so that the lower surface of the drive is located 25 ± 3 mm height from the chamber
desk.
No sound-absorbing material shall be used. The acoustical characteristics of the drive subsystem are measured under the
following conditions.
Idle Mode:
Powered on, disks spinning, track following, unit ready to receive and respond to host commands except every 40 seconds
when the idle time function incrementally sweeps the disk surface.
Operating Mode
Continuous random cylinder selection and seek operation of the actuator with dwell time at each cylinder. Seek rate for the drive
is calculated per the formula below:
Ns = average seek rate in seeks/sec where:
Ns = 0.4 / (Tt + Tl)
Tt = published random seek time
Tl = time for the drive to rotate by half a revolution
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
41
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
42
14.0 Identification
14.1 Labels
The following labels are affixed to every hard disk drive shipped from the drive manufacturing location in accordance with
appropriate hard disk drive assembly drawing:
•
A label containing Hitachi Global Storage Technologies logo, Hitachi part number and the statement “Made by Hitachi,” or Hitachi approved equivalent.
•
A label containing drive model number, manufacturing date, formatted capacity, country of origin or Hitachi
approved equivalent and UL, C-UL, TUV, CE and CTICK logos.
•
A bar code label containing the drive serial number.
•
A user designed label, per agreement
•
Interface definition mark, SAS-3 Model
The labels may be integrated with other labels.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
43
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
44
15.0 Electromagnetic Compatibility
The drive, when installed in a suitable enclosure and exercised with a random accessing routine at maximum data rate meets
the worldwide EMC requirements listed below.
Hitachi will provide technical support to meet the requirements to comply with the EMC specifications.
•
United States Federal Communications Commission (FCC) Rules and Regulations (Class A), Part 15
•
Hitachi Corporate Standard C-S 2-0001-005
•
CISPR Publication 22; 1993 (Class A)
•
CISPR Publication 22; Amendment 1, 1995
•
CISPR Publication 22; Amendment 2, 1996
•
Electrostatic Discharge Susceptibility limits for a Class 2 ESD environment specified in IBM Corporate Standard CS 2-0001-034.
•
Radiated Electromagnetic Susceptibility (RES) as specified in Hitachi Corporate Standard C-S 2-0001-037.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
45
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
46
16.0 Standards
The following shows the safety standards for different countries.
16.1 UL and C-UL Standard Conformity
The drive is qualified per ULIEC 60950-1: 2001, First Edition for use in Information Technology Equipment, including Electric Business Equipment. The UL recognition, or the C-UL certification, is maintained for the product life. The UL and C-UL
recognition mark appears on the drive.
16.2 European Standards Compliance
The product is certified to EN60950.
16.3 German Safety Mark
The product is approved by TUV on Test requirement: EN 60950, but the GS mark is not applicable to internal devices such as
these drives.
16.4 Flammability
The printed circuit boards used in this drive are made of material with a UL recognized flammability rating of V-1 or better.
The flammability rating is marked or etched on the board. All other parts not considered electrical components are made of
material with a UL recognized flammability rating of V-1 or better.
16.5 Corporate Standards Compliance
This product has been designed to meet the following Corporate Standards:
- NB 3-0501-201 Product Safety, National Requirements-All Countries.
- CS 3-0501-070 Electrical, Mechanical and Flammability
- NB 3-0501-033 Product Safety National Certification Conformity Requirement
- CS 1-9700-020 Eco-Product Design Requirement
Hitachi GST encourages owners of information technology (IT) equipment to responsibly recycle their equipment when it is
no longer needed. Hitachi GST offers a variety of programs and services to assist equipment owners in recycling their IT
products.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
47
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
48
17.0 SAS Attachment
This section defines some basic terminology and describes the behavior of the drive when attached to a Serial Attached Scsi
(i.e. SAS) domain.
17.1 General
This section introduces some of the terminology that is used in describing Serial Attached SCSI (i.e. SAS).
SAS is logically a bi-directional, point to point serial data channel that leverages the Scsi protocol set. Nodes are physically
connected via a Port.
Ports may be connected point-to-point via SAS expanders, to form a complex switching network, referred to as a SAS domain.
SAS is defined in terms of a hierarchy of functions or 'protocol layers'. This discussion will focus in on the aspects of SAS that
are relevent to this product.
•
SCSI Application Layer - Clause 10
•
SSP Transport Layer (Serial SCSI Protocol) - Clause 9
•
SAS Port Layer - Clause 8
•
SSP Link Layer - Clause 7
•
SAS PHY Layer - Clause 6
•
SAS Physical Layer - Clause 5
All layers are defined in the following ANSI standard.
•
“Serial Attached SCSI - 1.1 (SAS-1.1)” - ANSI
In addition, this drive claims compliance with the following ANSI standards.
•
SCSI Architecture Model (SAM-3)
•
SCSI Block Commands (SBC2)
17.2 SAS Features
The following SAS features are supported by the Drive.
• SAS Compliance
- “Serial Attached SCSI - 1.1 (SAS-1.1)” - ANSI
• SAS Protocol
- This drive supports Serial Scsi Protocol (SSP).
- STP (Tunneled SATA) and SMP (Management protocol) protocols are
NOT supported.
• SAS Dual Ported Operation
- single PHY ports (i.e. Narrow port. Wide Port NOT supported)
- ports function independently with separate firmware controls
- Multiple DMA engines capable of accessing either port
- full duplex and dual port DMA data/data operations
- Maximum outstanding credit of four per port
• Physical Link Rates
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
49
- G1 (1.5 Gbps) and G2 (3.0 Gbps) supported
- Largely Automated OOB and speed negotiation sequences
- Optional Support for the hot-plug timeout in hardware
• Delayed Spin up
- Hardware detects NOTIFY(Enable Spinup) primitive and interupts the firmware to begin spin up
- Reserved NOTIFYs also caused interrupts for future use
• Partial support for Disconnect/Reconnect Mode Page (0x02)
- Maximum Connect Time Limit - SUPPORTED
- Bus Inactivity Time Limit - NOT SUPPORTED
- Maximum Burst Size - NOT SUPPORTED
- First Burst Size - NOT SUPPORTED
•Others...
- Logical Link rate matching
- Hard Reset primitive sequence detection and validation in hardware
- Hashed WWN validation in hardware
- extended CDB support
17.3 SAS Names and Identifiers
In SAS, device and port names are worldwide unique names within a transport protocol. Port identifiers are the values by
which ports are identified within a domain, and are used as SAS addresses. Phy identifiers are unique within a device.
Object
SAS implementation
00b LUN Identifier
SAS address
01b SAS Address/Target Port
Identifier for Port 0
Not defined
SAS Address/Target Port Identifier for Port 1
SAS address
11b Target Device Name
Phy identifier
Where the SAS Address format is defined by ANSI as follows:
Byte/Bit
0
7
6
5
4
3
2
NAA (5h)
1
1
0
(MSB)
IEEE Company ID
2
3
(LSB)
(MSB)
4
5
6
Vendor Specific Identifier
7
(LSB)
The SAS Device Name is a unique SAS address world wide name. This device name is reported through the SCSI Vital Products Data.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
50
Each of the two SAS ports also has a unique SAS address world wide name. These port identifiers are reported in the IDENTIFY Address frame and are used as source and destination addresses in the OPEN address frame. They are also reported
through the SCSI Vital Products Data.
Since this drive is one device with two ports it has three SAS addresses. All SAS Addresses are in 64-bit IEEE Registered
Name format, as illustrated in Table 24.
Table 24: IEEE Registered Name format
Bit
63-60
59-36
35-24
23-22
21-0
0101
OUI in Canonical Form
Block Assignment
Object
S/N
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 Hitachi Global Storage Technologies
Device Name/Port Identifier
00b
Device
01b
Port 1
10b
Port 2
11b
Not assigned
Sequentially increasing drive serial number assigned at manufacturing.
17.4 Spin up
The drive supports the Active Wait, Active, and Stopped states specified by the SAS standard. After power on, the drive enters
the Active Wait state. The Drive will not spin up it's spindle motor after power on until it receives a NOTIFY(Enable Spinup)
primitive on either port to enter the Active state. If a NOTIFY(Enable Spinup) primitive is received prior to receiving a StartStop Unit command with the Start bit set to one, spin up will begin immediately. For SAS, this is analgous to auto-spinup function in legacy SCSI. This provision allows the system to control the power spikes typically incurred with multiple drives
powering on (and spinning up) simultaneously.
If a StartStop command with the Start bit set to one is received prior to receiving a NOTIFY(Enable Spinup), the Drive will not
start it’s spindle motor until Notify(Enable Spinup) is received on either port. Successful receipt of a NOTIFY(Enable Spinup)
is a prerequisite to spin up.
If the StartStop Unit command with the Start bit set, also has the immediate bit set, status will be returned prior to actually
spinning up the motor, but the actual act of spinning up the motor is deferred until receipt of the NOTIFY(Enable Spinup)
primitive. If a media access command is received after sending immediate Status and prior to receiving a NOTIFY(Enable
Spinup), the Drive will terminate the command with CHECK CONDITION status with a sense key of NOT READY and an
additional sense code of LUN NOT READY, NOTIFY (ENABLE SPINUP) REQUIRED. If a media access command is
received after receiving the NOTIFY(Enable Spinup) primitive and before the drive is finished spinning up, the Drive will terminate the command with CHECK CONDITION status with a sense key of LUN NOT READY and an addition sense code of
LUN IS IN THE PROCESS of BECOMING READY.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
51
Active
N O TIFY
(ENABLE SPINUP )
STO P UNIT
STA R T U N IT
Power On
Active Wait
Stopped
S TOP U N IT
17.5 PHY Layer
The Phy layer defines 8b10b coding and OOB signals. The Phy layer is the interface between the link layer and the physical
layer. This section describes Phy Layer behaviors of the Drive. For a complete description of SAS Phy Layer, please see the
ANSI specification, SAS 1.1.
17.5.1 Link Reset Sequence
The Link Reset Sequences for SAS are defined in the SAS 1.1 ANSI specification and shown below. As show in the diagram,
a Phy Reset sequence, consists of an OOB sequence, followed by speed negotiations. Link Reset Sequences will always
include a PHY Reset Sequence, followed by an Identification Sequence. Inclusion of a Hard reset sequence is optional. If Hard
Reset is performed, it will be preceeded by a Phy Reset sequence, and will be followed by Phy Reset/Identification sequences.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
52
Time
SAS
Link Reset sequence
Phy Reset sequence
OOB sequence
Identification sequence
Speed Negotiation
sequence
SAS w/Hard Reset
Time
Link Reset Sequence with hard Reset
Phy Reset sequence
Hard Reset Sequence
Phy Reset sequence
Identification sequence
17.5.2 Hard Reset
A Hard Reset sequence on a port will not affect the other port, but the outstanding commands on the other port will be aborted
due to the LUN reset associated with the Hard Reset. The effect of a Hard Reset will be similar to a Power on Reset, and will
result in the re-initialization of all Drive resources. The first command issued from every initiator on the port that received the
Hard Reset will result in a CHECK CONDITION with a sense key of UNIT ATTENTION and an additional sense code of
SCSI BUS RESET OCCURRED. The first command issued from every initiator on the other port will result in a CHECK
CONDITION and an additional sense code of BUS DEVICE RESET OCCURRED.
A Hard Reset Sequence will never be issued by the Drive. A link reset will be initiated by the drive on the affected port upon
completion of Hard Reset processing. .
17.5.3 SAS OOB (Out of Band)
Out of band (OOB) signals are low-speed signal patterns detected by the Phy that do not appear in normal data streams. They
consist of defined amounts of idle time followed by defined amounts of burst time. During the idle time, D.C. idel is transmitted. During the burst time, ALIGN (0) primitives are transmitted repeatedly. The signals are differentiated by the length of
idle time between the burst times.
As a SAS compliant device, the Drive uses three OOB signals: COMINIT/COMRESET and COMWAKE and COMSAS.OOB
operations are beyond the scope of this specification. Please refer to the ANSI SAS 1.1 specification for more details.
The drive will initiate OOB by sending COMINITs, under the following conditions:
• POR
• loss of sync
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
53
• Identify timeout
17.5.4 SAS Speed Negotiation
The Drive supports both G1 (1.5 Gbps) and G2 (3.0 Gbps) negotiation speeds. The default maximum negotiation rate is G2
speed (per byte 32 in the Phy Control and Discover Mode Page 19 subpage 1) and the drive will always attempt to negotiate
this rate. If the Link will not support G2, the drive will fall back to a G1 negotiated rate.
17.5.5 PHY Error Handling
This section defines the PHY layer error handling of the drive.
Error
Error Handling Procedure
Link Reset
After POR or Hard Reset, the drive initiates link reset by transmitting exactly 1
COMINIT. For other resets, the drive does not initiate Link Reset.
COMINIT Timeout
If COMINIT or COMSAS is not received before the"Hot Plug Timeout" period
expires, the drive continues to transmit DC zero and wait for COMINIT/COMSAS. Firmware is notified.
This is not considered an error..
COMSAS Timeout
If COMINIT is detected, COMSAS is transmitted, and COMSAS is not
received before the COMSAS Detect Timeout timer expires, firmware is notified and the drive continues to transmit DC zero and wait for COMINIT.
Speed Negotiation Errors
If speed negotiation fails with no match, or if the drive fails retrying the matched
link rate, firmware is notified and the drive continues to transmit DC zero and
wait for COMINIT. If the match link rate retry fails, the Phy Reset Problem
counter is incremented (Log Page 0x18).
Loss of 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
17.6 Link Layer
The SAS link layer defines primitives, address frames, and connections. The Link layer is the interface between the Port layer
and the Phy layer. This section describes Link Layer behaviors of the Drive. For a complete description of SAS Link Layer,
please see the ANSI specification, SAS 1.1.
17.6.1 Address Frames
Address frames are used for the identification sequence and for connection requests and are only sent outside connections. The
Address Frame format is defined below:
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
54
Table 25: Address Frame Format
Byte
Bit
7
0
6
Rsvd
5
4
3
Device Type
2
1
0
Address Frame Type
1-27
Frame Type Dependent bytes
28-31
CRC
•The ADDRESS FRAME TYPE field indicates the type of address frame and is defined in table 69. 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
17.6.1.1 Identify Address Frame
The IDENTIFY address frame format is used for the identification sequence. The IDENTIFY address frame is sent after the
phy reset sequence completes. The Idenfity Address Frame format is defined as follows:
Table 26: Identify Address Frame
Byte
Bit
7
0
Rsvd
6
5
3
Device Type = 1
1
•
•
•
•
4
2
1
0
Address Frame Type = 0
Reserved
2
Reserved
SMP
STP
SSP
Initiaor Initiaor Initiaor
Port=0b Port=0b Port=0b
Rsvd
3
Reserved
SMP
SSP
STP
Target
Target
Target
Port=1b Port=0b Port=0b
Rsvd
4-11
Reserved
12-19
SAS Address
20
PHY Identifuer
21-27
Reserved
28-31
CRC
Device Type: set to 001b to indicate that this drive is an "End Device".
Addess Frame Type: set to 00b to indicate that this is an IDENTIFY.
Initiator Port bits: set to 000b since this device is a target device only
Target Port bits: set to 100b since this device is a SSP target device only
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
55
•
•
SAS ADDRESS: field contains the port identifier of the SAS port transmitting this frame.
PHY Identifier: field contains the PHY identifier of the PHY transmitting this frame.
17.6.1.2 OPEN Address Frame
The OPEN address frame format is used for the identification sequence. The OPEN address frame is sent after the phy reset
sequence completes. The OPEN Address Frame format is defined as follows:
Byte
Bit
7
0
1
•
•
•
•
•
•
•
•
•
•
•
6
Initiator
Port=0
5
4
3
Protocol = 1
2
1
0
Address Frame Type = 1
Features = 0
Connection Rate = 8h or 9h
2-3
Initiator Connection Tag
4-11
Destination SAS Address
12-19
Source SAS Address
20
Compatible Features
21
Pathway Blocked Count
22-23
Arbitration Wait Time
24-27
More Compatible Features
28-31
CRC
Initiator Port: This bit is set to zero when the Drive is the source port acting as a SAS target.
Protocol: this field is set to 001b to indicate SSP Protocol.
Features: this field is set to zero and ignored by the Drive per SAS 1.1.
Connection Rate: field should be set to 8h (1.5Gbps) or 9h (3Gbps), depending on requested link rate. Rate 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: The Drive will set this value to the last value received from this Initiator.
Destination SAS Address: field contains the port identifier of the SAS port to which a connection is being requested.
Source SAS Address: field contains the port identifier on the port that originated this frame (i.e. the drive’s port address).
Compatible Features: this field is set to zero and ignored by the Drive per SAS 1.1.
Pathway Blocked Count: this field indicates the number of times the port has retried this connection request due to
receiving OPEN_REJECT (PATHWAY BLOCKED). The Drive willl not increment the PATHWAY BLOCKED COUNT
value past FFh.
Arbitration Wait Time: this field indicates how long the port transmitting the OPEN address frame has been waiting for
a connection request to be accepted. For values from 0000h to 7FFFh, the Arbitration Wait Time timer increments in one
microsecond steps. For values from 8000h to FFFFh, the Arbitration Wait Time timer increments in one millisecond step.
More Compatible Features: this field is set to zero and ignored by the Drive per SAS 1.1.
17.6.2 Link Layer Error Handling
This section defines the Link layer error handling of the drive.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
56
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 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 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 zero. If an ACK or NAK is not
received for a RESPONSE frame within 1ms, the RESPONSE frame will be
retransmitted with the RETRANSMIT bit set to one. The drive will retry sending a RESPONSE frame once.
Bad Frame 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.
OPEN_REJECT
OPEN_REJECT – Retryable Variations
• OPEN_REJECT(RETRY), OPEN_REJECT(PATHWAY_BLOCKED),
OPEN_REJECT(NO_DESTINATION) – These variations are retried automatically by the hardware until the I_T NEXUS LOSS Timer expires.
When this occurs, the command is internally aborted and all commands
from that initiator are aborted.
• OPEN_REJECT(RATE_NOT_SUPPORTED) – If this occurs, it must
mean that a link between the drive and initiator renegotiated to a lower link
rate after the command was received. In this case, we retry in a new connection at 1.5Gb/sec. If this error is received for a 1.5Gb connection, the
command is internally aborted.
OPEN_REJECT – Unretryable Variations
• OPEN_REJECT(BAD_DESTINATION),
OPEN_REJECT(WRONG_DESTINATION),
OPEN_REJECT(PROTOCOL_NOT_SUPPORTED) – If these
OPEN_REJECTs are received, we internally abort the command.
Credit Timeout
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
57
OPEN Frame Checking
OPEN Response Timeout
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.
If AIP or OPEN_ACCEPT is not received before the OPEN Response timer
expires, the 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.
\
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
58
17.7 Transport Layer
The Transport layer defines frame formats. The Transport layer is the interface between the application layer and port layer. It
is responsible for constructing and parsing frame contents. For SSP, the transport layer only receives frames from the port layer
that are going to be ACKed by the link layer. This section describes Transport Layer behaviors of the Drive. For a complete
description of SAS Transport Layer, please see the ANSI specification, SAS 1.1.
The transport layer defines the frame format as follows.
Table 27: SAS Frame Format
Byte
Bit
7
6
5
4
3
2
0
Frame Type
1-3
Hashed Destination Address
4
Reserved
5-7
Hashed Source Address
8-9
Reserved
10
Reserved
11
Reserved
1
0
Retransmit
Rsvd
# of fill bytes
12-15
Reserved
16-17
Tag
18-19
Target Port Transfer Tag
20-23
Data Offset
24-m
Information Unit
Fill Bytes (if Needed)
(n-3)-n
CRC
• FRAME TYPE field, which defines the format of the INFORMATION UNIT field as follows:
Code
Name of Frame
Information Unit
Originator
IU Size (bytes)
01h
DATA
Data
Initiator or Target
1-1024
05h
XFER_RDY
Data Transfer Ready
Target
12
06h
COMMAND
Command
Initiator
28-284
07h
RESPONSE
Response
Target
24-1024
16h
TASK
Task Management
Function
Initiator
28
f0-ffh
vendor specific
all others
reserved
• The HASHED DESTINATION SAS ADDRESS field contains the hashed value of the destination SAS address.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
59
• The HASHED SOURCE SAS ADDRESS field contains the hashed value of the source SAS address.
• The NUMBER OF FILL BYTES field indicates the number of fill bytes between the INFORMATION UNIT field and
the CRC field. The RETRANSMIT bit is set to one for RESPONSE 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
•. The TAG field contains a value that allows the SSP port to establish a context for commands and task management functions.
• The TARGET PORT TRANSFER TAG field is set and used by the drive. The initiator should echo this field in outbound data IU.
• The INFORMATION UNIT field contains the information unit, the format of which is defined by the FRAME TYPE
field.
• Fill bytes shall be included after the INFORMATION UNIT field so the CRC field is aligned on a four byte boundary.
17.7.1 Command Information Unit
The COMMAND frame is sent by an SSP initiator port to request that a command be processed by the drive.
Table 28: COMMAND Information Unit
Byte
Bit
7
6
5
4
3
0-7
Logical Unit Number
8
Reserved
9
Disable
first
burst=0
2
0
Task
Attribute
Reserved
10
1
Reserved
11
Additional CDB Length (in Dwords)
12-27
CDB
28-n
Additional CDB Bytes
Rsvd
• The LOGICAL UNIT NUMBER field contains the address of the logical unit. The drive only supports a LUN of 0’s.
• A DISABLE FIRST BURST bit is not supported by the drive
• The TASK ATTRIBUTE field is defined as follows:
Value
Attribute
000b
Simple_Q
001b
Head_of_Q
010b
Ordered_Q
100b
ACA_Q (not supported)
101b
Reserved
• The ADDITIONAL CDB LENGTH field contains the length in dwords (four bytes) of the ADDITIONAL CDB field.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
60
• The CDB and ADDITIONAL CDB BYTES fields together contain the CDB.
17.7.2 TASK Information Units
Table 29: TASK Information Unit
Byte
Bit
7
6
5
4
3
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
2
1
0
• The LOGICAL UNIT NUMBER field contains the address of the logical unit. The drive only supports a LUN of 0’s.
• The TASK MANAGEMENT FUNCTION field is defined as follows:
Value
Function
01h
ABORT TASK: The Drive shall perform the ABORT TASK associated with the value of the
TAG OF TASK TO BE MANAGED field
02h
ABORT TASK SET: The Drive shall perform the ABORT TASK SET by aborting all outstanding tasks for the Initiator that sent the TMF.
04h
CLEAR TASK SET: This TMF causes the Drive to abort all tasks in the task set. The action
is equivalent to receiving a series of Abort Task requests from all Initiators.
A unit attention condition shall be generated for all other Initiators with tasks in the task set.
The Additional Sense Code shall be Commands cleared by another Initiator.
08h
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.
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.
others
RESERVED: The Drive will return a RESPONSE frame with the DATAPRES field set to
RESPONSE_DATA and its RESPONSE CODE field set to TASK MANAGEMENT FUNCTION NOT SUPPORTED.
• 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
61
17.7.3 XFER_RDY Information Units
The XFER_RDY frame is sent by the Drive to request write data (i.e. out bound data) from the initiator.
Table 30: XFER_RDY Information Unit
Byte
Bit
7
6
5
4
3
0-3
REQUESTED OFFSET
4-7
WRITE DATA LENGTH
8 - 11
RESERVED
2
1
0
•The REQUESTED OFFSET field 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.
•The WRITE DATA LENGTH field contains the number of bytes of write data the Initiator may transmit to the Drive
(using DATA frames) from the requested offset.
17.7.4 DATA Information Units
The DATA frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data).
Table 31: DATA Information Unit
Byte
Bit
7
6
5
4
3
0 - (n-1)
2
1
0
DATA
17.7.5 RESPONSE Information Units
The RESPONSE frame is sent by the Drive to the Initiator (in bound data) or by the Initiator to the Drive (out bound data).
Table 32: Response Information Unit
Byte
Bit
7
0-9
10
6
5
4
3
2
1
0
RESERVED
RESERVED
11
STATUS
12 - 15
Reserved
16 - 19
SENSE DATA LENGTH (n bytes)
20 - 23
RESPONSE DATA LENGTH (m bytes)
24 - (24+m)
RESPONSE DATA
(24+m) (23+m+n)
SENSE DATA
DataPres
• The DATAPRES field, which indicates the format and content of the STATUS field, SENSE DATA LENGTH field,
RESPONSE DATA LENGTH field, RESPONSE DATA field, and SENSE DATA field.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
62
Value
DATAPRES Description
00b
NO DATA: no data present
01b
RESPONSE_DATA: response data present
10b
SENSE_DATA: sense data present
11b
RESERVED
Table 33: RESPONSE DATA
Byte
Bit
7
6
5
4
3
0-2
RESERVED
3
RESPONSE CODE
2
1
0
• RESPONSE CODES are defined as follows:
Value
RESPONSE Code Description
00b
Task Management Function complete
02b
Invalid Frame
04b
Task Management Function not supported
05b
Task Management Function failed
08b
Task Management Function succeeded
09b
Invalid LUN
others
RESERVED
17.7.6 Sequences of SSP Information Units
SSP Information Units are used in conjunction with one another to execute SCSI commands. This section provides a brief
overview of SAS SSP Information Unit sequences, that would be required to complete a SCSI command.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
63
Initiator
Initiator
Target
Target
Command IU
Command IU
Xfr_Rdy IU
Data IU (s)
Data IU (s)
Response IU
Response IU
Time
Read Type Command
IU Sequence
Time
Time
Write Type Command
IU Sequence
Time
Figure 1: SSP Information Unit Sequences
17.7.7 Transport Layer Error Handling
This section defines the Transport layer error handling by the drive.
Error
Error Handling Procedure
SSP Header Field 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
64
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
65
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
66
18.0 SCSI Command Set
Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory
Table 34: SCSI Commands Supported
Type
Code
Description
M
04h
FORMAT UNIT (04), page 70
M
12h
INQUIRY (12), page 76
O
4Ch
LOG SELECT (4C), page 89
O
4Dh
LOG SENSE (4D), page 92
O
15h
MODE SELECT (15), page 118
O
55h
MODE SELECT (55), page 119
O
1Ah
MODE SENSE (1A), page 120
O
5Ah
MODE SENSE (5A), page 153
O
5Eh
PERSISTENT RESERVE IN (5E), page 155
O
5Fh
PERSISTENT RESERVE OUT (5F), page 151
O
34h
PRE-FETCH (34), page 158
M
08h
READ (6) - (08), page 159
M
28h
READ (10) - (28), page 160
O
3Ch
READ BUFFER (3C), page 161
M
25h
READ CAPACITY (25), page 165
O
9Eh/10h
READ CAPACITY (16) (9E/10), page 170
O
37h
READ DEFECT DATA (37), page 169
O
B7h
READ DEFECT DATA (B7), page 173
O
3Eh
READ LONG (3E), page 175
O
07h
REASSIGN BLOCKS (07), page 176
O
1Ch
RECEIVE DIAGNOSTICS RESULTS (1C), page 178
M
17h
RELEASE (17), page 181
O
57h
RELEASE (57), page 182
O
A3h/05h
REPORT DEVICE IDENTIFIER (A3), page 183
O
A0h
REPORT LUNS (A0), page 185
O
A3h/0Ch
REPORT DEVICE IDENTIFIER (A3/0C), page 188
O
A3h/0Dh
REPORT SUPPORTED TASKS MANAGEMENT FUNCTIONS (A3/0D), page 189
M
03h
REQUEST SENSE (03), page 186
M
16h
RESERVE (16), page 187
O
56h
RESERVE (56), page 188
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
67
O
01h
REZERO UNIT (01), page 189
O
0Bh
SEEK (6) - (0B), page 190
O
2Bh
SEEK (10) - (2B), page 190
M
1Dh
SEND DIAGNOSTIC (1D), page 191
O
A4h/06h
SET DEVICE IDENTIFIER (A4), page 195
O
1Bh
START STOP UNIT (1B), page 204
O
35h
SYNCHRONIZE CACHE (35), page 205
M
00h
TEST UNIT READY (00), page 198
O
2Fh
VERIFY (2F), page 199
O
AFh
VERIFY(16) - (AFh), page 256
M
0Ah
WRITE (6) - (0A), page 201
M
2Ah
WRITE (10) - (2A), page 202
O
2Eh
WRITE AND VERIFY (10) - (2E), page 203
O
AEh
WRITE AND VERIFY (12) - (AE), page 210
O
8Eh
WRITE AND VERIFY (16) - (8E), page 259
O
3Bh
WRITE BUFFER (3B), page 206
O
3Fh
WRITE LONG (3F), page 210
O
41h
WRITE SAME (41), page 211
O
93h
WRITE SAME (16) - (93), page 267
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
68
18.1 SCSI Control Byte
The Control Byte is the last byte of every CDB. The format of this byte is shown below.
Table 35: SCSI Control Byte
BIT
7
6
5
VU = 0
4
3
2
Reserved = 0
1
0
FLAG
LINK
VU
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*
This bit 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.
18.2 Abbreviations
These abbreviations are used throughout the following sections:
LUN
Logical Unit Number. An encoded three bit identifier for the logical unit.
VU
Vendor Unique bits
LBA
Logical Block Address
RSVD Reserved
MSB
Most Significant Byte
LSB
Least Significant Byte
18.3 Byte ordering conventions
In this specification, where it is not explicitly stated, all multi-byte values are stored with the most significant byte first. For
example, in a 4 byte field, byte 0 will contain the MSB and byte 3 the LSB.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
69
18.4 FORMAT UNIT (04)
Table 36: FORMAT UNIT (04)
Byte
BIT
7
6
5
0
4
3
1
0
Command Code = 04h
1
Reserved = 0
FmtData
CmpLst
2
VU = 0
3-4
Obsolete = 0
5
2
VU = 0
Defect List Format
Reserved = 0
FLAG
LINK
The FORMAT command performs a physical formatting of the drive media. This includes handling of defective sectors and
the overwriting of all data areas with a constant data pattern. (Reserved areas of the media are not affected by the FORMAT
command.)
• FmtData set to one specifies that a Data Out phase follows the Command phase. The Data Out phase consists of a defect
list header followed by zero or more defect descriptors, the Glist. FmtData set to zero specifies that no Data Out
phase follows.
• 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 Description
000b
Block format
100b
Bytes From Index format
101b
Physical Sector format
If the FmtData bit is set to zero, this field must also be zero. Otherwise the command will complete with a CHECK
CONDITION with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
•Notes:It is recommended that the MODE SELECT command be issued prior to the FORMAT UNIT command to specify
parameters that affect the formatting process.
The Block Length parameter of the Mode Select Parameter List’s Block Descriptor is used during formatting and is
saved following a successful format operation. If a MODE SELECT command has not been issued since the last reset
or start-up (bring-up) sequence, then the Block Length from the previous format operation is used.
Subsequent to receiving a FORMAT UNIT command, the Target responds to commands as follows:
- 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
70
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
71
18.4.1 Defect list
Following is the format of the Dlist Header sent during the data out phase when FmtData is set to one.
Table 37: Format of Defect List Header
BIT
Byte
7
6
5
0
1
2
4
3
2
1
0
DSP
Immed
Ignored
Reserved = 0
FOV
(MSB)
DPRY
DCRT
STPF=1
IP = 0
Defect List Length
3
(LSB)
The Target has a limited implementation of the Format Option bits located in Bits 2 through 7 of Byte 1 in the Dlist Header. If
the Initiator attempts to select any function not implemented by the Target, the Target terminates the command with Check
Condition status. The sense key is set to Illegal Request and the additional sense code is set to Invalid Field in Parameter List.
• FOV (Format Options Valid) bit set to zero causes the Target to verify that the setting for the DPRY (Disable Primary),
DCRT (Disable Certification), STPF (Stop Format), IP (Initialize Pattern), and DSP (Disable Saving Parameters) bits
are zero. If any of these bits are not zero, the Target terminates the command with Check Condition status. The sense
key is set to Illegal Request and the additional sense code is set to Invalid Field in Parameter List.
Note:
When the FOV bit is one, six combinations of the DPRY, DCRT, STPF, IP and DSP bits are allowed. Any
other combinations return a Check Condition status with a sense key of Illegal Request and an additional
sense code of Invalid Field in Parameter List. The supported combinations are:
DPRY=0 DCRT=1 STPF=1 IP=0 DSP=0
DPRY=1 DCRT=1 STPF=1 IP=0 DSP=0
DPRY=0 DCRT=0 STPF=1 IP=0 DSP=0
DPRY=0 DCRT=1 STPF=1 IP=0 DSP=1
DPRY=1 DCRT=1 STPF=1 IP=0 DSP=1
DPRY=0 DCRT=0 STPF=1 IP=0 DSP=1
•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, theTarget 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.
• DCRT (Disable Certification) bit set to zero indicates that the Target performs a medium certification operation and generates a Certification List (Clist) and the Target adds the Clist to the Glist. A DCRT bit of one indicates that the Target
does not generate a Clist nor 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.
•The Target encounters an unrecoverable error while accessing a required Dlist.
• IP (Initialization Pattern) bit must be set to zero. The Target initializes all data with zeros.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
72
• DSP (Disable Saving Parameters) bit when zero indicates the target is to save all the current MODE SELECT saveable
parameters during the format operation. When the bit is one, the target is not to save the current MODE SELECT
saveable parameters.
• Immed (Immediate) bit set to zero requests that status be returned at the end of the format operation. An immediate bit
set to one requests that status be returned immediately following CDB validation and transfer of data in the Data Out
phase. If the format operation, with the immediate bit set to one, terminates in error, DEFERRED ERROR SENSE
data is generated.
Note:
With the immediate bit set to one, the Link bit must be set to zero. Otherwise, the command is terminated
with Check Condition status, sense key is set to Illegal Request and additional sense code is set to CDB
Invalid.
• Defect List Length field specifies the total length in bytes of the defect descriptors that follow. Up to 128 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.
18.4.2 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 Invalide Field in Parameter List.
18.4.2.1 Block Format - 000b
Format of the Dlist sent during the data out phase when Dlist Format is Block format (000b) and FmtData is set to one.
Table 38: Defect Descriptor - Block Format (for n + 1 defects)
Byte
BIT
7
6
5
4
3
2
1
0
(MSB)
Defective Logical Block Address
0-3
(LSB)
4n
4n+1
(MSB)
Defective Logical Block Address n
4n+2
4n+3
(LSB)
The Block format of the Glist 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
73
18.4.2.2 Bytes From Index Format - 100b
Format of the Dlist sent during the data out phase when Dlist Format is Bytes From Index format (100b) and FmtData is set to
one.
Table 39: Defect Descriptor - Bytes From Index Format (for n = 1 defects)
BIT
Byte
7
6
5
4
3
2
1
0
(MSB)
0-2
Cylinder Number of Defect
(LSB)
3
Head Number of Defect
(MSB)
4-7
Defect Bytes from Index
(LSB)
8n
(MSB)
Cylinder Number of Defect n
8n + 1
(LSB)
8n + 2
8n + 3
8n + 4
8n + 5
8n + 6
Head Number of Defect n
(MSB)
Defect (n) Bytes from Index
(LSB)
8n + 7
Each defect descriptor for the Bytes From Index format specifies that the sector containing this byte be marked defective. The
defect descriptor is comprised of the cylinder number of the defect, the head number of the defect, and the number of the
defect byte relative to index.
Note: If a Byte From Index entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
74
18.4.2.3 Physical Sector Format - 101b
Format of the Dlist sent during the data out phase when Dlist Format is Physical Sector format (101b) and FmtData is set to
one.
Table 40: Defect Descriptor - Physical Sector Format (for n + 1 defects)
BIT
Byte
7
0
6
5
4
3
2
Cylinder Number of Defect
(LSB)
2
3
5
Head Number of Defect
(MSB)
Defect Sector Number
6
(LSB)
7
8n
(MSB)
Cylinder Number of Defect n
8n + 1
(LSB)
8n + 2
8n + 3
8n + 4
8n + 5
8n + 6
0
(MSB)
1
4
1
Head Number of Defect n
(MSB)
Defect (n) Sector Number
(LSB)
8n + 7
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
75
18.5 INQUIRY (12)
Table 41: INQUIRY (12)
Byte
BIT
7
6
0
5
4
3
2
1
0
CmdDt =0
EVPD
FLAG
LINK
Operation Code = 12h
1
Reserved = 0
2
Page Code
3
Reserved = 0
4
Allocation Length
5
VU = 0
Reserved = 0
The INQUIRY command requests the parameters of theTarget to be sent to the Initiator.
An EVPD An EVPD bit of one specifies that the target return the vital product data page identified by the Page Code field in
the CDB The available VPD pages are defined in the addendum provided for each different drive model in the section entitled
Inquiry Data Format.
The Page Code specifies which page of vital product data information the drive shall return.
Table 42: Page Code descriptions
EVPD
PAGE
CODE
0
0
0
Non Zero
1
Non Zero The drive returns the vital product data of page code requested.
Description
The Target returns the standard INQUIRY data.
The drive returns Check Condition status with the sense key of Illegal Request and
the additional sense code of Invalid Field in CDB.
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).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
76
18.5.1 Inquiry Data
Fields with a value shown inside quotes (e.g. Value =’xyz’) are character fields. A value not in quotes is a numeric value.
Character fields are alphanumeric and represented in ASCII.
18.5.1.1 Inquiry Data Format - EVPD = 0, Page Code = 0
Table 43: Inquiry Data - EVPD = 0
BIT
Byte
7
6
0
1
5
4
Qualifier = 0
RMB = 0
1
0
Reserved=0
Version = 5
Obsolete
Obsolete
Norm
HiSup = 1
ACA=0
4
Response Data Format = 2
Additional Length = 159(9Fh)
5
SCCS=0
ACC=0
6
BQue= 0
EncSer=0
7
2
Peripheral Device Type = 0
2
3
3
Obsolete
ALUA=(00b)
3PC=0
Port
MultiP=1
MChngr= 0
Wb_16=0
Sync=0
Link =0
Reserved = 0
Obsolete
Obsolete
8-15
Vendor ID "HITACHI" (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
CmdQue=
1
Addr16=0
Rsvd=0
• Qualifier is set to zero to indicate that the LUN specified is currently supported. Qualifier is set to 011b when the LUN
specified is not present 1
• Peripheral Device Type is set to zero to indicate that the device is a Direct-Access Peripheral Device.
• Removal Media Bit (RMB) is always set to zero to indicate no removal media exists.
• Version indicates the level of the ANSI standard that the product supports. The drive supports ANSI SCSI version 3.
• NormACA (Normal ACA) field of 0 indicates the device server does not support setting the NACA bit to one in the
Control Byte of the CDB as defined in the SAM.
• HiSup bit of one indicates the drive uses the hierarchical addressing model to assign LUNs to logical units..
• Response Data Format is set to two to indicate that the INQUIRY Data Format as specified in the ANSI SCSI version 2
is supported by the Target.
• Additional Length indicates the number of bytes of INQUIRY information that follows.
• SCCS bit of zero indicates that the device does not contain an embedded storage array controller component.
• ACC bit of zero indicates that no access controls coordinator may be addressed through this logical unit.
1.If an INVALID LUN is specified, a Check Condition status will be returned for all commands except INQUIRY and REQUEST SENSE.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
77
• ALUA bit of zero indicates that the device does not support asymmetric logical unit access.
• 3PC bit of zero indicates that the device does not support thrid-party copy commands.
• BQue bit shall be zero if the CmdQue bit is one.
• EncSer (Enclosure Services) bit of 0 indicates that the Target does not contain an embedded enclosure service component.
• Port bit of 0 indicates that the drive received the Inquiry command on port A, while a Port bit of 1 indicates that the drive
received the Inquiry command on port B.
• MultiP (MultiPort) bit of 1 indicates that the Target has multiple ports and implements multi-port requirements.
• MChngr (Medium Changer) bit is always 0 to indicate MChngr is not supported.
• Addr16 (Wide SCSI Address 16) bit of 0 indicates that the Target does not support 16-bit wide SCSI Addresses.
• REL_A is set to zero to indicate that the Target does not support 'Relative Address Mode'.
• Wb_16 is set to zero to indicate that the Target does not support 16-bit wide data transfers.
• Sync is set to zero to indicate that the Target does not support synchronous data transfer.
• Link is set to zero to indicate that the Target does not support linked commands.
• CmdQue is set to one to indicate that the drive supports command queuing.
• Vendor ID is HITACHI padded with ASCII blanks.
• Product ID is specified in ASCII characters.
Product ID
Description
HUS151414VLS300
15000 RPM 147GB
HUS151473VLS300
15000 RPM 73GB
HUS151436VLS300
15000 RPM 36GB
• Product Revision Level indicates the level of microcode.
• Unit Serial Number contains the drive serial number.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
78
18.5.1.2 Inquiry Data Format - EVPD = 1 - Page Code = 00h
Table 44: Inquiry Data - EVPD = 1 (Page Code = 00h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 00h
2
Reserved = 0
3
Page Length = 09h
4
Supported Page Code - 00h
5
Supported Page Code - 03h
6
Supported Page Code - 80h
7
Supported Page Code - 83h
8
Supported Page Code = 86h
9
Supported Page Code = 87h
10
Supported Page Code = 88h
11
Supported Page Code - D1h
12
Supported Page Code - D2h
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page Code is set to 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
79
18.5.1.3 Inquiry Data Format - EVPD = 1, Page Code - 03h
Table 45: Inquiry Data - EVPD = 1 (Page Code = 03h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 03h
2
Reserved = 0
3
Page Length = 184 (B8h)
4
ASCII Fields Length = 00h
5-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
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page Code is set to the value of the page code field in the CDB.
• Page Length field specifies the length (in bytes) of the vendor unique VPD information (bytes 4 - 163). 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
80
• 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 name of the interface (e.g. SCSI, FCAL, SAS) this code is for.
• Code Type is the intended use of the this code. (e.g. local, released, test)
• User Name is the username of the person who built this version of the code.
• Machine Name is the workstation on which this version of the code was built.
• Directory Name is the last 32 characters of the directory from where this code was built.
• Operating State is the drive operating state. The least significant bit contains the following:
0 = OM_BROKEN
1 = OM_DEGRADED
2 = OM_INACCESSIBLE
3 = OM_STARTING
4 = OM_SPINNING
5 = OM_NORMAL
6 = OM_SLEEP
7 = OM_STOPPED
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.
• Functional Mode is the drive functional mode. The least significant byte (0x0000000n) contains the following:
0 = OM_NORMAL_MODE
Not in special or recovery mode.
1 = OM_SPECIAL_CMD
Special command mode on.
3 = OM_SPC_RSV_ACCESS
Special cmd mode and access to reserved area allowed.
5 = OM_SPC_SDWNLOAD
Special cmd mode and special download allowed.
7 = OM_SPC _ RACCESS_SDWNLD
Special cmd, access to reserved area, and special download allowed.
The second byte (0x000n0000) contains the following:
0 = Idle functions are not enabled.
1 = Idle functions are enabled.
• Degraded Reason (UECType) is why the file is in a degraded mode; i.e., how to exit this mode.
• 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
1 = OM_DISK
3 = OM_TRANSIENT
Drive is running flash code.
Drive is running code loaded from disk.
We are running downloaded code that isn’t saved.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
81
18.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h
Table 46: Inquiry Data - EVPD = 1 (Page Code = 80h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
Peripheral Device Type = 0
1
Page Code = 80h
2
Reserved = 0
3
Page Length = 16 (10h)
4-19
Serial Number (ASCII)
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
82
0
18.5.1.5 Inquiry Data - EVPD = 1 (Page Code = 83h)
Table 47: Inquiry Data - EVPD = 1 (Page Code = 83h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
Page Code = 83h
2
Reserved = 0
3
Page Length = 72 (48h)
5
Protocol Identifier = 0
PIV=0
RSVD
Association=0
Reserved = 0
7
Identifier Length = 8
Identifier Type = 3
LUN (World Wide ID)
(MSB)
(LSB)
16
17
0
Code Set = 1
6
8-15
1
Peripheral Device Type = 0
1
4
2
Protocol Identifier
PIV=1
RSVD
Code Set = 1
Association = 1
18
Reserved = 0
19
Identifier Length = 8
Identifier Type = 3
(MSB)
20-27
Target Port Identifier (World Wide ID)
(LSB)
28
29
Protocol Identifier
PIV=1
RSVD
Code Set = 1
Association = 1
30
Reserved = 0
31
Identifier Length = 4
Identifier Type = 4
(MSB)
32-35
Relative Port Identifier
(LSB)
36
37
Protocol Identifier = 0
PIV=1
RSVD
Code Set = 1
Association = 2
38
Reserved = 0
39
Identifier Length = 8
Identifier Type = 3
(MSB)
40-47
Target Device Name Identifier (World Wide ID)
(LSB)
48
Protocol Identifier = 0
Code Set = 3
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
83
49
PIV=0
RSVD
Association=2
Identifier Type = 8
50
Reserved = 0
51
Identifier Length =24 (18h)
52-55
"naa" (ASCII)
(MSB)
56-71
Target Device Name Identifier (World Wide ID) in ASCII
(LSB)
72-75
Reserved = 0
• Protocol Identifier is valid only when PIV=1. Protocol Identifier = 0 indicates Fibre Channel devices. 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 zero indicates that the Protocol Identifier field should be ignored. PIV set to one
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:
WorWide 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
- yy is the 2-bit port/node ID select
- n is the 22-bit drive unique serial number
- The Relative Port Identifier Identifier indicates the port which received the Inquiry command: 0000 0001h for
the Primary Port, or 0000 0002h for the Secondary Port.
18.5.1.6 Inquiry Data Format - EVPD = 1, Page Code - 86h
Table 48: Inquiry Data Format - EVPD = 1, Page Code - 86h
BIT
Byte
7
0
6
5
Qualifier = 0
4
3
2
Page Code = 86h
2
Reserved = 0
3
Page Length = 60 (3Ch)
5
7-63
Reserved = 0
0
Peripheral Device Type = 0
1
4
1
RTO
Reserved = 0
GRD_CHK APP_CHK REF_CHK
HEADSUP
ORDSUP
SIMPSUP
Reserved = 0
• RTO (Reference Tag Ownership), GRD_CHK (Guard Check), APP_CHK (Application Tag Check), and REF_CHK
(Reference Tag Check) are set to zero to indicate that end-to-end protection features are not supported.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
84
• HEADSUP (Head of Queue Supported), ORDSUP (Ordered Supported), and SIMPSUP (Simple Supported) are set to
one to indicate support for Head of Queue, Ordered, and Simple task attributes.
• 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 indicate support of a volatile cache.
18.5.1.7 Inquiry Data Format - EVPD = 1, Page Code - 87h
Table 49: Inquiry Data Format - EVPD = 1, Page Code - 87h
BIT
Byte
7
0
6
5
4
3
Qualifier = 0
2
Page Code = 87h
2-3
Page Length = 0004h
Reserved=0
5
6
7
0
Peripheral Device Type = 0
1
4
1
Policy Page Code = 3Fh
Policy Subpage Code = FFh
MILUS=1
Reserved = 0
Mode PagePolicy = 0
Reserved = 0
• 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 one indicates the policy is sharded by multiple logical units.
• Mode Page Policy set to 00b indicates that all mode pages and subpages are shared.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
85
18.5.1.8 Inquiry Data Format - EVPD = 1, Page Code - 88h
Table 50: Inquiry Data Format - EVPD = 1, Page Code - 88h
BIT
Byte
7
6
0
5
4
Qualifier = 0
3
2
Page Code = 88h
2-3
Page Length = 48 (0030h)
4-5
Reserved=0
6-7
Primary Relative Port = 0001h
8-9
Reserved = 0
10-11
Initiator Port Transport ID Length = 0
12-13
Reserved = 0
14-15
Primary Target Port Descriptors Length = 0Ch
17
Protocol Identifier
PIV=1
0
Peripheral Device Type = 0
1
16
1
RSVD
Code Set = 1
Association = 1
Identifier Type = 3
18
Reserved = 0
19
Identifier Length = 8
(MSB)
20-27
Primary Target Port Identifier (World Wide ID)
(LSB)
28-29
Reserved = 0
30-31
Secondary Relative Port = 0002h
32-33
Reserved = 0
34-35
Initiator Port Transport ID Length = 0
36-37
Reserved = 0
38-39
Secondary Target Port Descriptors Length = 0Ch
40
41
Protocol Identifier
PIV=1
RSVD
Code Set = 1
Association = 1
Identifier Type = 3
42
Reserved = 0
43
Identifier Length = 8
(MSB)
44-51
Secondary Target Port Identifier (World Wide ID)
(LSB)
• Protocol Identifier is valid only when PIV=1. Protocol Identifier = 0 indicates Fibre Channel devices. Protocol Identifier = 6 indicates SAS devices
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
86
• Code Set specifies the data type for the identifier field. Code Set = 1 indicates binary data
• PIV (Protocol Identifier Valid) set to one indicates that the Protocol Identifier field contains a valid value.
• Association specifies the entity with which the Identifier field is associated: 1h for Target or Relative Port.
• Identifier Type specifies the format and assignment authority for the identifier: 3h indicates NAA format of the WWID
for Target Port.
• 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 World Wide ID is a 64-bit unique identification for each drive. The format is: 5000CCAh
xxxh yyb n wherexxx is the 12-bit block assignment defined for each model and manufacturing site yy is the 2-bit
port/node ID select n is the 22-bit drive unique serial number.
18.5.1.9 Inquiry Data Format - EVPD = 1, Page Code - D1h
Table 51: Inquiry Data - EVPD = 1 (Page Code = D1h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
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
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page Code is set to the value of the page code field in the CDB.
• Page Length is set to 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).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
87
0
18.5.1.10 Inquiry Data Format - EVPD = 1, Page Code - D2h
Table 52: Inquiry Data - EVPD = 1 (Page Code = D2h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
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)
39 - 54
ASCII Card Assembly Part Number
55
Reserved = 0
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page Code is set to the value of the page code field in the CDB.
• Page Length is set to 32, 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).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
88
0
18.6 LOG SELECT (4C)
Table 53: Log Select (4C)
Bit
Byte
7
6
0
5
4
3
2
1
0
PCR
SP
Command Code = 4Ch
1
Reserved = 0
2
PC
Reserved = 0
Reserved = 0
3
4
5
Reserved = 0
6
7
(MSB)
Parameter List Length = 0
8
9
(LSB)
Reserved = 0
FLAG
LINK
The LOG SELECT command provides a means for the Initiator to clear statistical information maintained by the drive and
reported via the LOG SENSE command.
• PCR The Parameter Code Reset determines whether the Log Sense parameters will be cleared and unit attention posted
for all other Initiators. A value of 1 indicates that the parameters be cleared, while a value of zero (except when PC =
11b) indicates that the parameters not be cleared. Parameter list length must be zero when PCR is 1.
• SP The Save Parameters bit value of zero indicates that the page parameters not be saved. A value of 1 indicates that the
page parameters that are savable be saved after they have been changed. SP bit MUST be 1 if parameter list length is
greater than zero. Otherwise it will result in a Check Condition status being returned. The sense key shall be set to
Illegal Request and additional sense code of Invalid Field in CDB.
• PC The Page Control field defines the type of parameters to be selected. The PC field set to 11b (and PCR is then a don't
care) indicates that the Default Cumulative values are set to their default values of 0. If the PC field is set to 01b and
PCR is set to 1, the Current Cumulative values are also set to their default values of 0.
Parameter List Length MUST be zero when PC = 11b. Otherwise the command is terminated and a Check Condition
status is returned. The sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB.
• Parameter List Length The Parameter List Length field specifies the length in bytes of the parameter list that shall be
located in the DATA OUT buffer. A parameter list length zero indicates that no pages shall be transferred.
Note: A specified length greater than 0x00FF will result in a Check Condition status being returned. A length that results in
log data being truncated will generate a Check Condition status.
Note: For page 0Fh, the maximum parameter list length supported is 4004h (4 bytes for the header and 100h bytes for each
of the 40h parameters that are supported). The Parameter List Length must be an integral of the number of parameters plus the
4 byte header. (Ex: Parameter length =104h for one parameter, 204h for 2 parameters,... 4004h for all 40h parameters).
The drive allows updates to the current cumulative values only. A value of zero is acceptable and is not considered an error.
The drive updates only pages 0Eh, the Start/Stop Cycle page and 0Fh, the Application Client page. For other pages the parameters are ignored. If the data out buffer contains multiple pages then the application client should send the pages in ascending
order. If the data out buffer contains multiple log parameters within a page,all log parameters within the page should be sent
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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
89
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 zero by the LOG
SELECT command (when PCR=1).
• Page 02h parameters: (Counters for write errors)
- Write errors recovered without delay
- LBAs with write fault error
- LBAs with ID type error
- 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
- LBAs with ECC detected error
- LBAs with ID type error
- 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
- LBAs with ECC detected error
- LBAs with ID type error
- 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
90
• 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 PFA
- Hardware PFA
- Total Read Commands
- Total Write Commands
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
91
18.7 LOG SENSE (4D)
Table 54: Log Sense (4D)
Bit
Byte
7
6
0
4
3
2
1
0
PPC=0
SP
Command Code = 4Dh
1
Reserved = 0
2
PC
3
Reserved = 0
Page Code
Reserved = 0
4
5
5
(MSB)
Parameter Pointer = 0
6
7
(LSB)
(MSB)
Allocation Length
8
9
(LSB)
Reserved = 0
FLAG
LINK
The LOG SENSE command allows the Initiator to retrieve the statistical data regarding the drive.
• PPC (Parameter Pointer Control) bit must be set to zero. 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.
• Parameter Pointer Field specifies the beginning field for the transfer. This field must be set to 0000h. If the Parameter
Pointer Field is not zero a Check Condition status is returned with a sense key of Illegal Request and additional sense
code of Invalid Field in CDB.
• 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 zero. This condition is not considered an error. TheTarget 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
92
18.7.1 Log Page parameters
Each log page begins with a 4-byte page header followed by zero or more variable-length log parameters.
Page header
Page Code field identifies which log page is being transferred.
The Page Length field specifies the length in bytes of the following log parameters.
Log parameters
Each log parameter begins with a 4-byte parameter header followed by one or more bytes of parameter value data.
The Parameter Code field identifies which log parameter is being transferred for that log page.
The Parameter Control field, the 3rd byte of each parameter header, contains several fields.
- DU The Disable Update bit is set to 0 to indicate that the drive updates the log parameter value to reflect events that
should be noted by that parameter.
- DS The Disable Save bit is set to 1 to indicate the parameter is non-savable and is set to 0 to indicate that the
parameter is savable.
- TSD The Target Save Disable bit is set to zero to indicate that the drive provides a Target defined method for saving log parameters.
- ETC The enable Threshold Comparison bit is set to 0 to indicate the drive does not perform comparisons between
cumulative and any threshold values.
- TMC The Threshold Met Criteria field is not valid because this drive does not perform threshold comparisons.
This field is set to 0.
- LBIN The List Binary bit is only valid if the LP is 1. If the LP bit is 1 and the LBIN bit is 0, then the list parameter
is a string of ASCII graphic code (20h - 7Eh). If the LP bit is 1 and the LBIN bit is 1, then the list parameter is a list
of binary information.
- LP The List Parameter bit is set to 0 for parameters that are data counters. The LP bit is set to 1 for parameters that
are lists.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
93
18.7.2 Log Sense Page 0
Page 0 indicates the supported log sense pages. This page is used to determine which additional pages an Initiator can request.
Table 55: Log Sense Page 0
Bit
Byte
7
0
6
Reserved
5
4
3
2
1
Page code = 0
1
Reserved
2-3
Page Length = 000Eh (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 2Fh
16
Thirteenth supported Page Code =30h
17
Fourteenth supported Page Code = 37h
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
94
0
18.7.3 Log Sense Page 2
This page contains counters for write errors.
Table 56: Log Sense Page 2 (part 1 of 2)
Bit
Byte
7
0
6
5
4
Reserved
3
Reserved
2-3
PageLength = 54h
4-5
Parameter Code = 0000h
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Errors recovered without delay
16-17
Parameter Code = 0001h
18
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
19
Parameter Length = 08h
20-27
Count of write fault errors
28-29
Parameter Code = 0002h
30
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
31
Parameter Length = 08h
32-39
Count with ID type errors
40-41
Parameter Code = 0003h
42
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
43
Parameter Length = 08h
44-51
Total errors recovered
52-53
Parameter Code = 0004h
54
DU = 0
DS = 0
1
0
LBIN =
0
LP
Page code = 02h
1
6
2
TSD = 0 ETC = 0
TMC = 0
55
Parameter Length = 08h
56-63
Times recovery invoked
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
95
LBIN =
0
LBIN =
0
LBIN =
0
LBIN =
0
=0
LP
=0
LP
=0
LP
=0
LP
=0
Table 57: Log Sense Page 2 (part 2 of 2)
Bit
Byte
7
6
64-65
66
5
4
3
1
0
LBIN
=0
LP
Parameter Code = 0005h
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
67
Parameter Length = 08h
68-75
Total bytes written
76-77
Parameter Code = 0006h
78
2
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
79
Parameter Length = 08h
80-87
Count with hard errors
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
96
LBIN
=0
=0
LP
=0
18.7.4 Log Sense Page 3
This page contains counters for read errors.
Table 58: Log Sense Page 3 (part 1 of 2)
Bit
Byte
7
0
6
5
4
Reserved
3
Reserved
2-3
PageLength = 54h
4-5
Parameter Code = 0000h
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Errors recovered without delay
16-17
Parameter Code = 0001h
18
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
19
Parameter Length = 08h
20-27
Count with ECC detected errors
28-29
Parameter Code = 0002h
30
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
31
Parameter Length = 08h
32-39
Count with ID type errors
40-41
Parameter Code = 0003h
42
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
43
Parameter Length = 08h
44-51
Total errors recovered
52-53
Parameter Code = 0004h
54
DU = 0
DS = 0
1
0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
Page code = 03h
1
6
2
TSD=0
ETC = 0
TMC = 0
55
Parameter Length = 08h
56-63
Times recovery invoked
64-65
Parameter Code = 0005h
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
97
Table 59: Log Sense Page 3 (part 2 of 2)
Bit
Byte
66
7
6
DU = 0
DS = 0
5
4
TSD = 0 ETC = 0
3
TMC = 0
67
Parameter Length = 08h
68-75
Total bytes read
76-77
Parameter Code = 0006h
78
DU = 0
DS = 0
TSD = 0 ETC = 0
2
TMC = 0
79
Parameter Length = 08h
80-87
Count with hard errors
1
0
LBIN =
0
LP
=0
LBIN =
0
LP
=0
The drive will attempt to read data after a seek before the head has fully settled on track. This is done to aid performance.
However, as a result there is an increased incidence of error recovery invoked which normally uses ECC or retries to recover
the data. As a consequence of this an error recovered by a single retry is not reported by the error counters.
Additionally the drive does not report data recovered by ECC on the fly.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
98
18.7.5 Log Sense Page 5
This page contains counters for verify errors.
Table 60: Log Sense Page 5 (part 1 of 2)
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
PageLength = 54h
4-5
Parameter Code = 0000h
DU = 0
DS = 0
TSD = 0
ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Errors recovered without delay
16-17
Parameter Code = 0001h
18
DU = 0
DS = 0
TSD = 0
ETC = 0
TMC = 0
19
Parameter Length = 08h
20-27
Count with ECC detected errors
28-29
Parameter Code = 0002h
30
DU = 0
DS = 0
TSD = 0
ETC = 0
TMC = 0
31
Parameter Length = 08h
32-39
Count with ID type errors
40-41
Parameter Code = 0003h
42
DU = 0
DS = 0
TSD = 0
ETC = 0
TMC = 0
43
Parameter Length = 08h
44-51
Total errors recovered
52-53
Parameter Code = 0004h
54
DU = 0
0
LBIN = 0
LP = 0
LBIN = 0
LP = 0
LBIN = 0
LP = 0
LBIN = 0
LP = 0
LBIN = 0
LP= 0
Page code = 05h
1
6
1
DS = 0
TSD = 0
ETC = 0
TMC = 0
55.
Parameter Length = 08h
56-63
Times recovery invoked
64-65
Parameter Code = 0005h
Table 61: Log Sense Page 5 (part 2 of 2)
Bit
Byte
66
67
7
6
DU = 0
DS = 0
5
4
TSD = 0 ETC = 0
3
2
TMC = 0
Parameter Length = 08h
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
99
1
0
LBIN =
0
LP= 0
68-75
Total Bytes Verified
76-77
Parameter Code = 0006h
78
DU = 0
DS = 0
TSD = 0
TMC = 0
79
Parameter Length = 08h
80-87
Count with hard errors
LBIN =
0
LP
=0
In order to aid performance, the drive will attempt to read data after a seek before the head has fully settled on track. However
there is an increased incidence of error recovery invoked as a result which normally uses ECC or a retry to recover the data. As
a consequence of this an error recovered by a single retry is not reported by the error counters.
Additionally the drive does not report data recovered by ECC on the fly.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
100
18.7.6 Log Sense Page 6
This page contains counters for non-medium errors. This includes seek errors and other hardware type failures.
Table 62: Log Sense Page 6
Bit
Byte
7
0
6
5
4
Reserved
3
Reserved
2-3
PageLength = 0Ch
4-5
Parameter Code = 00h
DU = 0
DS = 0
1
0
LBIN =
0
LP
Page code = 06h
1
6
2
TSD = 0 ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Error count
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
101
=0
18.7.7 Log Sense Page D
This page contains temperature information.
Table 63: Log Sense Page D
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
PageLength = 0Ch
4-5
Parameter Code = 0000h
DU = 0
DS = 1
TSD = 0
ETC = 0
TMC = 0
7
Parameter Length = 02h
8
Reserved
9
Temperature (degrees Celsius)
10-11
Parameter Code 0001h
12
DU = 0
DS = 1
0
LBIN = 1
LP = 1
LBIN = 1
LP = 1
Page code = 0Dh
1
6
1
TSD = 0
ETC = 0
TMC = 0
13
Parameter Length = 02h
14
Reserved
15
Reference Temperature (degrees Celsius)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
102
18.7.8 Log Sense Page E
This page contains the start-stop cycle information.
Table 64: Log Sense Page E
Bit
Byte
7
0
6
5
4
Reserved
3
Reserved
2-3
PageLength = 24h
4-5
Parameter Code = 0001h
DU=0
DS=1
1
0
LBIN=0
LP = 1
Page code = 0Eh
1
6
2
TSD=0
ETC=0
TMC = 0
7
Parameter Length = 06h
8-11
Year of Manufacture (4 ASCII characters)
12-13
Week of Manufacture (2 ASCII characters)
14-15
Parameter Code 0002h
16
DU=0
DS=0
TSD=0
ETC=0
TMC = 0
LBIN=0
17
Parameter Length = 06h
18-21
Accounting Date Year (4 ASCII characters)
22-23
Accounting Date Week (2 ASCII characters)
24-25
Parameter Code 0003h
26
DU=0
DS=1
TSD=0
ETC=0
TMC = 0
27
Parameter Length = 04h
28-31
Specified cycle count over device lifetime
32-33
Parameter Code 0004h
34
DU=0
DS=1
TSD=0
ETC=0
TMC = 0
LP=1
LBIN=1
LP=1
LBIN=1
LP=1
35
Parameter Length = 04h
36-39
Accumulated start-stop cycles (4 byte binary number)
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
103
18.7.9 Log Sense Page F
This page contains the Application Client Log.
Table 65: Log Sense Page F
Bit
Byte
7
0
6
5
4
3
Reserved
2
1
0
1
0
LBIN
=1
LP
=1
Page code = 0Fh
1
Reserved
2-3
Page length = 4000h
Application client log parameter
4-259
1st application client log parameter
1613216387
64th application client log parameter
The following table describes the application client log parameter structure.
Table 66: Log Sense Page F, Application Client Log
Bit
Byte
7
6
5
0-1
2
4
3
2
Parameter code
DU
=1
DS
=0
TSD = 0 ETC = 0
TMC = 0
3
Parameter length = FCh
4-
First parameter byte
255
Last parameter byte
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
104
18.7.10 Log Sense Page 10
This page contains self-test results. The results of the 20 most recent self-tests are stored in this Log page.
Table 67: Log Sense Page 10
Bit
Byte
7
0
6
5
4
3
Reserved
2
1
0
1
0
LBIN = 1
LP = 1
Page code = 10h
1
Reserved
2-3
PageLength = 190h
4-23
1st self-test results log parameter
384- 403
20th self-test results log parameter
The following table describes the self-test results log parameter structure
Table 68: Log Sense Page 10, self-test results
Bit
Byte
7
6
5
4
0-1
2
2
Parameter code
DU = 0
DS = 0
TSD = 0
3
4
3
ETC = 0
TMC = 0
Parameter Length = 10h
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
• 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
105
self-test.
• Self-Test Results Value is described in the table below.
Table 69: Log Sense Page 10, self-test results
Value
Description
0h
The self-test routine completed without error.
1h
The background self-test routine was aborted by the initiator using a SEND
DIAGNOSTIC command with the Abort Background self-test function.
2h
The self-test routine was aborted by the application client by a Task Management function or a reset.
3h
An unknown error occurred while the Target was executing the self-test routine
and the Target was unable to complete the self-test routine.
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.
7h
The third or greater segment of the self-test failed (see the Extended segment
number field).
8h-Eh
Fh
Reserved.
The self-test is in progress.
• 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.
Table 70: Log Sense Page 10, Extended Segment Number
Extended
Segment
Number
Short Self-Test
Extended Self-Test
1h
Drive Ready Test
2h
RAM Test
3h
Drive Diagnostics
4h
SMART
5h
Low Level Format check
6h
Physical Head Check
7h
Random Verify
8h
9h
- Verify First 300 MB
- Verify Last 100 MB
Verify all LBAs
Recheck SMART
• 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
106
• 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 18.35 “SEND DIAGNOSTIC (1D)” on page 191, for detailed listing of operations carried out by SEND DIAGNOSTIC command and Power on Diagnostics.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
107
18.7.11 Log Sense Page 15
This page contains information about Background Medium Scan operations.
Table 71: Log Sense Page 15
Bit
Byte
7
0
6
5
4
3
Reserved
2
1
0
1
0
LBIN=1
LP=1
Page code = 15h
1
Reserved
2-3
Page Length = (19 + 24N -3)
Background Medium Scan parameters
4-19
BMS Status Parameter
20-43
First Medium Scan Parameter
...
19+24N
Last Medium Scan Parameter
The following table describes the BMS Status Parameter structure.
Bit
Byte
7
6
5
4
0-1
3
2
Parameter Code = 0000h
2
DU=0
DS=0
TSD=0
ETC=0
TMC=0
2-3
Page Length = 0Ch
4-7
Power On Minutes
8
Reserved = 0
9
BMS Status
10-11
Number of Scans Performed
12-13
Medium Scan Progess
14-15
Reserved = 0
• 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
Description
00h
No scans active
01h
Background medium scan is active
02h-07h
Not supported
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
108
BMS Status
Description
08h
Scan suspended until BMS Interval Timer expires
09h - FFh
Reserved
• Number of Scans Performed indicates the number of background scans that have been performed over the life of thedrive.
• 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.
The following table describes the Meduium Scan Parameter structure.
Bit
Byte
7
6
5
0-1
2
4
3
2
1
0
LBIN=1
LP=1
Parameter Code = 0001h - 0800h
DU=0
DS=0
TSD=0
ETC=0
TMC=0
2-3
Page Length = 14h
4-7
Power On Minutes
8
Reassign Status
Sense Key
9
Additional Sense Code
10
Additional Sense Code Qualifier
11-15
Reserved = 0
16-23
LBA
• 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
Description
0h
No reassignment needed
1h
Reassignment pending receipt of Reassign command or
write command (if auto write reallocation is allowed)
from the initiator
02h-5h
Not supported
6h - Fh
Reserved
• Additional Sense Code and Additional Sense Code Qualifier provide details about the error detected.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
109
18.7.12 Log Sense Page 18
Table 72: Log Sense Page 18
Bit
Byte
7
6
5
4
3
2
0
Page code = 18h
1
Reserved
1
0
(MSB)
2-3
Page Length (70h)
(LSB)
Protocol-specific log parameters
4
First Protocol-specific log parameter - Primary Port
112
Last Protocol-specific log parameters - Secondary Port
Table 73: SAS Log Descriptor
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0-1
Parameter Code (0001h for primary port; 0002h for secondary
(LSB)
2
DU (=0)
DS (=0) TSD (=0) ETC (=0)
3
TMC (00b)
LBIN (=1)
LP (=1)
Parameter Length (34h)
4
Reserved
Protocol IDENTIFIER (6h)
(MSB)
5-6
Reserved
(LSB)
7
Number of PHY’s = 01
8
Reserved
9
Phy Identifier (=00h or 01h)
10
Reserved
11
Reserved
12
Reserved
Attached Device Type
Reserved
13
Reserved
Negotiated Physical Link Rate
14
Reserved
Attached Attached Attached
SSP Initia- STP Initia- SMP Inititor Port
tor Port
ator Port
Reserved
15
Reserved
Attached
SSP Target
Port
Reserved
Attached
STP Target Port
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
110
Attached
SMP Target Port
(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
INVALID DWORD COUNT
(LSB)
(MSB)
44-47
RUNNING DISPARITY ERROR COUNT
(LSB)
(MSB)
48-51
LOSS OF DWORD SYNCHRONIZATION
(LSB)
(MSB)
52-55
PHY RESET PROBLEM
(LSB)
•
•
Attached Device Type: set to to the value received by this PHY during an Identify Sequence.
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
Attached Initiator Port bits: set to 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: field contains the SAS address transmitted by this PHY during an Identify Sequence.
Attached SAS ADDRESS: field contains the SAS address received by this PHY during an Identify Sequence.
Attached PHY Identifier: field 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: the Drive doesn’t differentiate between Invalid DWords and Running Disparity errors. Running Disparity errors will be included in the Invalid Dword Count. This field will always be zero.
LOSS OF DWORD SYNCRONIZATION: 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 speen negotiation. The count stops at the maximum value.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
111
18.7.13 Log Sense Page 2F
This page contains SMART Status and Temperature Reading.
Table 74: Log Sense Page 2F
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
PageLength = 8
4-5
Parameter Code = 0000h
DU = 0
DS = 0
0
LBIN = 1
LP = 1
Page code = 2Fh
1
6
1
TSD = 0
ETC = 0
TMC = 0
7
Parameter Length = 04h
8
SMART Sense Code Byte
9
SMART Sense Qualifier
10
Most Recent Temperature Reading
11
Vendor HDA Temperature Trip Point
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
112
18.7.14 Log Sense Page 30
This page contains Performance Counters.
Table 75: Log Sense Page 30
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
Page Length = 0030h
4-5
Parameter Code = 0000h
DU = 0
DS = 0
0
LBIN = 0
LP = 0
Page code = 30h
1
6
1
TSD = 0
ETC = 0
TMC = 0
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
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 each of the following SCSI commands:
• PRE-FETCH
• READ (6)
• READ (10)
• VERIFY
• VERIFY (16)
• WRITE (6)
• WRITE (10)
• WRITE AND VERIFY
• WRITE AND VERIFY (16)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
113
• WRITE SAME
• WRITE SAME (16)
• SEEK (6)
• SEEK (10)
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 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
114
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.
• 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 zero, the parameters on this page are not savable.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
115
18.7.15 Log Sense Page 37
This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.
Table 76: Log Sense Page 37
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
Page Length = 0030h (48)
4-5
Parameter Code =000h
DU=0
DS=0
7
8
0
LBIN=0
LP=0
Page code = 37h
1
6
1
TSD=0
ETC=0
TMC = 0
Parameter Length = 2Ch
(MSB)
Power on Hours (hours only)
-
(LSB)
11
12
(MSB)
-
Total Bytes Read
19
20
(LSB)
(MSB)
Total Bytes Written
-
(LSB)
27
28
29
-
Max Drive Temp (degrees Celsius)
(MSB)
GList Size
(LSB)
30
31
32
Number of PFA Occurrences
MED
PFA
HDW
PFA
Reserved = 0
33
-
Total Read Commands
40
41 - 48
Total Write Commands
49
Reserved = 0
50 - 51
Flash Correction Count
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
116
The Number of PFA Occurrences field gives the number of PFA occurrences during the life of the drive and not the number
of PFA events that have been reported. The number of reported PFA events may be less due to the settings of Mode Page
0x1C.
If set, the Media and Hardware PFA bits indicate that a PFA trip has occurred during the life of the drive. These flags are set
during a PFA occurrence that may or may not coincide with the reporting of a PFA event 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.
The Flash Correction Count is incremented each time ECC correction is applied to data stored in Flash ROM.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
117
18.8 MODE SELECT (15)
Table 77: Mode Select (15)
Bit
Byte
7
6
0
4
3
2
1
0
Command Code = 15h
1
Reserved = 0
2
PF=1
Reserved = 0
SP
Reserved = 0
3
4
5
5
Parameter List Length
VU = 0
Reserved = 0
FLAG
LINK
The MODE SELECT (15) command provides a means for the Initiator to specify LUN or device parameters to the Target. It
also allows an Initiator to specify options the Target uses in error recovery, caching, and formatting.
There is a single set of Mode Page parameters shared by all Initiators.
• PF A 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 to 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 an 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).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
118
18.9 MODE SELECT (55)
Table 78: Mode Select (55)
Bit
Byte
7
6
0
Reserved = 0
2-6
9
4
3
2
1
0
Command Code = 55h
1
7-8
5
PF=1
Reserved = 0
SP
Reserved = 0
(MSB)
Parameter List Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The MODE SELECT (55) command provides a means for the Initiator to specify LUN or device parameters to the Target. See
the MODE SELECT (15) command for a description of the fields in this command.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
119
18.10 MODE SENSE (1A)
Table 79: Mode Sense (1A)
Bit
Byte
7
6
0
1
2
5
4
3
1
0
Command Code = 1Ah
Reserved
PCF
RSVD
DBD
Subpage Code
4
Allocation Length
VU = 0
Reserved = 0
Page Code
3
5
2
Reserved = 0
FLAG
LINK
The MODE SENSE (1A) command provides a means for the drive to report various device parameters to the Initiator. It is the
complement to the MODE SELECT command.
If the DBD (Disable Block Descriptor) bit is zero, the Target will return the Block Descriptor. If the DBD bit is set to 1, the
Target will not return the 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
00
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.
01
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.
10
Report default value. The drive returns the default values for the page code specified. The parameters not supported
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
120
by the drive are set to zero.
11
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.
Table 80: Page Code Usage
Page Code
Description
00h - 1Ch
Return specific page, if supported.
3Fh
Return all supported pages.
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 CHECK CONDITION 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. Subpages are support for Mode Pages 19h and 1Ch only.
18.10.1 Mode Parameter List
The mode parameter list contains a header followed by zero or more block descriptors followed by zero or more variable
length pages.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
121
18.10.1.1 Header
The 6-byte command descriptor block header is defined below.
Table 81: Mode parameter header (6)
Bit
Byte
7
6
5
4
3
0
Mode Data Length
1
Medium Type = 0
2
WP=0
DPOFUA
=1
Reserved=0
3
2
1
0
Reserved = 0
Block Descriptor Length (= 0 or 8)
The 10-byte CDB header is defined below.
Table 82: Mode parameter header (10)
Bit
Byte
7
0
1
6
5
(MSB)
2
1
0
(LSB)
Medium Type = 0
WP=0
4
5
6
7
3
Mode Data Length
2
3
4
Reserved=0
DPOFUA
=1
Reserved = 0
Reserved = 0
(MSB)
Block Descriptor Length
(= 0 or 8)
(LSB)
• 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.
• Block Descriptor Length specifies the length in bytes of the block descriptors. When used with the MODE SELECT
command, zero or eight is supported by the drive. When used with the MODE SENSE command, the drive returns
eight to indicate that only a single block descriptor is available.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
122
18.10.1.2 Block Descriptor
Table 83: Mode Parameter Block Descriptor
Byte 0
(MSB)
Number of Blocks
Byte 1
Byte 2
Byte 3
(LSB)
Byte 4
Byte 5
Density code = 0
(MSB)
Byte 6
Block Length
Byte 7
(LSB)
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, the Number of Blocks field must be
-
Zero to indicate not to change available blocks
-
0xFFFFFFFF 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 used with the MODE SENSE command, the field contains the exact number of blocks.
• Density Code
-
Always 0 for direct access devices.
• Block Length
When used with the MODE SELECT command, the Block length field must contain the value from 512 to 528 (8
bytes step) or zero. 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.
When used with the MODE SENSE command, the field is dependent on how the media is currently formatted.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
123
18.10.1.3 Page Descriptor
Table 84: Mode Parameter Page Format
Byte 0
PS
SPF
Byte 1
Page Code
Page Length
Byte 2-n
Mode Parameters
Each mode page contains a page code, a page length, and a set of mode parameters.
When using the MODE SENSE command, a Parameter Savable (PS) bit of one indicates that the mode page can be saved by
the drive in the reserved area of the drive. A PS bit of zero indicates that the supported parameters cannot be saved. 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 indicate the long format is used,
supporting sub pages. The drive supports the following mode page codes:
Table 85: Mode Parameter Page Format
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
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
124
18.10.2 Mode Page 00 (Vendor Unique Parameters)
Table 86: Vendor Unique Parameters - Page 00
Default
Bit
Byte
0
7
6
PS
0
5
4
1
0
80h
Page Length = 0Eh
2
Ignored
Ignored
0Eh
MRG
VGMDE
Ignored
Ignored
4
RRNDE
00h
Ignored
Ignored
5
6
2
Page Code = 00h
1
3
3
Ignored
IGRA
AVERP
FDD
00h
00h
Ignored
Ignored
CAEN
Ignored
OCT (high nibble)
02h
00h
7
Overall Command Timer (low byte)
00h
8
Ignored
00h
9
Temperature Threshold
00h
10
Command Aging Limit (Hi byte)
00h
11
Command Aging Limit (Low byte)
30h
12
Read Reporting Threshold
0Ah
13
Write Reporting Threshold
0Ah
14
15
DRRT
Ignored
Ignored
FFMT
FCERT
Ignored
Ignored
Reserved = 0
00h
00h
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 indicates the drive, during its idle state, will execute random seeks at a predefined rate and
range of cylinders using predefined head.
• 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.
• IGRA (Ignore Reassigned LBA) bit is set to 1 for preventing the drive from reassigned processing against reassigned
LBA when RC bit (Mode Page 1 byte 2 bit 4) is active. The main purpose of this bit is to avoid undesirable read processing time delay due to reassigned LBA processing for continuous data availability requirements such as Audio
Visual application. IGRA bit set to 0 specifies that the drive shall process reassigned LBA even if RC bit is active.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
125
• 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 specifies the threshold value in degrees Celsius for the thermal sensor warning message. 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 50 ms.
• Read Reporting Threshold specifies the error reporting threshold for recovered data errors during read operations
when PER=1.
• Write Reporting Threshold specifies the error reporting threshold for recovered data errors during write operations
when PER=1.
• 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
126
18.10.3
Mode Page 01 (Read/Write Error Recovery Parameters)
Table 87: Mode Page 01 (Vendor Unique Parameters)
Bit
Byte
0
7
6
PS
0
5
3
2
1
0
Page Code = 01h
1
2
4
81h
Page Length = 0Ah
AWRE
ARRE
TB
RC
EER=0
Default
0Ah
PER
DTE
DCR
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)
Recovery Time Limit
11
00h
(LSB)
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 zero indicates that the drive shall not perform automatic reallocation of defective data blocks during write operations. An AWRE bit set to one indicates that the drive shall perform automatic reallocation of defective data blocks during write operations.
• ARRE (Automatic Read Reallocation Enabled) bit, set to zero indicates that the drive shall not perform automatic reallocation of defective data blocks during read operations. ARRE bit set to one indicates that the drive shall perform
automatic reallocation of defective data blocks during read operations.
• 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 following commands:
- READ (6)
- READ (10)
For all other commands, the RC bit setting is unused and treated as zero.
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 (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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
127
• PER, (Post Error) bit, is set to one to indicate that the drive reports recovered errors.
• DTE (Disable Transfer) on Error bit, must be set to 0 to indicate that the drive continues the DATA phase upon detection
of a recovered error.
• DCR (Disable Correction) bit, is set to one to indicate that Error Correction Code is not used for data error recovery. A
DCR bit of zero indicates that ECC is applied to recover the data.
• 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 nonzero 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 command execution time. The
value must be from 40 ms to 65535 ms (65.5 seconds). If a command is not able to be completed within the limit, a
Check Condition will be returned when following mode page parameter is set. The recovery time limit will not be
applied to Writes when WCE=1. A value of zero disables the timer.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
128
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.
PER DTE DCR TB DESCRIPTION
0
0
0
0 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.
0
0
0
1
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
transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.
0
0
1
0 Retries are attempted but no error correction (ECC) 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.
0
0
1
1
Retries are attempted but no error correction (ECC) 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.
0
1
0
0
Illegal Request-DTE must be zero when PER is zero.
0
1
0
1
Illegal Request-DTE must be zero when PER is zero.
0
1
1
0
Illegal Request-DTE must be zero when PER is zero.
0
1
1
1
Illegal Request-DTE must be zero when PER is zero.
1
0
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 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
129
1
0
0
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 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
transferred to the Initiator. The drive then creates the Check Condition status with the appropriate sense key.
1
0
1
0 The highest level error is reported at the end of transfer. Retries are attempted but ECC 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 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.
1
0
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 not returned to
the Initiator. The drive then creates the Check Condition status with the appropriate sense key.
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 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.
1
1
0
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
130
1
1
1
0
The highest level error is reported at the end of transfer. Retries are attempted but ECC 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.
1
1
1
1
The highest level error is reported at the end of transfer. Retries are attempted but ECC 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
131
18.10.4 Mode Page 02 (Disconnect/Reconnect Parameters)
Table 88: Mode Page 02 (Disconnect/Reconnect Parameters)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 02h
Default
82h
1
Page Length = 0Eh
0Eh
2
Read Buffer Full Ratio
00h
3
Write Buffer Empty Ratio
00h
4-5
(MSB)
Bus Inactivity Limit = 0
(LSB)
Reserved = 0
6-7
8-9
10-11
00h
(MSB)
00h
Maximum Connect Time Limit
00h
(LSB)
(MSB)
Maximum Burst Size
00h
(LSB)
12-13
Reserved = 0
00h
14-15
First Burst Size = 0
00h
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 is not supported
• 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 is supported on products with SAS interfaces. It 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 is not supported, and any value in this field is ignored.
• First Burst Size is not supported.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
132
18.10.5 Mode Page 03 (Format Device Parameters)
Table 89: Mode Page 03 (Format Device Parameters)
Bit
Byte
0
7
6
PS
0
5
4-5
6-7
8-9
10-11
12-13
14-15
16-17
18-19
20
21-23
3
2
1
0
Page Code = 03h
1
2-3
4
03h
Page Length = 16h
(MSB)
16h
xxh
Tracks per Zone
(LSB)
(MSB)
(LSB)
(LSB)
(LSB)
(LSB)
(LSB)
(LSB)
(LSB)
HSEC
RMB
SURF
RESERVED = 0
Reserved = 0
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
133
xxh
xxh
Cylinder Skew Factor
(LSB)
SSEC
01h
xxh
Track Skew Factor
(MSB)
xxh
00h
Interleave = 0001h or 0000h
(MSB)
xxh
xxh
Data Bytes per Physical Sector
(MSB)
00h
xxh
Sectors Per Track
(MSB)
00h
00h
Alternate Tracks per Logical Unit = 0
(MSB)
00h
00h
Alternate Tracks per Zone = 0
(MSB)
xxh
00h
Alternate Sectors per Zone = 0
(MSB)
Default
xxh
40h
00h
The format device page contains parameters that specify the medium format. This page contains no changeable parameters.
• 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
134
18.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters)
Table 90: Mode Page 04 (Rigid Disk Drive Geometry Parameters)
Bit
Byte
0
7
6
PS
0
1
5
4
3
2
1
0
Page Code = 04h
04h
Page Length = 16h
16h
xxh
(MSB)
2-4
Default
Number of Cylinders
xxh
(LSB)
5
Number of heads
xxh
00h
(MSB)
6-8
Starting Cylinder Write Precompensation = 0
00h
(LSB)
00h
(MSB)
9-11
Starting Cylinder -
00h
Reduced Write Current = 0
12-13
(MSB)
LSB)
00h
Drive Step Rate = 0 (Not used)
(LSB)
00h
(MSB)
14-16
00h
Landing Zone Cylinder = 0 (Not used)
00h
(LSB)
17
RESERVED = 0
RPL = 0
00h
18
Rotational Offset = 0 (Not used)
00h
19
RESERVED = 0
00h
20-21
22-23
(MSB)
3Ah
Medium Rotation Rate in RPM
(LSB)
Reserved = 0
The rigid disk drive geometric page specifies various parameters for the drive.
• RPL = 0, Indicates that the drive does not support spindle synchronization.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
135
98h
00h
18.10.7 Mode Page 07 (Verify Error Recovery Parameters)
Table 91: Mode Page 07 (Verify Error Recovery Parameters)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 07h
1
87h
Page Length = 0Ah
2
Reserved = 0
EER=0
Default
0Ah
PER
DTE=0
DCR
00h
3
Verify Retry Count
01h
4
Obsolete = 0
00h
5
Reserved = 0
00h
6
Reserved = 0
00h
7
Reserved = 0
00h
8
Reserved = 0
00h
9
Reserved = 0
00h
10-11
(MSB)
Verify Recovery Time Limit
00h
(LSB)
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.
Since bytes 4-11 are not changeable, the Mode Select Commands accepts only the values indicated for bytes 4 - 11.
• EER. This bit is 0 since the Target does not support early recovery.
• PER. See below for description of bit values.
• DTE. This bit is 0 since the Target always continues on recovered verify operation errors.
• DCR. See below for description of bit values.
PER, DTE, and DCR bit settings in page 7 override those of page 1 during VERIFY and the Verify portion of WRITE AND
VERIFY. There are only four valid conditions for the PER, DTE, and DCR bits. All other combinations return Check Condition status.
PER DTE DCR DESCRIPTION
0
0
0 Soft errors are not reported. ECC is applied to recover the data.
1
0
0 Soft errors are reported. ECC is applied to recover the data.
0
0
1 Soft errors are not reported. ECC is not used to recover the data.
1
0
1 Soft errors are reported. ECC is not used to recover the data.
• 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 operatoin. The value must be from 40ms to 65535 ms (65.5 seconds). The granularity of
the timer is 60ms. If an LBA is not able to be recovered within the limit, a Check Condition will be returned.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
136
18.10.8 Mode Page 08 (Caching Parameters)
Table 92: Page 08 (Caching Parameters)
Bit
Byte
0
7
6
PS
0
5
4
IC
3
Demand Read Retention Priority
8-9
ABPF
(MSB)
CAP
DISC
SIZE
(MSB)
88h
12h
WCE
MF
RCD
Write Retention Priority
04h
00h
FFh
Minimum Pre-fetch
00h
(LSB)
(MSB)
Maximum Pre-fetch
FFh
(LSB)
Maximum Pre-fetch Ceiling
FSW
(MSB)
LBCSS
DRA
FFh
Reserved = 0
00h
Number of Cache Segments
08h
Cache Segment Size
00h
(LSB)
16
Reserved = 0
00h
00h
(MSB)
17-19
Default
(LSB)
13
14-15
0
Disable Pre-fetch Transfer Length
10-11
12
1
Page Length = 12h
2
6-7
2
Page Code = 08h
1
4-5
3
Non Cache Segment Size
(LSB)
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 dependant upon the other parameters in this page.
• CAP (Caching Analysis Permitted ) is not supported and is ignored.
• DISC (Discontinuity) is not supported and is ignored.
• 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
137
drive may issue Good status for a WRITE (6) or WRITE (10) command after successfully receiving the data but
before writing it to the media. When WCE = 1, the drive operates as if AWRE = 1.
Note: When WCE = 1, a SYNCHRONIZE CACHE command must be done to ensure data are written to the media
before powering down the Target.
• MF (Multiplication Factor) bit determines how the Maximum and Minimum Pre-fetch parameters are interpreted. If this
bit is set to zero, the parameters are used as is. If the bit is set to one, the parameters are multiplied by the number of
blocks requested in the Read Command.
• RCD (Read Cache Disable) bit set at zero indicates that the drive may return some or all of the data requested by a
READ (6) or READ (10) command by accessing the data buffer, not the media. An RCD bit set at one indicates that
the Target does not return any of the data requested by a READ (6) or READ (10) command by accessing the data
buffer. All of the data requested is read from the media instead.
• Demand Read Retention Priority sets the retention priority of data requested on a Read command. It may be set as
defined below:
Value
Definition
0h
Do not distinguish between requested data and other
data
1h
Replace requested data before other data.
Fh
Replace other data before requested data.
where the value is the Demand Read Retention Priority or Write Retention Priority. Requested data is the blocks specified in
the Read or Write command. Other data is data in the cache from any other operation such as pre-fetch, read-ahead, etc.
If the Read Retention Priority is not set to Fh or if the DPO bit on the Read command is set to one, the requested data is overwritten by read-ahead data.
If the DPO bit is set to zero and the Read Retention Priority is set to Fh, the requested data is not overwritten with read-ahead
data. If the requested transfer is larger than the segment, the requested data is overwritten with more requested data and there
is no read-ahead
• Write Retention Priority sets the retention priority of data provided on a Write command. See the definition of
Demand Read Retention Priority above for more details.
• Disable Pre-fetch Transfer Length is used to prevent read-ahead after Read commands that are longer than the specified number of blocks. If this parameter is set to zero, a read-ahead is not performed.
• Minimum Pre-fetch specifies the minimum number of LBAs that the drive should read ahead 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.
• LBCSS (Logical Block Cache Segment Size) bit when set to one indicates that the Cache Segment Size field units shall
be interpreted as logical blocks. When it is set to zero, the Cache Segment Size field units shall be interpreted as
bytes.
• DRA (Disable Read Ahead) bit when set to one requests that the Target not read into the buffer any logical block beyond
the addressed logical block(s). When it is set at zero, the Target may continue to read logical blocks into the buffer
beyond the addressed logical block(s).
• Number of Cache Segments field is used to select the number of data buffer cache segments. This parameter is valid
only when the SIZE bit is set at zero. It is ignored when SIZE is set at one.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
138
• 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
139
18.10.9 Mode Page 0A (Control Mode Page Parameters)
Table 93: Page 0A (Control Mode Page Parameters)
Default
Bit
Byte
0
7
6
PS
0
5
TST=0
3
10-11
RSVD=0
Queue Algorithm Modifier
1
0
8Ah
0Ah
D_Sense=0 GLTSD=0 RLEC=0
Rsvd=0
RSVD=0 RAC=0 UA_INTLCK_CTRL=0 SWP=0
ATO=0 TAS=0
6-7
8-9
2
Page Length = 0Ah
2
5
3
Page Code = 0Ah
1
4
4
(MSB)
QErr
DQue
Obsolete
00h
00h
00h
00h
Reserved=0
Obsolete=0
00h
Busy Timeout Period
00h
(LSB)
(MSB)
Extended Self-test Routine
Completion Time
XXh
(LSB)
Following are parameter options for Page 0A.
• 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
140
• 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.
QERR
value
00b
01b
Description
Specifies that all tasks from all Initiators are blocked from execution when a Contintent
Alligience (CA condition) is pending. Those blocked tasks are allowed to resume execution
in a normal fashion after the CA condition is cleared.
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.
• Busy Timeout Period is ignored internally by the Target.
• Extended Self-test Routine Completion Time is an advisory parameter that an Initiator may use to determine the time
in seconds that the Target requires to complete self-test routine when the Target is not interrupted by an Initiator and
no errors occur during execution of the self-test routine.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
141
18.10.10 Mode Page 0C (Notch Parameters)
Table 94: Page 0C (Notch Parameters)
Bit
Byte
0
7
6
PS
0
1
2
6-7
4
3
2
1
0
Page Code = 0Ch
ND=1
LPN=0
16h
Reserved = 0
80h
Reserved = 0
(MSB)
00h
00h
Maximum Number of Notches
(LSB)
(MSB)
Default
8Ch
Page Length = 16h
3
4-5
5
11h
00h
Active Notch
(LSB)
00h
XXh
(MSB)
8-11
Starting Boundary
XXh
(LSB)
(MSB)
XXh
12-15
Ending Boundary
XXh
(LSB)
(MSB)
16-23
Pages Notched
0000h
0000h
0000h
(LSB) 100Ch
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.
• 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
•Mode Page 3
- Alternate Sector per Zone
- Alternate Track per Zone
- Alternate Track per Logical Unit
- Sector per Track
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
142
- 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
143
18.10.11 Mode Page 18h(SAS only)
Table 95: Page 18h (Protocol-Specific Logical Unit mode page)
Bit
Byte
0
7
6
PS
SPF=0
1
2
5
4
3
2
1
0
Page Code = 18h
Page Length = 6h
Reserved
Transport Layer Retries=0
Default
98h
6h
Protocol Identifier = 6h
6h
3
Reserved = 0
00h
4-7
Reserved
00h
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
144
18.10.12 Mode Page 19h (Port Control Parameters)
The Protocol-Specific Port mode page contains parameters that affect SSP target port operation. There is one copy of the mode
page shared by all SSP initiator ports.
18.10.12.1 Short Format of Port Control Page
Table 96: Short (Port Control Parameters) Short Format
Bit
Byte
0
7
6
PS
SPF=0
5
4
2
1
Page Length = 06h
2
RSVD
3
RSVD
Ready
LED
Meaning
06h
06h
Protocol Identifier = 6
00h
07h
|
D0h
I_T NEXUS LOSS TIMER
(LSB)
5
|
Default
99h
(MSB)
|
6
0
Page Code = 19h
1
4
3
07h
|
D0h
(MSB)
INITIATOR RESPONSE TIMEOUT
(LSB)
7
•
The Parameters Savable (PS) bit is set to one, indicating the the paramaters are saveable.
•
The SPF field shall be set to zero for access to the short format mode page.
•
Protocol Identifier has a value of 6h indicating this is a SAS SSP specific mode page.
•
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 1.1 draft standard.
•
The I_T NEXUS LOSS TIME field 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 that the function is disabled. A value of
FFFFh indicates an unlimited period. The default value of 7D0h, specifies a 2 second time period.
•
INITIATOR RESPONSE TIMEOUT field 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 will be aborted. An INITIATOR RESPONSE TIMEOUT field value of zero indicates that the SSP target port shall disable the timer. The default value of 7D0h, specifies a 2 second time period.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
145
•
Long Format of Port Control Page
Table 97: Long Format of Port Control Page
Bit
Byte
0
7
6
PS
SPF=1
5
3
2
1
0
Page Code = 19h
1
2
|
3
4
Default
39h
Subpage Code
...
00h
|
00h
(MSB)
Page Length (n-3)
(LSB)
4
RSVD
5
RSVD
00h
Protocol Identifier = 6h
6
06h
...
Protocol Specific Mode Parameters
n
...
The drive maintains an independent set of port control mode page parameters for each SAS initiator port.
•
The 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 support the following subpage codes. If the
Subpage Code is not supported, the drive returns a CHECK CONDITION status, the sense key is et to ILLEGAL
REQUEST and the additional sense code set to ILLEGAL FIELD IN PARAMETER LIST.
- 01h: PHY Control and Discover 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
146
18.10.12.2 PHY Control and Discover (Subpage 1)
Table 98: PHY Control and Discover (Subpage 1)
Bit
Byte
0
7
6
PS
SPF=1
5
1
2
|
3
4
3
2
1
0
Page Code = 19h
Default
39h
Subpage Code = 1
...
(MSB)
00h
|
60h
Page Length = 60h
(LSB)
4
5
6
Reserved
Reserved
00h
Protocol Identifier = 6h
Reserved
06h
00h
7
Number of PHYS = 2
02h
8-55
SAS PHY Mode Descriptor 0
...
56-103
SAS PHY Mode Descriptor 1
...
The Phy Control And Discover subpage contains phy-specific parameters. 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.
•
Number of PHYS field is set to 2, to represent the dual ported drive (one PHY per port)
•
There are 2, SAS PHY Mode Descriptor fields, one per port.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
147
Each SAS
PHY Mode Descriptor is defined as follows:
Table 99: SAS
PHY Mode Descriptor
Bit
Byte
7
6
5
0
6
7
•
•
2
1
0
0 or 1
Reserved
Rsvd
00h
Attached Device Type
Reserved
Default
00h
PHY Identifier
2-3
5
3
Reserved
1
4
4
Rsvd
10h
Negotiated PHY Link Rate
...
Rsvd
00h
Reserved
Attached Attached Attached
SMP
STP
SSP
Initiaor Initiaor Initiaor
Port
Port
Port
Rsvd
08h
Reserved
Attached Attached Attached
SMP
STP
SSP
Target
Target
Target
Port=1b Port=0b Port=0b
8-15
SAS Address
...
16-23
Attached SAS Address
...
24
Attached PHY Identifuer
...
25-31
Reserved
00h
32
Programmed Min Phy Link Rate = 8h
Hardware Min Phy Link Rate = 8h
88h
33
Programmed Max Phy Link Rate = 9h
Hardware Max Phy Link Rate = 9h
99h
33-41
Reserved
00h
42-43
Vendor Specific
00h
44-47
Reserved
00h
Attached Device Type: set to to the value received by this PHY during an Identify Sequence.
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
Attached Initiator Port bits: set to to the value received by this PHY during an Identify Sequence.
Attached Target Port: set to 100b indicating this device is a SSP target device only
SAS ADDRESS: field contains the SAS address transmitted by this PHY during an Identify Sequence.
Attached SAS ADDRESS: field contains the SAS address received by this PHY during an Identify Sequence.
Attached PHY Identifier: field contains the SAS PHY received by this PHY during an Identify Sequence.
Programmed Minimum Phy Link Rate: set to 8h to indicated 1.5G minimun.
Hardware Minimum Phy Link Rate: hardware minimum is set to 8h to indicated 1.5G minimun.
Programmed Maximum Phy Link Rate: set to 9h to indicated 3.0G maximum.
Hardware Maximum Phy Link Rate: hardware maximum is set to 9h to indicated 3.0G maximum.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
148
18.10.13 Mode Page 1A (Power Control)
Table 100: Page 1A (Power Control)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 1Ah
Default
9Ah
1
Page Length = 0Ah
0Ah
2
Reserved = 00h
00h
3
Reserved = 0
Idle
Standby
(MSB)
00h
00h
Idle Condition Timer = 0
4-7
(LSB)
00h
(MSB)
8-11
Standby Condition Timer
(LSB)
• The value for the Idle Condition Timer and the corresponding Idle control bit is accepted. Despite this, the drive does
not alter the internal power saving algorithms based upon this value.
• Standby bit of one indicates that the Target shall use the Standby Condition Timer to determine the length of inactivity
time to wait before entering the Standby condition. A standby bit of zero indicates that the Target shall not enter the
Standby condition.
• Standby Condition Timer field indicates the inactivity time in 100 millisecond increments that the Target shall wait
before entering the Standby condition. The minimum allowable inactivity time is 60 minutes. Any value less than this
is accepted, but will automatically default to 60 minutes.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
149
18.10.14 Mode Page 1C (Informational Exceptions Control)
Table 101: Page 1C (Informational Exceptions Control)
BIT
Byte
0
7
6
PS
0
5
3
2
1
0
Page Code = 1Ch
1
2
4
9Ch
Page Length = 0Ah
PERF
3
RSVD
EBF
EWASC DEXCPT
Reserved = 0
Default
0Ah
TEST
EBACKLOGERR
ERR
Method of Reporting
10h
00h
00h
(MSB)
4-7
00h
Interval Timer
(LSB)
00h
00h
00h
(MSB)
8-11
Report Count
(LSB)
• PERF (Performance) bit is not used and ignored internally by the Target.
• EBF (Enable Background Function)bit is not used and ignored internally by the drive.
• EWASC (Enable Warning ASC) bit of zero indicates that Temperature Warning will not be reported. An EWASC bit of
one allows Temperature Warning to be reported when DEXCPT bit is set to zero. If the temperature reading inside of
DE exceeds the threshold (default or set by Mode Select Page 0), Recovered Error (Sense Key 01h, ASC 0Bh, ASCQ
01h) will be reported.
DEXCPT bit of zero indicates that informational exception operations shall be enabled. The reporting of informational exception conditions when the DEXCPT bit is set to zero is determined from the method of reporting informational exceptions field.
Note: Disable exception control (DEXCPT) bit of zero indicates the failure prediction threshold exceeded reporting
shall be enabled. The method for reporting the failure prediction threshold exceeded when the DEXCPT bit is set to
zero is determined from the method of reporting informational exceptions field. A DEXCPT bit of one indicates the
Target shall disable reporting of the failure prediction threshold exceeded. The method of reporting informational
exceptions field is ignored when DEXCPT is set to one and EWASC is set to zero.
• 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. The method of reporting these errors is determined from the MRIE field.
• LOGERR (Log Errors) is not used and ignored internally by the Target.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
150
• Method of Reporting Informational Exceptions indicates the methods used by the Target to report informational exception conditions.
Code
Description
0h
No reporting of informational exception condition: This method instructs the Target to not report informational exception condition.
1h
Asynchronous event reporting: Not supported.
2h
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.
3h
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.
4h
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.
5h
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.
6h
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.
7h-Fh 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
151
18.10.14.1 Background Control (Subpage 01h)
Table 102: Background Control (Subpage 01h)
BIT
Byte
0
7
6
PS
SPF=1
5
4
3
2
1
0
Page Code = 1Ch
Default
5Ch
1
Subpage Code = 01h
01h
2-3
Page Length = 0Ch
000Ch
4
Reserved = 0
EN_BMS
00h
5
Reserved = 0
EN_PS
00h
6-7
BMS Interval Time
0000h
8-9
Pre-Scan Timeout Value = 000h
0000h
10-15
Reserved = 0
00h
• 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 prescan operation is started after the next power-on cycle. Once this pre-scan has completed, another pre-scan shall not
occur unless then EN_PS bit is set to zero, then set to one, and another power-on cycle occurs.
• BMS Interval Time specifies the minimum time, in hours, between the end of one background medium scan operation
and the start of the enxt background medium scan operation. The BMS Interval Time shall occur before the initial
background medium scan operation is started.
• Pre-Scan Timeout Value 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 timeout
value.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
152
18.11 MODE SENSE (5A)
Table 103: Mode Sense (5A)
Bit
Byte
7
6
5
0
Reserved = 0
2.
PCF
3-6
9
3
2
1
0
Command Code = 5Ah
1
7-8
4
DBD
Reserved = 0
Page Code
Reserved = 0
(MSB)
Allocation Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
•
The Parameters Savable (PS) bit is set to one, indicating the the paramaters are saveable.
•
The SPF field shall be set to zero for access to the short format mode page.
•
Protocol Identifier has a value of 6h indicating this is a SAS SSP specific mode page.
•
The I_T NEXUS LOSS TIME field 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 that the function is disabled. A value of
FFFFh indicates an unlimited period. The default value of 7D0h, specifies a 2 second time period.
•
INITIATOR RESPONSE TIMEOUT field 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 will be aborted. An INITIATOR RESPONSE TIMEOUT field value of zero indicates that the SSP target port shall disable the timer. The default value of 7D0h, specifies a 2 second time period.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
153
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
154
18.12 PERSISTENT RESERVE IN (5E)
Table 104: Persistent Reserve In (5E)
Bit
Byte
7
6
5
0
4
Reserved = 0
1
0
Service Action
2-6
9
2
Command Code = 5Fh
1
7-8
3
Reserved = 0
(MSB)
Allocation Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The PERSISTENT RESERVE IN command is used to obtain information about persistent reservations and reservation keys
that are active within the controller. This command is used in conjunction with the PERSISTENT RESERVE OUT command
“PERSISTENT RESERVE OUT (5F)” on page 158.
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.
18.12.1 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.
Table 105: PERSISTENT RESERVE IN, Service Action Codes
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
Reserved
Reserved
04h-1Fh
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
155
18.12.2 Parameter data for Read Keys
Table 106: PERSISTENT RESERVE IN, parameter data for Read Keys
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0-3
Generation
(LSB)
(MSB)
4-7
Additional length (n-7)
(LSB)
(MSB)
8-15
First reservation key
(LSB)
:
(n-7)
-
(MSB)
Last reservation key
(LSB)
n
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
156
18.12.3 Parameter Data for Read Reservations
Table 107: PERSISTENT RESERVE IN, parameter data for Read Reservations
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0-3
Generation
(LSB)
(MSB)
4-7
Additional length (n-7)
(LSB)
(MSB)
8-n
Reservation descriptors
(LSB)
The Generation field shall be as defined for the Persistent Reserve In Read Keys parameter data. The Additional Length field
contains a count of the number of bytes to follow in the Reservation Descriptor(s).
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.
Table 108: PERSISTENT RESERVE IN, Read Reservation Descriptor
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0-7
Reservation key
(LSB)
(MSB)
8-11
Scope-specific address
(LSB)
12
Reserved
13
Scope=0
Type
(MSB)
14-15
Extent Length=0
(LSB)
.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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
157
18.13 PERSISTENT RESERVE OUT (5F)
Table 109: PERSISTENT RESERVE OUT (5F)
Bit
Byte
7
6
5
0
1
4
3
2
0
FLAG
LINK
Command Code = 5Fh
Reserved = 0
2
Service Action
Scope=0
Type
3-6
Reserved = 0
7-8
Parameter List Length = 18h
11
1
VU = 0
Reserved = 0
The PERSISTENT RESERVE OUT command is used to request service actions that reserve the drive for the exclusive or
shared use of the initiator. The command uses other service actions to manage and remove such reservations. 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.
.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
158
18.13.1 Service Action
The following service action codes are supported.
Table 110: PERSISTENT RESERVE OUT, Service Action Code
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
Register a reservation key
existing key
07h-1Fh
Reserved
Reserved
18.13.2 Type
The Type field specifies the characteristics of the persistent reservation being established for all customer data sectors.
Thetable below describes the supported types and how read and write commands are handled for each reservation type.
Table 111: PERSISTENT RESERVE OUT, Type Code
Code
0h
Name
Description
Reserved
Reserved
1h
Write Exclusive
Reads Shared: Any initiator may execute commands
that transfer from the 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
3h
Exclusive Access
Reads Exclusive: Only the initiator with the reservation may execute commands that transfer data from the
media; Reservation Conflict status will be returned to
other initiators.
Writes Exclusive: Only the initator with the reservation may execute commands that transfer data to the
media; Reservation Conflict status will be returned to
other initators.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
159
4h
Reserved
Reserved
Reads Shard: Any initiator may execute commands
that transfer from media.
Write Exclusive
Registrants Only
5h
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
initiators.
Exclusive Access
Registrants Only
6h
7h-Fh
Writes Exclusive: Only registered initiators may execute commands that transfer data to the media; Reservation Conflict status will be returned to other
initiators.
Reserved
Reserved
18.13.3 Parameter list
The Parameter List required to perform the PERSISTENT RERSERVE OUT command is defined in the table below. All
fields must be sent on all PERSISTENT RESERVE OUT commands, even if the field is not required for the specified service
action.
Table 112: Parameter List
Bit
Byte
7
6
5
4
3
2
1
0
(MSB)
0-7
Reservation Key
(LSB)
(MSB)
8-15
Service Action Reservation Key
(LSB)
(MSB)
16-19
Scope-Specific Address
(LSB)
20
21-23
Reserved = 0
APTPL
Reserved = 0
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
160
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.
Scope-Specific Address is ignored.
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.
18.13.4 Summary
Table 113: PERSISTENT RESERVE OUT, Service Action, Parameters
Parameters
Service Action
Generation
counter
Scope
Rsv
SvcAct
S-spec
Extent
Type
Key
RsvKey
addr
length
(0) Register
ignore
verify
save
ignore
ignore
apply
+1
(1) Reserve
apply
verify
ignore
ignore
ignore
ignore
---
(2) Release
apply
verify
ignore
ignore
ignore
ignore
---
(5) Preempt and
Abort
apply
verify
save
ignore
ignore
ignore
+1
APTPL
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
161
18.13.4.1 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.
18.13.4.2 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.
18.13.4.3 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.
18.13.4.4 Scope-specified address
Parameter in the Scope-specified address field is ignored by the drive.
18.13.4.5 Extent length
Parameter in the Extent length field is ignored by the drive.
18.13.4.6 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.
Table 114: APTPL and information held by a drive
The last valid APTPL value
Information
held by the drive
Registration
Persistent Reservation
Generation counter
0
1
all keys are set to 0
retained
all are removed
retained
set to 0
set to 0
18.13.4.7 Generation counter
The drive increments the Generation counter when Register service action or Preempt and Clear service action complete successfully.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
162
18.14 PRE-FETCH (34)
Table 115: PRE-FETCH (34)
Bit
Byte
7
6
5
0
4
3
2
1
0
Immed
=0
RelAdr
=0
Command Code = 34h
1
Reserved = 0
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the Initiator.
•
Transfer length field specifies the number of contiguous blocks of data that are to be transferred into the cache. 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.
•
RelAdr Relative Block Address is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
163
18.15 READ (6) - (08)
Table 116: READ (6) - (08)
Bit
Byte
7
6
5
0
1
3
2
1
0
Command Code = 08h
Reserved = 0
(MSB)
LBA
Logical Block Address
2-3
(LSB)
4
5
4
Transfer Length
VU = 0
Reserved = 0
FLAG
LINK
The READ command requests the drive to transfer from the medium to the initiator the specified number of blocks (Transfer
Length) starting at the specified Logical Block Address (LBA).
•
Logical block address field specifies the logical unit at which the READ operation shall begin.
•
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
164
18.16 READ (10) - (28)
Table 117: READ (10) - (28)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 28h
1
Reserved = 0
DPO
FUA
Reserved = 0
RelAdr
=0
(MSB)
2-5
Logical Block Address
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
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.
•
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.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero. Relative addressing is not supported. If
RelAdr 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.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
165
18.17 READ BUFFER (3C)
Table 118: READ BUFFER (3C)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 3Ch
1
Reserved = 0
Mode
2
Buffer ID = 0
(MSB)
3-5
Buffer Offset
(LSB)
(MSB)
6-8
Allocation Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The READ BUFFER command is used in conjunction with the WRITE BUFFER command as a diagnostic function for testing the memory of the drive and the SCSI bus integrity. This command does not alter the medium.
The function of this command and the meaning of fields within the command descriptor block depend on the contents of the
mode field.
MODE
Description
00000
Read Combined Header and Data
00010
Read Data
00011
Descriptor
01010
Read Data from Echo Buffer
01011
Echo Buffer Descriptor
11010
Enable Expander Communications Protocol and Echo Buffer
All others
Not supported
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
166
18.17.1 Combined Header And Data (Mode 00000b)
In this mode a 4-byte header followed by data bytes is returned to the Initiator during the DATA IN phase. The Buffer ID and
the buffer offset field are reserved.
The drive terminates the DATA IN phase when allocation length bytes of header plus data have been transferred or when the
header and all available data have been transferred to the Initiator, whichever is less.
The 4-byte READ BUFFER header (see figure below) is followed by data bytes from the data buffer of the drive.
Table 119: Read Buffer Header
Bit
Byte
7
0
1-3
6
5
4
3
2
1
RSVD = 0
(MSB)
Buffer Capacity
(LSB)
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.
18.17.2 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 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.
•
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
167
18.17.3 Descriptor (Mode 00011b)
In this mode, a maximum of four bytes of READ BUFFER descriptor information are returned. The drive returns the descriptor information for the buffer specified by the Buffer ID.
•
Buffer ID field should normally be set to zero, indicating the drive data transfer buffer. If any other value is specified,
the drive returns all zeros in the READ BUFFER descriptor.
•
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 transfered.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.
Table 120: Read Buffer Description
Bit
Byte
7
0
1-3
6
5
4
3
2
1
Offset Boundary = 0x09
(MSB)
Buffer Capacity
(LSB)
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
168
18.17.4 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.
18.17.5 Echo Buffer Descriptor (Mode 01011b)
In this mode, a maximum of four bytes of Read Buffer Descriptor information is returned. The drive returns the descriptor
information for the echo buffer. The Buffer Offset field is reserved in this mode and must be zero. The drive transfers the lesser
of the allocation length or four bytes of following Echo Buffer Descriptor.
Table 121: Echo Buffer Descriptor
Bit
Byte
7
6
5
0
3
3
2
1
Reserved = 0
1
2
4
0
EBOS=0
Reserved = 0
Reserved = 0
(MSB) Buffer Capacity
Buffer Capacity
(LSB)
•
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.
18.17.6 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).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
169
18.18 READ CAPACITY (10) - (25)
Table 122: READ CAPACITY (10) - (25)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 25h
1
Reserved = 0
RelAdr
=0
Reserved = 0
(MSB)
2-5
Logical Block Address
(LSB)
6-7
Reserved = 0
8
Reserved = 0
9
VU = 0
Reserved = 0
PMI
FLAG
LINK
The READ CAPACITY command returns information regarding the capacity of the drive.
•
Logical Block Address is used in conjunction with the PMI bit.
•
RelAdr (Relative Address) is not supported. Must be set to zero.
•
PMI (Partial Medium Indicator) indicates:
PMI
Description
0
The drive returns the last LBA of the drive.
1
The drive returns the last LBA and block length in bytes are that of the LBA after which a substantial delay
in data transfer will be encountered. This returned LBA shall be greater than or equal to the LBA specified
by the LBA fields in the CDB.
This option provides the information that the Initiator needs to determine the amount of space available on the same track
that is accessible without a head switch or seek.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
170
18.18.0.1 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.
Table 123: Format of READ CAPACITY command reply
Bit
Byte
6
7
5
4
3
2
1
0
(MSB)
Maximum Logical Block Address
0-3
(LSB)
(MSB)
4-7
Block Length
(LSB)
•
Block Length specifies the length in bytes of the block.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
171
18.19 READ CAPACITY (16) (9E/10)
Table 124: Read Capcity (16) (9E/10)
Bit
Byte
6
7
5
0
4
3
2
1
0
Command Code = 9Eh
1
Reserved = 0
Service Action = 10h
(MSB)
2-9
Logical Block Address
(LSB)
(MSB)
10-13
Allocation Length
(LSB)
14
15
Reserved = 0
VU = 0
Reserved = 0
PMI
FLAG
Link
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
172
18.20 READ DEFECT DATA (37)
Table 125: READ DEFECT DATA (37)
Bit
Byte
7
6
5
0
Reserved = 0
2
Reserved = 0
3-6
9
3
2
1
0
Command Code = 37h
1
7-8
4
Reserved = 0
Plist
Glist
0
Defect List Format
Reserved = 0
(MSB)
Allocation Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
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 a 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
173
Table 126: Defect List Format
Preferred Defect List Format
Returned Defect List Format
Block (000b)
Physical Sector
Bytes from Index (100b)
Bytes from Index
Physical Sector (101b)
Physical Sector
Vendor Unique (110b)
Physical Sector
Reserved (001b)
Reserved (010b)
Reserved (011b)
Reserved (111b)
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
174
18.20.1 Defect List Header
Table 127: Defect List Header
Bit
Byte
7
6
5
4
3
2
1
0
Defect List Header
0
Reserved = 0
1
2-3
Reserved = 0
Plist
(MSB)
Glist
Defect List Format
Defect List length
(LSB)
18.20.2 Defect List Descriptor
Table 128: Defect List Descriptor
Bit
Byte
7
6
5
4
3
2
1
Defect List Descriptor
0-7
Defect Descriptor 0
.
8n (8n+7)
Defect Descriptor n
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
175
0
18.20.3 Bytes from Index Format (100b)
Table 129: Defect Descriptors of Bytes from Index Format
Byte
Defect Descriptors
(MSB)
0-2
Cylinder Number of Defect
(LSB)
3
Head Number of Defect
(MSB)
Defect Bytes from Index
4-7
(LSB)
Defect Bytes from Index is gotten using the following equation:
Bytes from Index = (Physical Sector Number) * N
Where: N = Bytes per sector
18.20.4 Physical Sector Format (101b)
Table 130: Defect Descriptors of Physical Sector Format
Byte
Defect Descriptors
(MSB)
0-2
Cylinder Number of Defect
(LSB)
3
Head Number of Defect
(MSB)
4-7
Defective Sector Number
(LSB)
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 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
176
18.21 READ DEFECT DATA (B7)
Table 131: READ DEFECT DATA (B7)
Bit
Byte
7
6
5
0
3
2
1
0
Command Code = B7h
1
Reserved = 0
Plist
2-5
6-9
4
Glist
Defect List Format
Reserved = 0
(MSB)
Allocation Length
(LSB)
10
Reserved = 0
11
VU = 0
Reserved = 0
FLAG
LINK
1
0
(See Section 18.20 “READ DEFECT DATA (37)” on page 173.)
18.21.1 Defect List Header
Table 132: Defect List Header
Bit
Byte
7
6
5
4
3
2
Defect List Header
0
Reserved = 0
1
Reserved = 0
2-3
Plist
Glist
Defect List Format
Reserved = 0
(MSB)
4-7
Defect List length
(LSB)
(See Defect List Header for Read Defect Data (37) in Section Table 18.20.1, “Defect List Header,” on page 175.)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
177
18.21.2 Defect List Descriptor
Table 133: Defect List Descriptor
Bit
Byte
7
6
5
4
3
2
1
0
Defect List Descriptor
0-7
Defect Descriptor 0
.
8n (8n+7)
Defect Descriptor n
(See Defect List Descriptor for Read Defect Data (37) in Section 18.20.2 “Defect List Descriptor” on page 175.)
18.21.3 Bytes from Index Format (100b)
Table 134: Defect Descriptors of Bytes from Index Format
Byte
Defect Descriptors
(MSB)
0-2
Cylinder Number of Defect
(LSB)
3
Head Number of Defect
(MSB)
4-7
Defect Bytes from Index
(LSB)
Defect Bytes from Index is derived using the following equation:
Bytes from Index = (Physical Sector Number) + N
where N = Bytes per sector.
18.21.4 Physical Sector Format (101b)
Table 135: Defect Descriptors of Physical Sector Format
Byte
Defect Descriptors
(MSB)
0-2
Cylinder Number of Defect
(LSB)
3
Head Number of Defect
(MSB)
4-7
Defective Sector Number
(LSB)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
178
18.22 READ LONG (3E)
Table 136: READ LONG (3E)
Bit
Byte
7
6
5
0
4
3
2
1
0
Correct
RelAdr
Command Code = 3Eh
1
Reserved = 0
Reserved = 0
=0
=0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Byte Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The READ LONG command requests the drive to transfer one block of data to the Initiator. The transfer data includes data and
ECC field data.
•
Correct bit of zero causes the logical block to be read without any correction attempts. When the bit is one, data will
be corrected with offline ECC correction before being transferred.
•
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 nonzero 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 + 43
•
RelAdr (Relative Block Address) is not supported by the drive.
The data read by this command is neither read from nor retained in the cache.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
179
18.23 REASSIGN BLOCKS (07)
Table 137: REASSIGN BLOCKS (07)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 07h
1
Reserved = 0
Reserved = 0
2
3
Reserved = 0
4
5
VU = 0
Reserved = 0
FLAG
LINK
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
180
Following is the format of the data sent by the Initiator during the DATA OUT phase.
Table 138: Format of Reassign Blocks data
Bit
Byte
7
6
5
4
0
Reserved = 0
1
Reserved = 0
(MSB)
2-3
3
2
1
Defect List Length = 4/8/12/16
(LSB)
(MSB)
4-7
Defect Logical Block Address 1
(LSB)
(MSB)
8-11
Defect Logical Block Address 2
(LSB)
(MSB)
12-15
Defect Logical Block Address 3
(LSB)
(MSB)
16-19
Defect Logical Block Address 4
(LSB)
•
Defect List Length must be 4, 8, 12, or 16. Otherwise, the drive returns Check Condition with a sense key of Illegal
Request.
•
Defective Logical Block Address is four bytes in length. The Initiator can specify from 1 to 4 Defective Logical
Block Addresses according to the Defect List Length from 4 to 16, respectively. LBAs are not required to be in
ascending order.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
181
18.24 RECEIVE DIAGNOSTICS RESULTS (1C)
Table 139: RECEIVE DIAGNOSTIC RESULTS (1C)
Bit
Byte
7
6
5
0
3
2
1
Reserved = 0
2
Reserved = 0
PCV
Page Code
(MSB)
Allocation Length
4
5
0
Command Code = 1Ch
1
3
4
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTIC command be sent to the Initiator.
•
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.
This command may also be used to retrieve a Diagnostic Page from an enclosure.
When requested to communicate with the enclosure via the Send and RECEIVE DIAGNOSTIC commands, the Target goes
through a 'discovery phase' with the enclosure as defined in the SFF-8067 standard. The results of this 'discovery phase', determine whether the enclosure: 1) does not support Enclosure Services, 2) supports only the 'short' Enclosure Service mode as
defined by SFF-8045, or 3) supports the 'long' Enclosure Service mode as defined by SFF-8067. After the 'discovery phase' the
drive behaves in accordance with the Enclosure Service mode capabilities of the enclosure. The drive does not attempt to
remember the Enclosure Service capabilities of the enclosure, but rather, in accordance with the SFF-8067 standard, re-performs the 'discovery phase' for each Send and RECEIVE DIAGNOSTIC command received.
If the Target determines that the enclosure does not support Enclosure Services, any attempts to access the Diagnostic Pages in
the enclosure will result in CHECK CONDITION status and sense data is built with the Sense Key and Additional Sense Code
indicating ENCLOSURE SERVICES UNAVAILABLE. In this case, only the Diagnostic Pages supported by the Target may
be requested.
If the Target determines that the enclosure supports the 'short' form of Enclosure Services, Diagnostic Page 08h is returned in
response to a request for any valid Diagnostic Page (i.e. 01h-0Fh).
If the Target determines that the enclosure supports the 'long' form of Enclosure Services, a request for the page is passed on to
the enclosure. Any diagnostic information returned to the Target is transferred to the Initiator. If the request for enclosure
transfer fails, the command is terminated with CHECK CONDITION status and sense data is built with the Sense Key and
Additional Sense Code indicating ENCLOSURE SERVICES UNAVAILABLE.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
182
18.24.1 Receive Diagnostic Results Page 0
This page contains a list of supported pages.
Table 140: Receive Diagnostic Results page 0
Bit
Byte
7
6
5
4
3
0
Page Code = 0
1
Reserved = 0
2-3
Page Length = 12h
5-19
(Supported Pages) Page = 0h
20
CJTPAT page = 3Fh
21
Translate address page = 40h
2
1
The supported diagnostic page returns a list of supported pages in ascending order.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
183
0
18.24.2 Receive Diagnostic Results Page 40
Using the SEND DIAGNOSTIC command, an address in either physical or logical format is supplied to the drive. This page is
then used to retrieve the address translated into the other format.
Table 141: Receive Diagnostic Results Page 40
Byte
Bit
7
6
5
4
3
0
Page Code = 40h
1
Reserved = 0
2-3
Page Length
4
5
Reserved = 0
RA
ALTS
ALTT
6-n
2
1
0
Supplied format
Reserved=0
Translate format
Translated Address
•
Page Length is set to 02h if the address is in a Reserved Area (RA =1). Otherwise, Page Length is set to 06h if the
Translate Format is Block format, or 0Ah if the Translate Format is Bytes From Index format or Physical Sector format.
•
Supplied Format is the value supplied by the SEND DIAGNOSTIC command; it may be one of the three following
values:
- 000b 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 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 Block format. Otherwise the Target will terminate the command with Check Condition
status.
•
RA (Reserved Area) is set to on 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. If it is an LBA, it is contained within the first four
bytes of the field (bytes 6 to 9) of the page data. For a physical format it is as follows:
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
184
Table 142: Translated address
Bit
Byte
7
6
5
4
3
2
6-8
Cylinder Number
9
Head Number
10-13
Sector Number or Bytes from Index
1
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
185
0
18.25 RELEASE (17)
Table 143: RELEASE (17)
Bit
Byte
7
6
5
0
1
4
3
2
0
Command Code = 17h
Reserved = 0
3rdPty=0
3rd Party ID
2
Reservation Identification
3-4
Reserved = 0
5
1
VU = 0
Reserved = 0
Ext=0
FLAG
LINK
The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that
is not currently active. The drive returns Good status without altering the reservation.
•
3rdPty must be 0. Third Party reservations are not supported. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
186
18.26 RELEASE (57)
Table 144: RELEASE (57)
Bit
Byte
7
6
5
0
1
4
3
2
0
Command Code = 57h
Reserved = 0
2
3rdPty=0
Reserved = 0
Ext = 0
Reservation Identification
3
3rd Party Device ID
4-8
Reserved = 0
9
1
VU = 0
Reserved = 0
FLAG
LINK
The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that
is not currently active. The drive returns Good status without altering the reservation.
•
3rdPty must be 0. Third Party reservations are not supported. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
187
18.27 REPORT DEVICE IDENTIFIER (A3/0C)
Table 145: REPORT DEVICE IDENTIFIER (A3/0C)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = A3h
1
Reserved = 0
2
Service Action = 0Ch
Reserved = 0
Service Action = 0Ch
3
Requested Operation Code
4-5
Requested Service Action
6-9
Allocation Length
10
Reserved = 0
11
VU = 0
Reserved
FLAG
LINK
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.
Reporting Options specifies the information to be returned in the parameter data.
Recording Option
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
010b
011b-111b
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.
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.
Reserved
Requested Operation Code specifies the opertion 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
188
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.
18.27.1 All_commands parameter data format
The Report Supported Operation Codes all_command parameter data format begins with a four-byte header that contains the
length in bytes of the parameter data, followed by a list of supported commands. Each command descriptor contains information about a single supported command CDB (i.e. one operation code and service action combination, or one non-serviceaction
operation code).
Bit
Byte
7
6
5
4
3
0-3
Command Data Length (n-3)
4
Command Descriptor 0
N
Command Descriptor X
2
1
0
Each Command Descriptor contains information about a single supported command CDB.
Bit
Byte
7
6
5
4
3
0-3
Operation Code
1
Reserved = 0
2-3
Service Action
4
Reserved = 0
5
6-7
2
1
Reserved = 0
0
Servactv
CDB Length
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.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
189
18.27.2 One_command parameter data format
The Report Supported Operation Codes one_command parameter data format contains information about the CDB and a usage
map for bits in the CDB for the command specified by the Reporting Options, Requested Operation Code, and Requested Service Action fields in the Reported Supported Operation Codes CDB.
Bit
Byte
7
6
5
0
4
3
2
1
0
Reserved = 0
1
Reserved = 0
Support
2-3
CDB Size (n-3)
4-n
CDB Usage Data
The Support field is defined in the table below.
Recording Option
000b
001b
Description
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.
010b
Reserved.
011b
The requested command is supported in conformance with the standard.
100b
Reserved
101b
The requested command is supported in a vendor specific manner.
110b-111b
Reserved.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
190
18.28 REPORT LUNS (A0)
Table 146: REPORT LUNS (A0)
Bit
Byte
7
6
5
4
3
0
Command Code = A0h
1-5
Reserved
2
1
0
(MSB)
6-9
Allocation Length
(LSB)
10
Reserved
11
VU = 0
Reserved = 0
FLAG
LINK
The REPORT LUNS command requests that the Target return the known LUN to the Initiator. The REPORT LUNS command
should always be available and is unaffected by any reservations.
The Allocation Length must be at least 16 bytes. 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.
Table 147: LUN Reporting parameter list format
Bit
Byte
7
0-3
(MSB)
6
5
4
3
2
1
0
LUN List Length = 8
(LSB)
4-7
Reserved
(MSB)
8-15
LUN = 0
(LSB)
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
191
18.29 REPORT SUPPORTED TASKS MANAGEMENT FUNCTIONS
(A3/0D)
Table 148: Report Supported Tasks Management Functions (A3/0D)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = A3h
1
Reserved = 0
Service Action = 0Dh
2-5
Reserved = 0
6-9
Allocation Length
10
Reserved = 0
11
VU = 0
Reserved = 0
Flag
Link
The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command requests information on task management
functions supported by the drive.
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
0
1-3
7
6
5
4
3
2
1
0
ATS
ATSS
CACAS
CTSS
LURS
QTS
TRS
WAKES
Reserved = 0
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
192
18.30 REQUEST SENSE (03)
Table 149: REQUEST SENSE (03)
Bit
Byte
7
6
5
0
1
4
3
1
0
FLAG
LINK
Command Code = 03h
Reserved = 0
Reserved = 0
2-3
Reserved = 0
4
Allocation Length
5
2
VU = 0
Reserved = 0
The REQUEST SENSE command requests the drive to transfer sense data.
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 shall 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.
The drive will return the number of bytes in the allocation length or 32 bytes, whichever is less.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
193
18.31 RESERVE (16)
Table 150: RESERVE (16)
Bit
Byte
7
6
5
0
Reserved = 0
2
5
3
2
1
0
Command Code = 16h
1
3-4
4
3rdPty=0
3rd Party ID
Ext=0
Reservation Identification
(MSB)
Extent List Length = 0
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the
command or for a third party as specified by the Initiator.
Extents are not supported by the drive. The Ext bit must be zero. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
194
18.32 RESERVE (56)
Table 151: RESERVE (56)
Bit
Byte
7
6
5
0
4
3
2
Reserved = 0
3rdPty=0
Reserved
2
Reservation Identification
3
Third Pay Device ID
4-6
Reserved = 0
9
0
Command Code = 57h
1
7-8
1
(MSB)
Ext=0
Extent List Length = 0
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the
command or for a third party as specified by the Initiator.
Extents are not supported by the drive. The Ext bit must be zero. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
195
18.33 REZERO UNIT (01)
Table 152: REZERO UNIT (01)
Bit
Byte
7
6
5
0
1
3
2
1
0
FLAG
LINK
Command Code = 01h
Reserved = 0
2-4
5
4
Reserved = 0
Reserved = 0
VU = 0
Reserved = 0
The REZERO UNIT command requests that the Target seek LBA 0.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
196
18.34 SEEK (6) - (0B)
Table 153: SEEK (6) - (0B)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 0Bh
1
Reserved = 0
(MSB)
2
LBA
Logical Block Address
3
(LSB)
4
Reserved = 0
5
VU = 0
Reserved = 0
FLAG
LINK
The SEEK (6) command requests the drive to seek the specified LBA. If the LBA is greater than the value returned by the
READ CAPACITY command, the Drive returns a Check Condition status with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
18.35 SEEK (10) - (2B)
Table 154: SEEK (10) - (2B)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 2Bh
1
Reserved = 0
Reserved = 0
0
(MSB)
Logical Block Address
2-5
(LSB)
6-8
9
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The SEEK (10) command requests the drive to seek the specified LBA. If the LBA is greater than the value returned by the
READ CAPACITY command, the Drive returns a Check Condition status with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
197
18.36 SEND DIAGNOSTIC (1D)
Table 155: SEND DIAGNOSTIC (1D)
Bit
Byte
7
6
5
0
Function Code
2
5
3
2
1
0
SlfTst
Dev0fl
Unt0fl
Command Code = 1Dh
1
3-4
4
PF
RSVD =0
Reserved = 0
(MSB)
Parameter List Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The SEND DIAGNOSTIC command requests the drive to perform its self-diagnostic test or to perform a function based on a
page of information sent in a Data Out phase during the command.
•
PF (Page Format) bit set to one indicates the data sent by the Initiator conform to the page structure as specified in
SCSI-2 standard. This bit must be set to one if the SlfTst bit is set to zero. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
198
Table 156: SEND DIAGNOSTIC Function Code (1D)
Value
Function name
Description
000b
NA
Value to be used when the SlfTst bit is set to one or if the
SEND DIAGNOSTIC command is not invoking one of the
other self-test function codes.
001b
Background Short self-test
The device server starts its short self-test routine in background mode.
010b
Background extended self-test
The device server starts its extended self-test routine in
background mode.
011b
NA
Reserved.
100b
Abort background self-test
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.
101b
Foreground short self-test
The device server starts its short self-test routine in the foreground mode. This self-test will complete in two minutes or
less.
110b
111b
Foreground extended self-test
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 17.11.9 "Mode
Page 0A).
Reserved.
•
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 21.19 "Diagnostics" on page 292 for a detailed listing of operations carried out by the SEND DIAGNOSTIC command and Power on Diagnostics.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
199
18.36.1 Send Diagnostic Page 0
This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS command.
Table 157: Diagnostic Page 0
Bit
Byte
7
6
5
4
3
0
Page Code = 0
1
Reserved = 0
2-3
2
1
0
2
1
0
Page Length = 0
18.36.2 Send Diagnostic Page 3F
Table 158: Diagnostic Page 3F
Bit
Byte
7
6
5
0
4
3
Page Code = 3F
1
Reserved = 0
2-3
Protocol Identifier = 6
Page Length = 1Ch
4
Phy Identifier
5
Phy Test Function
6
Phy Test Pattern
7
Reserved = 0
8-31
Phy Test Pattern Physical Link Rate
Reserved = 0
•
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
200
Phy Test Pattern
00h
01h
02h-FFh
•
•
Descripton
If the selected phy is performing
a phy-test function, then the
selected phy-shall 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 shall 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
Link Rate field and set to ignore
its receiver.
Unsupported
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
Descripton
00h
Reserved
01h
Not supported.
03h-EEh
Reserved
F0h
Vendor Unique: continuously
transmit the K28.5 character.
02h
CJTPAT
F1h - FFh
Reserved
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, and 9h for 3.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.
18.36.3 Send Diagnostic Page 40
This allows the Initiator to translate a LBA or physical sector address to the other format. The address to be translated is passed
to the Target with the SEND DIAGNOSTIC command and the results are returned to the Initiator by the RECEIVE DIAGNOSTICS command.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
201
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.
Table 159: Diagnostic Page 40
Bit
Byte
7
6
5
0
4
3
2
1
0
Page Code = 40h
1
Reserved = 0
2-3
Page Length = 0Ah
4
Reserved = 0
Supplied format
5
Reserved = 0
Translate format
6-13
Address to Translate
Supplied Format may take one of the following three values:
- 000b Block format
- 100b Bytes From Index format
- 101b Physical Sector format
It specifies the format in which the address has been supplied.
•
Translate Format specifies the format that the address should be translated into. If the supplied format is the 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 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 logical block format is specified, the first four bytes of
the field (bytes 6 to 9) contain the LBA and the remainder must be zero. For the physical format the address must be
specified as follows.
Table 160: Address to translate
Bit
Byte
7
6
5
4
3
2
6-8
Cylinder Number
9
Head Number
10-13
Sector Number or Bytes from Index
1
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
202
0
18.37 SET DEVICE IDENTIFIER (A4/06)
Table 161: SET DEVICE IDENTIFIER (A4/06)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = A4h
1
Reserved = 0
Service Action = 06h
2
Reserved = 0
3
Reserved = 0
4-5
Restricted = 0
(MSB)
6-9
Parameter List Length
(LSB)
10
Reserved = 0
11
VU = 0
Reserved = 0
FLAG
LINK
The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the
SET DEVICE IDENTIFIER parameter list.
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.
Table 162: SET DEVICE IDENTIFIER, Parameter List
Bit
Byte
7
0-n
6
5
4
3
2
1
0
Identifier
The IDENTIFIER field is a vendor specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
203
18.38 START STOP UNIT (1B)
Table 163: START STOP UNIT (1B)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 1Bh
1
Reserved = 0
2-3
Reserved = 0
Immed
Reserved = 0
4
Power Conditions = 0
5
VU = 0
Reserved=0
Reserved = 0
LoEj
=0
FLAG
Start
LINK
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 is not supported by the drive and must be set to 0.
•
LoEj is not supported by the drive and must be set to 0.
•
Start bit is to specify:
0
1
stop the spindle
start the spindle
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
204
18.39 SYNCHRONIZE CACHE (35)
Table 164: SYNCHRONIZE CACHE (35)
BIT
Byte
7
6
5
0
4
3
2
1
0
Immed
=0
RelAdr
=0
Command Code = 35h
1
Reserved = 0
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Number of Blocks
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded
on the media.
•
Logical Block Address is to specify where the operation is to begin.
•
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.
•
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.
•
RelAdr (Relative Address) must be zero. The drive does not support the relative addressing. If the RelAdr bit is set to
one, the drive returns 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
205
18.40 TEST UNIT READY (00)
Table 165: TEST UNIT READY (00)
Bit
Byte
7
6
5
0
1
3
2
1
0
FLAG
LINK
Command Code = 00h
Reserved = 0
2-4
5
4
Reserved = 0
Reserved = 0
VU = 0
Reserved = 0
The TEST UNIT READY command allows the Initiator to check if the drive is READY. The SCSI specification defines
READY as the condition where the device will accept a media-access command without returning Check Condition status.
The drive will first verify that the motor is spinning at the correct speed. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
206
18.41 VERIFY (2F)
Table 166: VERIFY (2F)
BIT
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
RSVD
=0
Command Code = 2Fh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Verification Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that
no data will be transferred. This condition is not considered an error.
•
ByteChk bit set to zero indicates that the data is read from the disk and verified using ECC.If an ECC error is
detected in the verify process, Check Condition status is returned with sense key set to Medium Error. ByteChk bit
set to one indicates that byte-by-byte comparison is performed between the data on the disk and data transferred from
the initiator during the data-out phase.
If the comparison is unsuccessful, the command is terminated with Check Condition status and the sense key is set
to Miscompare.
•
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
207
18.42 VERIFY (16) - (8F)
Table 167: Verify (16) - (8F)
Bit
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
Rsvd
=0
Command Code = 08Fh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
2-9
Logical Block Address
(LSB)
(MSB)
10-13
Verification Length
(LSB)
14
15
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that
no data will be transferred. This condition is not considered an error.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
208
18.43 WRITE (6) - (0A)
Table 168: WRITE (6) - (0A)
Bit
Byte
7
6
5
0
1
3
2
1
0
Command Code = 0Ah
Reserved = 0
(MSB)
LBA
Logical Block Address
2-3
(LSB)
4
5
4
Transfer Length
VU = 0
Reserved = 0
FLAG
LINK
The WRITE command requests the drive to write the specified number of blocks of data (Transfer Length) from the Initiator
to the medium starting at the specified Logical Block Address (LBA).
See Section 18.15 “READ (6) - (08)” on page 164 for the parameters.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
209
18.44 WRITE (10) - (2A)
Table 169: WRITE (10) - (2A)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 2Ah
1
Reserved = 0
DPO
FUA
Reserved=0
RelAdr
=0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The WRITE (10) command requests that the drive write the data transferred from the Initiator. This command is processed like
the standard WRITE (6) - (0A) command except for the longer transfer length.
•
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.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
210
18.45 WRITE AND VERIFY (10) - (2E)
Table 170: WRITE AND VERIFY (10) - (2E)
Bit
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
RelAdr
=0
Command Code = 2Eh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
WRITE AND VERIFY command requests that the drive writes the data transferred from the Initiator to the medium and then
verify that the data is correctly written.
•
Transfer Length of zero indicates that no data is transferred.
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 bit set to zero indicates that the data is read back from the disk and verified using ECC after the successful
write operation. If an ECC error is detected in the verify process, Check Condition status is returned with sense key
set to Medium Error. ByteChk bit set to one indicates that byte-by-byte comparison is performed between data on the
disk starting the block specified in LBA field and data transferred from the Initiator.
If the comparison is unsuccessful, the command is terminated with Check Condition status and the sense key is set
to Miscompare.
•
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.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero.\
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
211
18.46 WRITE AND VERIFY (12) - (AE)
Table 171: Write andVerify (12) - (AE)
Bit
Byte
7
6
5
0
4
3
2
1
0
ByteChk
RelAdr=0
Command Code = AEh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
2-5
Logical Block Address
(LSB)
(MSB)
6-9
Transfer Length
(LSB)
10
11
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The WRITE AND VERIFY command requests that the drive write the data transferred from the Initiator to the medium and
then verify that the data is correctly written.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
212
18.47 WRITE AND VERIFY (16) - (8E)
Table 172: Write and Verify (16) - (8E)
Bit
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
RelAdr
=0
Command Code = 8Eh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
2-9
Logical Block Address
(LSB)
10-13
(MSB)
(LSB)
14
15
Transfer Length
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The WRITE AND VERIFY command requests that the drive write the data transferred from the Initiator to the medium and
then verify that the data is correctly written.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
213
18.48 WRITE BUFFER (3B)
Table 173: WRITE BUFFER (3B)
Bit
Byte
7
6
5
0
1
4
3
2
1
0
Command Code = 3Bh
Reserved = 0
Mode
2
Buffer ID
(MSB)
3-5
Buffer Offset
(LSB)
(MSB)
6-8
Parameter List Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
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.
MODE
Description
00000
Write combined header and data
00010
Data
00100
Download Microcode
00101
Download Microcode and Save - single binary file
00111
Download Microcode and Save - multiple binary files
01010
Write Data to Echo Buffer
11010
Enable expander Communications Protocol
All Others
Not Supported
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.
18.48.1 Combined Header And Data (Mode 00000b)
In this mode, the data to be transferred is preceded by a four-byte header.
Buffer ID must be zero. If another value is specified, no download function is performed and the command is terminated with
Check Condition status. And the drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in
CDB.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
214
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.
Table 174: Write Buffer Header
Bit
Byte
7
6
5
0-3
4
3
2
1
0
Reserved = 0
18.48.2 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
215
18.48.3 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.
18.48.4 Download Microcode and Save (Mode 00101b) -Single Binary File
In this mode the data is transferred to the drive to save into the System reserved area on the disk. This is for functional upgrade
and configuration change reflecting the user's requirements and the 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 Hitachi development purposes only.
18.48.5 Download Microprocessor 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 8K bytes. The total length of all segments received shall be equal to the total length of the binary
microcode file. All segments must be sent in the proper sequential order.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
216
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.
18.48.6 Write Data to Echo Buffer (Mode 01010b)
In this mode the Target transfers data into the echo buffer. The echo buffer is assigned in the same manner by the Target as it
would for a WRITE operation. Data will be sent aligned on 4-byte boundaries.
Upon successful completion of a WRITE BUFFER command the data will be preserved in the echo buffer unless there is an
intervening command to any logical unit, in which case it may be changed.
18.48.7 Enable Expander Communications Protocol (Mode 11010b)
In this mode the drive behavior is the same as Write Data to Echo Buffer (Mode 0101b).
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
217
18.49 WRITE LONG (3F)
Table 175: WRITE LONG (3F)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 3Fh
1
Reserved = 0
RelAdr
=0
Reserved = 0
(MSB)
2-5
Logical Block Address
(LSB)
6
Reserved = 0
(MSB)
7-8
Byte Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The WRITE LONG command requests the drive to write one block of data transferred from the Initiator.
The transfer data must include
•
User Data
•
43 bytes of ECC data
Parameters are
•
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 non-zero
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.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
218
18.50 WRITE SAME (41)
Table 176: WRITE SAME (41)
Bit
Byte
7
6
0
5
4
3
2
1
0
PBDA
TA=0
LBDA
TA=0
RelAdr
=0
Command Code = 41h
1
Reserved=0
(MSB)
2-5
Logical Block Address
(LSB)
6
Reserved = 0
(MSB)
7-8
Number of Blocks
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The 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.
•
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
219
18.51 WRITE SAME (16) - (93)
Table 177: Write Same (16) - (93)
Bit
Byte
7
6
0
5
4
3
2
1
0
Command Code = 93h
1
PBDATA LBDATA RelAdr =
=0
=0
0
Reserved = 0
(MSB)
2-9
Logical Block Address
(LSB)
(MSB)
10-13
Number of Blocks
(LSB)
14
15
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The Write Same command instructs the Target to write a single block of data transferred to the Target from the Initiator to a
number of sequential logical blocks. This command is useful for writing large data areas without sending all of the data over
the SCSI bus.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
220
19.0 SCSI Status Byte
Upon the completion of a command a status byte is sent to the initiator. Additional sense information may also be available
depending on the contents of the status byte. The following section describes the possible values for the status byte and sense
data. All Reserved fields are set to zero.
Table 178: SCSI Status Byte. Format of the SCSI STATUS byte.
Bit
7
6
Reserved = 0
5
4
3
2
1
Status Code
0
RSVD
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
221
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
222
20.0 Additional information
This chapter provides additional information or descriptions of various functions, features, or operating models supported by
the Target that are not fully described in previous chapters.
20.1 SCSI Protocol
There are various operating conditions that prevent the Target from executing a SCSI command. This section describes each of
these operating conditions and their relative priority.
20.1.1 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 20.1.2, “Invalid LUN Processing” on page 223)
2. Check Condition status for Incorrect Initiator Connection (See Section20.1.3, “Overlapped Commands” on page 224)
3. Check Condition status for Unit Attention Condition (See Section 20.1.5, “Unit Attention Condition” on page 225
4. Busy Status or Queue Full Status (See 20.1.4, “Command Processing During Execution of Active I/O Process” on
page 224
5. Check Condition status for Deferred Error Condition (See Section 20.1.8, “Deferred Error Condition” on page 227)
6. Check Condition status during Startup and Format operations (See Section “20.1.6, “Command Processing During
Startup and Format Operations” on page 227)
7. Reservation Conflict status (See Section 20.1.10, “Command Processing while Reserved” on page 235)
8. Check Condition status for invalid command opcode
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.
20.1.2 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 18.5, “INQUIRY (12)” on page 76).
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 18.30, “REQUEST SENSE (03)” on page 193).
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
223
20.1.3 Overlapped Commands
The the drive does not perform any overlapped command checking.
20.1.4 Command Processing During Execution of Active I/O Process
When the target is not executing any I/O processes, a new I/O process is permitted to execute (unless execution is prevented by
another internal target condition listed in 20.1.1, “Priority of SCSI Status Byte Reporting” on page 223).
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 20.1.4, “Command Processing During Execution of
Active I/O Process” on page 224 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 20.1.1, “Priority of SCSI Status Byte Reporting” on
page 223).
•
The command is permitted to execute if:
•
the command is a priority command (see 20.5, “Concurrent I/O Process” on page 236).
•
the conditions to execute concurrently are met (see 20.5, “Concurrent I/O Process” on page 236).
•
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 20.1.9, “Degraded Mode” on page 228) 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
224
20.1.5 Unit Attention Condition
The target generates a unit attention condition when one of the following occurs:
•
The target has been reset
This includes a power-on reset or a reset caused by a LUN Reset Task Management function or Hard Reset sequence.
In all of these cases, a unit attention condition is generated for each initiator.
•
MODE SELECT command has been executed
In this case, a unit attention condition is generated for all initiators except the one that issued the MODE SELECT
command. 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 com
mand. 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
225
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.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
226
20.1.6 Command Processing During Startup and Format Operations
If the Target receives a command from an Initiator while the Target is executing a startup or format operation, the response of
the Target varies with the command as follows:
INQUIRY
The drive sends inquiry data and returns appropriate status.
REQUEST SENSE
Executes the command, returns a Sense key of NOT READY and an Additional Sense Code of
LOGICAL UNIT NOT READY and returns GOOD STATUS.
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.
20.1.7 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) 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
The drive executes the command with GOOD status and does not clear the Internal Error condition.
REQUEST SENSE
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.
20.1.8 Deferred Error Condition
Error code (71h) 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
227
20.1.9 Degraded Mode
There are certain errors or conditions which may impair the ability of the drive to function normally. Rather than fail hard the
drive is designed to be as responsive as possible. Also, in most cases, some action on the part of the initiator may be used to
restore normal operation. This mode of limited operation is called Degraded Mode.
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)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
228
20.1.9.1 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
Table 179: Spindle Motor Degraded Mode - Disable Auto Start
Command (w/Option)
Response
Request Sense
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ
0402h (Initialize Command Required)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed and Check Condition is returned with Sense Key 05h (Illegal Request)
ASC/ASCQ 2400h (Invalid Field in CDB)
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 0402h (Initialize Command Required)
Start Stop Unit
Executed
(Start)
- 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
Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
(Stop)
Other Commands
Not Executed. Check Condition Status is returned with Sense Key 02h (Not
Ready) ASC/ASCQ 0402h (Initialize Command Required)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
229
20.1.9.2 Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up
Table 180: Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up
Command (w/Option)
Response
Request Sense
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ
0401h (In Process of Becoming Ready)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed and Check Condition is returned with Sense Key 05h (Illegal Request)
ASC/ASCQ 2400h (Invalid Field in CDB)
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 0401h (In Process of Becoming Ready)
Start Stop Unit
Executed
(Start)
- 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)
Other Commands
Not Executed. Check Condition Status is returned with Sense Key 02h (Not
Ready) ASC/ASCQ 0401h (In Process of Becoming Ready)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
230
20.1.9.3 Response to SCSI Command in Degraded Mode - Spindle Start Failure
Table 181: Spindle Motor Degraded Mode - Spindle Start Failure
Command (w/Option)
Response
Request Sense
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ
0400h (Start Spindle Motor Fail)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed and Check Condition is returned with Sense Key 05h (Illegal Request)
ASC/ASCQ 2400h (Invalid Field in CDB)
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 0400h (Start Spindle Motor Fail)
Executed
Start Stop Unit
- Success: Good Status is returned. Motor Degraded Mode is cleared
(Start)
- 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
Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
(Stop)
Other Commands
Not Executed. Check Condition Status is returned with Sense Key 02h (Not
Ready) ASC/ASCQ 0400h (Start Spindle Motor Fail)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
231
20.1.9.4 Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command
Table 182: Spindle Motor Degraded Mode - Spindle Stopped by Command
Command (w/Option)
Response
Request Sense
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ
0402h (Initialize Command Required)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 0402h (Initialize Command Required)
Executed
Start Stop Unit
- Success: Good Status is returned. Motor Degraded Mode is cleared
(Start)
- 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
Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
(Stop)
Other Commands
Not Executed. Check Condition Status is returned with Sense Key 02h (Not
Ready) ASC/ASCQ 0402h (Initialize Command Required)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
232
20.1.9.5 Self Configuration Failure Degraded Mode
Table 183: Self Configuration Failure Degraded Mode
Command (w/Option)
Response
Request Sense
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)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed and Check Condition is returned with
Sense Key 05h (Illegal Request) ASC/ASCQ 2400h (Invalid Field in CDB)
Test Unit Ready
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
Start Stop Unit
- Success: Good Status is returned. Motor Degraded Mode is cleared
(Start)
- 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)
Write Buffer
Executed.
(Download and Save)
- 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)
Other Commands
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)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
233
20.1.9.6 Format Command Failure Degraded Mode
Table 184: Format Command Failure Degraded Mode
Command (w/Option)
Response
Request Sense
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)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 3100h (Format Corrupted)
Format Unit
Executed
- Success: Good Status is returned. Format Degraded Mode is cleared
- Failure: Check Condition Status is returned and Format Degraded Mode is
NOT cleared.
Other Commands
Note:
Not Executed. Check Condition Status is returned with Sense Key 03h (Medium
Error) ASC/ASCQ 3100h (Format Corrupted)
Mode Page 0 byte 5 bit 4 (FDD) = 0
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
234
20.1.10 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 20.1.1, “Priority of SCSI Status Byte Reporting” on
page 223.
20.2 Priority Commands
Certain SCSI commands always execute without returning a Busy Status or Reservation Conflict Status in response to the
command. These commands are
•
Inquiry
•
Request Sense
•
Report LUNs
•
Test Unit Ready
These commands are executed prior to attempting to complete the execution of any other pending command in the queue.
These commands are never queued.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
235
20.3 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.
20.3.1 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.
20.3.2 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.
20.3.3 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
20.4 Command Reordering
Command reordering is supported when enabled by the Queue Algorithm Modifier in mode page 0A ( see 18.10.9, “Mode
Page 0A (Control Mode Page Parameters)” on page 140.
20.5 Concurrent I/O Process
Concurrent command 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.
20.6 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
236
20.7 Automatic Rewrite/Reallocate
The target supports Auto and Recommended Reallocate for READ, WRITE, WRITE VERIFY, and VERIFY.
Automatic and Recommend Reallocate operate 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 ECC Errors.)
ARRE=1:
An error site determined to need rewriting or reallocation during a read is automatically rewritten or reallocated at the conclusion of the read and prior to the sending of the status. The site will be automatically
rewritten or reallocated only if the data has been successfully read.
ARRE=0:
An error site determined to need rewriting or reassignment during a read is recommended for rewriting or
reassignment at the conclusion of the read.
The setting of the ARRE bit is checked and the target will automatically rewrite/reallocate or recommend rewrite/reassign for
the following commands.
•
Read(6)
•
Read(10)
•
Verify
•
Verify Portion of Write and Verify
For all other commands the ARRE setting is ignored and the target will not automatically rewrite/ reallocate or recommend
rewrite/reassign.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
237
Following is a description of the target behavior for each setting of AWRE. AWRE setting effects only No Sector Found Errors
on writes.
AWRE=1:
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.
AWRE=0:
An error site determined to need reassignment during a write is recommended for reassignment at the conclusion of the write.
The setting of the AWRE bit is checked and the target will automatically reallocate or recommend reassign for the following
commands.
•
Write(6)
•
Write(10)
•
Write portion of Write and Verify
For all other commands the AWRE setting is ignored and the target will not automatically reallocate or recommend reassign.
Auto/Recommend 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.
Table 185: Sense data combinations with auto/recommend rewrite/reallocate
Key
Code
Qual
Description
1
17
01
Recovered Data with retries
1
17
06
Recovered Data without ECC - Auto Reallocated
1
17
07
Recovered Data without ECC - Recommend Reassign
1
17
09
Recovered Data without ECC - Data Rewritten
1
18
00
Recovered Data with ECC
1
18
02
Recovered Data with ECC - Auto Reallocated
1
18
05
Recovered Data with ECC - Recommend Reassign
1
18
07
Recovered Data with ECC - Data Rewritten
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
238
20.8 Segmented Caching
20.8.1 Overview
Segmented Caching divides the data buffer into several smaller buffers. Each buffer is used as Read/ Write/Read-Ahead buffer.
20.8.2 Read Ahead
The Read Ahead function consists of reading data that the Initiator has not yet requested to the drive buffer. This function is
intended to improve performance for an initiator that frequently accesses sequential data with successive SCSI read commands. 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(6), Read (10), 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.
20.9 Multiple Initiator Systems
This section describes how the target behaves in a multiple initiator system. Up to 64 initiators may be supported at any one
time.
20.9.1 Sense Data
A separate sense data area is reserved for each initiator. Each area is maintained independently. This allows a command from
one initiator to complete with a CHECK CONDITION status and generate sense data without being affected by a subsequent
command from a different initiator. There is no requirement for the first initiator to send a REQUEST SENSE command to
retrieve the Sense Data prior to the execution of a command from a different initiator.
20.9.2 Mode Pages
A single set of Mode pages is maintained. This includes both current and saved parameters. If a MODE SELECT command is
executed that updates the current parameters, a unit attention condition is generated for all initiators except the one that issued
the command. See 20.1.5, “Unit Attention Condition” on page 225 for more information.
20.10 Multiple Initiator Environment
20.10.1 Initiator Sense Data
Separate sense data is reserved for each I-T-L. Each sense data is maintained independent of commands from other initiators.
20.10.2 Initiator Mode Select/Mode Sense Parameters
A single shared copy of the Mode Select/Mode Sense parameters is maintained by the drive. This includes both the current and
saved parameters.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
239
20.11 Reset
Reset actions will return the drive to a known, initialized state.
Modify the remaining sentence to read: This device supports the Hard reset option as defined in the SCSI standards (see 7.1.9
Dev_Ctrl_Code_x on page 33) and the reset sources discussed below.
20.11.1 Reset Sources
There are four sources of resets detected by the target:
Reset Name
Reset Source
Power-On Reset
This is the signal generated by the hardware at initial power-on
Self-Initiated reset
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.
20.11.2 Reset Actions
The action taken by the drive following a reset is dependent on the source of the reset.
20.11.2.1 Power-On reset and Self-Initiated reset
These two reset conditions cause the following to be performed in the order shown:
•
A power-up sequence
•
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.
20.12 Diagnostics
The drive will execute Power on Diagnostics at power on time to assure the correct operation of the drive by validating components (ROM, RAM, Sector Buffer, EEPROM, HDC, Spindle Motor, Actuator), checking stored information in the Reserved
Area and EEPROM, and verifying fault detects circuits.
Self-test can be invoked by issuing a SEND DIAGNOSTIC command.
20.12.1 Power on Diagnostics
At power on time the following tests are executed:
1. Validation of ROM and EEPROM
2. RAM test for internal RAM
3. Test and Initialize HDC registers
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
240
4.
5.
6.
7.
8.
RAM test for Sector Buffer
Start Spindle Motor (if enabled)
Calibration of Actuator
Read/Write test for all Heads
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.
20.12.2 Self-test via SEND DIAGNOSTIC Command
20.12.2.1 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. ECC circuit test is a test for ECC circuit to ensure that errors can be corrected by the circuit.
4. Seek test is a servo test. It validates seeks to 256 random locations out of the full volume.
20.12.2.2 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. The results of self-test can be retrieved via the LOG SENSE command for Log Page 10.
20.12.2.3 Self-test Modes
There are two modes for short and extended self-tests: a foreground mode and a background mode. These modes are described
in the following clauses.
Foreground mode
When the drive receives a SEND DIAGNOSTIC command specifying a self-test to be performed in the foreground mode, the
drive will return status for that command after the self-test has been completed. While performing a self-test 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 - SELFTEST 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
241
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
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 self-test 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
242
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 difference between the Short and the
Extended tests, is the sequential verify test in segment 9h. Also note that either of these tests can be run in foreground or background mode as previously described.
Table 186: Short and Extended Self-Test Description
Segment
Number
Short SelfTest
Extended
Self-Test
Test Description
1h
Drive Ready Test
Internal check to insure drive is “ready”, similar to a Test
Unit Ready command.
2h
RAM Test
Write/Read/Compare of drive's entire sector buffer
3h
Drive Diagnostics
This test is comprised of the Default Self Test as defined
in Section 20.12.2.1, “Default Self-test” on page 241
4h
SMART
Perform SMART testing and check results to ensure that
SMART threshold criteria are not exceeded
5h
Low Level Format check
Check to insure that the media is currently not in the
MEDIA FORMAT CORRUPTED state.
6h
Physical Head Check
Write/Read test on each head in a predefined location in
the drive's Reserved Area of the disk.
7h
Random Verify
Perform 4000 random verify operations and insure no
uncorrectable errors.
8h
- Verify First
300MB
Verify all
LBA’s
Sequential verify operation. Ensure that no uncorrectable errors occur within the verify range.
- Verify Last
100 MB
9h
Recheck SMART
Same as segment 4h.
20.12.2.4 Background Medium Scan
For a related function, see Mode Page 1C (Informational Exceptions Control), page 150
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
243
20.13 Idle Time Function
The drive periodically saves data in logs and PFA 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. This is performed if the drive has not received
a SCSI command for 10 minutes.
20.14 Command Time out Limits
The 'Command Time-out Limits' are defined as the time period from the SCSI Arbitration phase through the SCSI Task complete message, associated with a particular command.
The following times are for environments where Automatic Reallocation is disabled and there are no queued commands.
20.14.1 Reassignment Time
The drive should be allowed a minimum of 5 seconds to complete a “Reassign Blocks” command.
20.14.2 Format Time
Approximately 60 minutes should be allowed to complete a "Format Unit" command when certification is disabled. Allow
120 minutes when certification is enabled. If "Fast Format" is enabled via the FFMT bit in mode page 00h, allow 30 seconds
for completion.
20.14.3 Unit Start/Stop 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). If the RNOT mode (see Mode
Page 00, page 79) bit is set to zero (mode page 0, byte 4, bit 1), this requirement is removed.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
244
20.14.4 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.
20.14.5 Time-out Limits for Other Commands
The drive should be allowed a minimum of 5 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
245
20.15 Recommended Initiator ERP
The Drive's design points for error reporting to the system assumes certain system action for the error return codes. These
assumptions are:
1. 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 ECC correction
•
18 - Recovered read error with ECC correction
Typically, data errors do not include positioning of the heads or the data path though the electronics.
Nondata errors are those errors that do not have a direct relationship with transferring data to and from the media. Nondata
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.
20.15.1 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.
2.
3.
4.
Back up all the customer data on this drive if possible
Replace the complete drive
Restore the customer data
Return the drive to customer service
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
246
20.15.2 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)
20.15.3 Data Recovery Procedure
Statistically, most data error activity is noise related and has nothing to do with defects in the media. It is wrong for the system
to assume that every data error reported occurred because of a defect in the media. It is also wrong for the system to assume
that every data error that occurred because of a media defect rendered the Drive unusable.
Recurring data error activity at the same physical location is an indication of a problem. 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 18.10.3, “Mode Page 01
(Read/Write Error Recovery Parameters)” on page 127) 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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
247
20.15.3.1 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 either reassign the physical sector, or recommend to the initiator that the LBA associated with the physical
sector be reassigned.
When the following Sense Key, Additional Sense Code, and Additional Sense Code Qualifier combinations are returned, the
initiator should reassign the LBA reported at the next opportunity.
Note:
etc.).
In Table 187, the Key, Code, and Qualifier fields are all hex values (i.e., Sense Key 1 is 1h, Sense Code 17 is 17h,
Table 187: Recommend Reassign Errors
Key
Code
Qual
Description
1
17
07
Recovered Data without ECC - Recommend Reassignment
1
18
05
Recovered Data with ECC - Recommend Reassignment
To reassign an LBA that has sense data recommending a reassignment, the initiator should:
1.
2.
Attempt to recover the data from the sector being reassigned with a Read (08) or Read (28) command.
Reassign the LBA using the Reassign Blocks (07) command.
- If the reassignment completes successfully (Good Status), log the error in the system error log.
- If the reassignment completes unsuccessfully (Check Condition Status), follow the procedure in Section 20.15.3.3,
“Reassign Blocks Recovery” on page 249.
3.
Write the LBA that was reassigned.
20.15.3.2 Data Error Logging
The Drive will report data errors to the initiator that do not require immediate action (successful auto reallocation, successful
auto rewrite, or no action needed on this occurrence). The initiator should log these errors in the system error log. No other
action is required.
Table 188: Log Only Errors
Key
Code
Qual
Description
1
16
00
Data Synchronization Mark Error
1
17
01
Recovered Data with Retries
1
17
06
Recovered Data without ECC - Auto Reallocated
1
17
09
Recovered Data without ECC - Data Rewritten
1
18
00
Recovered Data with ECC
1
18
02
Recovered Data with ECC - Auto Reallocated
1
18
07
Recovered Data with ECC - Data Rewritten
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
248
20.15.3.3 Reassign Blocks Recovery
The Drive provides the capability to remove media defects without reducing capacity. If the mode parameter bit ARRE is
active, the Drive will automatically reallocate LBA's determined to be defective. For those LBA's where the error is unrecoverable or the initiator elects to not have the Drive automatically reallocate LBA's, the Drive will recommend reassignment of
the LBA.
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 18.23, “REASSIGN BLOCKS (07)” on page 176, 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 20.15.1, “Drive Service Strategy” on page 246.
20.15.4 Nondata Error Recovery Procedure
The Drive will follow a logical recovery procedure for nondata errors. The initiator options for non-data errors are limited to
logging the error, retrying the failing command, or replacing the drive.
These recovery procedures assume the initiator practices data back-up and logs errors at the system level for interrogation by
service personnel.
20.15.4.1 Drive Busy
The Drive is busy performing an operation. This is not an error condition. 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 20.14, “Command Time out Limits” on
page 244, then service the drive using the service guidelines recommended in Section 20.15.1, “Drive Service
Strategy” on page 246. Otherwise return to normal processing.
•
If the Test Unit Ready (00) (or media access) command completes with Good Status, then return to normal processing.
20.15.4.2 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 20.15.4.3, “Recovered Drive Error” on page 250.
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
20.15.4.3, “Recovered Drive Error” on page 250.
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 20.15.1, “Drive Service Strategy” on page 246.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
249
20.15.4.3 Recovered Drive Error
The Initiator should log the error as soft with the recovery level.
20.15.4.4 Drive Not Ready
The initiator should do the following:
1. Issue a Start Stop Unit (1B) command.
2. Verify that the drive comes ready within the time specified in Section 4.5.2, “Drive ready time” on page 13.
3. If the drive fails to come ready within the specified time, service the drive using the service guidelines specified in Section 20.15.1, “Drive Service Strategy” on page 246.
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 20.15.1, “Drive Service Strategy”
on page 246.
20.15.4.5 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 20.15.1, “Drive Service Strategy” on page 246.
20.15.4.6 Degraded Mode
Refer to Section 20.1.9, “Degraded Mode” on page 228, 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 20.14, “Command Time out Limits”
on page 244, service the drive using the service guideline recommended in Section 20.15.1, “Drive Service Strategy”
on page 246.
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 20.15.1, “Drive Service
Strategy” on page 246.
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 20.15.1, “Drive Service
Strategy” on page 246.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
250
- 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 20.15.1, “Drive Service Strategy” on page 246, 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 20.15.1, “Drive Service Strategy” on page 246.
If the above defined recovery procedures fail to clear the degraded mode condition, the Drive should be replaced. Follow the
procedure in Section 20.15.1, “Drive Service Strategy” on page 246, when replacing the drive.
20.15.4.7 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 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 20.15.1, “Drive Service Strategy” on page 246.
20.15.4.8 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 20.15.1, “Drive Service Strategy” on page 246.
• Other, follow the recommendations for the error condition reported.
20.15.4.9 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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
251
- 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 20.15.1,
“Drive Service Strategy” on page 246.
•
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.
20.15.4.10 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 18.6, “LOG SELECT (4C)” on page 89). 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 18.36, “SET DEVICE IDENTIFIER (A4)” on page 195) A Unit Attention Condition is reported to all initiators excluding the initiator that issued the Set Device Identifier command.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
252
20.15.4.11 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 20.15.1, “Drive Service Strategy” on page 246.
20.15.4.12 Self Initiated Reset
The Drive will initiate a self reset when the condition of the Drive cannot be determined. The internal reset will terminate any
outstanding commands, release any reserved initiators, and stop the spindle motor. The initiator can recover by
1. Logging the error
2. Retrying the failing command. If the failing command completes with:
- Good Status, return to normal processing
- Self initiated reset sense, service the drive according the guidelines recommended in Section 20.15.1, “Drive Service Strategy” on page 246.
- Other, follow the recommendations for the error reported.
20.15.4.13 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 20.15.1, “Drive Service Strategy” on page 246.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
253
20.15.4.14 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 20.15.1, “Drive Service Strategy” on
page 246.
- 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 20.15.1, “Drive Service Strategy” on page 246.
20.15.4.15 Microcode Error
The microcode from the interface is validated before the device operates using that microcode. When the validation detects
incorrect or incomplete data, the Drive enters degraded mode.
If the initiator attempted to load microcode using the Write Buffer (3B) retry the Write Buffer (3B). If the command completes
with
•
Good Status - return to normal processing
•
Check Condition Status - service the drive using the service guidelines recommended in Section 20.15.1, “Drive Service Strategy” on page 246.
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 20.15.1, “Drive Service Strategy” on page 246.
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 20.15.1, “Drive Service Strategy” on page 246.
- 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
20.15.1, “Drive Service Strategy” on page 246.
•
Check Condition Status for any other error, follow the recommendations for the returned sense data.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
254
20.15.4.16 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 20.15.1, “Drive Service Strategy” on page 246.
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.
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
255
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
256
21.0 SCSI Sense Data
21.1 SCSI Sense Data Format
Format of the sense data returned by the drive in response to the REQUEST SENSE command.
Table 189: Format of Sense Data.
Bit
Byte
7
0
6
5
Valid
2
0
(MSB)
0
ILI
0
Sense Key
Information Bytes
(LSB)
7
Additional Sense Length
(MSB)
Product Specific Information
(LSB)
12
Additional Sense Code
13
Additional Sense Code Qualifier
14
FRU = 0
15
1
RSVD = 0
2
8-11
3
Error Code (70h or 71h)
1
3-6
4
SKSV
Sense-Key Specific Bits
16-17
Sense-Key Specific Bytes
18-19
Reserved = 0
20-23
Vendor unique Error information
24-29
Product Specific Information
30-31
Reserved = 0
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
257
21.2 Sense Data Description
21.2.1 Valid (Bit 7 of byte 0)
0
The Information Bytes (byte 3 through 6) are not defined.
1
The Information Bytes (byte 3 through 6) contain a valid logical block address.
21.2.2 Error Code (Bit 6 - 0 of byte 0)
70h
Current Error. This indicates an error for the current command.
71h
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.
21.2.3 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
ILI
Command = Read Long or Write
Long?
x
0
x
1
1
yes
Description
No incorrect length condition
Requested Logical block Length does not
match the logical block length of the data
on the disk
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
258
21.2.4 Sense Key (Bit 3 - 0 of byte 2)
The sense key provides generic categories in which error and exception conditions can be reported. Initiators would typically
use sense keys for high level error recovery procedures.
0h
No Sense
There is no sense key information to be reported for the logical unit.
1h
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.
2h
Not Ready
The logical unit addressed cannot be addressed. More detailed information is available in the Additional
Sense Code and Additional Sense Code Qualifier.
3h
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.
4h
Hardware Error
The drive detected a 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.
5h
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.
6h
Unit Attention
Indicates that the drive entered in the 'Unit Attention Condition'. (See Section 20.1.5, “Unit Attention Condition” on page 225)
7h
Data Protect
8h
Not used
9h
Vendor Specific
Ah
Not used
Bh
Aborted command
The drive aborted the command.
Ch-Dh Not Implemented
Eh
Miscompare
Fh
Reserved
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
259
21.2.5 Information Bytes (Byte 3 through 6)
This field is only valid when Valid Bit is one.
•
ILI = 0: This field contains the unsigned LBA associated with the sense key. The LBA reported will be within the
LBA range of the command as defined in the CDB.
Note:
An LBA other than the command LBA may be reported on the Reassign Block (07h) command.
•
ILI = 1: This field contains the difference (residue) of the requested length in bytes. Negative values are indicated by
two's complement notation.
Valid
ILI
Description
0
x
0x00000000 - (not used/invalid)
1
0
LBA
1
1
Residue of the requested length in bytes
21.2.6 Additional Sense Length (Byte 7)
Indicates the remaining number of bytes in the sense data. (It is always set to 18h.)
21.2.7 Command Specific Information (Byte 8 through 11)
This field is unused and will be set to zero.
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
260
21.2.8 Additional Sense Code/Qualifier (Byte 12 and 13)
The following table shows the description of the combination of Sense Key / Sense Code / Qualifier.
Valid Sense Key, Code, Qualifier Combinations Used by the Drive.
Key
Code
Qual
Description
Sense Key = No Sense
0
00
00
No Additional Sense Information
(00 00) No Error.
Sense Key = Recovered Error
1
01
00
No Index/Sector Signal
1413 Servo: Soft write no index error
1
02
00
No Seek Complete
141B Servo: Recovered No seek complete
141D Servo: Recovered Seek timeout
141F Servo: Recovered Seek error
142B Servo: Recovered RRO Calibration timeout
1
03
00
Peripheral Device Write Fault
1405 Servo: Recovered write inhibit error
1733 Recovered read/write abort
1737 Recovered post write abort
1739 Recovered Post PES check write abort
1
09
00
Track Following Error
1421 Servo: Recovered track following error
1423 Servo: Recovered track follow timeout
1
0B
01
Temperature Warning Error
xA02 Temperature Warning
Background Selftest Failure Warning
xA03 Background selftest failure warning
Background Pre-Scan Failure Warning
xA04 Background pre-scan failure warning
Background Media Scan Failure Warning
xA05 Background media scan failure warning
1
0C
01
Recovered Write Error with Auto Reallocation - Auto Reallocated
D703 Auto-reallocated due to write error
1
0C
03
Recovered Write Error - Recommend Reassignment
1704 Recommend reassign due to write error
1
15
00
Random Positioning Error
1714 Recovered sector overflow
173D Recovered sector miss
17B2 Recovered abort window error
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
261
1
16
00
Data Synchronization Mark Error
173B Recovered data address mark error
1
16
01
Data Sync Error - Data Rewritten
E70E Recovered Data Address Mark error - rewritten
1
16
02
Data Sync Error - Recommend Rewrite
E70F Recovered Data Address Mark error - recommend rewrite
1
16
03
Data Sync Error - Auto Reallocated
D710 Recovered Data Address Mark error - reassigned
1
16
04
Data Sync Error - Recommend Reassignment
E711 Recovered Data Address Mark error - recommend reassign
1
17
01
Recovered Data with Retries
1722 Recovered small thermal asperity
172C Recovered media error
172E Recovered media error (off-line correction discarded)
1
17
06
Recovered Data Without ECC - Data Auto-Reallocated
E705 Media error with OTF correction - reassigned
D72B Recovered thermal asperity - reassigned
1
17
07
Recovered Data Without ECC - Recommend Reassignment
E706 Media error with OTF correction - recommend reassign
E72A Recovered thermal asperity - recommend reassign
1
17
08
Recovered Data Without ECC - Recommend Rewrite
E707 Media error with OTF correction - recommend rewrite
E729 Recovered thermal asperity - recommend rewrite
1
17
09
Recovered Data Without ECC - Data Rewritten
D708 Media error with OTF correction - rewritten
E728 Recovered thermal asperity - rewritten
1
18
00
Recovered Data With ECC
1709 Media error with offline correction
1
18
02
Recovered Data - Data Auto-Reallocated
D70A Media error with offline correction and reassign
D724 Recovered thermal asperity with offline correction - reassigned
1
18
05
Recovered Data - Recommend Reassignment
E70B Media error with offline correction and recommend reassign
E725 Recovered thermal asperity with offline correction - recommend reassign
1
18
06
Recovered Data With ECC - Recommend Rewrite
E70C Media error with offline correction - recommend rewrite
E726 Recovered thermal asperity with offline correction - recommend rewrite
1
18
07
Recovered Data With ECC - Data Rewritten
E70D Media error with offline correction - rewritten
E727 Recovered thermal asperity with offline correction - rewritten
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
262
1
1C
00
Defect List Format Not Supported
1746 Defect list format not supported
1
1C
01
Primary Defect List Not Found. Requested Format Not Supported
1747 Primary defect list not found (Read Defect Data only)
1
1C
02
Grown Defect List Not Found. Requested Format Not Supported
1748 Grown defect list not found (Read Defect Data only)
1
1F
00
Partial Defect List Transfer
1749 Partial defect list transferred (Defect list longer than 64KB, 64 KB of data returned - Read
Defect Data only)
1
44
00
Internal Target Failure
F123 Invalid request to enter sleep mode
F128 DRAM test in progress
F129 DRAM test complete
F12A DRAM test error
F132 GEM FH track read error
1201 Error in UEC class
1202 Error in UEC cause
1301 Motor: Recovered internal error
1303 Motor: Recovered Open Loop Commutation failure
1305 Motor: Recovered No feedback detected
1307 Motor: Recovered Settle timeout
1309 Motor: Recovered Gross speed error
130B Motor: Recovered 12V OK error
130D Motor: Recovered Speed 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
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
263
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
1606 Recovered data with PPM or precomp load
1608 Recovered data with TA (Thermal Asperity) detection
160A Recovered data with SMM or VM or DDF
160C Recovered data with pre-PPM or FH (Fly Height) detection
160E Recovered data with write or pre-TA detection
1610 Recovered data with pre-SMM or VM or STM or DDF
1612 Recovered data with NRZ parity error
1614 Recovered parity PP correction or STW
1616 Recovered channel error
1618 Recovered AE thermal asperity
161A Recovered AE open MR element error
161C Recovered AE IC over temperature error
161E Recovered AE IP clock count error
1620 Recovered AE write data BLS error
1624 Recovered AE invalid head address error
1626 Recovered AE power supply error
1628 Recovered AE open write head error
162A Recovered AE write transition error
162C Recovered AE no write head current error
162E Recovered Channel Pre-TA error
1630 Recovered Channel write or NRZ parity error
1632 Recovered Channel write synth unlock error
1634 Recovered AE Short write read head error
1636 Recovered AE Short write head error
1638 Recovered AE Non-selected write head error
163C Recovered AE IH open short error
163E Recovered AE IH delay error
1640 Recovered Channel coarse tune timeout error
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
264
1712 Recovered ECC error
1716 Recovered overrun
171A Recovered ECC overrun
171C Recovered DRAM CRC error
171E Recovered ID Parity error
1731 Recovered write fault
1759 Unknown recovered error
1798 Recovered ID not found error
179C Recovered Channel write or NRZ parity error
17B4 Recovered Shock sensor error
17B8 Recovered Channel write synth unlock error
1
44
0B
Vendor Unique - Internal Target Failure
130F Motor: Recovered Spindle Current error
1
5D
xx
Predictive Failure Analysis Threshold Reached
xA14 SMART: Spare sector availability warning
xA32 SMART: Read error rate warning
xA43 SMART: Seek error rate warning
xA4A SMART: Write error rate warning
xA50 SMART: Load/unload cycle count warning
xA56 SMART: Spin-up time warning
xA5B SMART: Spin-up retry count warning
xAFE SMART: Over-temperature warning
xAFF SMART: Test warning
1
81
00
Vendor Unique - Internal Logic Error
1601 Channel/AE internal logic error
Sense Key = Not Ready
2
04
00
Logical Unit Not Ready - Start Spindle Motor Fail
1501 Logical unit not ready
2
04
01
Logical Unit Is In The Process of Becoming Ready
1502 Logical unit becoming ready
2
04
02
Logical Unit Not Ready, initializing command required
F124 Bring-up error
1503 Logical unit not ready - initializing command required
2
04
04
Logical Unit Not Ready, Format In Progress
1504 Not ready - format in progress
2
04
09
Not Ready - Self-test In Progress
1505 Not ready - self-test in progress
2
04
11
Not Ready - Notify (Enable Spin-up) Required
1553 Not ready - Notify (Enable Spin-up) required (SAS only)
2
04
F0
Vendor Unique - Logical Unit Not Ready
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
265
F133 BATS error: Vendor ID mismatch
2
31
00
Medium Format Corrupted - Reassign Failed
1506 Reassign failed
2
31
01
Format Command Failed
1507 Format failed
Sense Key = Medium Error
3
03
00
Medium Error - Write Fault
F734 Unrecovered read/write abort
F738 Unrecovered post write abort
F73A Unrecovered Post PES check write abort
3
11
00
Unrecovered Read Error
F723 Unrecovered small thermal asperity
F72D Unrecovered media error
F72F Unrecovered media error (off-line correction discarded)
F74D Too many heads
F74E Skew table size error
F74F Too many zones
F750 Too many SIDs
F751 Alternate track table full
F752 Drive capacity too small
F753 G-list full (Format command)
F754 G-list full (2) (Format command)
F755 Pointer repeat size error
F756 DST slot size error
F757 P-list full
F758 Spare list full
F75E Max servo cylinder too small
F79E Physical square wave format illegal
F79F Skew illegal
F7A0 Customer cylinders not evenly divisible by track span
F7A1 More than one head required for Serpentine format
F7A2 Reserved area cannot be Serpentine format
3
15
00
Random Positioning Error
F715 Unrecovered sector overflow
F73E Unrecovered sector miss
F7B3 Unrecovered abort window error
3
16
00
Data Synchronization Mark Error
F73C Unrecovered data address mark error
3
19
02
Defect List Error in Primary List
F74B Primary defect list error
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
266
3
19
03
Defect List Error in Grown List
F74C Grown defect list error
3
31
00
Medium Format Corrupted Reassign Failed
F701 Format corrupted
3
81
00
Vendor Unique - Internal Logic Error
F719 Recovered Abort immediate error
F75B Too many sectors
Sense Key = Hardware Error
4
02
00
No Seek Complete
F41C Servo: Unrecovered No seek complete
F41E Servo: Unrecovered Seek timeout
F420 Servo: Unrecovered Seek error
F42C Servo: Unrecovered RRO Calibration timeout
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
35
00
Enclosure Services Failure
1539 ESI: unspecified failure (FC-AL only)
4
35
01
Enclosure Services Failure - Unsupported Enclosure Function
153A ESI: unsupported function (FC-AL only)
4
35
02
Enclosure Services Failure - Enclosure Services Unavailable
153B ESI: enclosure unavailable (FC-AL only)
4
35
03
Enclosure Services Failure - Enclosure Services Transfer Failure
1556 ESI: transfer failed - write ack
1557 ESI: transfer failed - read ack
1558 ESI: transfer failed - write ready
1559 ESI: transfer failed - read ready
155E ESI: transfer failed - EDV
4
35
04
Enclosure Services Failure - Enclosure Services Refused
155A ESI: transfer refused - write ack
155B ESI: transfer refused - read ack
155C ESI: transfer refused - write ready
155D ESI: transfer refused - read ready
4
35
80
Enclosure Services Failure - Vendor Unique
F53C SES timeout
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
267
4
3E
03
Self-test Failed
F75D Self-test failed
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
110A BATS error: Reserved Area - Error reading second copy
F10B BATS error: Reserved Area - Read block error
110C BATS error: Reserved Area - Write fix soft error
F10D BATS error: Reserved Area - Write fix hard error
F10E BATS error: Directory broken
F10F BATS error: Overlay code load error
F110 BATS error: Overlay code check
F111 BATS error: RAM code load error
F112 BATS error: RAM code check
F113 BATS error: Config invalid
F114 BATS error: Log manager invalid
F115 BATS error: Media tables invalid
F116 BATS error: Logical-to-physical invalid
F117 BATS error: Defect manager invalid
F11D Incorrect Disk Code
F11F RPO SID invalid
F120 BATS error: Code compatibility failure
F121 BATS error: Code download in progress
F122 BATS error: Performance data read error
F125 BATS error: Invalid RID/FID
F126 BATS error: Code checksum error
F127 BATS error: Invalid header
F12B BATS error: Reserved area - invalid model
F12C BATS error: Invalid code size
F12D Format Reserved: FAT size exceeded
F12E Format Reserved: Insufficient DIRS good
F12F Format Reserved: Insufficient FATS good
F130 Incorrect Customer code
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
268
F131 Flash timeout
4
40
90
Diagnostic Failure
F118 BATS#2 error: Seek test error
4
40
A0
Diagnostic Failure
F119 BATS#2 error: Read/write test error
F11A BATS#2 error: ECC test error
F11B BATS#2 error: CRC test error
F11C BATS#2 error: XOR test error
4
44
00
Internal Target Failure
F203 Internal target failure
F302 Motor: Unrecovered internal error
F304 Motor: Unrecovered Open Loop Commutation error
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
F402 Servo: Unrecovered Requested re zero 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
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
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
269
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: Servo: Unrecovered VCM Retract error
F444 Servo: Unrecovered Load Retry error
F603 Channel/AE target failure
F604 Channel/AE calibration error
F607 Unrecovered data with PPM or precomp load
F609 Unrecovered data with TA detection
F60B Unrecovered with SMM or VM or DDF
F60D Unrecovered data pre-PPM or FH detection
F60F Unrecovered data write or pre-TA detection
F611 Unrecovered data with pre-SMM or VM or STM or DDF
F613 Unrecovered data with NRZ parity error
F615 Unrecovered parity PP correction or STW
F617 Unrecovered channel error
F619 Unrecovered AE thermal asperity found
F61B Unrecovered AE open MR element error
F61D Unrecovered AE IC over temperature error
F621 Unrecovered AE high MR current error
F623 Unrecovered AE write data BLS error
F625 Unrecovered AE invalud head address error
F627 Unrecovered AE power supply error
F629 Unrecovered AE open write head error
F62B Unrecovered AE write transition error
F62D Unrecovered AE no write head current error
F62F Unrecovered Channel Pre-TA error
F631 Unrecovered Channel write or NRZ parity error
F633 Unrecovered Channel write synch unlock error
F635 Unrecovered AE Short write read head error
F637 Unrecovered AE Short write head error
F639 Unrecovered AE Non-selected write head error
F63B Unrecovered AE Write current in read error
F63D Unrecovered AE IH open short error
F63F Unrecovered AE IH delay error
F641 Unrecovered Channel coarse tune timeout error
F713 Unrecovered ECC error
F717 Unrecovered overrun
F71B Unrecovered ECC overrun
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
270
F71D Unrecovered DRAM CRC error
F71F Unrecovered ID Parity error
F732 Unrecovered Write Fault
F75A Unknown unrecovered error
F799 Unrecovered ID not found error
F7B5 Unrecovered Shock sensor error
FCxx Unable to read RID or FID number xx
4
44
0B
Vendor Unique - Internal Target Failure
F310 Motor: Unrecovered Spindle Current 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
4
81
00
Vendor Unique - Internal Logic Error
F602 Channel/AE hard logic error
Sense Key = Illegal Request
5
1A
00
Parameter List Length Error
1509 Parameter list length error
5
20
00
Invalid Command Operation Code
150A Invalid opcode in CDB
5
21
00
Logical Block Address out of Range
150B LBA out of range
5
24
00
Invalid Field in CDB
150C Illegal request - invalid field in CDB
1542 SPC buffer not allocated
5
24
F3
Vendor Unique - Illegal Request
1545 Formatted without P-List
5
25
00
Logical Unit Not Supported
150D Invalid LUN
5
26
00
Invalid Field in Parameter List
150E Illegal request - invalid field in parameter list
150F Saved parameter not supported
1510 Unsupported log page
5
26
04
Invalid Release of Active Persistent Reservation
1538 Invalid release of persistent reservation
1540 Invalid release of persistent reservation
5
35
01
Unsupported Enclosure Function
1511 Unsupported enclosure services function (FC-AL only)
5
49
00
Invalid Message Error
1512 Invalid message (SCSI only)
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
271
5
55
00
System Buffer Full
1513 System buffer full
5
55
04
Insufficient Registration Resources
1567 Insufficient registration resources
Sense Key = Unit Attention
6
28
00
Not Ready To Ready Transition (Format completed)
1514 Not ready to read transition
6
29
00
Unit Attention - Login Reset
1515 Login reset (FC-AL only)
6
29
01
Unit Attention - POR Occurred
1516 Power on reset
6
29
02
Unit Attention - SCSI Bus Reset Occurred
1517 SCSI bus reset (SCSI), LIP Reset (FC-AL), SAS Hard Reset (SAS)
6
29
03
Unit Attention - Bus Device Reset Occurred
1518 Bus device reset (SCSI only), Target Reset (FC-AL), LUN Reset (SAS)
6
29
04
Unit Attention - Self Initiated Reset Occurred
1519 Self initiated reset
6
29
05
Transceiver Changed to SE
151A Tranceiver changed to single-ended (SCSI only)
1548 FC-AL Hard Reset (FC-AL only)
6
29
06
Transceiver Changed to LVD
151B Tranceiver changed to LVD (SCSI only)
6
29
07
I_T Nexus Loss Occurred
1554 I_T Nexus Loss Occurred (SAS only)
6
2A
01
Mode Parameters Changed
151C Mode parameters changed
6
2A
02
Log Parameters Changed
151D Log parameters changed
6
2A
03
Reservations Preempted
151E Reservations pre-empted
6
2A
04
Reservations Released
151F Reservations released
6
2A
05
Registrations Released
1520 Registrations pre-empted
6
2F
00
Commands Cleared by Another Initiator
1521 Commands cleared by another initiator
6
2F
01
Commands Cleared by Power Fail Event
156A Commands cleared by power fail event
6
3F
01
Microcode has been changed
1522 Microcode changed
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
272
6
3F
03
Inquiry Parameters Changed
1523 Inquiry parameters changed
6
3F
05
Device Identifier Changed
1537 Device identifier changed
6
5D
00
Predictive Failure Analysis Threshold Reached
1524 PFA Threshold reached
6
5D
FF
Predictive Failure Analysis Threshold Reached
1525 PFA Test warning
Sense Key = Aborted Command
B
1B
00
Synchronous Data Transfer Error
1527 Synchronous data transfer error (SCSI only)
1528 ACK synchronization error (SCSI only)
B
25
00
Logical Unit Not Supported
1529 Unsupported LUN (SCSI only)
B
3F
0F
Aborted Command - Echo Buffer Overwritten
1544 Echo buffer overwritten
B
43
00
Message Error
152A Message reject error (SCSI only)
152C Message parity error rcvd when no message sent by target (SCSI only)
B
44
00
Internal Target Failure
152D Buffer CRC error on read
152E Internal target failure - Host Interface
154A Xfer Ready credit exceeded (FC-AL only)
154B Xfer length error (FC-AL only)
F75C Internal media access timeout
F761 Read/write command timeout
F772 DASH starting timeout
F773 ID table timeout
F774 Servo timeout
F775 Buffers timeout
F776 DASH done timeout
F777 DASH unknown timeout
F77A Unrecovered Channel SBW timeout
F77B Unrecovered Channel write error timeout
F77D Recovery timeout
F7A5 Channel: course tune timeout
F7B1 Overall command timeout
B
45
00
Select or Reselect Failure
152F Selection reselection error (SCSI only)
B
47
00
SCSI Parity Error
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
273
1530 Message parity error - initiator (SCSI only)
1531 Message parity error - target (SCSI only)
B
47
03
Information Unit iuCRC Error Detected
1543 IU SCSI CRC error
B
48
00
Initiator Detected Error Message Received
1532 Initiator detected error message received (SCSI only)
B
49
00
Invalid Message Error
152B Attention dropped too late (SCSI only)
1533 Inappropriate or illegal message (SCSI only)
B
4B
00
Data Phase Error
153E Data phase error
0B
4B
02
Too Much Write Data
1560 Too much write data (SAS only)
B
4B
03
ACK/NAK Timeout
1551 ACK/NAK Timeout (SAS only)
B
4B
04
NAK Received
1550 NAK Received (SAS only)
B
4B
05
Data Offset Error
1552 Bad parameter offset (SAS only)
B
4B
06
Initiator Response Timeout
1555 Initiator response timeout (SAS only)
B
4E
00
Overlapped Commands Attempted
1534 Overlapped command attempted
B
4F
00
Command Aborted Due To Loop Initialization
153F Abort by LIP (FC-AL only)
Sense Key = Miscompare
E
1D
00
Miscompare During Verify Operation
1535 Miscompare during verify
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
274
21.2.9 RU: Field Replaceable Unit (Byte 14)
The FRU (Field Replaceable Unit) field value will always be zero.
21.2.10 Sense Key Specific (Byte 15 through 17)
The definition of this field is determined by the value of the sense key field.
21.2.10.1 Sense Key Specific - Illegal Request (Sense Key = 5h)
Error field pointer is returned.
Table 190: Field Pointer Bytes
Bit
Byte
7
6
15
SKSV
C/D
16
(MSB)
5
4
3
Reserved
BPV
2
1
Bit Pointer
Field Pointer
17
SKSV
C/D
BPV
0
(LSB)
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.
Bit Pointer
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.
Field Pointer
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.
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
275
21.2.10.2 Sense Key Specific - Recovered (Sense Key = 1h) or Medium (Sense Key = 3h) or Hardware (Sense Key = 4h)
Hardware (Sense Key = 4h) or Medium Error (Sense Key = 3h)
Actual Retry Count is reported.
Table 191: Actual Retry Count
Bit
Byte
7
15
SKSV
6
5
4
3
2
1
0
Reserved
16
Secondary Step
17
ERP Type
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
ERP Type
Read
0x00
Verify
0x01
Write
0x02
Seek
0x03
Read, Sync Byte branch
0x04
Read, Thermal Asperity branch
0x05
Read, Minus Mod branch
0x06
Verify, Sync Byte branch
0x07
Verify, Thermal Asperity branch
0x08
Verify, Minus Mod branch
0x09
21.2.10.3 Sense Key Specific - 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.
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
276
Progress indication is returned.
Table 192: Progress Indication
Bit
Byte
7
15
SKSV
16
(MSB)
6
5
4
3
2
Progress Indication
0
Reserved
Progress Indication
17
SKSV
1
(LSB)
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.
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
277
21.2.11 Reserved (Byte 18 through 19)
Reserved fields are filled with zero.
21.2.12 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.
21.2.13 Physical Error Record (Byte 24 thru 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 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 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
ILI
Description
1
0
Cylinder Number (bytes 24-26)
Head number (byte 27)
Sector Number (bytes 28-29)
1
1
0x000000000000
0
x
0x000000000000 - (not used/invalid)
21.2.14 Reserved (Byte 30 through 31)
Reserved fields are filled with zero.
Hitachi Ultrastar 15K147 SAS Hard Disk Drive Specification
278
22.0 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 21.0, “SCSI Sense Data” on page 257. These codes are used internally by Hitachi and may
change without notice.
How to find a specific UEC
The first hex digit of the UEC indicates the error severity, e.g. Fxxx codes are for hard/unrecoverable errors, 1xxx codes are for
soft/recoverable errors, etc. 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 193: Unit Error Codes
UEC
---0000
F101
F102
F103
F104
F105
F106
F107
F108
1109
110A
F10B
110C
F10D
F10E
F10F
F110
F111
F112
F113
F114
F115
F116
F117
F118
F119
Description
--------------------------------------------------------No error
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 - Error reading second copy
BATS error: Reserved Area - Read block error
BATS error: Reserved Area - Write fix soft error
BATS error: Reserved Area - Write fix hard error
BATS error: Directory broken
BATS error: Overlay code load error
BATS error: Overlay code check
BATS error: RAM code load error
BATS error: RAM code check
BATS error: Config invalid
BATS error: Log manager invalid
BATS error: Media tables invalid
BATS error: Logical-to-physical invalid
BATS error: Defect manager invalid
BATS#2 error: Seek test error
BATS#2 error: Read/write test error
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
279
UEC
Description
F11A
F11B
F11C
F11D
F11F
F120
F121
F122
F123
F124
F125
F126
F127
F128
F129
F12A
F12B
F12C
F12D
F12E
F12F
F130
F131
F132
F133
F134
F135
BATS#2 error: ECC test error
BATS#2 error: CRC test error
BATS#2 error: XOR test error
Incorrect Disk Code
RPO SID invalid
BATS error: Code Compatibility Failure
BATS error: Code download in progress
BATS error: Performance data read error
Invalid request to enter sleep mode
Bring-up error
BATS error: Invalid RID/FID
BATS error: Code checksum error
BATS error: Invalid header
DRAM test in progress
DRAM test complete
DRAM test error
BATS error: Reserved area - invalid model
BATS error: Invalid code size
Format Reserved: FAT size exceeded
Format Reserved: Insufficient DIRS good
Format Reserved: Insufficient FATS good
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
1201
1202
F203
F204
F205
F206
Error in UEC class
Error in UEC cause
Internal target failure
Reassign reserved area media error
G-list full - can't reassign any more sectors
No spares available
1301
F302
1303
F304
1305
F306
Motor: Recovered internal error
Motor: Unrecovered internal error
Motor: Recovered Open Loop Commutation failure
Motor: Unrecovered Open Loop Commutation failure
Motor: Recovered No feedback detected error
Motor: Unrecovered No feedback detected error
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
280
UEC
Description
1307
F308
1309
F30A
130B
F30C
130D
F30E
130F
F310
1311
F312
Motor: Recovered Settle timeout
Motor: Unrecovered Settle timeout
Motor: Recovered Gross speed error
Motor: Unrecovered Gross speed error
Motor: Recovered 12V OK error
Motor: Unrecovered 12V OK error
Motor: Recovered Speed error
Motor: Unrecovered Speed error
Motor: Recovered Spindle Current error
Motor: Unrecovered Spindle Current error
Moto: Recovered Internal 12V not OK timeout
Motor: Unrecovered Internal 12V not OK timeout
1401
F402
1403
F404
1405
F406
1407
F408
1409
F40A
140B
F40C
140D
F40E
140F
F410
1411
F412
1413
F414
1415
F416
1417
F418
1419
F41A
141B
F41C
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
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 No seek complete
Servo: Unrecovered No seek complete
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
281
UEC
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
F436
1437
F438
1439
F43A
143B
F43C
143D
F43E
143F
F440
1441
F442
1443
F444
Description
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
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
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
282
UEC
1501
1502
1503
1504
1505
1506
1507
1509
150A
150B
150C
150D
150E
150F
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
151A
151B
151C
151D
151E
151F
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
152A
Description
Logical unit not ready
Logical unit becoming ready
Logical unit not ready - initializing command required
Not ready - format in progress
Not ready - self-test in progress
Reassign failed
Format failed
Parameter list length error
Invalid opcode in CDB
LBA out of range
Illegal request - invalid field in CDB
Invalid LUN
Illegal request - invalid field in parameter list
Saved parameter not supported
Unsupported log page
Unsupported enclosure services function (FC-AL only)
Invalid message (SCSI only)
System buffer full
Not ready to ready transition
Login reset (FC-AL only)
Power on reset
SCSI bus reset (SCSI), LIP reset (FC-AL), SAS Hard Reset (SAS)
Bus device reset (SCSI), Target Reset (FC-AL), LUN Reset (SAS)
Self initiated reset
Tranceiver changed to single-ended (SCSI only)
Tranceiver changed to LVD (SCSI only)
Mode parameters changed
Log parameters changed
Reservations pre-empted
Reservations released
Registrations pre-empted
Commands cleared by another initiator
Microcode changed
Inquiry parameters changed
PFA threshold reached
PFA test warning
Write protected
Synchronous data transfer error (SCSI only)
ACK synchronization error (SCSI only)
Unsupported LUN (SCSI only)
Message reject error (SCSI only)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
283
UEC
152B
152C
152D
152E
152F
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
153A
153B
153C
153E
153F
1540
1541
1542
1543
1544
1545
154A
154B
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
155A
155B
155C
Description
Attention dropped too late (SCSI only)
Message parity error rcvd when no message sent by target (SCSI only)
Buffer CRC error on read
Internal target failure
Selection reselection error (SCSI only)
Message parity error - initiator (SCSI only)
Message parity error - target (SCSI only)
Initiator detected error message received (SCSI only)
Inappropriate or illegal message (SCSI only)
Overlapped command attempted
Miscompare during verify
Reservation conflict
Device identifier changed
Invalid release of persistent reservation
ESI: unspecified failure (FC-AL only)
ESI: unsupported function (FC-AL only)
ESI: enclosure unavailable (FC-AL only)
SES timeout (FC-AL only)
Data phase error (FC-AL only)
Abort by LIP (FC-AL only)
Invalid release of persistent reservation
Low power condition on
SPC buffer not allocated
IU SCSI CRC error
Echo buffer overwritten
Formatted with No P-List
Xfer Ready credit exceeded (FC-AL only)
Transfer length error (FC-AL only)
NAK rcvd (SAS)
ACK NAK Timeout (SAS)
Bad parameter offset (SAS)
LUN Not ready, Notify (Enable Spinup) required (SAS)
I_T_Nexus Loss Occurred (SAS)
Initiator Response Timeout (SAS)
ESI transfer failed - write ack (FC-AL)
ESI transfer failed - read ack (FC-AL)
ESI transfer failed - write ready (FC-AL)
ESI transfer failed - read ready (FC-AL)
ESI transfer refused - write ack (FC-AL)
ESI transfer refused - read ack (FC-AL)
ESI transfer refused - write ready (FC-AL)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
284
UEC
Description
155D
155E
1560
1567
156A
ESI transfer refused - read ready (FC-AL)
ESI transfer failed - EDV (FC-AL)
Too much write data (SAS)
Insufficient registration resources
Events cleared by power fail event (SAS only)
1601
F602
F603
F604
1606
F607
1608
F609
160A
F60B
160C
F60D
160E
F60F
1610
F611
1612
F613
1614
F615
1616
F617
1618
F619
161A
F61B
161C
F61D
161E
F61F
1620
F621
1622
F623
1624
Channel/AE internal logic error
Channel/AE hard logic error
Channel/AE target failure
Channel/AE calibration error
Recovered data with PPM or precomp load
Unrecovered data with PPM or precomp load
Recovered data with TA (Thermal Asperity) detection
Unrecovered data with TA detection
Recovered data with SMM or VM or DDF
Unrecovered data with SMM or VM or DDF
Recovered data with pre-PPM or FH (Fly Height) detection
Unrecovered data with pre-PPM or FH detection
Recovered data with write or pre-TA detection
Unrecovered data with write or pre-TA detection
Recovered data with pre-SMM or VM or STM or DDF
Unrecovered data with pre-SMM or VM or STM or DDF
Recovered data with NRZ parity error
Unrecovered data with NRZ parity error
Recovered parity PP correction or STW
Unrecovered parity PP correction or STW
Recovered channel error
Unrecovered channel error
Recovered AE thermal asperity found
Unrecovered AE thermal asperity found
Recovered AE open MR element error
Unrecovered AE open MR element error
Recovered AE IC over temperature error
Unrecovered AE IC over temperature error
Recovered AE IP clock count error
Unrecovered AE IP clock count error
Recovered AE high MR current error
Unrecovered AE high MR current error
Recovered AE write data BLS error
Unrecovered AE write data BLS error
Recovered AE invalid head address error
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
285
UEC
F625
1626
F627
1628
F629
162A
F62B
162C
F62D
162F
1630
F631
1632
F633
1634
F635
1636
F637
1638
F639
163A
F63B
163C
F63D
163E
F63F
1640
F641
F701
D703
1704
E705
E706
E707
D708
1709
D70A
E70B
E70C
E70D
E70E
Description
Unrecovered AE invalid head address error
Recovered AE power supply error
Unrecovered AE power supply error
Recovered AE open write head error
Unrecovered AE open write head error
Recovered AE write transition error
Unrecovered AE write transition error
Recovered AE no write head current error
Unrecovered AE no write head current error
Recovered Channel Pre-TA error
Recovered Channel write or NRZ parity error
Unrecovered Channel write or NRZ parity error
Recovered Channel Write Synth Unlock error
Unrecovered Channel Write Synth Unlock error
Recovered AE Short write read head error
Unrecovered AE Short write read head error
Recovered AE Short write head error
Unrecovered AE Short write head error
Recovered AE Non-selected write head error
Unrecovered AE Non-selected write head error
Recovered AE Write current in read error
Unrecovered AE Write current in read error
Recovered AE IH Open short error
Unrecovered AE IH Open short error
Recovered AE IH Deleay error
Unrecovered AE IH Deleay error
Recovered Channel Coarse tune timeout error
Unrecovered Channel Coarse tune timeout error
Format corrupted
Auto-reallocated due to write error
Recommend reassign due to write error
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 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
Recovered Data Address Mark error - rewritten
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
286
UEC
E70F
D710
E711
1712
F713
1714
F715
1716
F717
1718
F719
171A
F71B
171C
F71D
171E
F71F
1720
F721
1722
F723
D724
E725
E726
E727
E728
E729
E72A
D72B
172C
F72D
172E
F72F
1731
F732
1733
F734
1737
F738
1739
F73A
Description
Recovered Data Address Mark error - recommend rewrite
Recovered Data Address Mark error - reassigned
Recovered Data Address Mark error - recommend reassign
Recovered ECC error
Unrecovered ECC error
Recovered sector overflow
Unrecovered sector overflow
Recovered overrun
Unrecovered overrun
Recovered abort immediate
Unrecovered abort immediate
Recovered ECC overrun
Unrecovered ECC overrun
Recovered DRAM CRC error
Unrecovered DRAM CRC error
Recovered ID Parity error
Unrecovered ID Parity error
Recovered sudden death
Unrecovered sudden death
Recovered small thermal asperity
Unrecovered small thermal asperity
Recovered thermal asperity w/offline correction - reassigned
Recovered thermal asperity w/offline correction - recommend reassign
Recovered thermal asperity w/offline correction - recommend rewrite
Recovered thermal asperity w/offline correction - rewritten
Recovered thermal asperity - rewritten
Recovered thermal asperity - recommend rewrite
Recovered thermal asperity - recommend reassign
Recovered thermal asperity - reassigned
Recovered media error
Unrecovered media error
Recovered media error (off-line correction discarded)
Unrecovered media error (off-line correction discarded)
Recovered Write Fault
Unrecovered Write Fault
Recovered read/write abort
Unrecovered read/write abort
Recovered post write abort
Unrecovered post write abort
Recovered Post PES check write abort
Unrecovered Post PES check write abort
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
287
UEC
173B
F73C
173D
F73E
1746
1747
1748
1749
F74B
F74C
F74D
F74E
F74F
F750
F751
F752
F753
F754
F755
F756
F757
F758
1759
F75A
F75B
F75C
F75D
F75E
F761
F772
F773
F774
F775
F776
F777
F77A
F77B
F77D
1794
F795
1798
Description
Recovered data address mark error
Unrecovered data address mark error
Recovered sector miss
Unrecovered sector miss
Defect list format not supported
Primary defect list not found
Grown defect list not found
Partial defect list transferred
Primary defect list error
Grown defect list error
Too many heads
Skew table size error
Too many zones
Too many SIDs
Alternate track table full
Drive capacity too small
G-list full (Format command)
G-list full (2) (Format command)
Pointer repeat size error
DST slot size error
P-list full
Spare list full
Unknown recovered error
Unknown unrecovered error
Too many sectors
Internal media access timeout
Selftest failed
Max servo cylinder too small
Read/write command timeout
DASH starting timeout
ID table timeout
Servo timeout
Buffers timeout
DASH done timeout
DASH unknown timeout
Unrecovered channel SBW timeout
Unrecovered channelwrite error timeout
Recovery timeout
Recovered Drive DMA timeout error
Unrecovered Drive DMA timeout error
Recovered ID not found error
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
288
UEC
Description
F799
F79E
F79F
F7A0
F7A1
F7A2
F7A5
F7B1
17B2
F7B3
17B4
F7B5
Unrecovered ID not found error
Physical Square Wave Format Illegal
Skew Illegal
Customer cylinders not evenly divisible by track span
More than one head required for Serpentine format
Reserved area cannot be Serpentine format
Channel:Course tune timeout
Overall Command Timeout
Recovered abort window error
Unrecovered abort window error
Recovered shock sensor error
Unrecovered shock sensor error
1A02
2A02
3A02
1A03
2A03
3A03
1A04
2A04
3A04
1A05
2A05
3A05
1A14
2A14
3A14
1A32
2A32
3A32
1A43
2A43
3A43
1A4A
2A4A
3A4A
1A50
2A50
3A50
1A56
SMART: Temperature warning (no sense)
SMART: Temperature warning (recovered sense)
SMART: Temperature warning (unit attn sense)
SMART: Background selftest warning (no sense)
SMART: Background selftest warning (recovered sense)
SMART: Background selftest warning (unit attn sense)
SMART: Background Pre-Scan warning (no sense)
SMART: Background Pre-Scan warning (recovered sense)
SMART: Background Pre-Scan warning (unit attn sense)
SMART: Background Media Scan warning (no sense)
SMART: Background Media Scan warning (recovered sense)
SMART: Background Media Scan warning (unit attn sense)
SMART: Spare sector availability warning (no sense)
SMART: Spare sector availability warning (recovered sense)
SMART: Spare sector availability warning (unit attn sense)
SMART: Read error rate warning (no sense)
SMART: Read error rate warning (recovered sense)
SMART: Read error rate warning (unit attn sense)
SMART: Seek error rate warning (no sense)
SMART: Seek error rate warning (recovered sense)
SMART: Seek error rate warning (unit attn sense)
SMART: Write error rate warning (no sense)
SMART: Write error rate warning (recovered sense)
SMART: Write error rate warning (unit attn sense)
SMART: Load/unload cycle count warning (no sense)
SMART: Load/unload cycle count warning (recovered sense)
SMART: Load/unload cycle count warning (unit attn sense)
SMART: Spin up time warning (no sense)
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
289
UEC
Description
2A56
3A56
1A5B
2A5B
3ASB
1AFE
2AFE
3AFE
1AFF
2AFF
3AFF
SMART: Spin up time warning (recovered sense)
SMART: Spin up time warning (unit attn sense)
SMART: Spin up retry count warning (no sense)
SMART: Spin up retry count warning (recovered sense)
SMART: Spin up retry count warning (unit attn sense)
SMART: Thermal Sense trip (no sense)
SMART: Thermal Sense trip (recovered sense)
SMART: Thermal Sense trip (unit attn sense)
SMART: Test warning (no sense)
SMART: Test warning (recovered sense)
SMART: Test warning (unit attn sense)
FCxx
Unable to read RID or FID number xx
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
290
Index
A
Abbreviations ..................................................................................................................69
Acoustics .........................................................................................................................41
Active Notch ...................................................................................................................142
Actuator ..........................................................................................................................5
Additional information ...................................................................................................223
Additional Sense Length (Byte 7) ..................................................................................260
Address Frames ...............................................................................................................54
Alternate Sectors per Zone .............................................................................................133
Alternate Tracks per Logical Unit ..................................................................................133
Alternate Tracks per Zone ..............................................................................................133
Appendix .........................................................................................................................279
Automatic Read Reallocation Enabled ...........................................................................127
Automatic Rewrite/Reallocate ........................................................................................237
Automatic Write Reallocation Enabled ..........................................................................127
Average latency ..............................................................................................................12
B
Block Descriptor .............................................................................................................123
block format ....................................................................................................................73
Breather Hole ..................................................................................................................36
buffer overrun .................................................................................................................114
buffer underrun ...............................................................................................................114
Byte ordering conventions ..............................................................................................69
bytes from index format ..................................................................................................74
C
Caution ............................................................................................................................1
Command Information Unit ............................................................................................60
Command Processing During Execution of Active I/O process .....................................224
Command Processing During Startup and Format Operations .......................................227
Command processing while reserved .............................................................................235
Command Queuing .........................................................................................................236
Command queuing ..........................................................................................................236
Command Reordering .....................................................................................................236
Command reordering ......................................................................................................236
Command Time out Limits .............................................................................................244
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
Concurrent I/O Process ...................................................................................................236
Control Electronics .........................................................................................................5
Cooling requirements ......................................................................................................23
Corrosion test ..................................................................................................................22
D
DATA Information Units ................................................................................................62
Data Integrity ..................................................................................................................17
Data Recovery Procedure ...............................................................................................247
Data Reliability ...............................................................................................................31
Data Sheet .......................................................................................................................7
Data transfer speed ..........................................................................................................13
DC Power Requirements ................................................................................................27
Defect Descriptor ............................................................................................................73
defect descriptor ..............................................................................................................73
defect list .........................................................................................................................72
Deferred Error Condition ................................................................................................227
Degraded Mode ...............................................................................................................228
device cache fast writes ..................................................................................................115
device cache partial read hits ..........................................................................................115
device cache write hits ....................................................................................................115
Diagnostics ......................................................................................................................240
Disable Block Descriptor ................................................................................................120
Download Microcode and Save (Mode 0101b) ..............................................................216
Drive Characteristics .......................................................................................................7
Drive Mounting ...............................................................................................................36
Drive ready time .............................................................................................................13
Drive Service Strategy ....................................................................................................246
E
Electrical Interface ..........................................................................................................25
Electromagnetic Compatibility .......................................................................................45
Environment ....................................................................................................................21
Equipment errors .............................................................................................................31
Equipment Status ............................................................................................................17
European Standards Compliance ....................................................................................47
F
Failure prediction (PFA/S.M.A.R.T) ..............................................................................31
FC-AL attachment ..........................................................................................................49
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
FC-AL Connector ...........................................................................................................25
Flammability ...................................................................................................................47
Format Time ...................................................................................................................244
FORMAT UNIT .............................................................................................................70
format unit .......................................................................................................................70
FORMAT UNIT (04) ......................................................................................................70
Formatted Capacity .........................................................................................................7
Fundamentals ..................................................................................................................49
G
German Safety Mark .......................................................................................................47
Glossary ..........................................................................................................................1
Grown Defect List (Glist) ...............................................................................................173
H
Hard Reset .......................................................................................................................53
Head Disk Assembly ......................................................................................................5
I
Identification ...................................................................................................................43
Idle Time Function ..........................................................................................................244
IEEE registered name format ..........................................................................................51
Incorrect Length Indicator (Bit 5 of byte 2) ....................................................................258
inquiry .............................................................................................................................76
Inquiry Data ....................................................................................................................77
Interface Connector .........................................................................................................35
Internal Error Condition ..................................................................................................227
L
Labels ..............................................................................................................................43
Link Layer .......................................................................................................................54
Link Reset Sequence .......................................................................................................52
Log Page Parameters ......................................................................................................93
LOG SELECT .................................................................................................................89
LOG SELECT (4C) ........................................................................................................89
LOG SENSE ...................................................................................................................92
LOG SENSE (4D) ..........................................................................................................92
Logical Block Cache Segment Size ................................................................................138
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
M
Maximum Burst Size ......................................................................................................132
Maximum Pre-fetch ........................................................................................................138
Maximum Pre-fetch Ceiling ...........................................................................................138
Mechanical positioning ...................................................................................................11
Mechanical Specifications ..............................................................................................33
Merge G-List into P-List .................................................................................................125
Minimum Pre-fetch .........................................................................................................138
Mode Pages .....................................................................................................................239
MODE SELECT .............................................................................................................118, 119
MODE SELECT (15) .....................................................................................................118
MODE SELECT (55) .....................................................................................................119
MODE SENSE (1A) .......................................................................................................120
MODE SENSE (5A) .......................................................................................................153
Multiple Initiator Environment .......................................................................................239
Multiple Initiator Systems ..............................................................................................239
multiple initiator systems ................................................................................................239
N
Node and Port names ......................................................................................................50
node name .......................................................................................................................50
Non-operating shock .......................................................................................................40
Non-operating Vibrations ...............................................................................................39
O
OPEN Address Frame .....................................................................................................56
Operating shock ..............................................................................................................39
Operating Vibration ........................................................................................................39
Outline ............................................................................................................................33
Outline of the Drive ........................................................................................................3
overrun counter ...............................................................................................................115
Overview .........................................................................................................................239
P
Packaging ........................................................................................................................22
Page Code Valid .............................................................................................................182
Page Format ....................................................................................................................198
Parameter data for Read Keys .........................................................................................156
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Parameter data for Read Reservations ............................................................................157
Parameter list ..................................................................................................................160
Persistent Reservation .....................................................................................................155
PERSISTENT RESERVE IN (5E) .................................................................................155
PERSISTENT RESERVE OUT .....................................................................................158, 162
PERSISTENT RESERVE OUT (5F) .............................................................................158, 162
Persistent Reserve Out Parameter list .............................................................................160
PHY Error Handling .......................................................................................................54
PHY Layer ......................................................................................................................52
Physical Format ..............................................................................................................19
physical sector format .....................................................................................................75
Physical Sector Format (101b) .......................................................................................176
Post Error ........................................................................................................................128
Predictive Failure Analysis .............................................................................................255
PRE-FETCH ...................................................................................................................163
Preventive Maintenance ..................................................................................................31
Primary Defect List .........................................................................................................173
Priority Commands .........................................................................................................235
Priority commands ..........................................................................................................235
Product ID .......................................................................................................................7
Q
Queue Depth ...................................................................................................................236
Queue Full Status ............................................................................................................236
R
Random access ................................................................................................................15
Random Vibration ...........................................................................................................39
READ (10) - (28) ............................................................................................................165
Read Ahead .....................................................................................................................239
READ BUFFER (3C) .....................................................................................................166
Read Buffer Full Ratio ....................................................................................................132
Read Cache Disable ........................................................................................................138
READ CAPACITY .........................................................................................................170
READ CAPACITY command ........................................................................................170
Read Continuous .............................................................................................................127
READ DEFECT DATA (37) ..........................................................................................173
READ DEFECT DATA (B7) .........................................................................................177
READ LONG command .................................................................................................179
Read Retry Count ............................................................................................................128
REASSIGN BLOCKS (07) ............................................................................................180
Reassignment Time .........................................................................................................244
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
RECEIVE DIAGNOSTICS (1C) ....................................................................................182
Recommended Initiator ERP ..........................................................................................246
RELEASE (17) ...............................................................................................................186
RELEASE (57) ...............................................................................................................187
Reliability ........................................................................................................................31
REPORT LUNS (A0) .....................................................................................................191
Report Recovered Non Data Errors ................................................................................125
REQUEST SENSE (03) ..................................................................................................193
RESERVE (16) ...............................................................................................................194
RESERVE (56) ...............................................................................................................195
Reserved Area .................................................................................................................184
Reset ................................................................................................................................240
Reset Actions ..................................................................................................................240
Reset Sources ..................................................................................................................240
RESPONSE Information Units .......................................................................................62
REZERO UNIT (01) .......................................................................................................196
Ripple Voltage ................................................................................................................29
S
S.M.A.R.T .......................................................................................................................31
Safety ..............................................................................................................................47
SAS Attachment .............................................................................................................49
SAS Features ...................................................................................................................49
SAS OOB ........................................................................................................................53
SAS OOB (Out of Band) ................................................................................................53
SAS Speed Negotiation ..................................................................................................54
SCSI Command Set ........................................................................................................67
SCSI Control Byte ..........................................................................................................69
SCSI Protocol .................................................................................................................223
SCSI Sense Data .............................................................................................................257
SCSI Sense Data Format .................................................................................................257
SCSI Status Byte .............................................................................................................221
SCSI Status Byte Reporting ............................................................................................223
Sectors per Track ............................................................................................................134
SEEK (10) - (2B) ............................................................................................................197
SEEK (6) - (0B) ..............................................................................................................197
seek counter ....................................................................................................................114
Seek errors ......................................................................................................................31
seeks ................................................................................................................................114
Segmented Caching ........................................................................................................239
SEND DIAGNOSTIC (1D) ............................................................................................198
Sense Data .......................................................................................................................239
sense data ........................................................................................................................239
Sense Data Description ...................................................................................................258
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
Sense Key (Bit 3 - 0 of byte 2) .......................................................................................259
SenseData ........................................................................................................................257
Service Action .................................................................................................................155, 159
Size Enable .....................................................................................................................137
Sound power levels .........................................................................................................41
Spin up ............................................................................................................................51
Spindle stop time ............................................................................................................13
START STOP UNIT (1B) ..............................................................................................204
Start/Stop Cycles .............................................................................................................31
Storage requirements ......................................................................................................22
Storage time ....................................................................................................................22
Summary .........................................................................................................................161
Swept Sine Vibration ......................................................................................................39
SYNCHRONIZE CACHE (35) ......................................................................................205
T
Temperature and humidity ..............................................................................................21
Temperature Threshold ...................................................................................................126
Termination of I/O Processes .........................................................................................236
TEST UNIT READY (00) ..............................................................................................206
Throughput ......................................................................................................................14
Track Skew Factor ..........................................................................................................134
Tracks per Zone ..............................................................................................................134
Transfer Block ................................................................................................................127
Transport Layer ...............................................................................................................59
Type ................................................................................................................................159
U
UEC list ...........................................................................................................................279
UL and CSA Standard Conformity .................................................................................47
underrun counter .............................................................................................................115
Unit Attention Condition ................................................................................................225, 252
unit attention condition ...................................................................................................225
Unit Start/Stop Time .......................................................................................................244
V
Verify ..............................................................................................................................254
VERIFY (2F) ..................................................................................................................207
Vibration and Shock .......................................................................................................39
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specificationn
W
WRITE (10) - (2A) .........................................................................................................210
WRITE (6) - (0A) ...........................................................................................................209
WRITE AND VERIFY (2E) ...........................................................................................211, 213
WRITE BUFFER (3B) ...................................................................................................217
Write Buffer Empty Ratio ...............................................................................................132
Write Cache ....................................................................................................................236
Write Cache Enable ........................................................................................................137
WRITE LONG (3F) ........................................................................................................218
Write Retention Priority ..................................................................................................138
Write Retry Count ...........................................................................................................128
WRITE SAME (41) ........................................................................................................219
X
XFER_RDY Information Units ......................................................................................62
Z
zero seeks ........................................................................................................................114
Hitachi Ultrastar 15K147 (SAS) Hard Disk Drive Specification
© Copyright Hitachi Global Storage Technologies
Hitachi Global Storage Technologies
5600 Cottle Road
San Jose, CA 95193
Produced in the United States
11/06
All rights reserved Ultrastar™ is a trademark of
Hitachi Global Storage Technologies.
Microsoft, Windows XP, and Windows are trademarks
of Microsoft Corporation in the United States, other
countries, or both.
Other product names are trademarks or registered trademarks of their respective companies.
References in this publication to Hitachi Global Storage
Technologies products, programs or services do not
imply that Hitachi Global Storage Technologies intends
to make these available in all countries in which Hitachi
Global Storage Technologies operates.
Product information is provided for information purposes only and does not constitute a warranty.
Information is true as of the date of publication and is
subject to change. Actual results may vary.
This publication is for general guidance only. Photographs may show design models.
01 November 2006
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement