hit counter script
IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive Specifications
IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive Specifications

IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive Specifications

3.5 inch scsi hard disk drive
Table of Contents

Advertisement

IBM storage products
Hard disk drive specifications
Ultrastar 146Z10
3.5 inch SCSI hard disk drive
Models:
IC35L018UWDY10
IC35L018UCDY10
IC35L036UWDY10
IC35L036UCDY10
IC35L073UWDY10
IC35L073UCDY10
IC35L146UWDY10
IC35L146UCDY10
Revision 2.2
S07N9742-03
ibm
ibm
ibm
ibm
02 February 2002
Publication number 3630

Advertisement

Table of Contents
loading

Summary of Contents for IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive

  • Page 1 IBM storage products Hard disk drive specifications Ultrastar 146Z10 3.5 inch SCSI hard disk drive Models: IC35L018UWDY10 IC35L018UCDY10 IC35L036UWDY10 IC35L036UCDY10 IC35L073UWDY10 IC35L073UCDY10 IC35L146UWDY10 IC35L146UCDY10 Revision 2.2 02 February 2002 S07N9742-03 Publication number 3630...
  • Page 2 This page intentionally left blank.
  • Page 3 IBM storage products Hard disk drive specifications Ultrastar 146Z10 3.5 inch SCSI hard disk drive Models: IC35L018UWDY10 IC35L018UCDY10 IC35L036UWDY10 IC35L036UCDY10 IC35L073UWDY10 IC35L073UCDY10 IC35L146UWDY10 IC35L146UCDY10 Revision 2.2 02 February 2002 S07N9742-03 Publication number 3630...
  • Page 4 IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Armonk, NY 10577.
  • Page 5: Table Of Contents

    Table of contents Figures ................1.0 General .
  • Page 6 7.5.2 Power supply current ............7.5.3 Ripple voltage .
  • Page 7 8.7.9 Log Sense Page F ............8.7.10 Log Sense Page 10 .
  • Page 8 8.23.2 Receive Diagnostic Results Page 40 ........8.23.3 Receive Diagnostic Results Page 80 .
  • Page 9 10.1.18 QUEUE TAG MESSAGES (20xxh, 21xxh, 22xxh) ......10.1.19 IGNORE WIDE RESIDUE (2301h) ........10.1.20 IDENTIFY (80 - FFh) .
  • Page 10 11.17.1 Power on Diagnostics ..........11.17.2 Self-test by Send Diagnostic Command .
  • Page 11: Figures

    Figures Figure 1. Formatted capacity ............Figure 2.
  • Page 12 Figure 50. FORMAT UNIT (04h) ........... . . Figure 51.
  • Page 13 Figure 104. MODE SENSE (10) ........... . . Figure 105.
  • Page 14 Figure 158. SEND DIAGNOSTIC (1D) ..........Figure 159.
  • Page 15 Figure 211. Sense Data Byte 23 for POR Error ........Figure 212.
  • Page 16 Ultrastar 146Z10 hard disk drive specifications...
  • Page 17: General

    1.0 General 1.1 Introduction This document describes the specifications of the following IBM 3.5-inch SCSI drives: ! IC35L018UWDY10 (68 pin) ! IC35L018UCDY10 (80 pin) ! IC35L036UWDY10 (68 pin) ! IC35L036UCDY10 (80 pin) ! IC35L073UWDY10 (68 pin) ! IC35L073UCDY10 (80 pin)
  • Page 18: General Caution

    1.3 General caution This drive can be damaged by ESD (Electric Static Discharge). Any damages incurred to the drive after its removal from the shipping package and the ESD protective bag are the responsibility of the user. Ultrastar 146Z10 hard disk drive specifications...
  • Page 19: Outline Of The Drive

    ! Non head disk contact start stop ! Spindle rotation of 10,000 RPM ! Automatic actuator lock ! PFA (SMART) ! Glass substrate disks NOTE: PFA (Predictive Failure Analysis) is a trademark of the IBM Corporation Ultrastar 146Z10 hard disk drive specifications...
  • Page 20 This page intentionally left blank.
  • Page 21: Part 1. Functional Specification

    Part 1. Functional specification Ultrastar 146Z10 hard disk drive specifications...
  • Page 22 This page intentionally left blank.
  • Page 23: Fixed Disk Subsystem Description

    3.0 Fixed disk subsystem description 3.1 Control electronics The drive is electronically controlled by a microprocessor, logic modules, digital/analogue 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.
  • Page 24 This page intentionally left blank.
  • Page 25: Drive Characteristics

    4.0 Drive characteristics 4.1 Formatted capacity IC35L146UWDY10 IC35L073UWDY10 IC35L036UWDY10 IC35L018UWDY10 Description IC35L146UCDY10 IC35L073UCDY10 IC35L036UCDY10 IC35L018UCDY10 Label capacity 146.8 GB 73.4 GB 36.7 GB 18.35 GB Number of heads Number of disks Total data bytes 146,815,800,320 73,407,900,160 36,703,918,080 18,351,959,040 (512 bytes/sector) Total logical data 286,749,610 143,374,805...
  • Page 26: Inquiry Information

    4.3 Inquiry Information 4.3.1 Product ID Product ID in Section 8.5.1, "Inquiry data format - CmdDt = 0 EVPD = 0" on page 57 is as follows. Product ID Description IC35L018UWDY10-0 18.3 GB, 68 pin 18.3 GB, 80 pin IC35L018UCDY10-0 36.7 GB, 68 pin IC35L036UWDY10-0 36.7 GB, 80 pin...
  • Page 27: Cylinder Allocation

    4.4 Cylinder allocation Zone Physical Cylinders Sectors/Track Data Zone 0 0 - 383 Data Zone 1 384 - 3967 Data Zone 2 3968 - 5631 Data Zone 3 5632 - 6527 Data Zone 4 6528 - 8703 Data Zone 5 8704 - 15359 Data Zone 6 15360 - 18047...
  • Page 28: Performance Characteristics

    4.5 Performance characteristics The performance of a drive is characterized by the following parameters: ! Command overhead ! Mechanical head positioning - Seek time - Latency ! Data transfer speed ! Buffering operation (read ahead/write cache) NOTE: All the above parameters contribute to drive performance. There are other parameters that contri- bute to the performance of the actual system.
  • Page 29: Mechanical Positioning

    4.5.2 Mechanical positioning 4.5.2.1 Average seek time (including settling) Command Type Typical (ms) Max (ms) 146 GB model Read all other models 146 GB model Write all other models Figure 7. Mechanical positioning performance “Typical” and “Max” are given throughout the performance specification by: Typical Average of the drive population tested at nominal environmental and voltage conditions.
  • Page 30: Drive Ready Time

    4.5.2.3 Cylinder switch time (cylinder skew) Typical (ms) Cylinder skew 0.70 Figure 9. Cylinder Skew A cylinder switch time is defined as the amount of time required by the fixed disk to access the next sequential block after reading the last sector in the current cylinder. 4.5.2.4 Head switch time (head skew) Typical (ms) Head skew...
  • Page 31: Data Transfer Speed

    4.5.5 Data transfer speed Description Typical (Mbyte/s) Disk-Buffer Transfer (Zone 0) Instantaneous All models 73.7 146-GB Model 66.7 73-GB Model 66.6 Sustained 36-GB Model 66.4 18-GB Model 66.2 Disk-Buffer Transfer (Zone 16) Instantaneous All models 37.5 146-GB Model 33.9 73-GB Model 33.9 Sustained 36-GB Model 33.8 18-GB Model 45.9...
  • Page 32: Throughput

    4.5.7 Throughput 4.5.7.1 Simple sequential access Operation Typical (ms) Max (ms) Zone 0 <260 Zone 0 <290 Sequential read/write Zone 14 <510 Zone 11 <560 Figure 15. Simple sequential access performance (sector size 512 byte case) The above table gives the time required to read/write for a total of 8000x consecutive blocks (16,777,216 bytes) accessed by 128 read/write commands.
  • Page 33: Data Integrity

    5.0 Data integrity The drive retains recorded information under all non-write operations. No more than one sector will be lost by power down during write operation while write cache is disabled. If power down occurs before completion of data transfer from write cache to disk while write cache is enabled, the data remaining in write cache will be lost.
  • Page 34 This page intentionally left blank.
  • Page 35: Physical Format

    6.0 Physical format Media defects are remapped to the next available sector during the Format Process in manufacturing. The mapping from LBA to the physical locations is calculated by an internally maintained table. 6.1 Shipped format (P-List) ! Data areas are optimally used ! No extra sector is wasted as a spare throughout user data areas ! All pushes generated by defects are absorbed by spare tracks of the inner zone Figure 17.
  • Page 36 This page intentionally left blank.
  • Page 37: Specification

    7.0 Specification 7.1 Electrical interface specification 7.1.1 Power connector The power connector of 68-pin models complies with the SFF-8009 Rev. 4.2. Power pin assignment of 68-pin models is as shown below. Voltage +12 V Figure 18. Power connector pin assignments Eighty-pin SCA-2 models use a DDK connector (PN HD2-PA080-A14B) or equivalent, which is compatible with the Specification of “Single Attachment for Small SCSI Disk Drives”...
  • Page 38: Scsi Bus Connector

    7.1.2 SCSI bus connector The Ultrastar 146Z10 has 68-pin models and 80-pin SCA-2 models. 7.1.2.1 SCSI signal connector (68-pin model) The pin assignments of the interface signals conform to SPI-4 as shown in the table below. Connector contact Connector contact Signal name Signal name number...
  • Page 39: Figure 20. Table Of Signals

    7.1.2.2 SCSI signal connector (80 pin SCA-2 model) The 80-pin SCA-2 model uses a DDK connector which is compatible with SPI-4. Connector contact Connector contact Signal name Signal name number number 12 Volt Charge 12V Ground 12 Volt 12V Ground 12 Volt 12V Ground 12 Volt...
  • Page 40: Scsi Cable

    7.1.3 SCSI cable Refer to ANSI SPI-4. 7.1.4 SCSI bus terminator Onboard SCSI active termination feature is not supported. The using system is responsible for making sure that all required signals are terminated at both ends of the bus cable. Terminator power Termination power can be provided by the drive 5V supply through the current limiter and Schottky diode.
  • Page 41: Auxiliary Connector On 68-Pin Model

    7.1.7 Auxiliary connector on 68-pin model In addition to the Option Jumper Block the 68-pin models have an Auxiliary Connector between the power connector and the 68-pin SCSI connector. The settings at the Option Jumper Block and the Auxiliary Connector work as a logical OR. The drive conforms SFF-8009, Rev 4.2. ! Pin #1,3,5,7 specify SCSI-ID as -DAS0, 1 ,2, 3.
  • Page 42: Option Jumper Block

    7.2 Option jumper block Two jumper blocks, J4 and J6, are located on the card of 68- and 80-pin models as shown in the figure below. J4 has 14 positions numbered #1 - #14 and controls Terminator Power supply. As described in Section 7.1.7, "Auxiliary connector on 68-pin model" on page 25, some of the jumper pins on J4 of the 68-pin models can also be controlled through the Auxiliary Connector.
  • Page 43: Jumper Signal Description On J6

    7.2.1 Jumper signal description on J6 7.2.1.1 Position #1-2 ! Enable Auto Spin Up (68-pin model) If a jumper is installed, the drive will spin up automatically after power on reset. If a jumper is not installed, the drive will not spin up unless a START UNIT command is received. ! Disable Auto Spin Up (80-pin model) If a jumper is not installed, the drive will spin up automatically after power on reset.
  • Page 44: Jumper Signal Description On J4

    7.2.1.3 Position #7-8: Disable SCSI Parity Check Installing a jumper disables SCSI Parity checking 7.2.1.4 Position #9-10 Enable TI-SDTR Installing a jumper enables Target Initiated Synchronous Data Transfer Request (SDTR) and Wide Data Transfer Request (WDTR) negotiation. If this jumper is not installed, SSM (Synchronous select Mode) bit in Mode Page 0 controls Target Initiated SDTR and WDTR negotiation.
  • Page 45: Figure 25. Scsi Device Id

    7.2.2.4 Position #7-8 to #13-14: Device ID These four lines (-DAS0, -DAS1, -DAS2, -DAS3) define device ID on the SCSI BUS. -DAS0 is the least significant bit and -DAS3 is the most significant bit. Device ID is defined in the table below. In the table 'on' means a jumper is installed and 'off' means that no jumper is installed.
  • Page 46: Environment

    7.3 Environment Operating conditions Temperature 5 to 55°C (See note) Relative Humidity 8 to 90%, non-condensing Maximum Wet Bulb Temperature 29.4°C, non-condensing Maximum Temperature Gradient 15°C/Hour Altitude –300 to 3048 m Non-operating conditions Temperature –40 to 65°C Relative Humidity 5 to 95%, non-condensing Maximum Wet Bulb Temperature 35°C, non-condensing Maximum Temperature Gradient...
  • Page 47: Cooling Requirements

    7.4 Cooling requirements Drive component temperatures must remain within the limits specified in the following table. Maximum component temperature ratings must not be exceeded under any operating condition. The drive may re- quire forced air cooling to meet specified operating temperatures. Maximum allowable surface Module name Location...
  • Page 48: Dc Power Requirements

    7.5 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 special power on/off sequencing required. Adequate secondary over-current protection is the responsibility of the system. A limit of 10 A is required for safety purposes.
  • Page 49: Ripple Voltage

    36-GB models +5 Volts +5 Volts +12 Volts +12 Volts Total (W) (All values in Amps.) Pop Mean Std. Dev Pop Mean Std. Dev Idle Average 0.50 0.02 0.37 0.03 Idle ripple (peak-to-peak) 0.22 0.02 0.40 0.10 Seek average 0.55 0.02 0.86 0.03...
  • Page 50: Reliability

    7.6 Reliability 7.6.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 operating environment conditions specified on page 30. 7.6.2 Data reliability The probability of uncorrectable data error rate is 10 in 1x10 bits read.
  • Page 51: Temperature Warning

    7.6.7 Temperature Warning Temperature Warning is enabled by setting EWASC (Enable Warning Additional Sense Code) bit to 1 and setting DEXCPT (Disable Exception Control) bit to 0 in Mode Page 1C. For the mode page setting refer to Section 8.8.13, "Mode Page 1C (Informational Exceptions Control)" on page 111. The warning is issued as sense data (Sense Key 01h, Code 0Bh, Qual 01h).
  • Page 52: Mechanical Specifications

    7.7 Mechanical specifications 7.7.1 Outline 7.7.1.1 68-pin model Figure 36. Outline of the 68-pin model 7.7.1.2 80-pin model Figure 37. Outline of the 80-pin model Ultrastar 146Z10 hard disk drive specifications...
  • Page 53: Mechanical Dimensions

    7.7.2 Mechanical dimensions The drive complies with SFF-8301 with the exception of tolerance of width which is ±0.4 mm rather than ±0.25 mm. Height [mm] 25.4 ± 0.4 Width [mm] 101.6 ± 0.4 Length [mm] 146.0 ± 0.6 Weight [grams - maximum] Figure 39.
  • Page 54: Interface Connector

    7.7.3 Interface connector 7.7.3.1 68-pin model 51.3 ± 0.5 2.54 ± 0.1 1.27 ± 0.1 TYP Pin 1 10.4 ± 0.5 Pin 68 5.08 ± 0.1 32.5 ± 0.5 4.5 ± 0.5 2 ± 0.1 TYP Figure 40. Interface connector for 68-pin models 7.7.3.2 80-pin model Pin 41 4.6 ±...
  • Page 55: Mounting Positions And Tappings

    7.7.4 Mounting positions and tappings 1 1 1 1 1 1 1 1 (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (6X) 6-32 UNC (4X) (4X) (4X) (4X) (4X) (4X)
  • Page 56: Heads Unload And Actuator Lock

    Drive level vibration test and shock test are to be conducted with the drive mounted to the table using the bottom four screws. 7.7.5 Heads unload and actuator lock Heads are moved out from disks (unload) to protect the disk data during shipping, moving or storage. At power down, the heads are automatically unloaded from the disk area and the head actuator locking mechanism will secure the heads in the unload position.
  • Page 57: Vibration And Shock

    Vibration and shock All vibration and shock measurements in this section are made with a drive that has no mounting attach- ments for the systems. The input power for the measurements is applied to the normal drive mounting points. 7.8.1 Operating vibration 7.8.1.1 Random vibration The drive is designed to operate without unrecoverable errors while being subjected to the following vibration levels.
  • Page 58: Operating Shock

    Overall RMS (Root Mean Square) level of vibration is 1.04G (RMS). The disk drive does not sustain permanent hardware damage or loss of previously recorded data after being subjected to the environment described above. 7.8.2.2 Swept sine vibration ! 2 G (Zero to peak), 5 to 500 to 5 Hz sine wave ! 0.5 oct/min sweep rate 7.8.3 Operating shock The drive meets the following criteria:...
  • Page 59: Acoustics

    7.9 Acoustics The upper limit criteria of the 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 ISO7779. Drives are to meet this criteria in both board up and board down orientations. A-weighted sound power level (Bel) Model...
  • Page 60: Identification 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 IBM logo, IBM part number and the statement “Made by IBM Japan Ltd.”, or IBM approved equivalent...
  • Page 61: Electromagnetic Compatibility

    The drive, when installed in a suitable enclosure and exercised with a random accessing routine at maximum data rate, meets the worldwide EMC requirements listed below. IBM will provide technical support to meet the requirements to comply with the EMC specifications. ! United States Federal Communications Commission (FCC) Rules and Regulations (Class B), Part 15 ! IBM Corporate Standard C-S 2-0001-005 ! CISPR Publication 22;...
  • Page 62: Safety

    7.12 Safety The following shows the safety standards for different countries. 7.12.1 UL and CSA standard conformity The drive is qualified per UL1950 third edition and CAN/CSA C22.2 No. 950-95 third edition, for the use in Information Technology Equipment, including Electric Business Equipment. The UL recognition, or the CSA certification, is maintained for the product life.
  • Page 63: Part 2. Interface Specification

    Part 2. Interface specification Ultrastar 146Z10 hard disk drive specifications...
  • Page 64 This page intentionally left blank.
  • Page 65: Scsi Command Set

    8.0 SCSI Command Set Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory. Type Code Description FORMAT UNIT INQUIRY LOG SELECT LOG SENSE MODE SELECT (6) MODE SELECT (10) MODE SENSE (6) MODE SENSE (10) PERSISTENT RESERVE IN PERSISTENT RESERVE OUT...
  • Page 66: Scsi Control Byte

    8.1 SCSI Control Byte The Control Byte is the last byte of every CDB. The format of this byte is shown below. VU = 0 Reserved = 0 FLAG LINK Figure 49. SCSI Control Byte VU stands for Vendor Unique. FLAG The Flag bit specifies which message the drive shall return to the initiator if the link bit is one and the command completes without any error.
  • Page 67: Format Unit (04H)

    8.4 FORMAT UNIT (04h) Byte Command Code = 04h Reserved FmtData CmpList Defect List Format VU = 0 (MSB) Interleave Factor (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 50. FORMAT UNIT (04h) The FORMAT UNIT command performs a physical formatting of the drive media. This includes handling defective sectors and overwriting all data areas with a constant data pattern.
  • Page 68: Defect List

    8.4.1 Defect list Following is the format of the Defect List Header sent during the DATA OUT phase when FmtData is set to one. Byte Reserved = 0 DPRY DCRT STPF=1 IP = 0 DSP= 0 Immed (MSB) Defect List Length (LSB) Figure 51.
  • Page 69: Defect Descriptor

    1. The drive cannot locate a required defect list nor determine that the list exists. 2. The drive encounters an unrecoverable error while accessing a required defect list. ! IP (Initialization Pattern) bit must be set to zero. The drive initializes all data with zeros. ! DSP (Disable Saving Parameters) bit must be set to zero.
  • Page 70: Figure 53. Defect Descriptor - Bytes From Index Format

    8.4.2.2 Bytes From Index format Each defect descriptor for the Bytes From Index format specifies that the sector containing this byte be marked defective. The defect descriptor is comprised of the cylinder number of the defect, the head number of the defect, and the defect bytes from index. Byte (MSB) Cylinder Number of Defect...
  • Page 71: Inquiry (12H)

    8.5 INQUIRY (12h) Byte Command Code = 12h Reserved Reserved = 0 CmdDt EVPD Page Code Reserved = 0 Allocation Length VU =0 Reserved = 0 FLAG LINK Figure 55. INQUIRY (12) The INQUIRY command requests the parameters of the drive to be sent to the initiator. ! CmdDT bit of one specifies that the drive shall return the command support data information identified by the Page Code field in the CDB.
  • Page 72: Figure 56. Page Code Descriptions

    CmdDt EVPD PAGE CODE Description The drive returns the standard INQUIRY data. The drive returns CHECK CONDITION status with the Non Zero sense key of ILLEGAL REQUEST and the additional sense code of INVALID FIELD IN CDB. The drive returns the vital product data of page code Supported requested.
  • Page 73: Inquiry Data

    ACKREQ Addr32 Addr16 REL_A Wb_32 Wb_16 Sync Link CmdQu RSVD 8-15 Vendor ID = 'IBM ' (ASCII) 16-31 Product ID (ASCII) 32-35 Product Revision Level (ASCII) 36-43 Unit Serial Number (ASCII) 44-52 Reserved = 0 Reserved = 0 Clocking=11b 54-95...
  • Page 74 ! CmdQu is set to one to indicate that the drive supports command queuing. ! Vendor ID is 'IBM' padded with ASCII blanks. ! Product ID is specified in ASCII characters. Refer to Section 4.3.1, "Product ID" on page 10.
  • Page 75: Figure 58. Command Support Data Format

    8.5.1.2 Inquiry data format - CmdDt = 1 Byte Peripheral Qualifier Peripheral Device Type Reserved Support Version Reserved Reserved CDB Size = m-5 CDB Usage Data Figure 58. Command support data format ! Peripheral Qualifier is set to zero to indicate that the LUN specified in the IDENTIFY Message is cur- rently supported.
  • Page 76: Figure 59. Support Values And Meanings

    Support Description 000b Data about the requested SCSI operation code is not currently available. The drive does not support the tested SCSI operation code. All data after 001b byte 1 is undefined. 010b Reserved. The drive supports the tested SCSI operation code in conformance with 011b the SCSI standard.
  • Page 77: Figure 60. Inquiry Data - Evpd = 1 (Page Code = 00)

    8.5.1.3 Inquiry data format - EVPD = 1 - Page Code = 00 Byte Qualifier = 0 Peripheral Device Type = 0 Page Code = 00h Reserved = 0 Page Length = 03h Supported Page Code = 00h Supported Page Code = 80h Supported Page Code = 83h Figure 60.
  • Page 78: Figure 61. Inquiry Data - Evpd = 1 (Page Code = 80H)

    8.5.1.4 Inquiry data format - EVPD = 1 - Page Code = 80h Byte Qualifier = 0 Peripheral Device Type = 0 Page Code = 80h Reserved = 0 Page Length = 16 (10h) 4-19 Serial Number (ASCII) Figure 61. INQUIRY DATA - EVPD = 1 (Page Code = 80h) Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
  • Page 79: Figure 62. Inquiry Data - Evpd = 1 (Page Code = 83H)

    8.5.1.5 Inquiry data format - EVPD = 1 - Page Code = 83h Byte Qualifier = 0 Peripheral Device Type = 0 Page Code = 83h Reserved = 0 Page Length = 12 (0Ch) Reserved = 0 Code Set = 1 Reserved Association Identifier Type = 3...
  • Page 80: Log Select (4Ch)

    8.6 LOG SELECT (4Ch) Byte Command Code = 4Ch Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Parameter List Length (LSB) Reserved = 0 FLAG LINK Figure 63. LOG SELECT (4C) The LOG SELECT command provides a means for the initiator to clear statistical information maintained by the drive and reported via the LOG SENSE command.
  • Page 81: Log Sense (4Dh)

    8.7 LOG SENSE (4Dh) Byte Command Code = 4Dh Reserved = 0 Reserved = 0 PPC= 0 Page Code Reserved = 0 (MSB) Parameter Pointer (LSB) (MSB) Allocation Length (LSB) Reserved = 0 FLAG LINK Figure 64. LOG SENSE 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.
  • Page 82: Log

    8.7.1 Log Page parameters Each log page begins with a four-byte page header followed by zero or more variable-length log para- meters. ! 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 four-byte parameter header followed by one or more bytes of para- meter value data.
  • Page 83: Log Sense

    8.7.2 Log Sense Page 0 Page 0 indicates the supported log sense pages. This page is used to determine which additional pages can be requested by an Initiator. Byte Reserved Page code = 0 Reserved Page Length = 000Ah (Number of Pages Supported) First supported page 0h Second supported page 2h Third supported page 3h...
  • Page 84: Log Sense

    8.7.3 Log Sense Page 2 This page contains counters for write errors. Byte Reserved Page code = 02h Reserved PageLength = 54h Parameter Code = 00h DU = DS = TSD = ETC = LBIN = TMC = 0 Parameter Length = 08h 8-15 Errors recovered without delay = 0 16-17...
  • Page 85: Figure 67. Log Sense Page 2 (Part 2 Of 2)

    Byte 64-65 Parameter Code = 05h DU = DS = TSD = ETC = LBIN = TMC = 0 Parameter Length = 08h 68-75 Total bytes written 76-77 Parameter Code = 06h DU = DS = TSD = ETC = LBIN TMC = 0 Parameter Length = 08h...
  • Page 86: Log Sense

    8.7.4 Log Sense Page 3 This page contains counters for read errors. Byte Reserved Page code = 03h Reserved PageLength = 54h Parameter Code = 00h DU = DS = TSD = ETC = LBIN TMC = 0 Parameter Length = 08h 8-15 Errors recovered without delay = 0 16-17...
  • Page 87: Figure 69. Log Sense Page 3 (Part 2 Of 2)

    Byte DU = DS = TSD = ETC = LBIN TMC = 0 Parameter Length = 08h 68-75 Total bytes read 76-77 Parameter Code = 06h DU = DS = TSD = ETC = LBIN TMC = 0 Parameter Length = 08h 80-87 Total number of hard errors Figure 69.
  • Page 88: Log Sense

    8.7.5 Log Sense Page 5 This page contains counters for VERIFY command and the verify portion of WRITE AND VERIFY command. Byte Reserved Page code = 05h Reserved PageLength = 54h Parameter Code = 00h DU = DS = TSD = ETC = LBIN TMC = 0...
  • Page 89: Log Sense

    Byte DU = DS = TSD = ETC = LBIN TMC = 0 LP= 0 Parameter Length = 08h 68-75 Total Bytes Verified 76-77 Parameter Code = 06h DU = DS = TSD = LBIN TMC = 0 Parameter Length = 08h 80-87 Total number of hard errors Figure 71.
  • Page 90: Log Sense

    8.7.7 Log Sense Page D This page contains temperature information. Byte Reserved Page code = 0Dh Reserved PageLength = 0Ch Parameter Code = 0000h ETC = LBIN TMC = 0 Parameter Length = 02h Reserved Current temperature (degrees Celsius) 10-11 Parameter Code 0001h ETC = LBIN...
  • Page 91: Log Sense

    8.7.8 Log Sense Page E This page contains the start-stop cycle information. Byte Reserved Page code = 0Eh Reserved PageLength = 24h Parameter Code = 0001h TSD = ETC = LBIN TMC = 0 Parameter Length = 06h 8-11 Year of Manufacture (4 ASCII characters) 12-13 Week of Manufacture (2 ASCII characters) 14-15...
  • Page 92: Log Sense

    8.7.9 Log Sense Page F This page contains the Application Client Log. Byte Reserved Page code = 0Fh Reserved Page length = 4000h Application client log parameter First application client log parameter -4003h Last application client log parameter The following table describes the application client log parameter structure. Byte Parameter code ETC =...
  • Page 93: Log Sense

    8.7.10 Log Sense Page 10 This page contains Self-test results. Byte Reserved Page code = 10h Reserved PageLength = 190h Self-test results log parameters First self-test results log parameter -403h Last self-test results log parameter The results of the twenty most recent self-tests are stored in this Log page. The following table describes the self-test results log parameter structure.
  • Page 94: Figure 77. Log Sense Page 10 Self-Test Results

    Value Description The self-test routine completed without error The background self-test routine was aborted by the initiator using a SEND DIAGNOSTICS command with the Abort Background self-test function The self-test routine was aborted by the application client by a Task Management function of a reset An unknown error occurred while the drive was executing the self-test routine and the drive was unable to complete the self-test routine...
  • Page 95: Log Sense Page 2F

    Extended Segment Foreground Test Background Test Number Drive ready check Drive ready check RAM test Spin check Spin check Write, read and compare test Write, read and compare test ECC circuit test ECC circuit test Seek test Seek test SMART check SMART check Low level format check Low level format check...
  • Page 96: Mode Sense (6) (1A)

    8.8 MODE SENSE (6) (1A) Byte Command Code = 1Ah Reserved RSVD Reserved = 0 Page Code Subpage Code Allocation Length VU = 0 Reserved = 0 FLAG LINK Figure 80. MODE SENSE (1A) The MODE SENSE (1A) command provides a means for the drive to report various device parameters to the initiator.
  • Page 97: Mode Parameter List

    Report saved value. The drive returns the saved value for the page code specified. Saved values are one of following: ! the values saved as a result of MODE SELECT command ! identical to the default values ! zero when the parameters are not supported The Page Length byte value of each page returned by the drive indicates up to which fields are supported on that page.
  • Page 98: Figure 83. Mode Parameter Header

    Mode parameter header (10) Byte (MSB) Mode Data Length (LSB) Medium Type = 0 Reserved = 0 Reserved = 0 (MSB) Block Descriptor Length ( = 0 or 8) (LSB) Figure 83. Mode parameter header (10) ! Mode Data Length. When using the MODE SENSE command, the mode data length field specifies the length in bytes of the following data that is available to be transferred.
  • Page 99: Figure 84. Mode Parameter Block Descriptor

    8.8.1.2 Block Descriptor Byte 0 Number of Blocks (MSB) Byte 1 Byte 2 Byte 3 (LSB) Byte 4 Density code = 0 Byte 5 Block Length Byte 6 Byte 7 Figure 84. MODE Parameter Block Descriptor The Block descriptor provides formatting information about the Number of Blocks (user addressable) to format at the specified Block Length.
  • Page 100: Figure 85. Mode Parameter Page Format

    8.8.1.3 Page Descriptor RSVD= Byte 0 Page Code Byte 1 Page Length Byte Mode Parameters Figure 85. MODE Parameter Page Format Each mode page contains a page code, a page length, and a set of mode parameters. When using the MODE SENSE command, a Parameter Savable (PS) bit of one indicates that the mode page can be saved by the drive in the reserved area of the drive.
  • Page 101: Mode Page 0 (Vendor Unique Parameters)

    8.8.2 Mode Page 0 (Vendor Unique Parameters) Byte Default RSVD=0 Page Code = 00h Page Length = 0Eh Ignored Ignored ARHES ASDPE Ignored CMDAC Ignored RRNDE [CPE] Ignored Ignored Ignored CAEN Ignored IGRA AVERP Ignored Ignored ECRC Ignored Ignore [ADC] Ignored LED Mode Temperature...
  • Page 102 ARHES of zero indicates the drive will not perform ARHES operation. ARRE and AWRE (Mode Page 1) do not affect ARHES operation and ARHES works independently. ! ASDPE (Additional Save Data Pointer Enable) is used to control the sending of additional save data pointers messages.
  • Page 103 - LED Mode = 0h: CMDAC determines the behavior of LED. CMDAC is one: Command Active CMDAC is zero: Motor Active - LED Mode = 1h: Motor Active - LED Mode = 2h: Command Active - LED Mode = 3h: Degraded Mode - LED Mode = 4h: Command Active/Degraded Mode - LED Mode = other: Motor Active ! Temperature Threshold specifies the threshold value in degrees Celsius for the SMART warning for...
  • Page 104: Mode Page 1 (Read/Write Error Recovery Parameters)

    8.8.3 Mode Page 1 (Read/Write Error Recovery Parameters) Byte Default RSVD=0 Page Code = 01h Page Length = 0Ah AWRE ARRE EER=0 Read Retry Count Correction Span (Ignored) Head Offset Count (Ignored) Data Strobe Offset Count (Ignored) Reserved Write Retry Count Reserved (MSB) Recovery Time Limit...
  • Page 105 ! PER (Post Error) of one indicates that the drive reports recovered errors. PER of zero disables the reporting of recovered errors. ! DTE (Disable Transfer on Error) is ignored, but it must be set to zero if PER is set to zero. ! DCR (Disable Correction) of one indicates that the off-line ECC correction is not used for data error recovery.
  • Page 106 The following summarizes valid modes of operation. If an illegal mode is set, the MODE SELECT com- mand will complete successfully but the action of the drive when an error occurs is undefined. PER DTE DCR TB DESCRIPTION Retries and Error Correction are attempted. Recovered and/or corrected data (if any) are transferred with no CHECK CONDITION status at the end of the transfer.
  • Page 107 The highest level error is reported at the end of transfer. Retries and error correction are attempted. Recovered and/or corrected data (if any) 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.
  • Page 108: Mode Page 2 (Disconnect/Reconnect Parameters)

    8.8.4 Mode Page 2 (Disconnect/Reconnect Parameters) Byte Default RSVD=0 Page Code = 02h Page Length = 0Eh Read Buffer Full Ratio Write Buffer Empty Ratio (MSB) Bus Inactivity Limit = 0 (LSB) (MSB) Disconnect Time Limit = 0 (LSB) (MSB) Connect Time Limit = 0 (LSB) (MSB)
  • Page 109 ! DIMM (Disconnect Immediate) of one indicates that the drive is required to disconnect after receiving a command prior to starting a data phase. A DIMM of zero indicates that the drive may transfer data for a command immediately after receiving it without disconnecting. Whether or not the drive does so depends upon the workload and the settings of the other parameters in this mode page.
  • Page 110: Mode Page 3 (Format Device Parameters)

    8.8.5 Mode Page 3 (Format Device Parameters) Byte RSVD= PS = 0 Page Code = 03h Page Length = 16h (MSB Tracks per Zone (LSB) (MSB) Alternate Sectors per Zone = 0 (LSB) (MSB) Alternate Tracks per Zone = 0 (LSB) (MSB) Alternate Tracks per Logical Unit = 0...
  • Page 111 The format device page contains parameters which specify the medium format. This page contains no changeable parameters. ! Tracks per Zone specifies the number of tracks within the zone. This field is a function of the active notch. A value of 0 in the following parameters indicates that they are drive specific. Alternate Sectors per Zone Alternate Tracks per Zone Alternate Tracks per Logical Unit...
  • Page 112: Mode Page 4 (Rigid Disk Drive Geometry Parameters)

    8.8.6 Mode Page 4 (Rigid Disk Drive Geometry Parameters) Byte RSVD= 0 Page Code = 04h Page Length = 16h (MSB) Number of Cylinders (LSB) Number of heads (MSB) Starting Cylinder - Write Precompensation = 0 (LSB) (MSB) Starting Cylinder - 9-11 Reduced Write Current = 0 (LSB)
  • Page 113: Mode Page 7 (Verify Error Recovery Parameters)

    8.8.7 Mode Page 7 (Verify Error Recovery Parameters) Byte Default RSVD=0 Page Code = 07h Page Length = 0Ah Reserved EER=0 DTE=0 Verify Retry Count Correction Span (Ignored) Reserved Reserved Reserved Reserved Reserved (MSB) Verify Recovery Time Limit (LSB) Figure 92. Mode Page 7 (Verify Error Recovery Parameters) The Verify recovery parameters are used for VERIFY command and verify potion of WRITE AND VERIFY command.
  • Page 114: Mode Page 8 (Caching Parameters)

    ! Verify Recovery Time Limit is a timer for the maximum command execution time (AVERP is set to one, Mode Page 0) or the maximum accumulated ERP time (AVERP is zero). The unit of timer value is 1 ms which must be from 40 ms to 65535 ms (65.5 seconds). If time out occurs, a CHECK CONDITION will be returned.
  • Page 115 operates as if AWRE (Mode Page 1) is set to one. When WCE is set to zero indicates that the drive issues GOOD status for a WRITE command only after successfully writing the data to the media. Note: When WCE is set to one, a SYNCHRONIZE CACHE command must be issued to write the data in cache segments to be written to the media before powering down the drive.
  • Page 116: Mode Page A (Control Mode

    8.8.9 Mode Page A (Control Mode Page Parameters) Byte Default RSVD=0 Page Code = 0Ah Page Length = 0Ah TST=000b Reserved RLEC=0 GLSTD=0 Queue Algorithm Modifier RSVD=0 QErr DQue RAENP UAAENP EAENP EECA=0 Reserved = 0 Reserved = 0 (MSB) Ready AEN Holdoff Period (LSB) (MSB)
  • Page 117 1h : All active commands and all queued commands from all initiators are aborted when the drive returns the CHECK CONDITION status. A unit attention condition will be generated for each initiator which had commands in the queue except for the initiator that received the CHECK CONDITION status.
  • Page 118: Mode Page 0C (Notch Parameters)

    8.8.10 Mode Page 0C (Notch Parameters) Byte PS = RSVD= Page Code = 0Ch Page Length = 16h LPN = RSVD = 0 Reserved = 0 (MSB) Maximum Number of Notches = 011h (LSB) (MSB) Active Notch (LSB) (MSB) Starting Boundary (LSB) (MSB) Ending Boundary...
  • Page 119 Mode Page 3 - Alternate Sector per Zone - Alternate Track per Zone - Alternate Track per Logical Unit - Sector per Track - Track Skew Factor - Cylinder Skew Factor ! Starting Boundary contains the first physical location of the active notch. The first three bytes are the cylinder number and the last byte is the head.
  • Page 120: Mode Page 19 (Port Control)

    8.8.11 Mode Page 19 (Port Control) 8.8.11.1 Short Format of Port Control Page Byte Default Long=0 Page Code = 019h Page Length = 06h Reserved Reserved Protocol identifier = 1 (MSB) Synchronous transfer timeout (LSB) Reserved Reserved Figure 96. Page 19 (Port Control parameters) Short format The drive maintains an independent set of port control mode page parameters for each SCSI initiator port.
  • Page 121: Figure 97. Page 19 (Port Control Parameters) Long Format

    8.8.11.2 Long Format of Port Control Page Byte Default Long=1 Page Code = 019h Subpage code (MSB) Page Length (n–3) (LSB) Reserved Reserved Protocol identifier = 1h Protocol Specific Mode Parameters Figure 97. Page 19 (Port Control Parameters) Long Format The drive maintains an independent set of port control mode page parameters for each SCSI initiator port.
  • Page 122: Figure 98. Margin Control Subpage

    8.8.11.3 Margin Control Subpage Byte RSVD Driver Strength Reserved Driver Asymmetry Driver Precompensation Driver Slew Rate Reserved Reserved Vendor specific Reserved Figure 98. Margin Control Subpage The margin control subpage contains parameters that set and report margin control values for usage between the initiator and the drive on subsequent synchronous and paced transfers.
  • Page 123: Figure 99. Saved Training Configuration Subpage

    8.8.11.4 Saved Training Configuration Values Subpage Byte RSVD DB (0) Value 64-67 DB (15) Value 68-71 P_CRCA Value 72-75 P1 Value 76-79 BSY Value 80-83 SEL Value 84-87 RST Value 88-91 REQ Value 92-95 ACK Value 96-99 ATN Value 100-103 C/D Value 104-107 I/O Value...
  • Page 124: Figure 100. Negotiated Settings Subpage

    8.8.11.5 Negotiated Settings Subpage Byte Transfer Period Factor Reserved REQ/ACK Offset Transfer Width Exponent RSVD Protocol Options Bits Transceiver RSVD Mode Reserved Reserved 1: Sent PCOMP_EN 2: Received PCOMP_EN Figure 100. Negotiated Settings Subpage The negotiated settings subpage is used to report the negotiated settings of the drive for the current I_T nexus.
  • Page 125: Figure 101. Report Transfer Capabilities Subpage

    8.8.11.6 Report Transfer Capabilities Subpage Byte Minimum Transfer Period Factor Reserved Maximum REQ/ACK Offset Maximum Transfer Width Protocol Options Bits Supported Reserved Figure 101. Report Transfer Capabilities Subpage The report transfer capabilities subpage is used to report the transfer capabilities of the drive. The values in this subpage are not changeable via a MODE SELECT command.
  • Page 126: Mode Page 1A (Power Control Parameters)

    8.8.12 Mode Page 1A (Power Control Parameters) Byte RSVD RSVD Page Code = 1Ah Page Length = 0Ah Reserved Reserved [Idle] Standby (MSB) Idle Condition Timer (LSB) (MSB) Standby Condition Timer (LSB) Figure 102. Page 1A (Power Control) ! Idle and Idle Condition Timer are ignored. ! Standby of one indicates that the drive uses Standby Condition Timer to determine the length of inactivity time to wait before unloading the actuator.
  • Page 127: Mode Page 1C (Informational Exceptions Control)

    8.8.13 Mode Page 1C (Informational Exceptions Control) Default Byte RSVD=0 Page Code = 1Ch Page Length = 0Ah [PERF] RSVD [EBF] EWASC DEXCPT TEST RSVD [LOGERR] Reserved Method of Reporting (MSB) Interval Timer (LSB) (MSB) Report Count (LSB) Figure 103. Page 1C (Informational Exceptions Control) ! LOGERR (Log Errors) is ignored.
  • Page 128 is set to UNIT ATTENTION and the additional sense code indicates the cause of the informational exception condition. The command that has the CHECK CONDITION is not executed before the informational exception condition is reported. Conditionally generate recovered error: This method instructs the drive to report informational exception conditions, if PER (Mode Page 1) is set to one, by returning a CHECK CONDITION status on any command.
  • Page 129: Mode Sense (10) (5Ah)

    8.9 MODE SENSE (10) (5Ah) Byte Command Code = 5Ah Reserved = 0 RSVD Reserved = 0 Page Code Subpage Code Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 104.
  • Page 130: Mode Select (6) (15H)

    8.10 MODE SELECT (6) (15h) Byte Command Code = 15h Reserved = 0 PF=1 Reserved = 0 Reserved = 0 Parameter List Length VU = 0 Reserved = 0 FLAG LINK Figure 105. MODE SELECT (6) The MODE SELECT (6) command provides a means for the initiator to specify LUN or device parameters to the drive.
  • Page 131: Mode Select (10) (55H)

    8.11 MODE SELECT (10) (55h) Byte Command Code = 55h Reserved = 0 PF=1 Reserved = 0 Reserved = 0 (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 106. MODE SELECT (10) The MODE SELECT (10) command provides a means for the initiator to specify LUN or device parameters to the drive.
  • Page 132: Persistent Reserve In (5Eh)

    8.12 PERSISTENT RESERVE IN (5Eh) Byte Command Code = 5Eh Reserved = 0 Service Action Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 107. PERSISTENT RESERVE IN When the drive receives a PERSISTENT RESERVATION IN command and RESERVE(6) or RESERVE(10) logical unit is active, the command is rejected with a RESERVATION CONFLICT status.
  • Page 133: Parameter Data For Read Keys

    8.12.2 Parameter data for Read Keys Byte (MSB) Generation (LSB) (MSB) Additional length (n-7) (LSB) (MSB) First reservation key (LSB) (MSB) Last reservation key (LSB) Figure 109. PERSISTENT RESERVE IN parameter data for Read Keys ! Generation is a counter which increments when PERSISTENT RESERVATION OUT command with “Register”...
  • Page 134: Parameter Data For Read Reservation Descriptor

    8.12.4 Parameter data for Read Reservation Descriptor Byte (MSB) Reservation key (LSB) (MSB) Scope-specific address (LSB) Reserved Scope Type (MSB) Extent length (LSB) Figure 111. PERSISTENT RESERVE IN Read Reservation Descriptor ! Scope-specific address is filled with 0. ! Scope and Type are described in PERSISTENT RESERVE OUT command section. ! Extent length is filled with 0.
  • Page 135: Persistent Reserve Out (5Fh)

    8.13 PERSISTENT RESERVE OUT (5Fh) Byte Command Code = 5Fh Reserved = 0 Service Action Scope Type Reserved = 0 (MSB) Parameter List Length = 18h (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 112. Persistent Reserve Out (5F) When a drive receives a PERSISTENT RESERVATION OUT command and RESERVE(6) or RESERVE(10) logical unit is active, the command is rejected with a RESERVATION CONFLICT status.
  • Page 136: Service Action

    8.13.1 Service Action The drive implements service action codes as follows. If a code which is not supported or a reserved code is specified, the drive returns a CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST and the additional sense data is set to INVALID FIELD IN CDB. In case of PERSISTENT RESERVATION OUT command executing a Register service action, this field is ignored.
  • Page 137 If the key specified in the Reservation key field is already registered but the initiator which registered the key is different from the initiator requesting the command, the drive returns RESERVATION CONFLICT status. If persistent reservation that is being attempted conflicts with persistent reservation that is held, the drive returns a RESERVATION CONFLICT status.
  • Page 138: Scope

    When PERSISTENT RESERVE OUT command with Register and Ignore Existing Key service action completes successfully, the Generation counter is incremented. When keys are registered, the drive returns RESERVATION CONFLICT status against the RESERVE command and the RELEASE command. 8.13.2 Scope The drive implements scope codes as follows.
  • Page 139: Figure 116. Conflict Between New And Existing Persistent Reservation

    READ (6) command and READ (10) command WRITE (6) command and WRITE (10) command Commands except the following: ! READ (6) command and READ (10) command ! WRITE (6) command and WRITE (10) command ! RESERVE and RELEASE command If any key is registered, the drive returns a RESERVATION CONFLICT status. ! PERSISTENT RESERVE IN command and PERSISTENT RESERVE OUT command SHared: The drive executes the command from all initiators.
  • Page 140: Parameter List

    8.13.4 Parameter list Byte (MSB) Reservation Key (LSB) (MSB) Service Action Reservation Key (LSB) (MSB) Scope-specific address (LSB) Reserved APTPL Reserved (MSB) Extent length (LSB) Figure 117. PERSISTENT RESERVATION OUT parameter list 8.13.5 Summary Parameters Gener- Service ation Scope SvcAct S-spec Extent Action...
  • Page 141: Figure 119. Aptpl And Information Held By A Drive

    8.13.5.3 Service Action Reservation Key On Register service action, the drive saves the key specified in the Service Action Reservation Key field as a key of initiator requesting PERSISTENT RESERVATION OUT command. On Preempt and Clear service action, the reservation which has a key specified in the Service Action Reservation Key field is preempted.
  • Page 142: Pre-Fetch (34H)

    8.14 PRE-FETCH (34h) Byte Command Code = 34h Immed RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 120. Pre-Fetch The PRE-FETCH command requests the drive to transfer data to the cache. No data is transferred to the initiator.
  • Page 143: Read (6) (08H)

    8.15 READ (6) (08h) Byte Command Code = 08h Reserved = 0 (MSB) Logical Block Address (LSB) Transfer Length VU = 0 Reserved = 0 FLAG LINK Figure 121. READ (6) The READ command requests the drive to transfer the specified number of blocks of data to the initiator starting at the specified logical block address.
  • Page 144: Read (10) (28H)

    8.16 READ (10) (28h) Byte Command Code = 28h RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 122. READ (10) The READ (10) command requests the drive to transfer data to the initiator.
  • Page 145: Read Buffer (Ach)

    8.17 READ BUFFER (ACH) Byte Command Code = 3Ch Reserved = 0 Mode Buffer ID = 0 (MSB) Buffer Offset (LSB) (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 123. READ BUFFER ! 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.
  • Page 146: Combined Header And Data (Mode 0000B)

    8.17.1 Combined Header And Data (Mode 0000b) In this mode a four byte header followed by data bytes are 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.
  • Page 147: Read Data From Echo Buffer (Mode 1010B)

    ! Allocation Length must be set to four or greater. The drive transfers the allocation length or four bytes of READ BUFFER descriptor, whichever is less. The READ BUFFER descriptor is defined in the figure below. Byte Offset Boundary (MSB) Buffer Capacity (LSB) Figure 125.
  • Page 148: Read Capacity (25H)

    8.18 READ CAPACITY (25h) Byte Command Code = 25h RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 127. READ CAPACITY The READ CAPACITY command returns information regarding the capacity of the drive. ! Logical Block Address is used in conjunction with the PMI bit.
  • Page 149: Figure 128. Format Of Read Capacity Command Reply

    8.18.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. Byte (MSB) Logical Block Address (LSB) (MSB) Block Length (LSB) Figure 128. Format of READ CAPACITY command reply Block Length specifies the length in bytes of the block.
  • Page 150: Read Defect Data (10) (37H)

    8.19 READ DEFECT DATA (10) (37h) Byte Command Code = 37h Reserved = 0 Reserved = 0 Reserved = 0 P-list G-List Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 129.
  • Page 151: Defect List Header

    8.19.1 Defect List Header Byte Defect List Header Rsvd = 0 Reserved = 0 P-list G-List Defect List Format (MSB) Defect List length (LSB) Figure 130. Defect List Header 8.19.2 Bytes from Index Format (100b) Byte Defect Descriptors (MSB) Cylinder Number of Defect (LSB) Head Number of Defect (MSB)
  • Page 152: Physical Sector Format (101B)

    8.19.3 Physical Sector Format (101b) Byte Defect Descriptors (MSB) Cylinder Number of Defect (LSB) Head Number of Defect (MSB) Defective Sector Number (LSB) Figure 132. Defect Descriptors of Physical Sector Format The Defect List Format field specifies the format of the defect list data returned by the drive. The Defect List Length field specifies the length in bytes of the defect descriptors that follow.
  • Page 153: Read Defect Data (12) (B7H)

    8.20 READ DEFECT DATA (12) (B7h) Byte Command Code = B7h Reserved = 0 P-list G-List Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 133. Read Defect Data (12) The READ DEFECT DATA command requests that the drive transfer the medium defect data to the initiator.
  • Page 154: Defect List Header

    8.20.1 Defect List Header Byte Defect List Header Rsvd = 0 Reserved = 0 P-list G-List Defect List Format Rsvd = 0 (MSB) Defect List length (LSB) Figure 134. Defect List Header 8.20.2 Bytes from Index Format (100b) Byte Defect Descriptors (MSB) Cylinder Number of Defect (LSB)
  • Page 155: Physical Sector Format (101B)

    8.20.3 Physical Sector Format (101b) Byte Defect Descriptors (MSB) Cylinder Number of Defect (LSB) Head Number of Defect (MSB) Defective Sector Number (LSB) Figure 136. Defect Descriptors of Physical Sector Format The Defect List Format field specifies the format of the defect list data returned by the drive. The Defect List Length field specifies the length in bytes of the defect descriptors that follow.
  • Page 156: Read Long (3Eh)

    8.21 READ LONG (3Eh) Byte Command Code = 3Eh CORT RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Byte Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 137. READ LONG The READ LONG command requests the drive to transfer one block of data to the initiator.
  • Page 157: Reassign Blocks (07H)

    8.22 REASSIGN BLOCKS (07h) Byte Command Code = 07h Reserved = 0 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 138. REASSIGN BLOCKS 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.
  • Page 158: Figure 139. Format Of Reassign Blocks Data

    Following is the format of the data sent by the initiator during the DATA OUT phase Byte RSVD = RSVD = (MSB) Defect list length = 4/8/12/16 (LSB) (MSB) Defect Logical Block Address –1 (LSB) (MSB) Defect Logical Block Address –2 (LSB) (MSB) Defect Logical Block Address –3...
  • Page 159: Receive Diagnostics Results (1Ch)

    8.23 RECEIVE DIAGNOSTICS RESULTS (1Ch) Byte Command Code = 1Ch Reserved = 0 Reserved = 0 Page Code (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 140. RECEIVE DIAGNOSTIC The RECEIVE DIAGNOSTIC RESULTS command requests that analysis data requested by a SEND DIAGNOSTICS command be sent to the initiator.
  • Page 160: Receive Diagnostic Results

    8.23.2 RECEIVE DIAGNOSTIC RESULTS Page 40 Using the SEND DIAGNOSTICS command, an address in either physical or logical format is supplied to the drive. This page is then used to retrieve the address translated into the other format. Byte Page Code = 40h Reserved = 0 Page Length = 0Ah Reserved =...
  • Page 161: Receive Diagnostic Results

    ! Translated Address contains the address in the translate format. If it is a logical block address, it is contained within the first four bytes of the field (bytes 6 to 9) of the page data. For a physical format it is as follows: Byte Cylinder Number...
  • Page 162: Release (6) (17H)

    8.24 RELEASE (6) (17h) Byte Command Code = 17h Reserved = 0 3rdPty 3rd Party ID Ext=0 Reservation Identification Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 145. RELEASE (6) The RELEASE command is used to release a LUN previously reserved. It is not an error for an Initiator to attempt to release a reservation that is not currently active.
  • Page 163: Release (10) (57H)

    8.25 RELEASE (10) (57h) Byte Command Code = 57h Ext = Reserved = 0 3rdPty Reserved = 0 Reservation Identification 3rd Party Device ID Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK...
  • Page 164: Report Device Identifier (A3H)

    8.26 REPORT DEVICE IDENTIFIER (A3h) Byte Command Code = A3h Reserved = 0 Service Action = 05h Reserved = 0 Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Allocation Length (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 147.
  • Page 165: Figure 148. Report Device Identifier Parameter List

    Byte (MSB) Identifier Length = n-3 (LSB) Identifier Figure 148. REPORT DEVICE IDENTIFIER parameter list The IDENTIFIER LENGTH field specifies the length in bytes of the IDENTIFIER field. If the ALLOCATION LENGTH field in the CDB is too small to transfer all of the identifier, the length is not adjusted to reflect the truncation.
  • Page 166: Report Lun (A0H)

    8.27 REPORT LUN (A0h) Byte Command Code = A0h Reserved (MSB) Allocation Length (LSB) Reserved VU = 0 Reserved = 0 FLAG LINK Figure 149. REPORT LUN The REPORT LUN command requests that the drive return the known Logical Unit Numbers (LUN) to the initiator.
  • Page 167: Request Sense (03H)

    8.28 REQUEST SENSE (03h) Byte Command Code = 03h Reserved = 0 Reserved = 0 Reserved = 0 Allocation Length VU = 0 Reserved = 0 FLAG LINK Figure 151. REQUEST SENSE The REQUEST SENSE command requests the drive to transfer sense data. The sense data shall be available under the following conditions: ! The previous command to the specified I_T_L nexus terminated with CHECK CONDITION status.
  • Page 168: Reserve (6) (16H)

    8.29 RESERVE (6) (16h) Byte Command Code = 16h Ext = Reserved = 0 3rdPty 3rd Party ID Reservation Identification (MSB) Extent List Length = 0 (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 152. RESERVE (6) The RESERVE command is used to reserve a LUN for an initiator. This reservation can be either for the initiator which sends this command or for the third party as specified by the Initiator.
  • Page 169: Reserve (10) (56H)

    8.30 RESERVE (10) (56h) Byte Command Code = 57h Ext = Reserved = 0 3rdPty Reserved Reservation Identification Third Party Device ID Reserved = 0 Reserved = 0 Reserved = 0 (MSB) Extent List Length = 0 (LSB) VU = 0 Reserved = 0 FLAG LINK...
  • Page 170: Rezero Unit (01H)

    8.31 REZERO UNIT (01h) Byte Command Code = 01h Reserved = 0 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 154. REZERO UNIT The REZERO UNIT command requests that the drive seek logical block address 0. Ultrastar 146Z10 hard disk drive specifications...
  • Page 171: Seek (6) (0Bh)

    8.32 SEEK (6) (0Bh) Byte Command Code = 0Bh Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 155. SEEK (6) The SEEK command requests the drive to seek the specified logical block address. Ultrastar 146Z10 hard disk drive specifications...
  • Page 172: Seek Extended (10) (2Bh)

    8.33 SEEK EXTENDED (10) (2Bh) Byte Command Code = 2Bh Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 156. SEEK (10) The SEEK (10) command requests the drive to seek the specified logical block address. Ultrastar 146Z10 hard disk drive specifications...
  • Page 173: Send Diagnostic (1Dh)

    8.34 SEND DIAGNOSTIC (1Dh) Byte Command Code = 1Dh Function Code RSVD=0 SlfTst Dev0fl Unt0fl Reserved = 0 (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 157. SEND DIAGNOSTIC 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.
  • Page 174: Figure 158. Send Diagnostic (1D)

    Value Function Name Description 000b 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 The drive starts its short self-test self-test routine in background mode.
  • Page 175: Send Diagnostic

    8.34.1 SEND DIAGNOSTIC Page 0 This page requests that the drive return a list of supported pages on the next RECEIVE DIAGNOSTICS RESULTS command. Byte Page Code = 0 Reserved = 0 2 - 3 Page Length = 0 Figure 159. Diagnostic Page 0 8.34.2 SEND DIAGNOSTIC Page 40 This allows the initiator to translate a logical block address or physical sector address to the other format.
  • Page 176: Send Diagnostic

    ! 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. Byte Cylinder Number Head Number...
  • Page 177: Set Device Identifier (A4H)

    8.35 SET DEVICE IDENTIFIER (A4h) Byte Command Code = A4h Reserved = 0 Service Action = 06h Reserved = 0 (MSB) Parameter List Length (LSB) Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 163. SET DEVICE IDENTIFIER The SET DEVICE IDENTIFIER command requests that the device identifier information be set to the value received in the SET DEVICE IDENTIFIER parameter list.
  • Page 178: Start Stop Unit (1Bh)

    8.36 START STOP Unit (1Bh) Byte Command Code = 1Bh Reserved = 0 Reserved = 0 Immed Reserved = 0 Reserved LoEj Power Conditions = 0 Start VU = 0 Reserved = 0 FLAG LINK Figure 165. START STOP Unit The START STOP UNIT command is used to spin up or stop the spindle motor.
  • Page 179: Synchronize Cache (35H)

    8.37 SYNCHRONIZE CACHE (35h) Byte Command Code = 35h Immed RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB Number of Blocks (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 166. SYNCHRONIZE CACHE The SYNCHRONIZE CACHE Command ensures that logical blocks in the cache have their most recent data value recorded on the media.
  • Page 180: Test Unit Ready (00H)

    8.38 TEST UNIT READY (00h) Byte Command Code = 00h Reserved = 0 Reserved = 0 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 167. TEST UNIT READY 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.
  • Page 181: Verify (2Fh)

    8.39 VERIFY (2Fh) Byte Command Code = 2Fh Byte RSVD= Reserved = 0 Rsvd = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 168. VERIFY 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.
  • Page 182: Write (6) (0Ah)

    8.40 WRITE (6) (0Ah) Byte Command Code = 0Ah Reserved = 0 (MSB) Logical Block Address (LSB) Transfer Length VU = 0 Reserved = 0 FLAG LINK Figure 169. WRITE (6) The WRITE command requests the drive to write the specified number of blocks of data from the initiator to the medium starting at the specified logical block address.
  • Page 183: Write (10) (2Ah)

    8.41 WRITE (10) (2Ah) Byte Command Code = 2Ah RelAdr Reserved = 0 Reserved (MSB) Logical Block Address (LSB) Reserved = 0 (MSB Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 170. WRITE (10) The WRITE (10) command requests that the drive write the data transferred from the initiator. This command is processed like the WRITE (6) command except for the longer transfer length ! Transfer Length The number of contiguous blocks to be transferred.
  • Page 184: Write And Verify (2Eh)

    8.42 WRITE AND VERIFY (2Eh) Byte Command Code = 2Eh Reserved Byte RelAdr Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 171. WRITE AND VERIFY 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.
  • Page 185: Write Buffer (3Bh)

    8.43 WRITE BUFFER (3Bh) Byte Command Code = 3Bh Reserved = 0 Mode Buffer ID (MSB) Buffer Offset (LSB) (MSB) Parameter List Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 172. WRITE BUFFER (3B) The WRITE BUFFER command is used in conjunction with the READ BUFFER command as a diagnostic function for testing the memory of the drive and the SCSI bus integrity.
  • Page 186: Combined Header And Data (Mode 0000B)

    8.43.1 Combined Header And Data (Mode 0000b) 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 com- mand is terminated with CHECK CONDITION status.
  • Page 187: Download Microcode (Mode 0100B)

    8.43.3 Download Microcode (Mode 0100b) In this mode the microcode is transferred to the control memory space of the drive. When it is down- loaded, 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.
  • Page 188: Download Microcode And Save (Mode 0111B)

    Buffer ID field is used to indicate which portion of the microcode image is being downloaded. The follow- ing Buffer IDs are supported by the drive: - 00h : Main Microprocessor Code with all others in one (Single Binary or Chunked) - 01h - 02h : Reserved - 80h - 82h : Reserved Any other value for the Buffer ID will cause the command to terminate with CHECK CONDITION status.
  • Page 189: Write Long (3Fh)

    8.44 WRITE LONG (3Fh) Byte Command Code = 3Fh RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Byte Transfer Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 174. WRITE LONG The WRITE LONG command requests the drive to write one block of data transferred from the initiator.
  • Page 190: Write Same (41H)

    8.45 WRITE SAME (41h) Byte Command Code = 41h RelAdr Reserved = 0 Reserved = 0 (MSB) Logical Block Address (LSB) Reserved = 0 (MSB) Number of Blocks (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 175. WRITE SAME (41) The Write Same command instructs the drive to write a single block of data transferred to the drive from the initiator to a number of sequential logical blocks.
  • Page 191: Scsi Status Byte

    9.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 (R) are set to zero. Reserved = 0 Status Code RSVD...
  • Page 192 QUEUE FULL This status indicates that the drive command queue is full. If a tagged command queuing feature is enabled and there is no room on the command queue, this status is returned when the initiator sends a command. For this status sense is not valid.
  • Page 193: Scsi Message System

    10.0 SCSI Message System This chapter describes how the message system is implemented on the drive. Included is a functional description of the supported messages. 10.1 Supported Messages The messages supported by the drive are listed in the figure below. Negate ATN MESSAGE CODE (hex)
  • Page 194: Task Complete (00H)

    If an unsupported message is received, the drive will send the MESSAGE REJECT message to the initi- ator. If at the time the unsupported message is received a valid nexus exists, the drive will continue with the command. If no valid nexus exists, the drive will go to BUS FREE. 10.1.1 TASK COMPLETE (00h) The drive sends this message to the initiator to indicate that the execution of a command has been termi- nated and that valid status has been sent to the initiator.
  • Page 195: Figure 179. Initiator Request/Drive Response (Lvd Mode)

    10.1.2.1 Synchronous Negotiation started by the Initiator When the drive responds with REQ/ACK offset value of 0, the initiator shall use asynchronous data transfer mode. LVD mode. The drive responds to each Initiator requested transfer period as shown below. Target Target Transfer Initiator Request Transfer Rate...
  • Page 196: Figure 181. Target Response To Initiator's Transfer Period (Lvd Mode)

    10.1.2.2 Synchronous Negotiation started by the drive If the drive recognizes that negotiation is required, it sends a SDR message to the initiator with minimum transfer period on the current receiver mode. The drive interprets the initiator corresponding transfer period as shown in the figure below. LVD mode Initiator Request Target Transfer Period (ns)
  • Page 197: Wide Data Transfer Request (010203H)

    10.1.3 WIDE DATA TRANSFER REQUEST (010203H) A pair of WIDE DATA TRANSFER REQUEST messages is exchanged between an initiator and a drive to establish a data transfer width agreement between the two devices. The initiator may initiate a wide data transfer negotiation at any time after the LUN has been identified.
  • Page 198: Figure 185. Target Request To Initiator

    transfer width agreement is reinstated if the drive successfully retransmits the WIDE DATA TRANSFER REQUEST message to the Initiator. For any other message the drive completes negotiation and goes to the negotiated data transfer width. 10.1.3.2 Transfer Width Negotiation started by the drive If the drive recognizes that negotiation is required, it sends a WIDE DATA TRANSFER REQUEST mes- sage to the Initiator with the transfer width exponent equal to 1 (E = 01h).
  • Page 199: Parallel Protocol Request (01,06,04H)

    10.1.4 PARALLEL PROTOCOL REQUEST (01,06,04H) Parallel Protocol Request messages are used to negotiate a synchronous data transfer agreement and a wide data transfer agreement and to set the protocol options between two SCSI devices. Byte Extended message = 01h Extended message length = 06h Parallel Protocol Request = 04h Transfer period factor Reserved = 00h...
  • Page 200: Figure 188. Initiator Request/Target Response

    If DT_REQ is set to one and IU_REQ is set to zero, the following values are used. Target Target Transfer Initiator Request Transfer Rate Response Period (ns) 0 <= Mi <= Mt = 09h 12.5 Fast-80 10 <= Mi <= Mt = 0Ah Fast-40 11 <= Mi <=...
  • Page 201: Save Data Pointer (02H)

    ! HOLD_MCS (Hold Margin Control Settings) is used to negotiate if any margin control settings which has been set with the margin control subpage of the port control mode page is retained. ! QAS_REQ (Quick Arbitration and Selection Enable Request) is used to negotiate if QAS is enabled. The drive supports QAS when IU_REQ is negotiated to be effective.
  • Page 202: Abort (06H)

    10.1.9 ABORT (06h) This message is sent from the initiator to direct the drive to clear the present operation for this initiator and logical unit including queued command(s). If a logical unit has been identified, then all pending data and status for the issuing initiator and this logical unit will be cleared and the drive will go to the BUS FREE phase.
  • Page 203: Linked Command Complete With Flag (0Bh)

    10.1.14 LINKED COMMAND COMPLETE WITH FLAG (0Bh) The drive sends this message to the initiator to indicate that the execution of a linked command with flag bit set to one has completed and that valid status has been sent to the initiator. After successfully sending this message, the drive goes to COMMAND phase to receive the next command.
  • Page 204: Ignore Wide Residue (2301H)

    10.1.18.2 HEAD OF QUEUE (21xxh) Commands with this tag should be inserted into the head of the queue. When a command is being executed, this tagged command will be inserted to the head of queue to be executed after the command being currently executed.
  • Page 205: Supported Message Functions

    10.2 Supported Message Functions The implementation of the supported messages will also include the following functions. ! Retry SCSI Command or STATUS phase The retry will be caused by the following error condition. - The drive detected SCSI bus parity error (COMMAND phase) - The drive receives INITIATOR DETECTED ERROR MESSAGE during or at the conclusion of an information transfer phase (Command Data Out or Status Phase) Note: The initiator may send the INITIATOR DETECTED ERROR message as a result of an initiator...
  • Page 206: Attention Condition

    10.3 Attention Condition The attention condition allows an initiator to inform the drive that a MESSAGE OUT phase is desired. The initiator may create the attention condition by asserting the ATN signal at any time except during the ARBITRATION or BUS FREE phases. The initiator must create the attention condition by asserting the ATN signal at least two deskew delays before releasing ACK for the last byte transferred in a bus phase to guarantee that the attention condition will be honored before transition to a new bus phase.
  • Page 207: Scsi Bus Related Error Handling Protocol

    10.4 SCSI Bus Related Error Handling Protocol This protocol is used to handle errors that threaten the integrity of a connection between the Target and an initiator. 10.4.1 Unexpected BUS FREE Phase Error Condition There are several error conditions that will cause the drive to immediately change to the BUS FREE phase regardless of the state of the ATN signal.
  • Page 208: Initiator Detected Error Message

    10.4.6 INITIATOR DETECTED ERROR Message An INITIATOR DETECTED ERROR message is valid after a COMMAND, DATA IN/OUT or STATUS phase has occurred. If another phase has occurred, the message is rejected. Depending on the model, the drive will optionally retry the previous phase if it is command or status. If this fails or the previous phase was a data transfer the drive will generate a CHECK CONDITION status and a Sense key of ABORTED COMMAND with additional sense code of INITIATOR DETECTED ERROR.
  • Page 209: Additional Information

    11.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. 11.1 SCSI Protocol There are various operating conditions that prevent the Target from executing a SCSI command. This section describes each of these operating conditions and their relative priority.
  • Page 210: Invalid Lun In Identify Message

    11.1.2 Invalid LUN in Identify Message There are three different circumstances defined within the SCSI protocol when the response to an invalid LUN will occur. Each of these result in a different response. 1.1.1 .1 Case 1 - Selection message sequence with Inquiry command The INQUIRY command is a special case in SCSI.
  • Page 211 ! the command is permitted to execute if the conditions to execute concurrently are met. (See Section 11.5, “Concurrent I/O Process.”) ! the command is added to the command queue for an I_T_L nexus under the following conditions: - no Queue Tag message was received during the connection which established the I/O process, - disconnection is allowed for the current I/O process - there is no queued I/O process or active I/O process corresponding to the I_T_L nexus for the current I/O process...
  • Page 212: Unit Attention Condition

    11.1.5 Unit Attention Condition The drive will generate a unit attention condition for each initiator under the following conditions: The drive has been reset. This includes Power On Reset, SCSI Bus Reset, and TARGET RESET message. The transceiver mode has been changed. The mode parameters in effect for this initiator have been changed by another initiator.
  • Page 213: Command Processing During Startup And Format Operations

    11.1.6 Command Processing During Startup and Format Operations If the drive receives a command from an Initiator while it is executing a startup or format operation, the response of the drive varies with the command as follows: INQUIRY The drive sends INQUIRY data and returns appropriate status. REPORT LUNS Same as above.
  • Page 214: Figure 192. Spindle Motor Degraded Mode - Disable Auto Start

    11.1.8 .1 Response to SCSI Command in Degraded Mode The following tables show the degraded mode status with acceptable commands and additional sense codes. Command (w/Option) Response Executed. The Target may return Sense Key REQUEST SENSE 020402h (NOT READY, INITIALIZE COMMAND REQUIRED) INQUIRY Executed...
  • Page 215: Figure 193. Spindle Motor Degraded Mode - Auto Start Delay/Spinning Up

    Command (w/Option) Response Executed. The drive may return Sense KCQ REQUEST SENSE 020401h (NOT READY, IN PROCESS OF BECOMING READY) INQUIRY Executed REPORT LUNS Executed Executed and CHECK CONDITION is returned TEST UNIT READY with Sense KCQ 020401h (NOT READY, IN PROCESS OF BECOMING READY) START STOP UNIT Executed...
  • Page 216: Figure 194. Spindle Motor Degraded Mode - Spindle Start Failure

    Command (w/Option) Response Executed. The drive may return Sense KCQ REQUEST SENSE 020400h (NOT READY, START SPINDLE MOTOR FAIL) INQUIRY Executed REPORT LUNS Executed Executed and CHECK CONDITION is returned TEST UNIT READY with Sense KCQ 020400h (NOT READY, START SPINDLE MOTOR FAIL) Executed START STOP UNIT...
  • Page 217: Figure 195. Spindle Motor Degraded Mode - Spindle Stopped By Start Stop Unit

    Command (w/Option) Response Executed. The drive may return Sense KCQ REQUEST SENSE 020402h (NOT READY, INITIALIZE COMMAND REQUIRED) INQUIRY Executed REPORT LUNS Executed Executed and CHECK CONDITION is returned TEST UNIT READY with Sense KCQ 020402h (NOT READY, INITIALIZE COMMAND REQUIRED) Executed START STOP UNIT - Success: Good status is returned.
  • Page 218: Figure 196. Self Configuration Failure Degraded Mode

    Command (w/Option) Response REQUEST SENSE Executed. The drive may return Sense KCQ 024085h (NOT READY, DIAG FAIL - BRING-UP FAIL) or Sense KCQ 024085h (NOT READY, DIAG FAIL - RAM CODE NOT LOADED) INQUIRY Executed REPORT LUNS Executed Executed and CHECK CONDITION is returned with Sense KCQ 024080h (NOT READY, DIAG TEST UNIT READY FAIL - BRING-UP FAIL) or Sense KCQ 024085h...
  • Page 219: Command Processing While Reserved

    Command (w/Option) Response Executed. The drive may return Sense KCQ 023100h (NOT READY, FORMAT CORRUPTED) or REQUEST SENSE Sense KCQ 033100h (MEDIUM ERROR, FORMAT CORRUPTED) REQUEST SENSE INQUIRY Executed REPORT LUNS Executed Executed and CHECK CONDITION is returned TEST UNIT READY with Sense Key 023100h (NOT READY, FORMAT CORRUPTED) Executed...
  • Page 220: Priority Commands

    3. If the issuing initiator is the one that made the reservation but is not the one to receive the reservation, ! A REQUEST SENSE, INQUIRY, REPORT LUNS, LOG SENSE, READ CAPACITY, REPORT DEVICE IDENTIFIER or START STOP UNIT with START bit is permitted. ! Any other command results in a RESERVATION CONFLICT Status 4.
  • Page 221: Queue Depth

    ! Commands which cause an OVERLAPPED COMMANDS ATTEMPTED error. See Section 11.1.3 , “Incorrect Initiator Connection" on page 194. 11.3.1 Queue depth Any initiator can queue at least one command at any time irrespective of the actions of any other initiators in the system.
  • Page 222: Command Reordering

    as untagged commands with a MESSAGE REJECT message being returned immediately after the queue tag is received by the drive. 11.4 Command reordering Command reordering function is supported under tagged command queuing enabled (DQue, Mode Page A, is set to zero). The reorder feature reorders READ/WRITE commands in order to minimize seek time between commands.
  • Page 223: Write Cache

    11.7 Write Cache If WCE (Mode Page 8) is set to one, 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.
  • Page 224: Segmented Caching

    11.9 Segmented Caching Segmented Caching divides the data buffer into several buffer segments. Size and number of segments are determined by Number of Cache Segments, Cache Segment Size, SIZE and LBCSS (Mode Page 8). Number of Segments can be 1 through 255. (256 segments can be used by specifying segment size.) The Read Ahead is a function that read data that the initiator has not yet requested to the buffer segment.
  • Page 225: Multiple Initiator Environment

    11.14 Multiple Initiator Environment 11.14.1 Initiator Sense Data Separate sense data is reserved for each I_T_L nexus and I_T_L_Q nexus. Each sense data is main- tained independent of commands from other initiators. 11.14.2 Initiator Mode Select/Mode Sense Parameters A single shared copy of the Mode Select/Mode Sense parameters is maintained by the drive. This includes both the current and saved parameters.
  • Page 226: Reset

    11.16 Reset The Reset condition is used to clear all SCSI devices from the bus. This condition takes precedence over all other phases and conditions. After a reset condition is detected and the reset actions are completed, the drive returns to a 'SCSI bus enabled' state that allows the drive to accept SCSI commands. This device uses the Hard reset option as defined in the SCSI-3 Parallel Interface Standard.
  • Page 227: Scsi Bus Reset And Target Reset Message

    11.16.3 SCSI Bus Reset and TARGET RESET Message These two reset conditions cause the following to be performed. ! If reset goes active while the power-up sequence is in progress, the power-up sequence is started over. ! If the Auto Spin up is enabled and the bring-up operation has not been completed, the bring-up operation will be re-attempted from the beginning.
  • Page 228: Diagnostics

    11.17 Diagnostics The drive will execute the bring-up operation at POR to assure the correct operation of the drive by validating components (ROM, RAM, Sector Buffer, EEPROM, HDC, Spindle Motor, Actuator), checking stored information in the reserved area and EEPROM, and verifying fault detects circuits. Self-test can be invoked by a SEND DIAGNOSTIC command.
  • Page 229: Figure 198. Self-Test Menu For Send Diagnostic Command

    drive will begin the first self-test segment. While the drive is performing a self-test in the background mode, it will terminate with a CHECK CONDITION status any SEND DIAGNOSTIC command it receives that meets either of the following criteria: a) The SlfTst bit is one b) The Function Code field contains a value other than 000b or 100b.
  • Page 230: Idle Time Function

    ! Drive ready check is to check the voltage status of 12V. ! RAM test is a read/write test for the whole area of sector buffer. ! Spin check is to check if the spindle motor is running at the correct speed. ! Write, Read and Compare test is a disk read/write test.
  • Page 231: Scsi Sense Data

    12.0 SCSI Sense Data 12.1 SCSI Sense Data Format Format of the sense data returned by the drive in response to the REQUEST SENSE command. Byte Valid Error Code (70h or 71h) RSVD = 0 Sense Key (MSB) Information Bytes (LSB) Additional Sense Length (MSB) Product Specific Information...
  • Page 232: Sense Data Description

    12.2 Sense Data Description 12.2.1 Valid (Bit 7 of byte 0) The Information Bytes (byte 3 through 6) are not defined. The Information Bytes (byte 3 through 6) contain a valid logical block address. 12.2.2 Error Code (Bit 6 - 0 of byte 0) Current Error.
  • Page 233: Information Bytes (Byte 3 Through 6)

    without altering the medium. If an invalid parameter is found in parameters supplied as data, the drive might have altered the medium. UNIT ATTENTION Indicates that the drive entered in the 'Unit Attention Condition'. (See Section 11.1.5 , “Unit Attention Condition” on page 196.) 7h-8h Not used Vendor Specific Not used...
  • Page 234: Additional Sense Code/Qualifier (Byte 12 And 13)

    12.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. Code Qual Description No error No sense. Predictive Failure Analysis threshold reached Recovered write error. No index Recovered no seek comp Recovered write error.
  • Page 235: Figure 201. Sense Key / Sense Code / Qualifier Combinations (2 Of 4)

    Code Qual Description Not ready. Start spindle motor fail. Not ready. In process of becoming ready. Not ready. Initializing command (START STOP UNIT command) required Not ready. Format in progress. Not ready. Self-test in progress. Not ready. Medium format corrupted. Diag Fall - Bring-Up failure or degraded mode.
  • Page 236: Figure 202. Sense Key / Sense Code / Qualifier Combinations (3 Of 4)

    Code Qual Description Illegal request. Parameter list length error. The number of parameters supplied is not equal to the value expected. Illegal request. Illegal command operation code. This command is also returned when an unsupported command code is received. Illegal request. Logical block address out of range. Illegal request.
  • Page 237: Figure 203. Sense Key / Sense Code / Qualifier Combinations (4 Of 4)

    Code Qual Description Aborted command. Message reject error. A message reject error occurs when an inappropriate or unexpected message reject is received from the initiator or the initiator rejects a message twice Aborted command. Buffer CRC Error in reading from buffer to host. Aborted command.
  • Page 238: Fru : Field Replaceable Unit (Byte 14)

    12.2.9 FRU : Field Replaceable Unit (Byte 14) The FRU (Field Replaceable Unit) field value will always be zero. 12.2.10 Sense Key Specific (Byte 15 through 17) The definition of this field is determined by the value of the sense key field. 12.2.10.1 Sense Key Specific - ILLEGAL REQUEST (Sense Key = 5h) Error field pointer is returned.
  • Page 239: Figure 205. Actual Retry Count

    12.2.10.2 Sense Key Specific - Recovered (Sense Key = 1h), HARDWARE ERROR (sense key = 4h) or MEDIUM ERROR (sense key = 3h) Actual Retry Count is reported. Byte SKSV Reserved (MSB) Actual Retry Count (LSB) Figure 205. Actual Retry Count SKSV Sense-key specific valid Actual ERP Retry Count is not valid.
  • Page 240: Vendor Unique Error Information (Byte 18 Through 19)

    12.2.11 Vendor Unique Error Information (Byte 18 through 19) This field gives detailed information about errors. Sense Data Description Byte 18 Continued servo unlocks, or servo ID can not be found during load/unload operation ADC calibration failure during load/unload operation AE failure Motor driver failure Seek time out...
  • Page 241: Vendor Unique Error Information (Byte 20 Through 23)

    12.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 (that is, Bring-up operation, Read/Write operation, or SMART Alert).
  • Page 242: Figure 210. Sense Data Byte 22 Por Error

    Sense Data Description Byte 22 Bit 7 Not used Bit 6 Not used Bit 5 Not used Bit 4 Not used Bit 3 Not Used Bit 2 Not Used Bit 1 Spindle Motor Spin-Up Failed Bit 0 EEPROM Data Validation Failed Figure 210.
  • Page 243: Figure 211. Sense Data Byte 23 For Por Error

    Sense Date Description Byte 23 HDC Test Failure Sector Buffer RAM Test Failure EEPROM Read Failure AE Write Failure Channel Calibration Failure Head Load Failure POR Only Fail Spin-Up Failure Reserved Area Table Failure RAM Code Read Failure RAM Code Signature Failure Overlay Code Read Failure Read-Only Table Read Failure Head Test Failure...
  • Page 244: Figure 212. Sense Data Byte 20 For Read/Write Error

    12.2.12.2 Read/Write Error (Sense Key 03h/04h) When an error occurs during a read or write operation, the Vendor Unique Error information will contain the HDC Registers (Status and Error). Sense Data Description (Status) Byte 20 Bit 7 Sector Count Over Bit 6 ECC Error on LBA Bit 5...
  • Page 245: Figure 214. Sense Data Byte 22 For Read/Write Error

    Sense Data Description (Status) Byte 22 Bit 7 not used Bit 6 not used Bit 5 not used Bit 4 not used Bit 3 not used Bit 2 Sector Pulse Missing Bit 1 Write Abort at ID Miss Sector Bit 0 Write Fault caused by Servo Figure 214.
  • Page 246: Physical Error Record (Byte 24 Thru 29)

    12.2.12.3 PFA Warning (Sense Code 5Dh) When PFA Warning occurs (Sense Code 5Dh), the Vendor Unique Error information byte 21 will contain the following reason code. Sense Data PFA Alert Reason Byte 21 Power On Hour Warning Thermal Sense Warning Spare Sector Availability Warning Read Error Rate exceeding the threshold Seek Error Rate exceeding the threshold...
  • Page 247: Index

    Index Acoustics, 43 ECC on the fly correction, 34 Actuator, 7 Electrical interface specification, 21 Altitude, 30 Electromagnetic compatibility, 45 Attention Condition, 190 Equipment errors, 34 Automatic Rewrite/Reallocate, 207 Equipment Status, 17 Auxiliary connector, 68-pin model, 25 Error recovery procedure, 17 Average latency, 14 Average seek time, 13 Failure prediction ( PFA / S.M.A.R.T.), 34...
  • Page 248 Mechanical specifications, 36 SCSI Message System, 177 Mounting, 39 SCSI Protocol, 193 Multiple Initiator Environment, 209 SCSI SENSE DATA, 215 SCSI signal connector - 68-pin, 22 SCSI Signal Connector - 80-pin, 23 SCSI Status Byte, 175 Non-arbitrating systems, 208 SCSI Status Byte Reporting, 193 Non-operating conditions, 30 Seek/ID miscompare errors, 34 Segmented Caching, 208...
  • Page 249 IBM representative. Data subject to change without notice. References in this publication to IBM products, programs, or ser- vices do not imply that IBM intends to make them available in all countries in which IBM operates. Document # S07N9742-03...

Table of Contents