Ultrastar 15K147 Specification v3.1
Hard Disk Drive Specification
Ultrastar 15K147
3.5 inch SCSI Hard Disk Drive
Models:
HUS151414VL3800
HUS151473VL3800
HUS151436VL3800
HUS151414VL3600
HUS151473VL3600
HUS151436VL3600
Version 3.1
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 SCSI Hard Disk Drive Specification
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
Hard Disk Drive Specification
Ultrastar 15K147
3.5 inch SCSI Hard Disk Drive
Models:
Version 3.1
HUS151414VL3800
HUS151473VL3800
HUS151436VL3800
HUS151414VL3600
HUS151473VL3600
HUS151436VL3600
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 SCSI Hard Disk Drive Specification
1st Edition (Rev 1.0) (11 February 2004) DRAFT
2nd Edition (Rev 2.0)(30 September 2004) Revised
3rd Edition (Rev. 2.1)(09 March 2006) Revised
4th Edition (Rev. 3.1)(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.hitachigst.com
Hitachi Global Storage Technologies may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents.
©Copyright Hitachi Globlal 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 SCSI 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..........................................................................................................8
4.3.1 Product ID...............................................................................................................8
4.3.2 Worldwide ID - Block assignment .........................................................................9
4.4 Cylinder allocation...........................................................................................................10
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 (Plist) ......................................................................................................19
6.2 Reassigned format (Glist) ................................................................................................19
7.0 Electrical interface specification.........................................................................................21
7.1 Power connector ..............................................................................................................21
7.2 SCSI bus connector..........................................................................................................22
7.2.1 SCSI signal connector (68-pin model)....................................................................22
7.2.2 SCSI signal connector (80-pin SCA-2 model) .......................................................23
7.3 SCSI cable........................................................................................................................24
7.4 SCSI bus terminator.........................................................................................................24
7.5 Hot plug/unplug ...............................................................................................................24
7.6 SCSI bus electrical characteristics ...................................................................................24
7.7 Auxiliary connector on 68-pin model ..............................................................................25
7.8 Option jumper block ........................................................................................................26
7.9 Jumper signal Description on 80 pin Jumper Block ........................................................27
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
7.9.1 Disable Auto Spin (position 1-2) ............................................................................27
7.9.2 Auto Spin Delay and Delay Spin 12 / 6 (position 3-4) ...........................................27
7.9.3 Force Single Ended Mode (position 7-8)................................................................27
7.9.4 Reserved (position 9-10).........................................................................................27
7.9.5 LED Driver Out (position 11-12) ...........................................................................28
7.9.6 Positions #13-14 .....................................................................................................28
7.10 Jumper signal Description on 68 pin Jumper Block ......................................................29
7.10.1 LED Driver Out (position 1-2) .............................................................................29
7.10.2 Enable Termination Power (positions 3-4) ...........................................................29
7.10.3 Force Single Ended Mode (position 5-6)..............................................................29
7.10.4 Positions #7-8 to #13-14: Device ID ....................................................................29
7.11 Jumper Signal Description on 68 pin Jumper Block (J6) ..............................................30
7.11.1 Disable Auto Spin (position 1-2) ..........................................................................30
7.11.2 Auto Spin Delay and Delay Spin 12 / 6 (position 3-4 and 5-6)............................30
7.11.3 Disable Parity (position 7-8).................................................................................30
7.11.4 Disable Unit Attention (position 11-12) ...............................................................30
7.11.5 Reserved (positions 9-10 and 13-14) ...................................................................30
8.0 Environment.........................................................................................................................31
8.1 Temperature and humidity...............................................................................................31
8.2 Storage requirements .......................................................................................................32
8.2.1 Packaging................................................................................................................32
8.2.2 Storage time ............................................................................................................32
8.3 Corrosion test ...................................................................................................................32
8.4 Cooling requirements.......................................................................................................33
9.0 DC power requirements ......................................................................................................35
9.1 Power supply current, average, and peak.........................................................................36
9.2 Ripple voltage ..................................................................................................................38
9.3 Power consumption efficiency index...............................................................................39
10.0 Reliability............................................................................................................................41
10.1 Start/stop cycles .............................................................................................................41
10.2 Data reliability ...............................................................................................................41
10.3 Seek errors .....................................................................................................................41
10.4 Failure prediction (PFA/S.M.A.R.T) .............................................................................41
10.5 Preventive maintenance .................................................................................................41
10.6 Temperature warning .....................................................................................................41
11.0 Mechanical specifications..................................................................................................43
11.1 Outline ...........................................................................................................................43
11.2 Mechanical dimensions..................................................................................................44
11.3 Interface connector ........................................................................................................45
11.3.1 68 and 80 pin connectors ......................................................................................45
11.4 Mounting positions and tappings ...................................................................................46
11.5 Drive mounting ..............................................................................................................48
11.6 Heads unload and actuator lock .....................................................................................48
11.7 Breather hole..................................................................................................................48
12.0 Vibration and shock...........................................................................................................49
12.1 Operating vibration ........................................................................................................49
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
12.1.1 Random vibration .................................................................................................49
12.1.2 Swept sine vibration.............................................................................................49
12.2 Non-operating vibration.................................................................................................49
12.2.1 Random vibration .................................................................................................49
12.2.2 Swept sine vibration..............................................................................................49
12.3 Operating shock .............................................................................................................49
12.4 Non-operating shock.....................................................................................................50
12.4.1 Half sinewave shock pulse....................................................................................50
12.4.2 Rotational shock ..................................................................................................50
13.0 Acoustics .............................................................................................................................51
13.1 Sound power levels ........................................................................................................51
14.0 Identification ......................................................................................................................53
14.1 Labels.............................................................................................................................53
15.0 Standards ............................................................................................................................55
15.1 UL and CSA standard conformity .................................................................................55
15.2 European standards compliance.....................................................................................55
15.3 German safety mark.......................................................................................................55
15.4 Flammability ..................................................................................................................55
15.5 Corporate Standards Compliance ..................................................................................55
16.0 Electromagnetic Compatibility.........................................................................................57
17.0 SCSI Command Set ...........................................................................................................59
17.1 SCSI Control Byte .........................................................................................................61
17.2 Abbreviations.................................................................................................................61
17.3 Byte ordering conventions .............................................................................................61
17.4 FORMAT UNIT (04).....................................................................................................62
17.4.1 Defect list ..............................................................................................................64
17.4.2 Defect Descriptor ..................................................................................................65
17.5 INQUIRY (12) ...............................................................................................................68
17.5.1 Inquiry Data ..........................................................................................................69
17.6 LOG SELECT (4C) .......................................................................................................78
17.7 LOG SENSE (4D) .........................................................................................................81
17.7.1 Log Page parameters.............................................................................................82
17.7.2 Log Sense Page 0 ..................................................................................................83
17.7.3 Log Sense Page 2 ..................................................................................................84
17.7.4 Log Sense Page 3 ..................................................................................................86
17.7.5 Log Sense Page 5 ..................................................................................................88
17.7.6 Log Sense Page 6 ..................................................................................................90
17.7.7 Log Sense Page D .................................................................................................91
17.7.8 Log Sense Page E .................................................................................................92
17.7.9 Log Sense Page F..................................................................................................93
17.7.10 Log Sense Page 10 ..............................................................................................94
17.7.11 Log Sense Page 2F..............................................................................................97
17.7.12 Log Sense Page 30 ..............................................................................................98
17.7.13 Log Sense Page 37 ..............................................................................................101
17.8 MODE SELECT (15) ....................................................................................................103
17.9 MODE SELECT (55) ....................................................................................................104
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
17.10 MODE SENSE (1A) ....................................................................................................105
17.10.1 Mode Parameter List...........................................................................................107
17.10.2 Mode Page 00 (Vendor Unique Parameters) ......................................................111
17.10.3 Mode Page 01 (Read/Write Error Recovery Parameters)...................................114
17.10.4 Mode Page 02 (Disconnect/Reconnect Parameters) ...........................................119
17.10.5 Mode Page 03 (Format Device Parameters) .......................................................121
17.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters) ..................................123
17.10.7 Mode Page 07 (Verify Error Recovery Parameters)...........................................124
17.10.8 Mode Page 08 (Caching Parameters)..................................................................125
17.10.9 Mode Page 0A (Control Mode Page Parameters)...............................................128
17.10.10 Mode Page 0C (Notch Parameters) ..................................................................130
17.10.11 Mode page 19 (Port Control Parameters) .........................................................132
17.10.12 Mode Page 1A (Power Control) .......................................................................138
17.10.13 Mode Page 1C (Informational Exceptions Control) .........................................139
17.11 MODE SENSE (5A) ....................................................................................................141
17.12 PERSISTENT RESERVE IN (5E) ..............................................................................143
17.12.1 Service Action.....................................................................................................143
17.12.2 Parameter data for Read Keys ............................................................................144
17.12.3 Parameter Data for Read Reservations ...............................................................145
17.13 PERSISTENT RESERVE OUT (5F) ..........................................................................147
17.13.1 Service Action.....................................................................................................148
17.13.2 Scope...................................................................................................................151
17.13.3 Type ....................................................................................................................151
17.13.4 Parameter list ......................................................................................................153
17.13.5 Summary .............................................................................................................153
17.14 PRE-FETCH (34) ........................................................................................................155
17.15 READ (6) - (08) ...........................................................................................................156
17.16 READ (10) - (28) .........................................................................................................157
17.17 READ BUFFER (3C) ..................................................................................................158
17.17.1 Combined Header And Data (Mode 00000b).....................................................159
17.17.2 Read Data (Mode 00010b)..................................................................................159
17.17.3 Descriptor (Mode 00011b)..................................................................................160
17.17.4 Read Data from Echo Buffer (Mode 01010b) ....................................................161
17.17.5 Echo Buffer Descriptor (Mode 01011b) .............................................................161
17.17.6 Enable Expander Communications Protocol and Echo Buffer (Mode 11010b).161
17.18 READ CAPACITY (25) ..............................................................................................162
17.19 READ DEFECT DATA (37).......................................................................................164
17.19.1 Defect List Header ..............................................................................................166
17.19.2 Defect List Descriptor.........................................................................................166
17.19.3 Bytes from Index Format (100b) ........................................................................167
17.19.4 Physical Sector Format (101b) ...........................................................................167
17.20 READ DEFECT DATA (B7) ......................................................................................168
17.20.1 Defect List Header ..............................................................................................168
17.20.2 Defect List Descriptor.........................................................................................169
17.20.3 Bytes from Index Format (100b) ........................................................................169
17.20.4 Physical Sector Format (101b) ...........................................................................169
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
17.21 READ LONG (3E) ......................................................................................................170
17.22 REASSIGN BLOCKS (07) .........................................................................................171
17.23 RECEIVE DIAGNOSTICS RESULTS (1C) ..............................................................173
17.23.1 Receive Diagnostic Results Page 0.....................................................................173
17.23.2 Receive Diagnostic Results Page 40...................................................................174
17.24 RELEASE (17) ............................................................................................................175
17.25 RELEASE (57) ............................................................................................................176
17.26 REPORT DEVICE IDENTIFIER (A3) .......................................................................177
17.27 REPORT LUNS (A0) ..................................................................................................179
17.28 REQUEST SENSE (03)...............................................................................................180
17.29 RESERVE (16) ............................................................................................................181
17.30 RESERVE (56) ............................................................................................................182
17.31 REZERO UNIT (01)....................................................................................................183
17.32 SEEK (6) - (0B) ...........................................................................................................184
17.33 SEEK (10) - (2B) .........................................................................................................185
17.34 SEND DIAGNOSTIC (1D) .........................................................................................186
17.34.1 Send Diagnostic Page 0 ......................................................................................188
17.34.2 Send Diagnostic Page 40 ....................................................................................188
17.35 SET DEVICE IDENTIFIER (A4) ...............................................................................190
17.36 START STOP UNIT (1B) ...........................................................................................191
17.37 SYNCHRONIZE CACHE (35) ...................................................................................192
17.38 TEST UNIT READY (00) ...........................................................................................193
17.39 VERIFY (2F) ...............................................................................................................194
17.40 VERIFY (16) - (8F) .....................................................................................................195
17.41 WRITE (6) - (0A) ........................................................................................................196
17.42 WRITE (10) - (2A) ......................................................................................................197
17.43 WRITE AND VERIFY (16) - (8E)..............................................................................198
17.44 WRITE AND VERIFY (2E)........................................................................................199
17.45 WRITE BUFFER (3B) ................................................................................................200
17.45.1 Combined Header And Data (Mode 00000b).....................................................201
17.45.2 Write Data (Mode 00010b).................................................................................201
17.45.3 Download Microcode (Mode 00100b) ...............................................................202
17.45.4 Download Microcode and Save (Mode 00101b) -Single Binary File ................202
17.45.5 Download Microprocessor Microcode and Save (Mode 00111b) - Multiple Binary
Files..................................................................................................................................203
17.45.6 Write Data to Echo Buffer (Mode 01010b) ........................................................203
17.45.7 Enable Expander Communications Protocol (Mode 11010b) ............................203
17.46 WRITE LONG (3F).....................................................................................................204
17.47 WRITE SAME (41) .....................................................................................................205
17.48 WRITE SAME (16) - (93) ...........................................................................................206
18.0 SCSI Status Byte ................................................................................................................207
19.0 SCSI message system .........................................................................................................209
19.1 Supported messages .......................................................................................................210
19.1.1 Task Complete (00) ..............................................................................................210
19.1.2 Synchronous Data Transfer Request (01, 03, 01h) ...............................................211
19.1.3 Wide Data Transfer Request (01, 02, 03h) ...........................................................215
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
19.1.4 Parallel Protocol Request (01, 06, 04h) ................................................................217
19.1.5 Save Data Pointer (02) ..........................................................................................219
19.1.6 Restore Pointers (03) ............................................................................................219
19.1.7 Disconnect (04).....................................................................................................220
19.1.8 Initiator Detected Error (05) .................................................................................220
19.1.9 Abort Task Set (06)...............................................................................................220
19.1.10 Message Reject (07)............................................................................................220
19.1.11 No Operation (08) ...............................................................................................220
19.1.12 Message Parity Error (09)...................................................................................221
19.1.13 Linked Task Complete (0A) ...............................................................................221
19.1.14 Linked Task Complete With Flag (0B) ..............................................................221
19.1.15 Target Reset (0C)................................................................................................221
19.1.16 Abort Task (0D)..................................................................................................221
19.1.17 Clear Task Set (0E).............................................................................................221
19.1.18 Logical Unit Reset (17).......................................................................................221
19.1.19 Queue Tag messages (20H, 21H, 22H) ..............................................................222
19.1.20 Ignore Wide Residue ..........................................................................................222
19.1.21 Identify (80 - FF) ................................................................................................223
19.2 Supported message functions.........................................................................................224
19.3 Attention condition ........................................................................................................225
20.0 Additional information......................................................................................................227
20.1 SCSI Protocol ................................................................................................................227
20.1.1 Priority of SCSI Status Byte Reporting ................................................................227
20.1.2 Invalid LUN in Identify Message .........................................................................227
20.1.3 Incorrect Initiator Connection...............................................................................228
20.1.4 Command Processing During Execution of Active I/O Process ..........................228
20.1.5 Unit Attention Condition ......................................................................................230
20.1.6 Command processing during startup and format operations ................................231
20.1.7 Internal Error Condition........................................................................................231
20.1.8 Deferred Error Condition......................................................................................231
20.1.9 Degraded Mode.....................................................................................................232
20.1.10 Command Processing while Reserved................................................................239
20.2 Priority Commands ........................................................................................................239
20.3 Command Queuing ........................................................................................................240
20.3.1 Queue Depth .........................................................................................................240
20.3.2 Tagged Queuing....................................................................................................240
20.3.3 Untagged Queuing ................................................................................................240
20.3.4 Command Queuing Rule ......................................................................................240
20.3.5 Queue Full Status..................................................................................................240
20.3.6 Device Behavior on Command Queuing ..............................................................240
20.4 Command Reordering....................................................................................................241
20.5 Concurrent I/O Process ..................................................................................................241
20.6 Write Cache ...................................................................................................................241
20.7 Automatic Rewrite/Reallocate .......................................................................................242
20.8 Segmented Caching .......................................................................................................244
20.8.1 Overview...............................................................................................................244
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
20.8.2 Read Ahead...........................................................................................................244
20.9 Multiple Initiator Systems .............................................................................................244
20.9.1 Sense Data.............................................................................................................244
20.9.2 Mode Pages...........................................................................................................244
20.10 Reselection Time-out ...................................................................................................244
20.11 Single Initiator Selection .............................................................................................244
20.12 Non-arbitrating systems ...............................................................................................244
20.13 Selection without ATN ................................................................................................245
20.14 Multiple Initiator Environment ....................................................................................245
20.14.1 Initiator Sense Data.............................................................................................245
20.14.2 Initiator Mode Select/Mode Sense Parameters ...................................................245
20.14.3 Initiator Data Transfer Mode Parameter .............................................................245
20.15 Contingent Allegiance Condition ................................................................................245
20.16 Reset.............................................................................................................................245
20.16.1 Reset Sources ......................................................................................................246
20.16.2 Reset Actions ......................................................................................................246
20.17 Diagnostics...................................................................................................................246
20.17.1 Power on Diagnostics .........................................................................................246
20.17.2 Self-test via SEND DIAGNOSTIC Command...................................................247
20.18 Idle Time Function.......................................................................................................250
20.19 Command Time out Limits .........................................................................................250
20.19.1 Reassignment Time.............................................................................................250
20.19.2 Format Time .......................................................................................................250
20.19.3 Start/Unit Stop Time ...........................................................................................250
20.19.4 Medium Access Command Time .......................................................................251
20.19.5 Time-out Limits for Other Commands ...............................................................251
20.20 Recommended Initiator ERP .......................................................................................252
20.20.1 Drive Service Strategy ........................................................................................252
20.20.2 Recommendations for System Error Log ...........................................................253
20.20.3 Data Recovery Procedure ...................................................................................253
20.20.4 Nondata Error Recovery Procedure ....................................................................255
21.0 SCSI Sense Data.................................................................................................................261
21.1 SCSI Sense Data Format................................................................................................261
21.2 Sense Data Description ..................................................................................................262
21.2.1 Valid (Bit 7 of byte 0)...........................................................................................262
21.2.2 Error Code (Bit 6 - 0 of byte 0) ............................................................................262
21.2.3 ILI: Incorrect Length Indicator (Bit 5 of byte 2) ..................................................262
21.2.4 Sense Key (Bit 3 - 0 of byte 2) .............................................................................263
21.2.5 Information Bytes (Byte 3 through 6)...................................................................264
21.2.6 Additional Sense Length (Byte 7) ........................................................................264
21.2.7 Command Specific Information (Byte 8 through 11) ...........................................264
21.2.8 Additional Sense Code/Qualifier (Byte 12 and 13) ..............................................265
21.2.9 RU: Field Replaceable Unit (Byte 14).................................................................281
21.2.10 Sense Key Specific (Byte 15 through 17)...........................................................281
21.2.11 Reserved (Byte 18 through 19) ...........................................................................283
21.2.12 Vendor unique error information (Byte 20 through 23) .....................................283
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
21.2.13 Physical Error Record (Byte 24 thru 29) ............................................................283
21.2.14 Reserved (Byte 30 through 31) ...........................................................................283
22.0 Appendix. UEC list ...........................................................................................................285
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
List of Tables
Table 1. Formatted capacity.......................................................................................7
Table 2. Data sheet.....................................................................................................7
Table 3. Product ID in Inquiry Command .................................................................8
Table 4. Block assignment of worldwide ID in INQUIRY Command .....................9
Table 5. Cylinder allocation.......................................................................................10
Table 6. Mechanical positioning performance ..........................................................11
Table 7. Full stroke seek time ....................................................................................12
Table 8. Latency time ................................................................................................12
Table 9. Drive ready time ..........................................................................................13
Table 10. Spindle stop time .......................................................................................13
Table 11. Data transfer speed (sector size 512 Byte case).........................................13
Table 12. Simple sequential access performance (sector size 512 Byte case)...........14
Table 13. Random access performance (sector size 512 Byte case)..........................15
Table 14. Table of signals (68-pin)............................................................................22
Table 15. Table of signals (80-pin)............................................................................23
Table 16. Auto start delay & delay start 6/12 drive behavior....................................27
Table 17. SCSI Device ID .........................................................................................29
Table 18. Operating and non-operating conditions ...................................................31
Table 19. Maximum allowable module surface temperatures ...................................33
Table 20. Input voltage ..............................................................................................35
Table 21. Model 147GB ............................................................................................36
Table 22. Model 147GB: 5V Current during spinup .................................................36
Table 23. Model 147GB: 12V Current during spinup ...............................................37
Table 24. Model 73GB ..............................................................................................38
Table 25. Model 36GB ..............................................................................................38
Table 26. Power supply generated ripple at drive power connector..........................38
Table 27. Power consumption efficiency index.........................................................39
Table 28. Physical dimensions...................................................................................44
Table 29. A-weighted sound power levels.................................................................51
Table 30. SCSI Commands Supported ......................................................................59
Table 31. SCSI Control Byte .....................................................................................61
Table 32. FORMAT UNIT (04) ................................................................................62
Table 33. Format of Defect List Header ....................................................................64
Table 34. Defect Descriptor - Block Format (for n + 1 defects) ...............................65
Table 35. Defect Descriptor - Bytes From Index Format (for n = 1 defects) ............66
Table 36. Defect Descriptor - Physical Sector Format (for n + 1 defects) ................67
Table 37. INQUIRY (12)...........................................................................................68
Table 38. Page Code descriptions..............................................................................68
Table 39. Inquiry Data Format - EVPD = 0, Page Code = 0 .....................................69
Table 40. Inquiry Data - EVPD = 1 (Page Code = 00h)............................................70
Table 41. Inquiry Data - EVPD = 1 (Page Code = 03h)............................................72
Table 42. Inquiry Data - EVPD = 1 (Page Code = 80h)............................................74
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
Table 43. Inquiry Data - EVPD = 1 (Page Code = 83h)............................................75
Table 44. Inquiry Data - EVPD = 1 (Page Code = D1h) ...........................................76
Table 45. Inquiry Data - EVPD = 1 (Page Code = D2h) ...........................................77
Table 46. Log Select (4C)..........................................................................................78
Table 47. Log Sense (4D) ..........................................................................................81
Table 48. Log Sense Page 0.......................................................................................83
Table 49. Log Sense Page 2 (part 1 of 2)...................................................................84
Table 50. Log Sense Page 2 (part 2 of 2)...................................................................85
Table 51. Log Sense Page 3 (part 1 of 2)...................................................................86
Table 52. Log Sense Page 3 (part 2 of 2)...................................................................87
Table 53. Log Sense Page 5 (part 1 of 2)...................................................................88
Table 54. Log Sense Page 5 (part 2 of 2)...................................................................89
Table 55. Log Sense Page 6.......................................................................................90
Table 56. Log Sense Page D ......................................................................................91
Table 57. Log Sense Page E ......................................................................................92
Table 58. Log Sense Page F.......................................................................................93
Table 59. Log Sense Page F, Application Client Log ...............................................93
Table 60. Log Sense Page 10.....................................................................................94
Table 61. Log Sense Page 10, self-test results...........................................................94
Table 62. Log Sense Page 10, self-test results...........................................................95
Table 63. Log Sense Page 10, Extended Segment Number.......................................96
Table 64. Log Sense Page 2F....................................................................................97
Table 65. Log Sense Page 30.....................................................................................98
Table 66. Log Sense Page 37.....................................................................................101
Table 67. Mode Select (15)........................................................................................103
Table 68. Mode Select (55)........................................................................................104
Table 69. Mode Sense (1A) .......................................................................................105
Table 70. Page Code Usage .......................................................................................106
Table 71. Mode parameter header (6)........................................................................107
Table 72. Mode parameter header (10)......................................................................107
Table 73. Mode Parameter Block Descriptor ............................................................109
Table 74. Mode Parameter Page Format ...................................................................110
Table 75. Supported Page Codes ...............................................................................110
Table 76. Vendor Unique Parameters - Page00.........................................................111
Table 77. Mode Page 01 (Vendor Unique Parameters) .............................................114
Table 78. Mode Page 02 (Disconnect/Reconnect Parameters)..................................119
Table 79. Mode Page 03 (Format Device Parameters) ..............................................121
Table 80. Mode Page 04 (Rigid Disk Drive Geometry Parameters) .........................123
Table 81. Mode Page 07 (Verify Error Recovery Parameters)..................................124
Table 82. Page 08 (Caching Parameters)...................................................................125
Table 83. Page 0A (Control Mode Page Parameters) ................................................128
Table 84. Page 0C (Notch Parameters)......................................................................130
Table 85. Short (Port Control Parameters) Short Format .........................................132
Table 86. Page 19 (Port Control Parameters) Long Format ......................................133
Table 87. Margin Control Subpage............................................................................134
Table 88. Saved Training Configuration Subpage.....................................................135
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
Table 89. Negotiated Settings Subpage .....................................................................136
Table 90. Report Transfer Capabilities Subpage .......................................................137
Table 91. Page 1A (Power Control)...........................................................................138
Table 92. Page 1C (Informational Exceptions Control) ............................................139
Table 93. Mode Sense (5A) .......................................................................................141
Table 94. Persistent Reserve In (5E) .........................................................................143
Table 95. PERSISTENT RESERVE IN, Service Action Codes ...............................143
Table 96. PERSISTENT RESERVE IN, parameter data for Read Keys ..................144
Table 97. PERSISTENT RESERVE IN, parameter data for Read Reservations......145
Table 98. PERSISTENT RESERVE IN, Read Reservation Descriptor....................146
Table 99. PERSISTENT RESERVE OUT (5F) ........................................................147
Table 100. PERSISTENT RESERVE OUT, Service Action Code...........................148
Table 101. PERSISTENT RESERVE OUT, Scope Code ........................................151
Table 102. PERSISTENT RESERVE OUT, Type Code ..........................................151
Table 103. Conflict between new and existing Persistent Reserve ...........................152
Table 104. PERSISTENT RESERVE OUT, Parameter List.....................................153
Table 105. PERSISTENT RESERVE OUT, Service Action, Parameters and Generation counter
153
Table 106. APTPL and information held by a drive..................................................154
Table 107. PRE-FETCH (34) ....................................................................................155
Table 108. READ (6) - (08).......................................................................................156
Table 109. READ (10) - (28) ....................................................................................157
Table 110. READ BUFFER (3C) ..............................................................................158
Table 111. Read Buffer Header .................................................................................159
Table 112. Read Buffer Description ..........................................................................160
Table 113. Echo Buffer Descriptor............................................................................161
Table 114. READ CAPACITY (25)..........................................................................162
Table 115. Format of READ CAPACITY command reply.......................................163
Table 116. READ DEFECT DATA (37)...................................................................164
Table 117. Defect List Format ...................................................................................165
Table 118. Defect List Header ...................................................................................166
Table 119. Defect List Descriptor..............................................................................166
Table 120. Defect Descriptors of Bytes from Index Format .....................................167
Table 121. Defect Descriptors of Physical Sector Format.........................................167
Table 122. READ DEFECT DATA (B7) ..................................................................168
Table 123. Defect List Header ...................................................................................168
Table 124. Defect List Descriptor..............................................................................169
Table 125. Defect Descriptors of Bytes from Index Format .....................................169
Table 126. Defect Descriptors of Physical Sector Format.........................................169
Table 127. READ LONG (3E) ..................................................................................170
Table 128. REASSIGN BLOCKS (07) .....................................................................171
Table 129. Format of Reassign Blocks data ..............................................................172
Table 130. RECEIVE DIAGNOSTIC RESULTS (1C) ............................................173
Table 131. Receive Diagnostic Results page 0..........................................................173
Table 132. Receive Diagnostic Results Page 40........................................................174
Table 133. Translated address ...................................................................................174
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
Table 134. RELEASE (17) ........................................................................................175
Table 135. RELEASE (57) ........................................................................................176
Table 136. REPORT DEVICE IDENTIFIER (A3)...................................................177
Table 137. Report Device Identifier parameter list ...................................................178
Table 138. REPORT LUNS (A0) ..............................................................................179
Table 139. LUN Reporting parameter list format......................................................179
Table 140. REQUEST SENSE (03) ..........................................................................180
Table 141. RESERVE (16) ........................................................................................181
Table 142. RESERVE (56) ........................................................................................182
Table 143. REZERO UNIT (01)................................................................................183
Table 144. SEEK (6) - (0B) .......................................................................................184
Table 145. SEEK (10) - (2B) .....................................................................................185
Table 146. SEND DIAGNOSTIC (1D) .....................................................................186
Table 147. SEND DIAGNOSTIC Function Code (1D) ............................................187
Table 148. Diagnostic Page 0 ....................................................................................188
Table 149. Diagnostic Page 40 ..................................................................................188
Table 150. Address to translate..................................................................................189
Table 151. SET DEVICE IDENTIFIER (A4) ...........................................................190
Table 152. SET DEVICE IDENTIFIER, Parameter List ..........................................190
Table 153. START STOP UNIT (1B) .......................................................................191
Table 154. SYNCHRONIZE CACHE (35) ...............................................................192
Table 155. TEST UNIT READY (00).......................................................................193
Table 156. VERIFY (2F) ...........................................................................................194
Table 157. Write (16) - (8F) ......................................................................................195
Table 158. WRITE (6) - (0A) ....................................................................................196
Table 159. WRITE (10) - (2A) ..................................................................................197
Table 160. Write and Verify (8E) ..............................................................................198
Table 161. WRITE AND VERIFY (2E) ...................................................................199
Table 162. WRITE BUFFER (3B) ............................................................................200
Table 163. Write Buffer Header ................................................................................201
Table 164. WRITE LONG (3F).................................................................................204
Table 165. WRITE SAME (41) .................................................................................205
Table 166. Write Same (16) - (93).............................................................................206
Table 167. SCSI Status Byte. Format of the SCSI STATUS byte. ..........................207
Table 168. Synchronous Data Transfer Request. ......................................................211
Table 169. Initiator Request/Target Response (LVD mode) .....................................212
Table 170. Initiator Request/Target Response (SE mode) ........................................213
Table 171. Target response to Initiator's transfer period (LVD mode) .....................214
Table 172. Target response to Initiator's transfer period (SE mode) .........................215
Table 173. Wide Data Transfer Request....................................................................216
Table 174. Initiator request/Target response .............................................................216
Table 175. Target request to Initiator ........................................................................217
Table 176. Parallel Protocol Request.........................................................................217
Table 177. Initiator Request/Target Response (DT_REQ = 1, IU_REQ = 1) ...........218
Table 178. Initiator Request/Target Response (DT_REQ = 1, IU_REQ = 0) ...........218
Table 179. Initiator Request/Target Response (DT_REQ = 0, IU_REQ = 0) ...........218
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
Table 180. Bit position table for Byte 7 of Parallel Protocol Request.......................219
Table 181. Queue Tag messages................................................................................222
Table 182. Ignore Wide Residue message format .....................................................222
Table 183. Spindle Motor Degraded Mode - Disable Auto Start ..............................232
Table 184. Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up ...........234
Table 185. Spindle Motor Degraded Mode - Spindle Start Failure...........................235
Table 186. Spindle Motor Degraded Mode - Spindle Stopped by Unit Stop Command236
Table 187. Self Configuration Failure Degraded Mode ...........................................237
Table 188. Format Command Failure Degraded Mode .............................................238
Table 189. Sense data combinations with auto/recommend rewrite/reallocate.........243
Table 190. Short and Extended Self-Test Description ..............................................248
Table 191. Recommend Reassign Errors...................................................................254
Table 192. Log Only Errors .......................................................................................254
Table 193. Format of Sense Data...............................................................................261
Table 194. Field Pointer Bytes ..................................................................................281
Table 195. Actual Retry Count ..................................................................................282
Table 196. Progress Indication ..................................................................................283
Table 197. Unit Error Codes list ................................................................................285
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
1.0 General
1.1 Introduction
This document describes the specifications of the following Hitachi 3.5 inch SCSI drives.
•
HUS151414VL3600
(68-pin)
•
HUS151414VL3800
(80-pin)
•
HUS151473VL3600
(68-pin)
•
HUS151473VL3800
(80-pin)
•
HUS151436VL3600
(68-pin)
•
HUS151436VL3800
(80-pin)
Note: The specifications in this document are subject to change without notice.
For technical and ordering information, please visit our website at: http://www.hitachigst.com/portal/site/hgst
1.2 Glossary
Word
Meaning
Kb
Kilobit = 1000 bits
Mb
Megabit = 1,000,000 bits
GB
Gigabyte = 1,000,000,000 bytes
MB
Megabyte = 1,000,000 bytes
KB
Kilobyte = 1000 bytes
PFA
Predictive Failure Analysis
S.M.A.R.T.
Self-Monitoring and Reporting Technology
SE
Single-ended SCSI
LVD
Low Voltage Differential SCSI
FC-AL
Fibre Channel - Arbitrated Loop
1.3 Caution
This drive can be damaged by electrostatic discharge (ESD). 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 SCSI Hard Disk Drive Specification
1
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
2
2.0 Outline of the drive
•
Storage capacities of 147 GB, 73 GB, and 36 GB
•
Ultra 320
•
Variable Sector Size (512-528 bytes/sector)
•
Tagged Command Queuing support
•
Automatic read/write data transfer
•
3.7 ms seek time in read operation for 147 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
•
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
•
Spindle rotation of 15,000 RPM
•
Automatic actuator lock
•
PFA (SMART)
•
Glass substrate disks
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
3
Hitachi Ultrastar 15K147 SCSI 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 SCSI Hard Disk Drive Specification
5
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
6
4.0 Drive characteristics
4.1 Formatted capacity
Table 1: Formatted capacity
Description
HUS151414VL3800
HUS151473VL3800
HUS151436VL3800
HUS151414VL3600
HUS151473VL3600
HUS151436VL3600
Label capacity
147 GB
73 GB
36 GB
Number of heads
10
5
3
Number of disks
5
3
2
Total data bytes (512 147,015,821,824
bytes/sector)
73,407,900,160
36,703,949,824
Total logical data
blocks
287,140,277
143,374,805
71,687,402
(111D69B5h)
(88BB9D5h)
(445DCEAh)
4.2 Data sheet
Table 2: Data sheet
Buffer to/from media
760 - 1129 Mb/sec
Host to/from buffer (interface transfer rate)
320 [MB/sec]
Data buffer size
16MB
Number of buffer segments
1 - 256
Rotational speed
15,000 RPM
Recording density
686 [Kbpi] (Max)
Track density
90,000 [TPI] (average)
Areal density
61.7 [Gb/sq. in]
Data zone
24 for 147GB and 73GB, 20 for 36GB
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
7
4.3 Inquiry information
4.3.1 Product ID
Product ID in section 17.5.1.1, "Inquiry Data format - CmdDt = 0, EVPD = 0, Page code = 0" on page 76. is as follows:
Table 3: Product ID in INQUIRY Command
Product ID
Description
HUS151436VL3600
36 GB, 68-pin
HUS151436VL3800
36 GB, 80-pin
HUS151473VL3600
73 GB, 68-pin
HUS151473VL3800
73 GB, 80-pin
HUS151414VL3600
147 GB, 68-pin
HUS151414VL3800
147 GB, 80-pin
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
8
4.3.2 Worldwide ID - Block assignment
Block assignment of Worldwide ID is as follows:
Table 4: Block assignment of worldwide ID in INQUIRY Command
Manufacturing site
Product Name and Associtated
Models
Block assignment
HUS151414VLxxx0
Singapore
HUS151473VLxxx0
001h(1)
HUS151436VLxxx0
xxx Interface Values:380 = Ultra 320, 80 pin
360 = Ultra 320, 68 pin
F20 = Fibre Channel, 2GB
Note (1) - Additional block assignment will be issued as needed based on actual production volume
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
9
4.4 Cylinder allocation
Table 5: Cylinder allocation
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 SCSI Hard Disk Drive Specification
10
4.5.1 Mechanical positioning
4.5.1.1 Average seek time (including settling)
Table 6: Mechanical positioning performance
Model
Command
Typical (ms)
Max
147 GB
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
73 GB
36 GB
“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 SCSI Hard Disk Drive Specification
11
4.5.1.2 Full stroke seek time
Table 7: 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 8: Latency time
Rotation
Time for a revolution (ms)
Average latency (ms)
15,000 RPM
4.0
2.0
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
12
4.5.2 Drive ready time
Table 9: 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
4.5.3 Spindle stop time
Table 10: Spindle stop time
Model
Typical (sec)
Maximum (sec)
147 GB Model
13
20
73 GB Model
9
20
36 GB Model
8
20
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 54.
4.5.4 Data transfer speed
Table 11: Data transfer speed (sector size 512 Byte case)
Description
Zone
Model
Typical (MB / Sec)
Read
Write
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
--
Disk-buffer transfer
Instantaneous
Measured typical values
Notes:
•
Instantaneous disk-buffer transfer rate is derived by: (Number of sectors on a track) x 512 x (revolutions/sec)
•
For this table, '1 MB / Sec' should be interpreted as 1,000,000 bytes per Second.
•
The number of sectors per track will vary because of the linear density recording.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
13
•
Sustained disk-buffer transfer rate is the average rate measured while transferring multiple cylinders of data. It differs from the instantaneous transfer rate because of the time required to change tracks (Cylinder skew and Head
skew). In addition, time is added for the occasional missed transfer.
4.5.5 Buffering operation (read ahead/write cache)
This hard disk drive has a buffer for read ahead (see 20.8, “Segmented Caching” on page 244).
4.5.6 Throughput
4.5.6.1 Simple sequential access
Table 12: Simple sequential access performance (sector size 512 Byte case)
Operation
Zone
0
0
0
Model
147 GB
73 GB
36 GB
Typical (ms)
Read
Write
186
187
185
185
185
185
Maximum (ms)
Read
Write
186
187
186
185
185
185
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 SCSI Hard Disk Drive Specification
14
4.5.6.2 Random access
Table 13: 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 SCSI Hard Disk Drive Specification
15
Hitachi Ultrastar 15K147 SCSI 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 SCSI Hard Disk Drive Specification
17
Hitachi Ultrastar 15K147 SCSI 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 location is calculated using internally maintained tables.
6.1 Shipped format (Plist)
•
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.
Plist physical format
Figure 1 : Plist 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 (Glist)
•
Glist is prepared for 5000 LBAs.
•
Multiple reassignment of the same LBA does not increase the number of Glist entries.
•
A cylinder for spare sectors is prepared every 512 physical cylinders.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
19
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
20
7.0 Electrical interface specification
7.1 Power connector
The power connector of 68-pin models complies with the SFF-8009 Rev. 2.0. Power pin assignment of 68-pin models is as
shown below.
4
3
2
1
Pin
1
2
3
4
Voltage
+12 V
GND
GND
+5V
80-pin SCA-2 models use a Molex p/n 87641-0021 or DDK p/n HD2PF80-A11 connector, and 68 pin models use DDK p/n
HDW-RB68124G connector, which is compatible with the specification of “Single Attachment for Small SCSI Disk Drives”
SPI-4 document, Annex C.
Power pin assignment of the 80-pin (SCA-2) model is shown in Section 7.2.2, “SCSI signal connector (80-pin SCA-2 model)”
on page 23.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
21
7.2 SCSI bus connector
The Hitachi Ultrastar 15K147 has 68-pin models and 80-pin SCA-2 models.
7.2.1 SCSI signal connector (68-pin model)
The pin assignments of the interface signals conform to SPI-4 as shown in the table below.
Table 14: Table of signals (68-pin)
Connector contact
number
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
Note:
Signal name
+DB(12)
+DB(13)
+DB(14)
+DB(15)
+DB(P1)
+DB(0)
+DB(1)
+DB(2)
+DB(3)
+DB(4)
+DB(5)
+DB(6)
+DB(7)
+P_CRCA
Ground
DIFFSENS(*2)
TERMPWR(*1)
TERMPWR(*1)
Reserved
Ground
+ATN
Ground
+BSY
+ACK
+RST
+MSG
+SEL
+C/D
+REQ
+I/O
+DB(8)
+DB(9)
+DB(10)
+DB(11)
Connector contact
number
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Signal name
-DB(12)
-DB(13)
-DB(14)
-DB(15)
-DB(P1)
-DB(0)
-DB(1)
-DB(2)
-DB(3)
-DB(4)
-DB(5)
-DB(6)
-DB(7)
-P_CRCA
Ground
Ground
TERMPWR(*1)
TERMPWR(*1)
Reserved
Ground
-ATN
Ground
-BSY
-ACK
-RST
-MSG
-SEL
-C/D
-REQ
-I/O
-DB(8)
-DB(9)
-DB(10)
-DB(11)
*1 TERMPWR can be disabled
*2 HVD is not supported
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
22
7.2.2 SCSI signal connector (80-pin SCA-2 model)
Table 15: Table of signals (80-pin)
Connector contact
number
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Note:
Signal name
12 Volt Charge
12 volt
12 volt
12 volt
Opt 3.3 V/NC
Opt 3.3 V/NC
-DB(11)
-DB(10)
-DB(9)
-DB(8)
-I/O
-REQ
-C/D
-SEL
-MSG
-RST
-ACK
-BSY
-ATN
-P_CRCA
-DB(7)
-DB(6)
-DB(5)
-DB(4)
-DB(3)
-DB(2)
-DB(1)
-DB(0)
-DB(P1)
-DB(15)
-DB(14)
-DB(13)
-DB(12)
5 Volt
5 Volt
5 Volt Charge
Spindle Sync/NC
RMT START
SCSI ID (0)
SCSI ID (2)
Connector contact
number
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
Signal name
12V Ground
12V Ground
12V Ground
Mated 1
Opt 3.3 V charge/NC
DIFFSENS(*1)
+DB(11)
+DB(10)
+DB(9)
+DB(8)
+I/O
+REQ
+C/D
+SEL
+MSG
+RST
+ACK
+BSY
+ATN
+P_CRCA
+DB(7)
+DB(6)
+DB(5)
+DB(4)
+DB(3)
+DB(2)
+DB(1)
+DB(0)
+DB(P1)
+DB(15)
+DB(14)
+DB(13)
+DB(12)
Mated 2
5V Ground
5V Ground
ACTIVE LED OUT
DELAYED START
SCSI ID (1)
SCSI ID (3)
*1 HVD is not supported
Note: SCA-2 connector is not mechanically compatible with the 68-pin “P” connector as defined in the ANSI SCSI standard. The connector is intended for direct back plane attachment and is not intended to be cable attached to the bus.
Eight-bit devices that connect to the SCA-2 connector should have the following signals inactive (high): -DB(8), -DB(9), DB(10), -DB(11), -DB(12), -DB(13), -DB(14), -DB(15), -DB(P1). All other signals shall be connected as defined.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
23
7.3 SCSI cable
Refer to ANSI SPI-4.
7.4 SCSI bus terminator
Onboard SCSI active termination feature is not supported. The using system is responsible for making sure that all required
signals are terminated at both ends of the bus cable.
Terminator power
Termination power can be provided by drive 5V supply through current limiter and Schottky diode. This function can be
selected by jumper.
The 80-pin SCA-2 models do not support SCSI termination power.
7.5 Hot plug/unplug
The term “hot plug” refers to the action of mechanically engaging a device to the power and/or bus when other devices may be
active on the same bus. A comprehensive classification of the state of the SCSI bus during this event is located in the SCSI-3
Parallel Interface Standard.
While every effort was made to design the drive not to influence the SCSI bus during these events, it is the responsibility of the
system to ensure voltage regulation and conformance to operational and non-operational shock limits. During hot plug events
the non-operational shock levels should not be exceeded. The operational shock levels of adjacent drives should also not be
exceeded. The recommended procedure is to prohibit write operations to adjacent drives during hot plug and unplug actions.
During hot unplug the operational shock limit specifications should not be exceeded. If this cannot be guaranteed, the drive
should be issued a SCSI STOP UNIT command that is allowed to complete before unplugging. The basic requirement is that
while the drive is operational or spinning down the operational shock limits are in effect. When the drive has completely
stopped, the non-operational shock limits are in effect. The recommended procedure is to allow the unplugged drive to rest in
the drive bay for a minimum of 15 seconds and then complete the removal. During hot plug or unplug events the power supply
ripple on adjacent operational drives should not be outside the ±5% regulation tolerance. It is recommended that the system
have current limiter for in-rush current as described in ANSI SPI-4.
Hot plugging/unplugging the 68-pin model drive to the power supply or to a SCSI bus connector is not allowed since provisions are not available to determine which electrical contact is made first. It may cause glitches on the system SCSI bus and/or
electrical over stress that may result in permanent damage of electrical components of the drive. It is the responsibility of the
system to protect the drive from these situations when the 68-pin model is connected to the power supply of the SCSI bus.
7.6 SCSI bus electrical characteristics
Refer to ANSI SPI-4 for bus electrical characteristics.
Note:
If the drive is connected to an HVD bus, the drive I/O will be permanently damaged.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
24
7.7 Auxiliary connector on 68-pin model
In addition to the Option Jumper Block, the 68-pin models have an Auxiliary Connector between the power connector and the
68-pin SCSI connector. The settings at the Option Jumper Block and the Auxiliary Connector work as a logical OR. The drive
conforms to SFF-8009, Rev 2.0.
•
Pin numbers 1, 3, 5, and 7 specify SCSI-ID as 1D0, 1D1, 1D2, 1D3.
•
Pin numbers 2, 4, 6, and 12 are reserved and should be open.
•
Pin #8 is for external LED cathode.
34
1
68
35
Bit 3
Bit 2
NC
Bit 1
+5V
Bit 0
11
9
7
5
3
1
12 10
8
6
4
2
(Reserved)
(Reserved)
Ground
LED cathode
(Reserved)
(Reserved)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
25
SCSI ID
7.8 Option jumper block
As shown in the figure below, the 80 pin SCA-2 card has a single jumper block ( J6). The 68 pin card contains two jumper
blocks (J4 and J6).
J4 and J6 have 14 positions numbered #1 - #14.
As described in Section 7.7, “Auxiliary connector on 68-pin model” on page 33, some of the jumper pins on J4 of the 68-pin
models can also be controlled through the Auxiliary Connector. These controls work as logical OR between the Option Jumper
Block and the Auxiliary Connector.
As described in Section 7.2.2, “SCSI signal connector (80-pin SCA-2 model)” on page 31, some of the jumper pins on J6 of
the 80-pin models can also be controlled through the 80-pin SCA-2 connector. These controls work as a logical OR between
the Option Jumper Block and the SCA-2 connector.
SCA
J6
GND
1
2
GND
3
4
Disable Auto Spin
Auto Spin
Delay
68Pin
+5V
150 ohm
1
2
LED out
J4
+5V
Polyswitch
3
4
Enable
Term
Power
GND
5
6
GND
7
8
Force SE
Delay
mode
Spin 12
sec x ID,
else 6 sec
x ID
GND
9
10
+5V
150 ohm
11
12
GND
13
14
RSVD
LED out
RSVD
J6
GND
5
6
GND
7
8
GND
9
10
GND
11
12
GND
13
14
Force SE
mode
ID 0
ID 1
ID 2
ID 3
GND
1
2
GND
3
4
Disable Auto Spin
Auto Spin
Delay
GND
5
6
GND
7
8
GND
9
10
GND
11
12
GND
13
14
Delay
Spin 12
sec x ID,
else 6 sec
x ID
Disable
Parity
RSVD
Disable
Unit
Attention
RSVD
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
26
7.9 Jumper signal Description on 80 pin Jumper Block
7.9.1 Disable Auto Spin (position 1-2)
If a jumper is not installed, the drive will spin up automatically after the power on reset. If a jumper is installed, the
drive will not spin up unless a START UNIT command is received.
7.9.2 Auto Spin Delay and Delay Spin 12 / 6 (position 3-4)
These pins control when and how the drive spins up with the combination of Position #1-2 on J6. When both Auto Spin up and
Auto Start Delay are enabled, the drive start will be delayed by a period of time multiplied by its own SCSI address. If Auto
Spin up is disabled, these jumpers will be ignored. Placing a jumper on delay start 12 / 6 results in a start up delay of 12 seconds time the SCSI ID.
Note:
In the table below, “on” means a jumper is installed and “off” means that a jumper is not installed.
Table 16: Auto start delay & delay start 6/12 drive behavior
Model
Jumper Settings
68p/ SCA
Disable Auto Spin Dly 12 /6
Auto Spin Delay
Response
Auto
Start ?
Delay Multiplier
OFF
OFF
OFF
YES
0
OFF
OFF
ON
YES
0
OFF
ON
OFF
YES
6
OFF
ON
ON
YES
12
ON
OFF
OFF
NO
-
ON
OFF
ON
NO
-
ON
ON
OFF
NO
-
ON
ON
ON
NO
-
7.9.3 Force Single Ended Mode (position 7-8)
If a jumper is installed, the drive functions as a single-ended mode drive.
7.9.4 Reserved (position 9-10)
No connection should be made.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
27
7.9.5 LED Driver Out (position 11-12)
The LED pins are used to drive an external Light Emitting Diode. Up to 30 mA of sink current capability is provided. The
LED Anode must be tied to the current limited +5V source provided at the Location #11 on J6 jumper block.
The LED Cathode is then connected to pin #12 on J6 jumper block to complete the circuit.
7.9.6 Positions #13-14
No connection should be made.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
28
7.10 Jumper signal Description on 68 pin Jumper Block
7.10.1 LED Driver Out (position 1-2)
The LED pins are used to drive an external Light Emitting Diode. Up to 30 mA of sink current capability is provided. The
LED Anode must be tied to the current limited +5V source provided on pin 1 on J4 jumper block.
The LED Cathode is then connected to the pin 2 on J4 jumper block to complete the circuit.
+5V
68 pin
150 Ohms
Position #1 , 2 on J-4 Jumper Block
(pin 1 of J-4 ) to LED Anode
(pin 2 of J-4 ) to LED Cathode
150 Ohms
7.10.2 Enable Termination Power (positions 3-4)
If a jumper is installed, termination power is supplied to pins 17, 18, 51, and 52 of the 68-pin SCSI interface.
7.10.3 Force Single Ended Mode (position 5-6)
If a jumper is installed, the drive functions as a single-ended mode drive.
7.10.4 Positions #7-8 to #13-14: Device ID
These four lines define the device ID on the SCSI BUS. ID 0 is the least significant bit and ID 3 is the most significant bit.
Device ID is defined in the table below. In the table, "on" means a jumper is installed and "off" means that no jumper isinstalled.
Table 17: SCSI Device ID
ID 3
OFF
OFF
OFF
OFF
OFF
OFF
ID 2
OFF
OFF
OFF
OFF
ON
ON
ID 1
OFF
OFF
ON
ON
OFF
OFF
ID 0
OFF
ON
OFF
ON
OFF
ON
Device ID
0
1
2
3
4
5
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
29
OFF
ON
ON
OFF
OFF
ON
ON
ON
ON
ON
ON
ON
ON
ON
OFF
OFF
OFF
OFF
ON
ON
ON
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON
ON
ON
OFF
ON
OFF
ON
OFF
ON
OFF
ON
6, shipping default of
68 pin
7
8
9
10
11
12
13
14
15
7.11 Jumper Signal Description on 68 pin Jumper Block (J6)
7.11.1 Disable Auto Spin (position 1-2)
If a jumper is not installed, the drive will spin up automatically after the power on reset. If a jumper is installed, the
drive will not spin up unless a START UNIT command is received.
7.11.2 Auto Spin Delay and Delay Spin 12 / 6 (position 3-4 and 5-6)
7.11.3 Disable Parity (position 7-8)
Installing a jumper disables SCSI parity checking.
7.11.4 Disable Unit Attention (position 11-12)
Installing a jumper enables control of UAI (Unit Attention Inhibit) bit in Mode Page 0.
7.11.5 Reserved (positions 9-10 and 13-14)
No connection should be made.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
30
8.0 Environment
8.1 Temperature and humidity
Table 18: Operating and non-operating conditions
Operating conditions
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 temperature gradient
20ºC/hour
Altitude
-300 to 3,048 m
Shipping conditions
Temperature
-40°C to70ºC
Relative humidity
5 to 95%, non-condensing
Maximum wet bulb temperature
35ºC, non-condensing
Maximum temperature gradient
30ºC/hour
Altitude
-300 to 12,000 m
Storage conditions
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 should be maintained at all times. Maximum storage period within shipping package is
one year.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
31
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)
8.2 Storage requirements
8.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.
8.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.
8.3 Corrosion test
The hard disk drive shows no signs of corrosion inside or outside of the hard disk assembly and remains functional after being
exposed to a temperature of 50ºC and relative humidity of 90% for seven days.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
32
8.4 Cooling requirements
Drive component temperatures must remain within the limits specified in the following table. Maximum component temperature ratings must not be exceeded under any operating condition. The drive may require forced air cooling to meet specified
operating temperatures.
Table 19: 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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
33
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
34
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 20: Input voltage
Tolerance
+5 Volts supply
+12 Volts supply
+/- 5%
+/- 5%,
1
Absolute max
spike voltage
5.5 V
15 V
Supply rise time
0-200 ms
0-400 ms
1.
-8% of 12V voltage margin is acceptable during spin-up, but the drive ready time as specified in section 4.5.2 is not guaranteed.
CAUTION: To avoid damage to the drive electronics, power supply voltage spikes must not exceed 5.5V.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
35
9.1 Power supply current, average, and peak
Table 21: Model 147GB
Model 147GB
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
0.70
0.80
0.54
0.29
Current
+12V
1.70
2.30
0.71
0.45
Total Average
Note
Power (W)
--Maximum
Peak
11.22
Avg
--Pk to Pk
Random Peak AC 209
Random W/R(DC) 209
1.50
0.69
2.64
1.13
--16.99
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.69
0.66
0.63
0.60
0.57
1.03
0.96
0.90
0.84
0.77
15.79
14.87
13.96
13.05
12.14
Avg, 2KB, Qd=1
IO/Sec
150
120
90
60
30
Table 22: Model 147GB: 5V Current during spinup
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
36
Table 23: Model 147GB: 12V Current during spinup
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
37
Table 24: Model 73GB
Model 73GB
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
0.70
0.80
0.55
0.29
Current
+12V
1.70
2.30
0.51
0.41
Total Average
Note
Power (W)
--Maximum
Peak
8.83
Avg
--Pk to Pk
Random Peak AC 215
Random W/R(DC) 215
1.51
0.70
2.17
.87
--13.88
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.67
0.65
0.62
0.60
0.57
0.78
0.73
0.67
0.62
0.56
12.85
12.04
11.24
10.44
9.63
Avg, 2KB, Qd=1
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
0.70
0.80
0.55
0.27
Current
+12V
1.70
2.30
0.45
0.37
Total Average
Note
Power (W)
--Maximum
Peak
8.19
Avg
--Pk to Pk
Random Peak AC 220
Random W/R(DC) 220
1.41
0.70
2.15
0.80
--13.15
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.67
0.64
0.62
0.60
0.57
0.65
0.65
0.60
0.55
0.50
11.81
11.08
10.36
9.63
8.90
Avg, 2KB, Qd=1
IO/Sec
150
120
90
60
30
Table 25: Model 36GB
Model 36GB
IO/Sec
150
120
90
60
30
9.2 Ripple voltage
Table 26: Power supply generated ripple at drive power connector
+5 V DC
+12 V DC
Maximum (mV pp)
250
250
MHz
0-10
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
38
not exceed 20 mA.
9.3 Power consumption efficiency index
Table 27: Power consumption efficiency index
Model
Power consumption efficiency index (W/GB)
147GB model 73GB model
0.08
0.12
36GB model
0.23
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
39
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
40
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
"Enviornment" on page 36.
10.2 Data reliability
The probability of an uncorrectable data error is 10 in 1x1016 bits read.
The following ECC On-The-Fly (OTF) correction is implemented:
•
1 symbol = 8 bits
•
3 interleaves
•
18 symbols, 6 symbols per each interleave, for OTF correction This implementation always recovers 18 random burst
errors and a 144 bit continuous burst error.
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 17.11.13, “Mode page 1C
(Informational exceptions control)” on page 152. 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 17.7.11, “Log Sense page 2F” on page 111.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
41
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
42
11.0 Mechanical specifications
11.1 Outline
11.1.0.1 68-pin connector model
11.1.0.2 80-pin connector model
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
43
11.2 Mechanical dimensions
The drive complies with SFF-8301.
Table 28: 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 SCSI Hard Disk Drive Specification
44
11.3 Interface connector
11.3.1 68 and 80 pin connectors
11.3.1.1 Interface connector for 68-pin models
11.3.1.2 Interface connector for 80-pin models
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
45
11.4 Mounting positions and tappings
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
46
11.4.0.1 Mounting positions and tappings
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
47
11.5 Drive mounting
The drive will operate in all axes (six 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.
11.7.0.1 Breather hole location
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
48
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 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 vibration
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 SCSI Hard Disk Drive Specification
49
axes. There must be a minimum of 30 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 SCSI Hard Disk Drive Specification
50
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 29: 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 SCSI Hard Disk Drive Specification
51
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
52
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 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, CSA, TUV, CE, and CTICK logos.
•
A bar code label containing the drive serial number.
•
Jumper setting label.
•
A user designed label, per agreement.
•
Interface definition mark, SCSI LVD/SE multimode.
SCSI
LVD/SE
The labels may be integrated with other labels.
Hitachi Ultrastar15K147 SCSI Hard Disk Drive Specification
53
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
54
15.0 Standards
The following shows the safety standards for different countries.
15.1 UL and CSA 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 CSA certification, is maintained for the product life. The UL and C-UL
recognition mark, or CSA monogram for CSA certification, appears on the drive.
15.2 European standards compliance
The product is certified to EN60950.
15.3 German safety mark
The product is approved by the TUV and will carry the applicable Bauart mark on the label.
15.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.
15.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 SCSI Hard Disk Drive Specification
55
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
56
16.0 Electromagnetic Compatibility
The drive, when installed in a suitable enclosure and exercised with a random accessing routine at a maximum data rate will
comply with the worldwide EMC requirements listed below.
•
•
•
•
•
•
•
•
•
FCC, Title 47, Part 15, Class B (United States)
VCCI Class B (Japan)
EN 55022 Class B
EN 55024
EN 61000-3-2
EN 61000-3-3
CNS 13438 Class B (Taiwan)
AS/NZS 3548 Class B (Australia, New Zealand)
MIC Notice No. 2000-94, RRL Notice No. 2000-71 (Korea)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
57
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
58
17.0 SCSI Command Set
Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory
Table 30: SCSI Commands Supported
Type
Code
Description
M
04h
FORMAT UNIT (04), page 62
M
12h
INQUIRY (12), page 68
O
4Ch
LOG SELECT (4C), page 78
O
4Dh
LOG SENSE (4D), page 81
O
15h
MODE SELECT (15), page 103
O
55h
MODE SELECT (55), page 104
O
1Ah
MODE SENSE (1A), page 105
O
5Ah
MODE SENSE (5A), page 141
O
5Eh
PERSISTENT RESERVE IN (5E), page 143
O
5Fh
PERSISTENT RESERVE OUT (5F), page 147
O
34h
PRE-FETCH (34), page 155
M
08h
READ (6) - (08), page 156
M
28h
READ (10) - (28), page 157
O
3Ch
READ BUFFER (3C), page 158
M
25h
READ CAPACITY (25), page 162
O
37h
READ DEFECT DATA (37), page 164
O
B7h
READ DEFECT DATA (B7), page 168
O
3Eh
READ LONG (3E), page 170
O
07h
REASSIGN BLOCKS (07), page 171
O
1Ch
RECEIVE DIAGNOSTICS RESULTS (1C), page 173
M
17h
RELEASE (17), page 175
O
57h
RELEASE (57), page 176
O
A3h/05h
REPORT DEVICE IDENTIFIER (A3), page 177
O
A0h
REPORT LUNS (A0), page 179
M
03h
REQUEST SENSE (03), page 180
M
16h
RESERVE (16), page 181
O
56h
RESERVE (56), page 182
O
01h
REZERO UNIT (01), page 183
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
59
Type
Code
Description
O
0Bh
SEEK (6) - (0B), page 184
O
2Bh
SEEK (10) - (2B), page 185
M
1Dh
SEND DIAGNOSTIC (1D), page 186
O
A4h/06h
SET DEVICE IDENTIFIER (A4), page 190
O
1Bh
START STOP UNIT (1B), page 191
O
35h
SYNCHRONIZE CACHE (35), page 192
M
00h
TEST UNIT READY (00), page 193
O
2Fh
VERIFY (2F), page 194
O
AF
VERIFY (16) - (AF), page 210
M
0Ah
WRITE (6) - (0A), page 196
M
2Ah
WRITE (10) - (2A), page 197
O
2Eh
WRITE and VERIFY (2E), page 213
O
8E
WRITE and VERIFY (16) - (8E), page 212
O
3Bh
WRITE BUFFER (3B), page 200
O
3Fh
WRITE LONG (3F), page 204
O
41h
WRITE SAME (41), page 205
O
93
WRITE SAME (16) - (93), page 220
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
60
17.1 SCSI Control Byte
The Control Byte is the last byte of every CDB. The format of this byte is shown below.
Table 31: SCSI Control Byte
BIT
7
6
5
VU = 0
4
Reserved = 0
3
2
1
0
NACA
FLAG
LINK
VU
VU stands for Vendor Unique.
NACA
NACA stands for Normal Auto-Contingent Allegiance. This bit determines the rules for handling an ACA condition
that is caused by this command.
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: Linked commands are not supported and Check condition ’Illegal Request Invalid field in CDB’ will be returned if
LINK bit is set.
17.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.
17.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 SCSI Hard Disk Drive Specification
61
17.4 FORMAT UNIT (04)
Table 32: FORMAT UNIT (04)
Byte
BIT
7
6
5
0
3
2
1
0
Command Code = 04h
1
Reserved = 0
2
3
4
FmtData
CmpLst
Defect List Format
VU = 0
(MSB)
Interleave Factor
4
(LSB)
5
VU = 0
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. If no Defect List Header is supplied, the following defaults are assumed: DPRY=0, DCRT=1,
STPF=1, IP=0, DSP=0, Immed=0.
• CmpLst
• - set to one specifies that the Grown Defect List (GList) existing prior to the issuance of the Format Unit command
be discarded. If provided, the DList then becomes the GList. Following these operations, the Drive will be formatted
with the PList and GList.
• - set to zero specifies that the GList existing prior to the issuance of the Format Unit command is retained. If provided, the DList is combined with the GList to become the new GList. Following these operations, the Drive will be
formatted with the PList and GList.
Note: The drive manages two internal defect lists and one external. The Plist is created at time of manufacture. The Glist is
built after manufacture by the Initiators’ use of the REASSIGN BLOCK command and the Automatic Reallocate functions.
The Dlist is an external list. It is supplied by the Initiator in the Data Out phase of the FORMAT UNIT command.
• Defect List Format specifies the format of the defect descriptor transferred to the Target when FmtData bit is set to one.
The Target supports the following three defect descriptor formats for the FORMAT UNIT command:
Format 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
62
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
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 SCSI Hard Disk Drive Specification
63
17.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 33: Format of Defect List Header
BIT
Byte
7
6
5
0
3
2
1
0
DSP
Immed
Ignored
Reserved = 0
1
2
4
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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
64
• IP (Initialization Pattern) bit must be set to zero. The Target initializes all data with zeros.
• 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.
17.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.
17.4.2.1 Block Format - 000b
Format of the Glist sent during the data out phase when Glist Format is Block format (000b) and FmtData is set to one.
Table 34: 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 Dlist is the LBA of each defective sector.
Note: If a Defective LBA entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
65
17.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 35: 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 SCSI Hard Disk Drive Specification
66
17.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 36: 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 SCSI Hard Disk Drive Specification
67
17.5 INQUIRY (12)
Table 37: INQUIRY (12)
Byte
BIT
7
6
0
5
4
3
2
1
0
Command Code = 12h
1
Reserved = 0
CmdDt=0
2
Page Code
3
Reserved = 0
4
Allocation Length
5
VU = 0
Reserved = 0
EVPD
FLAG
LINK
The INQUIRY command requests the parameters of theTarget to be sent to the initiator.
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 Page Code specifies which page of vital product data information the drive shall return.
Table 38: 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 (without a FRU 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 SCSI Hard Disk Drive Specification
68
17.5.1 Inquiry Data
Fields with a value shown inside quotes (e.g. Value =’xyz’) are character fields. A value not in quotes is a numeric value.
Character fields are alphanumeric and represented in either ASCII.
17.5.1.1 Inquiry Data Format - EVPD = 0, Page Code = 0
Table 39: Inquiry Data Format - EVPD = 0, Page Code = 0
BIT
Byte
7
0
1
6
5
4
Qualifier = 0
RMB = 0
0
Version = 3
Obsolete
Obsolete
Norm
HiSup = 0
ACA=0
Response Data Formate = 2
Additional Length = 159 (9Fh)
SCCS=0
ACC=0
ALUA=00b
3PC=0
6
BQue = 0 EncSer = 0 Rsvd=0
7
Rel_A = 0 Obsolete Wb_16 =1 Sync = 1
MultiP=0 MChngr= 0
Link = 0
Reserved = 0
Obsolete
Vendor ID = 'HITACHI' (ASCII)
16-31
Product ID (ASCII)
32-35
Product Revision Level (ASCII)
36-43
Unit Serial Number (ASCII)
44-55
Reserved = 0
Reserved=0
Obsolete Addr16 = 1
Obsolete CmdQue= 1 RSVD = 0
8-15
56
1
Reserved=0
4
5
2
Peripheral Device Type = 0
2
3
3
Clock=11b
57-95
Reserved=0
96-145
Copyright Notice (ASCII)
146-163
Reserved = 0
QAS=1
IUS=1
• Qualifier is set to zero to indicate that the LUN specified in the Identify Message is currently supported. Qualifier is set
to 011b when the LUN specified in the Identify Message is not present 1
• Peripheral Device Type is set to zero to indicate that the device is a Direct-Access. Peripheral Dev. Type is set to 1Fh
when the LUN specified in the Identify Message is not present.
• 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 zero indicates the target does not use the hierarchical addressing model to assign LUNs to logical units.
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 SCSI Hard Disk Drive Specification
69
• 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.
• 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.
• MultiP (MultiPort) bit of 0 indicates that the Target has a single port and does not implement 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 supports 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 supports 16-bit wide data transfers.
• Sync is set to zero to indicate that the Target supports synchronous data transfer.
• Link is set to zero to indicate that the Target does not support linked commands.
• CmdQue is set to one to indicate that the drive supports command queuing.
• Vendor ID is 'HITACHI' padded with ASCII blanks.
• Product ID is specified in table 3 of section 4.3.1.
• Product Revision Level indicates the level of microcode. It indicates RAM microcode level.
• Unit Serial Number contains the drive serial number.
17.5.1.2 Inquiry Data Format - EVPD = 1 - Page Code = 00h
Table 40: Inquiry Data - EVPD = 1 (Page Code = 00h)
BIT
Byte
7
0
6
5
Qualifier = 0
4
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 00h
2
Reserved = 0
3
Page Length = 06h
4
Supported Page Code - 00h
5
Supported Page Code - 03h
6
Supported Page Code - 80h
7
Supported Page Code - 83h
8
Supported Page Code - D1h
9
Supported Page Code - D2h
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
70
• 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 SCSI Hard Disk Drive Specification
71
17.5.1.3 Inquiry Data Format - EVPD = 1, Page Code - 03h
Table 41: Inquiry Data - EVPD = 1 (Page Code = 03h)
BIT
Byte
7
0
6
5
Qualifier = 0
4
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-7
Reserved = 0
8-23
Reserved = 0
24-35
ASCII uCode Identifier
36-39
ASCII Servo P/N
40-41
Major Version
42-43
Minor Version
44-47
User Count
48-51
Build Number
52-83
Build Date String
84-91
Product ID
92-99
Interface ID
100-107
Code Type
108-119
User Name
120-135
Machine Name
136-167
Directory Name
168-171
Operating State
172-175
Functional Mode
176-179
Degraded Reason
180-183
Broken Reason
184-187
Code Mode
• 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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
72
length of the CDB is too small to transfer all the data, the Page Length field is not adjusted to reflect the truncation.
• ASCII uCode Identifier contains the drive’s microcode identifier. The field is alphanumeric (ASCII), left aligned, and
the unused bytes are ASCII spaces (20h).
• ASCII Servo P/N contains the part number of the Servo microcode installed on the drive. This field is hex numeric
ASCII (i.e., the characters will be in the set 0...9, A...F).
• Major Version and Minor Version are version numbers of the code loaded on the drive.
• User Count is the number of times the code has been built since the master build.
• Build Number is the master build version number.
• Build Date String is the date the code on the drive was built, in an extended string format.
• Product ID is the name of the product this code is for.
• Interface ID is the name of the interface (e.g. SCSI, FCAL) this code is intended.
• 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 SCSI Hard Disk Drive Specification
73
17.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h
Table 42: Inquiry Data - EVPD = 1 (Page Code = 80h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 80h
2
Reserved = 0
3
Page Length = 16 (10h)
4-19
Serial Number (ASCII)
• Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
• Peripheral Device Type is set to zero to indicate that the device is Direct Access.
• Page 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 SCSI Hard Disk Drive Specification
74
17.5.1.5 Inquiry Data Format - EVPD = 1, Page Code - 83h
Table 43: 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 = 12 (0Ch)
Reserved = 0
5
Reserved = 0
Association = 0
Reserved = 0
7
Identifier Length = 8
(MSB)
0
Code Set = 1
6
8-15
1
Peripheral Device Type = 0
1
4
2
Identifier Type = 3
World Wide ID
(LSB)
• 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 12, and this field specifies the length of the following page data.
• Code Set field specifies the code set used for the identifier field. The Target supports binary.
• Association field specifies the entity with which the identifier field is associated. The Target supports value of 0h, the
Identifier field is associated with the addressed physical or logical device.
• Identifier Type field specifies the format and assignment authority for the identifier. The Target supports the value of
03h.
• World Wide ID is 64-bit unique identification for each drive. The format is: 5000CCAh xxxh 11b n. where:
xxx is 12-bit Block assignment defined for each model and manufacturing site.
11b indicates parallel SCSI.
n is 22-bit drive unique serial number.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
75
17.5.1.6 Inquiry Data Format - EVPD = 1, Page Code - D1h
Table 44: Inquiry Data - EVPD = 1 (Page Code = D1h)
BIT
Byte
7
0
6
5
Qualifier = 0
4
3
2
1
0
Peripheral Device Type = 0
1
Page Code = D1h
2
Reserved = 0
3
Page Length = 80 (50h)
4-19
ASCII Media Disk Definition
20-35
ASCII Motor Serial Number
36-51
ASCII Flex Assembly Serial Number
52-67
ASCII Actuator Serial Number
68-83
ASCII Device Enclosure Serial Number
• 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 SCSI Hard Disk Drive Specification
76
17.5.1.7 Inquiry Data Format - EVPD = 1, Page Code - D2h
Table 45: Inquiry Data - EVPD = 1 (Page Code = D2h)
BIT
Byte
7
0
6
5
Qualifier = 0
4
3
2
1
0
Peripheral Device Type = 0
1
Page Code = D2h
2
Reserved = 0
3
Page Length = 32 (20h)
4-19
ASCII Card Serial Number
20-35
ASCII Card Assembly Part 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 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 SCSI Hard Disk Drive Specification
77
17.6 LOG SELECT (4C)
Table 46: Log Select (4C)
Bit
Byte
7
6
5
0
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).
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
78
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. 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, 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 or parameter codes out of order. The sense key shall be set to
Illegal Request and additional sense code set to Invalid Field in Parameter List.
If one or more fields of the CDB are not set correctly the command will be terminated with a Check Condition status. The
sense key shall be set to Illegal Request and additional sense code of Invalid Field in CDB.
To indicate that parameters have changed, the Target generates a unit attention condition for all Initiators except the one that
issued the LOG SELECT command.
The following list contains all individual page parameters (counters) that are set to their default value of 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 SCSI Hard Disk Drive Specification
79
• 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
- Device Cache Read Misses
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
80
17.7 LOG SENSE (4D)
Table 47: Log Sense (4D)
Bit
Byte
7
6
5
0
3
2
1
0
PPC=0
SP
Command Code = 4Dh
1
Reserved = 0
2
PC
3
Reserved = 0
Page Code
Reserved = 0
4
5
4
(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 is only available for Page Code = 0Fh.
If the parameter pointer field greater than 3Fh for Page Code = 0Fh, or if the field is not zero for Page Code other
than 0Fh, 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 SCSI Hard Disk Drive Specification
81
17.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 SCSI Hard Disk Drive Specification
82
17.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 48: Log Sense Page 0
Bit
Byte
7
0
6
Reserved
5
4
3
2
1
Page code = 0
1
Reserved
2-3
Page Length = 000Ch (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 2Fh
14
Eleventh supported Page Code =30h
15
Twelfth supported Page Code = 37h
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
83
0
17.7.3 Log Sense Page 2
This page contains counters for write errors.
Table 49: 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 of 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
LBIN =
0
LBIN =
0
LBIN =
0
LBIN =
0
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
84
=0
LP
=0
LP
=0
LP
=0
LP
=0
Table 50: 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 of hard errors
LBIN
=0
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
85
=0
LP
=0
17.7.4 Log Sense Page 3
This page contains counters for read errors.
Table 51: 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 = 00h
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Errors recovered without delay
16-17
Parameter Code = 01h
18
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
19
Parameter Length = 08h
20-27
Count of ECC errors
28-29
Parameter Code = 02h
30
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
31
Parameter Length = 08h
32-39
Count of ID type errors
40-41
Parameter Code = 03h
42
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
43
Parameter Length = 08h
44-51
Total errors recovered
52-53
Parameter Code = 04h
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 = 05h
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
86
Table 52: 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 = 06h
78
DU = 0
DS = 0
TSD = 0 ETC = 0
2
TMC = 0
79
Parameter Length = 08h
80-87
Count of 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 SCSI Hard Disk Drive Specification
87
17.7.5 Log Sense Page 5
This page contains counters for verify errors.
Table 53: 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 of 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 of 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
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
TSD = 0
ETC = 0
TMC = 0
55.
Parameter Length = 08h
56-63
Times recovery invoked
64-65
Parameter Code = 0005h
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
88
Table 54: Log Sense Page 5 (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 Verified
76-77
Parameter Code = 0006h
78
DU = 0
DS = 0
TSD = 0
2
TMC = 0
79
Parameter Length = 08h
80-87
Count of hard errors
1
0
LBIN =
0
LP= 0
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 SCSI Hard Disk Drive Specification
89
17.7.6 Log Sense Page 6
This page contains counters for non-medium errors. This includes seek errors and other hardware type failures.
Table 55: 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 SCSI Hard Disk Drive Specification
90
=0
17.7.7 Log Sense Page D
This page contains temperature information.
Table 56: 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 SCSI Hard Disk Drive Specification
91
17.7.8 Log Sense Page E
This page contains the start-stop cycle information.
Table 57: 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 SCSI Hard Disk Drive Specification
92
17.7.9 Log Sense Page F
This page contains the Application Client Log.
Table 58: 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 59: Log Sense Page F, Application Client Log
Bit
Byte
7
6
0-1
2
5
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 SCSI Hard Disk Drive Specification
93
17.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 60: 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 61: 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
self-test.
• Self-Test Results Value is described in the table below.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
94
Table 62: 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 of 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
95
Table 63: Log Sense Page 10, Extended Segment Number
Extended
Segment
Number
Short Self-Test
Extended Self-Test
1h
Drive Ready Test
2h
Drive Diagnostics
3h
SMART
4h
Low Level Format check
5h
Physical Head Check
6h
Random Verify
7h
8h
- 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.
• 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 17.34 “SEND DIAGNOSTIC (1D)” on page 186, for detailed listing of operations carried out by SEND DIAGNOSTIC command and Power on Diagnostics.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
96
17.7.11 Log Sense Page 2F
This page contains SMART Status and Temperature Reading.
Table 64: 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 SCSI Hard Disk Drive Specification
97
17.7.12 Log Sense Page 30
This page contains Performance Counters.
Table 65: 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
98
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)
• 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
99
• SEEKS >= 2/3 DISK
The number of seeks equal to or greater than 2/3 of the disk.
• SEEKS >= 1/3 AND < 2/3 DISK
The number of seeks equal to or greater than 1/3 and less than 2/3 of the disk.
• SEEKS >= 1/6 AND < 1/3 DISK
The number of seeks equal to or greater than 1/6 and less than 1/3 of the disk.
• SEEKS >= 1/12 AND < 1/6 DISK
The number of seeks equal to or greater than 1/12 and less than 1/6 of the disk.
• SEEKS > 0 AND < 1/12 DISK
The number of seeks less than 1/12 of the disk.
• OVERRUN COUNTER
The number of times that data was available to be transferred from the media but the device buffer still contained data
that had not been retrieved by the Initiator. Consequently, the disk had to take additional revolutions until the buffer
was available to accept data.
• UNDER RUN COUNTER
The number of times that the drive was ready to transfer data to its disk (on a write), but its buffer was empty (i.e.,
had not been filled by the Initiator), thus the disk was forced to take extra revolutions.
• 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 teh 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 SCSI Hard Disk Drive Specification
100
17.7.13 Log Sense Page 37
This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.
Table 66: 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 = 0000h
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
-
(LSB)
19
20
(MSB)
Total Bytes Written
-
(LSB)
27
28
29 - 30
Max Drive Temp (degrees Celsius)
(MSB)
GList Size
(LSB)
31
32
Number of PFA Occurrences
MED
PFA
HDW
PFA
Reserved = 0
33 - 40
Total Read Commands
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.
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
101
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.
The Total Read Commands counter is incremented for each Read (6) and Read (10) command received.
The 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 SCSI Hard Disk Drive Specification
102
17.8 MODE SELECT (15)
Table 67: Mode Select (15)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 15h
1
Reserved = 0
2
PF=1
Reserved = 0
SP
Reserved = 0
3
4
Parameter List Length
5
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 SCSI Hard Disk Drive Specification
103
17.9 MODE SELECT (55)
Table 68: Mode Select (55)
Bit
Byte
7
6
5
0
Reserved = 0
2-6
9
3
2
1
0
Command Code = 55h
1
7-8
4
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 SCSI Hard Disk Drive Specification
104
17.10 MODE SENSE (1A)
Table 69: Mode Sense (1A)
Bit
Byte
7
6
0
5
4
3
2
1
0
Command Code = 1Ah
1
Reserved
2
PCF
RSVD
DBD
Page Code
3
Subpage Code
4
Allocation Length
5
VU = 0
Reserved = 0
Reserved = 0
FLAG
LINK
The MODE SENSE (1A) command provides a means for the drive to report various device parameters to the Initiator. It is the
complement to the MODE SELECT command.
If the DBD (Disable Block Descriptor) bit is zero, the Target will return 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
105
10
Report default value. The drive returns the default values for the page code specified. The parameters not supported
by the drive are set to zero.
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 70: 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. Subpages are supported for the Port Control Mode Page only. If the
subpage is not supported or is not zero, the command is terminated with a Check Condition status and available sense of Illegal
Request/Invalid Field in CDB.
For other Mode Pages, this Subpage Code field must be zero. If this Subpage Code field is not zero for other Mode Pages, the
command is terminated with a Check Condition status and available sense of Illegal Request/Invalid Field in CDB.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
106
17.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.
17.10.1.1 Header
The 6-byte command descriptor block header is defined below.
Table 71: 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 72: 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)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
107
(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 SCSI Hard Disk Drive Specification
108
17.10.1.2 Block Descriptor
Table 73: 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 (2
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 SCSI Hard Disk Drive Specification
109
17.10.1.3 Page Descriptor
Table 74: Mode Parameter Page Format
Byte 0
PS
SPF
Page Code
Byte 1
Page Length
Byte 2-n
Mode Parameters
Each mode page contains a page code, a page length, and a set of mode parameters.
When using the MODE SENSE command, a Parameter Savable (PS) bit of one indicates that the mode page can be saved by
the drive in the reserved area of the drive. A PS bit of zero indicates that the supported parameters cannot be saved. 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 drive supports the following mode page
codes:
Table 75: Supported Page Codes
Page
Description
PS
00
Vendor Unique Parameters
1
01
Read-Write Error Recovery Parameters
1
02
Disconnect/Reconnect Control Parameters
1
03
Format Device Parameters
0
04
Rigid Disk Geometry Parameters
0
07
Verify Error Recovery Parameters
1
08
Caching Parameters
1
0A
Control Mode Page
1
0C
Notch Parameters
1
19
Port Control Page
1
1A
Power Control Parameters
1
1C
Informational Exceptions Control
1
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 SCSI Hard Disk Drive Specification
110
17.10.2 Mode Page 00 (Vendor Unique Parameters)
Table 76: Vendor Unique Parameters - Page00
Default
Bit
Byte
0
7
6
PS
0
5
4
1
0
80h
Page Length = 0Eh
2
Ignored
ASDPE
UAI
VGMDE CMDAC
4
0Eh
MRG
Ignored
Ignored
RRNDE
10h
Ignored
Ignored
5
6
2
Page Code = 00h
1
3
3
Ignored
IGRA
FDD
AVERP
7
DPSDP
Ignored
00h
Ignored
CAEN
Ignored
OCT (high nibble)
Overall Command Timer (low byte)
8
20h
Ignored
02h
00h
00h
LED Mode
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
• UAI (Unit Attention Inhibit) bit is not used during normal operation when the UAI jumper is removed from the drive. It
may however be changed by the user with no effects. If the UAI jumper is added to the drive, then this bit controls the
generation of unit attention conditions.
• MRG (Merge Glist into Plist) bit is set to 1 for merging the Glist entries into the Plist during FORMAT UNIT command.
• ASDPE (Additional Save Data Pointer Enable) bit is used to control the sending of additional save data pointers messages. When set it will cause a save data pointers message to be sent on every disconnection. This bit is only used by
the Target after the Default Mode parameter values are overridden with the Saved values that are read from the
Reserved Area of the media as a part of the motor startup sequence. Before the Saved values are read from the
Reserved Area of the media, the Save Data Pointer message is always sent to the Initiator prior to disconnection.
When not set, a save data pointers message is sent only if the current connection contained a data phase and a further
data phase will be required to complete the command.
• VGMDE (Veggie Mode) bit indicates the drive, during it’s idle state, will execute random seeks at a predefined rate and
range of cylinders using a predefined head.
• CMDAC (Command Active) bit in conjunction with LED Mode bits determines if an LED on the drive is activated
while commands are active. If CMDAC bit is one and LED Mode bits are zero, an LED driver is active when a command is queued or executed.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
111
• 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.
• DPSDP The Data Phase Save Data Pointer bit controls whether the Drive sends a Save Data Pointer message at the end
of the data phase. A DPSDP bit of 0 indicates that the Drive sends a Save Data Pointer message prior to disconnection only if the following conditions are true:
- A data phase has occurred since the connection for the current command was established.
- Another data phase is required to successfully complete the command.
A DPSDP bit of 1 indicates that the Drive will send a Save Data Pointer message prior to every disconnection once a
data phase has occurred for the current command. If the ASDPE bit is set to 1, the Save Data Pointer message is sent
prior to every disconnect regardless of the value of the DPSDP bit.
• 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.
• AVERP (AV ERP Mode) bit is set to one in order to specify maximum retry counts during Read DRP. When AVERPbit
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
disabled the feature.
• LED Mode is designed to control the operation of a drive LED driver.
- LED Mode = 0000b
The CMDAC bit controls the LED.
CMDAC = 1 (Command Active)
CMDAC = 0 (Motor Active)
- LED Mode = 0001b (Motor Active)
When the motor is spinning, the LED is high.
- LED Mode = 0010b (Command Active).
When there is a command active or in the queue, the LED is high.
• 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
112
• 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 SCSI Hard Disk Drive Specification
113
17.10.3 Mode Page 01 (Read/Write Error Recovery Parameters)
Table 77: 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
Correction Span
00h
5
Head Offset Count (Ignored)
00h
6
Data Strobe Offset Count (Ignored)
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, an 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, an 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, a 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, a 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
114
• EER, an Enable Early Recovery bit, must be set to zero, indicating that the drive shall use an error recovery procedure
that minimizes the risk of misdetection or miscorrection during the data transfer. Data shall not be fabricated.
• PER, a Post Error bit, is set to one to indicate that the drive reports recovered errors.
• DTE, a 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, a 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.
• Correction Span field specifies the size in bits of the largest data error burst for which data error correction may be
attempted. Any value can be placed in this field, including zero. The drive will always use its default correction capabilities.
• Head Offset Count is not supported by the drive.
Note: Head Offset is implemented in the read error recovery routine. The user cannot modify the offset value.
• Data Strobe Offset Count is not supported by the drive and it is ignored.
• Write Retry Count Write Retry Count sets a limit on the amount of DRP passes in which the Target attempts to recover
write errors. A value of zero disables all data recovery procedures.
• Recovery Time Limit indicates the period in 1 millisecond increments for the maximum recovery time of a single LBA.
The value must be from 40 ms to 65535 ms (65.5 seconds). The granularity of the timer is 50 ms. If an LBA is not
able to be recovered within the limit, a Check Condition will be returned. The Recovery Time Limit will not be
applied when WCE=1. A value of zero disables the timer.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
115
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 SCSI Hard Disk Drive Specification
116
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 SCSI Hard Disk Drive Specification
117
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 SCSI Hard Disk Drive Specification
118
17.10.4 Mode Page 02 (Disconnect/Reconnect Parameters)
Table 78: Mode Page 02 (Disconnect/Reconnect Parameters)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Default
Page Code = 02h
82h
1
Page Length = 0Eh
0Eh
2
Read Buffer Full Ratio
00h
3
Write Buffer Empty Ratio
00h
4-5
6-7
8-9
10-11
12
(MSB)
Bus Inactivity Limit = 0
00h
(LSB)
(MSB)
Disconnect Time Limit = 0
00h
(LSB)
(MSB)
Connect Time Limit = 0
00h
(LSB)
(MSB)
Maximum Burst Size
00h
(LSB)
EMDP=0
Fair Arbitration
DIMM
DTDC
00h
13-15
Reserved = 0
The disconnect/reconnect page provides the Initiator with the means to tune the performance of the SCSI bus.
An Initiator may use the IDENTIFY message to grant the drive the general privilege of disconnecting. (Disconnect requests
may still be selectively rejected by the Initiator by issuing a MESSAGE REJECT.)
The drive uses the disconnect/reconnect parameters to control recondition 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 reconnect to the SCSI bus. If the ratio is set to 0h, the target will calculate and use an optimal ratio based on the negotiated transfer rate.
• 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 reconnect to the SCSI bus. If the ratio is set to 0h, the target will
calculate and use an optimal ratio based on the negotiated transfer rate.
• Fair Arbitration set to 000b indicates that the drive will not use arbitration fairness during normal arbitration. Fair Arbitration set to nonzero value indicates that the drive will use arbitration fairness during normal arbitration. Regardless
of the value of Fair Arbitration, the drive will use arbitration fairness during QAS.
• DIMM (Disconnect Immediate) set to one indicates that the drive is required to disconnect after receiving a command
and prior to starting a data phase. A DIMM bit of zero indicates that the drive may transfer data for a command
immediately after receiving it, without disconnecting. Whether or not the drive does so depends upon the workload
and the settings of the other parameters in this mode page. Note: Priority commands do not disconnect from the SCSI
bus.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
119
• DTDC: (Data Transfer Disconnect Control) defines further restrictions for when a disconnect is permitted.
• A value of 000b indicates that DTDC is not used by the drive and disconnects are controlled by the other fields in this
page.
• A value of 001b indicates that the drive shall not attempt to disconnect when the data transfer of a command has
started until all requested data has been transferred.
• A value of 011b indicates that the drive shall not attempt to disconnect once the data transfer of a command has
started, until the command is complete.
• All other values are reserved.
•When DTDC is non-zero, the WCE bit in Mode Page 8 is ignored.
NOTE: If DTDC is nonzero and the maximum burst size is nonzero, a CHECK CONDITION status will be returned. The
sense key shall be set to ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN PARAMETER LIST.
• Maximum Burst Size is the maximum amount of data that the Target transfers during a data phase before disconnecting
if the Initiator has granted the disconnect privilege. This value is expressed in increments of single block size (for
example, a value of 0001h means 512 bytes, 0002h means 1024 bytes when the block size is 512 bytes). Disconnections attempted by the Target are on block boundaries only. For the case when (Maximum Burst Size x Block Size) is
less than the Block Length, the Target will transfer 1 block of data before attempting to disconnect. Value of 0000h
indicates there is no limit on the amount of data transferred per connection. Regardless of the value in Maximum
Burst Size the Target disconnects prior to completion of the data phase if the internal data buffer segment becomes
empty during a READ command or full during a WRITE command.
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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
120
17.10.5 Mode Page 03 (Format Device Parameters)
Table 79: 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 SCSI Hard Disk Drive Specification
121
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.
A value of 0 in the following parameters indicates that they are Target specific.
- Alternate Sectors per Zone
- Alternate Tracks per Zone
- Alternate Tracks per Logical Unit
• 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 SCSI Hard Disk Drive Specification
122
17.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters)
Table 80: 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
(MSB)
2-4
Default
xxh
Number of Cylinders
xxh
(LSB)
5
Number of heads
xxh
00h
(MSB)
6-8
Starting Cylinder -
00h
Write Precompensation = 0
(LSB)
00h
(MSB)
9-11
Starting Cylinder -
00h
Reduced Write Current = 0
12-13
(MSB)
LSB)
00h
Drive Step Rate = 0 (Not used)
(LSB)
(MSB)
14-16
00h
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 SCSI Hard Disk Drive Specification
123
98h
00h
17.10.7 Mode Page 07 (Verify Error Recovery Parameters)
Table 81: Mode Page 07 (Verify Error Recovery Parameters)
Bit
Byte
7
PS
0
1
2
3
4
5
6
7
8
9
(MSB)
10-11
6
0
5
4
3
2
Page Code = 07h
Page Length = 0Ah
Reserved = 0
EER=0
PER
Verify Retry Count
Correction Span = 00h
Reserved = 0
Reserved = 0
Reserved = 0
Reserved = 0
Reserved = 0
Verify Recovery Time Limit
1
0
DTE=0
DCR
Default
87h
0Ah
00h
01h
00h
00h
00h
00h
00h
00h
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 Correction Span field specifies the size in bits of the largest data error burst for which data error correction may
be attempted. The field can be set to any value but the drive will not use off-line correction during verify operations.
• Verify Recovery Time Limit indicates the period in 1 millisecond increments for the maximum recovery time of a single LBA during the verify operation. The value must be from 40 ms to 65535 ms (65.5 seconds). The granularity of
the timer is 50 ms. If an LBA is not able to be recovered within the limit, a Check Condition will be returned. A
value of zero disables the timer.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
124
17.10.8 Mode Page 08 (Caching Parameters)
Table 82: 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 cachHitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
125
ing segmentation.
• WCE (Write Cache Enable) bit when set at zero indicates that the drive must issue Good status for WRITE (6) or
WRITE EXTEND (10) command only after successfully writing the data to the media. When the WCE bit is set to
one, the drive may issue Good status for a WRITE (6) or WRITE EXTEND (10) command after successfully receiving the data but before writing it to the media. When WCE = 1, the drive operates as if AWRE = 1.
WCE is ingored when the DTDC field in Mode Page 2 is non-zero.
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
126
bytes.
• DRA (Disable Read Ahead) bit when set to one requests that the Target not read into the buffer any logical block beyond
the addressed logical block(s). When it is set at zero, the Target may continue to read logical blocks into the buffer
beyond the addressed logical block(s).
• Number of Cache Segments field is used to select the number of data buffer cache segments. This parameter is valid
only when the SIZE bit is set at zero. It is ignored when SIZE is set at one.
• Cache Segment Size field indicates the requested segment size in Bytes or Blocks, depending upon the value of the
LBCSS bit. The Cache Segment Size field is valid only when the SIZE bit is one. It is ignored when SIZE is set at
zero.
• Non Cache Segment Size is not supported and is ignored.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
127
17.10.9 Mode Page 0A (Control Mode Page Parameters)
Table 83: Page 0A (Control Mode Page Parameters)
Default
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 0Ah
1
8Ah
Page Length = 0Ah
2
TST = 0
Rsvd = 0
3
Queue Algorithm Modifier
Rsvd=0
4
TAS = 0 RAC = 0 UA_INTLCK_CTRL
SWP
0Ah
D_SENSE
GLTSD
QErr
RLEC
00h
DQue
00h
Obsolete
00h
5
Reserved = 0
00h
6-7
Obsolete = 0
00h
8-9
10-11
(MSB)
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 SCSI Hard Disk Drive Specification
128
• 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. Any queue commands for that I_T_L
nexus shall be aborted. Any subsequent queue tag message received shall be rejected with a MESSAGE REJECT
message and I/O process shall be executed as an untagged command.
• 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 SCSI Hard Disk Drive Specification
129
17.10.10 Mode Page 0C (Notch Parameters)
Table 84: Page 0C (Notch Parameters)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 0Ch
1
8Ch
Page Length = 16h
2
ND=1
LPN=0
16h
Reserved = 0
3
80h
Reserved = 0
(MSB)
4-5
00h
00h
Maximum Number of Notches
(LSB)
(MSB)
6-7
Default
11h
00h
Active Notch
(LSB)
00h
XXh
(MSB)
8-11
Starting Boundary
XXh
(LSB)
(MSB)
XXh
XXh
12-15
Ending Boundary
(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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
130
•Mode Page 3
- Alternate Sector per Zone
- Alternate Track per Zone
- Alternate Track per Logical Unit
- Sector per Track
- Track Skew Factor
- Cylinder Skew Factor
• Starting Boundary contains the first physical location of the active notch. The first three bytes are the cylinder number
and the last byte is the head. The value sent in this field is ignored.
• Ending Boundary contains the last physical location of the active notch. The first three bytes are the cylinder number
and the last byte is the head. The value sent in this field is ignored.
• Pages Notched is a bit map of the mode page codes that indicates which pages contain parameters that may be different
for different notches. The most significant bit of this field corresponds to page code 3Fh and the least significant bit
corresponds to page code 00h. If a bit is one, then the corresponding mode page contains parameters that may be different for different notches. If a bit is zero, then the corresponding mode page contains parameters that are constant
for all notches.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
131
17.10.11 Mode page 19 (Port Control Parameters)
17.10.11.1 Short Format of Port Control Page
Table 85: Short (Port Control Parameters) Short Format
Bit
Byte
0
7
6
PS
Long=0
5
3
2
1
0
Page Code = 19h
1
Page Length = 06h
2
RSVD
3
RSVD
4
4
99h
06h
Protocol Indentifier = 1
01h
00h
(MSB)
|
Default
00h
|
00h
Synchronous transfer timeout
5
(LSB)
6
RSVD
00h
7
RSVD
00h
•
Protocol Identifier has a value of 1h to indicate SPI SCSI devices.
•
Synchronous Transfer Timeout indicates the maximum amount that the drive waits before generating an error by
doing an unexpected bus free (see 10.3). The unit of time is 1 msec. The drive only goes to a BUS FREE phase if one
of the following events causes the timer, once started, to not reset or reload before expiring.
•
If there is a REQ transition when there are no outstanding REQs waiting for an ACK then load and start the timer.
•
If there is a REQ transition when there are any outstanding REQs waiting for an ACK then there is no effect on the
timer.
•
If there is an ACK transition when there are outstanding REQs waiting for an ACK the load and start the timer.
•
If after an ACK transition there are no outstanding REQs waiting for an ACK then stop the timer.
•
A value of 0000h in Synchronous Transfer Timeout indicates that the function is disabled. A value of FFFFh indicates an unlimited period.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
132
17.10.11.2 Long Format of Port Control Page
Table 86: Page 19 (Port Control Parameters) Long Format
Bit
Byte
0
7
6
PS
Long=1
1
2
|
3
5
4
3
2
1
0
Page Code = 19h
Default
39h
Subpage Code
00h
|
00h
(MSB)
Page Length (n-3)
(LSB)
4
RSVD
5
RSVD
00h
Protocol Identifier = 1h
01h
6
Protocol Specific Mode Parameters
n
The drive maintain an independent set of port control mode page parameters for each SCSI initiator port.
•
Subpage Code indicates which subpage is being accessed. The drive support the following subpage codes. If the
Subpage Code is not supported or is not zero, the drive returns a CHECK CONDITION status, the sense key is set to
ILLEGAL REQUEST and the additional sense code set to ILLEGAL FIELD IN PARAMETER LIST..
- 01h: Margin Control Subpage
- 02h: Saved Training Configuration Values Subpage
- 03h: Negotiated Settings Subpage
- 04h: Report transfer Capabilities 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 1h to indicate SPI SCSI devices.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
133
17.10.11.3 Margin Control Subpage
Table 87: Margin Control Subpage
Bit
Byte
7
6
5
0
1
2
3
4
3
2
1
0
RSVD
Driver Strength
RSVD
Driver Asymmetry
Driver Slew Rate
Driver Precomenstation
RSVD
4
|
RSVD
6
7
Vendor Specific
8
|
RSVD
15
The margin control subpage contains parameters that set and report margin control values for usage between the initiator and
the drive on subsequent synchronous and paced transfers. MODE SENSE command returns the current settings for the initiator.
• Driver Strength indicates the relative amount of driver source current used by the driver. The Driver Strength field
affects both the strong and weak drivers. A larger value indicates more driver source current.
•
Driver Precompensation indicates the relative difference between the weak driver and the strong driver amplitudes
when precompensation is enabled. A larger value indicates a larger difference between the weak and strong amplitudes.
•
Driver Asymmetry indicates the relative difference between the amplitudes of asserted and negated signals launched
from the driver. A larger value indicates a relatively stronger asserted signal compared to the negated signal.
•
Driver Slew Rate indicates the relative difference between the assertion and negation magnitudes divided by the rise
or fall time. A larger value indicates a faster slew rate.
•
Vendor Specific is reserved, and should be zero.
The default value of each margin control field should be 0000b.
The margin control fields indicate absolute conditions centered around their default values. The maximum supported setting
for each field is 0111b and the minimum supported setting for each field is 1000b.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
134
17.10.11.4 Saved Training Configuration Values Subpage
Table 88: Saved Training Configuration Subpage
Bit
Byte
7
6
5
0-3
RSVD
4-7
DB (0) Value
64-67
DB (15) Value
68-71
P_CRCA Value
72-75
P1 Value
76-79
BSY Value
80-83
SEL Value
84-87
RST Value
88-91
REQ Value
92-95
ACK Value
96-99
ATN Value
100-103
C / D Value
104-107
I / O Value
108-111
MSG Value
112-227
RSVD
4
3
2
1
0
The saved training configuration values subpage is used to report the drive's saved training
configuration values. These vendor specific values are maintained by the drive when the retain training information option is
enabled.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
135
17.10.11.5 Negotiated Setting Subpage
Table 89: Negotiated Settings Subpage
Bit
Byte
7
0
4
3
2
1
0
1
2
RSVD
2
REQ / ACK Offset
3
5
5
Transfer Period Factor
1
4
6
Transfer Width Exponent
RSVD
Protocol Options Bits
RSVD
Transceiver Mode
6
RSVD
7
RSVD
1: Sent PCOMP_EN
2: Received PCOMP_EN
The negotiated settings subpage is used to report the negotiated settings of the drive for the current I_T nexus.
•
Transfer Period Factor indicates the negotiated Transfer Period Factor.
•
REQ/ACK Offset indicates the negotiated REQ/ACK Offset.
•
Transfer Width Exponent indicates the negotiated Transfer Width Exponent.
•
Protocol Options Bits contain the negotiated protocol options except PCOMP_EN.
•
Received PCOMP_EN contains the value of PCOMP_EN received by the drive.
•
Send PCOMP_EN contains the value of PCOMP_EN sent by the drive.
•
Transceiver Mode specifies the current bus mode of the drive as defined below.
- 00b: Not used
- 01b: Single Ended
- 10b: Low Voltage Differential
- 11b: High Voltage Differential
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
136
17.10.11.6 Report Transfer Capabilities Subpage
Table 90: Report Transfer Capabilities Subpage
Bit
Byte
7
0
6
5
4
3
2
1
0
Minimum Transfer Period Factor
RSVD
1
2
Maximum REQ / ACK Offset
3
Maximum Transfer Width Exponent
4
Protocol Options Bits
5-7
RSVD
6
RSVD
7
RSVD
The report transfer capabilities subpage is used to report the transfer capabilities of the drive. The values in this subpage are
not changeable via a MODE SELECT command.
•
Minimum Transfer Period Factor is set to the smallest value of the Transfer Period Factor supported by the drive
which is 08h.
•
Maximum REQ/ACK Offset is set to the largest value of the REQ/ACK Offset supported by the drive which is 127.
•
Maximum Transfer Width Exponent is set to the largest value of the Transfer Width Exponent supported by the
drive which is 01h.
•
Protocol Options Bits Supported indicates the protocol options supported by the drive which is FFh.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
137
17.10.12 Mode Page 1A (Power Control)
Table 91: 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
00h
00h
(MSB)
Idle Condition Timer = 0
4-7
(LSB)
(MSB)
8-11
00h
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 SCSI Hard Disk Drive Specification
138
17.10.13 Mode Page 1C (Informational Exceptions Control)
Table 92: 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
RSVD
LOGERR
Method of Reporting
10h
00h
00h
(MSB)
4-7
00h
Interval Timer
(LSB)
00h
00h
(MSB)
8-11
00h
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 Warnings will not be reported. An EWASC bit of
one allows Temperature Warnings to be reported if the temperature inside the disk enclosure exceeds the threshold
set in Mode Page 00h. The Method of Reporting field controls the reporting method. EWASC is independent of
DEXCPT.
• DEXCPT (Disable Exception Control) bit of zero indicates information exception operations are enabled. The reporting
of information exception conditions when the DEXCPT bit is set to zero is determined from the Method of Reporting
field. A DEXCPT bit of one indicates the Target disabled all information exception operations.
• TEST bit of one instructs the drive to generate false drive notifications at the next interval time, (as determined by the
INTERVAL TIMER field), if the DEXCPT is zero. The Method of Reporting and Report Count would apply. The
false drive failure is reported as sense qualifier 5DFFh. The TEST bit of zero instructs the drive to stop generating
any false drive notifications.
• LOGERR (Log Errors) is not used and ignored internally by the Target.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
139
• 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 SCSI Hard Disk Drive Specification
140
17.11 MODE SENSE (5A)
Table 93: 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 MODE SENSE (5A) command provides a means for the drive to report various device parameters to the Initiator. See the
MODE SENSE (1A) command for a description of the fields in this command.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
141
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
142
17.12 PERSISTENT RESERVE IN (5E)
Table 94: Persistent Reserve In (5E)
Bit
Byte
7
6
5
0
4
2
1
0
Command Code = 5Eh
1
Reserved = 0
Service Action
2-6
7-8
3
Reserved = 0
(MSB)
Allocation Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
When a drive receives a PERSISTENT RESERVE IN command and RESERVE (6) or RESERVE (10) logical unit is active,
the command is rejected with a Reservation Conflict status.
PERSISTENT RESERVE IN command does not conflict with a reservation established by the PERSISTENT RESERVE OUT
command.
The PERSISTENT RESERVE IN command is used to obtain information about persistent reservations and reservation keys
that are present within a target. This command is used in conjunction with the PERSISTENT RESERVE OUT command.
The actual length of the PERSISTENT RESERVE IN parameter data is available in the parameter data. The Allocation Length
field in the CDB indicates how much space has been reserved for the returned parameter list.
If the length is not sufficient to contain the entire parameter list, the first portion of the list shall be returned. This shall not be
considered an error. If the remainder of the list is required, the Initiator should send a new PERSISTENT RESERVE IN command with an Allocation Length field large enough to contain the entire list.
17.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 95: 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
Reserved
Reserved
02h-1Fh
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
143
Hitachi Confidential
17.12.2 Parameter data for Read Keys
Table 96: 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 SCSI Hard Disk Drive Specification
144
Hitachi Confidential
17.12.3 Parameter Data for Read Reservations
Table 97: 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 (Table 103).
There shall be a Reservation Descriptor for the persistent reservation, if any, present in the Target having a persistent reservation.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
145
Hitachi Confidential
Table 98: 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
Type
(MSB)
14-15
Extent Length
(LSB)
•
Scope-specific address is filled with 0.
•
Scope and Type are described in PERSISTENT RESERVE OUT command section.
•
Extent length is filled with 0.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
146
Hitachi Confidential
17.13 PERSISTENT RESERVE OUT (5F)
Table 99: PERSISTENT RESERVE OUT (5F)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 5Fh
1
Reserved = 0
2
Service Action
Scope
Type
3
4
Reserved = 0
5
6
7
(MSB)
Parameter List Length = 18h
8
9
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
When a drive receives a PERSISTENT RESERVE OUT command and RESERVE (6) or RESERVE (10) logical unit is active,
the command is rejected with a Reserve Conflict status.
Parameter List Length must be 18h. If not, the drive returns Check Condition status. And the sense key is set to Illegal
Request and the additional sense data is set to Parameter List Length Error.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
147
Hitachi Confidential
17.13.1 Service Action
The following service action codes are implemented. If a code which is not supported or a reserved 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. In case of PERSISTENT RESERVE OUT command executing a Register service action, this field is ignored.
Table 100: PERSISTENT RESERVE OUT, Service Action Code
Code
Name
Description
Support
00h
Register
Register a reservation key with the device server
Yes
01h
Reserve
Create a persistent reservation using a reservation key
Yes
02h
Release
Release a persistent reservation
Yes
03h
Clear
Clear all reservation keys and all persistent reservations
Yes
04h
Preempt
Preempt persistent reservations from another Initiator
No
05h
Preempt and Abort
Preempt persistent reservations from another Initiator
and clear the task set for the preempted Initiator
Yes
06h
Register and
Ignore existing key
Register a reservation key with the drive
Yes
Reserved
Reserved
---
07h
1Fh
•
Register
This service action may conflict with a successfully established persistent reservation.
If the key specified in the reservation key field is not registered yet, a key specified in the Service Action Reservation
Key is registered as new key. If the key is already registered but the Initiator which registered the key is different
from the Initiator requesting the command, the drive returns Reservation Conflict status. If the key is already registered and the key is for the Initiator requesting the command, the key is replaced with new key specified in the Service Action Reservation Key field.
Up to four keys can be held at the same time. When four keys are already registered, PERSISTENT RESERVE OUT
command with Register service action which does not replace an existing key is rejected with Reservation Conflict
status.
When PERSISTENT RESERVE OUT command with Register service action completes successfully, the Generation
counter is incremented.
When keys are registered, the drive returns Reservation Conflict status against the RESERVE command and the
RELEASE command.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
148
Hitachi Confidential
•
Reserve
This service action does not conflict with a successfully established persistent reservation.
If the Initiator has not previously performed a Register service action, the command with this service action is
rejected with Reservation Conflict status.
If the key specified in the Reservation key field is already registered but the Initiator that registered the key is different from the Initiator requesting the command, the Target returns Reservation Conflict status.
If persistent reservation that is being attempted conflicts with persistent reservation that is held, the Target returns a
Reservation Conflict status.
The established persistent reservation applies to all commands received after the successful completion of the command.
•
Release
This service action may conflict with a successfully established persistent reservation.
If the Initiator requesting the command has not previously performed a Register service action, the command is
rejected with a status of Reservation Conflict.
If the key specified in the Reservation key field is already registered but the Initiator that registered the key is different from the Initiator requesting the command, the drive returns a Reservation Conflict status.
The drive returns Good status when a key specified in Reservation key field is not found.
When the key is found but the scope is different from the registered scope or the type is different from the registered
type, the command is rejected with Check Condition status. The sense key is set to Illegal Request and the additional
sense data is set to Invalid Release of Active Persistent Reservation.
•
Clear
If the indicator requesting the command has not previously performed a Register service action, the command is
rejected with a status of Reservation Conflict.
•
Preempt and Abort
This service action does not conflict with a successfully established persistent reservation.
If the Initiator requesting the command has not previously performed a Register service action, the command is
rejected with a status of Reservation Conflict.
If the key specified in the Reservation key field is already registered but the Initiator that registered the key is different from the Initiator requesting the command, the drive returns a Reservation Conflict status.
Even if the key specified in the Service Action Reservation key field is not registered, the drive makes new persistent
reservation without preempting if it does not conflict with an existing persistent reservation.
When the key is registered but reservation for the key is nothing yet and the new persistent reservation does not conflict with an existing persistent reservation, the drive makes new persistent reservation and clears the key and all
commands from the Initiator that was registered the key.
When the key specified in the Service Action Reservation Key is cleared even if a reservation for the key is nothing
yet, the drive makes UNIT ATTENTION condition for the Initiator that was registered the key. The sense key is set to
Unit Attention and the additional sense data is set to Reservation Preempted.
When PERSISTENT RESERVE OUT command with this service action completes successfully, the Generation
counter is incremented.
•
Register and Ignore Existing Key
This service action does not conflict with a successfully established persistent reservation.
The key specified in the Reservation Key field is ignored, and the key specified in the Service Action Reservation
Key field is registered as the new key, regardless of whether or not a key was already registered.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
149
Hitachi Confidential
Following the successful completion of the Register and Ignore Existing Key action, the Generation counter is incremented.
When the keys are registered, the drive returns Reservation Conflict status for Reserve and Release commands.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
150
Hitachi Confidential
17.13.2 Scope
Scope codes are implemented as follows. If an unsupported or reserved 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. In case of PERSISTENT RESERVE OUT command executing a Register service action, this field is ignored.
Table 101: PERSISTENT RESERVE OUT, Scope Code
Code
Name
Description
Support
0h
LU
Persistent reservation applies to the full logical unit
Yes
1h
Extent
Persistent reservation applies to the specific extent
No
2h
Element
Persistent reservation applies to the specific element
No
3h - Fh
Reserved
Reserved
---
17.13.3 Type
Type codes are implemented as follows. If an unsupported or reserved code is specified, the Target 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 102: PERSISTENT RESERVE OUT, Type Code
Code
Name
Support
RD
WR
NWR
Add Rsv
0h
Read Shared
No
---
---
---
---
1h
Write Exclusive
Yes
SH
EX
PH
A1
2h
Read Exclusive
No
---
---
---
---
3h
Exclusive Access
Yes
EX
EX
PH
A1
4h
Shared Access
No
---
---
---
---
5h
Write Exclusive Registrants Only
Yes
SH
EO
PH
A2
6h
Exclusive Access Registrants Only
Yes
EO
EO
PH
A2
7h-Fh
Reserved
---
---
---
---
---
RD
READ command and READ (10) command
WR
WRITE command and WRITE (10) command
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
151
Hitachi Confidential
NWR
Commands except following,
- READ command and READ (10) command
- WRITE command and WRITE (10) command
- RESERVE and RELEASE command
If any key is registered, the Target returns a Reservation Conflict status.
- PERSISTENT RESERVE IN command and PERSISTENT RESERVE OUT command
SH
SHared: The Target executes the command from all Initiators.
EX
EXclusive: The Target executes the command from the Initiator that holds the persistent reservation and
rejects the command from the other Initiators with Reservation Conflict status.
PH
ProHibited: The Target rejects the command from all Initiators.
EO
Exclusive registrant Only: The Target executes the command from the Initiator that has registered a key and
rejects the command from the other Initiators with Reservation Conflict status.
A1
The Target rejects new PERSISTENT RESERVE on any types and returns Reservation Conflict status.
A2
The Target accepts new PERSISTENT RESERVE with Write Exclusive Registrants Only type and Exclusive Access Registrants Only type. The Target rejects new PERSISTENT RESERVE with Write Exclusive
type and Exclusive Access type and returns Reservation Conflict status.
Table 103: Conflict between new and existing Persistent Reserve
Existing Type
1
3
5
6
New Type
Write Exclusive (1)
Yes
Yes
Yes
Yes
Exclusive Access (3)
Yes
Yes
Yes
Yes
Write Exclusive Registrants Only (5)
Yes
Yes
No
No
Exclusive Access Registrants Only (6)
Yes
Yes
No
No
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
152
Hitachi Confidential
17.13.4 Parameter list
Table 104: PERSISTENT RESERVE OUT, 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
Reserved
21
Reserved
22
(MSB)
Extent Length
23
(LSB)
17.13.5 Summary
Table 105: PERSISTENT RESERVE OUT, Service Action, Parameters and Generation counter
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 SCSI Hard Disk Drive Specification
153
Hitachi Confidential
17.13.5.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.
17.13.5.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.
17.13.5.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.
17.13.5.4 Scope-specified address
Parameter in the Scope-specified address field is ignored by the drive.
17.13.5.5 Extent length
Parameter in the Extent length field is ignored by the drive.
17.13.5.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 106: 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
17.13.5.7 Generation counter
The drive increments the Generation counter when Register service action or Preempt and Clear service action complete successfully.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
154
Hitachi Confidential
17.14 PRE-FETCH (34)
Table 107: 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
Reserved = 0
(MSB)
Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the Initiator.
•
Transfer length field specifies the number of contiguous blocks of data that are to be transferred into the cache. A
transfer length of zero indicates that blocks are to be transferred into the cache until the segment is filled or until the
last data 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 SCSI Hard Disk Drive Specification
155
Hitachi Confidential
17.15 READ (6) - (08)
Table 108: READ (6) - (08)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 08h
1
Reserved = 0
(MSB)
LBA
Logical Block Address
2-3
(LSB)
4
Transfer Length
5
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 SCSI Hard Disk Drive Specification
156
Hitachi Confidential
17.16 READ (10) - (28)
Table 109: 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
Reserved = 0
(MSB)
Transfer Length
(LSB)
9
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 SCSI Hard Disk Drive Specification
157
Hitachi Confidential
17.17 READ BUFFER (3C)
Table 110: 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 SCSI Hard Disk Drive Specification
158
Hitachi Confidential
17.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 111: 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.
17.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 SCSI Hard Disk Drive Specification
159
Hitachi Confidential
17.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 112: 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 SCSI Hard Disk Drive Specification
160
Hitachi Confidential
17.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.
17.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 113: Echo Buffer Descriptor
Bit
Byte
7
6
5
0
4
3
2
1
Reserved = 0
1
0
EBOS=0
Reserved = 0
2
Reserved = 0
3
(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.
17.17.6 Enable Expander Communications Protocol 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 SCSI Hard Disk Drive Specification
161
Hitachi Confidential
17.18 READ CAPACITY (25)
Table 114: READ CAPACITY (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 SCSI Hard Disk Drive Specification
162
Hitachi Confidential
17.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 115: 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)
Block Length
4-7
(LSB)
•
Block Length specifies the length in bytes of the block.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
163
Hitachi Confidential
17.19 READ DEFECT DATA (37)
Table 116: READ DEFECT DATA (37)
Bit
Byte
7
6
5
0
3
2
1
0
Command Code = 37h
1
Reserved = 0
2
Reserved = 0
3-6
7-8
4
Reserved = 0
Plist
Glist
0
Defect List Format
Reserved = 0
(MSB)
Allocation Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The READ DEFECT DATA command requests that the Target transfer the medium defect data to the Initiator.
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 SCSI Hard Disk Drive Specification
164
Hitachi Confidential
Table 117: 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 SCSI Hard Disk Drive Specification
165
Hitachi Confidential
17.19.1 Defect List Header
Table 118: 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)
17.19.2 Defect List Descriptor
Table 119: 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 SCSI Hard Disk Drive Specification
166
Hitachi Confidential
0
17.19.3 Bytes from Index Format (100b)
Table 120: 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
17.19.4 Physical Sector Format (101b)
Table 121: 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 SCSI Hard Disk Drive Specification
167
Hitachi Confidential
17.20 READ DEFECT DATA (B7)
Table 122: 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 17.19 “READ DEFECT DATA (37)” on page 164.)
17.20.1 Defect List Header
Table 123: 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 17.19.1, “Defect List Header,” on page 166.)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
168
Hitachi Confidential
17.20.2 Defect List Descriptor
Table 124: 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 17.19.2 “Defect List Descriptor” on page 166.)
17.20.3 Bytes from Index Format (100b)
Table 125: 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.
17.20.4 Physical Sector Format (101b)
Table 126: 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 SCSI Hard Disk Drive Specification
169
Hitachi Confidential
17.21 READ LONG (3E)
Table 127: 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
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
Reserved = 0
(MSB)
Byte Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The READ LONG command requests the drive to transfer one block of data to the Initiator. The transfer data includes data and
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 + 40
•
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 SCSI Hard Disk Drive Specification
170
Hitachi Confidential
17.22 REASSIGN BLOCKS (07)
Table 128: 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 SCSI Hard Disk Drive Specification
171
Hitachi Confidential
Following is the format of the data sent by the Initiator during the DATA OUT phase.
Table 129: Format of Reassign Blocks data
Bit
Byte
7
0-1
6
5
4
3
2
1
Reserved = 0
(MSB)
2-3
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. The LBAs are not required to be in
ascending order.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
172
Hitachi Confidential
17.23 RECEIVE DIAGNOSTICS RESULTS (1C)
Table 130: RECEIVE DIAGNOSTIC RESULTS (1C)
Bit
Byte
7
6
5
4
0
3
2
1
0
Command Code = 1Ch
1
Reserved = 0
Reserved = 0
2
PCV
Page Code
3
(MSB)
Allocation Length
4
(LSB)
5
VU = 0
Reserved = 0
FLAG
LINK
The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTIC command be sent to the Initiator.
•
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.
17.23.1 Receive Diagnostic Results Page 0
This page contains a list of supported pages.
Table 131: Receive Diagnostic Results page 0
Bit
Byte
7
6
5
4
3
0
Page Code = 0
1
Reserved = 0
2-3
Page Length = 02h
4
(Supported Pages) Page = 0h
5
Translate address page = 40h
2
1
The supported diagnostic page returns a list of supported pages in ascending order.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
173
Hitachi Confidential
0
17.23.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 132: Receive Diagnostic Results Page 40
Byte
Bit
7
6
5
4
3
0
Page Code = 40h
1
Reserved = 0
2-3
Page Length = 0Ah
4
Reserved = 0
5
RA
ALTS
ALTT
6-13
•
2
1
0
Supplied format
Reserved=0
Translate format
Translated Address
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
It specifies the format in which the address has been supplied.
•
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 one if the translated block is an inaccessible sector, which could reflect a defect, an
unused sector on a spare cylinder, or a sector beyond the Maximum Customer LBA.
•
ALTS (Alternate Sector) is set to one if the translated block is a sector in a spare cylinder that points to a reassigned
customer sector.
•
ALTT (Alternate Track) is set to one if the translated block is in alternate track area. This bit is not used by the
drive.
•
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:
Table 133: 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 SCSI Hard Disk Drive Specification
174
Hitachi Confidential
0
17.24 RELEASE (17)
Table 134: RELEASE (17)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 17h
1
Reserved = 0
3rdPty
3rd Party ID
2
Reservation Identification
3-4
Reserved = 0
5
VU = 0
Reserved = 0
Ext=0
FLAG
LINK
The RELEASE command is used to release a LUN previously reserved.
Note: It is not an error for an Initiator to release a LUN that is not currently reserved. The drive returns Good status without
altering the reservation.
•
3rdPty bit indicates that
1
this release process is for a third party that is specified by 3rd Party ID.
0
this release process is for the Initiator itself.
•
3rd Party ID specifies the ID of the third party for which the LUN is reserved. (Refer to Section 17.29 “RESERVE
(16)” on page 181.)
•
Extents must be 0. Extension is not supported by the drive.
•
Reservation Identification field is ignored.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
175
Hitachi Confidential
17.25 RELEASE (57)
Table 135: RELEASE (57)
Bit
Byte
7
6
5
0
1
4
3
2
0
Command Code = 57h
Reserved = 0
2
3rdPty
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 releases a LUN previously reserved. It is not an error for an Initiator to attempt to release a reservation that is not currently active. In this case the drive returns Good status without altering the reservation.
The drive does not support extents. The Ext (Extent) bit must be zero and the Reservation Identification field is ignored. If the
Ext 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.
If the 3rdPty bit is zero, then the third-party release option is not requested. If the 3rdPty bit is one, then the Target releases the
LUN, but only if the reservation was made using the third-party reservation option and the 3rd Party ID is the ID of the Initiator that made the reservation
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
176
Hitachi Confidential
17.26 REPORT DEVICE IDENTIFIER (A3)
Table 136: REPORT DEVICE IDENTIFIER (A3)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = A3h
1
Reserved = 0
Service Action = 05h
2
Reserved = 0
3
Reserved = 0
(MSB)
4-5
LUN=0
(LSB)
(MSB)
6-9
Allocation Length
(LSB)
10
11
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The REPORT DEVICE IDENTIFIER command requests that the device server send device identification information to the
application client.
The LUN contains the logical unit number parameter. This parameter is expected to be zero. Other value for this parameter
will cause the command to terminate with a CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST, and
the additional sense code is set to INVALID FIELD IN CDB.
The ALLOCATION LENGTH field indicates how much space has been reserved for the returned parameter data. If the
length is not sufficient to contain all the parameter data, the first portion of the data is returned. This is not considered an error.
The actual length of the parameter data is available in the IDENTIFIER LENGTH field in the parameter data. If the remainder
of the parameter data is required, the application client should send a new REPORT DEVICE IDENTIFIER command with an
ALLOCATION LENGTH field large enough to contain all the data.
The REPORT DEVICE IDENTIFIER parameter list contains a 4-byte field that contains the length in bytes of the parameter
list and the logical unit's identifier.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
177
Hitachi Confidential
Table 137: Report Device Identifier parameter list
Bit
Byte
7
0-3
(MSB)
4-n
6
5
4
3
2
1
0
Identifier Length = n - 3
(LSB)
Identifier
The IDENTIFIER LENGTH field specifies the length in bytes of the IDENTIFIER field. If the ALLOCATION LENGTH field
in the CDB is too small to transfer all of the identifier, the length is not adjusted to reflect the truncation. The identifier length
initially equals zero and is changed only by a successful SET DEVICE IDENTIFIER command.
The IDENTIFIER field contains a vendor specific value. The value reported is the last value written by a successful SET
DEVICE IDENTIFIER command. The value of the identifier is changed only by a SET DEVICE IDENTIFIER command.
The identifier value persist through resets, power cycles, media format operations.
The Target return the same Identifier to all Initiators on all ports.
The execution of a REPORT DEVICE IDENTIFIER requires the enabling of a nonvolatile memory within the logical unit. If
the nonvolatile memory is not ready, the device server returns Check Condition status rather than wait for the device to
become ready. The sense key is set to Not Ready and the additional sense data is set as described in the TEST UNIT READY
command. This information should allow the application client to determine the action required to cause the device server to
become ready.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
178
Hitachi Confidential
17.27 REPORT LUNS (A0)
Table 138: 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 139: 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 SCSI Hard Disk Drive Specification
179
Hitachi Confidential
17.28 REQUEST SENSE (03)
Table 140: REQUEST SENSE (03)
Bit
Byte
7
6
5
0
4
3
2
1
0
FLAG
LINK
Command Code = 03h
1
Reserved = 0
Reserved = 0
2-3
Reserved = 0
4
Allocation Length
5
VU = 0
Reserved = 0
The REQUEST SENSE command requests the drive to transfer sense data.
The sense data shall be available under the following conditions:
•
The previous command to the specified I_T_L1 nexus terminated with Check Condition status. Any other information (e.g. medium position) is available in any fields.
•
The previous command to the specified I_T_L nexus ended unexpected BUS FREE error.
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.
The sense data shall be preserved by the drive for the Initiator until retrieved by the REQUEST SENSE command or until any
other command for the same I_T_L nexus. Sense data shall be cleared upon receiving a subsequent command including
REQUEST SENSE to the same I_T_L nexus.
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.
The contents of the sense data are defined in Section 21.1 “SCSI Sense Data Format” on page 295.
1.A nexus which exists between an initiator, a target, and a logical unit.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
180
Hitachi Confidential
17.29 RESERVE (16)
Table 141: RESERVE (16)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 16h
1
Reserved = 0
2
3rdPty
3rd Party ID
Ext=0
Reservation Identification
(MSB)
3-4
Extent List Length = 0
(LSB)
5
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator that sends
this command or for the third party that is specified in this command.
This command results in reserving the entire LUN for the Initiator until one of the following occurs:
- The reservation is superseded by another valid RESERVE command from the Initiator that made the reservation.
- The LUN is released by a RELEASE command from the same Initiator.
- A hard reset condition occurs (a SCSI bus Reset assertion).
- A TARGET RESET message is received from any Initiator.
- Power off/on occurs.
•
•
3rdPty bit is to indicates that
1
this reservation is for a third party that is specified by 3rd Party ID.
0
this reservation is for the Initiator itself.
3rd Party ID specifies the ID of the third party for which the LUN is reserved.
Note: The LUN may be only released by the Initiator who sent the RESERVE command.
•
Extents must be 0. Extension is not supported by the drive.
•
Reservation Identification is ignored.
•
Extent List length must be zero. Extent List length is not supported.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
181
Hitachi Confidential
17.30 RESERVE (56)
Table 142: RESERVE (56)
Bit
Byte
7
6
5
0
4
3
2
0
Command Code = 57h
1
Reserved = 0
3rdPty
Reserved
2
Reservation Identification
3
Third Pay Device ID
4-6
Reserved = 0
7-8
1
(MSB)
Ext=0
Extent List Length = 0
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the
command or for a third party as specified by the Initiator.
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.
The 3rdPty bit of zero indicates that the Initiator that issued the Reserve command is the Initiator for which the LUN is
reserved.
The 3rdPty bit of one indicates that this is a third-party reservation. The 3rd Party ID byte specifies the ID of the third party for
which the LUN is reserved. A reservation made with the 3rdPty bit of one and the 3rd Party ID byte set to the Initiator that
issued this Reserve command is considered equivalent to a reservation made with the 3rdPty bit set to zero.
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 SCSI Hard Disk Drive Specification
182
Hitachi Confidential
17.31 REZERO UNIT (01)
Table 143: 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 SCSI Hard Disk Drive Specification
183
Hitachi Confidential
17.32 SEEK (6) - (0B)
Table 144: SEEK (6) - (0B)
Bit
Byte
7
6
5
0
1
4
3
2
1
Command Code = 0Bh
Reserved = 0
2
(MSB)
LBA
Logical Block Address
3
(LSB)
4
5
0
Reserved = 0
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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
184
Hitachi Confidential
17.33 SEEK (10) - (2B)
Table 145: 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 SCSI Hard Disk Drive Specification
185
Hitachi Confidential
17.34 SEND DIAGNOSTIC (1D)
Table 146: SEND DIAGNOSTIC (1D)
Bit
Byte
7
6
5
0
3
2
1
0
SlfTst
Dev0fl
Unt0fl
Command Code = 1Dh
1
Function Code
2
3-4
4
PF
RSVD =0
Reserved = 0
(MSB)
Parameter List Length
(LSB)
5
VU = 0
Reserved = 0
FLAG
LINK
The SEND DIAGNOSTIC command requests the drive to perform its self-diagnostic test or to perform a function based on a
page of information sent in a Data Out phase during the command.
•
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 SCSI Hard Disk Drive Specification
186
Hitachi Confidential
Table 147: 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
Foreground extended self-test
The device server starts its extended self-test routine in the
foreground mode. The completion for this test is reported in
Mode Page 0Ah (refer to section 17.11.9 Mode Page 0Ah).
111b
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 20.17 “Diagnostics” on page 246, for detailed listing of operations carried out by SEND DIAGNOSTIC command
and Power on Diagnostics.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
187
Hitachi Confidential
17.34.1 Send Diagnostic Page 0
This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS command.
Table 148: Diagnostic Page 0
Bit
Byte
7
6
5
4
3
0
Page Code = 0
1
Reserved = 0
2-3
2
1
0
Page Length = 0
17.34.2 Send Diagnostic Page 40
This allows the Initiator to translate a LBA or physical sector address to the other format. The address to be translated is passed
to the Target with the SEND DIAGNOSTIC command and the results are returned to the Initiator by the RECEIVE DIAGNOSTICS command.
The Target will read the parameter list from the Initiator, and, if no errors are detected in the parameter list, Good status will be
returned. The data translation will be performed upon receipt of the RECEIVE DIAGNOSTICS command.
Table 149: 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
188
Hitachi Confidential
•
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 150: 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 SCSI Hard Disk Drive Specification
189
Hitachi Confidential
0
17.35 SET DEVICE IDENTIFIER (A4)
Table 151: SET DEVICE IDENTIFIER (A4)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = A4h
1
Reserved = 0
Service Action = 06h
2-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 152: 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 SCSI Hard Disk Drive Specification
190
Hitachi Confidential
17.36 START STOP UNIT (1B)
Table 153: 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 SCSI Hard Disk Drive Specification
191
Hitachi Confidential
17.37 SYNCHRONIZE CACHE (35)
Table 154: 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
Reserved = 0
(MSB)
Number of Blocks
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded
on the media.
•
Logical Block Address is to specify where the operation is to begin.
•
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 SCSI Hard Disk Drive Specification
192
Hitachi Confidential
17.38 TEST UNIT READY (00)
Table 155: 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 SCSI Hard Disk Drive Specification
193
Hitachi Confidential
17.39 VERIFY (2F)
Table 156: 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
Reserved = 0
(MSB)
Verification Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that
no data will be transferred. This condition is not considered an error.
•
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 SCSI Hard Disk Drive Specification
194
Hitachi Confidential
17.40 VERIFY (16) - (8F)
Table 157: Write (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 SCSI Hard Disk Drive Specification
195
Hitachi Confidential
17.41 WRITE (6) - (0A)
Table 158: 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 17.15 “READ (6) - (08)” on page 156 for the parameters.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
196
Hitachi Confidential
17.42 WRITE (10) - (2A)
Table 159: 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
Reserved = 0
(MSB
Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The WRITE (10) command requests that the drive write the data transferred from the Initiator. This command is processed like
the standard WRITE (6) - (0A) command except for the longer transfer length.
•
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 SCSI Hard Disk Drive Specification
197
Hitachi Confidential
17.43 WRITE AND VERIFY (16) - (8E)
Table 160: Write and Verify (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 SCSI Hard Disk Drive Specification
198
Hitachi Confidential
17.44 WRITE AND VERIFY (2E)
Table 161: WRITE AND VERIFY (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
Reserved = 0
(MSB)
Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
WRITE AND VERIFY command requests that the drive writes the data transferred from the Initiator to the medium and then
verify that the data is correctly written.
•
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 SCSI Hard Disk Drive Specification
199
Hitachi Confidential
17.45 WRITE BUFFER (3B)
Table 162: 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
200
Hitachi Confidential
17.45.1 Combined Header And Data (Mode 00000b)
In this mode, the data to be transferred is preceded by a four-byte header.
Buffer ID must be zero. If another value is specified, no download function is performed and the command is terminated with
Check Condition status. And the drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in
CDB.
Buffer Offset must be zero. 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 163: Write Buffer Header
Bit
Byte
7
6
5
0-3
4
3
2
1
0
Reserved = 0
17.45.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 SCSI Hard Disk Drive Specification
201
Hitachi Confidential
17.45.3 Download Microcode (Mode 00100b)
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.
Note: If the write buffer command with this mode is executed and the invalid code is downloaded, then it is to be expected that
the drive will never be complete or hang up the subsequent command. This condition is normally recoverable by a power on/
off cycle, but there is no guarantee of it.
17.45.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. The following Buffer IDs are
supported by the Target:
- 00h : Main Microprocessor Code with all others in one (Single Binary or Chunked)
- nnh : ID of Vendor Unique Reserved Area
Any other value for the Buffer ID will cause the command to terminate with Check Condition status. The drive shall set the
sense key to Illegal Request and additional sense code to Illegal Field in CDB.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
202
Hitachi Confidential
17.45.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.
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.
17.45.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.
17.45.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 SCSI Hard Disk Drive Specification
203
Hitachi Confidential
17.46 WRITE LONG (3F)
Table 164: 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
•
40 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 SCSI Hard Disk Drive Specification
204
Hitachi Confidential
17.47 WRITE SAME (41)
Table 165: WRITE SAME (41)
Bit
Byte
7
6
0
5
4
3
2
1
0
Command Code = 41h
Reserved = 0
1
PBDATA LBDATA RelAdr =
0
=0
=0
(MSB)
2-5
Logical Block Address
(LSB)
6
7-8
Reserved = 0
(MSB)
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 SCSI Hard Disk Drive Specification
205
Hitachi Confidential
17.48 WRITE SAME (16) - (93)
Table 166: 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
7-8
Reserved = 0
(MSB)
9
Number of Blocks
(LSB)
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 SCSI Hard Disk Drive Specification
206
Hitachi Confidential
18.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 167: 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
This status is returned for every command except PRE-FETCH command in a series of linked commands
(except the last command), unless the command is terminated with CHECK CONDITION, RESERVATION
CONFLICT, BUSY status. If INTERMEDIATE or INTERMEDIATE-CONDITION MET status is not
returned, the series of linked commands is terminated and the task is ended.
14h
INTERMEDIATE CONDITION MET
This status is returned when a linked PRE-FETCH command has been completed, unless the command is
terminated with CHECK CONDITION, RESERVATION CONFLICT, BUSY status. If INTERMEDIATE or
INTERMEDIATE-CONDITION MET status is not returned, the series of linked commands is terminated
and the task is ended.
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 SCSI Hard Disk Drive Specification
207
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
208
19.0 SCSI message system
This chapter details how the message system is implemented on the drive. Included is a functional description of the supported
messages.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
209
19.1 Supported messages
The messages supported by the drive are listed below:
MESSAGE
CODE(hex)
Direction
Negate ATN
Before last ACK
TASK COMPLETE
00
IN
SYNCHRONOUS DATA TRANSFER REQUEST
01030
IN
OUT
Yes
WIDE DATA TRANSFER REQUEST*
010203
IN
OUT
Yes
PARALLEL PROTOCOL REQUEST
010604
IN
OUT
Yes
SAVE DATA POINTER
02
IN
---
RESTORE POINTERS
03
IN
---
DISCONNECT
04
IN
---
INITIATOR DETECTED ERROR
05
OUT
Yes
ABORT TASK SET
06
OUT
Yes
MESSAGE REJECT
07
OUT
Yes
NO OPERATION
08
OUT
Yes
MESSAGE PARITY ERROR
09
OUT
Yes
LINKED TASK COMPLETE
0A
IN
---
LINKED TASK COMPLETE (w/FLAG)
0B
IN
---
TARGET RESET
0C
OUT
Yes
ABORT TASK
0D
OUT
Yes
CLEAR TASK SET
0E
OUT
Yes
LOGICAL UNIT RESET
17
OUT
YES
SIMPLE
20XX
OUT
No
HEAD OF QUEUE
21XX
OUT
No
ORDERED
22XX
OUT
No
IGNORE WIDE RESIDUE*
2301
IN
---
IDENTIFY
80-FF
IN
---
IDENTIFY
80-FF
Key:
IN
YES
NO
--XX
*
IN
IN
---
OUT
No
= Target to Initiator, OUT = Initiator to Target
= Initiator shall negate ATN before last ACK of message
= Initiator may or may not negate ATN before last ACK of message
= Not applicable
= Queue Tag
= Wide SCSI Only
If an unsupported message is received, the drive will send the MESSAGE REJECT message to the Initiator. If at the time the
unsupported message is received a valid NEXUS exists, the drive will continue with the command. If no valid NEXUS exists,
the drive will go to Bus Free.
19.1.1 Task Complete (00)
The drive sends this message to the Initiator to indicate that the execution of a command has been terminated and that valid
status has been sent to the Initiator. After successfully sending this message the drive releases all bus signals and goes to BUS
FREE phase.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
210
19.1.2 Synchronous Data Transfer Request (01, 03, 01h)
Table 168: Synchronous Data Transfer Request.
Byte
Value
Description
0
01H
Extended message
1
03H
Extended message length
2
01H
SYNCHRONOUS DATA TRANSFER REQUEST code
3
M
Transfer period (M times 4 nanoseconds)
4
X
REQ/ACK offset
A pair of Synchronous Data Transfer Request (SDTR) messages shown in Figure 159 are exchanged between an Initiator and
a Target to establish the synchronous data transfer mode between the two devices. The message exchange establishes the permissible transfer period and REQ/ACK offset for a synchronous data transfer between the two devices. The Initiator may initiate a synchronous data transfer negotiation at any time after the LUN has been identified. A SDTR message exchange shall
be initiated by a SCSI device whenever a previously arranged data transfer agreement may have become invalid. The agreement becomes invalid after any condition that may leave the data transfer agreement in an indeterminate state such as
1. after a Power-on Reset
2. after a SCSI Bus “hard” reset condition
3. after a Target Reset message
In addition a SCSI device may initiate a SDTR message exchange whenever it is appropriate to negotiate a new data transfer
agreement (either synchronous or asynchronous).
M
The transfer period (M) is the minimum time allowed between leading edges of successive REQ pulses and of successive ACK pulses to meet the device requirements for successful reception of data. The drive supports transfer period in the range of 50 ns to 425 ns in increments of 25 ns. In addition to this, when the drive is
working in LVD mode, it supports transfer period of 25 ns.
REQ/ACK Offset
X
The ACK/REQ offset (X above) is the maximum number of REQ pulses allowed to be outstanding before the leading
edge of its corresponding ACK pulses is received at the drive. A REQ/ACK offset value of zero indicates asynchronous data transfer mode. The drive supports REQ/ACK offset values in the range 0 through 63.
If ATN is negated before all bytes of a multiple-byte extended message is received, the drive will go to BUS FREE to signal a
catastrophic error.
19.1.2.1 Synchronous Negotiation started by the Initiator
When the Target responds with REQ/ACK offset value of 0, the Initiator shall use asynchronous data transfer mode.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
211
LVD mode. The Target responds to each Initiator requested transfer period as shown below.
Table 169: Initiator Request/Target Response (LVD mode)
Initiator request
Target
response
Target transfer
period (ns)
Maximum
burst rate
(MT/s)
0 <= Mi <= 09
Mt = 10
25.00
40.00
10 <= Mi <= 10
Mt = 10
25.00
40.00
11 <= Mi <= 12
Mt = 12
50.00
20.00
13 <= Mi <= 18
Mt = Mi
75.00
13.33
19 <= Mi <= 25
Mt = Mi
100.00
10.00
26 <= Mi <= 31
Mt = Mi
125.00
8.00
32 <= Mi <= 37
Mt = Mi
150.00
6.67
38 <= Mi <= 43
Mt = Mi
175.00
5.71
44 <= Mi <= 50
Mt = Mi
200.00
5.00
51 <= Mi <= 56
Mt = Mi
225.00
4.44
57 <= Mi <= 62
Mt = Mi
250.00
4.00
63 <= Mi <= 68
Mt = Mi
275.00
3.64
69 <= Mi <= 75
Mt = Mi
300.00
3.33
76 <= Mi <= 81
Mt = Mi
325.00
3.08
82 <= Mi <= 87
Mt = Mi
350.00
2.86
88 <= Mi <= 93
Mt = Mi
375.00
2.67
94 <= Mi <= 100
Mt = Mi
400.00
2.50
101 <= Mi <= 106
Mt = Mi
425.00
2.35
107 <= Mi <= 255
Mt = 106
(Asynch mode)
N/A
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
212
SE mode. The Target responds to each Initiator requested transfer period as shown below.
Table 170: Initiator Request/Target Response (SE mode)
Initiator request
Target
response
Target transfer
period (ns)
Maximum
burst rate
(MT/s)
0 <= Mi <= 11
Mt = 12
50.00
20.00
12 <= Mi <= 12
Mt = 12
50.00
20.00
13 <= Mi <= 18
Mt = Mi
75.00
13.33
19 <= Mi <= 25
Mt = Mi
100.00
10.00
26 <= Mi <= 31
Mt = Mi
125.00
8.00
32 <= Mi <= 37
Mt = Mi
150.00
6.67
38 <= Mi <= 43
Mt = Mi
175.00
5.71
44 <= Mi <= 50
Mt = Mi
200.00
5.00
51 <= Mi <= 56
Mt = Mi
225.00
4.44
57 <= Mi <= 62
Mt = Mi
250.00
4.00
63 <= Mi <= 68
Mt = Mi
275.00
3.64
69 <= Mi <= 75
Mt = Mi
300.00
3.33
76 <= Mi <= 81
Mt = Mi
325.00
3.08
82 <= Mi <= 87
Mt = Mi
350.00
2.86
88 <= Mi <= 93
Mt = Mi
375.00
2.67
94 <= Mi <= 100
Mt = Mi
400.00
2.50
101 <= Mi <= 106
Mt = Mi
425.00
2.35
107 <= Mi <= 255
Mt = 106
(Asynch mode)
N/A
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
213
19.1.2.2 Synchronous Negotiation started by the Target
If the drive recognizes that negotiation is required, and if the “Target Initiated SDTR” jumper is installed, the drive sends a
SDTR message to the Initiator with minimum transfer period on the current receiver mode. The drive interprets the Initiator
corresponding transfer period as shown in the figure below.
LVD mode
Table 171: Target response to Initiator's transfer period (LVD mode)
Initiator's request
Target transfer
Maximum burst rate
period (ns)
(MT/s)
0 <= Mi <= 09
Send M+=10 to negotiate
N/A
10 <= Mi <= 10
25
40.00
11 <= Mi <= 11
50
20.00
12 <= Mi <= 12
50
20.00
13 <= Mi <= 18
75
13.33
19 <= Mi <= 25
100
10.00
26 <= Mi <= 31
125
8.00
32 <= Mi <= 37
150
6.67
38 <= Mi <= 43
175
5.71
44 <= Mi <= 50
200
5.00
51 <= Mi <= 56
225
4.44
57 <= Mi <= 62
250
4.00
63 <= Mi <= 68
275
3.64
69 <= Mi <= 75
300
3.33
76 <= Mi <= 81
325
3.08
82 <= Mi <= 87
350
2.86
88 <= Mi <= 93
375
2.67
94 <= Mi <= 100
400
2.50
101 <= Mi <= 106
425
2.35
107 <= Mi <= 255
Send Message Reject (Asynch mode) N/A
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
214
SE Mode
Table 172: Target response to Initiator's transfer period (SE mode)
Initiator's request
Target transfer
period (ns)
Maximum burst
rate (MT/s)
0 <= Mi <= 11
M+=12 to negotiate
N/A
12 <= Mi <= 12
50.00
20.00
13 <= Mi <= 18
75.00
13.33
19 <= Mi <= 25
100.00
10.00
26 <= Mi <= 31
125.00
8.00
32 <= Mi <= 37
150.00
6.67
38 <= Mi <= 43
175.00
5.71
44 <= Mi <= 50
200.00
5.00
51 <= Mi <= 56
225.00
4.44
57 <= Mi <= 62
250.00
4.00
63 <= Mi <= 68
275.00
3.64
69 <= Mi <= 75
300.00
3.33
76 <= Mi <= 81
325.00
3.08
82 <= Mi <= 87
350.00
2.86
88 <= Mi <= 93
375.00
2.67
94 <= Mi <= 100
400.00
2.50
101 <= Mi <= 106
425.00
2.35
107 <= Mi <= 255
Send Message Reject
(Asynch mode)
N/A
19.1.3 Wide Data Transfer Request (01, 02, 03h)
An Initiator and a Target exchange a pair of Wide Data Transfer Request messages to establish a data transfer width agreement
between the two devices. The Initiator may initiate a wide data transfer negotiation at any time after the LUN has been identified. The Target initiates a wide data transfer negotiation if the Target has not negotiated with the Initiator since the last time
the Target was Reset (Power-on Reset, SCSI Bus Hard Reset, or Target Reset message).
Target initiated negotiation occurs either immediately following the Command phase or immediately following the first reconnection. In either case negotiation occurs before any Data phase between the Target and the Initiator. The Target will negotiate
the data transfer width agreement prior to negotiating the synchronous data transfer agreement. If a synchronous data transfer
agreement is in effect when a Wide Data Transfer Request message is received, the Target will reset the synchronous agreement to asynchronous mode.
The implied data transfer width agreement remains in effect until the Target is Reset (Power-on Reset, SCSI Bus Hard Reset,
or Target Reset message) or a new data transfer width agreement is negotiated. If a Reset occurs, the Target goes to eight bit
mode.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
215
Table 173: Wide Data Transfer Request
Byte
E
Value
Description
0
01H
Extended message
1
02H
Extended message length
2
03H
WIDE DATA TRANSFER REQUEST code
3
E
Transfer width exponent
The Transfer Width Exponent (E) is two to the transfer width exponent bytes wide. Valid data transfer widths are 8
bits (E = 00h) and 16 bits (E = 01h). Value of E greater than 01h are reserved.
19.1.3.1 Transfer Width Negotiation started by the Initiator
If the Initiator recognizes that negotiation is required and sends a Wide Data Transfer Request message out, the Target
responds by changing to the Message In phase and sending a Wide Data Transfer Request message in to the Initiator prior to
transferring any additional message bytes (or any other Information phase bytes) from the Initiator. This provides an interlock
during the data transfer width negotiation.
The drive responds to each Initiator requested transfer width exponent as shown in the following table.
Table 174: Initiator request/Target response
Initiator's
request
Target’s
response
Target Data Transfer
Width
Ei = 00h
Et = 00h
8 Bit Data Transfers
Ei > 00h
Et = 01h
16 Bit Data Transfers
If after the Target's response above the Initiator asserts the ATN signal and the first message received is either a Message Parity
Error or a Message Reject message, the Target negates the data transfer width agreement and goes to 8 bits mode. For the Message Parity Error case the implied data transfer width agreement is reinstated if the Target successfully retransmits the Wide
Data Transfer Request message to the Initiator. For any other message the Target completes negotiation and goes to the negotiated data transfer width.
19.1.3.2 Transfer Width Negotiation started by the Target
If the Target recognizes that negotiation is required, the Target sends a Wide Data Transfer Request message to the Initiator
with the transfer width exponent equal to 1 (E = 01h). The Initiator must respond by asserting the ATN signal prior to its
release of ACK for the REQ/ACK handshake of the last byte of the Wide Data Transfer Request message. This provides an
interlock during the wide data transfer negotiation. If the Initiator does not assert the ATN signal, the Target goes to 8 bit
mode. If the Initiator does assert the ATN signal, the Target changes to the Message Out phase and receives a message from the
Initiator.
If the first message received is a Wide Data Transfer Request message, the Target establishes the new data transfer mode. The
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
216
drive interprets the Initiator corresponding transfer width exponent as shown in the following table.
Table 175: Target request to Initiator
Initiator request
Target Data Transfer Width
Ei = 00h
8 bit data transfers
Ei = 01h
16 bit data transfers
Ei > 01h
Send Message Reject (8 bit data transfer)
Note:
If the corresponding transfer width exponent received from the Initiator indicates a data transfer width that is greater
than 16 bits (E > 01h), the Target sends a Message Reject message to the Initiator to indicate 8-bit data transfer mode.
If the first message received from the Initiator is either a Message Parity Error or a Message Reject message, the Target goes to
8-bit data transfer mode. In the case of a Message Parity Error, the wide data transfer negotiation is restarted if the Target successfully retransmits the Wide Data Transfer Request message to the Initiator.
If the first message received from the Initiator is any other message, the Target goes to 8-bit data transfer mode. The Target
assumes that the Initiator does not support wide data transfer and does not attempt to renegotiate with this Initiator.
The Target does not consider the implied agreement for wide data transfer operation to exist until the Target leaves the Message Out phase, implying that no parity error was detected. If the Target detects a parity error while attempting to receive the
message from the Initiator, the Target goes to 8-bit data transfer mode. The Target will attempt to resume the wide data transfer
negotiation by retrying the Message Out phase.
Note: If during the Message In phase of negotiations, either Target or Initiator started, ATN is asserted prior to transmission
of the last byte of the message and the message is not Message Parity or Message Reject, the Target goes to 8-bit data transfer
mode.
19.1.4 Parallel Protocol Request (01, 06, 04h)
Parallel Protocol Request messages are used to negotiate a synchronous data transfer agreement and a wide data transfer agreement and to set the protocol options between two SCSI devices.
Table 176: Parallel Protocol Request
Byte
Bit
7
6
5
4
3
0
Extended Message = 01h
1
Extended Message Length = 06h
2
Parallel Protocol Request = 04h
3
Transfer Period Factor
4
Reserved = 00h
5
REQ/ACK Offset
6
Transfer Width Exponent
7
PCOMP_EN RTI
2
RD_STRM WR_FLOW HOLD_MCS QAS_REQ
1
DT_REQ
0
IU_REQ
PARALLEL PROTOCOL REQUEST messages are used to negotiate a synchronous data transfer agreement and a wide data
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
217
transfer agreement and to set the protocol options between the initiator and the drive.
•
Transfer Period Factor selects the transfer period and determines the timing values for the transfer rate. When both DT_REQ and IU_REQ are set to one, the following values are used. For the
values larger than 9 is received from the initiator when both DT_REQ and IU_REQ are set to one,
the drive responds with these bits set to zero.
Table 177: Initiator Request/Target Response (DT_REQ = 1, IU_REQ = 1)
Initiator Request
Target
Response
Target
Transfer
Transfer Rate
0 <= Mi <=
8
Mt = 08h
6.25 nSec
Fast-160
9 <= Mi <=
9
Mt = 09h
12.5 nSec
Fast-80
If DT_REQ is set one and IU_REQ is set to zero, the following values are used.
Table 178: Initiator Request/Target Response (DT_REQ = 1, IU_REQ = 0)
Initiator Request
Target
Response
Target
Transfer
9
Mt = 09h
12.5 nSec
Fast-80
10 <= Mi <=
10
Mt = 0Ah
25 nSec
Fast-40
11 <= Mi <=
12
Mt = 0Ch
50 nSec
Fast-20
13 <= Mi <=
25
Mt = 19h
100 nSec
Fast-10
255
Mt = 19h
(Asynch Mode)
Asynch
0 <= Mi <=
26 <= Mi <=
Transfer Rate
If both DT_REQ and IU_REQ is set to zero, the following values are used
Table 179: Initiator Request/Target Response (DT_REQ = 0, IU_REQ = 0)
Initiator Request
Target
Transfer
Transfer Rate
25 nSec
Fast-40
0 <= Mi <=
10
Mt = 0Ah
11 <= Mi <=
12
Mt = 0Ch
50 nSec
Fast-20
13 <= Mi <=
25
Mt = 19h
100 nSec
Fast-10
26 <= Mi <=
50
Mt = 32h
200 nSec
Fast-5
255
Mt = 32h
51 <= Mi <=
•
Target
Response
(Asynch Mode)
Asynch
REQ/ACK Offset determines the maximum number of REQs allowed to be outstanding before a
corresponding ACK is received at the drive during synchronous or paced transfers.
- The REQ/ACK Offset value is chosen to prevent overflow conditions in the reception buffer and offset
counter of the drive. The drive supports maximum offset of 127 (7Fh). A REQ/ACK Offset value of zero
indicates asynchronous data transfer mode and that the Transfer Period Factor and the protocol options
bits except QAS_REQ will be ignored.
•
Transfer Wide Exponent defines the transfer width to be used during DATA IN and DATA OUT
phases. If any of the protocol options bits other than QAS_REQ are set to one, then only wide
transfer agreements are valid. The following values are supported.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
218
- 00h: 8 bit data bus (Narrow transfer agreement).
- 01h: 16 bit data bus (Wide transfer agreement).
•
PCOMP_EN (Precompensation Enable) is used to negotiate if the pre-compensation is enabled
on all signals transmitted during DT DATA phases. The drive supports PCOMP_EN.
RTI (Retain Training Information) is used to negotiate if the saving of paced data transfer training
information is made so that the retraining is not necessary on each connection. The drive support
RTI.
RD_STRM (Read Streaming and Read Flow Control Enable) is used to negotiate if read streaming and read flow control are enabled. The drive supports RD_STRM.
WR_FLOW (Write Flow Control Enable) is used to negotiate if write flow control is enabled
during write streaming. The drive supports WR_FLOW.
HOLD_MCS (Hold Margin Control Settings) is used to negotiate if any margin control settings
which has been set with the margin control subpage of the port control mode page is retained.
QAS_REQ (Quick Arbitration and Selection Enable Request) is used to negotiate if QAS is
enabled. The drive supports QAS when IU_REQ is negotiated to be effective.
DT_REQ (DT Clocking Enable Request) is used to negotiate if DT DATA phase is enabled. The
drive supports DT_REQ.
IU_REQ (Information Unit Enable Request) is used to negotiate if information unit transfer is
enabled. The drive supports IU_REQ.
•
•
•
•
•
•
•
Table 180: Bit position table for Byte 7 of Parallel Protocol Request
Bit
7
6
5
4
3
Reserved
2
QAS_REQ
1
DT_REQ
0
IU_REQ
QAS_REQ (Quick Arbitrate and Select) is not supported. The bit should be zero.
DT_REQ A bit of zero for DT_REQ (Double Transition Enable Request) indicates that DT DATA phases are to be disabled
when received from the originating SCSI device and that DT DATA phases are not supported when received from the responding SCSI device.
A DT_REQ bit of one indicates that DT DATA phases are to be enabled when received from the originating SCSI device and
that DT DATA phases are supported when received from the responding SCSI device.
IU_REQ (Information Unit Request) is not supported. The bit should be 0.
19.1.5 Save Data Pointer (02)
This message is sent from the drive to direct the Initiator to copy the active data pointer to the saved data pointer. The SAVE
DATA POINTER message is only sent if the Initiator has previously indicated the ability to accommodate disconnection and
reconnection via the IDENTIFY message.
The drive will send the SAVE DATA POINTER message to the Initiator prior to sending a DISCONNECT message to the Initiator if a data phase has occurred and another data phase is required to successfully complete the command.
19.1.6 Restore Pointers (03)
This message is sent from the drive to direct an Initiator to copy the most recently saved pointers to the corresponding command, data, and status pointers. Command and status pointers should be restored to the beginning of the present command and
status areas. The data pointer should be restored to the value at the beginning of the data area in the absence of a SAVE DATA
POINTER message or to the value at the point at which the last SAVE DATA POINTER message occurred. Refer to Section
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
219
19.4, “SCSI Bus Related Error Handling protocol” on page 244.
19.1.7 Disconnect (04)
This message is sent from the drive to inform an Initiator that the present connection is going to be broken. A later reconnect
will be required in order to complete the current command. The disconnection serves to free the SCSI bus while the drive performs a relatively long operation that does not require the bus. These messages are sent only if the Initiator previously indicated (via the IDENTIFY message) the ability to accommodate disconnection and reconnection.
The DISCONNECT message may also be sent from the Initiator to the drive to disconnect from the SCSI bus. The drive does
not support the DISCONNECT message from the Initiator. And it always responds by sending MESSAGE REJECT message
to the Initiator.
19.1.8 Initiator Detected Error (05)
This message is sent from an Initiator to inform the drive that an error has been detected that does not preclude the drive from
retrying the previous COMMAND, DATA, and STATUS phase. The source of the error may be either related to previous activities on the SCSI bus or may be internal to the Initiator and unrelated to any previous SCSI bus activity.
If the Initiator intends to send this message, the Initiator must assert the ATN signal prior to its release of ACK for the last byte
transferred in the information phase that is to be retried. This provides an interlock so the drive can determine which information phase to retry.
After receiving this message the drive may retry the previous phase by sending a RESTORE POINTERS message to the Initiator and then repeating the previous COMMAND, DATA, or STATUS phase.
After receiving this message the drive may retry the MESSAGE IN phase by switching to the MESSAGE IN phase with
asserting REQ and repeating the previous MESSAGE IN phase.
19.1.9 Abort Task Set (06)
This message is sent from the Initiator to direct the drive to clear the present operation for this Initiator and logical unit including queued command(s). If a logical unit has been identified, then all pending data and status for the issuing Initiator and this
logical unit will be cleared and the drive will go to the BUS FREE phase. Pending data and status for other logical unit and Initiators will not be cleared. If a logical unit has not been identified, the drive will go to the BUS FREE phase without affecting
an operation on any logical unit for this or any other Initiator. In either case no status or ending message will be sent to the Initiator for this operation. It is not an error to send the ABORT message to a logical unit that is not currently performing an operation for the Initiator.
Note:
It is permissible for an Initiator to select the drive/LUN after the drive has disconnected from the Initiator for the purpose of sending an IDENTIFY message followed by an ABORT message. This will abort the command on the specified logical unit.
19.1.10 Message Reject (07)
This message is sent from either the Initiator or the drive to indicate that the last message received was inappropriate or has not
been implemented.
If the Initiator intends to send this message, the Initiator must assert the ATN signal prior to its release of ACK for the REQ/
ACK handshake of the message byte that is to be rejected. This provides an interlock so the drive can determine which message is rejected.
If the drive intends to send this message, the drive will change to the MESSAGE IN phase and send the MESSAGE REJECT
message to the Initiator prior to transferring any additional message bytes (or any other information phase bytes) from the Initiator regardless of ATN signal. This provides an interlock so the Initiator can determine which message is rejected. After the
drive sends a MESSAGE REJECT message and if ATN signal is still asserted, it shall return to the MESSAGE OUT phase.
The subsequent MESSAGE OUT phase shall begin with the first byte of a message
19.1.11 No Operation (08)
This message is sent from the Initiator to the drive when the Initiator does not currently have any other valid message to send.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
220
This message is ignored by the drive and will not affect any operation.
19.1.12 Message Parity Error (09)
This message is sent from the Initiator to inform the drive that the last message byte received had a parity error.
If the Initiator intends to send this message, the Initiator must assert the ATN signal prior to its release of ACK for the REQ/
ACK handshake of the message byte that has the parity error. This provides an interlock so the drive can determine which message byte has the parity error.
If the drive receives this message under any other circumstance, the drive will change to BUS FREE to signal a catastrophic
error. After receiving this message, the drive will retry sending the previous message to the Initiator.
19.1.13 Linked Task Complete (0A)
The drive sends this message to the Initiator to indicate that execution of a linked command (with flag bit equal to zero) has
completed and that valid status has been sent to the Initiator. After successfully sending this message, the drive goes to COMMAND phase to receive the next command.
19.1.14 Linked Task Complete With Flag (0B)
The drive sends this message to the Initiator to indicate that the execution of a linked command with flag bit set to one has
completed and that valid status has been sent to the Initiator. After successfully sending this message, the drive goes to COMMAND phase to receive the next command.
19.1.15 Target Reset (0C)
This message is sent from an Initiator to direct the drive to clear all current commands. This message forces a hard reset condition, which will reset the drive to an initial state with no operations pending for any Initiator. After receiving this message the
drive will go to the BUS FREE phase.
19.1.16 Abort Task (0D)
When the Target successfully receives this message, it clears the current I/O process and goes to Bus Free. If the Target has
already started execution of an I/O process, the execution will be halted.
Pending status, data, and commands for other active or queued I/O processes shall not be affected.
19.1.17 Clear Task Set (0E)
All I/O processes for all Initiators shall be cleared. All active I/O processes shall be terminated. The Target shall go to the Bus
Free phase following successful receipt of this message.
19.1.18 Logical Unit Reset (17)
This message is sent from an Initiator to direct the drive to clear all current commands and enter an initialized state with no
operations pending for any Initiator. This message forces a reset similar to the Target Reset message, with the exception that
initiator negotiated parameters (like interfaces speed and related options) are not reset, but are preserved.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
221
19.1.19 Queue Tag messages (20H, 21H, 22H)
Table 181: Queue Tag messages
Byte
0
1
Value
Description
20H
Simple Queue
21H
Head of Queue
22H
Ordered
XXh
Queue Tag
Queue Tag messages are used to specify an identifier called a Queue Tag for an I/O process that establishes the I_T_L_Q
nexus. The queue tag field is an 8-bit unsigned integer assigned by the Initiator during an initial connection. The Queue Tag for
every I/O process for each I_T_L nexus must be unique. If the Target receives a Queue Tag that is currently in use for the
I_T_L nexus, it will respond as “Incorrect Initiator Response”. A Queue Tag becomes available for reassignment when the I/O
process ends. The numeric value of a Queue Tag has no effect on the order of execution.
Whenever an Initiator connects to the Target, the appropriate Queue Tag message must be sent immediately following the
Identify message and within the same MESSAGE OUT phase to establish the I_T_L_Q nexus for the I/O process.
Whenever the Target reconnects to an Initiator to continue a tagged I/O process, the Simple message is sent immediately following the Identify and within the same MESSAGE IN phase to revive the I_T_L_Q nexus for the I/O process.
19.1.19.1 Simple (20h)
The Simple message specifies that the current I/O process be placed in the command queue. The order of execution with
respect to other I/O processes received with Simple messages is up to the discretion of the Target. The Target will send Simple
messages after reselection for I/O processes that were received with either Simple, Ordered, or Head of Queue messages.
19.1.19.2 Head Of Queue (21h)
Commands with this tag should be inserted into the head of the queue. When a command is being executed, this tagged command will be inserted to the head of queue to be executed after the command being currently executed. The previous executed
command will not be terminated by this tagged command. This tagged command will wait until the previous command is completed. If plural head-of-queue tagged commands are received, those command will be executed in LIFO (Last in First out)
order. This will be ignored if the WCE bit is set.
19.1.19.3 Ordered (22h)
This tagged command is executed in the order received. All commands received before this command should be executed
before this command and all commands received after this commands should be executed after this command.
19.1.20 Ignore Wide Residue
Table 182: Ignore Wide Residue message format
Byte
Value
Description
0
23H
Ignore Wide Residue message
1
01H
Ignore
The Ignore Wide Residue message is sent from the Target to indicate that the number of valid bytes sent during the last REQ/
ACK handshake of a DATA IN phase is less than the negotiated transfer width. The ignore field (always = 01h) indicates that
one byte (data bits 8-15) should be ignored. This message is sent immediately after the DATA IN phase and prior to any other
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
222
messages. Even though a byte is invalid, its corresponding parity bit is valid for the value transferred.
19.1.21 Identify (80 - FF)
This message is set by either the Initiator or the drive to establish the logical path connection between the two devices.
The IDENTIFY message is defined as follows:
Bit 7
This bit is always set to one to distinguish the IDENTIFY message from other messages.
Bit 6
This bit is only set to one by the Initiator to grant the drive the privilege of disconnecting. If this bit is zero,
the drive will not disconnect unless the Initiator instructs the drive to disconnect by sending a DISCONNECT message to the drive. This bit is set to zero when the drive sends an IDENTIFY message to the Initiator.
Bits 5-0
These bits specify the logical unit number (LUN).
Only one LUN may be identified for any one selection sequence. If the drive receives an IDENTIFY message with a new LUN
after the LUN had previously been identified, the drive will go to the BUS FREE phase to signal a catastrophic error. The Initiator may send more than one Identify message during a selection sequence in order to toggle disconnect/reconnect permission if the specified LUN remains the same.
When the IDENTIFY message is sent from the drive to the Initiator during reconnection, an implied RESTORE POINTERS
message must be performed by the Initiator.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
223
19.2 Supported message functions
The implementation of the supported messages will also include the following functions.
•
Retry SCSI Command or STATUS phase
The retry will be caused by the following error condition.
- The drive detected SCSI bus parity error (Command phase)
- The drive receives INITIATOR DETECTED ERROR MESSAGE during or at the conclusion of an information
transfer phase (Command Data Out or Status Phase)
Note: The Initiator may send the INITIATOR DETECTED ERROR message as a result of an Initiator detected SCSI
Bus parity error or an internal error.
•
Retry MESSAGE IN phase
- The retry will be caused by the receipt of a MESSAGE PARITY ERROR message immediately following a MESSAGE IN phase.
Note: The Initiator may send the MESSAGE PARITY ERROR message as a result of an Initiator detected SCSI Bus
parity error during the Message In phase.
•
Receipt of multiple Identify messages
- The Initiator is allowed to send multiple IDENTIFY messages out in order to toggle the disconnect/reconnect permission bit. This may be used to selectively enable or disable disconnect/reconnect permission during portions of a
command. Note that this function does not affect the operation of the Forced Disconnect function.
•
MESSAGE REJECT during Target Disconnection
- If the Initiator rejects the SAVE DATA POINTER message, the drive will disable disconnect/reconnect permission.
This is equivalent to receiving an IDENTIFY message with bit 6 equal to zero. This will cause the drive to inhibit
the pending disconnection.
- If the Initiator rejects the DISCONNECT message, the drive will not disconnect but may attempt to disconnect at a
later time. This function may be used to selectively disable disconnection during portions of a command.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
224
19.3 Attention condition
The attention condition allows an Initiator to inform the drive that a MESSAGE OUT phase is desired. The Initiator may create the attention condition by asserting the ATN signal at any time except during the ARBITRATION or BUS FREE phases.
The Initiator must create the attention condition by asserting the ATN signal at least two deskew delays before releasing ACK
for the last byte transferred in a bus phase to guarantee that the attention condition will be honored before transition to a new
bus phase. This will guarantee a predictable drive response to a message received during the MESSAGE OUT phase for this
attention condition. If the ATN signal is asserted later, it may be honored in the current bus phase or the next bus phase and
then may not result in the expected action.
After the Initiator asserts the ATN signal, the drive will respond with the MESSAGE OUT phase as follows:
Current phase
Response
COMMAND
MESSAGE OUT phase will occur after part or all of the Command Descriptor Block has been transferred to
the drive. The Initiator must continue REQ/ACK handshakes during the COMMAND phase until the drive
enters the MESSAGE OUT phase.
DATA
The Message Out phase will occur after part or all of the data bytes have been transferred and not necessarily
on a logical block boundary. The Initiator must continue REQ/ACK handshakes (asynchronous transfer)
until it detects the phase change.
Note: In synchronous transfer the Initiator must continue sending ACK pulses to reach an offset of zero.
STATUS
The Message Out phase will occur after the REQ/ACK handshake of the status byte has been completed.
MESSAGE IN The Message Out phase will occur before the drive sends another message.
SELECTION
If ATN occurs during a Selection phase and before the Initiator releases the BSY signal, the Message Out
phase will occur immediately after that Selection phase.
RESELECTIONThe MESSAGE OUT phase will occur after the drive has sent its IDENTIFY message for that RESELECTION phase. (The drive first tries to complete the reselection.)
The Initiator must keep the ATN signal asserted if more than one message byte is to be transferred during the MESSAGE Out
phase. The drive will process each message byte (multiple bytes for an extended message) prior to receiving the next message
from the Initiator. The drive will continue to handshake and process byte(s) in the MESSAGE OUT phase until ATN goes false
unless one of the following conditions occurs:
1. The drive receives an illegal or inappropriate message and goes to the MESSAGE IN phase to send a MESSAGE
REJECT message.
2. The drive detects a catastrophic error condition and goes to the BUS FREE phase.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
225
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
226
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 in Identify Message” on
page 259)
2. Check Condition status for Incorrect Initiator Connection (See Section20.1.3, “Incorrect Initiator Connection” on
page 228)
3. Check Condition status for Unit Attention Condition (See Section 20.1.5, “Unit Attention Condition” on page 230
4. Busy Status or Queue Full Status (See 20.1.4, “Command Processing During Execution of Active I/O Process” on
page 228
5. Check Condition status for Deferred Error Condition (See Section 20.1.8, “Deferred Error Condition” on page 231)
6. Check Condition status during Startup and Format operations (See Section “20.1.6, “Command processing during startup and format operations” on page 231)
7. Reservation Conflict status (See Section 20.1.10, “Command Processing while Reserved” on page 239)
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 in Identify Message
There are three different circumstances defined within the SCSI protocol when the response to an invalid LUN will occur.
Each of these result in a different response.
20.1.2.1 Case 1 - Selection message sequence with Inquiry command
The INQUIRY command is a special case in SCSI. It is used to configure the bus when the drive ID's and LUN's are not
known. The proper response is to return the inquiry data with a peripheral drive type of 1Fh which indicates that the specified
LUN is not supported.
20.1.2.2 Case 2 - Selection message sequence with any other command
Any other commands except REQUEST SENSE return CHECK CONDITION status when an invalid LUN is specified in the
message sequence following selection. In response to a REQUEST SENSE command the target shall return sense data. The
sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to LOGICAL UNIT NOT SUPPORTED.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
227
20.1.2.3 Case 3 - After selection message sequence
It is permissible for the initiator to issue multiple IDENTIFY messages during a single command sequence provided the LUN
remains the same. If the LUN is altered, the drive goes to a Bus Free Phase.
20.1.3 Incorrect Initiator Connection
Incorrect Initiator Connection error is reported if any of the following conditions occur:
•
an Initiator attempts to establish an I_T_L nexus when an I/O process (either queued or active) with an I_T_L nexus
already exists from a previous connection with the same Initiator.
•
an Initiator attempts to establish an I_T_L_Q nexus when an I_T_L nexus already exists from a previous connection
with the same Initiator.
•
an Initiator attempts to establish an I_T_L nexus when an I_T_L_Q nexus already exists from a previous connection
with the same Initiator.
Note: It is not an Incorrect Initiator Connection to send a command without a Queue tag message when sense is
pending on the logical unit for the Initiator that issues the REQUEST SENSE command. (If the command is not
REQUEST SENSE or INQUIRY, sense data is cleared upon receipt of the command.)
•
an Initiator attempts to establish an I_T_L_Q nexus when an I/O process (either queued or active) when an I_T_L_Q
nexus already exists from a previous connection with the same Initiator.
If any of the above errors occur, all queued I/O processes and active I/O processes associated with the issuing Initiator on the
specified logical unit are terminated. The current I/O process is ended with a Check Condition status, the sense key is set to
Aborted Command, and the additional sense code is set to Overlapped Commands Attempted. Status is only returned for the
current I/O process.
20.1.4 Command Processing During Execution of Active I/O Process
When the Target is not executing any active I/O processes, a new I/O process is permitted to execute (unless execution is prevented by another internal Target condition listed in Section “Priority of SCSI Status Byte Reporting” on page).
If an active I/O process does exist when the Target receives a new command, then the Target determines if
•
Check Condition Status with Sense Key = Aborted Command is returned for an Overlapped Commands Attempted
error
•
the command is permitted to execute
•
the command is added to the command queue
•
Queue Full Status is returned
•
Busy Status is returned
If an active I/O process does exist when the Target receives a new command, 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 Aborted Command and the additional sense code set to
Overlapped Commands Attempted
- See Section 20.1.3, “Incorrect Initiator Connection” on page 228.
•
the command is permitted to execute if the command is an Inquiry or Request Sense command
•
Check Condition Status is returned with Sense Key set to Logical Unit Not Ready if the startup operation or format
operation is an active process.
•
the command is permitted to execute if the conditions to execute concurrently are met. (See Section 20.5, “Concurrent I/O Process” on page 241)
•
the command is added to the command queue for an I_T_L nexus if all the following conditions exist:
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
228
- no Queue Tag message was received during the connection which established the I/O process
- disconnection is allowed for the current I/O process
- there is no queued I/O process or active I/O process corresponding to the I_T_L nexus for the current I/O process
- the command is not linked to a previous command
•
the command is added to the command queue for an I_T_L_Q nexus if the following conditions exist:
- a Queue Tag message was received during the connection which established the I/O process
- Tagged Queuing is enabled (DQue = 0)
- an I/O process (either active or queued) exists at the Target for this Initiator
- disconnection is allowed for the current I/O process
- there is no queued I/O process or active I/O process corresponding to the I_T_L_Q nexus for the current I/O process
- the command is not linked to a previous command.
•
Queue Full Status is returned if any one of the following conditions exists:
- the command would otherwise be queued (according to the rules described above) but the command queue is full
and all slots are utilized
- the command would otherwise be queued (according to the rules described above) but all of the available command
queue slots not reserved for use by another initiator are utilized
- Tagged Queuing is enabled (DQue = 0) and a Format Unit command was previously queued but has not yet begun
execution
- Tagged Queuing is enabled (DQue = 0) and a Unit start command was previously queued but has not yet begun
execution
•
Busy Status is returned if any of the following conditions exists:
- Tagged Queuing is disabled (DQue = 1) and a Format Unit command was previously queued but has not yet begun
execution
- Tagged Queuing is disabled (DQue = 1) and a Unit start command was previously queued but has not yet begun
execution
- the command would otherwise be queued (according to the rules described above) but disconnection is not allowed
for the current I/O process.
If a command is queued, command execution may still be prevented at a later time when the command is dequeued to become
an active I/O process. This occurs if command execution is prevented at the time the command is dequeued by another internal
Target condition listed in Section 20.1.1, “Priority of SCSI Status Byte Reporting” on page 227.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
229
20.1.5 Unit Attention Condition
The drive will generate a unit attention condition for each Initiator whenever these conditions are in effect:
•
The drive has been reset. This includes Power On Reset, SCSI Bus Reset, SCSI TARGET RESET message.
•
Another Initiator has changed the Mode parameters in effect for this Initiator.
•
Another Initiator issued a Log Select, thus clearing log parameters.
•
The microcode has been changed. WRITE BUFFER command has been executed to download microcode. In this
case a unit attention condition is generated for all Initiators except the one that issued the command.
•
Commands are cleared by another Initiator. This condition is generated against the Initiator that has queued commands if
- a Clear Queue Message is received
- a Contingent Allegiance Condition is cleared when QERR (in Mode Page 0A) is 1
- a DQue is set to 1 while queued commands exist
•
SCSI Bus transceiver mode change (LVD <==> Single Ended).
•
Another Initiator preempted Reservations or Registrations.
•
A Predictive Failure Analysis threshold has been reached.
The unit attention condition persists for each Initiator until that Initiator clears the condition as described in the following paragraphs.
If the drive receives a command from each Initiator before reporting a Check Condition status for a pending unit attention
condition for that Initiator, the response of the drive varies with the command as follows:
INQUIRY
The drive executes the command with Good status and preserves the unit attention condition.
REQUEST SENSE
If the drive has an available pending sense data for the Initiator, the drive sends the pending sense
data and preserves the unit attention condition for the Initiator. If the drive does not have an available pending sense data for the Initiator, the drive sends sense data for the unit attention condition
and clears the unit attention condition for the Initiator.
ALL OTHER
The drive terminates the command with a Check Condition status and preserves the unit attention
condition.
If the drive receives a command from each Initiator after reporting a Check Condition status for a pending unit attention condition for that Initiator, the response varies with the command as follows:
REQUEST SENSE
The drive sends the sense data for a pending unit attention condition, returns Good status, and
clears the unit attention condition for the Initiator.
ALL OTHER
The drive executes the command with Good status and clears the unit attention condition, unless
another unit attention condition exists. The sense data for the unit attention condition is then lost.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
230
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 send 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 SCSI Hard Disk Drive Specification
231
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 is not started by the option jumper setting (Disable Auto Spin Up)
- Spindle Motor is delayed from spinning up by the option jumper setting (Auto Start Delay)
- 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)
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 183: 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)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
232
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 SCSI Hard Disk Drive Specification
233
20.1.9.2 Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up
Table 184: 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 SCSI Hard Disk Drive Specification
234
20.1.9.3 Response to SCSI Command in Degraded Mode - Spindle Start Failure
Table 185: 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 SCSI Hard Disk Drive Specification
235
20.1.9.4 Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command
Table 186: Spindle Motor Degraded Mode - Spindle Stopped by Unit Stop 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 SCSI Hard Disk Drive Specification
236
20.1.9.5 Self Configuration Failure Degraded Mode
Table 187: 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 SCSI Hard Disk Drive Specification
237
20.1.9.6 Format Command Failure Degraded Mode
Table 188: 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)
Executed
Format Unit
- 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 SCSI Hard Disk Drive Specification
238
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 227.
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 do not disconnect from the SCSI bus prior to completion. They are executed prior to attempting to complete
the execution of any other pending command that has disconnected from the SCSI bus. Therefore, a second priority command
cannot be received during the execution of a priority command.
These commands are never queued whether or not the command is sent with a queue tag. However, the rule for an Incorrect
Initiator Connection still apply to priority commands. See Section 20.1.3, “Incorrect Initiator Connection” on page 228.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
239
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 and will be immediately executed without Bus disconnection:
•
Priority Commands (i.e.: Request Sense and Inquiry)
•
Commands linked to previous commands. These are defined to be part of a single I/O process. (Linked commands are
always executed immediately following the previous command from the same initiator. No other Initiator's command
are allowed to be executed between two linked commands.)
•
Commands for which disconnection is not allowed. (These may result in a Busy Status.)
•
Commands in which a SCSI bus error occurred between selection and first disconnection following the receipt of the
CDB.
•
Commands for an invalid LUN.
•
Commands which cause an OVERLAPPED COMMANDS ATTEMPTED error (see Section 20.1.3, “Incorrect Initiator Connection” on page 228).
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 Tagged Queuing
Commands with a tag message are saved in the command queue. Queued commands will be reordered by the target defined
rule. See the Section 20.4, “Command Reordering” on page 241 for details.
20.3.3 Untagged Queuing
The target supports queuing one I/O process from each initiator. If the target receives an untagged I/O process while executing
an I/O process from a different initiator, the untagged I/O process may be queued.
Untagged I/O processes are treated by the target as though they were received with Simple messages for purposes of queuing.
Note: There is no guarantee that I/O processes are executed in the order they were received in a multiple initiator environment when Untagged Queuing is enabled.
20.3.4 Command Queuing Rule
Commands can be received during an active I/O process if the Bus is free. Read(6), Read (10), Write(6) and Write (10) can be
active at the same time. See Section 20.5, “Concurrent I/O Process” on page 241 for details.
20.3.5 Queue Full Status
This status is returned when a Simple, ORDERED or HEAD OF QUEUE message is received and the command queue is full.
The I/O process is not placed in the command queue. Since one queue element is reserved for each initiator, any untagged
command that does not cause Incorrect Initiator Connection will not cause Queue Full status.
20.3.6 Device Behavior on Command Queuing
1. Initiators must send a Queue tag immediately after the Identify message in Message Out phase just after Selection. Tar-
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
240
gets send a Simple message immediately after the Identify message in Message In phase just after Reselection.
2. Each initiator can issue either a tagged command or an untagged command exclusively at the same time. Other initiators can exist which operate mutually exclusively with tagged or untagged commands
3. When DQue (Disable queue) of mode page 0Ah is 1, if an initiator issues a tagged command, the drive returns “Message Reject” message (07h) and receives that command as an untagged command.
4. Queue Tag number does not affect the order of execution.
5. If an initiator issues a command with a queue tag which is the same as the current I/O process or queued I/O process.
The target returns Incorrect Initiator connection.
6. A series of linked commands are a single I/O process and are assigned the queue tag established in the initial selection.
A command received with a Head-of-Queue tag message shall not suspend a series of linked commands for which the
target has begun execution.
7. If DQue is changed to 1 while queued commands exist, all queued commands for the all initiators will be aborted. All
future commands received from any initiator with a queue tag will be processed as untagged commands with a message
reject message being returned immediately after the qtag is received by the target.
20.4 Command Reordering
Command reordering function is supported under tagged command queuing enabled (DQue = 0). The recorder feature reorders
Read/Write commands in order to minimize seek time between commands. This function will improve total throughput of the
drive.
20.5 Concurrent I/O Process
The Concurrent I/O process when multiple I/O processes are active (not queued) on the same logical unit at the same time. The
target may start the data phase of an I/O process while another I/O process is not completed. The following I/O processes are
allowed to execute concurrently:
•
Unlinked and untagged Request Sense and Inquiry during execution of other commands.
•
One of the following commands can be executed while another one or the same one of the following commands is
being executed, if those are untagged or Simple tagged commands.
- Read(6), Read (10)
- Write(6), Write (10)
When an I/O process ends in check Condition Status, the drive enters the Contingent Allegiance Condition and other queued I/
O processes from the same initiator will not execute until the CAC is cleared by that initiator. See Section 20.16, "Contingent
Allegiance Condition" on page xxx for details.
If an I/O process(P-1) encounters an error while another I/O process (P-2) is active, the drive returns check Condition to P-1.
If P-2 is from the same initiator as P-1 the drive will suspend P-2 at the earliest convenient point and will not reconnect for
data or status. Depending on the setting of QErr bit in the Control mode page, P-2 will either be suspended until the CAC is
cleared or terminated. If the drive gets an error on P-2 before suspending the execution of P-2, it will keep the sense data separately from the sense data for P-1. The sense data for P-2 will be set after the Contingent Allegiance condition caused by P-1
is cleared.
If P-2 is from a different initiator than P-1, then P-2 is allowed to continue executing after entering CAC for P-1, pending QErr
is not set to terminate all processes to all initiators. Then if an error occurs on P-2 before the CAC is cleared on P-1, the drive
will send check condition and generate a CAC for P-2 while maintaining the CAC and sense for P-1.
20.6 Write Cache
If the WCE (Write cache enable) bit is 1, the drive returns Good Status and Task complete message and goes to Bus Free
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
241
Contingent allegiance condition all queued processes including commands from other initiators are suspended.
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 SCSI Hard Disk Drive Specification
242
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 189: 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 SCSI Hard Disk Drive Specification
243
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 32 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 230 for more information.
20.10 Reselection Time-out
If reselection fails, it will be retried one or more times depending on the drive model. Please see the individual drive specifications for the number of retries allowed.
20.11 Single Initiator Selection
For single initiator systems it is not an error to have only the target ID bit present during selection. Disconnection is not
allowed for Single Initiator Selection with only one ID bit present during selection. The initiator must not send an Identify
message with the disconnect permission bit(6) on.
20.12 Non-arbitrating systems
The Target cannot detect whether other SCSI devices on the SCSI bus use arbitration prior to selection. As a consequence the
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
244
Target allows disconnect permission to be enabled by the Identify message independent of the initiator's use of arbitration prior
to selection. A non-arbitrating initiator must ensure that disconnect permission in the Identify message is disabled (bit 6=0) for
proper operation.
20.13 Selection without ATN
If the target is selected without ATN signal active, no Identify message is received from the Initiator. In this case the LUN is
identified from the CDB and disconnect permission is disabled. The target does not perform any phase retries. The target still
responds to a subsequent attention condition. However the LUN is not considered to be known if a fatal error is detected during the Command phase. That is a Command phase parity error or a fatal message error in response to attention condition during Command phase is handled as a Bus Free error with no sense data. The target also knows the use of linked commands if
selected without ATN.
Phase retries may be allowed if a subsequent Identify message is received.
20.14 Multiple Initiator Environment
20.14.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.14.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.
20.14.3 Initiator Data Transfer Mode Parameter
A separate data transfer mode parameters area is reserved and maintained for each initiator.
20.15 Contingent Allegiance Condition
The contingent allegiance condition shall exist following the return of Check Condition, except for a Check Condition caused
by Invalid LUN. Execution of all queued commands shall be suspended until the contingent allegiance condition is cleared.
The contingent allegiance condition can be cleared by the initiator in one of the following ways:
•
By issuing a REQUEST SENSE command to the Target and receiving the sense data. This is the recommended way
•
By issuing any other command to the I_T_x nexus that reported the fault
•
By issuing an Abort message to the I_T_x nexus that reported the fault. This will also abort the current and queued I/
O process from that initiator
•
By issuing a Target Reset message to the Target. This will also abort all current and queued I/O processes
•
By generating a RESET condition on the bus. This MUST be the last resort
20.16 Reset
The Reset condition is used to clear all SCSI devices from the bus. This condition takes precedence over all other phases and
conditions. After a reset condition is detected and the reset actions completed, the target returns to a 'SCSI bus enabled' state
that allows the target to accept SCSI commands.
This device uses the Hard reset option as defined in the SCSI-3 standard.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
245
20.16.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.
SCSI Bus Reset
This is a reset generated when the SCSI bus control line RST goes active.
Target Reset Message
This is the reset generated by the SCSI Target Reset Message (0Ch).
20.16.2 Reset Actions
The action taken by the drive following a reset is dependent on the source of the reset.
20.16.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
20.16.2.2 SCSI Bus reset and SCSI Target Reset message
These two reset conditions cause the following to be performed.
- If reset goes active while the power-up sequence is in progress, the power-up sequence is started over.
- If the Auto Start pin is grounded and a startup sequence has not yet completed, a startup sequence will be reattempted from the beginning.
Note: The power-up sequence, having already completed, is not rerun.
- If reset occurs while a physical sector is being written, the write operation is disabled after the current physical sector is written. Data is not lost as long as power stays valid until the physical sector being written is completed.
20.17 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.17.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
4. RAM test for Sector Buffer
5. Start Spindle Motor (if Auto spin up enable)
6. Calibration of Actuator
7. Read/Write test for all Heads
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
246
8. Validation of RAM code and data table (RDM, Log, Mode Page) from the Reserved Area
If Auto spin up is disabled, steps 5 - 8 will be executed by the first START STOP UNIT command which has the Start bit set.
Faults detected before successful completion of the HDC section could prevent the drive from responding to a selection.
Faults detected after the successful completion of the HDC test section will be reported as CHECK CONDITION status to the
Initiator on the first command issued after a fault is detected (except for the INQUIRY, REPORT LUNS and REQUEST
SENSE commands). The INQUIRY, REPORT LUNS and REQUEST SENSE commands will always be responded with a
GOOD status. Detecting a fault during power on will not terminate execution of the tests nor will it terminate the power on
process.
20.17.2 Self-test via SEND DIAGNOSTIC Command
20.17.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.17.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.17.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.
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
247
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.
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 190: 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
Drive Diagnostics
This test is comprised of the Default Self Test as defined
in Section 20.17.2.1, “Default Self-test” on page 247
3h
SMART
Perform SMART testing and check results to ensure that
SMART threshold criteria are not exceeded
4h
Low Level Format check
Check to insure that the media is currently not in the
MEDIA FORMAT CORRUPTED state.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
248
5h
Physical Head Check
Write/Read test on each head in a predefined location in
the drive's Reserved Area of the disk.
6h
Random Verify
Perform 4000 random verify operations and insure no
uncorrectable errors.
7h
- Verify First
300MB
Verify all
LBA’s
Sequential verify operation. Ensure that no uncorrectable errors occur within the verify range.
- Verify Last
100 MB
8h
Recheck SMART
Same as segment 3h.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
249
20.18 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.19 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.19.1 Reassignment Time
The drive should be allowed a minimum of 5 seconds to complete a “Reassign Blocks” command.
20.19.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.19.3 Start/Unit 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.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
250
20.19.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.19.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 SCSI Hard Disk Drive Specification
251
20.20 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.20.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 SCSI Hard Disk Drive Specification
252
20.20.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.20.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 17.10.3, “Mode Page 01
(Read/Write Error Recovery Parameters)” on page 114) 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 SCSI Hard Disk Drive Specification
253
20.20.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 191, the Key, Code, and Qualifier fields are all hex values (i.e., Sense Key 1 is 1h, Sense Code 17 is 17h,
Table 191: 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.20.3.3,
“Reassign Blocks Recovery” on page 255.
3.
Write the LBA that was reassigned.
20.20.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 192: 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 SCSI Hard Disk Drive Specification
254
20.20.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 17.22, “REASSIGN BLOCKS (07)” on page 171, 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.20.1, “Drive Service Strategy” on page 252.
20.20.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.20.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.19, “Command Time out Limits” on
page 250, then service the drive using the service guidelines recommended in Section 20.20.1, “Drive Service
Strategy” on page 252. 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.20.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.20.4.3, “Recovered Drive Error” on page 256.
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.20.4.3, “Recovered Drive Error” on page 256.
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.20.1, “Drive Service Strategy” on page 252.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
255
20.20.4.3 Recovered Drive Error
The Initiator should log the error as soft with the recovery level.
20.20.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.20.1, “Drive Service Strategy” on page 252.
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.20.1, “Drive Service Strategy”
on page 252.
20.20.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.20.1, “Drive Service Strategy” on page 252.
20.20.4.6 Degraded Mode
Refer to Section 20.1.9, “Degraded Mode” on page 232, 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.19, “Command Time out Limits”
on page 250, service the drive using the service guideline recommended in Section 20.20.1, “Drive Service Strategy”
on page 252.
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.20.1, “Drive Service
Strategy” on page 252.
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.20.1, “Drive Service
Strategy” on page 252.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
256
- 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.20.1, “Drive Service Strategy” on page 252, 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.20.1, “Drive Service Strategy” on page 252.
If the above defined recovery procedures fail to clear the degraded mode condition, the Drive should be replaced. Follow the
procedure in Section 20.20.1, “Drive Service Strategy” on page 252, when replacing the drive.
20.20.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 duplicate copies of all data. A data
error must occur in both copies of the data record before the Drive considers a reserved area read error. When this happens, the
integrity of the drive is questionable.
Service the Drive using Section 20.20.1, “Drive Service Strategy” on page 252.
20.20.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.20.1, “Drive Service Strategy” on page 252.
• Other, follow the recommendations for the error condition reported.
20.20.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 SCSI Hard Disk Drive Specification
257
- 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.20.1,
“Drive Service Strategy” on page 252.
•
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.20.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, Bus reset, a Target Reset message, Transceiver Mode
Changed reset, 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 17.6, “LOG SELECT (4C)” on page 78). 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 17.35, “SET DEVICE IDENTIFIER (A4)” on page 190) A Unit Attention Condition is reported to all initiators excluding the initiator that issued the Set Device Identifier command.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
258
20.20.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.20.1, “Drive Service Strategy” on page 252.
20.20.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.20.1, “Drive Service Strategy” on page 252.
- Other, follow the recommendations for the error reported.
20.20.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.20.1, “Drive Service Strategy” on page 252.
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 SCSI Hard Disk Drive Specification
259
20.20.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.20.1, “Drive Service Strategy” on page 252.
- 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.20.1,
“Drive Service Strategy” on page 252.
20.20.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.20.1, “Drive Service Strategy”
on page 252.
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.20.1, “Drive Service Strategy” on page 252.
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.20.1,
“Drive Service Strategy” on page 252.
- 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.20.1,
“Drive Service Strategy” on page 252.
•
Check Condition Status for any other error, follow the recommendations for the returned sense data.
20.20.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.20.1, “Drive Service Strategy” on page 252.
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 SCSI Hard Disk Drive Specification
260
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 193: 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 SCSI Hard Disk Drive Specification
261
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 SCSI Hard Disk Drive Specification
262
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 21.6.5, “Unit Attention Condition” on page 288)
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 SCSI Hard Disk Drive Specification
263
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)
The values in this field vary with products. Please see the individual product specification for more details.
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
264
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.
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
1731 Recovered write fault
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
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
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
265
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
1718 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 asperify 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
1
1C
00
Defect List Format Not Supported
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
266
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
267
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
1427 Servo: Recovered DAC Offset calibration error
1429 Servo: Recovered Load speed error
1712 Recovered ECC error
1716 Recovered overrun
171A Recovered ECC overrun
171C Recovered DRAM CRC error
171E Recovered ID Parity error
173F Recovered channel error
1762 Recovered data with PPM or precomp load
1764 Recovered data with TA (Thermal Asperity) detection
1766 Recovered data with SMM or VM or DDF
1768 Recovered data with pre-PPM or FH (Fly Height) detection
176A Recovered data with write or pre-TA detection
176C Recovered data with pre-SMM or VM or STM or DDF
176E Recovered data with NRZ parity error
1770 Recovered parity PP correction or STW
177E Recovered AE thermal asperity found
1780 Recovered AE open MR element error
1782 Recovered AE IC over temperature error
1784 Recovered AE IP clock count error
1786 Recovered AE high MR current error
1788 Recovered AE write data BLS error
178A Recovered AE invalid head address error
178C Recovered AE power supply error
178E Recovered AE open write head error
1790 Recovered AE write transition error
1792 Recovered AE no write head current error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
268
1798 Recovered ID not found error
179A Recovered Channel Pre-TA error
179C Recovered Channel write or NRZ parity error
1
5D
xx
Predictive Failure Analysis Threshold Reached
xA00 SMART: Power on hour warning
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
xAFF SMART: Test warning
1
81
00
Vendor Unique - Internal Logic Error
1601 Channel/AE internal logic error
1759 Unknown recovered 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
F0
Vendor Unique - Logical Unit Not Ready
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
2
35
02
Enclosure Services Not Available
1508 Enclosure services not available (FC-AL only)
Sense Key = Medium Error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
269
3
03
00
Medium Error - Write Fault
F732 Unrecovered 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
F75A Unknown unrecovered error
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 SCSI Hard Disk Drive Specification
270
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
F75B Too many sectors
Sense Key = Hardware Error
4
02
00
No Seek Complete
F41C Servo: Unrecovered No seek complete
F42C Servo: Unrecovered RRO Calibration timeout
F41E Servo: Unrecovered Seek timeout
F420 Servo: Unrecovered Seek error
4
09
00
Track Following Error
F422 Servo: Unrecovered track following error
F424 Servo: Unrecovered track follow timeout
4
31
00
Medium Format Corrupted - Reassign Failed
F204 Reassign reserved area media error
4
32
00
No Defect Spare Location Available
F205 G-list full - can't reassign any more sectors
F206 No spares available
4
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
1550 ESI: transfer failed - write ack
1551 ESI: transfer failed - read ack
1552 ESI: transfer failed - write ready
1553 ESI: transfer failed - read ready
1558 ESI: transfer failed - EDV
4
35
04
Enclosure Services Failure - Enclosure Services Refused
1554 ESI: transfer refused - write ack
1555 ESI: transfer refused - read ack
1556 ESI: transfer refused - write ready
1557 ESI: transfer refused - read ready
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
271
4
35
80
Enclosure Services Failure - Vendor Unique
F53C SES timeout
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
272
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
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
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
273
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
F43A Servo: Unrecovered Valid Cylinder error
F43C Servo: Unrecovered ADC Saturation error
F43E Servo: Unrecovered Latch Break timeout
F603 Channel/AE target failure
F604 Channel/AE calibration error
F713 Unrecovered ECC error
F717 Unrecovered overrun
F71B Unrecovered ECC overrun
F71D Unrecovered DRAM CRC error
F71F Unrecovered ID Parity error
F740 Unrecovered channel error
F763 Unrecovered data with PPM or precomp load
F765 Unrecovered data with TA detection
F767 Unrecovered data with SMM or VM or DDF
F769 Unrecovered data with pre-PPM or FH detection
F76B Unrecovered data with write or pre-TA detection
F76D Unrecovered data with pre-SMM or VM or STM or DDF
F76F Unrecovered data with NRZ parity error
F771 Unrecovered parity PP correction or STW
F77A Unrecovered Channel SBW timeout
F77B Unrecovered Channel write error timeout
F77F Unrecovered AE thermal asperity found
F781 Unrecovered AE open MR element error
F783 Unrecovered AE IC over temperature error
F785 Unrecovered AE IP clock count error
F787 Unrecovered AE high MR current error
F789 Unrecovered AE write data BLS error
F78B Unrecovered AE invalid head address error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
274
F78D Unrecovered AE power supply error
F78F Unrecovered AE open write head error
F791 Unrecovered AE write transition error
F793 Unrecovered AE no write head current error
F799 Unrecovered ID not found error
F79B Unrecovered Channel Pre-TA error
F79D Unrecovered Channel write or NRZ parity error
FCxx Unable to read RID or FID number xx
4
44
F2
Vendor Unique - Internal Target Failure
F134 Head Health Check data compare error
4
44
0B
Vendor Unique - Internal Target Failure
F30F Motor: High spindle current
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
275
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)
5
55
00
System Buffer Full
1513 System buffer full
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 only)
6
29
03
Unit Attention - Bus Device Reset Occurred
1518 Bus device reset (SCSI only)
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)
6
29
06
Transceiver Changed to LVD
151B Tranceiver changed to LVD (SCSI 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
3F
01
Microcode has been changed
1522 Microcode changed
6
3F
03
Inquiry Parameters Changed
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
276
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
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
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 SCSI Hard Disk Drive Specification
277
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 (FC-AL 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 SCSI Hard Disk Drive Specification
278
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
279
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
280
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 194: 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 SCSI Hard Disk Drive Specification
281
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 195: Actual Retry Count
Bit
Byte
7
15
SKSV
6
3
Secondary Step
17
Actual Retry Count
4
2
1
0
Reserved
16
SKSV
5
ERP Type
Actual Retry Count
Sense-key specific valid
0
Actual Retry Count is not valid.
1
Actual Retry Count is valid.
Number of retry steps used in attempting to recover from the error condition.
The content of these two bytes indicates:
0x04nn - nn recovery steps were used in the 'Minus Mod' branch of the recovery process,
0x02nn - nn recovery steps were used in the 'TA' branch of the recovery process,
0x01nn - nn recovery steps were used in the 'Sync Byte' branch of the recovery process.
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 SCSI Hard Disk Drive Specification
282
Progress indication is returned.
Table 196: Progress Indication
Bit
Byte
7
15
SKSV
16
(MSB)
6
5
4
3
2
1
0
Reserved
Progress Indication
17
(LSB)
SKSV
Sense-key specific valid
Progress Indication
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.
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 high and low bytes, respectively of the sector number.
If the head is undetermined, bytes 24, 25, and 26 are set to 0FFFFFFh. If the head number is undetermined, byte 27 is
set to 0FFh. If cylinder, head, and sector have no relevance the error, bytes 24 through 29 will all be set to
0FFFFFFFFFFFFh for Valid = 0 and ILI = 0. This Physical Error Record field is valid for Sense Key 1, 3, and 4 only.
Valid
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 SCSI Hard Disk Drive Specification
283
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
284
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 261. 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. Unit Error Codes
list.
Table 197: Unit Error Codes list
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 SCSI Hard Disk Drive Specification
285
UEC
Description
F11A
F11B
F11C
F11D
F11E
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
Not Used
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
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
286
UEC
Description
F306
1307
F308
1309
F30A
130B
F30C
130D
F30E
Motor: Unrecovered No feedback detected error
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
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
141D
F41E
141F
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
Servo: Recovered Seek timeout
Servo: Unrecovered Seek timeout
Servo: Recovered Seek error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
287
UEC
Description
F420
1421
F422
1423
F424
1425
F426
1427
F428
1429
F42A
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
1501
1502
1503
1504
1505
1506
1507
1508
1509
150A
150B
150C
150D
150E
150F
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
151A
151B
151C
151D
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
Enclosure services not available (FC-AL only)
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 only)
Bus device reset (SCSI only)
Self initiated reset
Tranceiver changed to single-ended (SCSI only)
Tranceiver changed to LVD (SCSI only)
Mode parameters changed
Log parameters changed
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
288
UEC
151E
151F
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
152A
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
Description
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)
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
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)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
289
UEC
Description
1550
1551
1552
1553
1554
1555
1556
1557
1558
ESI: transfer failed - write ack
ESI: transfer failed - read ack
ESI: transfer failed - write ready
ESI: transfer failed - read ready
ESI: transfer refused - write ack
ESI: transfer refused - read ack
ESI: transfer refused - write ready
ESI: transfer refused - read ready
ESI: transfer failed - EDV
1601
F602
F603
F604
Channel/AE internal logic error
Channel/AE hard logic error
Channel/AE target failure
Channel/AE calibration error
F701
F702
1703
1704
E705
E706
E707
E708
1709
E70A
E70B
E70C
E70D
E70E
E70F
D710
E711
1712
F713
1714
F715
1716
F717
1718
F719
171A
Format corrupted
Format command failed
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
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
290
UEC
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
1735
F736
1737
F738
1739
F73A
173B
F73C
173D
F73E
173F
F740
1741
F742
1743
F744
Description
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 servo write abort
Unrecovered servo write abort
Recovered post write abort
Unrecovered post write abort
Recovered Post PES check write abort
Unrecovered Post PES check write abort
Recovered data address mark error
Unrecovered data address mark error
Recovered sector miss
Unrecovered sector miss
Recovered channel error
Unrecovered channel error
Recovered write parity error
Unrecovered write parity error
Recovered media error
Unrecovered media error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
291
UEC
1745
1746
1747
1748
1749
F74A
F74B
F74C
F74D
F74E
F74F
F750
F751
F752
F753
F754
F755
F756
F757
F758
1759
F75A
F75B
F75C
F75D
F75E
F75F
F760
F761
1762
F763
1764
F765
1766
F767
1768
F769
176A
F76B
176C
F76D
Description
Defect list not found
Defect list format not supported
Primary defect list not found
Grown defect list not found
Partial defect list transferred
Defect list error
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
SAT: No buffer overflow
SAT:buffer overflow
Read/write command timeout
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
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
292
UEC
176E
F76F
1770
F771
F772
F773
F774
F775
F776
F777
F77A
F77B
177C
F77D
177E
F77F
1780
F781
1782
F783
1784
F785
1786
F787
1788
F789
178A
F78B
178C
F78D
178E
F78F
1790
F791
1792
F793
1794
F795
1798
F799
179A
Description
Recovered data with NRZ parity error
Unrecovered data with NRZ parity error
Recovered parity PP correction or STW
Unrecovered parity PP correction or STW
DASH starting timeout
ID table timeout
Servo timeout
Buffers timeout
DASH done timeout
DASH unknown timeout
Unrecovered channel SBW timeout
Unrecovered channelwrite error timeout
Not Used
Recovery timeout
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
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 ECC error timeout
Unrecovered ECC error timeout
Recovered ID not found error
Unrecovered ID not found error
Recovered Channel Pre-TA error
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
293
UEC
Description
F79B
179C
F79D
F79E
F79F
F7A0
F7A1
F7A2
F7A5
F7B1
17B2
F7B3
Unrecovered Channel Pre-TA error
Recovered Channel write or NRZ parity error
Unrecovered Channel write or NRZ parity 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
1A02
2A02
3A02
1A14
2A14
3A14
1A32
2A32
3A32
1A43
2A43
3A43
1A4A
2A4A
3A4A
1A50
2A50
3A50
1A56
2A56
3A56
1A5B
2A5B
3A5B
1AFF
2AFF
3AFF
SMART: Temperature warning (no sense)
SMART: Temperature warning (recovered sense)
SMART: Temperature 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)
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: Test warning (no sense)
SMART: Test warning (recovered sense)
SMART: Test warning (unit attn sense)
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
294
UEC
FCxx
Description
Unable to read RID or FID number xx
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
295
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
296
Index
A
Abbreviations ..............................................................................61
Acoustics .....................................................................................51
Active Notch ...............................................................................130
Actuator ......................................................................................5
Additional information ...............................................................227
Additional Sense Length (Byte 7) ..............................................264
Alternate Sectors per Zone .........................................................121
Alternate Tracks per Logical Unit ..............................................121
Alternate Tracks per Zone ..........................................................121
Appendix .....................................................................................285
Automatic Read Reallocation Enabled .......................................114
Automatic Rewrite/Reallocate ....................................................242
Automatic Write Reallocation Enabled ......................................114
Auxiliary connector on 68-pin model .........................................25
Average latency ..........................................................................12
B
Block Descriptor .........................................................................109
block format ................................................................................65
Breather hole ...............................................................................48
buffer overrun .............................................................................99
buffer underrun ...........................................................................99
bytes from index format ..............................................................66
C
Command Processing During Execution of Active I/O process .228
Command Processing During Startup and Format Operations ...231
Command processing while reserved .........................................239
Command Queuing .....................................................................240
Command queuing ......................................................................240
Command reordering ..................................................................241
Command Time out Limits .........................................................250
Concurrent I/O Process ...............................................................241
Contingent Allegiance Condition ...............................................245
Control Electronics .....................................................................5
Cooling requirements ..................................................................33
Corrosion test ..............................................................................32
Cylinder allocation ......................................................................10
D
Data Error Logging .....................................................................254
Data Integrity ..............................................................................17
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
297
data phase save data pointer (DPSDP) .......................................112
Data reliability ............................................................................41
Data sheet ....................................................................................7
Data transfer speed ......................................................................13
DC power requirements ..............................................................35
defect descriptor ..........................................................................65
defect list .....................................................................................64
Deferred Error Condition ............................................................231
Degraded Mode ...........................................................................232, 256
device cache fast writes ..............................................................100
device cache partial read hits ......................................................100
device cache write hits ................................................................100
Diagnostics ..................................................................................246
Disable Block Descriptor ............................................................105
Download Microcode and Save (Mode 0101b) ..........................202
Drive characteristics ...................................................................7
Drive mounting ...........................................................................48
Drive ready time .........................................................................13
E
Electrical interface specification .................................................21
Electromagnetic Compatibility ...................................................57
enclosure services .......................................................................244
Environment ................................................................................31
Equipment errors .........................................................................41
Error Recovery Procedure ..........................................................17
F
Failure prediction (PFA/S.M.A.R.T) ..........................................41
Fixed-disk Subsystem Description .............................................5
format unit ...................................................................................62
Formatted capacity ......................................................................7
Full stroke seek time ...................................................................11
G
General ........................................................................................1
Glossary ......................................................................................1
Grown Defect List (Glist) ...........................................................164
H
Head Disk Assembly ..................................................................5
Head Offset Count ......................................................................115
Heads unload and actuator lock ..................................................48
I
Identification ...............................................................................53
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
298
Idle Time Function ......................................................................250
Incorrect Initiator Connection .....................................................228
Incorrect Length Indicator (Bit 5 of byte 2) ...............................262
inquiry .........................................................................................68
Interface connector .....................................................................45
Internal Error Condition ..............................................................231
Invalid LUN in Identify Message ...............................................227
J
Jumper signal Description on 68 pin Jumper Block ...................29
L
Labels ..........................................................................................53
Log Page Parameters ..................................................................82
LOG SELECT (4C) ....................................................................78
LOG SENSE (4D) ......................................................................81
Logical Block Cache Segment Size ............................................126
M
Maximum Burst Size ..................................................................120
Maximum Pre-fetch ....................................................................126
Maximum Pre-fetch Ceiling .......................................................126
Mechanical dimensions ...............................................................44
Mechanical positioning ...............................................................11
Mechanical specifications ...........................................................43
Merge G-List into P-List .............................................................111
Minimum Pre-fetch .....................................................................126
MODE SELECT (15) .................................................................103
MODE SELECT (55) .................................................................104
MODE SENSE (1A) ...................................................................105
MODE SENSE (5A) ...................................................................141
Mounting positions and tappings ................................................46
Multiple Initiator Environment ...................................................245
multiple initiator systems ............................................................244
N
Non-arbitrating systems ..............................................................244
Non-operating shock ...................................................................50
O
Operating conditions ...................................................................31
Operating shock ..........................................................................49
Operating vibration .....................................................................49
Option jumper block ...................................................................26
Outline ........................................................................................43
Outline of the drive .....................................................................3
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
299
overrun counter ...........................................................................100
P
Packaging ....................................................................................32
Page Code Valid .........................................................................173
Page Format ................................................................................186
Parameter data for Read Keys ....................................................144
Parameter data for Read Reservations ........................................145
Performance characteristics ........................................................10
Persistent Reservation .................................................................143
PERSISTENT RESERVE IN (5E) .............................................143
PERSISTENT RESERVE OUT (5F) .........................................147
Persistent Reserve Out Parameter list .........................................153
Physical format ...........................................................................19
physical sector format .................................................................67
Physical Sector Format (101b) ...................................................167
Post Error ....................................................................................115
Power connector .........................................................................21
Power consumption efficiency index ..........................................39
Power supply current, average, and peak ....................................36
Predictive Failure Analysis .........................................................260
Preventive maintenance ..............................................................41
Primary Defect List .....................................................................164
Priority Commands .....................................................................239
Priority commands ......................................................................239
R
Random access ............................................................................15
Random vibration .......................................................................49
READ (10) - (28) ........................................................................157
Read Ahead .................................................................................244
READ BUFFER (3C) .................................................................158
Read Buffer Full Ratio ................................................................119
Read Cache Disable ....................................................................126
READ CAPACITY command ....................................................162
Read Continuous .........................................................................114
READ DEFECT DATA (37) ......................................................164
READ DEFECT DATA (B7) .....................................................168
READ LONG command .............................................................170
Read Retry Count ........................................................................115
REASSIGN BLOCKS (07) ........................................................171
Reassigned format (Glist) ...........................................................19
RECEIVE DIAGNOSTICS (1C) ................................................173
Recommended Initiator ERP ......................................................252
RELEASE (17) ...........................................................................175
RELEASE (57) ...........................................................................176
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
300
Reliability ....................................................................................41
REPORT LUNS (A0) .................................................................179
Report Recovered Non Data Errors ............................................112
REQUEST SENSE (03) ..............................................................180
Reselection Timeout ...................................................................244
RESERVE (16) ...........................................................................181
RESERVE (56) ...........................................................................182
Reserved Area .............................................................................174
Reset ............................................................................................245
Reset condition ...........................................................................245
REZERO UNIT (01) ...................................................................183
Ripple voltage .............................................................................38
S
Safety ..........................................................................................55
SCSI bus connector .....................................................................22
SCSI Command Set ....................................................................59
SCSI Control Byte ......................................................................61
SCSI Message System ................................................................209
SCSI Protocol .............................................................................227
SCSI Sense Data .........................................................................261
SCSI Sense Data Format .............................................................261
SCSI Status Byte .........................................................................207
SCSI Status Byte Reporting ........................................................227
Sectors per Track ........................................................................122
SEEK (10) - (2B) ........................................................................185
SEEK (6) - (0B) ..........................................................................184
seek counter ................................................................................99
Seek errors ..................................................................................41
seeks ............................................................................................99
Segmented Caching ....................................................................244
Selection without ATN ...............................................................245
SEND DIAGNOSTIC (1D) ........................................................186
sense data ....................................................................................244
Sense Data Description ...............................................................262
Sense Key (Bit 3 - 0 of byte 2) ...................................................263
Service Action .............................................................................143, 148
Shipped format (Plist) .................................................................19
Shipping conditions ....................................................................31
Single Initiator Selection ............................................................244
Size Enable .................................................................................125
Sound power levels .....................................................................51
Spindle stop time ........................................................................13
START STOP UNIT (1B) ..........................................................191
Start/stop cycles ..........................................................................41
Storage requirements ..................................................................32
Hitachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
301
Storage time ................................................................................32
Supported Messages ...................................................................210
Supported messages ....................................................................210
SYNCHRONIZE CACHE (35) ..................................................192
T
Tagged Queuing ..........................................................................240
Temperature and humidity ..........................................................31
Temperature Threshold ...............................................................112
Temperature warning ..................................................................41
TEST UNIT READY (00) ..........................................................193
Throughput ..................................................................................14
Track Skew Factor ......................................................................122
Tracks per Zone ..........................................................................122
Transfer Block ............................................................................114
U
UEC list .......................................................................................285
UL and CSA standard conformity ..............................................55
underrun counter .........................................................................100
Unit Attention Condition ............................................................258
unit attention condition ...............................................................230
Untagged Queuing ......................................................................240
V
Verify ..........................................................................................260
VERIFY (2F) ..............................................................................194
Verify Correction Span ...............................................................124
Vibration and shock ....................................................................49
W
WRITE (10) - (2A) .....................................................................197
WRITE (6) - (0A) .......................................................................196
WRITE AND VERIFY (2E) .......................................................198, 200
WRITE BUFFER (3B) ...............................................................200
Write Buffer Empty Ratio ...........................................................119
Write Cache ................................................................................241
Write Cache Enable ....................................................................126
WRITE LONG (3F) ....................................................................204
Write Retention Priority ..............................................................126
Write Retry Count .......................................................................115
WRITE SAME (41) ....................................................................205
Z
zero seeks ....................................................................................99
HItachi Ultrastar 15K147 SCSI Hard Disk Drive Specification
302
© 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 Travelstar™ 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