Hard Disk Drive Specification Ultrastar 15K450 3.5 inch 4Gb FC-AL Hard Disk Drive Models: HUS154545VLF400 HUS154530VLF400 Version 1.2 29 October 2008 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.
3rd Edition (Rev. 1.2) (29 October 2008) 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.
Table of Contents 1.0 General............................................................................................................................1 1.1 Introduction................................................................................................................1 1.2 Glossary .....................................................................................................................1 1.3 Caution....................................................................................
8.2.1 Packaging..........................................................................................................26 8.2.2 Storage time ......................................................................................................26 8.3 Corrosion test .............................................................................................................26 8.4 Cooling requirements.................................................................................................27 9.
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.........................
18.4.5 Target Reset ....................................................................................................112 18.4.6 Clear Task Set .................................................................................................112 18.4.7 Reset LUN ......................................................................................................112 18.5 Miscellaneous ..........................................................................................................112 18.5.1 Tags..
19.10.12 Mode Page 19h (Fibre Channel Port Control Page) ...................................190 19.10.13 Mode Page 1A (Power Control) .................................................................192 19.10.14 Mode Page 1C (Informational Exceptions Control) ...................................193 19.11 MODE SENSE (5A) ..............................................................................................196 19.12 PERSISTENT RESERVE IN (5E) ............................................................
19.28 RELEASE (17) ......................................................................................................246 19.29 RELEASE (57) ......................................................................................................247 19.30 REPORT DEVICE IDENTIFIER (A3/05)............................................................248 19.31 REPORT LUNS (A0) ............................................................................................250 19.
19.62 WRITE SAME (16) - (93) .....................................................................................303 19.63 WRITE SAME (32) - (7F/0D)...............................................................................304 20.0 SCSI Status Byte ..........................................................................................................307 21.0 Additional information...............................................................................................309 21.
21.18.1 Power on Diagnostics ...................................................................................333 21.18.2 Self-test via SEND DIAGNOSTIC Command.............................................334 21.19 Idle Time Function.................................................................................................337 21.20 Command Time out Limits ...................................................................................337 21.20.1 Reassignment Time...................................
List of Tables Table 1.Product ID table ............................................................................................1 Table 2.Formatted Capacity.......................................................................................7 Table 3.Data Sheet .....................................................................................................7 Table 4.Product ID in Inquiry Command ..................................................................8 Table 5.
Table 45.ADISC payload...........................................................................................77 Table 46.ADISC ACC payload .................................................................................78 Table 47.PRLI payload ..............................................................................................78 Table 48.PRLI ACC payload.....................................................................................79 Table 49.Login Service Parameter page ...............
Table 91.FCP_RSP_INFO field ................................................................................109 Table 92.RSP_CODE definitions ..............................................................................109 Table 93.Task Management function RSP_CODE definitions .................................110 Table 94.SCSI Commands Supported .......................................................................115 Table 95.SCSI Control Byte .............................................................
Table 137.Mode parameter header (6).......................................................................168 Table 138.Mode parameter header (10).....................................................................169 Table 139.Mode Parameter Block Descriptor ...........................................................170 Table 140.Mode Parameter Page Format ..................................................................171 Table 141.Mode Parameter Page Format ............................................
Table 183.READ DEFECT DATA (37)....................................................................226 Table 184.Defect List Format ....................................................................................227 Table 185.Defect List Header ....................................................................................228 Table 186.Defect List Descriptor...............................................................................229 Table 187.Defect Descriptors of Bytes from Index Format ....
Table 229.VERIFY (2F) ............................................................................................273 Table 230.Verify (12) - (AF) .....................................................................................276 Table 231.Verify (16) - (8F) ......................................................................................277 Table 232.Verify (32) - 7F/0A) .................................................................................278 Table 233.WRITE (6) - (0A) ..............
1.0 General 1.1 Introduction This document describes the specifications of the following Hitachi 3.5 inch FC-AL drives. Table 1: Product ID table Product ID Description HUS154545VLF400 450 GB, FC-AL HUS154530VLF400 300 GB, FC-AL Note: The specifications in this document are subject to change without notice. For technical and ordering information, please visit our website at http://www.hitachigst.com. 1.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 2
2.0 Outline of the Drive • Storage capacities of 450 GB, 300 GB • Dual 4.250/2.1250/1.0625 Gb/s Fibre Channel Arbitrated Loop-2 host interfaces • Supports dual-ported operations • Supports full duplex 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.
Hitachi Ultrastar 15K450 (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.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 6
4.0 Drive Characteristics 4.1 Formatted Capacity Table 2: Formatted Capacity Description HUS154545VLF400 HUS154530VLF400 Label capacity 450 GB 300 GB Number of heads 8 8 Number of disks 4 4 450,098,159,616 300,000,000,000 879,097,968 (3465F870h) 585,937,500 (22ECB25Ch) Total data bytes (512 bytes/sector) Total logical data blocks 4.
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 126, is as follows: Table 4: Product ID in Inquiry Command Product ID Description HUS154545VLF400 450 GB, FC-AL HUS154530VLF400 300 GB, FC-AL 4.3.
4.
User Cylinder Allocation 300 GB Start Zone Sectors /Tracks Cylinder/Zone Cylinder 0 1188 5800 0 1 1170 13300 5800 2 1147 6400 19100 3 1134 3000 25500 4 1125 1200 28500 5 1080 13800 29700 6 1041 800 43500 7 1035 1800 44300 8 1026 1900 46100 9 1012 2700 48000 10 1002 600 50700 11 990 3100 51300 12 972 2200 54400 13 945 4600 56600 14 918 2600 61200 15 900 3300 63800 16 877 2500 67100 17 864 200 69600 End Cylinder 5799 19099 25499 28499 29699 43499 44299 46099 47999 50699 51299 54399 56599 61199 63799 67099 69
4.5.1 Mechanical positioning 4.5.1.1 Average seek time (including settling) Table 7: Mechanical positioning performance Model Command 450 GB 300 GB Typical (ms) Max Read 3.3 5.0 Write 3.8 5.4 Read 3.1 4.5 Write 3.6 5.1 “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.
4.5.1.2 Full stroke seek time Model Command 450 GB 300 GB Typical (ms) Max Read 6.2 11.1 Write 7.1 11.5 Read 5.8 9.4 Write 6.4 10.1 Full stroke seek is measured as the average of 1,000 full stroke seeks with a random head switch from both directions (inward and outward). 4.5.1.3 Average latency Table 8: Latency time Rotation Time for a revolution (ms) Average latency (ms) 15,000 RPM 4.0 2.
4.5.2 Drive ready time Table 9: Drive ready time Model Typical (sec) Maximum (sec) 450 GB Model 21.0 29.9 300 GB Model 21.0 29.9 Model Typical (sec) Maximum (sec) 450 GB Model 11.0 20 300 GB Model 11.0 20 4.5.3 Spindle stop time Table 10: Spindle stop time The period from power off to the complete stop of the rotating spindle is categorized as 'operating'. The Operating shock criteria apply during this period. Refer to section 12.3, “Operating shock” on page 41. 4.5.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 14
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.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 16
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. • All pushes generated by defects are absorbed by available tracks of the inner notch. P-List Physical Format Note: Defects are skipped without any constraint, such as track or cylinder boundary.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 18
7.0 Electrical Interface 7.1 FC-AL Connector The drive conforms to SFF specifications 8045, 8067 and 8451. The SFF 8045/8067 documents defines the electrical specification and SFF-8451 defines the mechanical 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.
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.
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 13: Start/Mated Controls Start_2 Mated Start_1 Mated Spin Function Open Open Drive is not mated. No spin-up will occur.
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
Table 15: 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 supp
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, DEV_CTRL_CODE_1 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.
8.0 Environment 8.1 Temperature and humidity Table 17: Operating and non-operating conditions Operating conditions Ambient Temperature 5°C to 55ºC Relative humidity 5 to 90%, non-condensing Maximum wet bulb temperature 29.
100 36'C/95% 90 31'C/90% 80 WetBuib=35.0'C Relative Humidity (%) 70 WetBuib=29.4'C 60 Non-operating 50 40 Operating 30 65'C/14% 20 55'C/15% 10 0 -45 -35 -25 -15 -5 5 15 25 35 45 55 65 Temperature ('C) 8.2 Storage requirements 8.2.1 Packaging The drive or option kit must be heat-sealed in a moisture barrier bag with desiccant 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.
8.4 Cooling requirements Drive component surface temperatures must remain within the limits specified in the following table. The drive may require forced air cooling to meet specified operating temperatures.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 28
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 on or power off sequencing requirement. Adequate secondary over-current protection is the responsibility of the system. Table 19: Input Voltage and capacitance Tolerance Absolute Max Spike Voltage Supply Rise Time Capacitance +5 Volts Supply +/- 5% 5.
9.1 Power Supply Current, Average and Peak The following current and power requirements are typical when operating under the following conditions: Nominal 5 and 12V, Background Media Scan (BMS) disabled for Idle, Write Caching disabled and the drive reporting a temperature of 45C.
Model FC 4 Gb/ s Start Peak Power DC Start Peak Power AC Idle Idle Ripple Random W / R Peak Random W / R Average Random W / R Average Sequential Read Peak Sequential Read Average Sequential Write Peak Sequential Write Average BMS Average BMS Peak 300 GB Current IO / Sec +5V Current +12V --1.12 0.83 0.25 1.36 0.88 0.86 0.85 0.85 0.84 0.84 1.92 2.44 0.71 0 .1 9 2.24 1.07 1.02 1.01 0.99 0.98 0.98 215 215 164 120 90 60 30 1.60 1.38 1.60 1.31 0.97 1.46 0.74 --0.74 0.74 Power Watts Note --12.7 --17.
9.2 Ripple Voltage Table 20: Power Supply Generated Ripple at Drive Power Connector Maximum (mV pp) MHz +5 V DC 250 0-10 +12 V DC 250 0-10 During drive start up and seek, 12 volt ripple is generated by the drive (referred to as dynamic loading). If the power of several drives is daisy chained, the power supply ripple plus other drive dynamic loading must remain within the regulation tolerance of +5%.
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 25. 10.2 Data Reliability The probability of an uncorrectable data error is 1 in 1016 bits read.
The drive temperature is reported in Log Sense page 2F. Refer to Section 19.7.12, “Log Sense Page 2F” on page 159.
11.0 Mechanical Specifications 11.1 Outline 11.2 Mechanical Dimensions The drive complies with SFF-8301. Table 22: Physical Dimensions Height [mm] 25.8 ± 0.3 Width [mm] 101.6 ± 0.25 Length [mm] 146.2 ± 0.
101. 6 ±0. 25 146. 2 ±0. 8 25. 8 ±0.
11.3 Interface Connector 4. 6 ±0.
11.4 Mounting Positions and Tappings ( 2x) 41. 28 ±0. 2 ( 2x ) 44. 45 ±0. 2 ( 4X) 6- 32 UNC ( 2x ) 95. 25 ±0. 2 ( 2 X) 3 . 1 8 ± 0 . 2 5 REAR RECOMMENDED TORQUE 0. 6 - 1. 0 Nm 1 MAX ALLOWABLE PENETRATI ON OF NOTED SCREW TO BE 4.
60 ±0. 2 28. 6 ±0. 2 ( 2x ) ( 2x ) 41. 6 ±0. 2 ( 2x ) ( 6x ) Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 39 6.
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.
12.0 Vibration and Shock All vibration and shock measurements in this section are made with a bare drive. The input for the measurements are applied to the normal drive mounting points unless noted otherwise. 12.1 Operating Vibration 12.1.1 Random Vibration The drive is designed to operate without unrecoverable errors while being subjected to the vibration levels as defined below. The assessments are carried out during 30 minutes of random vibration using the power spectral density (PSD) levels as follows.
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.
13.0 Acoustics 13.1 Sound power levels The upper limit criteria of A-weighted sound power levels are given in Bel, relative to one pico watt, and are shown in the following table. The measurement method is in accordance with ISO-7779. Table 23: A-weighted sound power levels A-weighted sound power level (Bel) Model Mode Typical Maximum Idle 3.7 4.0 Operating 4.3 4.7 Idle 3.7 4.0 Operating 4.3 4.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 44
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.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 46
15.0 Electromagnetic Compatibility The drive, when installed in a suitable enclosure and exercised with a random accessing routine at a maximum data rate will comply with the worldwide EMC requirements listed below. The drive is designed for system integration and installation into a suitable enclosure for use. As such, the drive is supplied as a subassembly and is not subject to Subpart A of Part 15 of the FCC Rules and Regulations.
15.1 Class A Regulatory Notices European Union This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC, as amended by Council Directive 93/68/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. Hitachi cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-Hitachi option cards.
Korea (MIC) Taiwan (BSMI) Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 49
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 50
16.0 Standards The following shows the safety standards for different countries. 16.1 UL and C-UL Standard Conformity The drive is qualified per ULIEC 60950-1: 2001, First Edition for use in Information Technology Equipment, including Electric Business Equipment. The UL recognition, or the C-UL certification, is maintained for the product life. The UL and C-UL recognition mark appears on the drive. 16.2 European Standards Compliance The product is certified to EN60950. 16.
Hitachi Ultrastar 15K450 (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.
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. 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.
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.
• 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 26.
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).
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 29: 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.
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.
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 33 and Table 34. Table 33: Extended Link Service replies Code Reply Abbr.
SCSI requirements. Table 35: Extended Link Service request 11h qualifiers Code Description Abbr.
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 36) contains a Reason Code and a Reason Explanation.
Table 38: 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 Ins
Table 39: 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 Ultrastar 15K450 (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 41: Common Service Parameter applicability (part 2 of 2) Service parameter Word Bits PLOGI and FLOGI PLOGI LS_ACC Parameter Parameter applicability applicability Class FLOGI LS_ACC Parameter applicability 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
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.
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.
• 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.
• 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.
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.
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 312.
17.3.5.1 Common Service Parameters The Common Service Parameters apply to all classes of service and are exchanged during Login.
• 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.
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.
• 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.
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.
Table 51: 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.
Table 53: 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.
• 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.
17.3.9.2 Process Login Response Service Parameter page Table 55: 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.
• 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 56: 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.
Table 58: 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.
17.3.10.2 Process Logout Response Service Parameter page Table 60: 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.
Table 61: RLS payload Byte 0-3 4 5-7 Item Size (Bytes) 0F00 0000h 4 Reserved 1 Port Identifier 3 Table 62: RLS ACC payload Byte 0-3 4 Item Size (Bytes) 0200 0000h 4 Link Error Status Block 24 - 27 Table 63: 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 d
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.
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.
•10 • 1 1 Worst The Preference field is ignored. The Document Identifier field specifies which Profile or Standard is associated with each Capability Entry. Valid Document Identifiers are listed in Table 66. If the Vendor Unique Flag is set to a value other than 00h, then the Document Identifier specifies a vendor unique capability.
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. 17.3.
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.
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 The drive will echo this bit from the TPRLO payload. • Bits 11-8 - Accept Response Code See Table 56. • 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.
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.
Table 77: 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.
Table 78: Topology Discovery Flags Byte BIT 7 6 5 0 4 3 2 1 Reserved 0 TDF Default request values 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.3.
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 81: 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.
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.
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 85: 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 86: FS_RJT Reason Explanations Encoded value Description 00 No additional explanation 01 Port Identifier not registered 02 Port Name not registe
17.5 FC-AL timers Table 87: 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.
• 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 drive will transmit LIP(F8) on that port. 17.
Hitachi Ultrastar 15K450 (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.
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 88).
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 89: 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.
The Task Management Function flags are used to request Task Management functions, as shown in Table 92. The Task Management functions are described in 18.4, “Task Management functions”, on page 110.
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.
18.2.4.1 FCP_STATUS The FCP_STATUS field is normally zero upon successful completion of an IOP. Table 95: 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.
18.2.4.5 FCP_RSP_INFO This field contains information describing only the protocol failures detected during the execution of an IOP. Table 96: 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.
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.
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.
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.
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.
Hitachi Ultrastar 15K450 (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 O M O O O O M M O O O O O O O O O O O O 35h 91h 00h 2Fh AFh AFh 7Fh/0Ah 0Ah 2Ah AAh 8Ah 7Fh/0Bh 2Eh AEh 8Eh 7Fh/0Ch 3Bh 3Fh 41h 93h 7Fh/0Dh SYNCHRONIZE CACHE (10) - (35), page 270 SYNCHRONIZE CACHE (16) - (91), page 271 TEST UNIT READY (00), page 272 VERIFY (2F), page 273 VERIFY (12) - (AF), page 276 VERIFY (16) - (8F), page 277 VERIFY (32) - (7F/0A), page 278 WRITE (6) - (0A), page 280 WRITE (10) - (2A), page 281 WRITE (12) - (AA), page 284 WRITE (16) - (8A), page 285 WRITE (32) - (7F/0B), page 286 WRI
19.1 SCSI Control Byte The Control Byte is the last byte of every CDB. The format of this byte is shown below. Table 100: SCSI Control Byte BIT 7 6 5 VU = 0 4 3 2 Reserved = 0 1 0 FLAG LINK VU VU stands for Vendor Unique. FLAG** If Link is zero, Flag must also be zero. If Link is one, Flag may also be one. Typically this bit is used to cause an interrupt in the Initiator between linked commands.
19.4 FORMAT UNIT (04) Table 101: FORMAT UNIT (04) Byte BIT 7 6 5 0 1 4 3 1 0 Command Code = 04h FMTPINFO RTO_REQ LONG LIST=0 FMTDATA CMPLIST 2 VU = 0 3-4 Obsolete = 0 5 2 VU = 0 Reserved = 0 Defect List Format FLAG LINK • FMTPINFO (Format Protection Information) set to zero specifies that the drive shall disable the use of protection information and format to the block size specified.
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.
19.4.1 Parameter List Header Following is the format of the Paramter List Header sent during the data out phase when FmtData is set to one.
Table 103: Initialization Pattern Descriptor: BIT Byte 7 0 6 5 IP Modifier = 0 SI 4 3 2 1 0 Reserved = 0 1 Initialization Pattern Type = 1 2-3 Initialization Pattern Length (n-3) • IP Modifier must be set to 0, indicating that the drive will not modify the initialization pattern. • SI (Security Initialize) bit set to one specifies that all customer data sectors, including those that have been previously reassigned, will be initialized.
Format of the Dlist sent during the data out phase when Dlist Format is Block format (000b) and FmtData is set to one. Table 104: 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 (LSB) 4n+3 The Block format of the Dlist is the LBA of each defective sector.
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.
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.
19.5 INQUIRY (12) Table 107: INQUIRY (12) Byte BIT 7 6 0 5 4 3 2 1 0 CmdDt =0 EVPD FLAG LINK Operation Code = 12h 1 Reserved = 0 2 Page Code 3-4 Allocation Length 5 VU = 0 Reserved = 0 The INQUIRY command requests the parameters of theTarget to be sent to the Initiator.
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.
• 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.
19.5.1.
19.5.1.
• Page Code is set to the value of the page code field in the CDB. • Page Length field specifies the length (in bytes) of the vendor unique VPD information (bytes 4 - 163). If the allocation length of the CDB is too small to transfer all the data, the Page Length field is not adjusted to reflect the truncation. • ASCII uCode Identifier contains the drive’s microcode identifier. The field is alphanumeric (ASCII), left aligned, and the unused bytes are ASCII spaces (20h).
19.5.1.4 Inquiry Data Format - EVPD = 1, Page Code - 80h Table 112: Inquiry Data - EVPD = 1 (Page Code = 80h) BIT Byte 7 0 6 5 Qualifier = 0 4 3 2 1 0 Peripheral Device Type = 0 1 Page Code = 80h 2 Reserved = 0 3 Page Length = 16 (10h) 4-19 Serial Number (ASCII) • Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported. • Peripheral Device Type is set to zero to indicate that the device is Direct Access.
19.5.1.
Logical Block Reference Tag field. • GRD_CHK (Guard Check) is set to one to indicate that the drive checks the Logical Block Guard Tag field in the protection information, if any. • APP_CHK (Application Tag Check) bit is set to one to indicate that the drive checks the Logical Block Application Tag field in the protection information, if any. • REF_CHK (Reference Tag Check) bit is set to one to indicate that the drive checks the Logical Block Reference Tag field in the protection information, if any.
8-9 Reserved = 0 10-11 Initiator Port Transport ID Length = 0 12-13 Reserved = 0 14-15 Primary Target Port Descriptors Length = 0Ch 16 17 Protocol Identifier PIV=1 RSVD Code Set = 1 Association = 1 Identifier Type = 3 18 Reserved = 0 19 Identifier Length = 8 (MSB) 20-27 Primary Target Port Identifier (World Wide ID) (LSB) 28-29 Reserved = 0 30-31 Secondary Relative Port = 0002h 32-33 Reserved = 0 34-35 Initiator Port Transport ID Length = 0 36-37 Reserved = 0 38-39 Secondary T
19.5.1.
19.5.1.
19.6 LOG SELECT (4C) Table 116: Log Select (4C) Bit Byte 7 6 0 5 4 3 2 1 0 PCR SP Command Code = 4Ch 1 Reserved = 0 2 PC Reserved = 0 Reserved = 0 3 4 5 Reserved = 0 6 7 (MSB) Parameter List Length = 0 8 9 (LSB) Reserved = 0 FLAG LINK The LOG SELECT command provides a means for the Initiator to clear statistical information maintained by the drive and reported via the LOG SENSE command.
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.
• Page 30h parameters: - Zero Seeks counter - Seeks > = to 2/3 counter - Seeks > = 1/3 and < 2/3 counter - Seeks > = 1/6 and < 1/3 counter - Seeks > = 1/12 and < 1/6 counter - Seeks > 0 and < 1/12 counter - Overrun Counter - Under run Counter - Device Cache Full Read Hits - Device Cache Partial Read Hits - Device Cache Write Hits - Device Cache Fast Writes - Device Cache Misses on Reads • Page 37h parameters: - Media PFA - Hardware PFA - Total Read Commands - Total Write Commands Hitachi Ultrastar 15K450 (
19.7 LOG SENSE (4D) Table 117: Log Sense (4D) Bit Byte 7 6 0 4 3 2 1 0 PPC=0 SP Command Code = 4Dh 1 Reserved = 0 2 PC 3 Reserved = 0 Page Code Reserved = 0 4 5 5 (MSB) Parameter Pointer = 0 6 7 (LSB) (MSB) Allocation Length 8 9 (LSB) Reserved = 0 FLAG LINK The LOG SENSE command allows the Initiator to retrieve the statistical data regarding the drive. • PPC (Parameter Pointer Control) bit must be set to zero.
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.
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.
19.7.3 Log Sense Page 2 This page contains counters for write errors.
66 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 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 79 Parameter Length = 08h 80-87 Count of hard errors F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of all recovery steps attempted on all sectors written.
19.7.4 Log Sense Page 3 This page contains counters for read errors.
66 DU = 0 DS = 0 TSD = 0 ETC = 0 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 TMC = 0 79 Parameter Length = 08h 80-87 Count of hard errors F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of all recovery steps attempted on all sectors read.
19.7.5 Log Sense Page 5 This page contains counters for verify errors.
Table 124: 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 F&L = 00b F&L = 00b All parameter counts indicate the number of sectors with the specified types of errors, except Times Recovery Invoked, which is a cumulative count of all recovery steps attempted on all
19.7.6 Log Sense Page 6 This page contains counters for non-medium errors. This includes seek errors and other hardware type failures.
19.7.7 Log Sense Page D This page contains temperature information.
19.7.8 Log Sense Page E This page contains the start-stop cycle information.
19.7.9 Log Sense Page F This page contains the Application Client Log. Table 128: Log Sense Page F Bit Byte 7 0 6 5 4 3 Reserved 2 1 0 1 0 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.
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 132: Log Sense Page 10, self-test results Value Description 0h The self-test routine completed without error. 1h The background self-test routine was aborted by the initiator using a SEND DIAGNOSTIC command with the Abort Background self-test function. 2h The self-test routine was aborted by the application client by a Task Management function or a reset.
Table 133: 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.
19.7.11 Log Sense Page 15 This page contains information about Background Medium Scan operations. Table 134: Log Sense Page 15 Bit Byte 7 0 6 5 4 3 Reserved 2 1 0 1 0 Page code = 15h 1 Reserved 2-3 Page Length = (19 + 24N -3) Background Medium Scan parameters 4-19 BMS Status Parameter 20-43 First Medium Scan Parameter ... 19+24N Last Medium Scan Parameter The following table describes the BMS Status Parameter structure.
BMS Status Description 03h-04h Not supported 05h Background scan halted due to medium formatted without P-List 06h Background scan halted due to a vendor-specific cause 07h Background scan halted due to temperature out of range 08h Scan suspended until BMS Interval Timer expires 09h - FFh Reserved • Number of Scans Performed indicates the number of background scans that have been performed over the life of thedrive. • Medium Scan Progress is a percent complete indication of the medium scan.
Reassign Status Description 1h Reassignment pending receipt of Reassign command or write command (if auto write reallocation is allowed) from the initiator 02h-5h Not supported 6h - Fh Reserved Additional Sense Code and Additional Sense Code Qualifier provide details about the error detected.
19.7.12 Log Sense Page 2F This page contains SMART Status and Temperature Reading.
19.7.13 Log Sense Page 30 This page contains Performance Counters.
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.
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.
19.7.14 Log Sense Page 37 This page contains a series of miscellaneous data counters including information about predictive failure analysis occurrences.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 164
19.8 MODE SELECT (15) Table 138: 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.
19.9 MODE SELECT (55) Table 139: 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.
19.10 MODE SENSE (1A) Table 140: Mode Sense (1A) Bit Byte 7 6 5 0 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.
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.
Table 143: 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.
19.10.1.2 Block Descriptor Table 144: Mode Parameter Block Descriptor Byte 0 (MSB) Number of Blocks Byte 1 Byte 2 Byte 3 (LSB) Byte 4 Byte 5 Density code = 0 (MSB) Byte 6 Block Length Byte 7 (LSB) The Block descriptor provides formatting information about the Number of Blocks (user addressable) to format at the specified Block Length.
19.10.1.3 Page Descriptor Table 145: 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.
19.10.
• IGRA (Ignore Reassigned LBA) bit works in conjunction with the RC bit (Mode Page 01h, byte 2, bit 4). The main purpose of this bit is to avoid undesirable read processing time delays due to reassigned LBA processing for continuous data availability requirements such as Audio Visual applications. If IGRA is set to one and RC is set to one, out-ofline reassigned LBAs will not be processed. If IGRA is set to one and RC is set to zero, or if IGRA is set to zero, reassigned LBAs will be processed normally.
19.10.
• PER a Post Error bit, is set to one to indicate that the drive reports recovered errors. • DTE (Data Terminate on Error) bit set to one specifies that data transfer will be halted when the first recovered error is encountered. PER must be set to one when DTE is set to one. DTE set to zero will cause data transfer to continue when recovered errors are encountered. • DCR a Disable Correction bit, is set to one to indicate that Error Correction Code is not used for data error recovery.
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.
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.
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.
19.10.
19.10.
The format device page contains parameters that specify the medium format. This page contains no changeable parameters. • Tracks per Zone specifies the number of tracks within the zone. This field is a function of the active notch. • Sectors per Track specifies the number of physical sectors within each track. This field is a function of the active notch. • Data Bytes per Physical Sector specifies the number of user data bytes per physical sector. The value depends upon the current formatted Block Length.
19.10.
19.10.
19.10.
Note: When WCE = 1, a SYNCHRONIZE CACHE command must be done to ensure data are written to the media before powering down the Target. • MF (Multiplication Factor) bit determines how the Maximum and Minimum Pre-fetch parameters are interpreted. If this bit is set to zero, the parameters are used as is. If the bit is set to one, the parameters are multiplied by the number of blocks requested in the Read Command.
19.10.
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.
19.10.
- 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.
19.10.
• 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.
19.10.13 Mode Page 1A (Power Control) Table 159: Page 1A (Power Control) Bit Byte 0 7 6 PS 0 5 4 3 2 1 0 Page Code = 1Ah Default 9Ah 1 Page Length = 0Ah 0Ah 2 Reserved = 00h 00h 3 Reserved = 0 Idle Standby (MSB) 00h 00h Idle Condition Timer 4-7 (LSB) 00h (MSB) 8-11 Standby Condition Timer (LSB) • Idle bit of one indicates that the Target shall use the Idle Condition Timer to determine the length of inactivity time to wait before entering the Idle power state.
19.10.14 Mode Page 1C (Informational Exceptions Control) Table 160: Page 1C (Informational Exceptions Control) BIT Byte 0 7 6 PS 0 5 3 2 1 0 Page Code = 1Ch 1 2 4 9Ch Page Length = 0Ah PERF 3 RSVD EBF EWASC DEXCPT Reserved = 0 Default 0Ah TEST EBACKLOGERR ERR Method of Reporting 10h 00h 00h (MSB) 4-7 00h Interval Timer (LSB) 00h 00h 00h (MSB) 8-11 Report Count (LSB) •PERF (Performance) bit is not supported and is ignored.
• 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.
19.10.14.
19.11 MODE SENSE (5A) Table 162: Mode Sense (5A) Bit Byte 7 6 5 0 4 3 Reserved = 0 2 PCF DBD 0 Subpage Code 4-6 Reserved = 0 (MSB) Reserved = 0 Page Code 3 9 1 Command Code = 5Ah 1 7-8 2 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.
19.12 PERSISTENT RESERVE IN (5E) Table 163: Persistent Reserve In (5E) Bit Byte 7 6 5 0 Reserved = 0 2-6 9 3 2 1 0 Command Code = 5Eh 1 7-8 4 Service Action Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK The PERSISTENT RESERVE IN command is used to obtain information about persistent reservations and reservation keys that are active within the controller.
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.
19.12.2 Parameter data for Read Keys Table 165: 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.
19.12.3 Parameter Data for Read Reservations Table 166: 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).
19.13 PERSISTENT RESERVE OUT (5F) Table 168: PERSISTENT RESERVE OUT (5F) Bit Byte 7 6 5 0 1 4 3 2 0 FLAG LINK Command Code = 5Fh Reserved = 0 2 Service Action Scope=0 Type 3-6 Reserved = 0 7-8 Parameter List Length = 18h 11 1 VU = 0 Reserved = 0 The PERSISTENT RESERVE OUT command is used to request service actions that reserve the drive for the exclusive or shared use of the initiator. The command uses other service actions to manage and remove such reservations.
19.13.1 Service Action The following service action codes are supported.
19.13.2 Type The Type field specifies the characteristics of the persistent reservation being established for all customer data sectors. Thetable below describes the supported types and how read and write commands are handled for each reservation type. Table 170: PERSISTENT RESERVE OUT, Type Code Code 0h Name Description Reserved Reserved 1h Write Exclusive Reads Shared: Any initiator may execute commands that transfer from the media.
19.13.3 Parameter list The Parameter List required to perform the PERSISTENT RERSERVE OUT command is defined in the table below. All fields must be sent on all PERSISTENT RESERVE OUT commands, even if the field is not required for the specified service action.
19.13.
19.13.4.1 Scope, Type The Scope and the Type are applied in the process for the Reserve, Release, and Preempted and Clear service action but they are ignored in the process for the Register service action because they are not used. 19.13.4.2 Reservation Key The Reservation Key is verified in each service action process. If the Initiator that registered a key is different from the Initiator requesting PERSISTENT RESERVE OUT command, the drive returns a Reservation Conflict status. 19.13.4.
19.14 PRE-FETCH (34) Table 174: PRE-FETCH (34) Bit Byte 7 6 5 0 4 3 2 1 0 Immed =0 Obsolete 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.
19.15 READ (6) - (08) Table 175: 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.
19.16 READ (10) - (28) Table 176: READ (10) - (28) Bit Byte 7 6 5 0 4 3 2 1 0 Rsvd= 0 FUA_ NV Obsolete Command Code = 28h 1 RDPROTECT DPO FUA (MSB) 2-5 Logical Block Address (LSB) 6 7-8 Reserved = 0 (MSB) Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The READ (10) command requests the drive to transfer data to the Initiator.
- Protection information is transmitted to the initiator with the user data - Logical Block Guard is checked - Logcial Block Application Tag is checked (applies to READ(32) command only) - Logical Block Reference Tag is checked RDPROTECT=010b - Protection information is transmitted to the initiator with the user data - Logical Block Guard is not checked - Logcial Block Application Tag is checked (applies to READ(32) command only) - Logical Block Reference Tag is checked RDPROTECT=011b - Protection informati
19.17 READ (12) - (A8) Table 177: Read (12) - (A8) Bit Byte 7 6 5 0 4 3 2 1 0 Rsvd = 0 FUA_N V Rsvd = 0 Command Code = A8h 1 RDPROTECT DPO FUA (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The READ(12) command causes the drive to transfer data to the initiator. See the READ(10) description for the definitions of the fields in this command.
19.18 READ (16) - (88) Table 178: READ (16) - (88) Bit Byte 7 6 0 5 4 3 2 1 0 Rsvd=0 FUA_NV Rsvd=0 Command Code = 88h 1 RDPROTECT DPO FUA (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The READ(16) command causes the drive to transfer data to the initiator. See the READ(10) description for the definitions of the fields in this command.
19.
See READ (10) - (28) for descriptions of the RDPROTECT, DPO, FUA, Logical Block Address, and Transfer Length fields. When checking of the Logical Block Reference Tag field is enabled, the Expected Initial Logical Block Reference Tag field contains the value of the Logical Block Reference Tag field expected in the protection information of the first logical block accessed by the command, instead of a value based on the LBA.
19.20 READ BUFFER (3C) Table 180: 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.
19.20.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.
19.20.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.
19.20.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.
19.20.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.
19.20.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.
19.20.6 Enable Expander Communications Protocol and Echo Buffer (Mode11010b) 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 (Read Data from Echo Buffer (Mode 01010b)*, page 219.
19.21 READ CAPACITY (10) - (25) Table 184: READ CAPACITY (10) - (25) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 25h 1 Reserved = 0 Obsolete 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.
19.21.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 185: 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 each block of user data (not including protection information).
19.22 READ CAPACITY (16) (9E/10) Table 186: Read Capcity (16) (9E/10) Bit Byte 6 7 5 0 4 3 2 1 0 Command Code = 9Eh 1 Reserved = 0 Service Action = 10h (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Allocation Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 PMI FLAG Link The READ CAPACITY (16) (9E/10) command returns information regarding the capacity of the drive. This command is processed like the standard READ CAPACITY (25) command.
19.22.1 Returned Data Format The following data is returned to the initiator in the DATA OUT phase. Table 187: Returned Data Format Bit Byte 6 7 5 4 3 2 1 0 (MSB) 0-7 Maximum Logical Address (LSB) (MSB) 8 - 11 Block Length (LSB) 12 13 - 31 Reserved = 0 RTO_E N PROT_ EN Reserved = 0 • RTO_EN (Reference Tag Own Enable) bit set to one indicates that application client ownership of the Logical Block Reference Tag field in protection information is enabled (i.e.
19.23 READ DEFECT DATA (37) Table 188: 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.
Table 189: 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.
19.23.
19.23.2 Defect List Descriptor Table 191: Defect List Descriptor Bit Byte 7 6 5 4 3 2 1 Defect List Descriptor 0-7 Defect Descriptor 0 .
19.23.
19.23.4 Physical Sector Format (101b) Table 193: 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.
19.24 READ DEFECT DATA (B7) Table 194: READ DEFECT DATA (B7) Bit Byte 7 6 5 0 Reserved = 0 2-5 2 1 0 Plist Glist Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) 10 11 3 Command Code = B7h 1 6-9 4 Reserved = 0 VU = 0 Reserved = 0 FLAG (See Section 19.23 “READ DEFECT DATA (37)” on page 226.
19.24.1 Defect List Header Table 195: Defect List Header Bit Byte 7 6 5 4 3 2 1 0 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.23.1, “Defect List Header,” on page 228.
19.24.2 Defect List Descriptor Table 196: 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.23.2 “Defect List Descriptor” on page 229.
19.24.3 Bytes from Index Format (100b) Table 197: 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.24.
19.25 READ LONG (3E) Table 199: READ LONG (3E) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 3Eh 1 Reserved = 0 Reserved = 0 Correct =0 Obsolete (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.
19.26 REASSIGN BLOCKS (07) Table 200: 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.
Following is the format of the data sent by the Initiator during the DATA OUT phase. Table 201: 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.
19.27 RECEIVE DIAGNOSTICS RESULTS (1C) Table 202: 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.
19.27.1 Receive Diagnostic Results Page 0 This page contains a list of supported pages. Table 203: Receive Diagnostic Results page 0 Bit Byte 7 6 5 4 3 2 0 Page Code = 0 1 Reserved = 0 2-3 Page Length = 12h 5-19 ESI Pages = 01h - 0Fh 20 Translate address page = 40h 21 Device LED Control Page = A0h 1 The supported diagnostic page returns a list of supported pages in ascending order.
19.27.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.
19.27.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.
6-8 Cylinder Number 9 Head Number 10-13 Sector Number or Bytes from Index Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 244
19.27.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.
19.28 RELEASE (17) Table 209: 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.
19.29 RELEASE (57) Table 210: RELEASE (57) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 57h Reserved = 0 2 3rdPty=0 Reserved = 0 Ext = 0 Reservation Identification 3 3rd Party Device ID 4-8 Reserved = 0 9 1 VU = 0 Reserved = 0 FLAG LINK The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to release a LUN that is not currently active. The drive returns Good status without altering the reservation. • 3rdPty must be 0.
19.30 REPORT DEVICE IDENTIFIER (A3/05) Table 211: REPORT DEVICE IDENTIFIER (A3/05) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A3h 1 Reserved = 0 Service Action = 05h 2 Reserved = 0 3 Reserved = 0 (MSB) 4-5 LUN=0 (LSB) (MSB) 6-9 Allocation Length (LSB) 10 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.
Table 212: 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.
19.31 REPORT LUNS (A0) Table 213: 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.
19.32 REPORT SUPPORTED OPERATION CODES (A3/0C) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A3h 1 Reserved = 0 2 Service Action = 0Ch Reserved = 0 Reporting Options 3 Requested Operation Code 4-5 Requested Service Action 6-9 Allocation Length 10 Reserved = 0 11 VU = 0 Reserved = 0 FLAG LINK The REPORT SUPPORTED OPERATION CODES command requests information on commands that the drive supports.
Allocation Length specifies the number of bytes that have been allocated for the returned parameter data. If the length is not sufficient to contain all the parameter data, the first portion of the data shall be returned. The actual length of the parameter data may be determined from the Additional Length field in the parameter data.
19.32.1 All_commands parameter data format The Report Supported Operation Codes all_command parameter data format begins with a four-byte header that contains the length in bytes of the parameter data, followed by a list of supported commands. Each command descriptor contains information about a single supported command CDB (i.e. one operation code and service action combination, or one non-serviceaction operation code).
19.32.2 One_command parameter data format The Report Supported Operation Codes one_command parameter data format contains information about the CDB and a usage map for bits in the CDB for the command specified by the Reporting Options, Requested Operation Code, and Requested Service Action fields in the Reported Supported Operation Codes CDB. Bit Byte 7 6 5 0 4 3 2 1 0 Reserved = 0 1 Reserved = 0 Support 2-3 CDB Size (n-3) 4-n CDB Usage Data The Support field is defined in the table below.
19.33 REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS (A3/0D) Table 215: Report Supported Tasks Management Functions (A3/0D) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A3h 1 Reserved = 0 Service Action = 0Dh 2-5 Reserved = 0 6-9 Allocation Length 10 Reserved = 0 11 VU = 0 Reserved = 0 Flag Link The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command requests information on task management functions supported by the drive.
WAKES (Wakeup) bit set to one indicates that WAKEUP is supported. A WAKES bit of zero indicates that WAKEUP is not supported.
19.34 REQUEST SENSE (03) Table 216: 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.
19.35 RESERVE (16) Table 217: 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.
19.36 RESERVE (56) Table 218: 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 = 56h 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.
19.37 REZERO UNIT (01) Table 219: 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.
19.38 SEEK (6) - (0B) Table 220: 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.
19.40 SEND DIAGNOSTIC (1D) Table 222: 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.
Table 223: 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.
19.40.1 Send Diagnostic Page 0 This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS command.
19.40.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.
• 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.
19.40.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 227: 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.
19.41 SET DEVICE IDENTIFIER (A4/06) Table 228: SET DEVICE IDENTIFIER (A4/06) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = A4h 1 Reserved = 0 Service Action = 06h 2 Reserved = 0 3 Reserved = 0 4-5 Restricted = 0 (MSB) 6-9 Parameter List Length (LSB) 10 Reserved = 0 11 VU = 0 Reserved = 0 FLAG LINK The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the SET DEVICE IDENTIFIER parameter list.
19.42 START STOP UNIT (1B) Table 230: 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.
19.43 SYNCHRONIZE CACHE (10) - (35) Table 231: SYNCHRONIZE CACHE (10) - (35) BIT Byte 7 6 5 0 4 3 2 1 0 Immed =0 Obsolete Command Code = 35h 1 Reserved = 0 Reserved = 0 (MSB) 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.
19.44 SYNCHRONIZE CACHE (16) - (91) Table 232: Synchronize Cache (16) - (91) BIT Byte 7 6 0 5 4 3 1 0 Immed =0 Rsvd= 0 FLAG LINK Command Code = 91h 1 Reserved = 0 2-9 Logical Block Address 10-13 Number of Blocks 14 Reserved = 0 15 2 VU = 0 Reserved = 0 The SYNCHRONIZE CACHE command ensures that logical blocks in the cache have their most recent data value recorded on the media. See the SYNCHRONIZE CACHE (10) description for definitions of the fields in this command.
19.45 TEST UNIT READY (00) Table 233: 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.
19.46 VERIFY (2F) Table 234: VERIFY (2F) BIT Byte 7 6 5 0 4 3 2 1 0 Byte Chk RSVD =0 Command Code = 2Fh 1 VRPROTECT 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.
If the drive is not formatted with protection information, VRPROTECT must be set to 000b, else Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. VRPROTECT=000b If the drive is not formatted with protection information, only user data is verified.
If ByteChk=1, and VRPROTECT is not set to 000b, checking of protection information is performed on the fields described above as a byte-by-byte comparison against the data transferred to the drive by the initiator during the Data Out phase.. Refer to the ANSI T10 standards for additional details of protection information.
19.47 VERIFY (12) - (AF) Table 235: Verify (12) - (AF) BIT Byte 7 6 5 0 4 3 2 1 0 Reserv ed=0 Byte Chk Reserv ed = 0 Command Code = AFh 1 VRPROTECT DPO FUA (MSB) Logical Block Address 2-5 (LSB) (MSB) 6-9 Verification Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The VERIFY(12) command causes the drive to verify data written on the media. See the VERIFY(10) description for the definitions of the fields in this command.
19.48 VERIFY (16) - (8F) Table 236: Verify (16) - (8F) Bit Byte 7 6 5 0 4 3 2 1 0 Byte Chk Rsvd =0 Command Code = 08Fh 1 VRPROTECT 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. See the VERIFY (10) description for the definitions of the fields in this command.
19.
See VERIFY (2F) for descriptions of the VPROTECT, DPO, ByteChk, Logical Block Address, and Verification Length fields. When checking of the Logical Block Reference Tag field is enabled, the Expected Initial Logical Block Reference Tag field contains the value of the Logical Block Reference Tag field expected in the protection information of the first logical block accessed by the command, instead of a value based on the LBA.
19.50 WRITE (6) - (0A) Table 238: 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 208 for the parameters.
19.51 WRITE (10) - (2A) Table 239: WRITE (10) - (2A) Bit Byte 7 6 5 0 4 3 2 1 0 Rsvd=0 FUA_N V Obsolete Command Code = 2Ah 1 WRPROTECT DPO FUA (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.
If the drive is not formatted with protection information, WRPROTECT must be set to 000b, else Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Field in CDB. WRPROTECT=000b Protection information is not transmitted to the drive. If the drive is formatted with protection information, the drive will write protection information to disk based on its internal algorithms.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 283
19.
19.53 WRITE (16) - (8A) Bit Byte 7 6 0 5 4 3 2 1 0 Rsvd=0 FUA_NV Rsvd=0 Command Code = 8Ah 1 WRPROTECT DPO FUA (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Tranfer Length (LSB) 14 15 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The WRITE(16) command causes the drive to write data from the initiator to the media. See the WRITE(10) description for the definitions of the fields in this command.
19.
includes user data and may include protection information, based on the WRPROTECT field and the drive format. Each logical block written includes user data and, if the drive is formatted with protection information enabled, protection information. If the RTO_EN bit is set to zero in the READ CAPACITY (16) parameter data, Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code.
19.55 WRITE AND VERIFY (10) - (2E) Table 242: WRITE AND VERIFY (10) - (2E) Bit Byte 7 6 5 0 4 3 2 1 0 Byte Chk Obsolete Command Code = 2Eh 1 WRPROTECT 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.
19.56 WRITE AND VERIFY (12) - (AE) Table 243: Write andVerify (12) - (AE) Bit Byte 7 6 5 0 4 3 2 1 0 ByteChk Obsolete Command Code = AEh 1 WRPROTECT DPO Reserved = 0 (MSB) 2-5 Logical Block Address (LSB) (MSB) 6-9 Transfer Length (LSB) 10 11 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK The WRITE AND VERIFY command requests that the drive write the data transferred from the Initiator to the medium and then verify that the data is correctly written.
19.57 WRITE AND VERIFY (16) - (8E) Table 244: Write and Verify (16) - (8E) Bit Byte 7 6 5 0 4 3 2 1 0 Byte Chk Obsolete Command Code = 8Eh 1 WRPROTECT 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.
19.
See WRITE AND VERIFY (10) - (2E) for descriptions of the WRPROTECT, DPO, ByteChk, Logical Block Address, and Transfer Length fields. When checking of the Logical Block Reference Tag field is enabled, the Expected Initial Logical Block Reference Tag field contains the value of the Logical Block Reference Tag field expected in the protection information of the first logical block accessed by the command, instead of a value based on the LBA.
19.59 WRITE BUFFER (3B) Table 246: 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.
19.59.1 Combined Header And Data (Mode 00000b) In this mode, the data to be transferred is preceded by a four-byte header. Buffer ID must be zero. If another value is specified, no download function is performed and the command is terminated with Check Condition status. And the drive shall set the sense key to Illegal Request and additional sense code to Illegal Field in CDB. Buffer Offset must be zero.
19.59.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.
19.59.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.
19.59.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.
19.59.5 Download Microcode and Save (Mode 00111b) - Multiple Binary Files In this mode the target receives a segment of the binary microcode file. The Parameter List Length (segment length) of each segment shall be a multiple of 4K bytes. The total length of all segments received shall be equal to the total length of the binary microcode file. All segments must be sent in the proper sequential order.
19.59.6 Write Data to Echo Buffer (Mode 01010b) In this mode the Target transfers data into the echo buffer. The echo buffer is assigned in the same manner by the Target as it would for a WRITE operation. Data will be sent aligned on 4-byte boundaries. Upon successful completion of a WRITE BUFFER command the data will be preserved in the echo buffer unless there is an intervening command to any logical unit, in which case it may be changed.
19.59.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.60 WRITE LONG (3F) Table 248: WRITE LONG (3F) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 3Fh 1 Reserved = 0 Obsolete Reserved = 0 (MSB) 2-5 Logical Block Address (LSB) 6 Reserved = 0 (MSB) 7-8 Byte Transfer Length (LSB) 9 VU = 0 Reserved = 0 FLAG LINK The WRITE LONG command requests the drive to write one block of data transferred from the Initiator.
19.61 WRITE SAME (41) Table 249: WRITE SAME (41) Bit Byte 7 6 5 0 4 3 2 1 0 PBDA TA=0 LBDA TA=0 Obsolete Command Code = 41h 1 WRPROTECT 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.
19.62 WRITE SAME (16) - (93) Table 250: Write Same (16) - (93) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 93h 1 WRPROTECT Reserved = 0 PBDATA LBDATA Obsolete =0 =0 (MSB) 2-9 Logical Block Address (LSB) (MSB) 10-13 Number of Blocks (LSB) 14 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.
19.
If the RTO_EN bit is set to zero in the READ CAPACITY (16) parameter data, Check Condition status will be returned with sense key of Illegal Request and additional sense code of Invalid Command Operation Code. If RTO_EN is one, this command will be processed normally. See WRITE SAME (41) for descriptions of the WRPROTECT, Logical Block Address, and Number of Blocks fields.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 306
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 252: SCSI Status Byte. Format of the SCSI STATUS byte.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 308
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.
Table 253: 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.
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 312.) After transmitting the LIFA frame, The Port waits to receive a LIPA frame. b.
The response to certain frames at various stages of login is defined in Table 254.
21.5.
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.
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.
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 315).
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.
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.
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.
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.
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 255: Spindle Motor Degraded Mode - Disable Auto Start Command (w/Option) Response Request Sense Executed.
21.6.9.2 Response to SCSI Command in Degraded Mode - Auto Start Delay/ Spinning Up Table 256: Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up Command (w/Option) Response Request Sense Executed.
21.6.9.3 Response to SCSI Command in Degraded Mode - Spindle Start Failure Table 257: Spindle Motor Degraded Mode - Spindle Start Failure Command (w/Option) Response Request Sense Executed.
21.6.9.4 Response to SCSI Command in Degraded Mode - Spindle Stopped by Unit Stop Command Table 258: Spindle Motor Degraded Mode - Spindle Stopped by Unit Stop Command Command (w/Option) Response Request Sense Executed.
21.6.9.5 Self Configuration Failure Degraded Mode Table 259: Self Configuration Failure Degraded Mode Command (w/Option) Response Request Sense Executed.
21.6.9.6 Format Command Failure Degraded Mode Table 260: Format Command Failure Degraded Mode Command (w/Option) Response Request Sense Executed.
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.
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.
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.
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.
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.
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.
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.
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.
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.
ground mode as previously described. Table 262: 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.
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. 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.
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.
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.
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.
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.
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.
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 339. 4.
- 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.
- 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 339.
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.
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.
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 339. Note: Service for this drive can be deferred.
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 265: Format of Sense Data.
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.
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.
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.
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. Valid Sense Key, Code, Qualifier Combinations Used by the Drive. Key Code Qual Description Sense Key = No Sense 0 00 00 No Additional Sense Information (00 00) No Error.
17FE Servo Recovered read/write abort no STM error 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 0B 03 Background Selftest Failure Warning xA03 Background selftest failure warning 1 0B 04 Background Pre-Scan Failure Warning xA04 Background pre-scan failure warning 0 0B 05 Background Media Scan Failure Warning xA05 Background media scan failure warning 1 0C
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 therm
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 1311 Motor: Recovered Internal 12V not OK timeout 1313 Motor: Recovered Iductive Sense measurement timeout 1315 Motor: Recovered Spin Se
142D Servo: Recovered ADC Calibration error 142F Servo: Recovered ADC Offset error 1431 Servo: Recovered ADC Limit error 1433 Servo: Recovered Balancer Resistance error 1435 Servo: Recovered Balancer Resistance Limit error 1437 Servo: Recovered First Cylinder error 1439 Servo: Recovered Valid Cylinder error 143B Servo: Recovered ADC Saturation error 143D Servo: Recovered Latch Break timeout 143F Servo: Recovered MR Resistance out of range error 1441 Servo: Recovered VCM Retract error 1443 Servo: Recovered L
1638 Recovered AE Non-selected write head error 163C Recovered AE IH open short error 163E Recovered AE IH delay error 1640 Recovered Channel coarse tune timeout error 1642 Recovered AE Readback error 1712 Recovered ECC error 1716 Recovered overrun 171A Recovered ECC overrun 171C Recovered DRAM CRC error 171E Recovered ID Parity error 1731 Recovered write fault 1759 Unknown recovered error 1792 Recovered Current pointer error 1798 Recovered ID not found error 179C Recovered Channel write or NRZ parity error
xA32 SMART: Read error rate warning xA4A SMART: Write error rate warning 1 5D 63 Predictive Failure Analysis Threshold Reached xA43 SMART: Seek error rate warning 1 5D 64 Predictive Failure Analysis Threshold Reached xA14 SMART: Spare sector availability warning 1 5D 66 Predictive Failure Analysis Threshold Reached xA56 SMART: Spin-up time warning 1 5D FF Predictive Failure Analysis Threshold Reached xAFF SMART: Test warning 1 81 00 Vendor Unique - Internal Logic Error 1601 Channel/AE int
3 03 00 Medium Error - Write Fault F734 Unrecovered read/write abort F738 Unrecovered post write abort F73A Unrecovered Post PES check write abort F7E1 Servo Unrecovered read/write abort estimator error F7E3 Servo Unrecovered read/write abort predictor error F7E5 Servo Unrecovered read/write abort PES error F7E7 Servo Unrecovered read/write abort seek start error F7E9 Servo Unrecovered read/write abort PES reset error F7EB Servo Unrecovered read/write abort SID unlock error F7ED Servo Unrecovered read/wr
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 3 19 03 Defect List Error in Grown List F74C Grown defect list error 3 31 00 Medium Format Corrupted Reassign Failed F701 Format corrupted 3 81 00 Vendor Unique - Internal Logic Error F719 Recovered Abort immediate error F75B Too many sectors Sense Key = Hardware Error 4 02 00 No Seek Complete F41C Servo: Unrecovered No seek complete
155E ESI: transfer failed - EDV 4 35 04 Enclosure Services Failure - Enclosure Services Refused 153D ESI: transfer refused 155A ESI: transfer refused - write ack 155B ESI: transfer refused - read ack 155C ESI: transfer refused - write ready 155D ESI: transfer refused - read ready 4 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 BAT
F125 BATS error: Invalid RID/FID 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 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 0
F328 Motor: Unrecovered unkown error F402 Servo: Unrecovered Requested re zero head does not exist F404 Servo: Unrecovered Back EMF movement in progress F406 Servo: Unrecovered Back EMF timeout error F408 Servo: Unrecovered ADC conversion timeout F40A Servo: Unrecovered Load/unload calibration error F40C Servo: Unrecovered Invalid 5 volts F40E Servo: Unrecovered Invalid 12 volts F410 Servo: Unrecovered Invalid harmonic requested F412 Servo: Unrecovered Gain BEMF Calibration error F414 Servo: Unrecovered VOF
F60D Unrecovered data pre-PPM or FH detection F60F Unrecovered data write or pre-TA detection F611 Unrecovered data with pre-SMM or VM or STM or DDF F613 Unrecovered data with NRZ parity error F615 Unrecovered parity PP correction or STW F617 Unrecovered channel error F619 Unrecovered AE thermal asperity found F61B Unrecovered AE open MR element error F61D Unrecovered AE IC over temperature error F61F Unrecovered AE IP clock count error F621 Unrecovered AE high MR current error F623 Unrecovered AE write dat
F7B5 Unrecovered Shock sensor error F7B9 Unrecovered Reference tag error F7BB Unrecovered Application tag error F7BD Unrecovered Channel write synthesis unlock error F7C1 Unrecovered End sector check error F7C3 Unrecovered Read CRC error F7C5 Unrecovered DRAM ECC error F7C7 Unrecovered DRAM ECC LBA error F7C9 Unrecovered DRAM ECC Write error FCxx Unable to read RID or FID number xx 4 44 0B Vendor Unique - Internal Target Failure F310 Motor: Unrecovered Spindle Current error F318 Motor: Unrecovered Spin S
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 02 Parameter Value Invalid F120 BATS error: Code compatibility failure F126 BATS error: Code checksum error F127 BATS error: Invalid header F130 Incorrect Customer code 5 26 04 Invalid Release of Active Persistent Reservation 1540 Invalid release of persistent reservation 5 35 01 Unsupported Enclosure Function 1511 Unsupported enclosu
151B Tranceiver changed to LVD (SCSI only) 6 29 07 I_T Nexus Loss Occurred 1554 I_T Nexus Loss Occurred (SAS only) 6 2A 01 Mode Parameters Changed 151C Mode parameters changed 6 2A 02 Log Parameters Changed 151D Log parameters changed 6 2A 03 Reservations Preempted 151E Reservations pre-empted 6 2A 04 Reservations Released 151F Reservations released 6 2A 05 Registrations Released 1520 Registrations pre-empted 6 2F 00 Commands Cleared by Another Initiator 1521 Commands cleared by a
B 43 00 Message Error 152A Message reject error (SCSI only) 152C Message parity error rcvd when no message sent by target (SCSI only) B 44 00 Internal Target Failure 152D Buffer CRC error on read 152E Internal target failure - Host Interface 154A Xfer Ready credit exceeded (FC-AL only) 154B Xfer length error (FC-AL only) 1568 End-to-End Data Protection Guard check 1569 End-to-End Data Protection Application Tag check 156A End-to-End Data Reference Tag check 156B ECC error in DRAM customer data area 1
152B Attention dropped too late (SCSI only) 1533 Inappropriate or illegal message (SCSI only) B 4B 00 Data Phase Error 153E Data phase error B 4B 01 Invaled Target Port Transfer Tag Received 1561 Information unit too short (SAS only) B 4B 02 Too Much Write Data 1560 Too much write data (SAS only) B 4B 03 ACK/NAK Timeout 1551 ACK/NAK Timeout (SAS only) B 4B 04 NAK Received 1550 NAK Received (SAS only) B 4B 05 Data Offset Error 1552 Bad parameter offset (SAS only) B 4B 06 Initiator
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 371
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.
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 267: 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.
Progress indication is returned. Table 268: Progress Indication Bit Byte 7 15 SKSV 16 (MSB) 6 5 4 3 2 1 Reserved Progress Indication 17 SKSV Progress Indication 0 (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.
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.
Hitachi Ultrastar 15K450 (FC-AL) Hard Disk Drive Specification 376
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 349. These codes are used internally by Hitachi and may change without notice.
UEC Description F11C F11D F11F F120 F121 F122 F123 F124 F125 F126 F127 F128 F129 F12A F12B F12C F130 F131 F132 F133 F134 F135 F136 BATS#2 error: XOR test error Incorrect Disk Code RPO SID invalid BATS error: Code Compatibility Failure BATS error: Code download in progress BATS error: Performance data read error Invalid request to enter sleep mode Bring-up error BATS error: Invalid RID/FID BATS error: Code checksum error BATS error: Invalid header DRAM test in progress DRAM test complete DRAM test error B
UEC Description F30A 130B F30C 130D F30E 130F F310 1311 F312 1313 F314 F315 F316 1317 F318 1319 F31A 131B F31C 131D F31E 131F F320 1321 F322 1323 F324 1325 F326 1327 F328 1329 F32A Motor: Unrecovered Gross speed error Motor: Recovered 12V OK error Motor: Unrecovered 12V OK error Motor: Recovered Speed error Motor: Unrecovered Speed error Motor: Recovered Spindle Current error Motor: Unrecovered Spindle Current error Moto: Recovered Internal 12V not OK timeout Motor: Unrecovered Internal 12V not OK timeou
UEC F408 1409 F40A 140B F40C 140D F40E 140F F410 1411 F412 1413 F414 1415 F416 1417 F418 1419 F41A 141B F41C 141D F41E 141F F420 1421 F422 1423 F424 1425 F426 1427 F428 1429 F42A 142B F42C 142D F42E 142F F430 Description 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: Recover
UEC Description 1431 F432 1433 F434 1435 F436 1437 F438 1439 F43A 143B F43C 143D F43E 143F F440 1441 F442 1443 F444 1445 F446 1447 F448 1449 F44A Servo: Recovered ADC Limit error Servo: Unrecovered ADC Limit error Servo: Recovered Balancer Resistance error Servo: Unrecovered Balancer Resistance error Servo: Recovered Balancer Resistance Limit error Servo: Unrecovered Balancer Resistance Limit error Servo: Recovered First Cylinder error Servo: Unrecovered First Cylinder error Servo: Recovered Valid Cylind
UEC 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 151A 151B 151C 151D 151E 151F 1520 1521 1522 1523 1524 1525 1527 1528 1529 152A 152B 152C 152D 152E 152F 1530 1531 1532 1533 1534 1535 1536 1537 1539 153A Description Unsupported log page Unsupported enclosure services function (FC-AL only) Invalid message (SCSI only) System buffer full Not ready to ready transition Login reset (FC-AL only) Power on reset SCSI bus reset (SCSI), LIP reset (FC-AL), SAS Hard Reset (SAS) Bus device reset (SCSI), Target Rese
UEC 153B 153C 153D 153E 153F 1540 1541 1542 1543 1544 1545 1548 154A 154B 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 155A 155B 155C 155D 155E 1560 1561 1562 1567 1568 1569 156A 156B 156C F56C F56F 1570 Description ESI: enclosure unavailable (FC-AL only) ESI: transfer failure (FC-AL only) ESI: tranfer refused (FC-AL only) Data phase error Abort by LIP (FC-AL), Abort by OOB (SAS) Invalid release of persistent reservation Low power condition on SPC buffer not allocated IU SCSI CRC error Echo buffer ove
UEC Description 1572 1573 LUN not ready; manual intervention required Commands cleared due to power failure event (SAS) 1601 F602 F603 F604 1606 F607 1608 F609 160A F60B 160C F60D 160E F60F 1610 F611 1612 F613 1614 F615 1616 F617 1618 F619 161A F61B 161C F61D 161E F61F 1620 F621 1622 F623 1624 F625 1626 F627 Channel/AE internal logic error Channel/AE hard logic error Channel/AE target failure Channel/AE calibration error Recovered data with PPM or precomp load Unrecovered data with PPM or precomp load
UEC Description F629 162A F62B 162C F62D 162E F62F 1630 F631 1632 F633 1634 F635 1636 F637 1638 F639 163A F63B 163C F63D 163E F63F 1640 F641 1642 F643 1644 F645 Unrecovered AE open write head error Recovered AE write transition error Unrecovered AE write transition error Recovered AE no write head current error Unrecovered AE no write head current error Recovered Channel Pre-TA error Unrecovered Channel Pre-TA error Recovered Channel write or NRZ parity error Unrecovered Channel write or NRZ parity error
UEC E70C E70D E70E E70F D710 E711 1712 F713 1714 F715 1716 F717 1718 F719 171A F71B 17B8 171C F71D 171E F71F 1720 F721 1722 F723 D724 E725 E726 E727 E728 E729 E72A D72B 172C F72D 172E F72F 1731 F732 1733 F734 Description 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 - rec
UEC 1737 F738 1739 F73A 173B F73C 173D F73E 1746 1747 1748 1749 F74B F74C F74D F74E F74F F750 F751 F752 F753 F754 F755 F756 F757 F758 1759 F75A F75B F75C F75D F75E F761 1770 F771 F772 F773 F774 F775 F776 F777 Description 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 Defect list format not supported Primary d
UEC F77A F77D 1792 1794 F795 1798 F799 F7B1 17B2 F7B3 17B4 F7B5 F7B9 17B8 17BA F7BB 17BC F7BD 17BE F7BF 17C0 F7C1 17C2 F7C3 17C4 F7C5 17C6 F7C7 17C8 F7C9 F7D0 17E0 F7E1 17E2 F7E3 17E4 F7E5 17E6 F7E7 17E8 F7E9 Description Unrecovered channel SBW timeout Recovery timeout Recovered Current pointer error Recovered Drive DMA timeout error Unrecovered Drive DMA timeout error Recovered ID not found error Unrecovered ID not found error Overall Command Timeout Recovered abort window error Unrecovered abort window e
UEC Description 17EA F7EB 17EC F7ED 17EE F7EF 17F0 F7F1 17F2 F7F3 17F4 F7F5 17F6 F7F7 17F8 F7F9 17FA F7FB 17FC F7FD 17FE F7FF Servo Recovered read/write abort SID unlock error Servo Unrecovered read/write abort SID unlock error Servo Recovered read/write abort WCS other error Servo Unrecovered read/write abort WCS other error Servo Recovered read/write abort hard reset Servo Unrecovered read/write abort hard reset Servo Recovered read/write abort RV sensor error Servo Unrecovered read/write abort RV sens
UEC Description 1A43 2A43 3A43 1A4A 2A4A 3A4A 1A50 2A50 3A50 1A56 2A56 3A56 1A5B 2A5B 3ASB 1AFE 2AFE 3AFE 1AFF 2AFF 3AFF 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
Index A Abbreviations...................................................................................................................117 abort sequence..................................................................................................................57 abort task..........................................................................................................................111 Abort Task (Implemented as ABTS BLS).....................................................................
C capability entry(s) ............................................................................................................87 Caution.............................................................................................................................1 class service parameters...................................................................................................68, 75 clear ACA .........................................................................................................
Download Microcode and Save (Mode 0101b) ...............................................................297 Drive Characteristics........................................................................................................7 Drive Mounting................................................................................................................40 Drive ready time ..............................................................................................................
FORMAT UNIT ..............................................................................................................118 format unit........................................................................................................................118 Formatted Capacity..........................................................................................................7 frame delimiter..............................................................................................................
LOG SENSE (4D) ...........................................................................................................140 Logical Block Cache Segment Size.................................................................................185 Logout (LOGO) ...............................................................................................................71 logout (LOGO) ................................................................................................................
Operating Vibration .........................................................................................................41 ordered set........................................................................................................................55 originator process associator............................................................................................79 Outline ......................................................................................................................
Q Queue Depth ....................................................................................................................328 Queue Full Status.............................................................................................................328 R Random Vibration............................................................................................................41 READ (10) - (28) .....................................................................................................
S S.M.A.R.T........................................................................................................................33 Safety ...............................................................................................................................51 SCSI Command Set .........................................................................................................115 SCSI Control Byte .................................................................................................
Temperature Threshold....................................................................................................173 terminate task ...................................................................................................................112 Terminology.....................................................................................................................103 TEST UNIT READY (00) ...............................................................................................
WRITE SAME (41) .........................................................................................................302 Z zero seeks .........................................................................................................................
© Copyright Hitachi Global Storage Technologies Hitachi Global Storage Technologies 5600 Cottle Road San Jose, CA 95193 Produced in the United States 10/08 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.