Ultrastar 15K147 (FC-AL) Specification v3.0
Hard Disk Drive Specification
Ultrastar 15K147
3.5 inch FC-AL Hard Disk Drive
Models:
HUS151414VLF200
HUS151473VLF200
HUS151436VLF200
Version 3.0
25 May 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 FC-AL Hard Disk Drive Specification
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Hard Disk Drive Specification
Ultrastar 15K147
3.5 inch FC-AL Hard Disk Drive
Models:
HUS151414VLF200
HUS151473VLF200
HUS151436VLF200
Version 3.0
25 May 2006
Warning: Printed copies of this document are considered current only on the date of print. Replacement and disposal
of down-level versions is the responsibility of the document holder.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
1st Edition (Rev. 1.0) (23 March 2004) DRAFT
2nd Edition (Rev. 2.0) (30 September 2004) RELEASE
3rd Edition (Rev. 3.0) (25 May 2006) RELEASE
The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent
with local law: HITACHI GLOBAL STORAGE TECHNOLOGIES PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer or express or implied warranties in certain transactions, therefore, this statement
may not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Hitachi may make improvements or changes
in any products or programs described in this publication at any time.
It is possible that this publication may contain reference to, or information about, Hitachi products (machines and programs),
programming, or services that are not announced in your country. Such references or information must not be construed to
mean that Hitachi intends to announce such Hitachi products, programming, or services in your country.
Technical information about this product is available by contacting your local Hitachi Global Storage Technologies representative or on the Internet at http://www.hgst.com
Hitachi Global Storage Technologies may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents.
©Copyright Hitachi Global Storage Technologies
Note to U.S. Government Users —Documentation related to restricted rights —Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with Hitachi Global Storage Technologies.
Hitachi Ultrastar 15K147 FC-AL 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 World Wide 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 Throughput....................................................................14
5.0 Data Integrity .............................................................................17
5.1 Equipment Status ...................................................................17
5.2 Error Recovery Procedure .....................................................17
6.0 Physical Format .........................................................................19
6.1 Shipped Format (P-List) ........................................................19
6.2 Reassigned Format (G-List)...................................................19
7.0 Electrical Interface ....................................................................21
7.1 FC-AL Connector ..................................................................21
7.1.1 40 pin SCA-2 SFF-8045 FC-AL Connector Definition21
7.1.2 Voltage and Ground Signals .........................................22
7.1.3 Fault LED Out ..............................................................22
7.1.4 Ready LED Out ............................................................22
7.1.5 Start Mated Controls .....................................................23
7.1.6 SEL_n and Enclosure Service Signals..........................23
7.1.7 –ENBL_BYP CH1, -ENBL_BYP_CH2......................25
7.1.8 –Drive Present..............................................................25
7.1.9 Dev_Ctrl_Code_x .........................................................25
8.0 Environment...............................................................................27
8.1 Temperature and humidity.....................................................27
8.2 Storage requirements .............................................................28
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
8.2.1 Packaging......................................................................28
8.2.2 Storage time ..................................................................28
8.3 Corrosion test .........................................................................28
8.4 Cooling requirements.............................................................29
9.0 DC Power Requirements...........................................................31
9.1 Power Supply Current, Average and Peak.............................32
9.2 Ripple Voltage .......................................................................33
9.3 Power Consumption Efficiency Index ...................................34
10.0 Reliability..................................................................................35
10.1 Start/Stop Cycles..................................................................35
10.2 Data Reliability ....................................................................35
10.3 Seek errors ...........................................................................35
10.4 Failure prediction (PFA/S.M.A.R.T) ...................................35
10.5 Preventive Maintenance.......................................................35
10.6 Temperature Warning ..........................................................35
11.0 Mechanical Specifications .......................................................37
11.1 Outline .................................................................................37
11.2 Mechanical Dimensions.......................................................37
11.3 Interface Connector..............................................................39
11.4 Mounting Positions and Tappings .......................................40
11.5 Drive Mounting....................................................................41
11.6 Heads Unload and Actuator Lock........................................41
11.7 Breather Hole .......................................................................41
12.0 Vibration and Shock ................................................................43
12.1 Operating Vibration .............................................................43
12.1.1 Random Vibration.......................................................43
12.1.2 Swept Sine Vibration .................................................43
12.2 Non-operating Vibration......................................................43
12.2.1 Random Vibration......................................................43
12.2.2 Swept Sine Vibration .................................................43
12.3 Operating shock ..................................................................43
12.4 Non-operating shock...........................................................44
12.4.1 Half sinewave shock pulse..........................................44
12.4.2 Rotational shock ........................................................44
13.0 Acoustics ...................................................................................45
13.1 Sound power levels ..............................................................45
14.0 Identification ............................................................................47
14.1 Labels...................................................................................47
15.0 Electromagnetic Compatibility...............................................49
16.0 Standards ..................................................................................51
16.1 UL and CSA Standard Conformity......................................51
16.2 European Standards Compliance .........................................51
16.3 German Safety Mark............................................................51
16.4 Flammability ........................................................................51
16.5 Corporate Standards Compliance ........................................51
17.0 FC-AL attachment ...................................................................53
Hitachi Ultrastar 15K147 F-CAL Hard Disk Drive Specification
17.1 Fundamentals .......................................................................53
17.1.1 Node and Port names ..................................................54
17.1.2 NL_Port address .........................................................54
17.1.3 Primitive signals and sequences .................................55
17.1.4 Frames........................................................................56
17.1.5 Sequences....................................................................56
17.1.6 Exchanges ...................................................................57
17.2 Basic Link Services .............................................................57
17.2.1 Abort sequence (ABTS).............................................57
17.2.2 Basic accept (BA_ACC) .............................................58
17.2.3 Basic reject (BA_RJT)................................................59
17.3 Extended Link Services .......................................................60
17.3.1 Link Service Accept (LS_ACC) ................................61
17.3.2 Link Service Reject (LS_RJT)...................................62
17.3.3 Port Login (PLOGI)...................................................63
17.3.4 Logout (LOGO) .........................................................71
17.3.5 Fabric Login (FLOGI) ...............................................72
17.3.6 Fabric Address Notification (FAN) ...........................76
17.3.7 Port Discovery (PDISC) ............................................77
17.3.8 Address Discovery (ADISC) .....................................77
17.3.9 Process Login (PRLI) ................................................78
17.3.10 Process Logout (PRLO)...........................................82
17.3.11 Read Link Error Status Block (RLS) .......................84
17.3.12 Report Node Capabilities (RNC) .............................86
17.3.13 Re-instate Recovery Qualifiers (RRQ) ....................90
17.3.14 Third Party Process Logout (TPRLO) .....................91
17.3.15 Request Node Identification Data (RNID) ...............93
17.4 Common Fibre Channel Services ........................................97
17.4.1 Register FC-4 Types (RFT_ID) ..................................99
17.5 FC-AL timers .......................................................................101
17.5.1 Link Failure.................................................................102
17.6 Invalid frame delimiter ........................................................102
18.0 SCSI-FCP .................................................................................103
18.1 Terminology.........................................................................103
18.2 Information Units.................................................................104
18.2.1 FCP_CMND ...............................................................105
18.2.2 FCP_XFER_RDY.......................................................107
18.2.3 FCP_DATA ................................................................107
18.2.4 FCP_RSP ....................................................................107
18.3 Task Attributes.....................................................................109
18.4 Task Management functions ................................................110
18.4.1 Abort Task (Implemented as ABTS BLS).................111
18.4.2 Abort Task Set ............................................................111
18.4.3 Terminate Task ...........................................................112
18.4.4 Clear ACA ..................................................................112
18.4.5 Target Reset ................................................................112
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
18.4.6 Clear Task Set .............................................................112
18.4.7 Reset LUN ..................................................................112
18.5 Miscellaneous ......................................................................112
18.5.1 Tags.............................................................................112
18.5.2 Auto-Contingent Allegiance (ACA) ...........................112
18.5.3 Autosense...................................................................113
19.0 SCSI Command Set .................................................................115
19.1 SCSI Control Byte ...............................................................117
19.2 Abbreviations.......................................................................117
19.3 Byte ordering conventions ...................................................117
19.4 FORMAT UNIT (04)...........................................................118
19.4.1 Defect list ....................................................................120
19.4.2 Defect Descriptor ........................................................121
19.5 INQUIRY (12) .....................................................................124
19.5.1 Inquiry Data ................................................................125
19.6 LOG SELECT (4C) .............................................................134
19.7 LOG SENSE (4D) ...............................................................137
19.7.1 Log Page parameters...................................................138
19.7.2 Log Sense Page 0 ........................................................139
19.7.3 Log Sense Page 2 ........................................................140
19.7.4 Log Sense Page 3 ........................................................142
19.7.5 Log Sense Page 5 ........................................................144
19.7.6 Log Sense Page 6 ........................................................146
19.7.7 Log Sense Page D .......................................................147
19.7.8 Log Sense Page E .......................................................148
19.7.9 Log Sense Page F........................................................149
19.7.10 Log Sense Page 10 ....................................................150
19.7.11 Log Sense Page 2F....................................................153
19.7.12 Log Sense Page 30 ....................................................154
19.7.13 Log Sense Page 37 ....................................................157
19.8 MODE SELECT (15) ..........................................................159
19.9 MODE SELECT (55) ..........................................................160
19.10 MODE SENSE (1A) ..........................................................161
19.10.1 Mode Parameter List.................................................162
19.10.2 Mode Page 00 (Vendor Unique Parameters) ............166
19.10.3 Mode Page 01 (Read/Write Error Recovery Parameters)168
19.10.4 Mode Page 02 (Disconnect/Reconnect Parameters) .173
19.10.5 Mode Page 03 (Format Device Parameters) .............174
19.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters)176
19.10.7 Mode Page 07 (Verify Error Recovery Parameters).177
19.10.8 Mode Page 08 (Caching Parameters)........................178
19.10.9 Mode Page 0A (Control Mode Page Parameters).....180
19.10.10 Mode Page 0C (Notch Parameters) ........................182
19.10.11 Mode Page 19h (Fibre Channel Port Control Page)184
19.10.12 Mode Page 1A (Power Control) .............................186
19.10.13 Mode Page 1C (Informational Exceptions Control)187
Hitachi Ultrastar 15K147 F-CAL Hard Disk Drive Specification
19.11 MODE SENSE (5A) ..........................................................189
19.12 PERSISTENT RESERVE IN (5E) ....................................191
19.12.1 Service Action...........................................................191
19.12.2 Parameter data for Read Keys ..................................192
19.12.3 Parameter Data for Read Reservations .....................193
19.13 PERSISTENT RESERVE OUT (5F) ................................195
19.13.1 Service Action...........................................................196
19.13.2 Scope.........................................................................198
19.13.3 Type ..........................................................................198
19.13.4 Parameter list ............................................................200
19.13.5 Summary ...................................................................200
19.14 PRE-FETCH (34) ..............................................................202
19.15 READ (6) - (08) .................................................................203
19.16 READ (10) - (28) ...............................................................204
19.17 READ BUFFER (3C) ........................................................205
19.17.1 Combined Header And Data (Mode 00000b)...........206
19.17.2 Read Data (Mode 00010b)........................................206
19.17.3 Descriptor (Mode 00011b)........................................207
19.17.4 Read Data from Echo Buffer (Mode 01010b) ..........208
19.17.5 Echo Buffer Descriptor (Mode 01011b) ...................208
19.17.6 Enable Expander Communications Protocol and Echo Buffer (Mode 11010b)208
19.18 READ CAPACITY (25) ....................................................209
19.19 READ DEFECT DATA (37).............................................211
19.19.1 Defect List Header ....................................................213
19.19.2 Defect List Descriptor...............................................213
19.19.3 Bytes from Index Format (100b) ..............................214
19.19.4 Physical Sector Format (101b) .................................214
19.20 READ DEFECT DATA (B7) ............................................215
19.20.1 Defect List Header ....................................................215
19.20.2 Defect List Descriptor...............................................216
19.20.3 Bytes from Index Format (100b) ..............................216
19.20.4 Physical Sector Format (101b) .................................216
19.21 READ LONG (3E) ............................................................217
19.22 REASSIGN BLOCKS (07) ...............................................218
19.23 RECEIVE DIAGNOSTICS RESULTS (1C) ....................220
19.23.1 Receive Diagnostic Results Page 0...........................221
19.23.2 Enclosure Service Information (ESI) Page Format ..222
19.23.3 Receive Diagnostic Results Page 40.........................223
19.23.4 Receive Diagnostic Page A0h...................................225
19.24 RELEASE (17) ..................................................................226
19.25 RELEASE (57) ..................................................................227
19.26 REPORT DEVICE IDENTIFIER (A3) .............................228
19.27 REPORT LUNS (A0) ........................................................230
19.28 REQUEST SENSE (03).....................................................231
19.29 RESERVE (16) ..................................................................232
19.30 RESERVE (56) ..................................................................233
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
19.31 REZERO UNIT (01)..........................................................234
19.32 SEEK (6) - (0B) .................................................................235
19.33 SEEK (10) - (2B) ...............................................................235
19.34 SEND DIAGNOSTIC (1D) ...............................................236
19.34.1 Send Diagnostic Page 0 ............................................238
19.34.2 Send Diagnostic Page 40 ..........................................238
19.34.3 Send Diagnostic Page A0h .......................................239
19.35 SET DEVICE IDENTIFIER (A4) .....................................241
19.36 START STOP UNIT (1B) .................................................242
19.37 SYNCHRONIZE CACHE (35) .........................................243
19.38 TEST UNIT READY (00) .................................................244
19.39 VERIFY (2F) .....................................................................245
19.40 VERIFY (16) - (8F) ...........................................................246
19.41 WRITE (6) - (0A) ..............................................................247
19.42 WRITE (10) - (2A) ............................................................248
19.43 WRITE AND VERIFY (16) - (8E)....................................249
19.44 WRITE AND VERIFY (2E)..............................................250
19.45 WRITE BUFFER (3B) ......................................................251
19.45.1 Combined Header And Data (Mode 00000b)...........251
19.45.2 Write Data (Mode 00010b).......................................252
19.45.3 Download Microcode (Mode 00100b) .....................253
19.45.4 Download Microcode and Save (Mode 00101b) -Single Binary File253
19.45.5 Download Microprocessor Microcode and Save (Mode 00111b) - Multiple Binary
Files................................................................................................................254
19.45.6 Write Data to Echo Buffer (Mode 01010b) ..............254
19.45.7 Enable Expander Communications Protocol (Mode 11010b)254
19.46 WRITE LONG (3F)...........................................................254
19.47 WRITE SAME (41) ...........................................................256
19.48 WRITE SAME (16) - (93) .................................................257
20.0 SCSI Status Byte ......................................................................259
21.0 Additional information............................................................261
21.1 Obtaining an AL_PA ...........................................................261
21.2 Loop Initialization Procedure ..............................................261
21.3 Flow Control ........................................................................263
21.4 Login Requirements.............................................................263
21.5 Public Loop Operation.........................................................264
21.5.1 NL_Port Initialization .................................................265
21.6 SCSI Protocol ......................................................................267
21.6.1 Priority of SCSI Status Byte Reporting ......................267
21.6.2 Invalid LUN Processing..............................................267
21.6.3 Overlapped Commands...............................................267
21.6.4 Command Processing During Execution of Active I/O Process268
21.6.5 Unit Attention Condition ............................................269
21.6.6 Command Processing During Startup and Format Operations271
21.6.7 Internal Error Condition..............................................271
21.6.8 Deferred Error Condition............................................271
Hitachi Ultrastar 15K147 F-CAL Hard Disk Drive Specification
21.6.9 Degraded Mode...........................................................272
21.6.10 Command Processing while Reserved......................279
21.7 Priority Commands ..............................................................279
21.8 Command Queuing ..............................................................280
21.8.1 Queue Depth ...............................................................280
21.8.2 Queue Full Status........................................................280
21.8.3 Effects of LIP on Command Queuing ........................280
21.8.4 Termination of I/O Processes .....................................280
21.9 Command Reordering..........................................................280
21.10 Concurrent I/O Process ......................................................280
21.11 Write Cache .......................................................................281
21.12 Automatic Rewrite/Reallocate ...........................................281
21.13 Segmented Caching ...........................................................283
21.13.1 Overview...................................................................283
21.13.2 Read Ahead...............................................................283
21.14 Multiple Initiator Systems .................................................283
21.14.1 Sense Data.................................................................283
21.14.2 Mode Pages...............................................................283
21.15 Enclosure Services .............................................................283
21.15.1 Enclosure Initiated ESI .............................................284
21.16 Multiple Initiator Environment ..........................................284
21.16.1 Initiator Sense Data...................................................284
21.16.2 Initiator Mode Select/Mode Sense Parameters .........284
21.17 Reset...................................................................................284
21.17.1 Reset Sources ............................................................285
21.17.2 Reset Actions ............................................................285
21.18 Diagnostics.........................................................................285
21.18.1 Power on Diagnostics ...............................................285
21.18.2 Self-test via SEND DIAGNOSTIC Command.........286
21.19 Idle Time Function.............................................................289
21.20 Command Time out Limits ...............................................289
21.20.1 Reassignment Time...................................................289
21.20.2 Format Time .............................................................289
21.20.3 Start/Unit Stop Time .................................................289
21.20.4 Medium Access Command Time .............................290
21.20.5 Time-out Limits for Other Commands .....................290
21.21 Recommended Initiator ERP .............................................291
21.21.1 Drive Service Strategy ..............................................291
21.21.2 Recommendations for System Error Log .................292
21.21.3 Data Recovery Procedure .........................................292
21.21.4 Nondata Error Recovery Procedure ..........................294
22.0 SCSI Sense Data.......................................................................301
22.1 SCSI Sense Data Format......................................................301
22.2 Sense Data Description ........................................................302
22.2.1 Valid (Bit 7 of byte 0).................................................302
22.2.2 Error Code (Bit 6 - 0 of byte 0) ..................................302
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
22.2.3 ILI: Incorrect Length Indicator (Bit 5 of byte 2) ........302
22.2.4 Sense Key (Bit 3 - 0 of byte 2) ...................................303
22.2.5 Information Bytes (Byte 3 through 6).........................304
22.2.6 Additional Sense Length (Byte 7) ..............................304
22.2.7 Command Specific Information (Byte 8 through 11) .304
22.2.8 Additional Sense Code/Qualifier (Byte 12 and 13) ....305
22.2.9 RU: Field Replaceable Unit (Byte 14).......................319
22.2.10 Sense Key Specific (Byte 15 through 17).................319
22.2.11 Reserved (Byte 18 through 19) .................................322
22.2.12 Vendor unique error information (Byte 20 through 23)322
22.2.13 Physical Error Record (Byte 24 thru 29) ..................322
22.2.14 Reserved (Byte 30 through 31) .................................322
23.0 Appendix. UEC list .................................................................323
Hitachi Ultrastar 15K147 F-CAL 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 World Wide 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.Cylinder skew ...............................................................................................12
Table 9.Head skew.....................................................................................................12
Table 10.Latency time ...............................................................................................12
Table 11.Drive ready time .........................................................................................13
Table 12.Spindle stop time ........................................................................................13
Table 13.Data transfer speed (sector size 512 Byte case)..........................................13
Table 14.Simple sequential access performance (sector size 512 Byte case)............14
Table 15.Random access performance (sector size 512 Byte case)...........................15
Table 16.Operating and non-operating conditions ....................................................27
Table 17.Maximum allowable module surface temperatures ....................................29
Table 18.Input Voltage ..............................................................................................31
Table 19.Model 147 GB ............................................................................................32
Table 20.Model 147GB: 5V Current during spinup ..................................................32
Table 21.Model 73 GB ..............................................................................................33
Table 22.Model 36 GB ..............................................................................................33
Table 23.Power Supply Generated Ripple at Drive Power Connector......................33
Table 24.Power Consumption Efficiency Index........................................................34
Table 25.Physical Dimensions...................................................................................37
Table 26.A-weighted sound power levels..................................................................45
Table 27.IEEE Registered Name format ...................................................................54
Table 28.NL_Port address .........................................................................................54
Table 29.General frame format..................................................................................56
Table 30.Frame header ..............................................................................................56
Table 31.Basic link service command codes .............................................................57
Table 32.BA_ACC Payload.......................................................................................58
Table 33. BA_RJT Payload .......................................................................................59
Table 34.BA_RJT Reason Codes ..............................................................................59
Table 35.BA_RJT Reason Code Explanations ..........................................................59
Table 36.Extended Link Service replies ....................................................................60
Table 37.Extended Link Service requests..................................................................60
Table 38.Extended Link Service request 11h qualifiers ............................................61
Table 39.LS_RJT payload .........................................................................................62
Table 40.LS_RJT reason codes .................................................................................62
Table 41.LS_RJT reason code explanations..............................................................63
Table 42.PLOGI_REQ/PLOGI_ACC payload..........................................................64
Table 43.Common Service Parameter applicability (part 1 of 2) ..............................65
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Table 44.Common Service Parameter applicability (part 2 of 2) ..............................66
Table 45.FC-PH Version ...........................................................................................66
Table 46.Class Service Parameters ............................................................................68
Table 47.LOGO payload............................................................................................71
Table 48.LOGO ACC payload ..................................................................................71
Table 49.FLOGI_REQ/FLOGI_ACC payload .........................................................72
Table 50.Common Service Parameters (FLOGI_REQ/FLOGI_ACC) .....................73
Table 51.Class Service Parameters ............................................................................75
Table 52.FAN payload...............................................................................................76
Table 53.ADISC payload...........................................................................................77
Table 54.ADISC ACC payload .................................................................................78
Table 55.PRLI payload ..............................................................................................78
Table 56.PRLI ACC payload.....................................................................................79
Table 57.Login Service Parameter page ....................................................................79
Table 58.Login Response Service Parameter page....................................................81
Table 59.PRLI/PRLO ACC response codes ..............................................................82
Table 60.PRLO payload ............................................................................................82
Table 61.PRLO ACC payload ...................................................................................83
Table 62.Logout Service Parameter page ..................................................................83
Table 63.Logout Response Service Parameter page..................................................84
Table 64.RLS payload ...............................................................................................85
Table 65.RLS ACC payload ......................................................................................85
Table 66.Link Error Status block...............................................................................85
Table 67.RNC/ACC payload .....................................................................................86
Table 68.RNC Capability Entry.................................................................................87
Table 69.Document Identifiers ..................................................................................89
Table 70.RRQ payload ..............................................................................................90
Table 71.RRQ ACC payload .....................................................................................90
Table 72.TPRLO payload ..........................................................................................91
Table 73.TPRLO ACC payload.................................................................................91
Table 74.Logout Service Parameter page ..................................................................91
Table 75.Logout Response Service Parameter page..................................................92
Table 76.RNID payload .............................................................................................93
Table 77.RNID accept payload..................................................................................94
Table 78.Common Node Identification Data.............................................................94
Table 79.Topology Discovery Specific Node Identification Data.............................95
Table 80.Topology Discovery Unit Type ..................................................................96
Table 81.Topology Discovery Flags..........................................................................97
Table 82.Payload of a CT Header..............................................................................97
Table 83.Command/Response Codes ........................................................................98
Table 84.RFT_ID payload .........................................................................................99
Table 85.RFT_ID ACC/RJT payload ........................................................................99
Table 86.FS_RJT Reason Codes ...............................................................................100
Table 87.FS_RJT Reason Explanations.....................................................................100
Table 88.FCAL timer values .....................................................................................101
Table 89.Information Units (IUs) ..............................................................................104
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Table 90.FCP_CMND payload..................................................................................105
Table 91.FCP_CNTL field ........................................................................................105
Table 92.Task Attribute values ..................................................................................105
Table 93.TMF flag values..........................................................................................106
Table 94.FCP_XFER_RDY payload .........................................................................107
Table 95.FCP_RSP payload ......................................................................................107
Table 96.FCP_STATUS field....................................................................................108
Table 97.FCP_RSP_INFO field ................................................................................109
Table 98.RSP_CODE definitions ..............................................................................109
Table 99.Task Management function RSP_CODE definitions .................................110
Table 100.SCSI Commands Supported .....................................................................115
Table 101.SCSI Control Byte ....................................................................................117
Table 102.FORMAT UNIT (04) ...............................................................................118
Table 103.Format of Defect List Header ...................................................................120
Table 104.Defect Descriptor - Block Format (for n + 1 defects) ..............................121
Table 105.Defect Descriptor - Bytes From Index Format (for n = 1 defects) ...........122
Table 106.Defect Descriptor - Physical Sector Format (for n + 1 defects) ...............123
Table 107.INQUIRY (12)..........................................................................................124
Table 108.Page Code descriptions.............................................................................124
Table 109.Inquiry Data - CmdDt = 0, EVPD = 0 ......................................................125
Table 110.Inquiry Data - EVPD = 1 (Page Code = 00h)...........................................127
Table 111.Inquiry Data - EVPD = 1 (Page Code = 03h)...........................................128
Table 112.Inquiry Data - EVPD = 1 (Page Code = 80h)...........................................130
Table 113.Inquiry Data - EVPD = 1 (Page Code = 83h)...........................................130
Table 114.Inquiry Data - EVPD = 1 (Page Code = D1h) ..........................................132
Table 115.Inquiry Data - EVPD = 1 (Page Code = D2h) ..........................................133
Table 116.Log Select (4C).........................................................................................134
Table 117.Log Sense (4D) .........................................................................................137
Table 118.Log Sense Page 0......................................................................................139
Table 119.Log Sense Page 2 (part 1 of 2)..................................................................140
Table 120.Log Sense Page 2 (part 2 of 2)..................................................................141
Table 121.Log Sense Page 3 (part 1 of 2)..................................................................142
Table 122.Log Sense Page 3 (part 2 of 2)..................................................................143
Table 123.Log Sense Page 5 (part 1 of 2)..................................................................144
Table 124.Log Sense Page 5 (part 2 of 2)..................................................................145
Table 125.Log Sense Page 6......................................................................................146
Table 126.Log Sense Page D .....................................................................................147
Table 127.Log Sense Page E .....................................................................................148
Table 128.Log Sense Page F......................................................................................149
Table 129.Log Sense Page F, Application Client Log ..............................................149
Table 130.Log Sense Page 10....................................................................................150
Table 131.Log Sense Page 10, self-test results..........................................................150
Table 132.Log Sense Page 10, self-test results..........................................................151
Table 133.Log Sense Page 10, Extended Segment Number......................................152
Table 134. Log Sense Page 2F...................................................................................153
Table 135.Log Sense Page 30....................................................................................154
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Table 136.Log Sense Page 37....................................................................................157
Table 137.Mode Select (15).......................................................................................159
Table 138.Mode Select (55).......................................................................................160
Table 139.Mode Sense (1A) ......................................................................................161
Table 140.Page Code Usage ......................................................................................162
Table 141.Mode parameter header (6).......................................................................162
Table 142.Mode parameter header (10).....................................................................163
Table 143.Mode Parameter Block Descriptor ...........................................................164
Table 144.Mode Parameter Page Format ..................................................................165
Table 145.Supported Page Codes ..............................................................................165
Table 146.Vendor Unique Parameters - Page 00.......................................................166
Table 147.Mode Page 01 (Vendor Unique Parameters) ............................................168
Table 148.Mode Page 02 (Disconnect/Reconnect Parameters).................................173
Table 149.Mode Page 03 (Format Device Parameters) .............................................174
Table 150.Mode Page 04 (Rigid Disk Drive Geometry Parameters) ........................176
Table 151.Mode Page 07 (Verify Error Recovery Parameters).................................177
Table 152.Page 08 (Caching Parameters)..................................................................178
Table 153.Page 0A (Control Mode Page Parameters) ...............................................180
Table 154.Page 0C (Notch Parameters).....................................................................182
Table 155.Mode Page 19h .........................................................................................184
Table 156.Values for RR_TOV Units .......................................................................185
Table 157.Page 1A (Power Control)..........................................................................186
Table 158.Page 1C (Informational Exceptions Control) ...........................................187
Table 159.Mode Sense (5A) ......................................................................................189
Table 160.Persistent Reserve In (5E) ........................................................................191
Table 161.PERSISTENT RESERVE IN, Service Action Codes ..............................191
Table 162.PERSISTENT RESERVE IN, parameter data for Read Keys .................192
Table 163.PERSISTENT RESERVE IN, parameter data for Read Reservations.....193
Table 164.PERSISTENT RESERVE IN, Read Reservation Descriptor...................194
Table 165.PERSISTENT RESERVE OUT (5F) .......................................................195
Table 166.PERSISTENT RESERVE OUT, Service Action Code............................196
Table 167.PERSISTENT RESERVE OUT, Scope Code .........................................198
Table 168.PERSISTENT RESERVE OUT, Type Code ...........................................198
Table 169.Conflict between new and existing Persistent Reserve ............................199
Table 170.PERSISTENT RESERVE OUT, Parameter List......................................200
Table 171.PERSISTENT RESERVE OUT, Service Action, Parameters and Generation counter
200
Table 172.APTPL and information held by a drive...................................................201
Table 173.PRE-FETCH (34) .....................................................................................202
Table 174.READ (6) - (08)........................................................................................203
Table 175.READ (10) - (28) .....................................................................................204
Table 176.READ BUFFER (3C) ...............................................................................205
Table 177.Read Buffer Header ..................................................................................206
Table 178.Read Buffer Description ...........................................................................207
Table 179.Echo Buffer Descriptor.............................................................................208
Table 180.READ CAPACITY (25)...........................................................................209
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Table 181.Format of READ CAPACITY command reply........................................210
Table 182.READ DEFECT DATA (37)....................................................................211
Table 183.Defect List Format ....................................................................................212
Table 184.Defect List Header ....................................................................................213
Table 185.Defect List Descriptor...............................................................................213
Table 186.Defect Descriptors of Bytes from Index Format ......................................214
Table 187.Defect Descriptors of Physical Sector Format..........................................214
Table 188.READ DEFECT DATA (B7) ...................................................................215
Table 189.Defect List Header ....................................................................................215
Table 190.Defect List Descriptor...............................................................................216
Table 191.Defect Descriptors of Bytes from Index Format ......................................216
Table 192.Defect Descriptors of Physical Sector Format..........................................216
Table 193.READ LONG (3E) ...................................................................................217
Table 194.REASSIGN BLOCKS (07) ......................................................................218
Table 195.Format of Reassign Blocks data ...............................................................219
Table 196.RECEIVE DIAGNOSTIC RESULTS (1C) .............................................220
Table 197.Receive Diagnostic Results page 0...........................................................221
Table 198.Enclosure Page Support for Send and Receive Diagnostic Commands ...222
Table 199.ESI Page Format .......................................................................................222
Table 200.Receive Diagnostic Results Page 40.........................................................223
Table 201.Translated address ....................................................................................224
Table 202.Device LED Control Page - Receive Diagnostic......................................225
Table 203.RELEASE (17) .........................................................................................226
Table 204.RELEASE (57) .........................................................................................227
Table 205.REPORT DEVICE IDENTIFIER (A3)....................................................228
Table 206.Report Device Identifier parameter list ....................................................229
Table 207.REPORT LUNS (A0) ...............................................................................230
Table 208.LUN Reporting parameter list format.......................................................230
Table 209.REQUEST SENSE (03) ...........................................................................231
Table 210.RESERVE (16) .........................................................................................232
Table 211.RESERVE (56) .........................................................................................233
Table 212.REZERO UNIT (01).................................................................................234
Table 213.SEEK (6) - (0B) ........................................................................................235
Table 214.SEEK (10) - (2B) ......................................................................................235
Table 215.SEND DIAGNOSTIC (1D) ......................................................................236
Table 216.SEND DIAGNOSTIC Function Code (1D) .............................................237
Table 217.Diagnostic Page 0 .....................................................................................238
Table 218.Diagnostic Page 40 ...................................................................................238
Table 219.Device LED Control Page - Send Diagnostic...........................................239
Table 220.Address to translate...................................................................................240
Table 221.SET DEVICE IDENTIFIER (A4) ............................................................241
Table 222.SET DEVICE IDENTIFIER, Parameter List ...........................................241
Table 223.START STOP UNIT (1B) ........................................................................242
Table 224.SYNCHRONIZE CACHE (35) ................................................................243
Table 225.TEST UNIT READY (00)........................................................................244
Table 226.VERIFY (2F) ............................................................................................245
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
Table 227.Verify (16) - (8F) ......................................................................................246
Table 228.WRITE (6) - (0A) .....................................................................................247
Table 229.WRITE (10) - (2A) ...................................................................................248
Table 230.Write and Verify (8E) ...............................................................................249
Table 231.WRITE AND VERIFY (2E) ....................................................................250
Table 232.WRITE BUFFER (3B) .............................................................................251
Table 233.Write Buffer Header .................................................................................252
Table 234.WRITE LONG (3F)..................................................................................254
Table 235.WRITE SAME (41) ..................................................................................256
Table 236.Write Same (16) - (93)..............................................................................257
Table 237.SCSI Status Byte. Format of the SCSI STATUS byte. ...........................259
Table 238.LIxx Frame Payloads ................................................................................262
Table 239.Response to Frames before PLOGI or PRLI ............................................264
Table 240.Spindle Motor Degraded Mode - Disable Auto Start ...............................273
Table 241.Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up ............274
Table 242.Spindle Motor Degraded Mode - Spindle Start Failure............................275
Table 243.Spindle Motor Degraded Mode - Spindle Stopped by Unit Stop Command276
Table 244.Self Configuration Failure Degraded Mode ............................................277
Table 245.Format Command Failure Degraded Mode ..............................................278
Table 246.Sense data combinations with auto/recommend rewrite/reallocate..........282
Table 247.Short and Extended Self-Test Description ...............................................288
Table 248.Recommend Reassign Errors....................................................................293
Table 249.Log Only Errors ........................................................................................293
Table 250.Format of Sense Data................................................................................301
Table 251.Field Pointer Bytes ...................................................................................319
Table 252.Actual Retry Count ...................................................................................320
Table 253.Progress Indication ...................................................................................321
Table 254.Unit Error Codes list .................................................................................323
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
1.0 General
1.1 Introduction
This document describes the specifications of the following Hitachi 3.5 inch drives.
•
HUS151414VLF200
•
HUS151473VLF200
•
HUS151436VLF200
Note: The specifications in this document are subject to change without notice.
1.2 Glossary
Word
Meaning
Kb
Kilobit = 1000 bits
Mb
Megabit = 1,000,000 bits
GB
Gigabyte = 1,000,000,000 bytes
MB
Megabyte = 1,000,000 bytes
KB
Kilobyte = 1000 bytes
MLC
Machine Level Control
PFA
Predictive Failure Analysis
S.M.A.R.T.
Self-Monitoring and Reporting Technology
ADM
Automatic Drive Maintenance
SE
Single Ended SCSI
LVD
Low Voltage Differential SCSI
FC-AL
Fibre Channel - Arbitrated Loop
1.3 Caution
This drive can be damaged by ESD (Electric Static Discharge). Any damages incurred to the drive after its removal from the
shipping package and the ESD protective bag are the responsibility of the user.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
1
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
2
2.0 Outline of the Drive
•
Storage capacities of 147 GB, 73 GB, and 36 GB
•
Dual 2.1250/1.0625 Gb/s Fibre Channel Arbitrated Loop-2 host interfaces
•
Supports dual-ported operations
•
Supports full duplex (command and data only) operations
•
Login BB_Credit=0
•
Enclosure Service Interface (ESI, SFF-8045 Rev. 4.2) and Enclosure Initiated ESI (SFF-8067 Rev. 2.6) compliant
•
Variable sector size (512, 520, 528 bytes/sector)
•
Tagged Command Queuing support
•
Automatic read/write data transfer
•
3.7 ms seek time in read operation for 146 GB
•
3.6 ms seek time in read operation for 73 GB
•
3.3 ms seek time in read operation for 36 GB
•
Adaptive read ahead algorithm
•
Write Cache
•
Back to back write
•
ECC On The Fly correction
•
Automatic defect reallocation
•
Self diagnostics at power on
•
Closed loop actuator servo
•
High level of integration of the electronics
•
Non head disk contact start/stop
•
15,000 RPM spindle rotation speed
•
Automatic actuator lock
•
PFA (S.M.A.R.T.)
•
Glass substrate disks
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
3
Hitachi Ultrastar 15K147 FC-AL 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 FC-AL Hard Disk Drive Specification
5
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
6
4.0 Drive Characteristics
4.1 Formatted Capacity
Table 1: Formatted Capacity
Description
HUS151414VLF200 HUS151473VLF200 HUS151436VLF200
Label capacity
147 GB
73 GB
36 GB
Number of heads
10
5
3
Number of disks
5
3
2
147,015,821,824
73,407,900,160
36,703,949,824
287,140,277
(111D69B5)
143,374,805
(88BB9D5h)
71,687,402
(445DCEAh)
Total data bytes (512
bytes/sector)
Total logical data
blocks
4.2 Data Sheet
Table 2: Data Sheet
Buffer to/from media
760 - 1129 [Mb/sec]
Host to / from buffer (interface transfer rate)
106.25 MB/s (1 GB/s) 212.5 MB/s (2 Gb/s)
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 model
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
7
4.3 Inquiry Information
4.3.1 Product ID
Product ID in Section 19.5.1.1, “Inquiry Data Format - EVPD = 0, Page Code = 0” on page 125, is as follows:
Table 3: Product ID in Inquiry Command
Product ID
Description
HUS151436VLF200
36 GB
HUS151473VLF200
73 GB
HUS151414VLF200
147 GB
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
8
4.3.2 World Wide ID - Block Assignment
Block Assignment of World Wide ID is as follows:
Table 4: Block assignment of World Wide ID in INQUIRY Command
Manufacturing Site
Singapore
Product
Block Assignment
HUS151414VLF200
001h(1)
HUS151473VLF200
001h(1)
HUS151436VLF200
001h(1)
Interface values: F20 = Fiber Channel
Note (1) - Additional block assignment will be issued as needed based on actual production volume.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
9
4.4 Cylinder allocation
Table 5: Cylinder allocation
Model
36GB
Zone
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
73 & 147 GB
Zone
Sectors/ trk cyln /zone
0
840
4950
1
812
972
2
800
1440
3
793
1435
4
784
952
5
770
2016
6
760
1044
7
756
522
8
746
2580
9
735
512
10
728
1530
11
720
1014
12
700
3906
13
680
1410
14
672
936
15
665
936
16
653
1856
17
640
1386
18
630
1378
19
616
2015
20
606
1612
21
595
1590
22
588
522
23
560
4422
start cyln end cyln
0
4949
4950
5921
5922
7361
7362
8796
8797
9748
9749
11764
11765
12808
12809
13330
13331
15910
15911
16422
16423
17952
17953
18966
18967
22872
22873
24282
24283
25218
25219
26154
26155
28010
28011
29396
29397
30774
30775
32789
32790
34401
34402
35991
35992
36513
36514
40935
Note: Section 19.10.5, “Mode Page 03 (Format Device Parameters)” on page 174 and Section 19.10.10, “Mode Page 0C
(Notch Parameters)” on page 182 provide methods to determine medium format and zone parameters.
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 FC-AL 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
147 GB
73 GB
36 GB
Typical (ms)
Max
Read
3.7
3.9
Write
4.1
4.3
Read
3.6
3.8
Write
4.0
4.1
Read
3.3
3.5
Write
3.7
3.8
“Typical” and “Max” are used throughout this document and are defined as follows:
Typical
Average of the drive population tested at nominal environmental and voltage conditions.
Max
Maximum value measured on any one drive over the full range of the environmental and voltage conditions.
(See Section 8.0, “Environment” on page 31 and Section 9.0, “DC power requirements” on page 35 for
ranges.)
The seek time is measured from the start of the actuator’s motion to the start of a reliable read or write operation. “Reliable
read or write” implies that error correction or recovery is not used to correct arrival problems. The average seek time is measured as the weighted average of all possible seek combinations.
Weighted average =
Max
∑ = ( max + 1 – n ) ⋅ ( Tnin + Tnout )
n=1
----------------------------------------------------------------------------------------------( max + 1 ) ⋅ ( max )
Where:
max
n
Tn.in
Tn.out
= Maximum seek length
= Seek length (1 to max)
= Inward measured seek time for an n track seek
= Outward measured seek time for an n track seek
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
11
4.5.1.2 Full stroke seek time
Table 7: Full stroke seek time
Function
Read
Write
Typical (ms)
6.7
7.0
Max (ms)
6.8
7.6
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 Cylinder switch time (Cylinder skew)
Table 8: Cylinder skew
Typical (ms)
Track to track skew
0.6
A cylinder switch time is defined as the amount of time required by the fixed disk to access the next sequential block after
reading the last sector in the current cylinder.
4.5.1.4 Head switch time (Head skew)
Table 9: Head skew
Typical (ms)
Head skew
1.4
A head switch time is defined as the amount of time required by the fixed disk to access the next sequential block after reading
the last sector in the current track.
4.5.1.5 Average latency
Table 10: Latency time
Rotation
Time for a revolution (ms)
Average latency (ms)
15,000 RPM
4.0
2.0
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
12
4.5.2 Drive ready time
Table 11: Drive ready time
Model
Typical (sec)
Maximum (sec)
147 GB Model
20.5
29.9
73 GB Model
14.3
29.9
36 GB Model
12.4
29.9
Model
Typical (sec)
Maximum (sec)
147 GB Model
13
20
73 GB Model
9
20
36 GB Model
8
20
4.5.3 Spindle stop time
Table 12: Spindle stop time
The period from power off to complete stop of spindle is categorized as operating and the Operating shock criteria are
applied until complete stop of spindle. Refer to Section 12.3, “Operating shock” on page 54.
4.5.4 Data transfer speed
Table 13: Data transfer speed (sector size 512 Byte case)
Description
Typical (MB / Sec)
Read
Write
Disk-buffer transfer
Instantaneous
Measured typical values
Zone
Model
0
0
0
0
All
147 GB
73 GB
36 GB
107.5
93.3
93.3
93.3
107.5
93
93
93
Instantaneous
Measured typical values
19
19
19
19
All
147 GB
73 GB
36 GB
78.8
68.5
68.5
68.5
78.8
68.5
68.5
68.5
Instantaneous
Measured typical values
23
23
23
23
All
147 GB
73 GB
36 GB
71.7
62.3
62.3
--
71.7
62.3
62.3
--
Notes:
•
Instantaneous disk-buffer transfer rate is derived by: (Number of sectors on a track)*512*(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 FC-AL 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 Throughput
4.5.5.1 Simple sequential access
Table 14: Simple sequential access performance (sector size 512 Byte case)
Operation
Typical (ms)
Read
Write
186
187
185
185
185
185
Maximum (ms)
Read
Write
186
187
186
185
185
185
Zone
0
0
0
Model
147 GB
73 GB
36 GB
Sequential Read / Write
19
19
19
147 GB
73 GB
36 GB
251
250
249
251
250
250
251
250
249
251
250
250
Sequential Read / Write
23
23
23
147 GB
73 GB
36 GB
275
274
--
275
275
--
275
274
--
275
275
--
Sequential Read / Write
The above table gives the time required to read / write for a total of 32,768 consecutive blocks ( 16,777,216 bytes) accessed by
128 READ /WRITE commands. Typical and Max values are given by 100 % and 110% of T respectively, throughout the following performance description.
Note: It is assumed that a host system responds instantaneously.
T = A + B + C + 16,777,216/D
Where:
T = Calculated time
A = Command overhead (no cache hit)
B = Average seek time
C = Average latency
D = Sustained disk-buffer transfer rate
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
14
4.5.5.2 Random access
Table 15: 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 FC-AL Hard Disk Drive Specification
15
Hitachi Ultrastar 15K147 FC-AL 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 FC-AL Hard Disk Drive Specification
17
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
18
6.0 Physical Format
Media defects are remapped to the next available sector during the Format Process in manufacturing. The mapping from Logical Block Address (LBA) to the physical Block locations is calculated using internally maintained tables.
6.1 Shipped Format (P-List)
•
Data areas are optimally used.
•
No extra sector is wasted as a spare throughout user data areas.
•
All pushes generated by defects are absorbed by spare tracks of the inner zone.
P-List Physical Format
Note: Defects are skipped without any constraint, such as track or cylinder boundary. The calculation from LBA to physical
is done automatically by internal table.
6.2 Reassigned Format (G-List)
•
G-List is prepared for 5000 LBAs.
•
Multiple reassignment of the same LBA does not increase the number of G-List entries.
•
A cylinder for spare sectors is prepared every 512 physical cylinders.
Note: G-List entries are part of the normal maintenance work of hard disk drives.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
19
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
20
7.0 Electrical Interface
7.1 FC-AL Connector
The drive uses the 40 pin SCA-2 connector defined by the SFF-8045 specification and the SFF-8067 specification. The only
difference between SFF-8045 and SFF-8067 is the Enclosure Service Interface. The drive will 'discover' the level of Enclosure
Service Interface supported by the enclosure, and use the proper level for enclosure communication. This 'discovery' process is
defined in the SFF-8067 specification.
The connector is expected to be used in an environment which uses a common connector structure for racking disk drives in a
cabinet. The connector allows for plugging a drive directly into a backplane by providing the necessary electrical connection.
Mechanical stability and device retention must be provided by a mechanism outside the drive.
The signals defined in this connector include:
•
•
•
•
•
•
•
•Dual ported Fibre Channel In/Out control signals
+5V and +12V power
ID select
Motor start control
LED drive signals
PBC Interlock control
Fibre Channel link rate selection/Hard Reset
Power control
7.1.1 40 pin SCA-2 SFF-8045 FC-AL Connector Definition
The drive uses the connector compatible with the SFF-8045 connector specifications. The connector contact assignment is
shown in following table.
Table 16: 40-pin Connector Signal Definition
Signal Name
Pin #
Pin #
Signal Name
-ENBL BYP CH1
1
21
12V Charge
12 Volts
2
22
12V Ground
12 Volts
3
23
12V Ground
12 Volts
4
24
+Port 1_In
-Parallel ESI
5*
25
-Port 1_In
-Drive Present
6
26
12V Ground
Ready LED Out
7
27
+Port 2_In
Power Control
8
28
-Port 2_In
Start_1/Mated
9
29
12V Ground
Start_2/Mated
10
30
+Port 1_Out
-ENBL BYP CH2
11
31
-Port 1_Out
Sel_6/-EFW
12*
32
5V Ground
Sel_5/-P_ESI_5
13*
33
+Port 2_Out
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
21
Sel_4/-P_ESI_4
14*
34
-Port 2_Out
Sel_3/-P_ESI_3
15*
35
5V Ground
Fault LED Out
16
36*
Sel_2/-P_ESI_2
Dev_Ctrl_Code_2
17
37*
Sel_1/-P_ESI_1
Dev_Ctrl_Code_1
18
38*
Sel_0/-P_ESI_0
5 Volts
19
39
Dev_Ctrl_Code_0
5 Volts
20
40
5V Charge
Note:
The guide pins are connected to 5V ground.
* Definition changes for SFF-8067
7.1.2 Voltage and Ground Signals
The 12 V and 5 V contacts provide all of the voltages required by the drive. The two voltages share a common ground plane to
which all of the ground contacts are connected.
7.1.3 Fault LED Out
As specified in the SFF-8045 specification, the Fault LED is driven under the following conditions:
•
•
•both enable bypass signals are asserted by the drive
an internal failure has been detected by the drive
the drive has been instructed by the host to turn on the LED
The drive provides an open-collector TTL driver with up to 30mA of current sink capability to the drive fault LED. The cathode of the LED should be connected to this signal. The LED and the current-limiting resistor must be provided by the enclosure.
7.1.4 Ready LED Out
As specified in the SFF-8045 specification, the Ready LED Out signal has the following definition (per the Hot Plug Implementation):
• Drive not mated:
–
•
Drive mated, motor not spinning:
–
•
The signal is asserted (i.e. low) for a period long enough to be detected by the observer whenever a SCSI command is
received. The LED is normally off.
Drive mated, spinning up or down:
–
•
The signal is de-asserted (i.e. high). The LED is off.
The signal is alternately asserted and de-asserted for a period of 1/2 second. The LED is flashing.
Drive mated, motor spinning:
–
The signal is normally asserted continuously. The signal is de-asserted for a period long enough to be detected by an
observer, whenever a SCSI command is received. The LED is usually on.
The drive provides an open-collector TTL driver with up to 30mA of current sink capability to the Ready LED Out signal. The
cathode of the LED should be connected to this signal. The LED and the current-limiting resistor must be provided by the
enclosure.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
22
7.1.5 Start Mated Controls
The Start_X Mated signals are TTL inputs to the drive and have 10K ohm pull-up resistors.
As per the SFF-8045 specification, the 'Start_x Mated' function is implemented as in the following table. Please refer to SFF8045 for a more complete definition.
Table 17: Start/Mated Controls
Start_2 Mated
Start_1 Mated
Spin Function
Open
Open
Drive is not mated. No spin-up will occur.
Open
Gnd
The motor will spin up with the SCSI Unit Start Cmd
Gnd
Open
The motor will spin up after a delay of 6 times the modulo 8 of
Sel_ID (in seconds)
Gnd
Gnd
The motor will spin up after drive initialization
7.1.6 SEL_n and Enclosure Service Signals
These signals have different definitions depending on the state of -Parallel ESI and the level of enclosure service supported by
the backplane.
7.1.6.1 SEL_n and Enclosure Service Signals
-Parallel ESI is a TTL open-drain output from the drive. It is used to establish the definition of the SEL_n signals. When -Parallel ESI is de-asserted (high), the backplane shall preset SEL_ID information on these signals (within 1usec). When -Parallel
ESI is asserted (low), the backplane (if supported) will present enclosure service information on these signals (within 1usec).
The drive will then go through a 'discovery' phase to determine the level of enclosure services that the backplane supports (i.e.
none, SFF-8045, or SFF-8067) and behave accordingly.
7.1.6.2 SEL_ID Function
The SEL_n (TTL compatible) inputs (defined when -Parallel ESI is de-asserted) provide a binary value of loop identifier to the
drive. These 7 signals define 128 possible values and are directly translated into an 8 bit hard AL_PA via the table below. Only
AL_PA's with neutral disparity are valid values. The drive will attempt to acquire this hard AL_PA for its own during the
LIHA phase of the loop initialization process (LIP).
Table 18: SEL_ID/AL_PA
SEL_ID
AL_PA
SEL_ID
AL_PA
SEL_ID
AL_PA
SEL_ID
AL_PA
0
EF
20
B2
40
72
60
3A
1
E8
21
B1
41
71
61
39
2
E4
22
AE
42
6E
62
36
3
E2
23
AD
43
6D
63
35
4
E1
24
AC
44
6C
64
34
5
E0
25
AB
45
6B
65
33
6
DC
26
AA
46
6A
66
32
7
DA
27
A9
47
69
67
31
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
23
8
D9
28
A7
48
67
68
2E
9
D6
29
A6
49
66
69
2D
A
D5
2A
A5
4A
65
6A
2C
B
D4
2B
A3
4B
63
6B
2B
C
D3
2C
9F
4C
5C
6C
2A
D
D2
2D
9E
4D
5A
6D
29
E
D1
2E
9D
4E
59
6E
27
F
CE
2F
9B
4F
56
6F
26
10
CD
30
98
50
55
70
25
11
CC
31
97
51
54
71
23
12
CB
32
90
52
53
72
1F
13
CA
33
8F
53
52
73
1E
14
C9
34
88
54
51
74
1D
15
C7
35
84
55
4E
75
1B
16
C6
36
82
56
4D
76
18
17
C5
37
81
57
4C
77
17
18
C3
38
80
58
4B
78
10
19
BC
39
7C
59
4A
79
F
1A
BA
3A
7A
5A
49
7A
8
1B
B9
3B
79
5B
47
7B
4
1C
B6
3C
76
5C
46
7C
2
1D
B5
3D
75
5D
45
7E
1
1E
B4
3E
74
5E
43
7E
NA
1F
B3
3F
73
5F
3C
7F
-
Note: All values are in hex format. An AL_PA value of 0x00 is not valid for an NL_Port. A SEL_ID of 0x7F forces the
drive to obtain a soft address.
7.1.6.3 P_ESI_n Function
The SEL_N (TTL compatible) I/O's (defined when -Parallel ESI is asserted) provide an interface between the enclosure and
the drive. When signals are defined as outputs, they are configured as open-drain drivers with 4mA sink capability.
When the drive asserts -Parallel ESI, it goes through a 'discovery' process (see SFF-8067) to determine the level of enclosure
service supported by the backplane. The outcome of the 'discovery' process is that the backplane:
1. Does not support enclosure services or
2. Supports SFF-8045 enclosure services or
3. Supports SFF-8067 enclosure services
The definition of the signals are summarized in the table below:
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
24
Table 19: SEL_N/P_ESI_N Signal Definition
-Parallel ESI
-Parallel ESI asserted (low)
de-asserted (high)
SFF-8045*
SFF-8067*
Sel_0 (input)
P_ESI_0 (input)
Data(0) (bi-di**)
Sel_1 (input)
P_ESI_1 (input)
Data(1) (bi-di**)
Sel_2 (input)
P_ESI_2 (input)
Data(2) (bi-di**)
Sel_3 (input)
P_ESI_3 (input)
Data(3) (bi-di**)
Sel_4 (input)
P_ESI_4 (input)
-ENCL_ACK (output)
Sel_5 (input)
P_ESI_5 (input)
-DSK_RD (input)
Sel_6 (input)
-EFW (input)
-DSK_WR (input)
Note:
* level of backplane support as established in 'discovery'
** the direction is determined by the state of DSK_RD and DSK_WR
all signals are assumed valid 1 usec after -Parallel ESI changes state
7.1.6.4 SFF-8045 Enclosure Service Interface
The SFF-8045 Enclosure Service Interface defines 7 bits of enclosure status. This status is read by the drive, and presented to
the initiator, upon receipt of the appropriate SCSI RECEIVE DIAGNOSTIC command. The definitions of the status bits are
vendor specific. The drive does not try to interpret the status. The drive assumes -EFW is status and treats it as it does the other
P_ESI_n signals.
7.1.6.5 SFF-8067 Enclosure Service Interface
The SFF-8067 Enclosure Service Interface defines a bidirectional communication path between the backplane and the drive.
Read Communications are invoked by the drive upon receipt of the appropriate SCSI RECEIVE DIAGNOSTIC command.
This has the system level effect of the host reading information from the enclosure. Write Communications are invoked by the
drive upon receipt of the appropriate SCSI SEND DIAGNOSTIC command. This has the system level effect of the host writing information to the enclosure. The meaning of the information is vendor specific. The drive does not try to interpret the
information. See the SFF-8067 Specification for a detailed description of the communication protocol.
7.1.7 –ENBL_BYP CH1, -ENBL_BYP_CH2
These TTL outputs from the drive provide 4mA of sink capability. They are intended to control the state of a loop port bypass
circuit on the backplane. The drive powers up with these signals turned off. It is assumed that the backplane will provide a
1Kohm pull-down resistor that will ensure the drive is bypassed on the loop when it is not present, or when it is powering up.
After a successful power-up, the drive will attempt to enable itself on both loops (if allowed to do so via SCSI mode page 19h).
These signals are also controllable by the host with the LPB and LPE fibre channel primitives.
7.1.8 –Drive Present
This signal is connected to the drive's ground plane. The backplane can use this signal to detect the presence of the drive.
7.1.9 Dev_Ctrl_Code_x
The signals DEV_CTRL_CODE_2 through DEV_CTRL_CODE_0 provide a binary code to the drive to control functions
such as FC link rate, Power Failure Warning (PFW) and Hard Reset. The control function is either identified by a code or a
sequence of codes on the DEV_CTRL_CODE signals. The table below defines the functions and assigned codes that use a
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
25
decode of the value on the DEV_CTRL_CODE signals.
The Hard Reset function uses a sequence of values on the DEV_CTRL_CODE signals. The sequence is 5, 1, 3, 2, 3, 1, 5. A
drive detecting a valid Hard Reset sequence shall perform the equivalent of a power-on-reset.
10 Kohm pull up resistors to 3.3 VOLTS are provided on the drive for both DEV_CTRL_CODE_ 2 and
DEV_CTRL_CODE_0 to be sure that each signal is maintained in its high state unless a low is provided from the backplane.
For more information refer to the SFF-8045 Specification.
Table 20: DEV_CTRL_CODE_N Signal Definition
Link Rate
DEV_CTRL_CODE_2
DEV_CTRL_CODE_1
DEV_CTRL_CODE_0
1.0625 GHz
1
1
1
2.1250 GHz
1
1
0
4.250 GHZ (not supported)
1
0
1
Reserved
1
0
0
Reserved
0
1
1
Reserved
0
1
0
Reserved
0
0
1
Power Failure Warning
0
0
0
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
26
8.0 Environment
8.1 Temperature and humidity
Table 21: 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 to 70º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 FCAL Hard Disk Drive Specification
27
100
36'C/95%
90
WetBuib=35.0'C
31'C/90%
80
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)
Figure 1 : Temperature and humidity
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 FCAL Hard Disk Drive Specification
28
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 22: 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
Figure 2 : Module locations
Hitachi Ultrastar 15K147 FCAL Hard Disk Drive Specification
29
Hitachi Ultrastar 15K147 FCAL Hard Disk Drive Specification
30
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 23: Input Voltage
Tolerance
Absolute Max
Spike Voltage
Supply Rise Time
+5 Volts Supply
+/- 5%
5.5 V
0-200 ms
+12 Volts Supply
+/- 5%
15 V
0-400 ms
Note: -8% is acceptable during spin up, but the spin up time is not guaranteed.
CAUTION: To avoid damage to the drive electronics, power supply voltage spikes must not exceed 5.5V.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
31
9.1 Power Supply Current, Average and Peak
Table 24: Model 147 GB
Model 147GB
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
1.08
1.18
0.70
0.20
Current
+12V
1.70
2.30
.071
0.45
Total Average
Note
Power (W)
--Maximum
Peak
12.02
Avg
--Pk to Pk
Random Peak AC 209
Random W/R(DC) 209
1.54
0.86
2.64
1.13
--17.84
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.85
0.82
0.81
0.79
0.77
1.03
0.96
0.90
0.84
0.77
16.57
15.66
14.82
13.99
13.14
Avg, 2KB, Qd=1
IO/Sec
150
120
90
60
30
Table 25: Model 147GB: 5V Current during spinup
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
32
Table 26: Model 73 GB
Model 73GB
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
1.08
1.18
0.70
.20
Current
+12V
1.70
2.30
0.51
0.41
Total Average
Note
Power (W)
--Maximum
Peak
9.60
Avg
--Pk to Pk
Random Peak AC 215
Random W/R(DC) 215
1.54
0.86
2.17
0.87
--14.70
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.85
0.82
0.81
0.79
0.77
0.78
0.73
0.67
0.62
0.56
13.62
12.82
12.08
11.36
10.63
Avg, 2KB, Qd=1
Start Peak DC
Start Peak AC
Idle
Idle Ripple
Current
+5V
1.08
1.18
0.70
0.20
Current
+12V
1.70
2.30
0.45
0.37
Total Average
Note
Power (W)
--Maximum
Peak
8.92
Avg
--Pk to Pk
Random Peak AC 220
Random W/R(DC) 220
1.54
0.86
2.15
0.80
--13.94
Peak 2KB Qd = 4
Avg, 2KB Qd = 4
IOPS
0.85
0.82
0.81
0.79
0.77
0.71
0.65
0.60
0.55
0.50
12.73
11.97
11.27
10.59
9.88
Avg, 2KB, Qd=1
IO/Sec
150
120
90
60
30
Table 27: Model 36 GB
Model 36GB
IO/Sec
150
120
90
60
30
9.2 Ripple Voltage
Table 28: Power Supply Generated Ripple at Drive Power Connector
Maximum (mV pp)
MHz
+5 V DC
250
0-10
+12 V DC
250
0-10
During drive start up and seek, 12 volt ripple is generated by the drive (referred to as dynamic loading). If the power of several
drives is daisy chained, the power supply ripple plus other drive dynamic loading must remain within the regulation tolerance
of +5%. A common supply with separate power leads to each drive is a more desirable method of power distribution.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
33
To prevent external electrical noise from interfering with the drive's performance, the drive must be held by four screws in a
user system frame that has no electrical level difference at the four screw positions. The drive enclosure must not be used in
the current return path of the drive power supply. The maximum common-mode noise current passing through the drive must
not exceed 20 mA.
9.3 Power Consumption Efficiency Index
Table 29: Power Consumption Efficiency Index
Model
147GB Model 73GB Model
Power Consumption Efficiency Index -Idle Mode (W/GB)
0.08
0.13
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
34
36GB Model
0.25
10.0 Reliability
10.1 Start/Stop Cycles
The drive is designed to withstand a minimum of 50,000 start/stop cycles at ambient environment.
The drive is designed to withstand a minimum of 10,000 start/stop cycles at the operating environment conditions specified in
“Environment” on page 27.
10.2 Data Reliability
The probability of an uncorrectable data error is 10 in 1x1016 bits read.
The following ECC On-The-Fly correction is implemented:
•
1 symbol = 8 bits
•
3 interleaves
•
18 symbols, 6 symbols per each interleave, for on the fly 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 19.10.13, “Mode Page 1C
(Informational Exceptions Control)” on page 187. 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 19.7.11, “Log Sense Page 2F” on page 153.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
35
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
36
11.0 Mechanical Specifications
11.1 Outline
11.2 Mechanical Dimensions
The drive complies with SFF-8301.
Table 30: 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 FC-AL Hard Disk Drive Specification
37
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
38
11.3 Interface Connector
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
39
11.4 Mounting Positions and Tappings
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
40
11.5 Drive Mounting
The drive will operate in all axes (6 directions). Performance and error rate will stay within specification limits if the drive is
operated in the other orientations from which it was formatted.
The recommended mounting screw torque is 0.6 - 1.0 Nm (6 - 10 Kgf.cm). The recommended mounting screw depth is 4 mm
maximum for bottom and 4.5 mm maximum for horizontal mounting.
To avoid performance degradation, mount the drive in the system securely enough to prevent excessive motion or vibration of
the drive at seek operation or spindle rotation, using appropriate screws or equivalent mounting hardware. Consult with the
issuer of this specification for actual application if necessary.
Drive level vibration tests and shock tests are to be conducted with the drive mounted to a table using the bottom four screws.
11.6 Heads Unload and Actuator Lock
Heads are moved out from the disks (unload) to protect the disk data during shipping, moving or storage. At power down, the
heads are automatically unloaded from over the disk area and the head actuator locking mechanism will secure the heads in the
unload position.
11.7 Breather Hole
The breather hole must be kept clear and unobstructed at all times. Do not cover the breather hole.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
41
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
42
12.0 Vibration and Shock
All vibration and shock measurements in this section are made with a drive that has no mounting attachments for the systems.
The input power for the measurements is applied to the normal drive mounting points.
12.1 Operating Vibration
12.1.1 Random Vibration
The drive is designed to operate without unrecoverable errors while being subjected to the vibration levels as defined below.
The assessments are carried out during 30 minutes of random vibration using the power spectral density (PSD) levels as follows.
No Errors:
0.4 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes.
No Data Loss: 1.2 G RMS, 5-500 Hz, flat PSD profile for each of the three mutually perpendicular axes.
Note:
The specified levels are measured at the mounting points.
12.1.2 Swept Sine Vibration
The drive will meet the criterion while operating in the respective conditions as described below.
No errors:
0.5 G 0-peak, 5-400-5 Hz sine wave, 0.5 octave/minute sweep rate
No data loss:
0.75 G 0-peak, 5-400-5 Hz sine wave, 0.5 octave/minute sweep rate
1.0 G 0-peak, 5-300-5 Hz sine wave, 0.5 octave/minute sweep rate
12.2 Non-operating 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 FC-AL Hard Disk Drive Specification
43
axes. There must be a minimum of thirty seconds delay between shock pulses. The input level is applied to a base plate where
the drive is attached using four mounting screws.
12.4 Non-operating shock
The drive will not sustain permanent damage or loss of recorded data after being subjected to the environments as described
below.
12.4.1 Half sinewave shock pulse
80 G, 11 ms duration, half sinewave pulse
250 G, 2 ms duration, half sinewave pulse
The shocks are applied in each direction of the drive for the three mutually perpendicular axes, one axis at a time. The input
level is applied to a base plate where the drive is attached using four mounting screws.
12.4.2 Rotational shock
30,000 radians /second2, 1 ms duration
20,000 radians /second2, 2 ms duration
The shock input is applied around the axis of the actuator pivot. The shock input does not displace the heads from the actuator
latched position.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
44
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 31: 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 FC-AL Hard Disk Drive Specification
45
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
46
14.0 Identification
14.1 Labels
The following labels are affixed to every hard disk drive shipped from the drive manufacturing location in accordance with
appropriate hard disk drive assembly drawing:
•
A label containing Hitachi Global Storage Technologies logo, Hitachi part number and the statement “Made by Hitachi.”, or Hitachi approved equivalent.
•
A label containing drive model number, manufacturing date, formatted capacity, country of origin or Hitachi
approved equivalent and UL, CSA, TUV, CE and CTICK logos.
•
A bar code label containing the drive serial number.
•
A user designed label, per agreement
•
Interface definition mark, FC-AL-2 Model
The labels may be integrated with other labels.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
47
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
48
15.0 Electromagnetic Compatibility
The drive, when installed in a suitable enclosure and exercised with a random accessing routine at maximum data rate meets
the worldwide EMC requirements listed below.
Hitachi will provide technical support to meet the requirements to comply with the EMC specifications.
•
United States Federal Communications Commission (FCC) Rules and Regulations (Class A), Part 15
•
Hitachi Corporate Standard C-S 2-0001-005
•
CISPR Publication 22; 1993 (Class A)
•
CISPR Publication 22; Amendment 1, 1995
•
CISPR Publication 22; Amendment 2, 1996
•
Electrostatic Discharge Susceptibility limits for a Class 2 ESD environment specified in IBM Corporate Standard CS 2-0001-034.
•
Radiated Electromagnetic Susceptibility (RES) as specified in Hitachi Corporate Standard C-S 2-0001-037.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
49
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
50
16.0 Standards
The following shows the safety standards for different countries.
16.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.
16.2 European Standards Compliance
The product is certified to EN60950.
16.3 German Safety Mark
The product is approved by TUV on Test requirement: EN 60950, but the GS mark is not applicable to internal devices such as
these drives.
16.4 Flammability
The printed circuit boards used in this drive are made of material with a UL recognized flammability rating of V-1 or better.
The flammability rating is marked or etched on the board. All other parts not considered electrical components are made of
material with a UL recognized flammability rating of V-1 or better.
16.5 Corporate Standards Compliance
This product has been designed to meet the following Corporate Standards:
- NB 3-0501-201 Product Safety, National Requirements-All Countries.
- CS 3-0501-070 Electrical, Mechanical and Flammability
- NB 3-0501-033 Product Safety National Certification Conformity Requirement
- CS 1-9700-020 Eco-Product Design Requirement
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
51
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
52
17.0 FC-AL attachment
This section defines some basic terminology and describes the behavior of the drive when attached to a Fibre Channel Arbitrated Loop.
17.1 Fundamentals
This section introduces some of the terminology that is used in describing Fibre Channel and FC-AL.
Fibre Channel is logically a bi-directional serial data channel between two Nodes. Nodes are physically connected by a Link;
the point of connection between the link and the node is called a Port.
Ports may be connected point-to-point by a single link or by a switching network (Fabric). If the port is part of the Fabric it is
called an F_Port, otherwise it is an N_Port.
Fibre Channel is defined in terms of a hierarchy of functions or 'protocol layers'.
•
FC-0: Physical Link
•
FC-1: Transmission Protocol
•
FC-2: Signaling and Framing Protocol
•
FC-3: Common Services
•
FC-4: Mapping
All layers except FC-4 are defined in
•
“Fibre Channel Physical and Signaling Interface (FC-PH)” - ANSI
The Arbitrated Loop is an extension of FC-1 and FC-2 that allows more than two nodes to be connected without the expense of
a Fabric. A port that connects to an Arbitrated Loop is generally referred to as an L_Port. However, the terms NL_Port and
FL_Port are also used if it is necessary to distinguish whether or not the L_Port is part of a Fabric. FC-AL is defined in:
•
“Fibre Channel Arbitrated Loop (FC-AL)” -ANSI
FC-4, the Mapping layer, defines how other communication protocols (e.g. SCSI, IPI-3, HIPPI) may use Fibre Channel functions. The FC-4 used by The Drive is SCSI-FCP, which is defined in:
•
“Fibre Channel Protocol for SCSI (SCSI-FCP)” -ANSI
The 'Disk Profile', recommends which features from the other documents should and should not be implemented in order to
ensure compatibility between devices from different manufacturers. The full title of the Disk Profile is:
•
“Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)” -ANSI
An additional document, the ‘Public Loop Profile’, describes the additional features needed to support communication over a
FC Fabric Topology. In addition to communicating with devices on their local loop, Public Loop devices can also communicate to devices across a network through the use of a “Fabric Port.” Public Loop behavior is defined in:
•
“Fibre Channel - Fabric Loop Attach (FC-FLA)” -ANSI
The Drive complies with the FC-FLA, which makes the following requirements:
1. The upper two bytes of the device’s NL_Port ID must not be zero.
2. The device must be able to communicate with the Fabric Port i.e., open AL_PA 0x00.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
53
In addition, the Drive implements FC-FLA as a super-set of the FC-PLDA. Thus, the Drive conforms to FC-PLDA except for
those behaviors explicitly defined by the FC-FLA profile. The PLDA makes the following additional requirements.
1. The FC-4 is SCSI-FCP (see 2.0, “SCSI-FCP”).
2. The Drive provides a Class 3 Fibre Channel service.
- NO indication of (un)successful class 3 frame delivery is transmitted.
- Frame flow control is buffer-to-buffer only.
- Class 1 and 2 frames are ignored.
3. Direct point-to-point attachment with an N_Port is not supported.
17.1.1 Node and Port names
Every Fibre Channel Node and Port in the world must have a unique name. The Drive is a node with two L_Ports and therefore
has a Node_Name and two Port_Names.
Both the Node_Name and Port_Name are in 64-bit IEEE Registered Name format, as illustrated in Table 32.
Table 32: IEEE Registered Name format
Bit
63-60
59-36
35-24
23-22
21-0
0101
OUI in Canonical Form
Block Assignment
Port
S/N
The Name Address Authority field (0101b) specifies the format used for the rest of the name as follows:
• OUI
Organizationally Unique Identifier (24 bits). Canonical form means that each byte is stored in
“bit reversed” order.
• Block Assignment
• Port
Block assignment within Hitachi Global Storage Technologies
Node/Port Identifier
• S/N
00b
Node
01b
Port 1
10b
Port 2
11b
Not assigned
Sequentially increasing drive serial number assigned at manufacturing.
17.1.2 NL_Port address
An NL_Port address, as illustrated in Table 33, is a 3 byte value that uniquely identifies an NL_Port on a Fibre Channel network. The Domain and Area bytes are assigned to a NL_Port by its local FL_Port. The least significant byte in the NL_Port
address is the Arbitrated Loop Physical Address (AL_PA), and uniquely identifies a NL_Port on its local loop.
A Hard AL_PA is one which is supplied, via the Drive connector, from external switches or jumpers. A Soft AL_PA is one
which is assigned during Loop Initialization
Table 33: NL_Port address
Bits 23-16
Bits 15-8
Bits 7-0
Domain
Area
AL_PA
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
54
17.1.3 Primitive signals and sequences
The fundamental unit of transfer on a Fibre Channel link is the 8b/10b encoded Transmission Character. Only 256 characters
are required to represent a byte of data so the set of valid transmission characters is sub-divided into Data Characters and Special Characters.
A Word is a group of four consecutive transmission characters.
An Ordered Set is a word that starts with a special character (to give word and byte sync) and which has special significance to
the communication protocol. Fibre Channel defines the following types of ordered sets:
•
Frame delimiters
•
Primitive signals
•
Primitive sequences
A Frame Delimiter immediately precedes or follows the contents of a frame (see 17.1.4, “Frames” on page 56). Fibre Channel
defines the following:
•
SOF
Start of frame
•
EOF
End of frame
A Primitive Signal is an ordered set that has special meaning when received by itself. Fibre Channel defines the following:
•
R_RDY
Receiver Ready
•
IDLE
Idle
FC-AL adds the following:
•
ARBx
Arbitrate
•
ARB(F0)
Arbitrate
•
OPNyx
Open Full-duplex
•
OPNyy
Open Half-duplex
•
OPNfr
Open Broadcast Replicate1
•
OPNyr
Open Selective Replicate1
•
CLS
Close
•
MRKtx
Mark1
A Primitive Sequence is an ordered set that is transmitted repeatedly and continuously. Three or more of the ordered sets must
be received consecutively in order to recognize the primitive sequence. Fibre Channel defines the following:
•
NOS
Not Operational2
•
OLS
Offline2
•
LR
Link Reset2
•
LRR
Link Reset Received2
FC-AL adds the following:
•
LPByx
Loop Port Bypass
•
LPEyx
Loop Port Enable
1. Since normal buffer-to-buffer flow control is disabled when OPNr is used, there is no guarantee that the drive has a buffer available to receive an
in-bound frame. It is therefore, recommended that OPNr not be used.
2. Used to convey information about a dedicated connection and therefore not relevant to FC-AL. If detected during an open connection, the drive
will immediately close. Otherwise it will simply re-transmit.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
55
•
LPEfx
Loop Port Enable all
•
LIP(F7,F7)
Loop Initialization, no valid AL_PA
•
LIP(F8,F7)
Loop Initialization, loop failure, no valid AL_PA
•
LIP(F7,AL_PS)
Loop Initialization, valid AL_PA
•
LIP(F8,AL_PS)
Loop Initialization, loop failure, valid AL_PA
•
LIP(AL_PD,AL_PS)
Loop Initialization, reset L_Port
17.1.4 Frames
Information transfer is achieved via frames that are constructed from words and ordered sets. All frames have the same general
format, as shown in Table 34.
Table 34: General frame format
Field name
SOF
Header
Payload
Fill bytes
CRC
EOF
Field size, # of bytes
4
24
0 to 2048
0 to 3
4
4
The SOF ordered set indicates the start of frame and provides word synchronization.
The Header is the first field after the SOF delimiter. It is used by the link control facility to control link operations, control
device protocol transfer, and to detect missing or out of order frames. The header is illustrated in Table 35.
FC-PH describes the content of each field except 'Parameter'. SCSI-FCP defines this field as RLTV_OFF (Relative Offset).
Table 35: Frame header
Byte
3
2
1
0
word
0
R-CTL
D-ID
1
Reserved
S-ID
2
TYPE
F-CTL
3
SEQ-ID
4
DF-CTL
OX-ID
5
SEQ-CNT
RX-ID
Parameter (RLTV_OFF)
The Payload follows the header and has a length between 0 and 2048 bytes, which must be divisible by 4. An additional 0-3
fill bytes are appended to the payload in order to ensure that it ends on a word boundary.
The Cyclic Redundancy Check (CRC) is a four byte field following the payload. It is used to verify the integrity of the header
and payload.
The EOF ordered set marks the end of a frame.
17.1.5 Sequences
A Sequence is a set of one or more related frames that flow in one direction only. The sequence is identified by the Sequence
Identifier (SEQ_ID) field in the frame header.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
56
17.1.6 Exchanges
An Exchange is a set of one or more related non-concurrent sequences that may flow in the same or opposite directions. The
exchange is identified by an Originator Exchange Identifier (OX_ID) and a Responder Exchange Identifier (RX_ID) in the
frame header.
17.2 Basic Link Services
The Basic Link Services are all frames with no payload. The Header TYPE field is set to 00h (Basic Link Service) and R_CTL
is set to 1000xxxxb (Basic Link_Data, Code = xxxx).
Table 36: Basic link service command codes
Command
Description
Abbr.
0000
No Operation
NOP
0001
Abort Sequence
ABTS
0010
Remove Connection
RMC
0100
Basic Accept
BA_ACC
0101
Basic Reject
BA_RJT
Others
Reserved
NOP and RMC are prohibited by the Disk Profile. If the drive receives either an NOP or an RMC, it will ignore it.
Note: PLDA 2.1 specifies: “Reserved FC-PH fields are not required to be checked for zeroes. Validity bits set to 0 remove any
requirement to check the corresponding field for zeroes (e.g., if F_CTL bit 3=0, receiving N_Ports are not required to verify
that the parameter field in word 5 of the frame header contains zeroes).” As such, the drive does not validate 1) reserved FC
fields or 2) fields that are not reserved but are not valid for the current frame (as the example above with F_CTL bit 3). This
does not apply to any reserved field checking and testing within the FCP_CDB. These fields are checked as per ANSI SCSI
requirements.
17.2.1 Abort sequence (ABTS)
Although ABTS is a Fibre Channel Basic Link Service, it is used by SCSI-FCP to implement the Abort Task, Task Management function. It may only be used by a SCSI initiator to abort an entire exchange using the Recovery Abort protocol. Refer to
18.4.1, “Abort Task (Implemented as ABTS BLS)” on page 111 for a description of the Recovery Abort Protocol and the
frame payloads.
The response to ABTS is either BA_ACC or BA_RJT.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
57
17.2.2 Basic accept (BA_ACC)
BA_ACC indicates that a Basic Link Service Request has been completed. The drive only sends a BA_ACC in response to an
ABTS Basic Link Service.
Table 37: BA_ACC Payload
Byte
Item
Size (Bytes)
0
SEQ_ID Validity (80h = valid, 00h = invalid)
1
1
SEQ_ID
1
2
Reserved
2
OX_ID
2
RX_ID
2
Low SEQ_CNT
2
High SEQ_CNT
2
3
4
5
6
7
8
9
10
11
•
SEQ_ID Validity specifies whether the SEQ_ID field in the BA_ACC payload is valid or not. The drive always sets
this field to 00h.
•
SEQ_ID specifies the last SEQ_ID which is deliverable to the Upper Level Protocol. Since the drive uses the ABTS
protocol to abort an entire exchange, this field is unused. The drive sets this field to 00h.
•
OXID specifies the OXID of the exchange that has been aborted by the drive.
•
RXID specifies the RXID of the exchange that has been aborted by the drive.
•
Low SEQ_CNT specifies the last data frame of the last delivered sequence. Since the drive aborts the entire
exchange, this field is set to 0000h.
•
High SEQ_CNT is only valid when an ABTS is used to abort a single sequence. Since the drive only supports aborting of entire exchanges, this field is set to 0000h.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
58
17.2.3 Basic reject (BA_RJT)
BA_RJT indicates that a Basic Link Service Request has been rejected. The payload contains a four byte reason code to indicate why the request was rejected.
Table 38: BA_RJT Payload
Byte
Item
Size (Bytes)
0
Reserved
1
1
Reason Code
1
2
Reason Explanation
1
3
Vendor Unique
1
Table 39: BA_RJT Reason Codes
Code
Description
0000 0001
Invalid command code
0000 0011
Logical error
0000 0101
Logical busy
0000 0111
Protocol error
0000 1001
Unable to perform command requested
1111 1111
Vendor unique error
Others
Reserved
Table 40: BA_RJT Reason Code Explanations
Code
Description
0000 0000
No additional explanation
0000 0011
Invalid OX_ID-RX_ID combination
0000 0101
Sequence aborted, no Sequence information provided
Others
Reserved
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
59
17.3 Extended Link Services
For Extended Link Service frames, the Header TYPE field is set to 01h (Extended Link Service). R_CTL is either 22h
(Extended Link Data, Unsolicited Control) for a Request, or 23h (Extended Link Data, Solicited Control) for a Reply.
The first byte of the payload is the LS_Command and encodes the Request or Reply, as shown in Table 41 and Table 42.
Table 41: Extended Link Service replies
Code
Reply
Abbr.
02h
Accept
LS_ACC
01h
Link Service Reject
LS_RJT
Table 42 is a comprehensive list of all Extended Link Service commands supported by the drive.
Table 42: Extended Link Service requests
Code
Request
Abbr.
52h
Address Discovery
ADISC
60h
Fabric Address Notification
FAN
04h
Fabric Login
FLOGI
05h
Logout
LOGO
50h
Port Discovery
PDISC
03h
Port Login
PLOGI
20h
Process Login
PRLI
21h
Process Logout
PRLO
0Fh
Read Link Status
RLS
53h
Report Node Capabilities
RNC
78h
Report Node ID
RNID
12h
Re-instate Recovery Qualifier
RRQ
24h
Third Party Process Logout
TPRLO
Note: Only lists ELSs supported by the drive. Refer to FC-PH for a complete list of ELSs.
The code '11h' for the TEST ELS (not supported by the drive) is also used by the LIPxx frames that circulate during Loop Initialization. To differentiate these from a TEST ELS, the second byte of the payload must be examined and compared with
Table 43.
Note: PLDA 1.10 specifies: “Reserved FC-PH fields are not required to be checked for zeroes. Validity bits set to 0 remove
any requirement to check the corresponding field for zeroes (e.g., if F_CTL bit 3=0, receiving N_Ports are not required to verify that the parameter field in word 5 of the frame header contains zeroes).” As such, the drive does not validate 1) reserved FC
fields or 2) fields that are not reserved but are not valid for the current frame (as shown in the example above with F_CTL bit
3). This does not apply to any reserved field checking and testing within the FCP_CDB. These fields are checked as per ANSI
SCSI requirements.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
60
Table 43: Extended Link Service request 11h qualifiers
Code
Description
Abbr.
01h
Select Master
LISM
02h
Fabric Assign AL_PA
LIFA
03h
Previously Acquired AL_PA
LIPA
04h
Hard Assigned AL_PA
LIHA
05h
Soft Assigned AL_PA
LISA
06h
Report AL_PA Position Map
LIRP
07h
Loop AL_PA Position Map
LILP
If a Loop Initialization frame is received when the Port is not performing a Loop Initialization Procedure, it will be responded
to by an LS_RJT containing a reason code of “Command not supported” and a reason code explanation of “No additional
explanation”. This also applies to all unsupported link services, as defined by Table 42.
17.3.1 Link Service Accept (LS_ACC)
LS_ACC is used in response to an Extended Link Service Request. It indicates that the request has been completed.
The LS_ACC payload depends upon the Extended Link Service Request and is therefore described separately for each of the
following:
17.3.3 “Port Login (PLOGI)”
17.3.4 “Logout (LOGO)”
17.3.5 “Fabric Login (FLOGI)”
17.3.6 “Fabric Address Notification (FAN)”
17.3.7 “Port Discovery (PDISC)”
17.3.8 “Address Discovery (ADISC)”
17.3.9 “Process Login (PRLI)”
17.3.10 “Process Logout (PRLO)”
17.3.11 “Read Link Error Status Block (RLS)”
17.3.12 “Report Node Capabilities (RNC)”
17.3.13 “Re-instate Recovery Qualifiers (RRQ)”
17.3.14 “Third Party Process Logout (TPRLO)”
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
61
17.3.2 Link Service Reject (LS_RJT)
LS_RJT indicates that the Extended Link Service request has been rejected. The payload (shown in Table 44) contains a Reason Code and a Reason Explanation.
Table 44: LS_RJT payload
Byte
0
Item
Size (Bytes)
0100 0000h
4
4
Reserved
1
5
Reason Code (Table 45)
1
6
Reason Explanation (Table 46)
1
7
Vendor Unique
1
3
Table 45: LS_RJT reason codes
Code
Description
01h
Invalid command code
03h
Logical error
05h
Logical busy
07h
Protocol error
09h
Unable to perform command requested
0Bh
Command not supported
FFh
Vendor unique error
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
62
Table 46: LS_RJT reason code explanations
Code
Description
00h
No additional explanation
01h
Service Parm error - Options
03h
Service Parm error - Initiator Ctl
05h
Service Parm error - Recipient Ctl
07h
Service Parm error - Rec Data Field Size
09h
Service Parm error - Concurrent Seq
0Bh
Service Parm error - Credit
0Dh
Invalid Port Name
0Eh
Invalid Node/Fabric Name
0Fh
Invalid Common Service Parameters
19h
Command (request) already in progress
1Fh
Invalid N_Port identifier
29h
Insufficient resources to support Login
2Ah
Unable to supply requested data
2Ch
Request not supported
Note: Refer to FC-PH for a full list. Only the explanations relevant to supported Extended Link Services are shown.
17.3.3 Port Login (PLOGI)
PLOGI is used by the Initiator to register Service Parameters with the Target if Implicit Login is not being used (see 19.10.11,
“Mode Page 19h (Fibre Channel Port Control Page)” on page 184). The Target responds with an LS_ACC that has a payload
similar to the PLOGI but which contains the Targets parameters. This exchange of parameters establishes the operating environment between the Initiator and the Target.
PLOGI can also be issued by the Target when it is operating as a Public Loop Device. In this case, the Target uses a PLOGI to
establish the operating environment between it and the Fabric Name Server.
Bytes 1, 2, and 3, of the payload must be set to zeros. Otherwise, the drive will respond with an LS_RJT containing a reason
code of “Command not supported”, and a reason code explanation of 00h “No additional explanation”.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
63
Table 47: PLOGI_REQ/PLOGI_ACC payload
Byte
0-3
Item
Size (Bytes)
Request = 0300 0000h; Accept = 0200 0000h
4
Common Service Parameters
16
20 - 27
Port Name
8
28 - 35
Node Name
8
Class 1 Service Parameters
16
Class 2 Service Parameters
16
Class 3 Service Parameters
16
Reserved
16
Vendor Version Level
16
4
19
36
51
52
67
68
83
84
99
100
115
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
64
17.3.3.1 Common Service Parameters
The Common Service Parameters apply to all classes of service and are exchanged during Login. The table below defines the
applicability, by class as well as by PLOGI, FLOGI, PLOGI LS_ACC and FLOGI LS_ACC, of the Common Service Parameters to N_Port and Fabric Login. These are words 1-4 in the Payload..
Table 48: Common Service Parameter applicability (part 1 of 2)
Service parameter
Word
Bits
FLOGI LS_ACC
Parameter
applicability
FLOGI
PLOGI and
PLOGI LS_ACC Parameter
applicability
Parameter
applicability
Class
Class
Class
1*
2
3
4
1*
2
3
4
1*
2
3
4
FC-PH Version - Obsolete
1
31-16
n
n
n
n
n
n
n
n
n
n
n
n
Buffer-to-Buffer Credit
1
15-0
y
y
y
n
y
y
y
n
y
y
y
n
Common Features
2
31-16
Continuously increasing relative offset
2
31
y
y
y
y
n
n
n
n
n
n
n
n
Clean Address
2
31
n
n
n
n
n
n
n
n
y
y
y
y
Random relative offset
2
30
y
y
y
y
n
n
n
n
n
n
n
n
Valid Vendor Version Level
2
29
y
y
y
y
y
y
y
y
n
n
n
n
N_Port/F_Port
2
28
y
y
y
y
y
y
y
y
y
y
y
y
BB_Credit Management
2
27
y
y
y
y
y
y
y
y
n
n
n
n
E_D_TOV Resolution
2
26
y y y y
** ** ** **
n
n
n
n
y
y
y
y
Multicast supported by Fabric
2
25
n
n
n
n
n
n
n
n
y
y
y
y
Broadcast supported by Fabric
2
24
n
n
n
n
n
n
n
n
y
y
y
y
Hunt Group routing supported by Fabric
2
23
n
n
n
n
n
n
n
n
y
y
y
y
Simplex Dedicated Connection - Obsolete
2
22
n
n
n
n
n
n
n
n
n
n
n
n
Reserved for security
2
21
n
n
n
n
n
n
n
n
n
n
n
n
Clock Synchronization Primitive Capable
2
20
y
y
y
y
y
y
y
y
y
y
y
y
R_T_TOV Value
2
19
y
y
y
y
y
y
y
y
y
y
y
y
Dynamic Half Duplex Supported
2
18
y
y
y
y
y
y
y
y
y
y
y
y
SEQ_CNT
2
17
y
y
y
y
n
n
n
n
n
n
n
n
Payload bit
2
16
y
y
y
y
y
y
y
y
y
y
y
y
"y" indicates yes, applicable (i.e. has meaning)
"n" indicates no, not applicable (i.e. has no meaning)
* The Class 1 Service Parameters shall be used for Class 6. Each has the same applicability as Class 1.
** E_D_TOV resolution and the corresponding value are only meaningful in a point-to-point topology and when doing
PLOGI with an NL_Port on the same loop.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
65
Table 49: Common Service Parameter applicability (part 2 of 2)
Service parameter
Word
Bits
FLOGI LS_ACC
Parameter
applicability
FLOGI
PLOGI and
PLOGI LS_ACC Parameter
Parameter
applicability
applicability
Class
Class
Class
1*
2
3
4
1*
2
3
4
1*
2
3
4
BB_SC_N
2
15-12
y
y
y
n
y
y
y
n
y
y
y
n
Buffer-to-Buffer Receive Data Field Size
2
11-0
y
y
y
y
y
y
y
y
y
y
y
y
Nx_Port Total Concurrent Sequences
3
31-16
y
y
y
y
n
n
n
n
n
n
n
n
Relative offset by Info Category
3
15-0
y
y
y
y
n
n
n
n
n
n
n
y
R_A_TOV
3
31-0
n
n
n
n
n
n
n
n
y
y
y
y
E_D_TOV Value
4
31-0
y y y y
** ** ** **
n
n
n
n
y
y
y
y
"y" indicates yes, applicable (i.e. has meaning)
"n" indicates no, not applicable (i.e. has no meaning)
* The Class 1 Service Parameters shall be used for Class 6. Each has the same applicability as Class 1.
** E_D_TOV resolution and the corresponding value are only meaningful in a point-to-point topology and when doing
PLOGI with an NL_Port on the same loop.
The upper byte of the FC-PH Version field indicates the highest version of FC-PH that is supported and the lower byte indicates the lowest. The code/version relationship is shown in Table 50.
Table 50: FC-PH Version
Hex value
Version
00
None
06
FC-PH 4.0
07
FC-PH 4.1
08
FC-PH 4.2
09
FC-PH 4.3
10h
FC-PH-2
20h
FC-PH-3
Others
Reserved
The BB_Credit field indicates the number of frame buffers that a port guarantees to have immediately available when a loop
circuit is opened. The drive returns 0 (zero) in this field; i.e., every Initiator is given a Login BB_Credit of 0.
The Common Features field contains flags.
• CIO - Continuously Increasing Offset
When set to one, this flag indicates that the Port supports Continuously Increasing Relative Offset within a Sequence
on a frame by frame SEQ_CNT basis. The Relative Offset is only present if bit 3 of the F_CTL field in the frame
header is set to 1b. The drive requires that an initiator support Continuously Increasing Relative Offset. If this field is
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
66
not one, the drive will respond with an LS_RJT containing a reason code of 03h “Logical error”, and a reason code
explanation of 0Fh “Invalid Common Service Parameters”. The drive returns a 1b in this field.
• RRO - Random Relative Offset
When set to one, this flag indicates that the Port supports Random Relative Offset within a Sequence. The Relative
Offset is only present if bit 3 of the F_CTL field in the frame header is set to 1b. The drive returns a 0b in this field.
• VV - Valid Vendor Version Level
When set to one, this flag indicates that the Vendor Version Level field in the frame payload contains valid information. The drive returns a 0b in this field.
• N/F Port - N_Port/F_Port
When set to one, this flag indicates that the Port is an F_Port. When set to zero, it is an N_Port. The drive returns a 0b
in this field.
• ABCM - Alternate BB-Credit Model
When set to one, this flag indicates that the Port supports the Alternate BB-Credit model. The drive returns a 1b in
this field.
• E_D_TOV - E_D_TOV Resolution
When set to one, this flag indicates that the resolution of the E_D_TOV timer shall be 1 ns. When set to zero, the resolution shall be 1 ms. The flag is only applicable in a point to point topology. The drive returns a 0b in this field.
• DS - Dedicated Simplex
Only applies to class 1 service. The drive sets this field to 0b.
• DHD - Dynamic Half Duplex
When set to one, this flag indicates that the Port supports Dynamic Half Duplex. The drive returns a 0b in this field.
• SEQ_CNT - SEQ_CNT
When set to one, this flag indicates that the Port is guaranteeing that it will transmit all frames within an Exchange
using a continuously increasing SEQ_CNT. If set to zero, normal FC_PH rules regarding SEQ_CNT usage apply. The
drive returns a 0b in this field.
• PL - Payload Length
When set to one, this flag indicates that PLOGI Payload Length shall be 256 bytes. If set to zero, the flag specifies
that the normal 116 byte PLOGI Payload specified in FC-PH-2 is used. The drive returns a 0b in this field.
The Buffer-to-Buffer Receive Data_Field Size field (word 2, bits 11-0) specifies the largest FT_1 frame Data_Field Size that
may be received by the Nx_Port supplying the Service Parameters as a Sequence Recipient for:
a) a connect-request (SOFc1),
b) a Class 2 Data frame, or
c) a Class 3 Data frame
Values less than 256 or greater than 2 112 are invalid and shall be a multiple of four bytes. An Fx_Port shall support a Data
Field size of at least 256 bytes.
The Total Concurrent Sequences field indicates the number of concurrent sequences that the Port can support for all 3
classes. The value sent must be > 0, or the drive will respond with an LS_RJT with a reason code of 03h “Logical error” and a
reason code explanation of 09h “Service Parm error - Concurrent Seq”. The drive returns a value of FFh in this field.
The Relative Offset by Information Category field is all flags. The bit position of each set (1) bit determines the Information
Category; e.g., if Relative Offset is supported for category 0001b (Solicited Data), bit 1 is set. The drive returns a value of
0002h in this field (Relative Offset supported for Solicited Data only).
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
67
The E_D_TOV field specifies the E_D_TOV (Error Detect Timeout Value) in units of 1ns or 1ms. If the E_D_TOV Resolution bit is set to one, this field specifies E_D_TOV as a count of 1ns increments, otherwise it specifies E_D_TOV as a count of
1ms increments. It is only applicable in a point to point topology. The drive returns zero in this field. It is not interpreted or
checked.
17.3.3.2 Class Service Parameters
Since the drive only supports Class 3 service, it only checks and responds to the Class 3 Service Parameters.
Table 51: Class Service Parameters
Byte
BIT
7
6
5
4
3
2
1
0
Default
ACC
Values
68
CV
IM
TM
LDM
SD
DS
Camp-On
BufC1
80h
69
Priority
Reserved
00h
Initiator Control Flags (Bytes 70-71)
70
X_ID Reassign
71
DCHBS
IP Associator
DEC
ACK_0
ACK_N
CSC
ACK Gen
DCC
Reserved
00h
00h
Recipient Control Flags (Bytes 72-73)
72
ACK_0
Cap
73
DCC
74
ACK_N
Cap
(MSB)
X_ID Int.
DCHBS
EP Supported
DDC
Reserved
CSS
Categ. Per Sequence
00h
Reserved
00h
Receive Data-Field Size
75
76
(MSB)
(MSB)
(MSB)
(MSB)
00h
FFh
(LSB)
00h
00h
(LSB)
00h
01h
(LSB)
00h
00h
Open Sequences per Exchange
81
82
(LSB)
End-to-End Credit
79
80
08h
00h
Concurrent Sequences
77
78
(LSB)
Class 6 Multi-cast RX_ID
83
The Service Options field contains the following flags.
• CV - Class Validity
When set to one, this flag indicates that the class of service is supported. The drive only supports Class 3, thus this bit
is only set for the Class 3 Service Parameters. If this bit is not set for Class 3 Service Parameters, the drive will
respond with an LS_RJT containing a reason code of 03h “Logical error” and a reason code explanation of 01h “Service Parm error - Options”.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
68
• IM - Intermix Mode
The flag only applies to class 1 service and is reserved for classes 2 and 3. The drive returns 0b in this field.
• TM - Transparent Mode
The flag does not apply to PLOGI. The drive returns 0b in this field.
• LDM - Lock Down Mode
This flag does not apply to PLOGI. The drive returns 0b in this field.
• SD - Sequential Delivery
This flag does not apply to PLOGI. The drive returns 0b in this field.
• DS - Dedicated Simplex
This flag only applies to class 1 service. The drive returns 0b in this field.
• Camp-On - Camp-On
This flag only applies to class 1 service. The drive returns 0b in this field.
• BufC1 - Buffered Class 1
This flag only applies to class 1 service. The drive returns 0b in this field.
• Priority
This flag does not apply to class 3 service. The drive returns 0b in this field.
The Initiator Control flags specify which protocols, policies, or functions the supplier of the Service Parameters requests of
the recipient or is capable of.
• X_ID Reassign - X_ID Reassignment
00
X_ID Reassignment not supported.
01
X_ID Reassignment supported.
10
Reserved.
11
X_ID Reassignment required.
The X_ID Reassignment bits only apply to class 1 or 2 and therefore are not checked by the drive.
• IP Associator - Initial Process Associator
00
Initial Process Associator not supported.
01
Initial Process Associator supported.
10
Reserved.
11
Initial Process Associator required.
The drive accepts values of “00” and “01” in this field. If other values are sent, the drive responds with an LS_RJT
containing a reason code of 03h “Logical error” and a reason code explanation of 03h “Service Parm error - Initiator
Ctl”. The drive returns 00b in this field.
• ACK_0 - ACK_0 Capability
This flag does not apply to class 3 and therefore is not checked by the drive. The drive returns 0b in this field.
• ACK_N - ACK_N Capability
This flag does not apply to class 3 and therefore is not checked by the drive. The drive returns 0b in this field.
• ACK Gen - ACK generation assistance
This flag does not apply to class 3 and therefore is not checked by the drive. The drive returns 0b in this field.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
69
• DCC - Data compression capable
When set to one, this flag indicates the Port supports data compression as a Sequence Initiator. The drive does not
support data compression, therefore the drive returns 0b in this field.
• DCHBS - Data compression History buffer size
This field indicates the History buffer size supported by the Port as a Sequence Initiator. The drive does not support
data compression, therefore, the drive returns 00b in this field.
• DEC - Data encryption capable
When set to one, this flag indicates the Port supports data encryption as a Sequence Initiator. The drive does not support data compression, therefore the drive returns 0b in this field.
• CSC - Clock synchronization capable
When set to one, this flag indicates the Port is capable of performing clock synchronization as a Sequence Initiator
(Clock Synchronization Server). The drive is not capable of performing clock synchronization, therefore the drive
returns 0b in this field.
The Recipient Control flags specify which functions the supplier of the Service Parameters supports when receiving frames.
• ACK_0 Cap - ACK_0 Capability
This flag only applies to class 1 or 2, therefore is not checked by the drive. The drive returns 0b in this field.
• ACK_N Cap - ACK_N Capability
This flag only applies to class 1 or 2, therefore is not checked by the drive. The drive returns 0b in this field.
• X_ID Int. - X_ID Interlock
This flag only applies to class 1 or 2, therefore is not checked by the drive. The drive returns 0b in this field.
• EPS - Error Policy Supported
00
Only discard supported
01
Reserved
10
Both discard and process supported
11
Reserved
The Error Policy bits are not checked by the drive. The drive returns 00b in this field.
• Categ. per Sequence - Categories per Sequence
00
1 Category/Sequence
01
2 Categories/Sequence
10
Reserved
11
More than 2 Categories/Sequence. The drive returns 00b in this field.
The Receive Data Field size is the largest payload (in bytes) that the Port is capable of receiving. It must be less than or equal
to the Buffer to Buffer Receive Data Field specified in the Common Service Parameters. Sizes less than 128, greater than
2112, or not divisible by 4 are invalid, in which case the drive will respond with an LS_RJT containing a reason code of 03h
“Logical error” and a reason code explanation of 07h “Service Parm error - Rec Data Field Size”. The drive returns 2048 in
this field.
The Concurrent Sequences field specifies the number of separate Sequences that the drive is capable of tracking. The value
sent must be > 0, or the drive will respond with an LS_RJT containing a reason code of 03h “Logical error” and a reason code
explanation of 09h “Service Parm error - Concurrent Seq”. The drive returns a value of 255 in this field.
The End-to-end Credit field applies only to classes 1 and 2 and is therefore not checked by the drive. The drive returns 0 in
this field.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
70
The Open Sequences per Exchange field indicates the maximum number of Sequences per Exchange that can be open at the
recipient at one time. The value sent must be > 0, or the drive will respond with an LS_RJT containing reason code of 03h
“Logical error” and a reason code explanation of 00h “No additional explanation”. The drive returns 01b in this field.
The Class 6 Multicast RXID is used in Class 6 only and is therefore not checked by the drive. The drive returns 00b in this
field.
17.3.4 Logout (LOGO)
LOGO is used by an Initiator to request invalidation of the Service Parameters that were exchanged during PLOGI. If implicit
login is enabled by the settings in Mode Page 19, then the default Service Parameters apply. If no valid Service Parameters
exist for an Initiator, a LOGO_ACC is still returned.
Bytes 1, 2, and 3 of the payload must be set to zero. Otherwise, the drive will respond with an LS_RJT containing a reason
code of 0Bh “Command not supported” and a reason code explanation of 00h “No additional explanation”.
Table 52: LOGO payload
Byte
0-3
4
5-7
8
Item
Size (Bytes)
0500 0000h
4
Reserved
1
Port Identifier
3
Port Name
8
15
Table 53: LOGO ACC payload
Byte
0-3
Item
Size (Bytes)
0200 0000h
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
71
4
17.3.5 Fabric Login (FLOGI)
FLOGI is used by the drive to register its Service Parameters with the Fabric assuming the drive exists on a Public Loop (i.e.
the loop contains an FL_Port). Once the drive has completed FLOGI, it is then permitted to use the local FL_Port as a gateway,
allowing it to communicate with other N_Ports and NL_Ports attached to the fabric. (See 21.5, “Public Loop Operation” on
page 264.)
The drive performs a FLOGI by opening a full duplex connection to FL_Port located at AL_PA 00h and sending a FLOGI
request to the well-known address of FFFFFEh. The FL-Port responds to a valid request with a FLOGI Accept frame that contains the FL_Port’s operating parameters. The D-ID field of the FLOGI Accept frame contains the fabric assigned Domain,
Area, and the AL-PA of the drive performing the FLOGI. The drive uses this address in all further communication with other
N_Ports and Public NL_Ports. The drive will not perform a FLOGI if the drive fails to detect an FL_Port during Loop-Initialization.
Table 54: FLOGI_REQ/FLOGI_ACC payload
Byte
0-3
4
Item
Size (Bytes)
Request = 0400 0000h; Accept = 0200 0000h
4
Common Service Parameters
16
Port Name
8
Node Name
8
Class 1 Service Parameters
16
Class 2 Service Parameters
16
Class 3 Service Parameters
16
Reserved
16
Vendor Version Level
16
19
20
27
28
35
36
51
52
67
68
83
84
99
100
115
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
72
17.3.5.1 Common Service Parameters
The Common Service Parameters apply to all classes of service and are exchanged during Login.
Table 55: Common Service Parameters (FLOGI_REQ/FLOGI_ACC)
Byte
BIT
7
6
5
4
Default
Request
Values
3
2
1
0
4
PH Version - Highest Supported
20h
5
PH Version - Lowest Supported
20h
6
(MSB)
Buffer-to-Buffer Credit
7
(LSB)
8
Reserved
VV
9
10
N/F Port
Reserved
(MSB)
ABCM
Reserved
DHD
Reserved
12
00h
PL
BB Received Data Field Size
11
(LSB)
(MSB)
FLOGI_REQ = Reserved; FLOGI_ACC = R_A_TOV
13
(LSB)
14
00h
00h
00h
08h
00h
00h
00h
00h
00h
15
16
17
00h
00h
00h
00h
(MSB)
FLOGI_REQ = Reserved; FLOGI_ACC = E_D_TOV
18
(LSB)
19
The upper byte of the FC-PH Version field indicates the highest version of FC-PH that is supported and the lower byte indicates the lowest. The code/version relationship is given by Table 50.
The BB_Credit field indicates the number of frame buffers that a port guarantees to have immediately available when a loop
circuit is opened. The drive sets this field to 0 (zero); i.e., the drive grants the FL_Port a Login BB_Credit of 0.
The Common Features field contains the following flags:
• VV- Valid Vendor Version Level
When set to one, this flag indicates that the Vendor Version Level field in the frame payload contains valid information. The drive sets this field to 0b.
• N/F Port - N_Port/F_Port
When set to one, this flag indicates that the Port is an F_Port. When set to zero, it is an N_Port. The drive checks this
field in the FLOGI_ACC and will revert to PLDA behavior if it is not set to one. The drive sets this field to 0b.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
73
• ABCM - Alternate BB-Credit model
When set to one, this flag indicates that the Port supports the Alternate BB-Credit model. As per the FC-AL Specification, an L_Port and must support the Alternate BB-Credit model. The drive checks the value returned by the
FL_Port and will revert to PLDA behavior if it is not set to one. The drive sets this field to 1b.
• DHD - Dynamic Half Duplex
When set to one, this flag indicates that the Port supports the Dynamic Half Duplex. The drive sets this field to 0b.
• PL - Payload Length
When set to one, this flag indicates that FLOGI Payload Length shall be 256 bytes. If set to zero, the flag specifies
that the normal 116 byte FLOGI payload specified in FC-PH-2. The drive sets this field to 0b.
The Buffer to Buffer Receive Data Field size indicates the largest frame payload (in bytes) that the Port can receive. Sizes
less than 128, greater than 2112, or not divisible by 4 are invalid. The drive check this field in the FLOGI_ACC payload and
will revert to PLDA behavior if an invalid value is returned. The drive sets this field to 2048.
The R_A_TOV field specifies the R_A_TOV (Resource Allocation Timeout Value) supplied by the fabric in units of 1ms. The
fabric port sets this field in its FLOGI_ACC payload. This field is reserved in the FLOGI_REQ and the drive therefore sets
this field to zero. After FLOGI is complete, the drive will use this value for R_A_TOV until the drive is reset, reverts to PLDA
behavior, or performs another FLOGI.
The E_D_TOV field specifies the E_D_TOV (Error Detect Timeout Value) supplied by the fabric in units of 1ns or 1ms. The
fabric port sets this field in its FLOGI_ACC payload. This field is reserved in the FLOGI_REQ and the drive therefore sets
this field to zero. After FLOGI is complete, the drive will use this value for E_D_TOV until the drive is reset, reverts to PLDA
behavior, or performs another FLOGI.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
74
17.3.5.2 Class Service Parameters
Since the drive only supports class 3 service, it only checks and responds to the class 3 Service Parameters.
Table 56: Class Service Parameters
Byte
BIT
7
6
5
4
3
2
1
0
Default
Request
Values
68
CV
IM
TM
LDM
SD
DS
Camp-On
BufC1
80h
69
Priority
Reserved
00h
Initiator Control Flags (Bytes 70-71)
70
Reserved
00h
71
Reserved
00h
Recipient Control Flags (Bytes 72-73)
72
Reserved
00h
73
Reserved
00h
74
(MSB)
Receive Data-Field Size (Reserved)
75
76
(MSB)
(MSB)
(MSB)
00h
00h
(LSB)
00h
00h
(LSB)
00h
00h
(LSB)
00h
00h
Open Sequences per Exchange (Reserved)
81
82
(LSB)
End-to-End Credit (Reserved)
79
80
00h
00h
Concurrent Sequences (Reserved)
77
78
(LSB)
(MSB)
Class 6 Multi-cast RXID (Reserved)
83
The Service Options field contains the following flags:
• CV - Class Validity
When set to one, this flag indicates that the class of service is supported. The drive only supports class 3 thus this bit
is only set for the class 3 Service Parameters. If the FLOGI_ACC indicates that the fabric does not support class 3,
the drive will revert to PLDA behavior.
• IM - Intermix Mode
This flag only applies to class 1 service. It is reserved for classes 2 and 3. The drive sets this field to 0b.
• TM - Transparent Mode
This flag only applies to class 1 service. It is reserved for classes 2 and 3. The drive sets this field to 0b.
• LDM - Lock Down Mode
This flag only applies to class 1 service. It is reserved for classes 2 and 3. The drive sets this field to 0b.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
75
• SD - Sequential Delivery
The drive sets this field to 1b to request that the fabric deliver all frames in the same order they were transmitted. The
fabric sets this flag to 1b if it can honor this request. Since the drive does not support out of order frame delivery, the
drive checks the FLOGI_ACC to ensure that this field is set to 1b and will revert to PLDA behavior if it is not.
• DS - Dedicated Simplex
This flag only applies to class 1 service. The drive sets this field to 0b.
• Camp On - Camp-On
This flag only applies to class 1 service. The drive sets this field to 0b.
• BufC1 - Buffered Class 1
This flag only applies to class 1 service. The drive sets this field to 0b.
• Priority - Priority
This flag does not apply to class 3 service. The drive sets this field to 0b.
The Initiator Control Flags are not meaningful for FLOGI and are therefore reserved. The drive sets this field to 00h.
The Recipient Control Flags are not meaningful for FLOGI and are therefore reserved. The drive sets this field to 00h.
The Receive Data Field Size field is not meaningful for FLOGI and is therefore reserved. The drive sets this field to 00h.
The Concurrent Sequences field is not meaningful for FLOGI and is therefore reserved. The drive sets this field to 00h.
The End-to-End Credit field is not meaningful for FLOGI and is therefore reserved. The drive sets this field to 00h.
The Open Sequences per Exchange field is not meaningful for FLOGI and is therefore reserved. The drive sets this field to
00h.
The Class 6 Multi-cast RXID field is not meaningful for FLOGI and is therefore reserved. The drive sets this field to 00h.
17.3.6 Fabric Address Notification (FAN)
The FAN ELS is sent by an FL_Port to all previously logged in (FLOGI) NL_Ports after an initialization event has occurred.
An initialization event can be a LIP or any other event that may cause a Port to change its ID. The FAN ELS is used by
attached NL_Ports to validate their operating parameters with the local FL_Port after an initialization event has occurred. The
drive does not return a response to this ELS.
(Note: When operating as a private loop device, the drive will discard the FAN ELS request.)
Table 57: FAN payload
Byte
0-3
4
5-7
8
Item
Size (Bytes)
Command Code = 60000000h
4
reserved
1
Loop Fabric Address
3
Fabric Port Name
8
Fabric Name
8
-15
16
-23
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
76
The Command Code must be equal to 60000000h or the drive will ignore the request.
The Loop Fabric Address is the 3 byte Port_ID of the local FL_Port.
The Fabric Port Name is the world-wide-unique 8-byte Port_Name of the local FL_Port.
The Fabric Name is the world-wide-unique 8-byte name of the Fabric.
17.3.7 Port Discovery (PDISC)
An Initiator uses PDISC to exchange service parameters without affecting the operating environment between it and the drive.
The PDISC and corresponding ACC payloads are exactly as defined for PLOGI (see 17.3.3, “Port Login (PLOGI)” on page
63), except that byte 0 of the payload is 50h. It can be used as a means of authentication following a Loop Initialization process. If AL_PA's of the Initiator and Target have not changed since the previous login, the Initiator and Target can continue
where they left off prior to the LIP and all open exchanges will continue. If the current AL_PA's do not match the login values,
the drive will implicitly log out the Initiator.
If some means of authentication following a LIP does not occur within RR_TOV, the drive will implicitly log out the Initiator.
Bytes 1, 2, and 3 of the payload must be set to zero. Otherwise, the drive will respond with an LS_RJT containing a reason
code of 0Bh “Command not supported” and a reason code explanation of 00h “No additional explanation”.
17.3.8 Address Discovery (ADISC)
The ADISC ELS allows communicating N-Ports to exchange addresses and port/node name identifiers. It can be used as a
quick means of authentication following a Loop Initialization process. If the AL_PA's of the Initiator and Target have not
changed since the previous login, the Initiator and Target can continue where they left off prior to the LIP, and all open
exchanges will continue. If the current AL_PA's do not match the login values, the drive will implicitly log out the Initiator.
ADISC can also be used as a means to determine if a port was able to acquire its hard AL_PA during LIP.
Bytes 1, 2, and 3 of the payload must be set to zero. Otherwise, the drive will respond with an LS_RJT containing a reason
code of 0Bh “Command not supported” and a reason code explanation of 00h “No additional explanation”.
If some means of authentication following a LIP does not occur within RR_TOV, the drive will implicitly log out the Initiator.
The following tables show the ADISC payload and the ADISC ACC payload.
Table 58: ADISC payload
Byte
0-3
Item
Size (Bytes)
Command Code = 52000000h
4
4
Reserved
1
5
Hard Address of Originator
3
Port Name of Originator
8
Node Name of Originator
8
Reserved
1
N_Port ID of Originator
3
-7
8
-15
16
-23
24
25-27
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
77
Table 59: ADISC ACC payload
Byte
0-3
4
5-7
8
Item
Size (Bytes)
ACC Code = 02000000h
4
Reserved
1
Hard Address of Responder
3
Port Name of Responder
8
Node Name of Responder
8
Reserved
1
N_Port ID of Responder
3
-15
16
-23
24
25-27
Hard Address: This 3 byte identifier consists of:
•
The MSB is an 8-bit domain address. If the drive is acting as a Public Loop Device, it returns the domain address
given to it by the Fabric port during login. Otherwise the drive returns 0s in this field.
•
The middle byte is an 8-bit area address. If the drive is acting as a Public Loop Device, it returns the area address
given to it by the Fabric port during login. Otherwise the drive returns 0s in this field.
•
The LSB is the 8-bit AL_PA that the port attempts to acquire during the LIHA sequence of LIP. For the drive, this
number is calculated from the SEL-ID pins on the SCA-2 backplane connector.
When the Hard Address field is equal to the N_Port ID field, the port was able to obtain its hard address during LIP. The drive
does not check the value sent from the originator.
Port Name: IEEE unique address assigned during the manufacturing process.
Node Name: IEEE unique address assigned during the manufacturing process.
N_Port ID: This is the 24-bit NL_Port Identifier used in the S_ID of the ADISC Accept header. The lower 8 bits are the
AL_PA the drive acquired during loop initialization, and the upper 16 bits are the domain and area addresses the drive obtained
from the Fabric port. For private devices the upper two bytes should be all 0s. When this field matches the Hard Address field,
the drive was able to acquire its hard AL_PA during LIP.
17.3.9 Process Login (PRLI)
The PRLI request informs the recipient of the capabilities and requirements of the originator. The recipient responds with an
ACC to indicate agreement or LS_RJT otherwise.
Table 60: PRLI payload
Byte
Item
Size (Bytes)
0
20h
1
1
Page Length = 10h
1
Payload Length
2
2-3
4-max
Login service parameter pages
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
78
n*16
Table 61: PRLI ACC payload
Byte
Item
Size (Bytes)
0
02h
1
1
Page Length=10h
1
Payload Length
2
2-3
4-max
Login response service parameter pages
n*16
17.3.9.1 Process Login Service Parameter page
Table 62: Login Service Parameter page
Byte
Item
Size (Bytes)
0
TYPE Code = 08h
1
1
TYPE Code Extension = 00h
1
2-3
Flags
2
4-7
Originator Process Associator
4
8-11
Responder Process Associator
4
12-15
Service Parameters
4
The TYPE code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
The Flags field is as follows:
• Bit 15 - Originator Process Associator Valid
When set to one, the Originator Process Associator field for this Service Parameter page is valid.
• Bit 14 - Responder Process Associator Valid
When set to one, the Responder Process Associator field for this Service Parameter page is valid.
• Bit 13 - Establish Image Pair
When set to one, this flag indicates that the Originator wishes to establish an image pair.
• Bits 12-0 - Reserved
The Originator Process Associator identifies a group of related processes (an 'image') within the originator.
The Responder Process Associator identifies a group of related processes (an 'image') within the responder.
The Service Parameters field contains flags, as follows:
• Bits 31-7 - Reserved
• Bit 6 - Data Overlay Allowed
When set to one, this flag indicates that the initiator function is capable of supporting data overlay.
• Bit 5 - Initiator Function
When set to one, this flag indicates that the process defined by this page is operating as a SCSI Initiator.
This bit must be set to one in order for the drive to accept the login request. If not, the drive will respond with an
LS_RJT containing a reason code of 03h “Logical error” and a reason code explanation of 00h “No additional explanation”.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
79
• Bit 4 - Target Function
When set to one, this flag indicates that the process defined by this page is operating as a SCSI Target.
• Bit 3 - Command/Data Mixed Allowed
When set to one, this flag indicates that FCP_CMND and FCP_DATA may be combined in one IU.
• Bit 2 - Data/Response Mixed Allowed
When set to one, this flag indicates that FCP_DATA and FCP_RSP may be combined in one IU.
• Bit 1 - Read XFER_RDY Disabled
When set to one, this flag indicates that the FCP_XFER_RDY IU may not be used for SCSI READ operations.
• Bit 0 - Write XFER_RDY Disabled
When set to one, this flag indicates that the FCP_XFER_RDY IU may not be used for SCSI WRITE operations.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
80
17.3.9.2 Process Login Response Service Parameter page
Table 63: Login Response Service Parameter page
Byte
Item
Size (Bytes)
Drive Response
0
TYPE Code
1
08h
1
TYPE Code Extension
1
00h
2-3
Flags
2
21 00h
4-7
Originator Process Associator
4
00 00 00 00h
8-11
Responder Process Associator
4
00 00 00 00h
12-15
Service Parameters
4
00 00 00 12h
The TYPE Code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
The Flags field is as follows:
• Bit 15 - Originator Process Associator Valid
Since the drive does not support Process Associators, this bit must be set to zero in the payload. If not, the drive will
respond with a PRLI ACC response code of 07h. The drive returns 0b in this field.
• Bit 14 - Responder Process Associator Valid
Since the drive does not support Process Associators, this bit must be set to zero in the payload. If not, the drive will
respond with a PRLI ACC response code of 04h. The drive returns 0b in this field.
• Bit 13 - Image Pair Established
The drive returns a 1b in this field.
• Bit 12 - Reserved
• Bits 11-8 - Accept Response Code
See Table 64.
• Bits 7-0 - Reserved
The Originator Process Associator and Responder Process Associator fields are not used and will be set to
00000000h by the drive.
The Service Parameters field contains flags, as follows:
• Bits 31-6 - Reserved
• Bit 5 - Initiator Function
The drive returns 0b in this field.
• Bit 4 - Target Function
The drive returns 1b in this field.
• Bit 3 - Command/Data Mixed Allowed
The drive returns 0b in this field.
• Bit 2 - Data/Response Mixed Allowed
The drive returns 0b in this field.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
81
• Bit 1 - Read XFER_RDY Disabled
The drive returns 1b in this field.
• Bit 0 - Write XFER_RDY Disabled
The drive returns 0b in this field.
Table 64: PRLI/PRLO ACC response codes
Code
Description
00h
Reserved.
01h
Request executed.
02h
The target image has no resources available for establishing image pairs between the specified source and destination N_Ports. The PRLI request may be retried.
03h
Initialization is not complete for the target image. The PRLI request may be retried.
04h
The target image corresponding to the responder PA specified in the PRLI request and PRLI
accept does not exist. The PRLI request shall not be retried.
05h
The target image has a predefined configuration that precludes establishing this image pair.
The PRLI request shall not be retried.
06h
Request executed conditionally. Some service parameters were not able to be set to their
requested state. See the service parameters response field for further details.
07h
The destination N_Port is unable to process multiple page PRLI requests. The PRLI request
may be retried as a single page request.
08h-FFh
Reserved.
17.3.10 Process Logout (PRLO)
The PRLO request indicates to the responder that those process image pairs specified in the service parameter pages are being
discontinued by the originator. All tasks, reservations, mode page parameters and status for the specified image pairs are set to
the state they would have after a SCSI hard reset or power-on reset.
Table 65: PRLO payload
Byte
Item
Size (Bytes)
0
21h
1
1
Page Length=10h
1
Payload Length
2
2-3
4-max
Logout service parameter pages
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
82
n*16
Table 66: PRLO ACC payload
Byte
Item
Size (Bytes)
0
02h
1
1
Page Length=10h
1
Payload Length
2
2-3
4-max
Logout service parameter response pages
n*16
17.3.10.1 Process Logout Service Parameter page
Table 67: Logout Service Parameter page
Byte
Item
Size (Bytes)
0
TYPE Code = 08h
1
1
TYPE Code Extension = 00h
1
2-3
Flags
2
4-7
Originator Process Associator
4
8-11
Responder Process Associator
4
12-15
Reserved
4
The TYPE Code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
The Flags field is as follows:
• Bit 15 - Originator Process Associator Valid
When set to one, the Originator Process Associator field of this Service Parameter page is valid.
• Bit 14 - Responder Process Associator Valid
When set to one, the Responder Process Associator field of this Service Parameter page is valid.
• Bits 13-0 - Reserved
The Originator Process Associator identifies a group of related processes (an 'image') within the originator.
The Responder Process Associator identifies a group of related processes (an 'image') within the responder.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
83
17.3.10.2 Process Logout Response Service Parameter page
Table 68: Logout Response Service Parameter page
Byte
Item
Size (Bytes)
Drive Response
0
TYPE Code
1
08h
1
TYPE Code Extension
1
00h
2-3
Flags
2
0X 00h
4-7
Originator Process Associator
4
00 00 00 00h
8-11
Responder Process Associator
4
00 00 00 00h
12-15
Reserved
4
00 00 00 00h
The TYPE Code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
The Flags field is as follows:
• Bit 15 - Originator Process Associator Valid
The drive returns 0b in this field.
• Bit 14 - Responder Process Associator Valid
The drive returns 0b in this field.
• Bits 13-12 - Reserved
• Bits 11-8 - Accept Response Code
See Table 64.
• Bits 7-0 - Reserved
The Originator Process Associator and Responder Process Associator fields are not used.
17.3.11 Read Link Error Status Block (RLS)
RLS requests the recipient to return the Link Error Status Block associated with the Port Identifier specified in the payload.
The drive implements a Link Error Status Block for each port. When a counter overflows, it wraps back to zero. The only way
to reset the Link Error Status Block is to power off the drive.
Bytes 1, 2, and 3 of the payload must be set to zero. Otherwise, the drive will respond with an LS_RJT with a reason code of
“Command not supported” and a reason code explanation of “No additional explanation”.
Valid Port Identifiers are:
0
Return the Link Error Status Block for the same port on which the request was received.
1
Return the Link Error Status Block for Port A.
2
Return the Link Error Status Block for Port B.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
84
Table 69: RLS payload
Byte
0-3
4
5-7
Item
Size (Bytes)
0F00 0000h
4
Reserved
1
Port Identifier
3
Table 70: RLS ACC payload
Byte
0-3
4
Item
Size (Bytes)
0200 0000h
4
Link Error Status Block
24
-
27
Table 71: Link Error Status block
Byte
Item
Size (Bytes)
0-3
Link Failure Count
4
4-7
Loss of sync count
4
8-11
Loss of signal count
4
12-15
Primitive Sequence Protocol error
4
16-19
Invalid Transmission Word
4
20-23
Invalid CRC Count
4
The Drive's Link Error Status block is defined as follows:
Link Failure Count: This is a count of the number of times that the port's receiver loses synchronization for a continuous
period of time determined by RT_TOV. When a link failure condition is detected by the drive, it will remove itself from the
loop (i.e., enable its port bypass). It will then run a loopback diagnostic test. If the test passes, the drive assumes that its port is
good, and a condition outside of it caused the failure. In this case it will re-enable itself on the loop (i.e., reset its port bypass)
and transmit LIP (F8). If the loopback test fails, the drive assumes the failure is inside its own port and remains bypassed.
Loss of sync count: This is a count of the number of times that the port's receiver loses synchronization.
Loss of signal count: Not implemented.
Primitive Sequence Protocol error: Not implemented.
Invalid Transmission Word: This is a count of the number of times that the port detects an invalid transmission word on its
receiver.
Invalid CRC Count: This is a count of the number of frames received with invalid CRC. Only one invalid CRC is counted for
each command nexus.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
85
17.3.12 Report Node Capabilities (RNC)
The Report Node Capabilities (RNC) ELS is used to exchange node capabilities, vendor identification, and other vendor
unique information. It is used to discover which document identifiers (along with their associated FC-4 protocols and profiles)
a node supports. RNC can also be used to specify which document(s) define the operating parameters between two nodes, as
well as specify any additional parameters not specified during N_Port Login.
Table 72: RNC/ACC payload
Byte
Item
Size (Bytes)
0
53h for RNC, 02 for ACC
4
1
Reserved
1
Payload Length
2
RNC Flags
1
Reserved
2
7
VU Information Length (VU_Len)
1
8
Vendor Identifier
8
Capability Entry(s)
m
2-3
4
5-6
-15
16->
16+m->
Vendor Unique Information
0-128
Payload Length is a two byte unsigned integer that specifies the length of the RNC payload. The minimum length of the RNC
payload is 16 bytes, and its maximum length is limited to 256 bytes. While the maximum length of the ACC payload is not
defined, the drive limits its RNC_ACC to 256 bytes.
RNC Flags is a one byte field that defines options that are applicable to all Capability Entries contained in the RNC payload.
The RNC Flags field is as follows:
• Bit 7 - Select
When this flag is set to one, the RNC_ACC payload shall contain only one Capability Entry. This Capability Entry is
selected from the list of Capability Entries specified in the RNC payload. When this flag is set to zero, the RNC_ACC
payload shall contain all of the Capability Entries that a node wishes to report.
The drive does not support the Select Flag and this field must be set to zero. Otherwise, the drive will respond with
an LS_RJT containing a reason code of 03h “Logical error” and a reason code explanation of 2Ah “No additional
explanation”.
• Bits 6-0 - Reserved
The VU Information Length (VU_Len) field is a one byte unsigned integer, which specifies the length of the Vendor Unique
Information field. A maximum length of 128 bytes is supported.
The Vendor Identifier contains eight bytes of ASCII data, which identifies the vendor of the product.
Vendor Unique Information is defined by vendor or profile specific documentation.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
86
17.3.12.1 Capability Entry(s)
Capability Entry(s) are used to specify standards and profiles, with which a node is compliant or supports. Nodes may also use
capability entries to exchange vendor unique parameters or information.
Table 73: RNC Capability Entry
Byte
Item
Size (Bytes)
0
Flags
1
1
Document Identifier
1
2
Low Revision
1
3
High Revision
1
4-5
Reserved
0 or 2
6-7
Extension Length
0 or 2
8->
Extension
0 or n
The Flags field is as follows:
• Bit 7 – Invalidate Previous
This flag is only meaningful when the RNC Flags Select bit is set to one. Furthermore, it may only be set in the first
Capability Entry in the RNC Payload. When the RNC Flags Select field and the Invalidate Previous field are both set
to one, then the node issuing the RNC is requesting that the responding node invalidate this Capability Entry. All
bytes of the Capability Entry marked with the Invalidate flag must match the values set in a prior RNC exchange.
When the Invalidate Previous field is reset(0), the responding node selects one Capability Entry to return in the
RNC_ACC.
Since the drive does not support the Select Flag (it must be set to 0), the Invalidate Previous Flag has no meaning and
is ignored.
• Bit 6 – Extended
When this flag is set to zero, the Capability Entry shall be exactly 4 bytes long. If this flag is set to one, the length of
the Capability Entry is 4 bytes plus the length of the Extension.
• Bits 5-4 – Vendor Unique
• 0 0 Specifies that the Document Identifier field should be interpreted according to Table 74.
• 0 1 Specifies a Vendor Unique Document Identifier.
• 1 0 Specifies a Vendor Unique Document Identifier as defined by the vendor of the N_Port receiving
the RNC payload.
• 1 1 Reserved
• Bits 3-2 – Reserved
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
87
• Bits 1-0 - Preference
Preference is a two bit value that indicates the level of support or performance relative to the other capabilities supported by the node. It is used to aid a node in selecting a specific capability when multiple capabilities are supported.
The Preference field has a range from 0 to 3.
• 0 0 Best
•01
•10
• 1 1 Worst
The drive does not support the Preference field ignores it.
The Document Identifier field specifies which Profile or Standard is associated with each Capability Entry. Valid Document
Identifiers are listed in Table 74. If the Vendor Unique Flag is set to a value other than 00h, then the Document Identifier specifies a vendor unique capability.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
88
Table 74: Document Identifiers
Profile or standard name
Identifier
Supported
Reserved
00h
N
FC-LE
01h
N
FC-SB
02h
N
IPI-3
03h
N
SCSI-FCP
04h
Y
FC-FP
05h
N
06h-0Fh
N
FC-GS
10h
N
FC-FG
11h
N
FC-SW
12h
N
FC-AL
13h
Y
14h-1Fh
N
IBM/HP/Ancor FC-PH 4.2 Deviations
20h
N
FCSI Mixed Mode SCSI Profile
21h
N
FCSI Class 2 SCSI Profile
22h
N
FCSI IP Profile
23h
N
FCSI IP Class 2 Profile
24h
N
FC-PLDA – Private Loop Direct Attach
25h
Y
FLA Fabric Loop Attach Profile
26h
Y
FCA IP Profile
27h
N
28h-FFh
N
Reserved
Reserved
Reserved
The Low Revision field defines the lowest revision of the specified document supported. The field represents a decimal revision number between 0.0 and 25.5.
The High Revision field defines the highest revision of the specified document supported. The field represents a decimal revision number between 0.0 and 25.5.
The Extension Length field is a two byte unsigned integer that specifies the number of additional bytes present in the Capability Entry. This number includes itself, the preceding reserved field, and the length of Extension Field.
The Extension field is used to specify any additional bit flag, parameters, or other information defined by the document associated with the Capability Entry. The drive does not currently make use of Extension field, therefore all Capability Entries
returned by the drive are 4 bytes in length.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
89
17.3.13 Re-instate Recovery Qualifiers (RRQ)
The Re-instate Recovery Qualifier (RRQ) can be sent by the Initiator to the drive, as an indication that the Recovery Qualifier
(S_ID, D_ID, OX_ID, RX_ID, SEQ_ID, and SEQ_CNT) for an aborted exchange may be reused. RRQ is not required by the
drive following an aborted exchange. Following an ABTS the drive allows immediate reuse of the Recovery Qualifier. The
drive responds to RRQ with a valid ACC.
The following tables show the RRQ payload and the RRQ ACC payload.
Table 75: RRQ payload
Byte
0-3
Item
Size (Bytes)
Command Code = 12000000h
4
reserved
1
5-7
Originator S_ID
3
8-9
OX_ID
2
10-11
RX_ID
2
Association Header (Opt)
32
4
12
43
Table 76: RRQ ACC payload
Byte
0-3
Item
Size (Bytes)
ACC Code = 02000000h
4
The drive performs no protocol checking on the RRQ payload. When it recognizes an ELS with 12h in byte 0, it simply
responds with an RRQ ACC.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
90
17.3.14 Third Party Process Logout (TPRLO)
The TPRLO request is used to invalidate the operating environments between the specified image(s) at the recipient N_Port
(i.e., the drive). These image pairs being invalidated are assumed to have been previously established with a Process Login
(PRLI). The originator establishing the process image (with the PRLI ELS) can itself terminate the image with a Process
Logout (i.e. PRLO) ELS. An originator can terminate the process pair established between another third party originator and
the recipient (i.e. the drive) using TPRLO. TPRLO has the same effect as if the third party originator performed PRLO. Upon
execution of a valid TPRLO ELS, the drive will set all tasks, reservations, mode page parameters, and status for the specified
image pairs to the state they would have after a SCSI device reset or power-on reset.
Table 77: TPRLO payload
Byte
Item
Size (Bytes)
0
Command Code = 24h
1
1
Page Length = 10h
1
Payload Length = 14h
2
2-3
4-max
Logout service parameter pages
n*16
Table 78: TPRLO ACC payload
Byte
Item
Size (Bytes)
0
ACC Cmd Code = 02h
1
1
Page Length = 10h
1
Payload Length = 14h
2
2-3
4-max
Logout service parameter response pages
n*16
17.3.14.1 Third Party Process Logout Service Parameter page
Table 79: Logout Service Parameter page
Byte
Item
Size (Bytes)
0
TYPE Code = 08h
1
1
TYPE Code Extension = 00h
1
2-3
Flags
2
4-7
Third Party Originator Process Associator
4
8-11
Responder Process Associator
4
Reserved
1
Third Party Originator N_Port ID
3
12
13-15
The TYPE Code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
91
The Flags field is as follows:
• Bit 15 - Third Party Originator Process Associator Valid
When set to one, the Third Party Originator Process Associator field of this Service Parameter page is valid.
• Bit 14 - Responder Process Associator Valid
When set to one, the Responder Process Associator field of this Service Parameter page is valid.
• Bit 13 - Third Party Originator N_Port ID Valid
When set to one, the Third Party N_Port ID field of this Service Parameter page is valid.
• Bit 12 - Global Process Logout
When set to one, all established image pairs for all N_Ports with which Process Login has been performed will be
removed. This will be as if all N_Ports that had previously executed a Process Login (i.e. PRLI) with the drive had
now executed the PRLO ELS. When this bit is set, only one logout parameter page shall be transmitted, and only the
TYPE Code and the TYPE Code Extension fields shall have meaning.
• Bits 11-0 - Reserved
The Third Party Originator Process Associator identifies a group of related processes (an 'image') within the originator.
The Responder Process Associator identifies a group of related processes (an 'image') within the responder.
The Third Party N_Port ID specifies the N_Port associated with the image to be removed.
17.3.14.2 Third Party Process Logout Response Service Parameter page
Table 80: Logout Response Service Parameter page
Byte
Item
Size (Bytes)
Drive Response
0
TYPE Code
1
08h
1
TYPE Code Extension
1
00h
2-3
Flags
2
XX 00h
4-7
Third Party Originator Process Associator
4
00 00 00 00h
8-11
Responder Process Associator
4
00 00 00 00h
Reserved
1
00h
Third Party Originator N_Port ID
3
XX XX XXh
12
13-15
The TYPE Code field for SCSI-FCP is 08h, and the TYPE Code Extension field is 00h.
The Flags field is as follows:
• Bit 15 - Third Party Originator Process Associator Valid
The drive returns 0b in this field.
• Bit 14 - Responder Process Associator Valid
The drive returns 0b in this field.
• Bit 13 - Third Party Originator N_Port ID Valid
The drive will echo this bit from the TPRLO payload. It is not valid when the Global Process Logout flag is set to
one.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
92
• Bit 12 - Global Process Logout
The drive will echo this bit from the TPRLO payload.
• Bits 11-8 - Accept Response Code
See Table 64.
• Bits 7-0 - Reserved
The Originator Process Associator and Responder Process Associator fields are not used.
The drive will echo the Third Party N_Port ID field from the TPRLO request payload when the Third Party Originator
N_Port ID Valid Flag is set to one and the Global Process Logout Flag is set to zero.
17.3.15 Request Node Identification Data (RNID)
The Request Node Identification Data ELS provides a mechanism for a node to acquire Node Identification Data from other
nodes in a Fibre Channel fabric. This function is normally used by nodes that wish to determine the topology of the network to
which they are attached.
The normal response to a RNID Req is RNID ACC from the drive containing the requested Node Identification information.
RNID is available prior to LOGIN.
Table 81: “RNID payload” shows the RNID payload.
Table 81: RNID payload
Item
Size (Bytes)
hex ’78 00 00 00’
4
Node Identification Data Format
1
Reserved
3
The Node Identification Data Format specifies the format of Node Identification Data returned from the drive. Acceptable
values for this field are 00h (Common Node Identification Data only) or DFh (Topology Discovery data). If this field is set to
any other value, the drive will return a LS_RJT containing a reason code of 03h "Logical Error" and a reason code explanation
of 2Ah "No additional explanation".
Table 82: “RNID accept payload” shows the RNID ACC payload.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
93
Table 82: RNID accept payload
Item
Size Bytes
hex ’02 00 00 00’
4
Node Identification Data Format
1
Common Node-Identification-Data Length
1
Reserved
1
Specific Node-Identification-Data Length
1
Common Node Identification Data
0 or 16
Specific Node Identification Data
0-max
The Node Identification Data Format specifies the format of Node Identification Data returned from the drive. The drive
sets this field to the same value that was in the RNID Request.
The Common Node-Identification-Data Length specifies the length of the Common Node-Identification-Data. This field is
set to 10h.
The Specific Node-Identification-Data Length specifies the length of the Specific Node-Identification-Data. This field is set
to 34h if the Node Identification Data Format was set to DFh (Topology Discovery Data) or 0h otherwise.
Common Node-Identification-Data specifies the port’s 8-byte Node_Name and 8-byte Port_Name. The format is defined in
Table 83: “Common Node Identification Data” .
Table 83: Common Node Identification Data
Format
Size (Bytes)
N_Port_Name
8
Node_Name
8
The Specific Node-Identification-Data specifies Topology Discovery Data whose format is described in Table 84: “Topology Discovery Specific Node Identification Data” . This Data is only returned when the Node Identification Data Format is
set to DFh "Topology Discovery Data".
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
94
Table 84: Topology Discovery Specific Node Identification Data
Format
Size (Bytes)
Global ID
16
Unit Type
4
Physical Port Number
4
Number of Attached Nodes
4
IP Version
2
UDP Port Number
2
IP Address
16
Reserved
2
Topology Discovery Flags
2
The Global ID field is a World Wide unique name whose format is identical to the Common Node-Identification-Data field as
specified in the table.
The Unit Type field specifies the type of device returning the Node-Identification-Data. Valid values for this field are shown
in Table 85: “Topology Discovery Unit Type” .
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
95
Table 85: Topology Discovery Unit Type
Value - hex
Type
’00 00 00 00’
Reserved
’00 00 00 01’
Unknown
’00 00 00 02’
Other (none of the following)
’00 00 00 03’
Hub
’00 00 00 04’
Switch
’00 00 00 05’
Gateway
’00 00 00 06’
Converter
’00 00 00 07’
HBA
’00 00 00 08’
Proxy-agent
’00 00 00 09’
Storage device (disk, CD, tape, etc.)
’00 00 00 0A’
Host
’00 00 00 0B’
Storage subsystem (raid, library, etc.)
’00 00 00 0C’
Module (subcomponent of a system)
’00 00 00 0D’
Software driver
’00 00 00 0E’ ’FF FF FF FF’
Reserved
The drive returns a value of 9h in this field.
The Physical Port Number specifies the port that received the RNID REQ. Valid values are 00h if the RNID was received on
port A and 01h if the RNID was received on port B.
The Number of Attached Nodes field specifies the number of nodes attached to the node returning the RNID ACC. Since the
drive does not perform any topology discovery, it sets this field to 0h.
The IP Version field specifies the level of IP supported. Since the drive does not support the IP protocol, it sets this field to 0h.
The UDP Port field specifies the numerical value that identifies a port using the User Datagram Protocol. Since the drive does
not support UDP, it sets this field to 0h.
The IP Address specifies the IP address of the node. Since the drive does not support IP, this field is set to 0h.
The Topology Discovery Flags (TDF) are defined in Table 86: “Topology Discovery Flags” .
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
96
Table 86: Topology Discovery Flags
Byte
BIT
7
6
5
0
4
3
2
Reserved
1
Default
request
values
0
TDF
000h
The Topology Discovery Support flag signals that the node supports further Topology Discovery inquiries. This flag is set to
0 by the drive.
The Loop Position Valid flag indicates that multiple Node Identification Data records are reported in the order detected by a
Loop Position Report Primitive. The drive returns only a single Node Identification Data record and sets this flag to 0.
17.4 Common Fibre Channel Services
Common Fibre Channel Service Request uses the Common Transport (CT) Interface to communicate with FC Fabric Servers.
The CT interface provides several Information Units, (CT_IU)s, which provide the transport mechanism between service
requestors and their servers.
In CT_IU frames, the TYPE field in the frame header is set to 20h (Fibre Channel Service). R_CTL is either 02h (FC-4
Device_Data, Unsolicited Control) for a Request or 03h (FC-4 Device_Data, Solicited Control) for a Reply.
Each CT_IU payload starts with a 16 byte CT Header as shown in Table 87.
Note: Common FC Services are used to communicate with the Fabric Name Server and are only issued by the drive when it is
operating as a Public Loop Device.
Table 87: Payload of a CT Header
Byte
Item
Size (Bytes)
0
FC_CT
1
1-3
IN_ID
3
4
FCS_Type
1
5
FCS_Subtype
1
6
Options
1
7
Reserved
1
Command/Response Code
2
Maximum/Residual Size
2
12
Reserved
1
13
Reason Code
1
14
Reason Code Explanation
1
15
Vendor Unique
1
8-9
10-11
The FC_CT field contains the FC_CT revision. The drive always sets this value to 0x01.
IN_ID is a reserved field that may be used to carry the S_ID of the original requestor between different servers in the fabric.
Its value in the FC_ACC/FC_FJT frame may be non zero if it was used.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
97
The FCS_Type indicates which FC Service is requested and the FCS_Subtype specifies which server will process the
request. The drive does not check the FCS_Type/FCS_Subtype values returned by the Name Server in the FS_ACC/FS_RJT.
The Options field specifies various options used during FCS processing. The drive sends a value of 0x00, which specifies that
this request must complete before another can be attempted.
The Command/Response Code field identifies specific Fibre Channel Service Information Units (FS_IUs). The Command/
Response Code also determines the type of FS_IU. Command codes are as shown in Table 88.
Table 88: Command/Response Codes
Value
Description
0000h
Non-(FS_IU)
0001h - 7FFFh
Fibre Channel Service Requests (FS_REQ)
8001h
Fibre Channel Service Reject (FS_RJT)
8002h
Fibre Channel Service Accept (FS_ACC)
other values
Reserved
The drive supports only the Command code of 0217h, which specifies a RFT_ID request.
The Maximum/Residual Size field is used by the sender of an FS_REQ to indicate the maximum number of bytes it can
accept in an FS_ACC payload. If the size of the responder’s FS_ACC payload is greater than this value, the responder will
transfer only the number of bytes requested and set the Maximum/Residual field in the FS_ACC to the number of residual
bytes that were not transferred.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
98
17.4.1 Register FC-4 Types (RFT_ID)
The drive uses RFT_ID to register its FC-4 type, (SCSI-FCP), with the Fabric Name Server. An RFT_ID request is sent to the
well-know address FFFFFCh (Fabric Name Server) and must be attempted after a successful FLOGI.
Table 89: RFT_ID payload
Byte
Item
Size (Bytes)
CT_IU Header
16
16
Reserved
1
17
19
S_ID of sending NL_Port
3
20
Supported FC-4 types bit map: byte 22 = 0x01, all others = 0x00
32
0
15
51
As with all Common Transport requests, the payload of an RFT_ID starts with the CT_IU header. The FCS_Type value of the
CT_IU Header is set to FCh to indicate a Directory Service Request, while the FCS_Subtype value is set 02h to indicate that
the request is directed to the Name Server. The Command code is set to 0217h to specify an RFT_ID request. For an
RFT_ID_ACC/RJT, the Command/Response code is set to 8001h for a RFT_ID_RJT and 8002h for RFT_ID_ACC. If the
response was a FA_RJT, the Reason Code, Reason Code Explanation, and Vendor Unique fields would be set to indicate which
error condition occurred. The drive does not check any other fields in an FS_ACC/RJT payload.
The Supported FC-4 Bitmap indicates which FC-4 protocols the RFT_ID requestor supports. The drive sets the eighth bit of
this bitmap to indicate that it supports FC-4 type 08h (SCSI-FCP).
Table 90: RFT_ID ACC/RJT payload
Byte
0
Item
Size (Bytes)
CT_IU Header
16
15
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
99
Table 91: FS_RJT Reason Codes
Encoded value Description
0000 0001
Invalid command code
0000 0010
Invalid version level
0000 0011
Logical error
0000 0100
Invalid IU size
0000 0101
Logical busy
0000 0111
Protocol error
0000 1001
Unable to perform command request
0000 1011
Command not supported
others
1111 1111
Reserved
Vendor Unique Error
Table 92: FS_RJT Reason Explanations
Encoded value Description
00
No additional explanation
01
Port Identifier not registered
02
Port Name not registered
03
Node Name not registered
04
Class of Service not registered
05
IP address not registered
06
Initial Process Associator not registered
07
FC-4 TYPEs not registered
08
Symbolic Port Name not registered
09
Symbolic Node Name not registered
0A
Port Type not registered
10
Access Denied
11
Unacceptable Port Identifier
12
Data base empty
Others
Reserved
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
100
17.5 FC-AL timers
Table 93: FCAL timer values
Timer
Description
Value
(PLDA/FLA)*
AL_TIME
LIS_HOLD_TIME
Arbitrated Loop Timeout Value
15 ms
Loop Initialization Sequence Hold Time
1 ms
R_T_TOV
Receiver Transmitter Timeout Value
100 ms
E_D_TOV
Error Detect Timeout Value
2 sec./2 sec.*
R_A_TOV
Resource Allocation Timeout Value
2 sec./10 sec.*
RR_TOV
Resource Recovery Timeout Value
2 sec.
LP_TOV
Loop Timeout Value
2 sec.
The drive uses FCAL timers as specified in PLDA 2.1 as required in the standard.
• AL_TIME
AL_TIME represents two times the worst case round trip latency for a very large loop.
• LIS_HOLD_TIME
LIS_HOLD_TIME is the maximum amount of time between when a node receives a Loop Initialization Sequence
until it forwards it to the next node.
• R_T_TOV
R_T_TOV is used by the receiver logic to detect a Link Failure. A Link Failure is defined as loss of synchronization
for a period greater than R_T_TOV.
• E_D_TOV
E_D_TOV is the minimum time a port shall wait for the next expected frame in a sequence before detecting an error.
• R_A_TOV
R_A_TOV is defined by the PLDA to be two distinct timers.
• R_A_TOVSEQ_QUAL defines the minimum time a port shall wait before reuse of the sequence qualifiers SEQ_CNT
and SEQ_ID. The PLDA defines the value of R_A_TOVSEQ_QUAL to be zero seconds.
Twice the value of R_A_TOVELS defines the minimum time a port shall wait for the response to an Extended Link
Service Request. The PLDA defines this value to be two seconds. Therefore a port must wait twice this value (four
seconds) before timing out an ELS.
Note: In the FLA, there is no split definition of the R_A_TOV value. One timer value is used for both
R_A_TOVSEQ_QUAL and R_A_TOVELS.
• RR_TOV
RR_TOV is the minimum time a target shall wait for an Initiator to perform exchange authentication following LIP. If
this timer expires, the Target will implicitly log out the Initiator and free up the resources associated with that timer.
An RR_TOV timer is maintained for each Initiator that has logged in.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
101
• LP_TOV
LP_TOV is used to keep a Loop from deteriorating due to protocol errors or lost Ordered Sets.
LP_TOV is also used during initialization and to reset the fairness window.
17.5.1 Link Failure
Link Failure is defined when a receiver has continuously detected loss of synchronization for a period of R_T_TOV.
When this occurs, the port will bypass itself and run a loopback test. If the loopback test passes, the port assumes that
it is not the cause of the loop failure, and it resets its bypass circuit and transmits a LIP(F8). When it receives its own
LIP(F8), the drives assumes the loop is now intact and issues a LIP(F7). If the port’s loopback test fails, it assumes
that it was the cause of the loop failure, and it remains in the bypassed state.
17.6 Invalid frame delimiter
If an invalid frame delimiter is received for a:
•- FCP_DATA frame, the exchange shall terminate with a CHECK CONDITION status. The resulting Sense data will
have the Sense Key set to Aborted command and the Additional Sense Code set to Data Phase Error.
•- non-FCP_DATA frame, the frame shall be discarded and ignored.
Hitachi Ultratstar 15K147 FC-AL Hard Disk Drive Specification
102
18.0 SCSI-FCP
This section describes the drive’s implementation of SCSI-FCP. SCSI-FCP is the FC-4 mapping recommended by the Disk
Profile. It maps the ANSI SCSI protocol onto the FC-PH functions.
Note: PLDA 2.1 specifies: “Reserved FC-PH fields are not required to be checked for zeroes. Validity bits set to 0 remove any
requirement to check the corresponding field for zeroes (e.g., if F_CTL bit 3=0, receiving N_Ports are not required to verify
that the parameter field in word 5 of the frame header contains zeroes).” As such, the drive does not validate 1) reserved FC
fields or 2) fields that are not reserved but are not valid for the current frame (as the example above with F_CTL bit 3). This
does not apply to any reserved field checking and testing within the FCP_CDB. These fields are checked as per ANSI SCSI
requirements.
18.1 Terminology
The SCSI Architecture Model (SAM) defines a new SCSI vocabulary in order to remain independent from physical protocol
and interconnect. Common SCSI-2 terms have been replaced and new ones introduced.
As might be expected, the terminology used to describe SCSI-FCP is a problem. It needs elements of SAM and Fibre Channel.
Most of the Fibre Channel terms have been introduced in 1.0, “FC-AL Attachment”, and some essential SAM terms are covered here. However, SAM is still recommended reading!
SCSI-FCP describes all communication in terms of Fibre Channel Information Units (IUs). FC-PH defines these simply as
"sequences that have special meaning to the FC-4" (i.e. SCSI-FCP).
IUs are used to send commands, data, and status; bus phases are part of parallel SCSI and no longer exist. Execution of a command requires several IUs to pass between theTarget and Initiator so an I/O Process (IOP) equates to a Fibre Channel
exchange. In fact, the exchange ID is used as the command tag.
An IOP is represented in the Target by a Task. The Initiator uses Task Management functions to control execution of the task
in the Target. IUs are used to transfer Task Management functions.
SAM defines a Target as consisting of a Task Manager and one or more Logical Units. The Task Manager handles all the Task
Management functions and the logical unit handles commands.
The logical unit consists of a Target and a Task Set. The Target actually executes the commands and the task set is simply what
used to be known as the Command Queue.
SCSI-FCP recognizes that Targets and Initiators may simply be software procedures and therefore calls them Processes.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
103
18.2 Information Units
SCSI-FCP defines a number of IUs that are used to describe the mapping of SAM Device and Task Management functions.
The Disk Profile defines an 'FCP Feature Set', which is a subset of those IUs.
This section defines the IUs implemented by the drive (see Table 94).
Table 94: Information Units (IUs)
IU
SAM primitive
Data block
CAT
Content
F/M/L
SI
M/O
T1
Command Request
6
FCP_CMND
F
T
M
T6
Data Out action
1
FCP_DATA
M
T
M
I1
Data delivery request
5
FCP_XFER_RDY (WRITE)
M
T
M
I3
Data In action
1
FCP_DATA
M
H
M
I4
Response
7
FCP_RSP
L
T
M
Note:
Key:
SAM
= SCSI-3 Access Method
IU
= Information Unit
CAT
= Information category of Device_Data frame
F/M/L = First/Middle/Last IU of Sequence
SI
= Sequence Initiative
H
= Hold Sequence Initiative
T
= Transfer Sequence Initiative
M/O
= Mandatory/Optional
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
104
18.2.1 FCP_CMND
The FCP_CMND IU carries either a SCSI command to be executed or a Task Management function to be performed.
Table 95: FCP_CMND payload
Byte
Field
Description
Size (Bytes)
0
FCP_LUN
Logical Unit Number
8
8-11
FCP_CNTL
Control Field
4
12
FCP_CDB
SCSI Command Descriptor Block
16
Data Length
4
-7
27
28-31
FCP_DL
18.2.1.1 FCP_LUN
The FCP_LUN field identifies the logical unit number within the Target. The drive is a single LUN with address 0000 0000
0000 0000h.
18.2.1.2 FCP_CNTL
The FCP_CNTL field contains a number of control flags.
Table 96: FCP_CNTL field
Byte
Description
Size (Bytes)
0
Reserved
1
1
Task Codes
1
2
Task Management function flags
1
3
Execution management codes
1
The Task Codes field contains the Task Attributes, as shown in Table 97. The Task Attributes are described in 18.3, “Task
Attributes”, on page 109.
Table 97: Task Attribute values
Value
Attribute
xxxx x000b
Simple_Q
xxxx x001b
Head_of_Q
xxxx x010b
Ordered_Q
xxxx x100b
ACA_Q (not supported)
xxxx x101b
Untagged
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
105
The Task Management Function flags are used to request Task Management functions, as shown in Table 98. The Task Management functions are described in 18.4, “Task Management functions”, on page 110.
Table 98: TMF flag values
Value
Function
1000 0000b
Terminate Task
0100 0000b
Clear ACA (not supported)
0010 0000b
Target Reset
0000 0100b
Clear Task Set
0000 0010b
Abort Task Set
The Execution management codes field contains flags, as follows:
Bits 7-2 - Reserved
Bit 1 - Read Data
When set to one, this flag indicates that the Initiator expects FCP_DATA IUs for the task to be in the direction opposite to the direction of the FCP_CMND IU. This is a SCSI READ type operation.
Bit 0 - Write Data
When set to one, this flag indicates that the Initiator expects FCP_DATA IUs for the task to be in the same direction
as the FCP_CMND IU. This is a SCSI WRITE type operation.
18.2.1.3 FCP_CDB
The FCP_CDB field contains the SCSI CDB to be executed by the addressed logical unit. This field is ignored if any of the
Task Management function flags are set.
This is a 16-byte field. Bytes beyond the end of the CDB are ignored by the Target and may have any value.
18.2.1.4 FCP_DL
The FCP_DL field contains a count of the greatest number of data bytes expected to be transferred by execution of the SCSI
CDB. An FCP_DL field of zero indicates that no data transfer is expected and that no FCP_XFER_RDY or FCP_DATA IUs
shall be transferred.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
106
18.2.2 FCP_XFER_RDY
The FCP_XFER_RDY IU indicates that the Target is prepared to perform all or part of the data transfer for a command.
During WRITE operations, the FCP_XFER_RDY IU indicates the amount of data that the Target expects from the Initiator.
Since the Target has planned buffer resources based on that amount of data, the Initiator is expected to provide exactly the
amount requested.
Table 99: FCP_XFER_RDY payload
Byte
Field
0-3
DATA_RO
4-7
BURST_LEN
8-11
Reserved
Description
Size (Bytes)
Relative Offset
4
Length of FCP_DATA IU that follows
4
4
The DATA_RO field indicates the contents of the RLTV_OFF field for the first data byte of the next FCP_DATA IU. The
RLTV_OFF field is part of the frame header.
The BURST_LEN field indicates the amount of buffer space prepared for the next FCP_DATA IU and requests an IU of that
exact length.
18.2.3 FCP_DATA
SCSI data transfers may be performed by one or more data delivery requests, each one performing a transfer no longer than the
maximum burst length defined by the parameters of the disconnect/reconnect mode page.
18.2.4 FCP_RSP
The content of the FCP_RSP IU is as shown in Table 100.
Table 100: FCP_RSP payload
Byte
Field
0
Reserved
Description
Size (Bytes)
8
-7
8-11
FCP_STATUS
Field Validity and SCSI Status
4
12-15
FCP_RESID
Residual Count
4
16-19
FCP_SNS_LEN
Length of FCP_SNS_INFO field
4
20-23
FCP_RSP_LEN
Length of FCP_RSP_INFO field
4
24->
FCP_RSP_INFO
FCP Response Information
m
24+m->
FCP_SNS_INFO
SCSI Sense Information
n
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
107
18.2.4.1 FCP_STATUS
The FCP_STATUS field is normally zero upon successful completion of an IOP.
Table 101: FCP_STATUS field
Byte
0-1
Description
Size (Bytes)
Reserved
2
2
Flags
1
3
SCSI Status byte
1
The Flags field contains the following:
Bits 7-4 - Reserved
Bit 3 - FCP_RESID_UNDER
When set to one, this flag indicates that the FCP_RESID field is valid and contains a count of the number of bytes
that were expected but not received.
Bit 2 - FCP_RESID_OVER
When set to one, this flag indicates that the FCP_RESID field is valid and contains a count of the number of bytes
that could not be transferred because FCP_DL was not sufficient.
Bit 1 - FCP_SNS_LEN_VALID
When set to one, this flag indicates that the FCP_SNS_LEN field is valid and contains a count of the number of bytes
in the FCP_SNS_INFO field.
Bit 0 - FCP_RSP_LEN_VALID
When set to one, this flag indicates that the FCP_RSP_LEN field is valid and contains a count of the number of bytes
in the FCP_RSP_INFO field.
The SCSI Status byte field is defined in 20.0, “SCSI Status Byte”, on page 259.
18.2.4.2 FCP_RESID
This field contains a count of the number of residual data bytes that were not transferred for this SCSI command.
18.2.4.3 FCP_SNS_LEN
This field contains a count of the number of valid bytes in the FCP_SNS_INFO field.
18.2.4.4 FCP_RSP_LEN
If the FCP_RSP_LEN_VALID flag in the FCP_STATUS field is set to 1b, this field contains a count of the number of valid
bytes in the FCP_RSP_INFO field.
Valid values are 0, 4, and 8.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
108
18.2.4.5 FCP_RSP_INFO
This field contains information describing only the protocol failures detected during the execution of an IOP.
Table 102: FCP_RSP_INFO field
Byte
0-2
3
Description
Size (Bytes)
Reserved
3
RSP_CODE
1
The content of the RSP_CODE field is defined below.
Table 103: RSP_CODE definitions
Code
Description
00h
No Failure (Function Complete)
01h
FCP_DATA length different from BURST_LEN
02h
FCP_CMND Fields Invalid
03h
FCP_DATA_RO mismatch with FCP_XFER_RDY DATA_RO
04h
Function Rejected
05h
Service Delivery or Target Failure
06-FFh
Reserved
18.2.4.6 FCP_SNS_INFO
This field contains the Sense information specified by SCSI (see 22.1, “SCSI Sense Data Format”, on page 301).
FCP_SNS_INFO is only returned if the SCSI Status byte in the FCP_STATUS field is set to CHECK CONDITION status.
Refer to 18.5.3, “Autosense”, on page 113 for more details.
18.3 Task Attributes
Task Attributes are specified in the Task Codes field of the FCP_CMND IU. They apply only to the SCSI command contained
within the FCP_CDB field and are ignored if any of the Task Management function flags are set.
A task shall have one of the following attributes:
Simple Queue
This attribute specifies that the task shall be accepted into the task set and executed after tasks with the Head of
Queue attribute and tasks with the Ordered attribute that were received earlier. The order of execution, with respect to
other tasks with the Simple attribute, is determined by the Queue Algorithm currently in effect. Refer to the Queue
Algorithm Modifier field in 19.10.9, “Mode Page 0A (Control Mode Page Parameters)”, on page 180.
Head of Queue
This attribute specifies that the task shall be accepted into the task set and executed next. Successive tasks received
with Head of Queue attribute will be executed in LIFO order.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
109
Ordered Queue
This attribute specifies that the task shall be accepted into the task set and executed in the order received. All tasks
received earlier shall complete before this task. All tasks received later shall complete after this task, except for tasks
received with Head of Queue attribute.
Untagged
This attribute specifies that the task shall be accepted into the task set according to the rules for an untagged task.
Only one untagged task can exist for each logical unit/Initiator pair. A second untagged task for the same pair is
treated as an overlapped command. SCSI-FCP commands are inherently tagged with the OXID/RXID specified in
the frame header. Therefore, commands sent with the untagged task attribute are handled as if they had the Ordered
Queue attribute.
Note: The uncoupled nature of FCAL makes it impossible for the drive to perform command overlap checking. (See
Section 21.6.3 "Overlapped Commands")
18.4 Task Management functions
Task Management functions allow an Initiator to explicitly control the execution of one or more Tasks. SAM defines the following:
•
Abort Task (Implemented as ABTS BLS)
•
Abort Task Set
•
Reset LUN
•
Clear ACA (not supported)
•
Clear Task Set
•
Target Reset
•
Terminate Task
Note: The following description applies to all Task Management functions except Abort Task, which is described separately in
18.4.1, “Abort Task (Implemented as ABTS BLS)”, on page 111.
Task Management functions are transmitted in a new exchange using a T1 FCP_CMND IU (see 18.2.1, “FCP_CMND”, on
page 105). The Task Management function flags in the IU specify the required function. If any flag is set, all CDB related
fields of the IU are ignored (FCP_CDB, FCP_DL, the Task Codes and Execution Management fields of FCP_CNTL). Only
one Task Management function flag may be set.
The Target responds to a Task Management function with an I4 FCP_RSP IU (see 18.2.4, “FCP_RSP”, on page 107). The
RSP_CODE in the FCP_RSP_INFO field shall be as shown in Table 104 and all other fields shall be zeroes.
Table 104: Task Management function RSP_CODE definitions
Code
Description
00h
No Failure (Function Complete)
04h
Function Rejected
05h
Service Delivery or Target Failure
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
110
18.4.1 Abort Task (Implemented as ABTS BLS)
The Abort Task function is performed using the FC-PH link management functions. Specifically, the Abort Sequence (ABTS)
Basic Link Service (BLS). Refer to 17.2.1, “Abort sequence (ABTS)”, on page 57 for a detailed description of this BLS.
Abort Task causes the Target to abort the specified task, if it exists. Previously established conditions such as Mode parameters
and reservations are not affected.
The Initiator performs the Abort Task by using the FC-PH Recovery Abort Protocol. This protocol recovers any resources
associated with the exchange that is being terminated.
The Initiator shall also use the recovery abort protocol for each open exchange following receipt of an FCP_RSP with a
RSP_CODE of No Failure (Function Complete) to Abort Task Set, Clear Task Set, or Target Reset Task Management function.
The recovery abort protocol is as follows:
•
The Initiator generates an ABTS sequence. This may be done regardless of whether or not the Initiator has sequence
initiative. In the ABTS frame:
- SEQ_ID is set to the SEQ_ID of an open sequence at the Initiator. If no sequence is open, any SEQ_ID not currently in use between the Initiator and the Target may be used.
- SEQ_CNT is set to one more than the SEQ_CNT of the last frame transmitted in the open sequence. If no
sequence is open, SEQ_CNT is zero.
- OX_ID is set to the OX_ID assigned by the Initiator to the task that is being aborted.
- RX_ID is set to FFFFh if no FCP_XFR_RDY (WRITE) or READ data (READ) has been received from the Target.
Otherwise, RX_ID is set to the RX_ID assigned by the Target to the task that is being aborted.
- F_CTL is set for Sequence Context = Initiator.
•
The Target may reject the ABTS with a BA_RJT frame only if
1. the Target has assigned an RX_ID to an OX_ID in a previous frame, and
2. the ABTS has an unknown OX_ID/RX_ID combination.
The reason code in the BA_RJT is Logical error and the reason code explanation is Invalid OX_ID-RX_ID combination. The F_CTL field is set to indicate that this is the last frame of the exchange.
•
The target accepts the ABTS with a BA_ACC frame. In the frame header:
- OX_ID is set from the OX_ID in the ABTS
- RX_ID is set from the RX_ID in the ABTS
- F_CTL is set to indicate that this is the last frame of the exchange (L_S = 1b) and Sequence Context =Recipient.
In the frame payload:
- SEQ_ID Validity is set to 00h
- SEQ_ID is ignored by the recipient and may therefore be any value
- OX_ID is set from the OX_ID in the ABTS
- RX_ID is set from the RX_ID in the ABTS
- Low SEQ_CNT is set to 0000h
- High SEQ_CNT is set to FFFFh
18.4.2 Abort Task Set
Abort Task Set causes the Target to abort all tasks in the task set that were created by the Initiator. The action is equivalent to
receiving a series of Abort Task requests. Previously established conditions such as Mode parameters and reservations are not
affected.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
111
18.4.3 Terminate Task
The drive does not support Terminate Task. An FCP_RSP with a RSP_CODE of Function Rejected will be returned.
18.4.4 Clear ACA
The drive does not support Clear ACA. An FCP_RSP with a RSP_CODE of Function Rejected will be returned.
18.4.5 Target Reset
The Target Reset Task Management function causes the Target to execute a hard reset, as defined by SAM. This means:
1.
2.
3.
4.
Abort all tasks for all Initiators.
Release any device reservation.
Return all internal states to their initial power-on and default values, as established by PRLI.
Set a unit attention condition for all Initiators.
Target Reset does not affect any login state.
18.4.6 Clear Task Set
Clear Task Set causes the Target to abort all tasks in the task set. The action is equivalent to receiving a series of Abort Task
requests from all Initiators.
A unit attention condition shall be generated for all other Initiators with tasks in the task set. The Additional Sense Code shall
be Commands cleared by another Initiator.
Previously established conditions such as Mode parameters and reservations are not affected.
18.4.7 Reset LUN
The Reset LUN Task Management function causes the drive to execute a hard reset with the same actions as Target Reset. See
section 18.4.5.
18.5 Miscellaneous
18.5.1 Tags
Using SCSI-FCP, an I/O Process equates to a Fibre Channel Exchange. All IOPs are therefore implicitly tagged by the Fully
Qualified Exchange ID (FQXID).
The FQXID is the 80-bit concatenation of the S_ID, D_ID, OX_ID and RX_ID from any frame in the exchange.
18.5.2 Auto-Contingent Allegiance (ACA)
In parallel SCSI-2, a CHECK CONDITION generates sense data for the faulted initiator (the one that got the CHECK CONDITION) and either suspends or aborts all commands queued by that Initiator. Execution of the next command from the
faulted Initiator clears the sense data and allows queued commands to resume. This is 'Contingent Allegiance' (CA).
CA requires an interlocked interface to work. In a non-interlocked serial interface, the 'next' command could already be on its
way before the faulted Initiator receives the CHECK CONDITION and sense data could be inadvertently lost.
In SCSI-3, ACA replaces the SCSI-2 Contingent Allegiance and Extended Contingent Allegiance conditions.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
112
ACA is a condition that is created within the Target task set whenever CHECK CONDITION is returned. While it exists, all
tasks in the task set are blocked (i.e., the queue is frozen). New tasks from Initiators other than the faulted Initiator are not
entered into the task set and are completed with a status of ACA ACTIVE.
New tasks from the faulted Initiator are entered into the task set under two different conditions, depending on the state of the
NACA bit in the CDB Control Byte of the faulting command.
1. If the NACA bit was set to 0b, the previously described SCSI-2 CA rules apply.
2. If the NACA bit was set to 1b, the new task must have the ACA attribute and there must be no other task in the task set
with the ACA attribute. If these conditions are not met, the task is completed with a status of ACA ACTIVE.
Note: Only NACA = 0b is supported.
18.5.3 Autosense
Autosense is the automatic return of sense data upon completion of the task. It is equivalent to an explicit REQUEST SENSE
command being executed immediately after Check Condition status is returned.
The sense data is returned in the I4 FCP_RSP IU. The FCP_SNS_LEN field indicates how many bytes of valid sense are contained in the FCP_SNS_INFO field.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
113
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
114
19.0 SCSI Command Set
Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory
Table 105: SCSI Commands Supported
Type
Code
Description
M
04h
FORMAT UNIT (04), page 118
M
12h
INQUIRY (12), page 124
O
4Ch
LOG SELECT (4C), page 134
O
4Dh
LOG SENSE (4D), page 137
O
15h
MODE SELECT (15), page 159
O
55h
MODE SELECT (55), page 170
O
1Ah
MODE SENSE (1A), page 161
O
5Ah
MODE SENSE (5A), page 189
O
5Eh
PERSISTENT RESERVE IN (5E), page 191
O
5Fh
PERSISTENT RESERVE OUT (5F), page 205
O
34h
PRE-FETCH (34), page 202
M
08h
READ (6) - (08), page 203
M
28h
READ (10) - (28), page 204
O
3Ch
READ BUFFER (3C), page 205
M
25h
READ CAPACITY (25), page 219
O
37h
READ DEFECT DATA (37), page 211
O
B7h
READ DEFECT DATA (B7), page 215
O
3Eh
READ LONG (3E), page 217
O
07h
REASSIGN BLOCKS (07), page 218
O
1Ch
RECEIVE DIAGNOSTICS RESULTS (1C), page 220
M
17h
RELEASE (17), page 226
O
57h
RELEASE (57), page 227
O
A3h
REPORT DEVICE IDENTIFIER (A3), page 228
O
A0h
REPORT LUNS (A0), page 230
M
03h
REQUEST SENSE (03), page 231
M
16h
RESERVE (16), page 232
O
56h
RESERVE (56), page 233
O
01h
REZERO UNIT (01), page 234
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
115
Type
Code
Description
O
0Bh
SEEK (6) - (0B), page 235
O
2Bh
SEEK (10) - (2B), page 235
M
1Dh
SEND DIAGNOSTIC (1D), page 236
O
A4h
SET DEVICE IDENTIFIER (A4), page 241
O
1Bh
START STOP UNIT (1B), page 242
O
35h
SYNCHRONIZE CACHE (35), page 243
M
00h
TEST UNIT READY (00), page 244
O
2Fh
VERIFY (2F), page 245
O
AF
VERIFY(16) - (AF), page 256
M
0Ah
WRITE (6) - (0A), page 247
M
2Ah
WRITE (10) - (2A), page 248
O
2Eh
WRITE AND VERIFY (2E), page 250
O
8E
WRITE AND VERIFY (16) - (8E), page 259
O
3Bh
In this mode the drive behavior is the same as Write Data to
Echo Buffer (Mode 0101b)., page 254
O
3Fh
WRITE LONG (3F), page 254
O
41h
WRITE SAME (41), page 256
O
93
WRITE SAME (16) - (93), page 267
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
116
19.1 SCSI Control Byte
The Control Byte is the last byte of every CDB. The format of this byte is shown below.
Table 106: SCSI Control Byte
BIT
7
6
5
VU = 0
4
3
2
Reserved = 0
1
0
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: * - NACA: This bit must be set to 0.
Note: ** - PLDA 1.10 says the following: “11.3 Command Linking: Command Linking is Prohibited by all SCSI Initiators
communicating with block devices conforming to this document. The Link and Flag bits of the CDB shall be set to zero.”
Therefore, this drive does not support command linking. The drive ignores the link bit and flag bit in the CDB.
19.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
19.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 FC-AL Hard Disk Drive Specification
117
19.4 FORMAT UNIT (04)
Table 107: 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.
•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:
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
118
- 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 FC-AL Hard Disk Drive Specification
119
19.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 108: 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 FC-AL Hard Disk Drive Specification
120
• 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.
19.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.
19.4.2.1 Block Format - 000b
Format of the Dlist sent during the data out phase when Dlist Format is Block format (000b) and FmtData is set to one.
Table 109: Defect Descriptor - Block Format (for n + 1 defects)
Byte
BIT
7
6
5
4
3
2
1
0
(MSB)
Defective Logical Block Address
0-3
(LSB)
4n
4n+1
(MSB)
Defective Logical Block Address n
4n+2
4n+3
(LSB)
The Block format of the Glist is the LBA of each defective sector.
Note: If a Defective LBA entry, when converted to a physical sector, is equal to the physical sector of a Plist entry and
DPRY = 1, then the entry is not added to the Glist.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
121
19.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 110: 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 FC-AL Hard Disk Drive Specification
122
19.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 111: 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 FC-AL Hard Disk Drive Specification
123
19.5 INQUIRY (12)
Table 112: INQUIRY (12)
Byte
BIT
7
6
5
0
4
3
2
1
0
CmdDt =0
EVPD
FLAG
LINK
Operation Code = 12h
1
Reserved = 0
2
Page Code
3
Reserved = 0
4
Allocation Length
5
VU = 0
Reserved = 0
The INQUIRY command requests the parameters of theTarget to be sent to the Initiator.
An EVPD An EVPD bit of one specifies that the target return the vital product data page identified by the Page Code field in
the CDB The available VPD pages are defined in the addendum provided for each different drive model in the section entitled
Inquiry Data Format.
The Page Code specifies which page of vital product data information the drive shall return.
Table 113: 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 FC-AL Hard Disk Drive Specification
124
19.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.
19.5.1.1 Inquiry Data Format - EVPD = 0, Page Code = 0
Table 114: Inquiry Data - CmdDt = 0, EVPD = 0
BIT
Byte
7
0
1
6
5
4
Qualifier = 0
RMB = 0
1
0
Reserved=0
Version = 3
Obsolete
Obsolete
Norm
HiSup = 0
ACA=0
4
5
2
Peripheral Device Type = 0
2
3
3
Response Data Formate = 2
Additional Length = 159 (9Fh)
SCCS=0
ACC=0
ALUA=00b
Port
3PC=0
6
BQue = 0 EncSer = 1
MultiP=1 MChngr= 0
7
Rel_A = 0 Obsolete Wb_16 =0 Sync = 0
Link = 0
Reserved = 0
Obsolete
Obsolete Addr16 = 0
Obsolete CmdQue= 1 RSVD = 0
8-15
Vendor ID = "HITACHI " (ASCII)
16-31
Product ID (ASCII)
32-35
Product Revision Level (ASCII)
36-43
Unit Serial Number (ASCII)
44-95
Reserved = 0
96
Hard Assigned ALPA
97
Acquired ALPA
98-147
Copyright Notice (ASCII)
148-163
Reserved=0
• Qualifier is set to zero to indicate that the LUN specified is currently supported. Qualifier is set to 011b when the LUN
specified is not present 1
• Peripheral Device Type is set to zero to indicate that the device is a Direct-Access. Peripheral 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 FC-AL Hard Disk Drive Specification
125
• 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 1 indicates that the Target contains an embedded enclosure services component.
•Port bit of 0 indicates that the drive received the Inquiry command on port A, while a Port bit of 1 indicates that the drive
received the Inquiry command on port B.
• MultiP (MultiPort) bit of 1 indicates that the Target has multiple ports and implements multi-port requirements.
• MChngr (Medium Changer) bit is always 0 to indicate MChngr is not supported.
• Addr16 (Wide SCSI Address 16) bit of 0 indicates that the Target does not support 16-bit wide SCSI Addresses.
• REL_A is set to zero to indicate that the Target does not support 'Relative Address Mode'.
• Wb_16 is set to zero to indicate that the Target does not support 16-bit wide data transfers.
• Sync is set to zero to indicate that the Target does not support synchronous data transfer.
• Link is set to zero to indicate that the Target does not support linked commands.
• CmdQue is set to one to indicate that the drive supports command queuing.
• Vendor ID is HITACHI padded with ASCII blanks.
• Product ID is specified in ASCII characters.
Product ID
Description
HUS151414VLF200
15000RPM 147GB
HUS151473VLF200
15000RPM 73GB
HUS151436VLF200
15000RPM 36GB
• Product Revision Level indicates the level of microcode. It indicates RAM microcode level.
• Unit Serial Number contains the drive serial number.
• Hard Assigned ALPA contains the hard Abritrated Loop Physical Address of the port which received the Inquiry command.
•Acquired ALPA contains the Arbitrated Loop Physical Address acquired by the port which received the Inquiry command.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
126
19.5.1.2 Inquiry Data Format - EVPD = 1 - Page Code = 00h
Table 115: Inquiry Data - EVPD = 1 (Page Code = 00h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 00h
2
Reserved = 0
3
Page Length = 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.
• 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 FC-AL Hard Disk Drive Specification
127
19.5.1.3 Inquiry Data Format - EVPD = 1, Page Code - 03h
Table 116: Inquiry Data - EVPD = 1 (Page Code = 03h)
BIT
Byte
7
0
6
5
4
Qualifier = 0
3
2
1
0
Peripheral Device Type = 0
1
Page Code = 03h
2
Reserved = 0
3
Page Length = 184 (B8h)
4
ASCII Fields Length = 00h
5-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 length of the
CDB is too small to transfer all the data, the Page Length field is not adjusted to reflect the truncation.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
128
• 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 FC-AL Hard Disk Drive Specification
129
19.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h
Table 117: Inquiry Data - EVPD = 1 (Page Code = 80h)
BIT
Byte
7
0
6
5
4
3
Qualifier = 0
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.
•Inquiry Data Format - CmdDt = 0, EVPD = 1, Page Code - 83h
19.5.1.5 Inquiry Data - EVPD = 1 (Page Code = 83h)
Table 118: 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)
5
Reserved = 0
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.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
130
• Association field is set to 0, indicating that the Identifier field is associated with the logical unit.
• 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 yyb n where:
xxx is the 12-bit Block assignment defined for each model and manufacturing site.
yy is the 2-bit Port/Node ID select.
n is the 22-bit drive unique serial number.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
131
19.5.1.6 Inquiry Data Format - EVPD = 1, Page Code - D1h
Table 119: 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 FC-AL Hard Disk Drive Specification
132
19.5.1.7 Inquiry Data Format - EVPD = 1, Page Code - D2h
Table 120: 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 FC-AL Hard Disk Drive Specification
133
19.6 LOG SELECT (4C)
Table 121: 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).
The drive allows updates to the current cumulative values only. A value of zero is acceptable and is not considered an error.
The drive updates only pages 0Eh, the Start/Stop Cycle page and 0Fh, the Application Client page. For other pages the parameters are ignored. If the data out buffer contains multiple pages then the application client should send the pages in ascending
order. If the data out buffer contains multiple log parameters within a page,all log parameters within the page should be sent
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
134
and they should be sent in ascending order by parameter code value. The drive shall return Check Condition status if the application client sends pages out of order, parameter codes out of order or missing parameter code. The sense key shall be set to
Illegal Request and additional sense code set to Invalid Field in Parameter List. If one or more fields of the CDB are not set
correctly the command will be terminated with a Check Condition status. The sense key shall be set to Illegal Request and
additional sense code of Invalid Field in CDB. To indicate that parameters have changed, the Target generates a unit attention
condition for all Initiators except the one that issued the LOG SELECT command.
The following list contains all individual page parameters (counters) that are set to their default value of 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 FC-AL Hard Disk Drive Specification
135
• 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
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
136
19.7 LOG SENSE (4D)
Table 122: 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 must be set to 0000h. If the Parameter
Pointer Field is not zero a Check Condition status is returned with a sense key of Illegal Request and additional sense
code of Invalid Field in CDB.
• Allocation Length field specifies the maximum number of bytes the Initiator has allocated for returned Log Sense Data.
No bytes are transferred if the length is zero. This condition is not considered an error. TheTarget terminates the Data
In phase when all available Log Sense data has been transferred or when the number of bytes equals the allocation
length, whichever is less.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
137
19.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 FC-AL Hard Disk Drive Specification
138
19.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 123: 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 FC-AL Hard Disk Drive Specification
139
0
19.7.3 Log Sense Page 2
This page contains counters for write errors.
Table 124: 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 FC-AL Hard Disk Drive Specification
140
=0
LP
=0
LP
=0
LP
=0
LP
=0
Table 125: 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 FC-AL Hard Disk Drive Specification
141
=0
LP
=0
19.7.4 Log Sense Page 3
This page contains counters for read errors.
Table 126: Log Sense Page 3 (part 1 of 2)
Bit
Byte
7
0
6
5
4
Reserved
3
Reserved
2-3
PageLength = 54h
4-5
Parameter Code = 0000h
DU = 0
DS = 0
TSD=0
ETC = 0
TMC = 0
7
Parameter Length = 08h
8-15
Errors recovered without delay
16-17
Parameter Code = 0001h
18
DU = 0
DS = 0
TSD = 0 ETC = 0
TMC = 0
19
Parameter Length = 08h
20-27
Count of ECC 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 = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
LBIN
=0
LP = 0
Page code = 03h
1
6
2
TSD=0
ETC = 0
TMC = 0
55
Parameter Length = 08h
56-63
Times recovery invoked
64-65
Parameter Code = 0005h
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
142
Table 127: Log Sense Page 3 (part 2 of 2)
Bit
Byte
66
7
6
DU = 0
DS = 0
5
4
TSD = 0 ETC = 0
3
TMC = 0
67
Parameter Length = 08h
68-75
Total bytes read
76-77
Parameter Code = 0006h
78
DU = 0
DS = 0
TSD = 0 ETC = 0
2
TMC = 0
79
Parameter Length = 08h
80-87
Count 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 FC-AL Hard Disk Drive Specification
143
19.7.5 Log Sense Page 5
This page contains counters for verify errors.
Table 128: 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 FC-AL Hard Disk Drive Specification
144
Table 129: 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 FC-AL Hard Disk Drive Specification
145
19.7.6 Log Sense Page 6
This page contains counters for non-medium errors. This includes seek errors and other hardware type failures.
Table 130: 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 FC-AL Hard Disk Drive Specification
146
=0
19.7.7 Log Sense Page D
This page contains temperature information.
Table 131: 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 FC-AL Hard Disk Drive Specification
147
19.7.8 Log Sense Page E
This page contains the start-stop cycle information.
Table 132: 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=0
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=1
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 FC-AL Hard Disk Drive Specification
148
19.7.9 Log Sense Page F
This page contains the Application Client Log.
Table 133: 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 134: 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 FC-AL Hard Disk Drive Specification
149
19.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 135: 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 136: 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 FC-AL Hard Disk Drive Specification
150
Table 137: 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 FC-AL Hard Disk Drive Specification
151
Table 138: 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 19.34 “SEND DIAGNOSTIC (1D)” on page 236, for detailed listing of operations carried out by SEND DIAGNOSTIC command and Power on Diagnostics.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
152
19.7.11 Log Sense Page 2F
This page contains SMART Status and Temperature Reading.
Table 139: 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 FC-AL Hard Disk Drive Specification
153
19.7.12 Log Sense Page 30
This page contains Performance Counters.
Table 140: 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 FC-AL Hard Disk Drive Specification
154
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 FC-AL Hard Disk Drive Specification
155
• 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 the read cache.
The statistics reported by this page are lost on a self-initiated reset or when the Drive is powered off. Even though the DS field
equals zero, the parameters on this page are not savable.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
156
19.7.13 Log Sense Page 37
This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.
Table 141: Log Sense Page 37
Bit
Byte
7
0
6
5
4
3
Reserved
2
Reserved
2-3
Page Length = 0030h (48)
4-5
Parameter Code =000h
DU=0
DS=0
7
8
0
LBIN=0
LP=0
Page code = 37h
1
6
1
TSD=0
ETC=0
TMC = 0
Parameter Length = 2Ch
(MSB)
Power on Hours (hours only)
-
(LSB)
11
12
(MSB)
Total Bytes Read
-
(LSB)
19
20
(MSB)
Total Bytes Written
-
(LSB)
27
28
29
-
Max Drive Temp (degrees Celsius)
(MSB)
GList Size
(LSB)
30
31
32
Number of PFA Occurrences
MED
PFA
HDW
PFA
Reserved = 0
33
-
Total Read Commands
40
41
-
Total Write Commands
48
49-51
Reserved
The Power on Hours field specifies the total time the drive has been powered on in hours only.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
157
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
0x1C.
If set, the Media and Hardware PFA bits indicate that a PFA trip has occurred during the life of the drive. These flags are set
during a PFA occurrence that may or may not coincide with the reporting of a PFA event as mentioned above.
Total Read Commands counter is incremented for each Read (6) and Read (10) command received.
Total Write Commands counter is incremented for each Write (6), Write (10), Write Verify and Write Verify (16) command
received.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
158
19.8 MODE SELECT (15)
Table 142: 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 FC-AL Hard Disk Drive Specification
159
19.9 MODE SELECT (55)
Table 143: 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 FC-AL Hard Disk Drive Specification
160
19.10 MODE SENSE (1A)
Table 144: 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 FC-AL Hard Disk Drive Specification
161
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 145: 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.
19.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.
19.10.1.1 Header
The 6-byte command descriptor block header is defined below.
Table 146: Mode parameter header (6)
Bit
Byte
7
6
5
4
3
0
Mode Data Length
1
Medium Type = 0
2
WP=0
Reserved=0
3
DPOFUA
=1
2
1
Reserved = 0
Block Descriptor Length (= 0 or 8)
The 10-byte CDB header is defined below.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
162
0
Table 147: Mode parameter header (10)
Bit
Byte
7
0
1
6
5
(MSB)
2
1
0
(LSB)
Medium Type = 0
WP=0
4
5
6
7
3
Mode Data Length
2
3
4
Reserved=0
DPOFUA
=1
Reserved = 0
Reserved = 0
(MSB)
Block Descriptor Length
(= 0 or 8)
(LSB)
• Mode Data Length. When using the MODE SENSE command, the mode data length field specifies the length in bytes
of the following data that is available to be transferred. The mode data length does not include the length byte itself.
When using the MODE SELECT command, this field is reserved.
• Medium Type field is always set to zero in the drive (Default Medium Type).
• WP. When used with the MODE SELECT command, the Write Protect (WP) bit is reserved.
When used with the MODE SENSE command, a Write Protect (WP) bit of zero indicates that the medium is write
enabled.
• DPOFUA bit value of 1 indicates that the Target supports the FUA and DPO bits in the Read and Write Commands.
• Block Descriptor Length specifies the length in bytes of the block descriptors. When used with the MODE SELECT
command, zero or eight is supported by the drive. When used with the MODE SENSE command, the drive returns
eight to indicate that only a single block descriptor is available.
Note: DPOFUA is ignored during Mode Select command processing although the SCSI Standard states that it is reserved during Mode Select. Ignoring it allows the Mode Sense Parameter List for the byte containing this bit to be re-used as a Mode
Select Parameter List.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
163
19.10.1.2 Block Descriptor
Table 148: 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)
Block Length
Byte 6
(LSB)
Byte 7
The Block descriptor provides formatting information about the Number of Blocks (user addressable) to format at the specified Block Length.
• Number of Blocks
When used with the MODE SELECT command, the Number of Blocks field must be
-
Zero to indicate not to change available blocks
-
0xFFFFFFFF to indicate all available blocks
-
The exact number of blocks in the data area of the drive, which can be obtained with the MODE SENSE
-
The number of blocks less than exact one, in order to CLIP the number of blocks
Any other value is invalid and causes the command to fail with Check Condition status.
When used with the MODE SENSE command, the field contains the exact number of blocks.
• Density Code
-
Always 0 for direct access devices.
• Block Length
When used with the MODE SELECT command, the Block length field must contain the value from 512 to 528 (8
bytes step) or zero. Otherwise the drive will terminate the command with Check Condition status.
A FORMAT UNIT command is required to cause these parameters to become current only if the block length parameter is different from the current block length.
When used with the MODE SENSE command, the field is dependent on how the media is currently formatted.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
164
19.10.1.3 Page Descriptor
Table 149: 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 150: 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.
Subpage Code: This field specifies the subpage to return. This field must be zero, since no subpages are supported.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
165
19.10.2 Mode Page 00 (Vendor Unique Parameters)
Table 151: Vendor Unique Parameters - Page 00
Default
Bit
Byte
0
7
6
PS
0
5
4
1
0
80h
Page Length = 0Eh
2
Ignored
Ignored
0Eh
MRG
VGMDE
Ignored
Ignored
4
RRNDE
00h
Ignored
Ignored
5
6
2
Page Code = 00h
1
3
3
Ignored
IGRA
AVERP
FDD
00h
00h
Ignored
Ignored
CAEN
Ignored
OCT (high nibble)
02h
00h
7
Overall Command Timer (low byte)
00h
8
Ignored
00h
9
Temperature Threshold
00h
10
Command Aging Limit (Hi byte)
00h
11
Command Aging Limit (Low byte)
30h
12
Read Reporting Threshold
0Ah
13
Write Reporting Threshold
0Ah
14
15
DRRT
Ignored
Ignored
FCERT
FFMT
BYPS
HIM
Ignored
Ignored
Reserved = 0
00h
00h
Fields marked in the table as 'Ignored' are not used or checked by the drive. They will be initialized to zero but can be set as
desired for compatibility with older drives.
• MRG (Merge Glist into Plist) bit is set to 1 for merging the Glist entries into the Plist during FORMAT UNIT command.
• VGMDE (Veggie Mode) bit indicates the drive, during its idle state, will execute random seeks at a predefined rate and
range of cylinders using predefined head.
• RRNDE (Report Recovered Non Data Errors) bit controls the reporting of recovered Non Data Errors when the PER bit
is set. If RRNDE is set, recovered Non Data Errors are reported. If the RRNDE bit is not set, then recovered Non
Data Errors are not reported.
• FDD (Format Degraded Disable) controls the reporting of Format Degraded sense data for Test Unit Ready commands
when the drive is in a format degraded state. When the FDD bit is one, Format Degraded sense data will not be
reported for a Test Unit Ready command. When the FDD bit is zero, Format Degraded sense data will be reported
for Test Unit Ready commands when the drive is in a format degraded state. This bit does not affect the reporting of
Format Degraded conditions for any media access commands.
• CAEN (Command Aging Enable) When set this bit causes the Command Age Limit timer to be used to avoid commands
waiting in the command queue for an indefinite period. When commands have been in the queue for a period of time
greater than the timer limit they will be reordered to be executed on a first come first served basis. When this bit is
reset, commands are always executed based on the queue reordering rules.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
166
• 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 AVERP bit
is set to one, the maximum retry counts for read operations is specified by Read Retry Count (Mode Page 1 Byte 3).
AVERP bit is set to zero to specify that the drive shall process read DRP up to the default maximum retry count when
Read Retry Count is set to a non-zero value.
• OCT (Overall Command Timer) controls the maximum command execution time, from receipt by the drive until status
is returned. If the command is unable to complete in the specified amount of time, it will be aborted with Check Condition status, Aborted Command sense key. The Overall Command Timer does not alter the behavior of the Command Aging Limit or Recovery Time Limit. Each unit of this timer is 50 milliseconds. Setting the value to zero
disabled the feature.
• Temperature Threshold specifies the threshold value in degrees Celsius for the thermal sensor warning message. A
value of 0 selects the default value (85 degrees Celsius).
• Command Aging Limit This value controls the maximum time a command should wait in the command queue when the
CAEN bit is set. Each unit of this timer is 50 ms.
• Read Reporting Threshold specifies the error reporting threshold for recovered data errors during read operations
when PER=1.
• Write Reporting Threshold specifies the error reporting threshold for recovered data errors during write operations
when PER=1.
• DRRT (Disable Restore Reassign Target) bit disables the reading and restoration of the target LBA during a Reassign
Blocks command. If the DRRT bit is zero, the reassign command attempts to restore the target LBA's data. If the data
cannot be restored, the target LBA is reassigned and written with a data pattern of all 00s. If the DRRT bit is one, no
attempt is made to restore the target LBA.
• FFMT (Fast Format Enable) bit allows the formatting of the drive without any writes to the customer media. All format
operations are allowed including changing block sizes and manipulating defects. The drive will operate normally
after a fast format with the following caveat: since no data is written to any customer data blocks as a result of a Fast
Format operation, there is a possibility that a read attempt to any particular block (without having previously written
to that block) will result in an unrecoverable data error. This will most likely happen if the block size is changed as
every LBA will contain data of an incorrect length and apparently an incorrect starting point. It is also possible to
generate an uncorrectable data error without changing block sizes if the defect list is shortened and previously bad
blocks become visible in the customer address space. Of course ALL DATA ON THE DRIVE WILL BE LOST as
the result of any format operation and so any attempt to read blocks which have not been written to will result in
unpredictable behavior.
• FCERT (Format Certification) bit determines whether the certification step will be performed during a Format Unit
command. FCERT bit set to 0 disables certification. FCERT bit set to 1 enables the certification step.
• BYPS (Bypass) controls the drive's actions following a self-initiated reset. If set, the drive will bypass both ports, and
remain bypassed when all reset actions are complete. In this mode, intended for development and qualification use, a
power cycle is required to re-establish loop communications. If the BYPS bit is zero, the drive will temporarily
bypass both ports during the reset, but enable both when the reset actions are complete. A unit attention condition
will be reported to indicate that the self-initiated reset has occurred.
• HIM (High Impedance Mode) bit determines how the drive will communicate with an 8067 compliant enclosure. When
this bit is set to one, the drive configures its enclosure services bus drivers tobe standard open collector outputs.
When set to zero, the drive will actively drive the bus lines high, rather than rely on an external pull-up resistor.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
167
19.10.3 Mode Page 01 (Read/Write Error Recovery Parameters)
Table 152: 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 FC-AL Hard Disk Drive Specification
168
• 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 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 FC-AL Hard Disk Drive Specification
169
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 FC-AL Hard Disk Drive Specification
170
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 FC-AL Hard Disk Drive Specification
171
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 FC-AL Hard Disk Drive Specification
172
19.10.4 Mode Page 02 (Disconnect/Reconnect Parameters)
Table 153: Mode Page 02 (Disconnect/Reconnect Parameters)
Bit
Byte
0
7
6
PS
0
5
4
3
2
1
0
Page Code = 02h
Default
82h
1
Page Length = 0Eh
0Eh
2
Read Buffer Full Ratio
00h
3
Write Buffer Empty Ratio
00h
4-5
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)
Reserved = 0
00h
00h
13-15
Reserved = 0
The disconnect/reconnect page provides the Initiator with the means to tune the performance of the Fibre Channel Loop.
The drive uses the disconnect/reconnect parameters to control when it attempts to regain control of the Loop during READ
(operation code 08h and 28h) and WRITE (0Ah, 2Ah and 2E).
• Read Buffer Full Ratio is the numerator of a fraction whose denominator is 256. The fraction indicates how full the
drive data buffer should be before attempting to re-arbitrate for the Loop. 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 re-arbitrate for the Loop. If the ratio is set to 0h, the target will
calculate and use an optimal ratio based on the negotiated transfer rate.
Both the Read Buffer Full Ratio and the Write Buffer Empty Ratio pertain to the current active notch. For each active notch as
defined in page 0Ch there are separate Read Buffer Full Ratios and Write Buffer Empty Ratios. When the active notch is set to
zero, the values are applied in mode page 0Ch across all notches.
• Maximum Burst Size is not supported, and any value in this field is ignored.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
173
19.10.5 Mode Page 03 (Format Device Parameters)
Table 154: 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 FC-AL Hard Disk Drive Specification
174
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 FC-AL Hard Disk Drive Specification
175
19.10.6 Mode Page 04 (Rigid Disk Drive Geometry Parameters)
Table 155: Mode Page 04 (Rigid Disk Drive Geometry Parameters)
Bit
Byte
0
7
6
PS
0
1
5
4
3
2
1
0
Page Code = 04h
04h
Page Length = 16h
16h
xxh
(MSB)
2-4
Default
Number of Cylinders
xxh
(LSB)
5
Number of heads
xxh
00h
(MSB)
6-8
Starting Cylinder -
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)
00h
(MSB)
14-16
00h
Landing Zone Cylinder = 0 (Not used)
00h
(LSB)
17
RESERVED = 0
RPL = 0
00h
18
Rotational Offset = 0 (Not used)
00h
19
RESERVED = 0
00h
20-21
22-23
(MSB)
3Ah
Medium Rotation Rate in RPM
(LSB)
Reserved = 0
The rigid disk drive geometric page specifies various parameters for the drive.
• RPL = 0, Indicates that the drive does not support spindle synchronization.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
176
98h
00h
19.10.7 Mode Page 07 (Verify Error Recovery Parameters)
Table 156: 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 FC-AL Hard Disk Drive Specification
177
19.10.8 Mode Page 08 (Caching Parameters)
Table 157: Page 08 (Caching Parameters)
Byte
0
1
2
3
4-5
Bit
7
PS
6
0
5
4
3
2
1
0
Page Code = 08h
Page Length = 12h
IC
ABPF
CAP
DISC
SIZE
WCE
MF
RCD
Demand Read Retention Priority
Write Retention Priority
(MSB)
Disable Pre-fetch Transfer Length
Default
88h
12h
04h
00h
FFh
(LSB)
6-7
(MSB)
Minimum Pre-fetch
(MSB)
Maximum Pre-fetch
00h
(LSB)
8-9
FFh
(LSB)
10-11
12
13
14-15
FSW
(MSB)
LBCSS
Maximum Pre-fetch Ceiling
DRA
Reserved = 0
Number of Cache Segments
Cache Segment Size
FFh
00h
08h
00h
(LSB)
16
Reserved = 0
00h
00h
(MSB)
17-19
Non Cache Segment Size
(LSB)
The caching parameters page defines parameters that affect the use of the cache.
• IC (Initiator Control) bit of one specifies that the drive will honor the following parameters to control cache
segmentation and pre-fetch: SIZE, FSW, LBCSS, Number of Cache Segments, Cache Segment Size. The drive will
never pre-fetch less data than specified by ABPF, MF, Demand Read Retention Priority, Write Retention Priority,
Disable Pre-fetch Transfer Length, Minimum Pre-fetch, Maximum Pre-fetch, and Maximum Pre-fetch Ceiling, but
may pre-fetch more based on internal cache algorithms. When the IC bit is set to zero, all the parameters listed above
are ignored, and an internal caching algorithm is used.
• ABPF (Abort Pre-fetch) bit of one, with DRA set to zero, causes the drive to abort the pre-fetch upon receipt of a new
command. ABPF set to one takes precedence over Minimum Pre-fetch. When ABPF is zero, with DRA set to zero,
the termination of any active pre-fetch is dependant upon the other parameters in this page.
• CAP (Caching Analysis Permitted ) is not supported and is ignored.
• DISC (Discontinuity) is not supported and is ignored.
• SIZE (Size Enable) bit when set to one indicates that the Cache Segment Size is to be used to control caching segmentation. When SIZE is set to zero, the Initiator requests that the Number of Cache Segments is to be used to control caching segmentation.
• WCE (Write Cache Enable) bit when set at zero indicates that the drive must issue Good status for WRITE (6) or
WRITE 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.
Note: When WCE = 1, a SYNCHRONIZE CACHE command must be done to ensure data are written to the media
before powering down the Target.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
178
• MF (Multiplication Factor) bit determines how the Maximum and Minimum Pre-fetch parameters are interpreted. If this
bit is set to zero, the parameters are used as is. If the bit is set to one, the parameters are multiplied by the number of
blocks requested in the Read Command.
• RCD (Read Cache Disable) bit set at zero indicates that the drive may return some or all of the data requested by a
READ (6) or READ (10) command by accessing the data buffer, not the media. An RCD bit set at one indicates that
the Target does not return any of the data requested by a READ (6) or READ (10) command by accessing the data
buffer. All of the data requested is read from the media instead.
• Demand Read Retention Priority sets the retention priority of data requested on a Read command. It may be set as
defined below:
Value
Definition
0h
Do not distinguish between requested data and other data
1h
Replace requested data before other data.
Fh
Replace other data before requested data.
where the value is the Demand Read Retention Priority or Write Retention Priority. Requested data is the blocks specified in
the Read or Write command. Other data is data in the cache from any other operation such as pre-fetch, read-ahead, etc.
If the Read Retention Priority is not set to Fh or if the DPO bit on the Read command is set to one, the requested data is overwritten by read-ahead data.
If the DPO bit is set to zero and the Read Retention Priority is set to Fh, the requested data is not overwritten with read-ahead
data. If the requested transfer is larger than the segment, the requested data is overwritten with more requested data and there
is no read-ahead
• Write Retention Priority sets the retention priority of data provided on a Write command. See the definition of
Demand Read Retention Priority above for more details.
• Disable Pre-fetch Transfer Length is used to prevent read-ahead after Read commands that are longer than the specified number of blocks. If this parameter is set to zero, a read-ahead is not performed.
• Minimum Pre-fetch specifies the minimum number of LBAs that the drive should read ahead after each READ command. A value of zero indicates that read ahead should be terminated immediately after a new command arrives,
except when the new command is on the current head and track.
• Maximum Pre-fetch specifies the maximum number of LBAs to read ahead after a Read command.
• Maximum Pre-fetch Ceiling specifies the maximum number of blocks the drive should attempt to read ahead. This field
is ignored.
• FSW (Force Sequential Write) is not supported and is ignored.
• LBCSS (Logical Block Cache Segment Size) bit when set to one indicates that the Cache Segment Size field units shall
be interpreted as logical blocks. When it is set to zero, the Cache Segment Size field units shall be interpreted as
bytes.
• DRA (Disable Read Ahead) bit when set to one requests that the Target not read into the buffer any logical block beyond
the addressed logical block(s). When it is set at zero, the Target may continue to read logical blocks into the buffer
beyond the addressed logical block(s).
• Number of Cache Segments field is used to select the number of data buffer cache segments. This parameter is valid
only when the SIZE bit is set at zero. It is ignored when SIZE is set at one.
• 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 FC-AL Hard Disk Drive Specification
179
19.10.9 Mode Page 0A (Control Mode Page Parameters)
Table 158: 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
3
RSVD=0
Queue Algorithm Modifier
4
TAS=0
0Ah
D_Sense=0 GLTSD=0 RLEC=0
Rsvd=0
QErr
RAC=0 UA_INTLCK_CTRL SWP=0
DQue
Obsolete
00h
00h
00h
5
Reserved = 0
00h
6-7
Obsolete=0
00h
Busy Timeout Period
00h
8-9
10-11
(MSB)
(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 FC-AL Hard Disk Drive Specification
180
• QErr (Queue Error Management) The queue error management (QERR) field specifies how the device server shall handle blocked tasks when another task receives a Check Condition status.
QERR
value
00b
01b
Description
Specifies that all tasks from all Initiators are blocked from execution when a Contintent
Alligience (CA condition) is pending. Those blocked tasks are allowed to resume execution
in a normal fashion after the CA condition is cleared.
Specifies that all tasks from all Initiators are aborted when the Target returns Check Condition status. A unit attention condition will be generated for each Initiator that had commands in the queue except for the Initiator that received the Check Condition status. The
sense key will be set to Unit Attention and the additional sense code will be set to Commands
Cleared by Another Initiator.
10b
Reserved
11b
Blocked tasks in the task set belonging to the Initiator to which a Check Condition status is
sent shall be aborted when the status is sent.
• DQue (Disable Queuing) bit set at zero specifies that tagged queuing shall be enabled if the Target supports tagged queuing. A DQue bit set at one specifies that tagged queuing shall be disabled. Command queuing is always enabled on
the drive, therefore this bit is ignored.
• Busy Timeout Period is ignored internally by the Target.
• Extended Self-test Routine Completion Time is an advisory parameter that an Initiator may use to determine the time
in seconds that the Target requires to complete self-test routine when the Target is not interrupted by an Initiator and
no errors occur during execution of the self-test routine.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
181
19.10.10 Mode Page 0C (Notch Parameters)
Table 159: 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)
XXh
(MSB)
12-15
Ending Boundary
XXh
(LSB)
(MSB)
16-23
Pages Notched
0000h
0000h
0000h
(LSB) 100Ch
The notch page contains parameters for direct-access devices that implement a variable number of blocks per cylinder. Each
section of the logical unit with a different number of blocks per cylinder is referred as a notch. The only field that is changeable is the Active Notch field.
• ND = One meaning that this device is a notched drive.
• LPN = Zero meaning that the notches are based upon physical parameters of the drive (cylinder #), not logical parameters.
• Maximum Number of Notches is the number of notches the drive can support.
• Active Notch indicates to which notch subsequent MODE SELECT/SENSE command parameters pertain. A value of 0
is used for parameter values which apply to all notches. Values from 1 to the maximum value depending on the model
specify the notch number, where notch 1 is the outermost notch. Following mode parameters are based on the current
active notch:
•Mode Page 2
- Read Buffer Full Ratio
- Write Buffer Empty Ratio
•Mode Page 3
- Alternate Sector per Zone
- Alternate Track per Zone
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
182
- 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 FC-AL Hard Disk Drive Specification
183
19.10.11 Mode Page 19h (Fibre Channel Port Control Page)
Table 160: Mode Page 19h
Byte
0
BIT
7
6
5
PS
RSVD=
0
4
Default
3
2
1
0
Page Code = 19h
99h
1
Page Length = 06h
06h
2
Reserved = 0
00h
3
DTFD
PLPB
DDIS
4
7
RHA
ALWLI DTIPE
DTOLI
Reserved = 0
00h
00h
Reserved = 0
5
6
DLM
00h
RR_TOV Units
Resource Recovery Time Out Value (RR_TOV)
00h
00h
•
DTFD (Disable Target Fabric Discovery) bit of one indicates that a Target attached by an FC-AL loop shall not recognize the presence of a fabric loop port, FL_Port, on the loop. The Target shall perform only the private loop functions defined for Targets defined by FC-PLDA. When DTFD bit is zero, the Target attached by an FC-AL loop shall
discover FL_Port if present on the loop and perform the public loop functions defined for Targets by FC-FLA.
•
PLPB (Prevent Loop Port Bypass) bit of one specifies that the Target ignores all LPB (Loop Port Bypass) and LPE
(Loop Port Enable) primitive sequences. The Target’s ports always remain in participating mode. A PLPB bit of zero
specifies that the Target allow LPB and LPE primitive sequences to control its port bypass circuitry.
•
DDIS (Disable Discovery) bit of one specifies the Target does not require receipt of Address or Port Discovery in
order to resume tasks following loop initialization. When DDIS is zero, the Target will only resume tasks for an Initiator on receipt of an Address or Port Discovery from that Initiator.
•
DLM (Disable Loop Master) bit of one specifies the Target does not become loop master during loop initialization.
When DLM is zero, the Target may become loop master.
•
RHA (Require Hard Address) bit of one indicates that a Target attached to an FC-AL loop shall only attempt to
obtain its hard address available in the SCA-2 SFF-8067 connector or device address jumpers during loop initialization. The Target shall not attempt to obtain an address during the LISA phase of initialization. If there is a conflict for
the hard address selection during loop initialization or the Target does not have a valid hard address available, the
Target shall enter the non-participating state. If the Target detects loop initialization while in the non-participating
state, the Target shall again attempt to get its hard address. If the hard address has not changed from the address
obtained in a previous successful loop initialization, the Target shall attempt to obtain the address in the LIFA phase
if a valid Fabric login exists or LIPA phase of loop initialization. If the hard address has changed, the Target shall
attempt to obtain the new address in the LIHA phase. When the RHA bit is zero, the Target follows the normal initialization procedure, including the possibility of obtaining a soft address during the loop initialization process.
•
ALWLI (Allow Login Without Loop Initialization) bit of one specifies the Target uses its hard address to accept logins without verifying the address with loop initialization. When ALWLI is zero, the Target is required to obtain an
address via the loop initialization procedure before accepting a login.
•
DTIPE (Disable Target Initiated Port Enable) bit of one specifies the Target waits for a Loop Port Enable primitive
with its own hard address before inserting itself onto the loop. When DTIPE is zero, the Target inserts itself onto the
loop without waiting for a Loop Port Enable primitive.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
184
•
DTOLI (Disable Target Originated Loop Initialization) bit of one specifies the Target does not generate the initializing LIP following insertion into the loop. The Target will respond to an initializing LIP, if received. The Target will
generate the loop failure LIP if it detects a loop failure at its input and the initializing LIP when the loop failure is corrected. When DTOLI is zero, the Target generates the initializing LIP after it enables a port into a loop.
•
RR_TOV Units field indicates the units in which the RR_TOV is calculated, according to Table 161.
Table 161: Values for RR_TOV Units
Byte 6
bit 2
bit 1
bit 0
0
0
0
No timer is specified
0
1
1
0.1 seconds
1
0
1
10 seconds
All other values
•
Units of measure for RR_TOV
Reserved
RR_TOV (Resource Recovery Time Out Value) field indicates the number of time units specified by the RR_TOV
UNITS field that shall be used by the timer that performs the RR_TOV timeout functions. The timer accuracy is +/0.1 seconds. Changes to RR_TOV will only affect the usage of the timer for non-authentication situations.
When the RR_TOV Units are set to no timer, the RR_TOV value (byte 7) shall be ignored by the Target and a default
timeout value of 2.0 seconds shall be used for RR_TOV.
When the RR_TOV Units are set to 0.1 seconds the following rules apply:
- a value of 00h will result in an infinite timeout value (no timeout will occur) Note: This well also cause E_D_TOV
to have an infinite timeout value.
- a value from 01h to 7Eh will result in a timeout duration that is the product of the RR_TOV value and 0.1 seconds
any value from 7Fh to FFh will result in the Target terminating 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 the PARAMETER LIST.
When the RR_TOV Units are set to 10 seconds, the following rules apply:
- a value of 00h will result in an infinite timeout value (no timeout will occur) Note: This will also cause E_D_TOV
to have an infinite timeout value.
- a value of 01h will result in a timeout duration that is the product of the RR_TOV value and 10 seconds
- any value from 02h to FFh will result in the Target terminating 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 the PARAMETER LIST.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
185
19.10.12 Mode Page 1A (Power Control)
Table 162: 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)
00h
(MSB)
8-11
Standby Condition Timer
(LSB)
• The value for the Idle Condition Timer and the corresponding Idle control bit is accepted. Despite this, the drive does
not alter the internal power saving algorithms based upon this value.
• Standby bit of one indicates that the Target shall use the Standby Condition Timer to determine the length of inactivity
time to wait before entering the Standby condition. A standby bit of zero indicates that the Target shall not enter the
Standby condition.
• Standby Condition Timer field indicates the inactivity time in 100 millisecond increments that the Target shall wait
before entering the Standby condition. The minimum allowable inactivity time is 60 minutes. Any value less than this
is accepted, but will automatically default to 60 minutes.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
186
19.10.13 Mode Page 1C (Informational Exceptions Control)
Table 163: 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
00h
(MSB)
8-11
Report Count
(LSB)
•PERF (Performance) bit is not used and ignored internally by the Target.
• EBF (Enable Background Function) bit is not used and ignored internally by the drive.
• EWASC (Enable Warning ASC) bit of zero indicates that Temperature 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 that information exception operations are enabled. The
reporting of information exception conditions is determined by the Method of Reporting field. A DEXCPT bit of one
disables all information exception operations. DEXCPT is independent of EWASC.
• 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 FC-AL Hard Disk Drive Specification
187
• 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 FC-AL Hard Disk Drive Specification
188
19.11 MODE SENSE (5A)
Table 164: 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 FC-AL Hard Disk Drive Specification
189
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
190
19.12 PERSISTENT RESERVE IN (5E)
Table 165: Persistent Reserve In (5E)
Bit
Byte
7
6
5
0
4
Reserved = 0
1
0
Service Action
2-6
9
2
Command Code = 5Eh
1
7-8
3
Reserved = 0
(MSB)
Allocation Length
(LSB)
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.
19.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 166: 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 FC-AL Hard Disk Drive Specification
191
19.12.2 Parameter data for Read Keys
Table 167: 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 FC-AL Hard Disk Drive Specification
192
19.12.3 Parameter Data for Read Reservations
Table 168: 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 FC-AL Hard Disk Drive Specification
193
Table 169: 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 FC-AL Hard Disk Drive Specification
194
19.13 PERSISTENT RESERVE OUT (5F)
Table 170: 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 FC-AL Hard Disk Drive Specification
195
19.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 171: 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.
•
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
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
196
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 initiator requesting the command has not previously performed a Register service action, the command is
rejected with a status of Reservation Conflict.
Following the successful completion of the Clear action, a Unit Attention Condition will be established for all other
registered initiators with an additional sense code of Reservation Preempted.
•
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.
Following the successful completion of the Register and Ignore Existing Key action, the Generation counter is incremented.
When keys are registered, the drive returns Reservation Conflict status for Reserve and Release commands.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
197
19.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 172: 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
---
19.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 173: 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 FC-AL Hard Disk Drive Specification
198
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 174: 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 FC-AL Hard Disk Drive Specification
199
19.13.4 Parameter list
Table 175: 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)
19.13.5 Summary
Table 176: 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 FC-AL Hard Disk Drive Specification
200
19.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.
19.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.
19.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.
19.13.5.4 Scope-specified address
Parameter in the Scope-specified address field is ignored by the drive.
19.13.5.5 Extent length
Parameter in the Extent length field is ignored by the drive.
19.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 177: 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
19.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 FC-AL Hard Disk Drive Specification
201
19.14 PRE-FETCH (34)
Table 178: PRE-FETCH (34)
Bit
Byte
7
6
5
0
4
3
2
1
0
Immed
=0
RelAdr
=0
Command Code = 34h
1
Reserved = 0
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the Initiator.
•
Transfer length field specifies the number of contiguous blocks of data that are to be transferred into the cache. A
transfer length of zero indicates that blocks are to be transferred into the cache until the segment is filled or until the
last block on the media.
•
Immed (Immediate) must be zero. An immediate bit of zero indicates that the status shall not be returned until the
operation has completed.
If the Immed bit is set to one, the drive returns a Check Condition status. The sense key shall be set to Illegal
Request and the additional sense code shall be set to Invalid Field in CDB.
•
RelAdr Relative Block Address is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
202
19.15 READ (6) - (08)
Table 179: READ (6) - (08)
Bit
Byte
7
6
5
0
1
3
2
1
0
Command Code = 08h
Reserved = 0
(MSB)
LBA
Logical Block Address
2-3
(LSB)
4
5
4
Transfer Length
VU = 0
Reserved = 0
FLAG
LINK
The READ command requests the drive to transfer from the medium to the initiator the specified number of blocks (Transfer
Length) starting at the specified Logical Block Address (LBA).
•
Logical block address field specifies the logical unit at which the READ operation shall begin.
•
Transfer length field specifies the number of blocks to be transferred. A value of zero implies 256 blocks are to be
transferred.
Note:
Error recovery procedure (ERP) handles errors. The error recovery parameters specified by the MODE SELECT
command control ERPs.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
203
19.16 READ (10) - (28)
Table 180: READ (10) - (28)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 28h
1
Reserved = 0
DPO
FUA
Reserved = 0
RelAdr
=0
(MSB)
2-5
Logical Block Address
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The READ (10) command requests the drive to transfer data to the Initiator. The larger LBA and Transfer Length fields permit
greater quantities of data to be requested per command than with the READ command and are required to access the full LBA
range of the larger capacity drives.
•
Transfer length The number of contiguous blocks to be transferred. If the transfer length is zero, the seek occurs, but
no data is transferred. This condition is not considered an error. If read ahead is enabled, a read ahead is started after
the seek completes.
•
DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified in the
Mode Select Page 8 Caching Parameters. A DPO bit of zero indicates the priority is determined by the retention priority. The Initiator should set the DPO bit when the blocks read by this command are not likely to be read again in the
near future.
•
FUA (Force Unit Access) bit of one indicates that the data is read from the media and not from the cache. A FUA bit
of zero allows the data to be read from either the media or the cache.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero. Relative addressing is not supported. If
RelAdr is set to 1, Check Condition status is returned with a sense key of Illegal Request and additional sense code
of Invalid Field in CDB.
If the transfer length is zero, no data is transferred. The CDB is validated and protocol checked and, if no problems are found,
Good status is returned immediately. This condition is not considered an error.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
204
19.17 READ BUFFER (3C)
Table 181: 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 FC-AL Hard Disk Drive Specification
205
19.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 182: 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.
19.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 FC-AL Hard Disk Drive Specification
206
19.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 183: 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 FC-AL Hard Disk Drive Specification
207
19.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.
19.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 184: Echo Buffer Descriptor
Bit
Byte
7
6
5
0
3
3
2
1
Reserved = 0
1
2
4
0
EBOS=0
Reserved = 0
Reserved = 0
(MSB) Buffer Capacity
Buffer Capacity
(LSB)
•
EBOS (Echo Buffer Overwritten Supported) bit of zero indicates that the echo buffer is shared by all Initiators.
•
Buffer Capacity field returns the size of the echo buffer in byte aligned to a 4-byte boundary.
19.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 FC-AL Hard Disk Drive Specification
208
19.18 READ CAPACITY (25)
Table 185: 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 FC-AL Hard Disk Drive Specification
209
19.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 186: Format of READ CAPACITY command reply
Bit
Byte
6
7
5
4
3
2
1
0
(MSB)
Maximum Logical Block Address
0-3
(LSB)
(MSB)
4-7
Block Length
(LSB)
•
Block Length specifies the length in bytes of the block.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
210
19.19 READ DEFECT DATA (37)
Table 187: READ DEFECT DATA (37)
Bit
Byte
7
6
5
0
Reserved = 0
2
Reserved = 0
3-6
9
3
2
1
0
Command Code = 37h
1
7-8
4
Reserved = 0
Plist
Glist
0
Defect List Format
Reserved = 0
(MSB)
Allocation Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The READ DEFECT DATA command requests that the Target transfer the medium defect data to the Initiator.
If the Target is unable to access any medium defect data it will return a Check Condition status with the appropriate sense
key. The sense key will be set to either Medium Error (03h) if a medium error occurred or No Sense (00h) if the list does not
exist and the additional sense code will be set to Defect List Error (19h).
•
Plist bit set to one indicates that the Target returns the Plist. A Plist bit of zero indicates that the Target shall not return
the Plist of defects.
•
Glist bit set to one indicates that the Target returns the Glist. A Glist bit of zero indicates that the Target shall not
return the Glist.
Note: With both bits set to one Plist and Glist the Target will return both the primary and grown defect lists. With
both bits set to zero, the Target will return only a 4-byte Defect List Header.
•
Defect List format field is used by the Initiator to indicate the preferred format for the defect list.
The Defect List Format of '100 (Bytes from Index Format)' and '101 (Physical Sector Format)' are supported. If the
requested format is not supported by the drive, it will return the defect list in its default format '101' and then terminate the command with Check Condition status. The sense key will be set to Recovered Error (01h) and the additional sense code will be set to Defect List Not Found (1Ch).
The drive sends defect list (Defect Descriptors) in a 8-byte Absolute Block Address (ABA) format that follows a four byte
Defect List Header.
The Target will transfer all of the Read Defect Data up to the number of bytes allocated by the Initiator.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
211
Table 188: 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 FC-AL Hard Disk Drive Specification
212
19.19.1 Defect List Header
Table 189: 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)
19.19.2 Defect List Descriptor
Table 190: 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 FC-AL Hard Disk Drive Specification
213
0
19.19.3 Bytes from Index Format (100b)
Table 191: 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
19.19.4 Physical Sector Format (101b)
Table 192: 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 FC-AL Hard Disk Drive Specification
214
19.20 READ DEFECT DATA (B7)
Table 193: 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 19.19 “READ DEFECT DATA (37)” on page 211.)
19.20.1 Defect List Header
Table 194: 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 19.19.1, “Defect List Header,” on page 213.)
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
215
19.20.2 Defect List Descriptor
Table 195: 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 19.19.2 “Defect List Descriptor” on page 213.)
19.20.3 Bytes from Index Format (100b)
Table 196: 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.
19.20.4 Physical Sector Format (101b)
Table 197: 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 FC-AL Hard Disk Drive Specification
216
19.21 READ LONG (3E)
Table 198: READ LONG (3E)
Bit
Byte
7
6
5
0
4
3
2
1
0
Correct
RelAdr
Command Code = 3Eh
1
Reserved = 0
Reserved = 0
=0
=0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Byte Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The READ LONG command requests the drive to transfer one block of data to the Initiator. The transfer data includes data and
ECC field data.
•
Correct bit of zero causes the logical block to be read without any correction attempts. When the bit is one, data will
be corrected with offline ECC correction before being transferred.
•
Logical Block Address field specifies the logical block at which the read operation shall occur.
•
Byte Transfer Length field must specify exactly the number of bytes of data that are available for transfer. If a nonzero byte transfer length does not match the available data length, the Target terminates the command with Check
Condition status, the sense key is set to Illegal Request, and an additional sense code set to Invalid Field in CDB.
The valid and ILI bits are set to one and the information field is set to the difference of the requested length minus the
actual length in bytes. Negative values are indicated by two's complement notation.
The transfer length is calculated as follows:
transfer length = logical block size + 44
•
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 FC-AL Hard Disk Drive Specification
217
19.22 REASSIGN BLOCKS (07)
Table 199: 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 FC-AL Hard Disk Drive Specification
218
Following is the format of the data sent by the Initiator during the DATA OUT phase.
Table 200: Format of Reassign Blocks data
Bit
Byte
7
6
5
4
0
Reserved = 0
1
Reserved = 0
(MSB)
2-3
3
2
1
Defect List Length = 4/8/12/16
(LSB)
(MSB)
4-7
Defect Logical Block Address 1
(LSB)
(MSB)
8-11
Defect Logical Block Address 2
(LSB)
(MSB)
12-15
Defect Logical Block Address 3
(LSB)
(MSB)
16-19
Defect Logical Block Address 4
(LSB)
•
Defect List Length must be 4, 8, 12, or 16. Otherwise, the drive returns Check Condition with a sense key of Illegal
Request.
•
Defective Logical Block Address is four bytes in length. The Initiator can specify from 1 to 4 Defective Logical
Block Addresses according to the Defect List Length from 4 to 16, respectively. LBAs are not required to be in
ascending order.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
219
19.23 RECEIVE DIAGNOSTICS RESULTS (1C)
Table 201: RECEIVE DIAGNOSTIC RESULTS (1C)
Bit
Byte
7
6
5
0
3
2
1
Reserved = 0
2
Reserved = 0
PCV
Page Code
(MSB)
Allocation Length
4
5
0
Command Code = 1Ch
1
3
4
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTIC command be sent to the Initiator.
•
PCV (Page Code Valid) bit of zero indicates that the most recent SEND DIAGNOSTIC command shall define the
data returned by this command. PCV bit of one indicates that the contents of the Page Code field shall define the data
returned by this command.
•
Allocation Length specifies the amount of data to be returned to the Initiator. This value may be zero and this is not
considered an error. The Target terminates the Data In phase when all available data has been transferred or when the
number of bytes transferred equals the Parameter List Length.
This command may also be used to retrieve a Diagnostic Page from an enclosure.
When requested to communicate with the enclosure via the Send and RECEIVE DIAGNOSTIC commands, the Target goes
through a 'discovery phase' with the enclosure as defined in the SFF-8067 standard. The results of this 'discovery phase', determine whether the enclosure: 1) does not support Enclosure Services, 2) supports only the 'short' Enclosure Service mode as
defined by SFF-8045, or 3) supports the 'long' Enclosure Service mode as defined by SFF-8067. After the 'discovery phase' the
drive behaves in accordance with the Enclosure Service mode capabilities of the enclosure. The drive does not attempt to
remember the Enclosure Service capabilities of the enclosure, but rather, in accordance with the SFF-8067 standard, re-performs the 'discovery phase' for each Send and RECEIVE DIAGNOSTIC command received.
If the Target determines that the enclosure does not support Enclosure Services, any attempts to access the Diagnostic Pages in
the enclosure will result in CHECK CONDITION status and sense data is built with the Sense Key and Additional Sense Code
indicating ENCLOSURE SERVICES UNAVAILABLE. In this case, only the Diagnostic Pages supported by the Target may
be requested.
If the Target determines that the enclosure supports the 'short' form of Enclosure Services, Diagnostic Page 08h is returned in
response to a request for any valid Diagnostic Page (i.e. 01h-0Fh).
If the Target determines that the enclosure supports the 'long' form of Enclosure Services, a request for the page is passed on to
the enclosure. Any diagnostic information returned to the Target is transferred to the Initiator. If the request for enclosure
transfer fails, the command is terminated with CHECK CONDITION status and sense data is built with the Sense Key and
Additional Sense Code indicating ENCLOSURE SERVICES UNAVAILABLE.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
220
19.23.1 Receive Diagnostic Results Page 0
This page contains a list of supported pages.
Table 202: Receive Diagnostic Results page 0
Bit
Byte
7
6
5
4
3
0
Page Code = 0
1
Reserved = 0
2-3
Page Length = 12h
4
(Supported Pages) Page = 0h
5
ESI Pages = 1h-Fh
2
1
–
19
20
Translate address page = 40h
21
Device LED Control Page = A0h
The supported diagnostic page returns a list of supported pages in ascending order.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
221
0
19.23.2 Enclosure Service Information (ESI) Page Format
The drive supports the following enclosure pages as specified by the “SCSI-3 Enclosure Service (SES) Rev 8a” standard.
Please refer to that standard for more definition on these pages. Note that the drive does not attempt to process the information
in these pages, but only acts as a pass through node, to allow the initiator to communicate with the enclosure.
Table 203: Enclosure Page Support for Send and Receive Diagnostic Commands
Page Code
Send Diagnostic Command
Receive Diagnostic Command
01h
Reserved
Configuration
02h
Enclosure Control
Enclosure Status
03h
Reserved
Help Text
04h
String Out
String In
05h
Threshold Out
Threshold In
06h
Array Control
Array Status
07h
Reserved
Element Descriptor
08h
Reserved
Short Enclosure Status
Reserved for SES
Reserved for SES
09-0Fh
These pages are formatted as in the following table.
Table 204: ESI Page Format
Bit
Byte
7
6
5
4
3
0
Page Code = 1h-0Fh
1
Page Specific
2
(MSB)
2
1
Page Length
3
n
0
(LSB)
Page Specific
If the enclosure supports ’short’ mode, only page 08h is supported. If the enclosure supports ’long’ mode, pages 01h-0Fh are
supported.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
222
19.23.3 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 205: Receive Diagnostic Results Page 40
Byte
Bit
7
6
5
4
3
0
Page Code = 40h
1
Reserved = 0
2-3
Page Length
4
5
Reserved = 0
RA
ALTS
ALTT
6-n
2
1
0
Supplied format
Reserved=0
Translate format
Translated Address
•
Page Length is set to 02h if the address is in a Reserved Area (RA =1). Otherwise, Page Length is set to 06h if the
Translate Format is Block format, or 0Ah if the Translate Format is Bytes From Index format or Physical Sector format.
•
Supplied Format is the value supplied by the SEND DIAGNOSTIC command; it may be one of the three following
values:
- 000b Block format
- 100b Bytes From Index format
- 101b Physical Sector format
•
Translate Format is the value supplied by the SEND DIAGNOSTIC command and specifies the format in which the
address has been translated into List. If the supplied format is the Block format, the Translate format must be either
Bytes from Index or Physical Sector format. If the supplied format is the Bytes from Index or Physical Sector format,
the Translate format must be Block format. Otherwise the Target will terminate the command with Check Condition
status.
•
RA (Reserved Area) is set to on if the translated block is an inaccessible sector, which could reflect a defect, an
unused sector on a spare cylinder, or a sector beyond the Maximum Customer LBA.
•
ALTS (Alternate Sector) is set to one if the translated block is a sector in a spare cylinder that points to a reassigned
customer sector.
•
ALTT (Alternate Track) is not used.
•
Translated Address contains the address in the translate format. If it is an LBA, it is contained within the first four
bytes of the field (bytes 6 to 9) of the page data. For a physical format it is as follows:
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
223
Table 206: 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 FC-AL Hard Disk Drive Specification
224
0
19.23.4 Receive Diagnostic Page A0h
The Receive Diagnostic Device LED Control Page A0h is returned as a result of the Send Diagnostic Device LED Control
Page A0h. For a description of the parameters in this page, see 19.34.3, "Send Diagnostic Page A0h" on page 231.
Table 207: Device LED Control Page - Receive Diagnostic
Bit
Byte
7
6
5
4
3
0
Page Code = A0h
1
Reserved = 0
2
(MSB)
2
1
Page Length = 0002h
3
4
5
0
(LSB)
Reserved = 0
Reserved = 0
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
225
SBDL
19.24 RELEASE (17)
Table 208: RELEASE (17)
Bit
Byte
7
6
5
0
1
4
3
2
0
Command Code = 17h
Reserved = 0
3rdPty=0
3rd Party ID
2
Reservation Identification
3-4
Reserved = 0
5
1
VU = 0
Reserved = 0
Ext=0
FLAG
LINK
The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that
is not currently active. The drive returns Good status without altering the reservation.
•
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is
returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
•
3rd Party ID is ignored.
•
Extents must be 0. Extension is not supported by the drive.
•
Reservation Identification field is ignored.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
226
19.25 RELEASE (57)
Table 209: RELEASE (57)
Bit
Byte
7
6
5
0
1
4
3
2
0
Command Code = 57h
Reserved = 0
2
3rdPty=0
Reserved = 0
Ext = 0
Reservation Identification
3
3rd Party Device ID
4-8
Reserved = 0
9
1
VU = 0
Reserved = 0
FLAG
LINK
The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that
is not currently active. The drive returns Go
od status without altering the reservation.
•
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is
returned with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
•
3rd Party ID is ignored.
•
Extents must be 0. Extension is not supported by the drive.
•
Reservation Identification field is ignored.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
227
19.26 REPORT DEVICE IDENTIFIER (A3)
Table 210: 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 FC-AL Hard Disk Drive Specification
228
Table 211: Report Device Identifier parameter list
Bit
Byte
7
0-3
4-n
(MSB)
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 FC-AL Hard Disk Drive Specification
229
19.27 REPORT LUNS (A0)
Table 212: 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 213: 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 FC-AL Hard Disk Drive Specification
230
19.28 REQUEST SENSE (03)
Table 214: REQUEST SENSE (03)
Bit
Byte
7
6
5
0
1
4
3
1
0
FLAG
LINK
Command Code = 03h
Reserved = 0
Reserved = 0
2-3
Reserved = 0
4
Allocation Length
5
2
VU = 0
Reserved = 0
The REQUEST SENSE command requests the drive to transfer sense data.
If REQUEST SENSE command with an invalid LUN is received, the drive returns Good status and reports a sense key of Illegal Request and an additional sense code of Logical Unit Not Supported.
If the drive has no sense data available to return, it shall return a sense key of No Sense and an additional sense code of No
Additional Sense Information.
Separate sense data is maintained by the device for each Initiator. Therefore, there is no requirement for an Initiator to expeditiously clear a Check Condition as this will not affect other initiators in a multi-Initiator system.
The drive will return the number of bytes in the allocation length or 32 bytes, whichever is less.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
231
19.29 RESERVE (16)
Table 215: RESERVE (16)
Bit
Byte
7
6
5
0
Reserved = 0
2
5
3
2
1
0
Command Code = 16h
1
3-4
4
3rdPty=0
3rd Party ID
Ext=0
Reservation Identification
(MSB)
Extent List Length = 0
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the
command or for a third party as specified by the Initiator.
Extents are not supported by the drive. The Ext bit must be zero. If Ext bit is set to one, Check Condition status is returned
with a sense key of Illegal Request and additional sense code of Invalid Field in CDB. The Reservation Identification and
Extent List Length fields are ignored.
The Reserve command requests that the entire LUN be reserved for the Initiator until
•
the reservation is superseded by another valid Reserve command from the Initiator that made the reservation.
•
the reservation is released by a RELEASE command from the same Initiator.
•
a hard Reset condition occurs.
•
a Target Reset message is received from any Initiator.
•
a power off/on cycle occurs.
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is returned
with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
3rd Party ID is ignored.
Only the Initiator that issued the Reserve command for a LUN may release the LUN, regardless of the 3rdPty option. This Initiator may also release the LUN by issuing another RESERVE command. This superseding RESERVE command releases the
previous reservation when the new reservation is granted.
Reservation queuing is not supported by the drive. If a LUN is reserved and a RESERVE command is issued from a different
Initiator, the Target responds with a RESERVATION CONFLICT.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
232
19.30 RESERVE (56)
Table 216: RESERVE (56)
Bit
Byte
7
6
5
0
4
3
2
Reserved = 0
3rdPty=0
Reserved
2
Reservation Identification
3
Third Pay Device ID
4-6
Reserved = 0
9
0
Command Code = 57h
1
7-8
1
(MSB)
Ext=0
Extent List Length = 0
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The RESERVE command is used to reserve a LUN for an Initiator. This reservation can be either for the Initiator sending the
command or for a third party as specified by the Initiator.
Extents are not supported by the drive. The Ext bit must be zero. If Ext bit is set to one, Check Condition status is returned
with a sense key of Illegal Request and additional sense code of Invalid Field in CDB. The Reservation Identification and
Extent List Length fields are ignored.
The Reserve command requests that the entire LUN be reserved for the Initiator until
•
the reservation is superseded by another valid Reserve command from the Initiator that made the reservation.
•
the reservation is released by a RELEASE command from the same Initiator.
•
a hard Reset condition occurs.
•
a Target Reset message is received from any Initiator.
•
a power off/on cycle occurs.
3rdPty must be 0. Third Party reservations are not supported. If the 3rdPty bit is not zero, Check Condition status is returned
with a sense key of Illegal Request and additional sense code of Invalid Field in CDB.
3rd Party ID is ignored.
Only the Initiator that issued the Reserve command for a LUN may release the LUN, regardless of the 3rdPty option. This Initiator may also release the LUN by issuing another RESERVE command. This superseding RESERVE command releases the
previous reservation when the new reservation is granted.
Reservation queuing is not supported by the drive. If a LUN is reserved and a RESERVE command is issued from a different
Initiator, the Target responds with a RESERVATION CONFLICT.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
233
19.31 REZERO UNIT (01)
Table 217: 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 FC-AL Hard Disk Drive Specification
234
19.32 SEEK (6) - (0B)
Table 218: SEEK (6) - (0B)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 0Bh
1
Reserved = 0
(MSB)
2
LBA
Logical Block Address
3
(LSB)
4
Reserved = 0
5
VU = 0
Reserved = 0
FLAG
LINK
The SEEK (6) command requests the drive to seek the specified LBA. If the LBA is greater than the value returned by the
READ CAPACITY command, the Drive returns a Check Condition status with a sense key of Illegal Request and an additional sense code of Invalid Field in CDB.
19.33 SEEK (10) - (2B)
Table 219: 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 FC-AL Hard Disk Drive Specification
235
19.34 SEND DIAGNOSTIC (1D)
Table 220: SEND DIAGNOSTIC (1D)
Bit
Byte
7
6
5
0
Function Code
2
5
3
2
1
0
SlfTst
Dev0fl
Unt0fl
Command Code = 1Dh
1
3-4
4
PF
RSVD =0
Reserved = 0
(MSB)
Parameter List Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The SEND DIAGNOSTIC command requests the drive to perform its self-diagnostic test or to perform a function based on a
page of information sent in a Data Out phase during the command.
•
PF (Page Format) bit set to one indicates the data sent by the Initiator conform to the page structure as specified in
SCSI-2 standard. This bit must be set to one if both the SlfTst bit and the Function Code field are 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 FC-AL Hard Disk Drive Specification
236
Table 221: SEND DIAGNOSTIC Function Code (1D)
Value
Function name
Description
000b
NA
Value to be used when the SlfTst bit is set to one or if the
SEND DIAGNOSTIC command is not invoking one of the
other self-test function codes.
001b
Background Short self-test
The device server starts its short self-test routine in background mode.
010b
Background extended self-test
The device server starts its extended self-test routine in
background mode.
011b
NA
Reserved.
100b
Abort background self-test
Abort the current self-test in the background mode. This
value is only valid if a previous SEND DIAGNOSTIC command specified a background self-test function and that
function has not been completed.
101b
Foreground short self-test
The device server starts its short self-test routine in the foreground mode. This self-test will complete in two minutes or
less.
110b
111b
Foreground extended self-test
The device server starts its extended self-test routine in the
foreground mode .The completion time for this test is
reported in Mode Page 0Ah (refer to section 17.11.9 "Mode
Page 0A).
Reserved.
•
DevOfl is ignored by the Target for compatibility.
•
UntOfl is ignored by the Target for compatibility.
•
Parameter List Length must be 0 when the SlfTst bit is one. Otherwise, Check Condition status will be generated
with a sense key of Illegal Request and additional sense of Invalid Field in CDB. If the SlfTst bit is zero, it should be
set to the length of the page to be transferred in the DATA OUT phase of the command. If it does not match the
expected length of the page a Check Condition status will be also generated with a sense key of Illegal Request and
additional sense of Invalid Field in CDB.
If the motor is not running at the correct speed when the command is received, it is rejected by a Check Condition status with
a Not Ready sense key.
If a fault is detected during the default or foreground self-test, a Check Condition is reported as an end status. If a fault is
detected during the background self-test, it is logged in the log page for later retrieval by a LOG SENSE command.
See Section 21.19 "Diagnostics" on page 292 for a detailed listing of operations carried out by the SEND DIAGNOSTIC command and Power on Diagnostics.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
237
19.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 222: 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
19.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 223: 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 FC-AL Hard Disk Drive Specification
238
19.34.3 Send Diagnostic Page A0h
The Device LED Control Page A0h allows the initiator to turn on or off the device fault LED light.
Table 224: Device LED Control Page - Send Diagnostic
Bit
Byte
7
0
6
5
4
3
2
1
0
Page Code = A0h
1
Reserved = 0
(MSB)
2-3
Page Length = 0002h
(LSB)
4
5
Reserved = 0
Reserved = 0
SBDL
The page begins with a four-byte page header which specifies the page code and length. A SBDL (Set Bad Device Light) bit of
one turns the device LED on, zero turns the device LED off. If the target detects an error in the passed parameter data it shall
terminate the command with CHECK CONDITIONS Status. The sense key shall be set to Illegal Request and the Additional
Sense code set to Illegal Field in CDB.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
239
•
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 225: 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 FC-AL Hard Disk Drive Specification
240
0
19.35 SET DEVICE IDENTIFIER (A4)
Table 226: 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
Reserved = 0
3
Reserved = 0
4-5
Restricted = 0
(MSB)
6-9
Parameter List Length
(LSB)
10
Reserved = 0
11
VU = 0
Reserved = 0
FLAG
LINK
The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the
SET DEVICE IDENTIFIER parameter list.
On successful completion of a SET DEVICE IDENTIFIER command a unit attention is generated for all Initiators except the
one that issued the service action. When reporting the unit attention condition the additional sense code is set to Device Identifier Changed.
•
Parameter List Length field specifies the length in bytes of the Identifier that is transferred from the host system to
the Target. The maximum value for this field is 512 bytes. A parameter list length of zero indicates that no data is
transferred, and that subsequent REPORT DEVICE IDENTIFIER commands return an Identifier length of zero.
The SET DEVICE IDENTIFIER parameter list contains the identifier to be set by the addressed logical unit.
Table 227: 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 FC-AL Hard Disk Drive Specification
241
19.36 START STOP UNIT (1B)
Table 228: 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 FC-AL Hard Disk Drive Specification
242
19.37 SYNCHRONIZE CACHE (35)
Table 229: SYNCHRONIZE CACHE (35)
BIT
Byte
7
6
5
0
4
3
2
1
0
Immed
=0
RelAdr
=0
Command Code = 35h
1
Reserved = 0
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Number of Blocks
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded
on the media.
•
Logical Block Address is to specify where the operation is to begin.
•
Number of Blocks specifies the total number of contiguous logical blocks within the range. Number of Blocks of
zero indicates that all remaining logical blocks on the logical unit shall be within the range.
•
Immed (immediate) must be zero. An immediate bit of zero indicates that the status shall not be returned until the
operation has completed. If the Immed bit is set to one, the drive returns a Check Condition status. The sense key
shall be set to Illegal Request and the additional sense code shall be set to Invalid Field in CDB.
•
RelAdr (Relative Address) must be zero. The drive does not support the relative addressing. If the RelAdr bit is set to
one, the drive returns Check Condition status. The sense key shall be set to Illegal Request and the additional sense
code shall be set to Invalid Field in CDB.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
243
19.38 TEST UNIT READY (00)
Table 230: 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 FC-AL Hard Disk Drive Specification
244
19.39 VERIFY (2F)
Table 231: VERIFY (2F)
BIT
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
RSVD
=0
Command Code = 2Fh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB)
Verification Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that
no data will be transferred. This condition is not considered an error.
•
ByteChk bit set to zero indicates that the data is read from the disk and verified using ECC.If an ECC error is
detected in the verify process, Check Condition status is returned with sense key set to Medium Error. ByteChk bit
set to one indicates that byte-by-byte comparison is performed between the data on the disk and data transferred from
the initiator during the data-out phase.
If the comparison is unsuccessful, the command is terminated with Check Condition status and the sense key is set
to Miscompare.
•
DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified in the
Mode Select Page 8 Caching Parameters. A DPO bit of zero indicates the priority is determined by the retention priority. The Initiator should set the DPO bit when the blocks read by this command are not likely to be read again in the
near future.
If caching is enabled, the command performs an implied FUA and an implied Synchronize Cache before starting the VERIFY.
This ensures that the medium, not the cache, is being verified.
The command stops on Check Condition and reports the LBA in error. The command must be reissued, starting with the next
LBA, to verify the remainder of the Drive.
The Verification Length is the number of blocks to check.
The data (if any) from the data-out phase and the data from the media are not retained in the cache. Therefore, the DPO bit has
no effect on this command and is ignored.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
245
19.40 VERIFY (16) - (8F)
Table 232: Verify (16) - (8F)
Bit
Byte
7
6
5
0
4
3
2
1
0
Byte
Chk
Rsvd
=0
Command Code = 08Fh
1
Reserved = 0
DPO
Reserved = 0
(MSB)
2-9
Logical Block Address
(LSB)
(MSB)
10-13
Verification Length
(LSB)
14
15
Reserved = 0
VU = 0
Reserved = 0
FLAG
LINK
The VERIFY command requests that the drive verify the data written on the media. A verification length of zero indicates that
no data will be transferred. This condition is not considered an error.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
246
19.41 WRITE (6) - (0A)
Table 233: 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 19.15 “READ (6) - (08)” on page 203 for the parameters.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
247
19.42 WRITE (10) - (2A)
Table 234: WRITE (10) - (2A)
Bit
Byte
7
6
5
0
4
3
2
1
0
Command Code = 2Ah
1
Reserved = 0
DPO
FUA
Reserved=0
RelAdr
=0
(MSB)
Logical Block Address
2-5
(LSB)
6
7-8
9
Reserved = 0
(MSB
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The WRITE (10) command requests that the drive write the data transferred from the Initiator. This command is processed like
the standard WRITE (6) - (0A) command except for the longer transfer length.
•
Transfer Length is the number of contiguous blocks to be transferred. If the transfer length is zero, the seek occurs,
but no data is transferred. This condition is not considered an error.
•
DPO (Disable Page Out) bit of one indicates that the data accessed by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified in the
Mode Select Page 8 Caching Parameters. A DPO bit of zero indicates that the priority is determined by the retention
priority. The Initiator should set the DPO bit when the blocks written by this command are not likely to be read in the
near future.
•
FUA (Force Unit Access) bit of one indicates that the Target must write the data to the media before returning Good
status. A FUA bit of zero indicates that the Target may return Good status prior to writing the data to the media.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
248
19.43 WRITE AND VERIFY (16) - (8E)
Table 235: 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 FC-AL Hard Disk Drive Specification
249
19.44 WRITE AND VERIFY (2E)
Table 236: 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
9
Reserved = 0
(MSB)
Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
WRITE AND VERIFY command requests that the drive writes the data transferred from the Initiator to the medium and then
verify that the data is correctly written.
•
Transfer Length of zero indicates that no data is transferred.
If caching is enabled, the command performs an implied FUA and an implied Synchronize Cache before starting the
operation. This insures that the medium, not the cache, is being verified.
•
ByteChk bit set to zero indicates that the data is read back from the disk and verified using ECC after the successful
write operation. If an ECC error is detected in the verify process, Check Condition status is returned with sense key
set to Medium Error. ByteChk bit set to one indicates that byte-by-byte comparison is performed between data on the
disk starting the block specified in LBA field and data transferred from the Initiator.
If the comparison is unsuccessful, the command is terminated with Check Condition status and the sense key is set
to Miscompare.
•
DPO (Disable Page Out) bit of one indicates that the data written by this command is to be assigned the lowest priority for being written into or retained by the cache. A DPO bit of one overrides any retention priority specified in the
Mode Select Page 8 Caching parameters. A DPO bit of zero indicates the priority is determined by the retention priority.
The Initiator should set the DPO bit when the blocks written by this command are not likely to be read again in the
near future.
•
RelAdr (Relative Block Address) is not supported. Must be set to zero.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
250
19.45 WRITE BUFFER (3B)
Table 237: 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.
19.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.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
251
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 238: Write Buffer Header
Bit
Byte
7
6
5
0-3
4
3
2
1
0
Reserved = 0
19.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 FC-AL Hard Disk Drive Specification
252
19.45.3 Download Microcode (Mode 00100b)
NOTE: It is not expected that a customer will ever issue this format of the command.
In this mode, the microcode is transferred to the control memory space of the drive. When downloaded, the drive will operate
with the newly downloaded code immediately until the next power cycle.
Buffer ID field is used to indicate which portion of the microcode image is being downloaded. The following Buffer IDs are
supported by the Target:
- 00h: Main Microprocessor Code
- nnh : ID of Vendor Unique Reserved Area
Any unsupported value for the Buffer ID will cause the command to terminate with Check Condition status. And the drive
shall set the sense key to Illegal Request and additional sense code to Illegal Field In CDB.
Buffer Offset must be zero. If an invalid value is specified, the command is terminated with Check Condition status. The
drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in CDB.
Parameter List Length must be the size of the data set to be downloaded. It may also be set to 0000h in which case no code
is updated and command status is returned. If an invalid value is specified, the command is terminated with Check Condition
status. And the drive shall set the sense key to Illegal Request and additional sense code to Illegal Field In CDB.
This process generates a unit attention condition for MICROCODE HAS BEEN CHANGED for all Initiators except the one
which sent the WRITE BUFFER command. Upon the completion of the WRITE BUFFER command the new microcode is
immediately ready for operation.
Note: The Download Microcode mode described in this specification is to indicate that the drive will accept a command with
this mode, though it is not expected that a user will ever issue such a command. To use the write buffer command with this
mode, a special microcode version is required from development. If such a microcode is released from development, then it
will include appropriate instructions on the function of new microcode and its effect on the drive operations after download.
19.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. To download microcode, the
buffer ID should be set to 00h. Other values are reserved for Hitachi development purposes only.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
253
19.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 4K bytes. The total length of all segments received shall be equal to the total length of the binary
microcode file. All segments must be sent in the proper sequential order.
If an invalid Parameter List Length is specified, Check Condition status is returned with sense key of Illegal Request and
additional sense code of Invalid Field in CDB.
The first segment sent in this mode indicates, by default, the first segment of the binary microcode file. If a Check Condition
status is returned in this mode, a Buffer ID == 00h in the subsequent Write Buffer command in this mode indicates the first
segment of the binary microcode file. Otherwise the Buffer ID field is ignored.
The Buffer Offset field is ignored.
After all segments of the binary microcode file have been received, the drive behavior is the same as Download Microcode and
Save (Mode 00101b) - Single Binary File.
19.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.
19.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).
19.46 WRITE LONG (3F)
Table 239: 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
7-8
9
Reserved = 0
(MSB)
Byte Transfer Length
(LSB)
VU = 0
Reserved = 0
FLAG
LINK
The WRITE LONG command requests the drive to write one block of data transferred from the Initiator.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
254
The transfer data must include
•
User Data
•
44 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 FC-AL Hard Disk Drive Specification
255
19.47 WRITE SAME (41)
Table 240: WRITE SAME (41)
Bit
Byte
7
6
0
5
4
3
2
1
0
PBDA
TA=0
LBDA
TA=0
RelAdr
=0
Command Code = 41h
1
Reserved=0
(MSB)
2-5
Logical Block Address
(LSB)
6
7-8
9
Reserved = 0
(MSB)
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.
•
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 FC-AL Hard Disk Drive Specification
256
19.48 WRITE SAME (16) - (93)
Table 241: Write Same (16) - (93)
Bit
Byte
7
0
6
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
Reserved = 0
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 FC-AL Hard Disk Drive Specification
257
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
258
20.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 242: SCSI Status Byte. Format of the SCSI STATUS byte.
Bit
7
6
Reserved = 0
5
4
3
2
1
Status Code
0
RSVD
STATUS BYTE Description
00h
GOOD
The command has been successfully completed.
02h
CHECK CONDITION
An error, exception, or abnormal condition has been detected. The sense data is set by the drive. The
REQUEST SENSE command should be issued to determine the nature of the condition.
04h
CONDITION MET
This status is returned when an unlinked PRE-FETCH command has been successfully completed.
08h
BUSY
This condition is returned when disconnect privilege is not granted while the drive is BUSY processing the
other command for the other initiator. The normal initiator recovery action is to issue the command at a later
time or to reissue the command and grant the disconnect privilege.
10h
INTERMEDIATE
Not supported by FC-AL products.
14h
INTERMEDIATE CONDITION MET
Not supported by FC-AL products.
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 FC-AL Hard Disk Drive Specification
259
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
260
21.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.
21.1 Obtaining an AL_PA
The SCA-2 FC-AL connector used by the drive provides 7 bits which encode a preferred Hard AL_PA for use on both loops.
If this value is set to 7Fh, a Soft AL_PA will be used.
Note: Loop Initialization cannot be bypassed if Soft AL_PA is selected.
A Soft AL_PA will also be used if, for any reason, the Hard AL_PA cannot be obtained. If this happens, The drive will
•
log out all initiators
•
accept new port logins
•
accept each process login with a reason code of: 05h
No special action is taken if the connector supplied AL_PA is changed while the drive is participating on the loop(s).
21.2 Loop Initialization Procedure
L_Ports use the Loop Initialization Procedure in order to acquire an AL_PA and participate on the loop.
The drive optionally initiates the Loop Initialization Procedure shortly after power-on, depending on the configured mode settings. In addition, it may (depending on the mode settings) initiate the Loop Initialization Procedure for the following reasons:
3. When it has been unable to obtain the loop for E_D_TOV.
4. When a loop failure has been detected (loss of sync for R_T_TOV)
The Loop Initialization Procedure is disruptive to any communication that is actually in progress on the loop. IOPs that are
queued or active but without any frames 'in flight' are not affected.
Initiators are not logged out by the Loop Initialization Procedure, but it is their responsibility to login if their AL_PA changes.
The drive detects (via the Port_Name) this situation and implicitly ends the prior login. The initiator may perform a 'Port Discovery' sequence to check that the targets have not physically changed.
The L_Port that initiates the Loop Initialization Procedure must transmit LIPs for 2 x AL_TIME to ensure that all L_Ports participate. By default, AL_TIME is set to 15ms.
All L_Ports must provide sufficient buffering to receive and transmit the LIxx frames that are circulated during the Loop Initialization Procedure. The largest of these (LILP and LIRP) have a 132 byte payload and are supported by the drive.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
261
Table 243: LIxx Frame Payloads
LIxx Frame
Payload
LISM
1101 0000h
8 - byte Port_Name
LIFA
1102 0000h
16 - byte AL_PA bit map
LIPA
1103 0000h
16 - byte AL_PA bit map
LIHA
1104 0000h
16 - byte AL_PA bit map
LISA
1105 0000h
16 - byte AL_PA bit map
LIRP
1106 0000h
128 - byte AL_PA position map
LILP
1107 0000h
128 - byte AL_PA position map
The Loop Initialization Procedure is as follows...
1. Select Initial AL_PA
The initial AL_PA is EFh.
2. Select a Loop Master
LISM frames are continuously transmitted. The D_ID and S_ID fields are set to 0000EFh.
If a LISM frame is received which is the same as the one transmitted, the Port becomes the Loop Master and continues the
procedure at step 3.
For all other received LISM frames...
- If the D_ID is 000000h, the frame is retransmitted.
- If the Port_Name in the payload is greater than the Port_Name, the frame is discarded.
- If the Port_Name in the payload is less than the Port_Name, the frame is retransmitted.
If an ARB(F0) is received, the Port continues the procedure at step 4.
3. Loop Master
a. ARB(F0) is continuously transmitted until ARB(F0) is received.
b. The Port prepares an LIFA frame with an initial AL_PA bit map of all zeros. After transmitting the LIFA frame, the
Port waits to receive a LIPA frame.
c. The AL_PA bit map from the LIFA frame is used in a LIPA frame. If the bit corresponding to the Port’s previously
assigned AL_PA is not set it is set now. If it is already set, the Port attempts to obtain its Hard AL_PA in step d. The
Port transmits the LIPA and waits to receive it back.
d. The AL_PA bit map from the LIPA frame is used in a LIHA frame. If the bit corresponding to the Port’s hard
assigned AL_PA is not set it is set now (unless a bit was set for LIPA). If it is already set, the Port attempts to obtain a
Soft AL_PA in step e. The Port transmits the LIHA and waits to receive it back.
e. The AL_PA bit map from the LIHA frame is used in a LISA frame. If a bit was not set for LIHA, the bit associated
with the lowest priority AL_PA still available is set. This is the Port’s “soft assigned” AL_PA. If no bits are available,
the Port shall stay in non-participating mode. The Port transmits the LISA and waits to receive it back. If byte 3 of the
payload in the received LISA frame is still 01h (indicating that all nodes on the loop support positional mapping) the
drive continues with the next two steps. Otherwise, the next two steps are skipped.
f. The Port creates a LIRP frame with an AL_PA position map of all FFh, except for the first two bytes which are
01xxh (xx is the Port’s AL_PA). The Port transmits the LIRP frame and waits to receive it back.
g. The AL_PA position map from the received LIRP is used to create a LILP frame. The Port transmits the LILP frame
and waits to receive it back.
h. CLS is transmitted to put all other Ports into MONITORING state. When received back, the Loop Master itself goes
to MONITORING state.
4. Non Loop Master
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
262
The Port retransmits received ARB(F0) and prepares to receive the following frames, followed by CLS.
a. When a LIFA frame is received, the Port will set the bit corresponding to the Port’s “Fabric Assigned” AL_PA if the
Port was logged-in to the local FL_Port prior to the LIP. (See 21.5, “Public Loop Operation” on page 264.) After
transmitting the LIFA frame, The Port waits to receive a LIPA frame.
b. When a LIPA frame is received (and a bit was not set for LIPA), the bit corresponding to any previously assigned
AL_PA is checked. If not set, it is set now. If it is already set, the Port attempts to obtain its Hard AL_PA in step c.
The Port transmits the LIPA.
c. When a LIHA frame is received (and a bit was not set for LIPA), the bit corresponding to any required hard assigned
AL_PA is checked. If not set, it is set now. If it is already set, the Port attempts to obtain a Soft AL_PA in step d. The
Port transmits the LIHA.
d. When a LISA frame is received (and a bit was not set for LIHA), the bit associated with the lowest priority AL_PA
still available is set. This is the Port’s soft assigned AL_PA. If no bits are available, the Port shall stay in non-participating mode. The Port transmits the LISA.
e. If a LIRP frame is received, and the Port was able to claim an AL_PA in one of the LIxA frames, the left most byte
is incremented by one and used as an offset at which to store the Port’s AL_PA. The Port transmits the LIRP.
f. If a LILP frame is received, the Port may store the AL_PA position map for use in error recovery. The Port transmits
the LILP.
g. When CLS is received, the Port retransmits it and goes to MONITORING state.
21.3 Flow Control
The drive provides a Class 3 service. Flow control is maintained using R_RDYs.
Each initiator is required to login with every target. This establishes the Login BB_Credit, (i.e. how many frames the initiator
or target may send immediately on opening or being opened.)
Prior to login, BB_Credit is zero.
The Alternate BB_Credit Model is operated as follows...
•
On opening, the Available BB_Credit in each direction is set to the agreed Login BB_Credit value.
•
Each frame sent decrements the Available BB_Credit and each R_RDY received increments it.
•
If the Available BB_Credit reaches zero, the node must stop sending frames until enough R_RDYs have been
received to restore positive credit.
•
It is permissible to close before credit is balanced (i.e. R_RDY received for each frame sent) but only when enough
buffers are available to satisfy the maximum Login BB_Credit that has been extended.
Available BB_Credit may exceed Login BB_Credit but a point to note is that R_RDY is not specific to any frame type. Therefore, the amount of Available BB_Credit that the drive will extend is limited by the amount of buffer space available for
FCP_CMND or FCP_DATA IUs. For example, during the execution of a 512K WRITE command, there may be buffer space
for 256 2K FCP_DATA IUs and 10 FCP_CMND IUs. The amount of credit extended will be for 10 frames.
21.4 Login Requirements
In order to communicate effectively, a pair of L_Ports must exchange operational parameters. The same applies to any SCSI
processes that use the L_Ports.
The exchange of parameters is called Login and may be either explicit or implicit.
•
Explicit Login is the default. L_Ports use the PLOGI Extended Link Service sequence to exchange parameters and
SCSI Processes use the PRLI Extended Link Service.
•
Implicit Login is enabled via setting of mode page 19h. When enabled, PLOGI and PRLI are not required and a
default set of parameters is assumed.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
263
The response to certain frames at various stages of login is defined in Table 244.
Table 244: Response to Frames before PLOGI or PRLI
Frame Received
No PLOGI
PLOGI but no PRLI
ABTS
Discard and Send LOGO
BA_ACC or BA_RJT(1)
ADISC
Discard and Send LOGO
ACC(2) or LS_RJT
LOGO
ACC
ACC
PDISC
Discard and Send LOGO
ACC(2) or LS_RJT
PLOGI
ACC
ACC
PRLI
Discard and Send LOGO
ACC
PRLO
Discard and Send LOGO
ACC or LS_RJT(3)
Unlisted Extended Link Service
Discard and Send LOGO
ACC or LS_RJT(4)
Note:
1 - The drive returns BA_RJT to ABTS BLS when ABTS BLS has RX_ID other than 0FFFFh
2 - N_Port ID, Port_Name and Node Name must match a logged in port for ACC to be returned.
3 - If PRLI has not been successfully completed, Reason Code = 'Image Pair does not exist'
4 - Unsupported Extended Link Services are rejected.
Login parameters remain in effect until reset or updated by...
•
Power cycle
•
LIP Reset
•
Explicit Logout (LOGO)
•
Explicit Login (PLOGI/PRLI)
•
Implicit Logout (failure to re-Discover within RR_TOV following LIP)
21.5 Public Loop Operation
The drive is designed to perform as a Public NL_Port described in the FLA 2.70 profile.
The drive will:
•
tolerate unfairness of a FL_Port
•
support 24bit addressing
•
accept FAN extended link service
•
perform FLOGI to Fabric F_Port (AL_PA = 00h, well known address 0FFFFFEh)
•
perform registration to a simple name server (AL_PA = 00h, well known address 0FFFFFCh) using RFC-4 service.
•
claim a fabric-assigned AL_PA during LIP in the LIFA sequence
•
receive frames from a FL_Port for more than one S_ID in a single loop tenancy
•
open L_Port at AL_PA = 00h and send frames to remote port
•
use values of E_D_TOV, R_A_TOV as specified by the fabric in FLOGI ACC
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
264
21.5.1 NL_Port Initialization
NFS
Client
Public Loop
Device
Fabric
F
Public Loop
Device
FL
SCSI
Initiator
F
Public Loop
Device
IP Host
F
Public Loop
Device
Public Loop
Device
FL
Public Loop
Device
a) FLOGI
Required?
No
e) Receive
FAN
i) Non FLA
- L_bit set
- AL_PA changed
- no FLOGI yet
b) Perform
FLOGI
Change/Timeout
No Address Change
c) Address
Changed
No Address Change
and L_bit not set
First FLOGI
f) No Address
Change
g) Perform
RFC-4
R_A_TOV
Implicit LOGO
d) Recovery
from Change
Exchange Resume
h) Initialize
Complete
Figure 3 : NL_Port Initialization
During LIP, if the port had an AL_PA prior to the LIP, and the port had completed FLOGI, then the port attempts to acquire its
Fabric-assigned AL_PA during LIFA sequence.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
265
a) FLOGI Required
Upon completion of LIP, the port will implicitly log out with the Fabric and perform FLOGI if one or more of the following is true:
• the L_bit was set to one in at least the LISA sequence during the LIP.
• the port did not acquire the AL_PA it had prior to the LIP.
• the port did not have an AL_PA prior to the LIP.
• the port had not completed FLOGI prior to the LIP
b) Perform FLOGI
The port attempts to send FLOGI to the FL_Port by opening AL_PA = 00h using Full-Duplex. Meanwhile the port
ignores any FAN ELS and responds to ADISC or PLOGI request sequences with an LS_RJT reply sequence, with a
Reason code of “Unable to perform Command Request at this time”. If the FLOGI request fails for any reason, the port
proceeds to step i). If no address change occurred and the L_bit is not set then the port proceeds to step f). If this is the
first FLOGI or if the address has not changed and the L_bit is set, then the port proceeds to step g).
c) Address has changed
The port has determined that its own addressing information and/or that of the FL_Port has changed, or that it did not
have completed addressing information (via FLOGI) prior to the initialization. The port discards all pending Exchanges,
and performs implicit LOGO with all other ports. The port proceeds to step d).
d) Recovery from address change
The port waits R_A_TOV. During this time the port discards all frame received except for the PLOGI and ADISC
request sequences and LOGO ACC reply sequences. The port responds to all PLOGI request with an LS_RJT reply
sequence, with a Reason code of “Unable to perform Command Request at this time”. The port responds to each ADISC
request sequence with a LOGO request sequence. The port proceeds to step g).
e) Receive FAN
If FLOGI is not required, the port waits E_D_TOV to receive FAN ELS. The port discards all frames received except
ADISC and PLOGI requests until FAN is received. The port responds to ADISC and PLOGI request sequences with an
LS_RJT reply sequence, with a Reason code of “Unable to perform Command Request at this time”.
After receiving the FAN ELS, if the port determines the FL_Port has the same address, F_Port_Name and
Fabric_Name that the FL_Port had before initialization, the port proceeds to f). Otherwise, the port implicitly logs out
with the Fabric and proceeds to b).
If the port does not receive a FAN ELS within E_D_TOV the port proceeds to b).
f) Address has not changed
The port resumes all suspended Exchanges with Remote Ports and with Local Ports that are known to be Public
NL_Ports. If the port has any suspended Exchanges with Private Loop devices on the Local Loop, the port requires the
private loop authentication described in PLDA profile. The port proceeds to step h).
g) Perform RFC-4
The port performs PLOGI with the Directory Server (AL_PA = 00h, well known address 0FFFFFCh) and attempts an
RFC-4 request with the Name Service. Regardless of this attempt of RFC-4, the port proceeds to step h).
h) Initialize complete
This completes initialization for the port.
i) Non FLA
The port is not connected to a loop that contains an FL_Port. The port completes initialization based on the rules
described in PLDA profile.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
266
21.6 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.
21.6.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 21.6.2, “Invalid LUN Processing” on page 267)
2. Check Condition status for Incorrect Initiator Connection (See Section21.6.3, “Overlapped Commands” on page 267)
3. Check Condition status for Unit Attention Condition (See Section 21.6.5, “Unit Attention Condition” on page 269
4. Busy Status or Queue Full Status (See 21.6.4, “Command Processing During Execution of Active I/O Process” on
page 268
5. Check Condition status for Deferred Error Condition (See Section 21.6.8, “Deferred Error Condition” on page 271)
6. Check Condition status during Startup and Format operations (See Section “21.6.6, “Command Processing During
Startup and Format Operations” on page 271)
7. Reservation Conflict status (See Section 21.6.10, “Command Processing while Reserved” on page 279)
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.
21.6.2 Invalid LUN Processing
Any value other than zero in the FCP_LUN field of the FCP_CMD IU is invalid.
The target's response to an invalid LUN varies with the command, as follows:
Inquiry: Execute the command, return the INQUIRY data that indicates unknown device type (byte 0 = 7Fh), and return
GOOD status. All other bytes are valid (see 19.5, “INQUIRY (12)” on page 124).
Request Sense: Execute the command, return the sense data with the Sense Key set to Illegal Request and the Additional
Sense Code and Additional Sense Code Qualifier set to LOGICAL UNIT NOT SUPPORTED, and return GOOD status (see
also19.28, “REQUEST SENSE (03)” on page 231).
All Others: Do not execute the command and return CHECK CONDITION status, along with the auto-sense data with the
Sense Key set to Illegal Request and the Additional Sense Code and Additional Sense Code Qualifier set to LOGICAL UNIT
NOT SUPPORTED.
In all cases, the target's response to the command for an invalid LUN does not affect the current execution of a command on
the valid LUN for this initiator or any other initiator.
21.6.3 Overlapped Commands
Fibre Channel Protocol for SCSI Revision 012 (X3.269-1996) says the following: "5.5.9 The value of the OX_ID is the tag
defined by X3.270-1996. Since the value of the OX_ID is required by FC-PH to be unique, there is no requirement for an FCP
logical unit to check for overlapping commands." Thus the drive does not perform any overlapped command checking.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
267
21.6.4 Command Processing During Execution of Active I/O Process
When the target is not executing any I/O processes, a new I/O process is permitted to execute (unless execution is prevented by
another internal target condition listed in 21.6.1, “Priority of SCSI Status Byte Reporting” on page 267).
If an active I/O process exists when the target receives a new command, then the target determines if:
•
the command is permitted to execute
•
the command is added to the queue
•
Queue Full status is to be returned
•
Busy status is to be returned
If an active I/O process exists when the target receives a new command, then the target determines how the new command
should be handled based on the following rules:
•
Check Condition status is returned with sense key set to Logical Unit Not Ready if:
•
the startup operation or a format operation is active. See 21.6.6, “Command Processing During Startup and Format Operations” on page 271 for the exact conditions which cause this response.
Note: If a Unit Attention is pending when this condition exists, the sense key is set to Unit Attention rather than Logical Unit
Not Ready since Unit Attention has a higher reporting priority (see 21.6.1, “Priority of SCSI Status Byte Reporting” on
page 267).
•
The command is permitted to execute if:
•
the command is a priority command (see21.6.1, “Priority of SCSI Status Byte Reporting” on page 267).
•
the conditions to execute concurrently are met (see 21.10, “Concurrent I/O Process” on page 280).
•
The command is added to the queue if:
•
•
•
any I/O process already exists at the target, and
•
this is not an incorrect initiator connection.
Queue Full status is returned if:
•
the command would otherwise be added to the queue (according to the rules described above), but all slots in
the queue are full, or
•
the command would otherwise be added to the queue (according to the rules described above), but all of the
available queue slots not reserved for use by another initiator are full, or
•
a Format Unit command was previously queued but has not yet begun execution, or
•
the target is in a Degraded Mode (see 21.6.9, “Degraded Mode” on page 272) and a Start Unit command was previously queued but has not yet begun execution.
Busy status is never returned.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
268
21.6.5 Unit Attention Condition
The target generates a unit attention condition when one of the following occurs:
•
The target has been reset
This includes a power-on reset or a reset caused by a Target Reset Task Management function or Reset LIP. In all of
these cases, a unit attention condition is generated for each initiator. In addition, a process login (PRLI) will cause a
Unit Attention Condition Power-On Reset for that initiator with an Additional Sense Code and Additional Sense
Code Qualifier reported as Power-On Reset, Power-On Reset Occurred.
•
MODE SELECT command has been executed
In this case, a unit attention condition is generated for all initiators except the one that issued the MODE SELECT
command. The Additional Sense Code and Additional Sense Code Qualifier reported is MODE PARAMETERS
CHANGED. The unit attention condition is generated if any of the current page parameters are set by the MODE
SELECT command. The target does not check to see that the old parameters are different from the new parameters.
For example: If the initiator issues a MODE SENSE command with a page code to report the current values followed
by a MODE SELECT command with the same parameter list, a unit attention condition is generated despite the fact
that the current parameters were not changed from their previous value. However, if the target detects an illegal
parameter or error condition prior to modifying the current parameters, a unit attention condition is not generated
since the parameters were not set. The unit attention condition is also not generated if the MODE SELECT command
parameter list does not include any pages and only the header or header/block descriptor is present.
•
FORMAT UNIT command has been executed
In this case, a unit attention condition is generated for all initiators except the one that issued the FORMAT UNIT
command. The Additional Sense Code and Additional Sense Code Qualifier reported is NOT READY TO READY
TRANSITION, (MEDIUM MAY HAVE CHANGED). This indicates that the block descriptor parameters from the
last MODE SELECT command have been used and are now considered current values.
•
WRITE BUFFER command to download microcode has been executed
In this case, a unit attention condition is generated for all initiators except the one that issued the WRITE BUFFER
command. The Additional Sense Code and Additional Sense Code Qualifier reported is MICROCODE HAS BEEN
CHANGED.
•
Commands Cleared by another initiator
This unit attention condition is generated after an initiator sends a Clear Task Set Task Management function. The
unit attention condition is generated for all other initiators with I/O processes that were either active or queued for the
logical unit. The Additional Sense Code and Additional Sense Code Qualifier reported is COMMANDS CLEARED
BY ANOTHER INITIATOR.
•
LOG SELECT command with PCR bit has cleared parameters.
In this case, a unit attention condition is generated for all initiators except the one that issued the LOG SELECT com
mand. The additional sense code and additional sense code qualifier reported is Log Select Parameters Changed.
•
The registration or reservation made by a Persistent Reserve Out command was cleared by another initiator.
In this case, a unit attention condition is generated for the initiator that held the cleared registration or reservation.
•
A Predictive Failure Analysis threshold has been reached and the Method of Reporting field of mode page 1Ch is 2h.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
269
The unit attention condition persists for each initiator until that initiator clears the condition from the logical unit as described
below. Several commands are handled as special cases during a unit attention condition These cases are also discussed below.
If the target receives a command from an initiator before reporting a CHECK CONDITION status for a pending unit attention
condition for that initiator, the target's response varies with the command as follows:
Inquiry
Execute the command, return GOOD status, and preserve the unit attention condition.
Report Luns
Same as above
Request Sense
Execute the command, return any pending sense data, return GOOD status, and preserve the unit
attention condition. If there is not any pending sense data, the sense data associated with the highest
priority unit attention condition is returned and the highest priority unit attention condition is
cleared for this initiator.
All Others
Do not execute the command, return a CHECK CONDITION status, clear the highest priority unit
attention condition for this initiator and return the associated sense data.
More than one unit attention condition may be generated for an initiator before that initiator clears the unit attention condition.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
270
21.6.6 Command Processing During Startup and Format Operations
If the Target receives a command from an Initiator while the Target is executing a startup or format operation, the response of
the Target varies with the command as follows:
INQUIRY
The drive sends inquiry data and returns appropriate status.
REQUEST SENSE
Executes the command, returns a Sense key of NOT READY and an Additional Sense Code of
LOGICAL UNIT NOT READY and returns GOOD STATUS.
The Additional Sense Code Qualifier that is returned depends on type of I/O processes that are
active:
For the START/UNIT STOP and the Auto-start operation, the qualifier returned is LOGICAL
UNIT IS IN PROCESS OF BECOMING READY. For the FORMAT UNIT command, the qualifier returned is LOGICAL UNIT NOT READY, FORMAT IN PROGRESS, and the Sense key specific bytes are set to return the progress indication.
REPORT LUNS
The drive sends REPORT LUNS data and approprate status.
ALL OTHER
The drive terminates the command with CHECK CONDITION status. The Sense data generated is
described in Request Sense above.
21.6.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.
21.6.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 FC-AL Hard Disk Drive Specification
271
21.6.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)
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
272
21.6.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 245: Spindle Motor Degraded Mode - Disable Auto Start
Command (w/Option)
Response
Request Sense
Executed. The Target may return Sense Key 02h (Not Ready) ASC/ASCQ
0402h (Initialize Command Required)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed and Check Condition is returned with Sense Key 05h (Illegal Request)
ASC/ASCQ 2400h (Invalid Field in CDB)
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 0402h (Initialize Command Required)
Start Stop Unit
Executed
(Start)
- Success: Good Status is returned. Motor Degraded Mode is cleared
- Spindle Motor Start Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 0400h (Start Spindle Motor Fail)
- Self Configuration Failure: Check Condition with Sense Key 02h (Not Ready)
ASC/ASCQ 4080h (Diag Fail- Bring up Fail)
Sense Key 02h (Not Ready) ASC/ASCQ 4085h (Diag Fail-RAM Code NOT
load)
Start Stop Unit
Executed. Good Status is returned. Motor Degraded Mode is NOT cleared
(Stop)
Other Commands
Not Executed. Check Condition Status is returned with Sense Key 02h (Not
Ready) ASC/ASCQ 0402h (Initialize Command Required)
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
273
21.6.9.2 Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up
Table 246: 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 FC-AL Hard Disk Drive Specification
274
21.6.9.3 Response to SCSI Command in Degraded Mode - Spindle Start Failure
Table 247: 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 FC-AL Hard Disk Drive Specification
275
21.6.9.4 Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command
Table 248: 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 FC-AL Hard Disk Drive Specification
276
21.6.9.5 Self Configuration Failure Degraded Mode
Table 249: 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 FC-AL Hard Disk Drive Specification
277
21.6.9.6 Format Command Failure Degraded Mode
Table 250: Format Command Failure Degraded Mode
Command (w/Option)
Response
Request Sense
Executed. The Target may return
Sense Key 02h (Not Ready) ASC/ASCQ 3100h (Format Corrupted)
Sense Key 03h (Medium Error) ASC/ASCQ 3100h (Format Corrupted)
Inquiry (EVPD=0)
Executed
Inquiry (EVPD=1)
Executed
Test Unit Ready
Executed and Check Condition is returned with Sense Key 02h (Not Ready)
ASC/ASCQ 3100h (Format Corrupted)
Format Unit
Executed
- Success: Good Status is returned. Format Degraded Mode is cleared
- Failure: Check Condition Status is returned and Format Degraded Mode is
NOT cleared.
Other Commands
Note:
Not Executed. Check Condition Status is returned with Sense Key 03h (Medium
Error) ASC/ASCQ 3100h (Format Corrupted)
Mode Page 0 byte 5 bit 4 (FDD) = 0
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
278
21.6.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 21.6.1, “Priority of SCSI Status Byte Reporting” on
page 267.
21.7 Priority Commands
Certain SCSI commands always execute without returning a Busy Status or Reservation Conflict Status in response to the
command. These commands are
•
Inquiry
•
Request Sense
•
Report LUNs
•
Test Unit Ready
These commands are executed prior to attempting to complete the execution of any other pending command in the queue.
These commands are never queued.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
279
21.8 Command Queuing
When the initiator specifies that the drive shall disable command queuing, the initiator must send only untagged commands.
When the initiator specifies that the target shall enable command queuing, the initiator may send either tagged or untagged
command, but shall not use both at the same time.
The following commands are never queued.
•
Priority Commands (i.e.: Request Sense and Inquiry)
•
Commands for an invalid LUN.
21.8.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.
21.8.2 Queue Full Status
The drive will respond with QUEUE FULL status to a SCSI command when all queue slots are utilitzed. The SCSI command
is not placed in the command queue under this condition.
21.8.3 Effects of LIP on Command Queuing
When a loop re-initializes (via a LIP sequence) command execution for all initiators on the initializing port is suspended. After
loop initialization is complete, the drive will maintain all queued commands for all initiators up to RR_TOV. If an initiator performs Exchange Authentication (via PDISC or ADISC) within RR_TOV, its queued commands will now be free to execute.
If an initiator fails to authenticate within RR_TOV, the initiator will be implicitly logged out, and the commands will be
removed from the command queue.
21.8.4 Termination of I/O Processes
Normal termination of I/O processes occurs when the target returns SCSI status. I/O processes may also be terminated by the
following:
•
An ABORT TASK terminates the specified I/O process from the issuing initator
•
An ABORT TASK SET terminates all I/O processes from the issuing initiator
•
A CLEAR TASK SET, TARGET RESET or reset terminates all I/O processes from all initiators
•
Failure by an initiator to initiate Exchange Authentication within RR_TOV of the completion of Loop Initialization
results in an implicit logout and termination of all associated I/O processes (21.8.5 Effects of LIP on Command Queing on a page 291)
21.9 Command Reordering
Command reordering is supported when enabled by the Queue Algorithm Modifier in mode page 0A ( see 19.10.9, “Mode
Page 0A (Control Mode Page Parameters)” on page 180.
21.10 Concurrent I/O Process
Concurrent command are always allowed to execute concurrently with non-priority commands. A second priority command
received while a priority command is being executed is put at the head of the command queue.
•
WRITE commands when another WRITE command is an active I/O process
•
READ commands when another READ command is an active I/O process
When a concurrent command ends in CHECK CONDITION status, the QErr bit on the Mode Page 0Ah will determine how
other active I/O processes from the same initiator for that drive will be handled.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
280
21.11 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
Contingent allegiance condition all queued processes including commands from other initiators are suspended.
21.12 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 FC-AL Hard Disk Drive Specification
281
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 251: 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 FC-AL Hard Disk Drive Specification
282
21.13 Segmented Caching
21.13.1 Overview
Segmented Caching divides the data buffer into several smaller buffers. Each buffer is used as Read/ Write/Read-Ahead buffer.
21.13.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.
21.14 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.
21.14.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.
21.14.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 21.6.5, “Unit Attention Condition” on page 269 for more information.
21.15 Enclosure Services
Enclosure Services allow the Host Computer System to access information held by the Enclosure Microcontroller using the
same industry standard interface as the enclosed devices.
This disk drive supports the ESI (Enclosure Services Interface) for this purpose, as described in the Functional Specification.
The drive sets the EncServ bit to 1b in the Standard INQUIRY Data indicating that it supports enclosure services. This indicates that the Host may use the SEND DIAGNOSTIC and RECEIVE DIAGNOSTIC RESULTS commands to access information held by the Enclosure. This information is in the form of 'Diagnostic Pages'.
Diagnostic Pages 01h to 0Fh are reserved for Enclosure Services.
There are two distinct forms of Enclosure Services. The EncServ bit does not specify which form the Target and Enclosure are
capable of (if any). The Host can discover this by using a RECEIVE DIAGNOSTIC RESULTS command to request Diagnotic Page 00h.
When requested to communicate with the enclosure via the SEND and RECEIVE DIAGNOSTIC commands, the drive goes
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
283
through a 'discovery phase' with the enclosure as defined in the SFF-8067 standard. The results of this discovery phase determine whether the enclosure: 1) does not support Enclosure Services, 2) supports only the 'short' Enclosure Services mode as
defined by SFF-8045, or 3) supports the 'long' Enclosure Services mode as defined by SFF-8067. After the discovery phase,
the drive behaves in accordance with the Enclosure Services mode capabilities of the enclosure. The drive does not attempt to
remember the Enclosure Services capabilities of the enclosure, but rather, in accordance with the SFF-8067 standard, re-performs the discovery phase for each SEND and RECIEVE DIAGNOSTIC command received.
Short
This mode is defined for use when an Enclosure simply supplies an 7-bit parameter as defined by the SFF-8045 standard to the drive.
When mounted in this type of Enclosure, an attempt to access any Enclosure Service Diagnostic Page using the SEND DIAGNOSTIC command will terminate the
command with CHECK CONDITION status. The sense data will have a Sense
Key of Illegal Request and an Additional Sense Code of UNSUPPORTED
ENCLOSURE FUNCTION.
Requesting any Enclosure Service Diagnostic Page using the RECEIVE DIAGNOSTIC RESULTS command will return only Diagnostic Page 08h (Short Enclosure Status).
Long
This form is defined for use when the Enclosure and target are able to communicate using the secondary interface as defined in the SFF-8067 standard.
When mounted in this type of Enclosure, any attempt to access an Enclosure Service Diagnostic Page using the SEND DIAGNOSTIC or RECEIVE DIAGNOSTIC RESULTS commands results in the Diagnostic Page being transferred to/from
the enclosure. CHECK CONDITION status and sense data with an appropriate
Sense Key and Additional Sense Code is generated if the transfer fails or cannot be
performed.
Note: For a more detailed description of Enclosure Services, please refer to the following specifications:
•
SFF-8067 Specification
21.15.1 Enclosure Initiated ESI
This drive supports Enclosure Initiated ESI as described in the SFF-8067 standard.
21.16 Multiple Initiator Environment
21.16.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.
21.16.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.
21.17 Reset
Reset actions will return the drive to a known, initialized state.
Modify the remaining sentence to read: This device supports the Hard reset option as defined in the SCSI standards (see 7.1.9
Dev_Ctrl_Code_x on page 33) and the reset sources discussed below.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
284
21.17.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.
LIP Reset
This is a LIP(AL_PS_PD) primitive sequence where the AL_PD matches the AL_PA
of the drive.
Target Reset
This is an FCP_CMD IU with the TARGET RESET TMF flag set.
Reset LUN
This is a FCP_CMD IU with the RESET LUN TMF flag set.
21.17.2 Reset Actions
The action taken by the drive following a reset is dependent on the source of the reset.
21.17.2.1 Power-On reset and Self-Initiated reset
These two reset conditions cause the following to be performed in the order shown:
•
A power-up sequence
•
A startup sequence is necessary to put the drive in a ready state
These reset conditions cause the following actions:
•
If the reset occurs during the power-up sequence, the power-up sequence is re-started.
•
If the auto-start option is enabled and a start-up sequence has not yet completed, the start-up sequence is restarted.
Note: The power-up sequence is not re-run, since it has already completed.
•
If the reset occurs while a physical sector is being written, the WRITE operation is disabled at the end of the current
sector. The media is not corrupted if power is maintained to the end of the current sector.
21.18 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.
21.18.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)
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
285
6. Calibration of Actuator
7. Read/Write test for all Heads
8. Validation of RAM code and data table (RDM, Log, Mode Page) from the Reserved Area
If Auto spin up is disabled, steps 5 - 8 will be executed by the first START STOP UNIT command which has the Start bit set.
Faults detected before successful completion of the HDC section could prevent the drive from responding to a selection.
Faults detected after the successful completion of the HDC test section will be reported as CHECK CONDITION status to the
Initiator on the first command issued after a fault is detected (except for the INQUIRY, REPORT LUNS and REQUEST
SENSE commands). The INQUIRY, REPORT LUNS and REQUEST SENSE commands will always be responded with a
GOOD status. Detecting a fault during power on will not terminate execution of the tests nor will it terminate the power on
process.
21.18.2 Self-test via SEND DIAGNOSTIC Command
21.18.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.
21.18.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.
21.18.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
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
286
When the drive receives a SEND DIAGNOSTIC command specifying a self-test to be performed in the background mode, the
drive will return status for that command as soon as the command descriptor block has been validated. After returning status
for the SEND DIAGNOSTIC command specifying a self- test to be performed in the background mode, the drive will initialize the self-test results log page as follows. The Function Code from the SEND DIAGNOSTIC command will be placed in the
Function Code field in the log page. The self-test Results field shall be set to 0Fh. After the self-test results log page is initialized, the drive will begin the first self-test segment.
While the device server is performing a self-test in the background mode, it shall terminate with a CHECK CONDITION status any SEND DIAGNOSTIC command it receives that meets one of the following criteria:
a. The SlfTst bit is one
b. The Function Code field contains a value other than 000b or 100b.
When terminating the SEND DIAGNOSTIC command, the sense key shall be set to NOT READY and the additional sense
While performing a self-test in the background mode, the drive will suspend the self- test to service any other command other
than SEND DIAGNOSTIC (with Function Code field set to 100b) WRITE BUFFER (with the mode set to any download
microcode option), FORMAT UNIT and START UNIT STOP command. Suspension of the self-test to service the command
will occur within 2 seconds. If SEND DIAGNOSTIC (with Function Code field set to 100b), WRITE BUFFER (with the
mode set to any download microcode option), FORMAT UNIT or START UNIT STOP command is received, the drive will
abort the self-test, update the self-test log, and service the command within two seconds after the command descriptor block
has been validated.
An application client may terminate a self-test that is being performed in the background mode by issuing a SEND DIAGNOSTIC command with the Function Code field set to 100b (Abort background self-test function).
Elements common to foreground and background self-test modes
The Progress Indication field returned in response to a REQUEST SENSE command may be used by the application client at
any time during execution of a self-test to poll the progress of the test. While executing a self-test unless an error has occurred,
the drive will respond to a REQUEST SENSE command by returning a sense key of NOT READY and an additional sense
code of LOGICAL UNIT NOT READY - SELF-TEST IN PROGRESS with the sense key specific bytes set for progress indication.
The application client may obtain information about the twenty most recently completed self-tests by reading the self-test
results log page. This is the only method for an application client to obtain information about self-tests performed in the background mode. The default self-test results are not logged in the log page.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
287
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 252: 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 21.18.2.1, “Default Self-test” on page 286
3h
SMART
Perform SMART testing and check results to ensure that
SMART threshold criteria are not exceeded
4h
Low Level Format check
Check to insure that the media is currently not in the
MEDIA FORMAT CORRUPTED state.
5h
Physical Head Check
Write/Read test on each head in a predefined location in
the drive's Reserved Area of the disk.
6h
Random Verify
Perform 4000 random verify operations and insure no
uncorrectable errors.
7h
- Verify First
300MB
Verify all
LBA’s
Sequential verify operation. Ensure that no uncorrectable errors occur within the verify range.
- Verify Last
100 MB
8h
Recheck SMART
Same as segment 3h.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
288
21.19 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.
21.20 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.
21.20.1 Reassignment Time
The drive should be allowed a minimum of 5 seconds to complete a “Reassign Blocks” command.
21.20.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."
21.20.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 FC-AL Hard Disk Drive Specification
289
21.20.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.
21.20.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 FC-AL Hard Disk Drive Specification
290
21.21 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.
21.21.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 FC-AL Hard Disk Drive Specification
291
21.21.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)
21.21.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 19.10.3, “Mode Page 01
(Read/Write Error Recovery Parameters)” on page 168) 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 FC-AL Hard Disk Drive Specification
292
21.21.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 253, the Key, Code, and Qualifier fields are all hex values (i.e., Sense Key 1 is 1h, Sense Code 17 is 17h,
Table 253: 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 21.21.3.3,
“Reassign Blocks Recovery” on page 294.
3.
Write the LBA that was reassigned.
21.21.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 254: 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 FC-AL Hard Disk Drive Specification
293
21.21.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 19.22, “REASSIGN BLOCKS (07)” on page 218, 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 21.21.1, “Drive Service Strategy” on page 291.
21.21.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.
21.21.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 21.21, “Command Time out Limits” on
page 297, then service the drive using the service guidelines recommended in Section 21.21.1, “Drive Service
Strategy” on page 291. Otherwise return to normal processing.
•
If the Test Unit Ready (00) (or media access) command completes with Good Status, then return to normal processing.
21.21.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 21.21.4.3, “Recovered Drive Error” on page 295.
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
21.21.4.3, “Recovered Drive Error” on page 295.
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 21.21.1, “Drive Service Strategy” on page 291.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
294
21.21.4.3 Recovered Drive Error
The Initiator should log the error as soft with the recovery level.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
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 21.21.1, “Drive Service Strategy”
on page 291.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
21.21.4.6 Degraded Mode
Refer to Section 21.6.9, “Degraded Mode” on page 272, 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 21.21, “Command Time out Limits”
on page 297, service the drive using the service guideline recommended in Section 21.21.1, “Drive Service Strategy”
on page 291.
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 21.21.1, “Drive Service
Strategy” on page 291.
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 21.21.1, “Drive Service
Strategy” on page 291.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
295
- 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 21.21.1, “Drive Service Strategy” on page 291, 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 21.21.1, “Drive Service Strategy” on page 291.
If the above defined recovery procedures fail to clear the degraded mode condition, the Drive should be replaced. Follow the
procedure in Section 21.21.1, “Drive Service Strategy” on page 291, when replacing the drive.
21.21.4.7 Reserved Area Hard Error
Sectors found defective in the reserved area of the disk cannot be reassigned after the Drive leaves the factory. The data in the
reserved area is not directly accessible by the initiator. For this reason, the reserved area has all data. A data error must occur in
both copies of the data record before the Drive considers a reserved area read error. When this happens, the integrity of the
drive is questionable.
Service the Drive using Section 21.21.1, “Drive Service Strategy” on page 291.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
• Other, follow the recommendations for the error condition reported.
21.21.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 FC-AL Hard Disk Drive Specification
296
- 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 21.21.1,
“Drive Service Strategy” on page 291.
•
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.
21.21.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, LIP Reset, Target 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 19.6, “LOG SELECT (4C)” on page 134). 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 19.35, “SET DEVICE IDENTIFIER (A4)” on page 241) A Unit Attention Condition is reported to all initiators excluding the initiator that issued the Set Device Identifier command.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
297
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
- Other, follow the recommendations for the error reported.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
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 FC-AL Hard Disk Drive Specification
298
21.21.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 21.21.1, “Drive Service Strategy” on
page 291.
- 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 21.21.1, “Drive Service Strategy” on page 291.
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
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 21.21.1, “Drive Service Strategy” on page 291.
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 21.21.1, “Drive Service Strategy” on page 291.
- 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
21.21.1, “Drive Service Strategy” on page 291.
•
Check Condition Status for any other error, follow the recommendations for the returned sense data.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
299
21.21.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 21.21.1, “Drive Service Strategy” on page 291.
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 FC-AL Hard Disk Drive Specification
300
22.0 SCSI Sense Data
22.1 SCSI Sense Data Format
Format of the sense data returned by the drive in response to the REQUEST SENSE command.
Table 255: 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 Hard Disk Drive Specification
301
22.2 Sense Data Description
22.2.1 Valid (Bit 7 of byte 0)
0
The Information Bytes (byte 3 through 6) are not defined.
1
The Information Bytes (byte 3 through 6) contain a valid logical block address.
22.2.2 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.
22.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 FC-AL Hard Disk Drive Specification
302
22.2.4 Sense Key (Bit 3 - 0 of byte 2)
The sense key provides generic categories in which error and exception conditions can be reported. Initiators would typically
use sense keys for high level error recovery procedures.
0h
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 269)
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 Hard Disk Drive Specification
303
22.2.5 Information Bytes (Byte 3 through 6)
This field is only valid when Valid Bit is one.
•
ILI = 0: This field contains the unsigned LBA associated with the sense key. The LBA reported will be within the
LBA range of the command as defined in the CDB.
Note:
An LBA other than the command LBA may be reported on the Reassign Block (07h) command.
•
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
22.2.6 Additional Sense Length (Byte 7)
Indicates the remaining number of bytes in the sense data. (It is always set to 18h.)
22.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 FC-AL Hard Disk Drive Specification
304
22.2.8 Additional Sense Code/Qualifier (Byte 12 and 13)
The following table shows the description of the combination of Sense Key / Sense Code / Qualifier.
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 Hard Disk Drive Specification
305
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 FC-AL Hard Disk Drive Specification
306
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 Hard Disk Drive Specification
307
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 FC-AL Hard Disk Drive Specification
308
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 Hard Disk Drive Specification
309
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 FC-AL Hard Disk Drive Specification
310
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 Hard Disk Drive Specification
311
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 FC-AL Hard Disk Drive Specification
312
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 Hard Disk Drive Specification
313
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 FC-AL Hard Disk Drive Specification
314
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 Hard Disk Drive Specification
315
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 FC-AL Hard Disk Drive Specification
316
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 Hard Disk Drive Specification
317
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 FC-AL Hard Disk Drive Specification
318
22.2.9 RU: Field Replaceable Unit (Byte 14)
The FRU (Field Replaceable Unit) field value will always be zero.
22.2.10 Sense Key Specific (Byte 15 through 17)
The definition of this field is determined by the value of the sense key field.
22.2.10.1 Sense Key Specific - Illegal Request (Sense Key = 5h)
Error field pointer is returned.
Table 256: 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 Hard Disk Drive Specification
319
22.2.10.2 Sense Key Specific - Recovered (Sense Key = 1h) or Medium (Sense Key = 3h) or Hardware (Sense Key = 4h)
Hardware (Sense Key = 4h) or Medium Error (Sense Key = 3h)
Actual Retry Count is reported.
Table 257: Actual Retry Count
Bit
Byte
7
15
SKSV
6
5
4
3
2
1
0
Reserved
16
Secondary Step
17
ERP Type
Actual Retry Count
SKSV
Sense-key specific valid
0
Actual Retry Count is not valid.
1
Actual Retry Count is valid.
Actual Retry Count
Number of retry steps used in attempting to recover from the error condition.
Secondary Step
Secondary error recovery step (valid for servo errors only).
ERP Type
Error recovery table branch for this error. Valid values are shown in the table below.
Recovery Type
ERP Type
Read
0x00
Verify
0x01
Write
0x02
Seek
0x03
Read, Sync Byte branch
0x04
Read, Thermal Asperity branch
0x05
Read, Minus Mod branch
0x06
Verify, Sync Byte branch
0x07
Verify, Thermal Asperity branch
0x08
Verify, Minus Mod branch
0x09
22.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 FC-AL Hard Disk Drive Specification
320
Progress indication is returned.
Table 258: Progress Indication
Bit
Byte
7
15
SKSV
16
(MSB)
6
5
4
3
2
Progress Indication
0
Reserved
Progress Indication
17
SKSV
1
(LSB)
Sense-key specific valid
0
Progress Indication is not valid.
1
Progress Indication is valid.
Indicates a percent complete in which the returned value is the numerator that has 10000h as its
denominator.
Hitachi Ultrastar 15K147 Hard Disk Drive Specification
321
22.2.11 Reserved (Byte 18 through 19)
Reserved fields are filled with zero.
22.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.
22.2.13 Physical Error Record (Byte 24 thru 29)
•
ILI = 1 - This field contains zeros.
•
ILI = 0 - These bytes contain the physical location of the error in cylinder, head, and sector. Bytes 24, 25, and 26 are
cylinder high, middle and low bytes respectively, of the cylinder number. Byte 27 is the head number. Bytes 28 and
29 are the the high and low bytes, respectively of the sector number.
If the head is undetermined, bytes 24, 25, and 26 are set to 0FFFFFFh. If the head number is undetermined, byte 27 is
set to 0FFh. If cylinder, head, and sector have no relevance the the error, bytes 24 through 29 will all be set to
0FFFFFFFFFFFFh for Valid = 0 and ILI = 0. This Physical Error Record field is valid for Sense Key 1, 3, and 4 only.
Valid
ILI
Description
1
0
Cylinder Number (bytes 24-26)
Head number (byte 27)
Sector Number (bytes 28-29)
1
1
0x000000000000
0
x
0x000000000000 - (not used/invalid)
22.2.14 Reserved (Byte 30 through 31)
Reserved fields are filled with zero.
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
322
23.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 22.0, “SCSI Sense Data” on page 309. 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 259: 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
F11A
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
BATS#2 error: ECC test error
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
323
UEC
Description
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: 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
F306
Motor: Recovered internal error
Motor: Unrecovered internal error
Motor: Recovered Open Loop Commutation failure
Motor: Unrecovered Open Loop Commutation failure
Motor: Recovered No feedback detected error
Motor: Unrecovered No feedback detected error
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
324
UEC
Description
1307
F308
1309
F30A
130B
F30C
130D
F30E
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
F420
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
Servo: Unrecovered Seek error
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
325
UEC
Description
1421
F422
1423
F424
1425
F426
1427
F428
1429
F42A
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
151E
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
Reservations pre-empted
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
326
UEC
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
1550
Description
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)
ESI: transfer failed - write ack
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
327
UEC
Description
1551
1552
1553
1554
1555
1556
1557
1558
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
F71B
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
Unrecovered ECC overrun
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
328
UEC
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
1745
Description
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
Defect list not found
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
329
UEC
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
176E
Description
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
Recovered data with NRZ parity error
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
330
UEC
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
F79B
Description
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
Unrecovered Channel Pre-TA error
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
331
UEC
Description
179C
F79D
F79E
F79F
F7A0
F7A1
F7A2
F7A5
F7B1
17B2
F7B3
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)
FCxx
Unable to read RID or FID number xx
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
332
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
333
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
334
A
Abbreviations ..................................................................................................................117
abort sequence .................................................................................................................57
abort task .........................................................................................................................111
Abort Task (Implemented as ABTS BLS) ......................................................................111
abort task set ...................................................................................................................111
Acoustics .........................................................................................................................45
Active Notch ...................................................................................................................182
Actuator ..........................................................................................................................5
Additional information ...................................................................................................261
Additional Sense Length (Byte 7) ..................................................................................304
Address Discovery ..........................................................................................................77
address discovery (ADISC) ............................................................................................77
Alternate Sectors per Zone .............................................................................................174
Alternate Tracks per Logical Unit ..................................................................................174
Alternate Tracks per Zone ..............................................................................................174
Appendix .........................................................................................................................323
auto-contingent allegiance (ACA) ..................................................................................112
Automatic Read Reallocation Enabled ...........................................................................168
Automatic Rewrite/Reallocate ........................................................................................281
Automatic Write Reallocation Enabled ..........................................................................168
autosense .........................................................................................................................113
Average latency ..............................................................................................................12
B
basic accept (BA_ACC) ..................................................................................................58
Basic Link Services ........................................................................................................57
basic link services ...........................................................................................................57
basic reject (BA_RJT) ....................................................................................................59
Block Descriptor .............................................................................................................164
block format ....................................................................................................................121
Breather Hole ..................................................................................................................41
buffer overrun .................................................................................................................155
buffer underrun ...............................................................................................................155
Byte ordering conventions ..............................................................................................117
bytes from index format ..................................................................................................122
C
capability entry(s) ...........................................................................................................87
Caution ............................................................................................................................1
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
335
class service parameters ..................................................................................................68, 75
clear ACA .......................................................................................................................112
clear task set ....................................................................................................................112
Command Processing During Execution of Active I/O process .....................................268
Command Processing During Startup and Format Operations .......................................271
Command processing while reserved .............................................................................279
Command Queuing .........................................................................................................280
Command queuing ..........................................................................................................280
Command Reordering .....................................................................................................280
Command reordering ......................................................................................................280
Command Time out Limits .............................................................................................289
Common Fibre Channel Services ...................................................................................97
common service parameters ............................................................................................65
common transport (CT) interface ...................................................................................97
Concurrent I/O Process ...................................................................................................280
concurrent sequences ......................................................................................................70
Control Electronics .........................................................................................................5
Cooling requirements ......................................................................................................29
Corrosion test ..................................................................................................................28
cyclic redundancy check (CRC) .....................................................................................56
Cylinder switch time (Cylinder skew) ............................................................................12
D
Data Integrity ..................................................................................................................17
Data Reliability ...............................................................................................................35
Data Sheet .......................................................................................................................7
Data transfer speed ..........................................................................................................13
DC Power Requirements ................................................................................................31
Defect Descriptor ............................................................................................................121
defect descriptor ..............................................................................................................121
defect list .........................................................................................................................120
Deferred Error Condition ................................................................................................271
Degraded Mode ...............................................................................................................272
device cache fast writes ..................................................................................................156
device cache partial read hits ..........................................................................................156
device cache write hits ....................................................................................................156
Diagnostics ......................................................................................................................285
Disable Block Descriptor ................................................................................................161
document identifier .........................................................................................................88
Download Microcode and Save (Mode 0101b) ..............................................................253
Drive Characteristics .......................................................................................................7
Drive Mounting ...............................................................................................................41
Drive ready time .............................................................................................................13
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
336
E
Effects of LIP on Command Queuing ............................................................................280
effects of LIP on command queuing ...............................................................................280
Electrical Interface ..........................................................................................................21
Electromagnetic Compatibility .......................................................................................49
enclosure services ...........................................................................................................283
end-to-end credit .............................................................................................................70
Environment ....................................................................................................................27
Equipment errors .............................................................................................................35
Equipment Status ............................................................................................................17
European Standards Compliance ....................................................................................51
exchange .........................................................................................................................57
Extended Link Services ..................................................................................................60
extended link services .....................................................................................................60
F
Fabric ..............................................................................................................................72
fabric address notification (FAN) ...................................................................................76
Fabric Login ....................................................................................................................72
fabric login (FLOGI) ......................................................................................................72
Failure prediction (PFA/S.M.A.R.T) ..............................................................................35
FC-AL attachment ..........................................................................................................53
FC-AL Connector ...........................................................................................................21
FC-AL timers ..................................................................................................................101
FCP_CDB .......................................................................................................................106
FCP_CMND IU ..............................................................................................................105
FCP_CNTL .....................................................................................................................105
FCP_DL ..........................................................................................................................106
FCP_LUN .......................................................................................................................105
FCP_RESID ....................................................................................................................108
FCP_RSP_INFO .............................................................................................................109
FCP_RSP_LEN ..............................................................................................................108
FCP_SNS_INFO .............................................................................................................109
FCP_SNS_LEN ..............................................................................................................108
FCP_XFER_RDY ...........................................................................................................107
Flammability ...................................................................................................................51
Flow Control ...................................................................................................................263
FORMAT UNIT .............................................................................................................118
format unit .......................................................................................................................118
Formatted Capacity .........................................................................................................7
frame delimiter ................................................................................................................55
frames ..............................................................................................................................56
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
337
Full stroke seek time .......................................................................................................12
Fundamentals ..................................................................................................................53
G
German Safety Mark .......................................................................................................51
Glossary ..........................................................................................................................1
Grown Defect List (Glist) ...............................................................................................211
H
Head Disk Assembly ......................................................................................................5
Head Offset Count ..........................................................................................................169
Head switch time ............................................................................................................12
I
Identification ...................................................................................................................47
Idle Time Function ..........................................................................................................289
IEEE registered name format ..........................................................................................54
Incorrect Length Indicator (Bit 5 of byte 2) ....................................................................302
information units (IUs) ...................................................................................................103
initiator control (IC) ........................................................................................................69
inquiry .............................................................................................................................124
Interface Connector .........................................................................................................39
Internal Error Condition ..................................................................................................271
invalid transmission word ...............................................................................................85
L
Labels ..............................................................................................................................47
link failure .......................................................................................................................102
link failure count .............................................................................................................85
link service accept (LS_ACC) ........................................................................................61
link service reject (LS_RJT) ...........................................................................................62
Log Page Parameters ......................................................................................................138
LOG SELECT .................................................................................................................134
LOG SELECT (4C) ........................................................................................................134
LOG SENSE ...................................................................................................................137
LOG SENSE (4D) ..........................................................................................................137
Logical Block Cache Segment Size ................................................................................179
Logout (LOGO) ..............................................................................................................71
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
338
logout (LOGO) ...............................................................................................................71
loop initialization frame ..................................................................................................61
Loop Initialization Procedure .........................................................................................261
loop initialization procedure ...........................................................................................261
loss of signal count .........................................................................................................85
loss of sync count ............................................................................................................85
M
Maximum Burst Size ......................................................................................................173
Maximum Pre-fetch ........................................................................................................179
Maximum Pre-fetch Ceiling ...........................................................................................179
Mechanical positioning ...................................................................................................11
Mechanical Specifications ..............................................................................................37
Merge G-List into P-List .................................................................................................166
Minimum Pre-fetch .........................................................................................................179
MODE SELECT .............................................................................................................159, 160
MODE SELECT (15) .....................................................................................................159
MODE SELECT (55) .....................................................................................................160
MODE SENSE (1A) .......................................................................................................161
MODE SENSE (5A) .......................................................................................................189
Multiple Initiator Environment .......................................................................................284
Multiple Initiator Systems ..............................................................................................283
multiple initiator systems ................................................................................................283
N
N_Port ID ........................................................................................................................78
NL_Port address .............................................................................................................54
Node and Port names ......................................................................................................54
node name .......................................................................................................................54, 78
Non-operating shock .......................................................................................................44
Non-operating Vibrations ...............................................................................................43
O
Obtaining an AL_PA ......................................................................................................261
obtaining an AL_PA .......................................................................................................261
open sequences per exchange .........................................................................................71
Operating shock ..............................................................................................................43
Operating Vibration ........................................................................................................43
ordered set .......................................................................................................................55
originator process associator ...........................................................................................79
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
339
Outline ............................................................................................................................37
Outline of the Drive ........................................................................................................3
overrun counter ...............................................................................................................156
P
Packaging ........................................................................................................................28
Page Code Valid .............................................................................................................220
Page Format ....................................................................................................................236
Parameter data for Read Keys .........................................................................................192
Parameter data for Read Reservations ............................................................................193
payload length .................................................................................................................86
Persistent Reservation .....................................................................................................191
PERSISTENT RESERVE IN (5E) .................................................................................191
PERSISTENT RESERVE OUT .....................................................................................195
PERSISTENT RESERVE OUT (5F) .............................................................................195
Persistent Reserve Out Parameter list .............................................................................200
Physical Format ..............................................................................................................19
physical sector format .....................................................................................................123
Physical Sector Format (101b) .......................................................................................214
port discovery (PDISC) ..................................................................................................77
port login (PLOGI) .........................................................................................................63
port name ........................................................................................................................78
Post Error ........................................................................................................................169
Predictive Failure Analysis .............................................................................................300
PRE-FETCH ...................................................................................................................202
Preventive Maintenance ..................................................................................................35
Primary Defect List .........................................................................................................211
primitive sequence ..........................................................................................................55
primitive sequence protocol error ...................................................................................85
primitive signal ...............................................................................................................55
Priority Commands .........................................................................................................279
Priority commands ..........................................................................................................279
process login (PRLI) .......................................................................................................78
process logout (PRLO) ...................................................................................................82
Product ID .......................................................................................................................8
public loop operation ......................................................................................................264
Q
Queue Depth ...................................................................................................................280
Queue Full Status ............................................................................................................280
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
340
R
Random access ................................................................................................................15
Random Vibration ...........................................................................................................43
READ (10) - (28) ............................................................................................................204
Read Ahead .....................................................................................................................283
READ BUFFER (3C) .....................................................................................................205
Read Buffer Full Ratio ....................................................................................................173
Read Cache Disable ........................................................................................................179
READ CAPACITY .........................................................................................................209
READ CAPACITY command ........................................................................................209
Read Continuous .............................................................................................................168
READ DEFECT DATA (37) ..........................................................................................211
READ DEFECT DATA (B7) .........................................................................................215
read link error status block (RLS) ...................................................................................84
READ LONG command .................................................................................................217
Read Retry Count ............................................................................................................169
REASSIGN BLOCKS (07) ............................................................................................218
receive data field .............................................................................................................70
RECEIVE DIAGNOSTICS (1C) ....................................................................................220
Recommended Initiator ERP ..........................................................................................291
register FC-4 types (RFT_ID) .........................................................................................99
re-instate recovery qualifiers (RRQ) ...............................................................................90
RELEASE (17) ...............................................................................................................226
RELEASE (57) ...............................................................................................................227
Reliability ........................................................................................................................35
REPORT LUNS (A0) .....................................................................................................230
report node capabilities (RNC) .......................................................................................86
Report Recovered Non Data Errors ................................................................................166
REQUEST SENSE (03) ..................................................................................................231
RESERVE (16) ...............................................................................................................232
RESERVE (56) ...............................................................................................................233
Reserved Area .................................................................................................................223
Reset ................................................................................................................................284
Reset Actions ..................................................................................................................285
responder process associator ...........................................................................................79, 92
REZERO UNIT (01) .......................................................................................................234
Ripple Voltage ................................................................................................................33
RNC flags .......................................................................................................................86
S
S.M.A.R.T .......................................................................................................................35
Safety ..............................................................................................................................51
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
341
SCSI Command Set ........................................................................................................115
SCSI Control Byte ..........................................................................................................117
SCSI Protocol .................................................................................................................267
SCSI Sense Data .............................................................................................................301
SCSI Sense Data Format .................................................................................................301
SCSI Status Byte .............................................................................................................259
SCSI Status Byte Reporting ............................................................................................267
SCSI-FCP ........................................................................................................................103
Sectors per Track ............................................................................................................175
SEEK (10) - (2B) ............................................................................................................235
SEEK (6) - (0B) ..............................................................................................................235
seek counter ....................................................................................................................155
Seek errors ......................................................................................................................35
seeks ................................................................................................................................155
Segmented Caching ........................................................................................................283
SEND DIAGNOSTIC (1D) ............................................................................................236
sense data ........................................................................................................................283
Sense Data Description ...................................................................................................302
Sense Key (Bit 3 - 0 of byte 2) .......................................................................................303
SenseData ........................................................................................................................301
sequence ..........................................................................................................................56
Service Action .................................................................................................................191, 196
Size Enable .....................................................................................................................178
Sound power levels .........................................................................................................45
Spindle stop time ............................................................................................................13
START STOP UNIT (1B) ..............................................................................................242
Start/Stop Cycles .............................................................................................................35
Storage requirements ......................................................................................................28
Storage time ....................................................................................................................28
Swept Sine Vibration ......................................................................................................43
SYNCHRONIZE CACHE (35) ......................................................................................243
T
target reset .......................................................................................................................112
Task Attributes ................................................................................................................109
Task Management functions ...........................................................................................110
task management functions .............................................................................................103
Temperature and humidity ..............................................................................................27
Temperature Threshold ...................................................................................................167
terminate task ..................................................................................................................112
Terminology ....................................................................................................................103
TEST UNIT READY (00) ..............................................................................................244
third party N_Port ID ......................................................................................................92
third party originator process associator .........................................................................92
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
342
third party process logout (TPRLO) ...............................................................................91
Throughput ......................................................................................................................14
Track Skew Factor ..........................................................................................................175
Tracks per Zone ..............................................................................................................175
Transfer Block ................................................................................................................168
transmission character .....................................................................................................55
U
UEC list ...........................................................................................................................323
UL and CSA Standard Conformity .................................................................................51
underrun counter .............................................................................................................156
Unit Attention Condition ................................................................................................297
unit attention condition ...................................................................................................269
V
vendor identifier ..............................................................................................................86
vendor unique information ..............................................................................................86
Verify ..............................................................................................................................299
VERIFY (2F) ..................................................................................................................245
Verify Correction Span ...................................................................................................177
Vibration and Shock .......................................................................................................43
VU information length (VU_Len) ..................................................................................86
W
word ................................................................................................................................55
WRITE (10) - (2A) .........................................................................................................248
WRITE (6) - (0A) ...........................................................................................................247
WRITE AND VERIFY (2E) ...........................................................................................249, 250
WRITE BUFFER (3B) ...................................................................................................254
Write Buffer Empty Ratio ...............................................................................................173
Write Cache ....................................................................................................................281
Write Cache Enable ........................................................................................................178
WRITE LONG (3F) ........................................................................................................254
Write Retention Priority ..................................................................................................179
Write Retry Count ...........................................................................................................169
WRITE SAME (41) ........................................................................................................256
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
343
Z
zero seeks ........................................................................................................................155
Hitachi Ultrastar 15K147 FC-AL Hard Disk Drive Specification
344
© Copyright Hitachi Global Storage Technologies
Hitachi Global Storage Technologies
5600 Cottle Road
San Jose, CA 95193
Produced in the United States
05/06
All rights reserved Ultrastar™ is a trademark of
Hitachi Global Storage Technologies.
Microsoft, Windows XP, and Windows are trademarks
of Microsoft Corporation in the United States, other
countries, or both.
Other product names are trademarks or registered trademarks of their respective companies.
References in this publication to Hitachi Global Storage
Technologies products, programs or services do not
imply that Hitachi Global Storage Technologies intends
to make these available in all countries in which Hitachi
Global Storage Technologies operates.
Product information is provided for information purposes only and does not constitute a warranty.
Information is true as of the date of publication and is
subject to change. Actual results may vary.
This publication is for general guidance only. Photographs may show design models.
25 May 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