Specifications

ManualsBrandsUltra Start ManualsAutomobile Alarm22xx

ibm

ibmibm

ibm

Hard disk drive specifications

Ultrastar 146Z10

3.5 inch SCSI hard disk drive

IC35L018UWDY10

IC35L018UCDY10

IC35L036UWDY10

IC35L036UCDY10

IC35L073UWDY10

IC35L073UCDY10

IC35L146UWDY10

IC35L146UCDY10

Models:

Revision 2.2 02 February 2002

S07N9742-03 Publication number 3630

IBM storage products

Summary of content (249 pages)

PAGE 1
IBM storage products ibm Hard disk drive specifications Ultrastar 146Z10 3.5 inch SCSI hard disk drive Models: IC35L018UWDY10 IC35L018UCDY10 IC35L036UWDY10 IC35L036UCDY10 IC35L073UWDY10 IC35L073UCDY10 IC35L146UWDY10 IC35L146UCDY10 Revision 2.
PAGE 2
This page intentionally left blank.
PAGE 3
IBM storage products ibm Hard disk drive specifications Ultrastar 146Z10 3.5 inch SCSI hard disk drive Models: IC35L018UWDY10 IC35L018UCDY10 IC35L036UWDY10 IC35L036UCDY10 IC35L073UWDY10 IC35L073UCDY10 IC35L146UWDY10 IC35L146UCDY10 Revision 2.
PAGE 4
1st Edition (Rev. 2.0) S07N9742-01 (31 January 2002) 2nd Edition (Rev. 2.1) S07N9742-02 (01 February 2002) 3rd Edition (Rev. 2.
PAGE 5
Table of contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix 1.0 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Glossary . . . . .
PAGE 6
7.5.2 Power supply current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.3 Ripple voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.4 Power consumption efficiency index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
8.7.9 Log Sense Page F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 8.7.10 Log Sense Page 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 8.7.11 Log Sense Page 2F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 8.8 MODE SENSE (6) (1A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
.23.2 Receive Diagnostic Results Page 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.23.3 Receive Diagnostic Results Page 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.24 RELEASE (6) (17h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.25 RELEASE (10) (57h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
10.1.18 QUEUE TAG MESSAGES (20xxh, 21xxh, 22xxh) . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.19 IGNORE WIDE RESIDUE (2301h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.20 IDENTIFY (80 - FFh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Supported Message Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 Attention Condition . . . . . .
PAGE 10
11.17.1 Power on Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.17.2 Self-test by Send Diagnostic Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.18 Idle Time Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.19 Information Unit Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Figures Figure 1. Formatted capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Figure 2. Data sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Figure 3. Product ID in Inquiry Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Figure 4. Block assignment of World Wide ID in Inquiry Command . . . . . .
PAGE 12
Figure 50. FORMAT UNIT (04h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Figure 51. Format of Defect List Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 52. Defect descriptor - Block format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Figure 53. Defect descriptor - Bytes from Index format. . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 13
Figure 104. MODE SENSE (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 105. MODE SELECT (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 106. MODE SELECT (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 107. Persistent Reserve In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
Figure 158. SEND DIAGNOSTIC (1D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 159. Diagnostic Page 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 160. Diagnostic Page 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 161. Address to translate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
Figure 211. Sense Data Byte 23 for POR Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 212. Sense Data Byte 20 for Read/Write Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 213. Sense Data Byte 21 for Read/Write Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 214. Sense Data Byte 22 for Read/Write Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 215.
PAGE 16
Ultrastar 146Z10 hard disk drive specifications xiv
PAGE 17
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) ! IC35L146UWDY10 (68 pin) ! IC35L146UCDY10 (80 pin) The specifications in this document are subject to change without notice. 1.
PAGE 18
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.
PAGE 19
2.0 Outline of the drive ! Storage capacities of 146.8 GB, 73.4 GB, 36.7 GB, and 18.3 GB ! Ultra 320 and Ultra 160 ! Interleave factor 1:1 ! Variable Sector Size (512-528 bytes/sector) ! Tagged Command Queuing support ! Automatic read/write data transfer ! 8 MB segmented sector buffer (from 1 through 256) ! 4.
PAGE 20
This page intentionally left blank.
PAGE 21
Part 1.
PAGE 22
This page intentionally left blank.
PAGE 23
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. ! Analyze servo signals to provide closed loop control.
PAGE 24
This page intentionally left blank.
PAGE 25
4.0 Drive characteristics 4.1 Formatted capacity Description Label capacity Number of heads Number of disks Total data bytes (512 bytes/sector) Total logical data blocks IC35L146UWDY10 IC35L073UWDY10 IC35L146UCDY10 IC35L073UCDY10 146.8 GB 12 6 146,815,800,320 286,749,610 (111773AAh) 73.4 GB 6 3 IC35L036UWDY10 IC35L036UCDY10 36.7 GB 3 2 18.35 GB 2 1 73,407,900,160 36,703,918,080 18,351,959,040 143,374,805 (88BB9D5h 71,687,340 (445DCACh) 35,843,670 (222EE56h) Figure 1. Formatted capacity 4.
PAGE 26
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 IC35L018UWDY10-0 IC35L018UCDY10-0 IC35L036UWDY10-0 IC35L036UCDY10-0 IC35L073UWDY10-0 IC35L073UCDY10-0 IC35L146UWDY10-0 IC35L146UCDY10-0 Description 18.3 GB, 68 pin 18.3 GB, 80 pin 36.7 GB, 68 pin 36.7 GB, 80 pin 73.4 GB, 68 pin 73.4 GB, 80 pin 146.8 GB, 68 pin 146.8 GB, 80 pin Figure 3. Product ID in Inquiry Command 4.3.
PAGE 27
4.
PAGE 28
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 contribute to the performance of the actual system.
PAGE 29
4.5.2 Mechanical positioning 4.5.2.1 Average seek time (including settling) Command Type 146 GB model all other models 146 GB model all other models Read Write Typical (ms) 4.7 4.7 5.9 5.3 Max (ms) 5.9 5.7 6.9 6.9 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
4.5.2.3 Cylinder switch time (cylinder skew) Typical (ms) 0.70 Cylinder skew 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) 0.63 Head skew Figure 10.
PAGE 31
4.5.5 Data transfer speed Description Disk-Buffer Transfer (Zone 0) Instantaneous Typical (Mbyte/s) Sustained Disk-Buffer Transfer (Zone 16) Instantaneous Sustained All models 146-GB Model 73-GB Model 36-GB Model 18-GB Model 73.7 66.7 66.6 66.4 66.2 All models 146-GB Model 73-GB Model 36-GB Model 18-GB Model 37.5 33.9 33.9 33.8 45.9 Buffer-Host 68/80pin Ultra 320 320 Figure 14.
PAGE 32
4.5.7 Throughput 4.5.7.1 Simple sequential access Operation Sequential read/write Typical (ms) Zone 0 <260 Zone 14 <510 Max (ms) Zone 0 <290 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. Typical and Max values are given by 100% and 110% of T respectively throughput the following performance description.
PAGE 33
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. To prevent this data loss at power off, the following action is recommended: ! Confirm successful completion of SYNCHRONIZE CACHE (35h) command. 5.
PAGE 34
This page intentionally left blank.
PAGE 35
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
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. 4 3 2 1 Pin 1 2 3 4 Voltage +12 V GND GND +5V 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” SPI-3 document, Annex C.
PAGE 38
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.
PAGE 39
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 number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Signal name 12 Volt Charge 12 Volt 12 Volt 12 Volt Opt 3.3 V/NC Opt 3.
PAGE 40
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. This function can be selected by jumper. The 80-pin SCA-2 models do not support SCSI bus termination power. 7.1.
PAGE 41
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
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. These controls work as logical OR between the Option Jumper Block and the Auxiliary Connector.
PAGE 43
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. If a jumper is installed, the drive will not spin up unless a START UNIT command is received. 7.2.1.
PAGE 44
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. If this jumper is installed, SSM bit is ignored. 7.2.1.
PAGE 45
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
7.3 Environment Operating conditions Temperature Relative Humidity Maximum Wet Bulb Temperature Maximum Temperature Gradient Altitude Non-operating conditions Temperature Relative Humidity Maximum Wet Bulb Temperature Maximum Temperature Gradient Altitude 5 to 55°C (See note) 8 to 90%, non-condensing 29.4°C, non-condensing 15°C/Hour –300 to 3048 m –40 to 65°C 5 to 95%, non-condensing 35°C, non-condensing 15°C/Hour –300 to 12,000 m Figure 26.
PAGE 47
7.4 Cooling requirements Drive component temperatures must remain within the limits specified in the following table. Maximum component temperature ratings must not be exceeded under any operating condition. The drive may require forced air cooling to meet specified operating temperatures. Module name Location MPU + HDC integration module DRAM VCM + Spindle Driver Channel module 1 2 3 4 Maximum allowable surface temperature 95°C 95°C 95°C 95°C Figure 28.
PAGE 48
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. 7.5.1 Input voltage +5 volts supply +12 volts supply During run and spin up 5 V ± 5% 12 V ± 5% * Absolute max spike voltage 5.
PAGE 49
36-GB models (All values in Amps.) Idle Average Idle ripple (peak-to-peak) Seek average Seek peak Start up (max) Random R/W peak Random R/W average +5 Volts Pop Mean 0.50 0.22 0.55 0.91 1.07 1.40 0.66 +5 Volts Std. Dev 0.02 0.02 0.02 0.05 0.03 0.10 0.02 +12 Volts Pop Mean 0.37 0.40 0.86 2.12 2.12 2.12 0.73 +12 Volts Std. Dev 0.03 0.10 0.03 0.10 0.13 0.10 0.03 +5 Volts Std. Dev 0.02 0.02 0.02 0.05 0.03 0.10 0.02 +12 Volts Pop Mean 0.28 0.40 0.77 1.96 1.98 1.98 0.64 +12 Volts Std. Dev 0.03 0.10 0.03 0.
PAGE 50
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 1x1016 bits read.
PAGE 51
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). The drive temperature can be detected by Log Sense Page 2F. Refer to Section 8.7.11 on page 79.
PAGE 52
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.
PAGE 53
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] Width [mm] Length [mm] Weight [grams - maximum] 25.4 ± 0.4 101.6 ± 0.4 146.0 ± 0.6 780 Figure 39. Physical dimensions 101.6 +/- 0.4 BREATHER HOLE (*) LEFT FRONT 146 +/- 0.6 25.4 +/- 0.4 * DO NOT BLOCK THE BREATHER HOLE Figure 40.
PAGE 54
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 2 ± 0 .1 T Y P Pin 1 Pin 68 4.5 ± 0.5 10.4 ± 0.5 32.5 ± 0.5 5.08 ± 0.1 2 ± 0.1 TYP Figure 40. Interface connector for 68-pin models 7.7.3.2 80-pin model Pin 41 4.6 ± 0.7 Pin 1 Figure 41.
PAGE 55
7.7.4 Mounting positions and tappings (2X) 41.28 +/- 0.5 (2X) 44.45 +/- 0.2 (4X) 6-32 UNC 2 (2X) 28.5 +/- 0.5 (2X) 41.6 +/- 0.2 (2X) 60 +/- 0.2 (6X) 6-32 UNC 1 (6X) 6.35 +/- 0.2 RIGHT (2X) 95.25 +/- 0.2 REAR RECOMMENDED TORQUE 0.6 - 1.0 Nm 1 MAX ALLOWABLE PENETRATION OF NOTED SCREW TO BE 4.5 mm . 2 MAX ALLOWABLE PENETRATION OF NOTED SCREW TO BE 4.0 mm . SCREW 6-32 UNC THICKNESS OF BRACKET 1 2 Figure 42.
PAGE 56
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. 7.7.6 Breather hole The breather hole must be kept clear and unobstructed at all times.
PAGE 57
7.8 Vibration and shock All vibration and shock measurements in this section are made with a drive that has no mounting attachments for the systems. The input power for the measurements is applied to the normal drive mounting points. 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
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.
PAGE 59
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. Model A-weighted sound power level (Bel) Typical Maximum 3.7 4.1 4.5 4.8 3.4 3.8 4.5 4.8 Mode 146 GB all other models Idle Operating Idle Operating Figure 46.
PAGE 60
7.10 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.
PAGE 61
7.11 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.
PAGE 62
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. The UL and C-UL recognition mark, or CSA monogram for CSA certification, appears on the drive. 7.12.
PAGE 63
Part 2.
PAGE 64
This page intentionally left blank.
PAGE 65
8.0 SCSI Command Set Summaries of the SCSI commands supported by the drive are listed below. O = optional, M = mandatory.
PAGE 66
8.1 SCSI Control Byte The Control Byte is the last byte of every CDB. The format of this byte is shown below. Bit 7 6 5 VU = 0 4 3 2 Reserved = 0 1 FLAG 0 LINK Figure 49. SCSI Control Byte VU 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. If Link is zero, Flag must also be zero.
PAGE 67
8.4 FORMAT UNIT (04h) Bit Byte 7 6 0 1 5 4 5 2 1 0 Command Code = 04h FmtData CmpList Defect List Format Reserved 2 3 4 3 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. (Reserved areas of the media are not affected by the FORMAT UNIT command.
PAGE 68
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. Bit Byte 7 6 5 4 0 3 2 1 0 Reserved = 0 1 FOV 2 3 (MSB) DPRY DCRT STPF=1 IP = 0 DSP= 0 Immed 0 Defect List Length (LSB) Figure 51. Format of Defect List Header The drive has a limited implementation of the Format Option bits located in Bits 2 through 7 of Byte 1 of the Defect List Header (See Figure 48).
PAGE 69
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. The drive saves all the MODE SELECT savable parameters during the format operation.
PAGE 70
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. Bit Byte 7 0 1 2 6 4 3 2 1 0 (MSB) Cylinder Number of Defect (LSB) 3 4 5 6 7 5 Head Number of Defect (MSB) Defect Bytes from Index (LSB) 8n 8n +7 Defect Descriptor n Figure 53.
PAGE 71
8.5 INQUIRY (12h) Bit Byte 7 6 0 1 5 4 3 2 0 Command Code = 12h Reserved Reserved = 0 2 Page Code 3 Reserved = 0 4 Allocation Length 5 1 VU =0 Reserved = 0 CmdDt EVPD 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
CmdDt EVPD PAGE CODE Description 0 0 0 The drive returns the standard INQUIRY data. 0 0 Non Zero The drive returns CHECK CONDITION status with the sense key of ILLEGAL REQUEST and the additional sense code of INVALID FIELD IN CDB. 0 1 Supported The drive returns the vital product data of page code requested.
PAGE 73
8.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 or EBCDIC as stated. 8.5.1.
PAGE 74
! ISO is set to zero to indicate that this drive does not claim compliance to the International Organization for Standardization (ISO) version of SCSI (ISO DP 9316). ! ECMA is set to zero to indicate that this drive does not claim compliance to the European Computer Manufacturers Association (ECMA) version of SCSI (ECMA-111). ! ANSI indicates the level of the ANSI standard that is supported by the drive. The drive supports ANSI SCSI version 3.
PAGE 75
8.5.1.2 Inquiry data format - CmdDt = 1 Bit Byte 7 0 1 6 5 4 Peripheral Qualifier 3 1 0 Peripheral Device Type Reserved Support 2 Version 3 Reserved 4 Reserved 5 CDB Size = m-5 6 2 CDB Usage Data m Figure 58. Command support data format ! Peripheral Qualifier is set to zero to indicate that the LUN specified in the IDENTIFY Message is currently supported. Peripheral Qualifier is set to 011b when the LUN specified in the IDENTIFY Message is not present.
PAGE 76
Support Description 000b Data about the requested SCSI operation code is not currently available. 001b The drive does not support the tested SCSI operation code. All data after byte 1 is undefined. 010b Reserved. 011b The drive supports the tested SCSI operation code in conformance with the SCSI standard. 100b Vendor-specific 101b The drive supports the tested SCSI operation code in a vendor-specific manner. 110b Vendor-specific 111b Reserved Figure 59.
PAGE 77
8.5.1.3 Inquiry data format - EVPD = 1 - Page Code = 00 Bit Byte 7 0 6 5 Qualifier = 0 4 3 2 1 0 Peripheral Device Type = 0 1 Page Code = 00h 2 Reserved = 0 3 Page Length = 03h 4 Supported Page Code = 00h 5 Supported Page Code = 80h 6 Supported Page Code = 83h Figure 60. INQUIRY DATA - EVPD = 1 (Page Code = 00) ! Qualifier is set to zero to indicate that the LUN specified in the Command Block is currently supported.
PAGE 78
8.5.1.4 Inquiry data format - EVPD = 1 - Page Code = 80h Bit Byte 7 0 6 5 Qualifier = 0 4 3 1 0 Peripheral Device Type = 0 1 Page Code = 80h 2 Reserved = 0 3 Page Length = 16 (10h) 4-19 2 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. ! Peripheral Device Type is set to zero to indicate that the device is Direct Access.
PAGE 79
8.5.1.5 Inquiry data format - EVPD = 1 - Page Code = 83h Bit Byte 7 0 6 5 Qualifier = 0 4 3 2 Page Code = 83h 2 Reserved = 0 3 Page Length = 12 (0Ch) Reserved = 0 Reserved = 0 5 Code Set = 1 Association = 0 Identifier Type = 3 6 Reserved = 0 7 Identifier Length = 8 8-15 (MSB) 0 Peripheral Device Type = 0 1 4 1 World Wide ID (LSB) Figure 62.
PAGE 80
8.6 LOG SELECT (4Ch) Bit Byte 7 6 0 1 2 4 3 2 1 0 PCR SP Command Code = 4Ch Reserved = 0 PC 3 4 5 6 7 8 5 Reserved = 0 Reserved = 0 Reserved = 0 (MSB) 9 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
8.7 LOG SENSE (4Dh) Bit Byte 7 6 5 0 1 2 4 3 2 1 0 Command Code = 4Dh Reserved = 0 Reserved = 0 PC 3 4 PPC= 0 SP Page Code Reserved = 0 5 6 (MSB) 7 8 (MSB) Parameter Pointer (LSB) 9 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
8.7.1 Log Page parameters Each log page begins with a four-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 four-byte parameter header followed by one or more bytes of parameter value data.
PAGE 83
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.
PAGE 84
8.7.3 Log Sense Page 2 This page contains counters for write errors.
PAGE 85
Bit Byte 7 6 64-65 66 5 4 3 2 0 LBIN = 0 LP = 0 Parameter Code = 05h DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 67 Parameter Length = 08h 68-75 Total bytes written 76-77 Parameter Code = 06h 78 1 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 79 Parameter Length = 08h 80-87 Total number of hard errors LBIN = 0 Figure 67.
PAGE 86
8.7.4 Log Sense Page 3 This page contains counters for read errors.
PAGE 87
Bit Byte 66 7 6 5 4 DU = 0 DS = 0 TSD = 0 ETC = 0 3 2 TMC = 0 67 Parameter Length = 08h 68-75 Total bytes read 76-77 Parameter Code = 06h 78 DU = 0 DS = 0 TSD = 0 ETC = 0 TMC = 0 79 Parameter Length = 08h 80-87 Total number of hard errors 1 0 LBIN = 0 LP = 0 LBIN = 0 LP = 0 Figure 69.
PAGE 88
8.7.5 Log Sense Page 5 This page contains counters for VERIFY command and the verify portion of WRITE AND VERIFY command.
PAGE 89
Bit Byte 66 7 6 5 4 3 DU = 0 DS = 0 TSD = 0 ETC = 0 2 TMC = 0 67 Parameter Length = 08h 68-75 Total Bytes Verified 76-77 Parameter Code = 06h 78 DU = 0 DS = 0 TSD = 0 TMC = 0 79 Parameter Length = 08h 80-87 Total number of hard errors 1 0 LBIN = 0 LP= 0 LBIN = 0 LP = 0 Figure 71. Log Sense Page 5 (part 2 0f 2) 8.7.6 Log Sense Page 6 This page contains counters for seek errors.
PAGE 90
8.7.7 Log Sense Page D This page contains temperature information.
PAGE 91
8.7.8 Log Sense Page E This page contains the start-stop cycle information.
PAGE 92
8.7.9 Log Sense Page F This page contains the Application Client Log. Bit Byte 7 0 6 5 4 Reserved 3 2 1 0 Page code = 0Fh 1 Reserved 2-3 Page length = 4000h Application client log parameter 4- First application client log parameter -4003h Last application client log parameter The following table describes the application client log parameter structure.
PAGE 93
8.7.10 Log Sense Page 10 This page contains Self-test results. Bit Byte 7 0 6 5 4 Reserved 3 2 1 0 Page code = 10h 1 Reserved 2-3 PageLength = 190h Self-test results log parameters 4- 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
Value Description 0h The self-test routine completed without error 1h The background self-test routine was aborted by the initiator using a SEND DIAGNOSTICS command with the Abort Background self-test function 2h The self-test routine was aborted by the application client by a Task Management function of a reset 3h An unknown error occurred while the drive was executing the self-test routine and the drive was unable to complete the self-test routine 4h The self-test completed with a test element
PAGE 95
Extended Segment Number Foreground Test Background Test 0h NA NA 1h Drive ready check Drive ready check 2h RAM test NA 3h Spin check Spin check 4h Write, read and compare test Write, read and compare test 5h ECC circuit test ECC circuit test 6h Seek test Seek test 7h SMART check SMART check 8h Low level format check Low level format check 9h Physical head test Physical head test Ah Read scan test Read scan test Bh SMART check SMART check Figure 78.
PAGE 96
8.8 MODE SENSE (6) (1A) Bit Byte 7 6 0 5 4 3 1 0 Command Code = 1Ah 1 Reserved 2 PCF RSVD DBD Subpage Code 4 Allocation Length VU = 0 Reserved = 0 Page Code 3 5 2 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. It is the complement to the MODE SELECT command. If the DBD (Disable Block Descriptor) bit is zero, the drive will return the Block Descriptor.
PAGE 97
11 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 Code: This field specifies which page or pages to return. Page code usage is defined in the figure below.
PAGE 98
Mode parameter header (10) Bit Byte 7 0 1 (MSB) 4 3 2 1 0 Mode Data Length Medium Type = 0 WP 4 5 6 7 5 (LSB) 2 3 6 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. The mode data length does not include the length byte itself.
PAGE 99
8.8.1.2 Block Descriptor Byte Byte Byte Byte 0 1 2 3 Number of Blocks (MSB) (LSB) Byte 4 Density code = 0 Byte 5 Byte 6 Byte 7 Block Length 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
8.8.1.3 Page Descriptor Byte 0 PS RSVD= 0 Byte 1 Page Code Page Length Byte 2-n 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. A PS bit of zero indicates that the supported parameters cannot be saved.
PAGE 101
8.8.
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. When it is set to one, it will cause a SAVE DATA POINTER message to be sent on every disconnection.
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 temperature. A value of 0 selects the default value (85 degrees Celsius).
PAGE 104
8.8.3 Mode Page 1 (Read/Write Error Recovery Parameters) Bit Byte Default 7 0 PS 1 2 6 5 4 RSVD=0 3 2 1 0 Page Code = 01h 81h Page Length = 0Ah AWRE ARRE TB RC 0Ah EER=0 PER DTE DCR C0h 3 Read Retry Count 01h 4 Correction Span (Ignored) 00h 5 Head Offset Count (Ignored) 00h 6 Data Strobe Offset Count 00h 7 Reserved 00h 8 Write Retry Count 01h 9 Reserved 00h 10 (Ignored) (MSB) 00h Recovery Time Limit 11 (LSB) 00h Figure 88.
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. A DCR of zero indicates that the off-line ECC correction is used. ! Read Retry Count sets a limit on the ERP steps in which the drive attempts to recover read errors.
PAGE 106
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 and/or corrected data (if any) are transferred with no CHECK CONDITION status at the end of the transfer. no err The transfer length is exhausted. soft err The transfer length is exhausted.
PAGE 107
1 0/1 0 0 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. soft err The transfer length is exhausted. Transferred data includes blocks containing recovered errors.
PAGE 108
8.8.4 Mode Page 2 (Disconnect/Reconnect Parameters) Bit Byte Default 7 0 PS 6 RSVD=0 5 4 3 2 1 0 Page Code = 02h 82h 1 Page Length = 0Eh 0Eh 2 Read Buffer Full Ratio 00h 3 Write Buffer Empty Ratio 00h 4-5 6-7 8-9 10-11 12 13-15 (MSB) (MSB) (MSB) (MSB) Bus Inactivity Limit = 0 (LSB) 00h 00h (LSB) 00h 00h (LSB) 00h 00h (LSB) 00h 00h Disconnect Time Limit = 0 Connect Time Limit = 0 Maximum Burst Size Fair arbitration DIMM RSVD DTDC Reserved = 0 70h 00h 00h 00h Figure 89.
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. Note: Priority commands do not disconnect from the SCSI bus.
PAGE 110
8.8.
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 ! Sectors per Track specifies the number of physical sectors within each track.
PAGE 112
8.8.
PAGE 113
8.8.7 Mode Page 7 (Verify Error Recovery Parameters) Bit Byte Default 7 0 PS 6 5 RSVD=0 4 3 2 1 0 Page Code = 07h 87h 1 Page Length = 0Ah 2 Reserved 3 Verify Retry Count 01h 4 Correction Span (Ignored) 00h 5 Reserved 00h 6 Reserved 00h 7 Reserved 00h 8 Reserved 00h 9 Reserved 00h 10 0Ah EER=0 PER DTE=0 DCR 00h 00h (MSB) Verify Recovery Time Limit (LSB) 11 00h Figure 92.
PAGE 114
! 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. 8.8.
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. ! MF (Multiplication Factor) is ignored.
PAGE 116
8.8.9 Mode Page A (Control Mode Page Parameters) Bit Byte Default 7 0 PS 6 3 4 8-9 10-11 3 2 1 0 Page Code = 0Ah 8Ah Page Length = 0Ah TST=000b Reserved Queue Algorithm Modifier EECA=0 RSVD=0 Reserved = 0 5 6-7 4 RSVD=0 1 2 5 0Ah GLSTD=0 RLEC=0 QErr RAENP = 0 DQue 00h UAAENP EAENP = 0 = 0 00h Reserved = 0 (MSB) 00h Ready AEN Holdoff Period (LSB) (MSB) Busy Timeout Period (LSB) (MSB) 00h Extended Self-test Routine Completion Time (LSB) 00h 00h --- Figure 94.
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. The sense key will be set to UNIT ATTENTION and the additional sense code will be set to COMMANDS CLEARED BY ANOTHER INITIATOR.
PAGE 118
8.8.10 Mode Page 0C (Notch Parameters) Bit Byte 7 0 PS = 1 1 2 ND = 1 RSVD= 0 4 3 2 1 0 Page Code = 0Ch LPN = 0 RSVD = 0 Reserved = 0 (MSB) Maximum Number of Notches = 011h (LSB) 5 6 5 Page Length = 16h 3 4 6 (MSB) Active Notch 7 (LSB) 8 | 11 (MSB) 12 | 15 (MSB) 16 | 23 (MSB) Starting Boundary (LSB) Ending Boundary (LSB) Pages Notched = 000000000000100Ch (LSB) Figure 95. Page 0C (Notch Parameters) The notch page contains parameters for variable number of blocks per cylinder.
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. 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.
PAGE 120
8.8.11 Mode Page 19 (Port Control) 8.8.11.1 Short Format of Port Control Page Bit Byte Default 7 0 PS 6 5 4 Long=0 3 2 1 0 Page Code = 019h 99h 1 Page Length = 06h 06h 2 Reserved 00h 3 Reserved 4 | 5 Protocol identifier = 1 (MSB) Synchronous transfer timeout (LSB) 01h 00h | 00h 6 Reserved 00h 7 Reserved 00h 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
8.8.11.2 Long Format of Port Control Page Bit Byte Default 7 0 PS 6 5 4 Long=1 6 1 0 39h Subpage code (MSB) Page Length (n–3) (LSB) 4 5 2 Page Code = 019h 1 2 | 3 3 Reserved Reserved Protocol identifier = 1h 00h | 00h 00h 01h Protocol Specific Mode Parameters n 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. ! Subpage Code indicates which subpage is being accessed.
PAGE 122
8.8.11.3 Margin Control Subpage Bit Byte 7 6 5 0 4 3 2 1 0 RSVD 1 Driver Strength Reserved 2 Driver Asymmetry Driver Precompensation 3 Driver Slew Rate Reserved 4 | 6 Reserved 7 Vendor specific 8 | 15 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
8.8.11.4 Saved Training Configuration Values Subpage Bit Byte 7 6 5 4 0-3 RSVD 4-7 DB (0) Value 64-67 DB (15) Value 68-71 P_CRCA Value 72-75 P1 Value 76-79 BSY Value 80-83 SEL Value 84-87 RST Value 88-91 REQ Value 92-95 ACK Value 96-99 ATN Value 100-103 C/D Value 104-107 I/O Value 108-111 MSG Value 112-227 RSVD 3 2 1 0 Figure 99.
PAGE 124
8.8.11.5 Negotiated Settings Subpage Bit Byte 7 6 5 4 3 0 Transfer Period Factor 1 Reserved 2 REQ/ACK Offset 3 Transfer Width Exponent 4 RSVD 2 1 0 1 2 Protocol Options Bits 5 RSVD 6 Reserved 7 Reserved Transceiver Mode 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
8.8.11.6 Report Transfer Capabilities Subpage Bit Byte 7 6 5 4 3 2 0 Minimum Transfer Period Factor 1 Reserved 2 Maximum REQ/ACK Offset 3 Maximum Transfer Width 4 Protocol Options Bits Supported 5-7 1 0 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
8.8.12 Mode Page 1A (Power Control Parameters) Bit Byte 7 0 RSVD 6 5 RSVD Page Length = 0Ah 2 Reserved 3 Reserved (MSB) 8 | 11 (MSB) 3 2 1 0 Page Code = 1Ah 1 4 | 7 4 [Idle] Standby Idle Condition Timer (LSB) 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
8.8.13 Mode Page 1C (Informational Exceptions Control) BIT Default Byte 7 0 6 PS 5 RSVD=0 3 2 1 0 Page Code = 1Ch 1 2 4 9Ch Page Length = 0Ah [PERF] 3 4 RSVD [EBF] EWASC DEXCPT Reserved 0Ah TEST RSVD [LOGERR] Method of Reporting 00h 00h 00h (MSB) 5 00h Interval Timer 6 00h (LSB) 7 8 00h 00h (MSB) 9 00h Report Count 10 00h (LSB) 11 00h 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. 3h 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
8.9 MODE SENSE (10) (5Ah) Bit Byte 7 6 0 1 2 5 4 3 Reserved = 0 PCF RSVD DBD 0 4 Reserved = 0 5 Reserved = 0 6 Reserved = 0 (MSB) Reserved = 0 Page Code Subpage Code 9 1 Command Code = 5Ah 3 7-8 2 Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 104. MODE SENSE (10) The MODE SENSE (10) command provides a means for the drive to report various device parameters to the initiator. See Section 8.
PAGE 130
8.10 MODE SELECT (6) (15h) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 15h 1 Reserved = 0 PF=1 Reserved = 0 2 3 Reserved = 0 4 Parameter List Length 9 VU = 0 Reserved = 0 SP 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. It also allows an Initiator to specify options the drive uses in error recovery and caching. There is a single set of Mode Page parameters shared by all initiators.
PAGE 131
8.11 MODE SELECT (10) (55h) Bit Byte 7 6 5 0 1 9 3 2 1 0 Command Code = 55h Reserved = 0 PF=1 2 | 6 7 8 4 Reserved = 0 SP 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. See the MODE SELECT (6) command for a description of the fields in this command.
PAGE 132
8.12 PERSISTENT RESERVE IN (5Eh) Bit Byte 7 6 5 0 1 4 2 1 0 Command Code = 5Eh Reserved = 0 Service Action 2 | 6 7 8 3 Reserved = 0 (MSB) 9 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
8.12.2 Parameter data for Read Keys Bit Byte 7 0 | 3 (MSB) 4 | 7 (MSB) 8 | 15 (MSB) 6 5 4 3 2 1 0 Generation (LSB) Additional length (n-7) (LSB) First reservation key (LSB) : n-7 | n (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” or “Preempt and Clear” completes successfully.
PAGE 134
8.12.4 Parameter data for Read Reservation Descriptor Bit Byte 7 0 | 7 (MSB) 8 | 11 (MSB) 6 4 3 2 1 0 Reservation key (LSB) Scope-specific address (LSB) 12 Reserved 13 14 | 15 5 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
8.13 PERSISTENT RESERVE OUT (5Fh) Bit Byte 7 6 5 0 1 Reserved = 0 2 1 0 Service Action Scope 3 4 5 6 9 3 Command Code = 5Fh 2 7 8 4 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. ! Parameter List Length must be 18h.
PAGE 136
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. The established persistent reservation applies to all commands received after the successful completion of the command.
PAGE 138
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. If a code which is not supported or a reserved code is specified, the drive returns a CHECK CONDITION status.
PAGE 139
RD READ (6) command and READ (10) command WR WRITE (6) command and WRITE (10) command NWR 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 SH SHared: The drive executes the command from all initiators.
PAGE 140
8.13.4 Parameter list Bit Byte 7 6 0 | 7 (MSB) 8 | 15 (MSB) 16 | 19 (MSB) 5 4 2 1 0 Reservation Key (LSB) Service Action Reservation Key (LSB) Scope-specific address (LSB) 20 Reserved 21 Reserved 22 23 3 (MSB) APTPL Extent length (LSB) Figure 117. PERSISTENT RESERVATION OUT parameter list 8.13.
PAGE 141
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. On other service actions, this field is ignored. 8.13.5.4 Scope-specified address Parameter in the Scope-specified address field is ignored by the drive. 8.
PAGE 142
8.14 PRE-FETCH (34h) Bit Byte 7 6 0 1 2 3 4 5 9 4 3 2 1 0 Command Code = 34h Reserved = 0 Reserved = 0 Immed RelAdr = 0 = 0 (MSB) Logical Block Address (LSB) 6 7 8 5 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. ! Transfer length specifies the number of contiguous blocks of data that are to be transferred into the cache.
PAGE 143
8.15 READ (6) (08h) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 08h Reserved = 0 (MSB) 2 3 Logical Block Address 4 Transfer Length 5 1 LBA (LSB) 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. ! Logical block address specifies the LBA at which the read operation shall begin.
PAGE 144
8.16 READ (10) (28h) Bit Byte 7 6 0 1 2 | 5 9 4 3 2 1 0 Command Code = 28h Reserved = 0 DPO FUA Reserved = 0 RelAdr = 0 (MSB) Logical Block Address (LSB) 6 7 8 5 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
8.17 READ BUFFER (ACH) Bit Byte 7 6 0 1 5 4 3 2 1 0 Command Code = 3Ch Reserved = 0 2 Mode Buffer ID = 0 3 4 5 (MSB) 6 7 8 (MSB) 9 VU = 0 Buffer Offset (LSB) Allocation Length (LSB) 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. This command does not alter the medium.
PAGE 146
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
! 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. Bit Byte 7 6 5 0 1 2 3 4 3 2 1 0 Offset Boundary (MSB) Buffer Capacity (LSB) Figure 125. Read Buffer Descriptor The value contained in the Buffer Offset field of subsequent WRITE BUFFER and READ BUFFER commands should be a multiple of two to the power of the offset boundary.
PAGE 148
8.18 READ CAPACITY (25h) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 25h 1 Reserved = 0 2 3 4 5 (MSB) RelAdr = 0 Reserved = 0 Logical Block Address (LSB) 6 7 Reserved = 0 8 Reserved = 0 9 VU = 0 Reserved = 0 PMI 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. ! RelAdr A Relative Address is not supported. Must be set to zero.
PAGE 149
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. Bit Byte 6 0 1 2 3 (MSB) 4 5 6 7 (MSB) 7 5 4 3 2 1 0 Logical Block Address (LSB) Block Length (LSB) Figure 128. Format of READ CAPACITY command reply ! Block Length specifies the length in bytes of the block.
PAGE 150
8.19 READ DEFECT DATA (10) (37h) Bit Byte 7 6 5 0 Reserved = 0 2 Reserved = 0 3 4 5 6 9 3 2 1 0 Command Code = 37h 1 7 8 4 Reserved = 0 0 P-list G-List Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 129. Read Defect Data (10) The READ DEFECT DATA command requests that the drive transfer the medium defect data to the initiator.
PAGE 151
8.19.1 Defect List Header Bit 7 Byte 6 5 4 3 2 1 0 Defect List Header 0 Rsvd = 0 1 Reserved = 0 2 3 (MSB) P-list G-List Defect List Format Defect List length (LSB) Figure 130. Defect List Header 8.19.2 Bytes from Index Format (100b) Byte 0 1 2 Defect Descriptors (MSB) Cylinder Number of Defect (LSB) 3 4 5 6 7 Head Number of Defect (MSB) Defect Bytes from Index (LSB) Figure 131.
PAGE 152
8.19.3 Physical Sector Format (101b) Byte 0 1 2 Defect Descriptors (MSB) Cylinder Number of Defect (LSB) 3 4 5 6 7 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. The Defect List Length is equal to eight times the number of defect descriptors.
PAGE 153
8.20 READ DEFECT DATA (12) (B7h) Bit Byte 7 6 5 0 1 Reserved = 0 2 1 0 P-listG-List Defect List Format Reserved = 0 (MSB) Allocation Length (LSB) 10 11 3 Command Code = B7h 2 3 4 5 6 | 9 4 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
8.20.1 Defect List Header Bit Byte 7 6 5 4 3 2 1 0 Defect List Header 0 Rsvd = 0 1 Reserved = 0 2 3 P-listG-List Defect List Format Rsvd = 0 4 | 7 (MSB) Defect List length (LSB) Figure 134. Defect List Header 8.20.2 Bytes from Index Format (100b) Byte 0 1 2 Defect Descriptors (MSB) Cylinder Number of Defect (LSB) 3 4 5 6 7 Head Number of Defect (MSB) Defect Bytes from Index (LSB) Figure 135.
PAGE 155
8.20.3 Physical Sector Format (101b) Byte 0 1 2 Defect Descriptors (MSB) Cylinder Number of Defect (LSB) 3 4 5 6 7 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. The Defect List Length is equal to eight times the number of defect descriptors.
PAGE 156
8.21 READ LONG (3Eh) Bit Byte 7 6 0 1 2 3 4 5 9 4 3 2 1 0 Command Code = 3Eh Reserved = 0 Reserved = 0 CORT RelAdr = 0 = 0 (MSB) Logical Block Address (LSB) 6 7 8 5 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. The transfer data includes data and ECC field data.
PAGE 157
8.22 REASSIGN BLOCKS (07h) Bit Byte 7 6 0 1 5 3 2 1 0 Command Code = 07h Reserved = 0 2 3 4 5 4 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. The logical block address is transferred to the drive during the DATA OUT phase.
PAGE 158
Following is the format of the data sent by the initiator during the DATA OUT phase Bit Byte 7 6 5 4 3 0 RSVD = 0 1 RSVD = 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 2 1 0 (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 (LSB) (MSB) Defect Logical Block Address –4 (LSB) Figure 139. Format of REASSIGN BLOCKS data ! Defect List Length must be 4, 8, 12, or 16.
PAGE 159
8.23 RECEIVE DIAGNOSTICS RESULTS (1Ch) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 1Ch 1 Reserved = 0 2 Reserved = 0 PCV Page Code 3 4 (MSB) Parameter List Length (LSB) 5 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
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. Bit Byte 7 6 5 4 0 Page Code = 40h 1 Reserved = 0 2-3 2 1 0 Page Length = 0Ah 4 Reserved = 5 RA 6-13 3 ALTS 0 Supplied format ALTT Reserved=0 Translate format Translated Address Figure 142.
PAGE 161
! 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: Bit Byte 7 6-8 9 0-13 6 5 4 3 2 1 0 Cylinder Number Head Number Sector Number or Bytes from Index Figure 143. Translated address 8.23.3 RECEIVE DIAGNOSTIC RESULTS Page 80 This page contains the off-line read scan status.
PAGE 162
8.24 RELEASE (6) (17h) Bit Byte 7 6 5 0 1 3 2 1 0 Command Code = 17h Reserved = 0 2 3rdPty 3rd Party ID Ext=0 Reservation Identification 3 4 5 4 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. In this case the drive returns a GOOD status. Extents are not supported by the drive.
PAGE 163
8.25 RELEASE (10) (57h) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 57h Reserved = 0 2 3rdPty Reserved = 0 Ext = 0 Reservation Identification 3 3rd Party Device ID 4 Reserved = 0 5 Reserved = 0 6 Reserved = 0 7 Reserved = 0 8 Reserved = 0 9 1 VU = 0 Reserved = 0 FLAG LINK Figure 146. RELEASE (10) 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 164
8.26 REPORT DEVICE IDENTIFIER (A3h) Bit Byte 7 6 0 1 5 4 3 Reserved = 0 0 Service Action = 05h Reserved = 0 3 Reserved = 0 4 Reserved = 0 5 Reserved = 0 (MSB) Allocation Length (LSB) 10 11 1 Command Code = A3h 2 6 | 9 2 Reserved = 0 VU = 0 Reserved = 0 FLAG LINK Figure 147. REPORT DEVICE IDENTIFIER The REPORT DEVICE IDENTIFIER command requests that the drive send device identification information to the application client.
PAGE 165
Bit Byte 7 0 | 3 4 n 6 5 4 3 2 1 0 (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. The identifier length initially equals zero, and is changed only by a successful SETDEVICE IDENTIFIER command.
PAGE 166
8.27 REPORT LUN (A0h) Bit Byte 7 6 5 4 3 2 0 Command Code = A0h 1 | 5 Reserved 6 | 9 0 (MSB) Allocation Length (LSB) 10 11 1 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. The Report LUN command should always be available and is unaffected by any reservations. The Allocation Length must be at least 16 bytes.
PAGE 167
8.28 REQUEST SENSE (03h) Bit Byte 7 6 5 0 1 4 3 2 0 Command Code = 03h Reserved = 0 Reserved = 0 2 3 Reserved = 0 4 Allocation Length 5 1 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 nexus4 terminated with CHECK CONDITION status. All other information (e.g.
PAGE 168
8.29 RESERVE (6) (16h) Bit Byte 7 6 5 0 1 5 3 2 1 0 Command Code = 16h Reserved = 0 2 3 4 4 3rdPty 3rd Party ID Ext = 0 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. Extents are not supported by the drive.
PAGE 169
8.30 RESERVE (10) (56h) Bit Byte 7 6 5 0 1 4 3 2 1 Command Code = 57h Reserved = 0 3rdPty Reserved 2 Reservation Identification 3 Third Party Device ID 4 Reserved = 0 5 Reserved = 0 6 Reserved = 0 7 8 9 0 Ext = 0 (MSB) Extent List Length = 0 (LSB) VU = 0 Reserved = 0 FLAG LINK Figure 153. RESERVE (10) The RESERVE command is used to reserve a LUN for an Initiator.
PAGE 170
8.31 REZERO UNIT (01h) Bit Byte 7 6 0 1 4 3 2 1 0 Command Code = 01h Reserved = 0 2 3 4 5 5 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.
PAGE 171
8.32 SEEK (6) (0Bh) Bit Byte 7 6 0 1 4 3 2 1 0 Command Code = 0Bh Reserved = 0 2 3 (MSB) LBA Logical Block Address (LSB) 4 5 5 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.
PAGE 172
8.33 SEEK EXTENDED (10) (2Bh) Bit Byte 7 6 0 1 2 3 4 5 4 3 2 1 0 Command Code = 2Bh Reserved = 0 Reserved = 0 0 (MSB) Logical Block Address (LSB) 6 7 8 9 5 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.
PAGE 173
8.34 SEND DIAGNOSTIC (1Dh) Bit Byte 7 6 5 0 1 5 3 2 1 0 Command Code = 1Dh Function Code 2 3 4 4 PF 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
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 drive starts its short self-test routine in background mode. 010b Background extended self-test The drive starts its extended self-test routine in background mode. 011b NA Reserved 100b Abort background self-test Abort the current self-test in the background mode.
PAGE 175
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. Bit Byte 7 6 5 0 Page Code = 0 1 Reserved = 0 2 - 3 4 3 2 1 0 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
! 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. Bit Byte 7 6-8 6 5 4 3 2 1 0 Cylinder Number 9 Head Number 10-13 Sector Number or Bytes from Index Figure 161. Address to translate 8.34.3 SEND DIAGNOSTIC Page 80 This requests the drive to perform off-line read scan.
PAGE 177
8.35 SET DEVICE IDENTIFIER (A4h) Bit Byte 7 6 5 0 4 Reserved = 0 2 3 4 5 1 0 Service Action = 06h Reserved = 0 (MSB) Parameter List Length (LSB) 10 11 2 Command Code = A4h 1 6 | 9 3 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
8.36 START STOP Unit (1Bh) Bit Byte 7 6 0 5 4 3 2 1 0 Command Code = 1Bh 1 Reserved = 0 Reserved = 0 2 3 Immed Reserved = 0 4 Power Conditions = 0 5 VU = 0 Reserved = 0 Reserved = 0 LoEj Start = 0 FLAG LINK Figure 165. START STOP Unit The START STOP UNIT command is used to spin up or stop the spindle motor. ! Immed bit is to specify 0 1 status is to be returned at the end of the operation GOOD status shall always be returned immediately after command has been received.
PAGE 179
8.37 SYNCHRONIZE CACHE (35h) BIT Byte 7 6 5 0 1 2 3 4 5 9 3 2 1 0 Command Code = 35h Reserved = 0 Reserved = 0 Immed RelAdr = 0 = 0 (MSB) Logical Block Address (LSB) 6 7 8 4 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. ! Logical Block Address is to specify where the operation is to begin.
PAGE 180
8.38 TEST UNIT READY (00h) Bit Byte 7 6 5 0 1 2 3 4 5 4 3 2 1 0 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. The drive will first verify that the motor is spinning at the correct speed.
PAGE 181
8.39 VERIFY (2Fh) Bit Byte 7 6 0 1 2 3 4 5 9 4 3 2 1 0 Byte Chk RSVD= 0 Command Code = 2Fh Reserved = 0 DO Rsvd = 0 (MSB) Logical Block Address (LSB) 6 7 8 5 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. This condition is not considered an error.
PAGE 182
8.40 WRITE (6) (0Ah) Bit Byte 7 6 5 0 1 3 2 1 0 Command Code = 0Ah Reserved = 0 2 3 (MSB) LBA Logical Block Address (LSB) 4 5 4 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. Logical block address This field specifies the LBA at which the write operation shall begin.
PAGE 183
8.41 WRITE (10) (2Ah) Bit Byte 7 6 5 0 1 2 | 5 9 3 2 1 0 Command Code = 2Ah Reserved = 0 DPO FUA Reserved RelAdr = 0 (MSB) Logical Block Address (LSB) 6 7 8 4 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.
PAGE 184
8.42 WRITE AND VERIFY (2Eh) Bit Byte 7 6 5 0 1 2 3 4 5 9 3 2 1 0 Command Code = 2Eh Reserved = 0 DPO Reserved = 0 Byte RelAdr Chk = 0 (MSB) Logical Block Address (LSB) 6 7 8 4 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
8.43 WRITE BUFFER (3Bh) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 3Bh 1 Reserved = 0 2 Mode Buffer ID 3 4 5 (MSB) 6 7 8 (MSB) Buffer Offset (LSB) Parameter List Length (LSB) 9 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. This command does not alter the medium of the drive.
PAGE 186
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 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.
PAGE 187
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 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.
PAGE 188
Buffer ID field is used to indicate which portion of the microcode image is being downloaded. The following 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. The drive shall set the sense key to ILLEGAL REQUEST and additional sense code to ILLEGAL FIELD IN CDB. 8.43.4.
PAGE 189
8.44 WRITE LONG (3Fh) Bit Byte 7 6 5 0 4 3 2 1 0 Command Code = 3Fh 1 Reserved = 0 2 3 4 5 RelAdr = 0 Reserved = 0 (MSB) Logical Block Address (LSB) 6 Reserved = 0 7 8 (MSB) Byte Transfer Length (LSB) 9 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
8.45 WRITE SAME (41h) Bit Byte 7 6 5 0 1 2 3 4 5 9 3 2 1 0 Command Code = 41h Reserved = 0 RelAdr = 0 Reserved = 0 (MSB) Logical Block Address (LSB) 6 7 8 4 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
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. Bit 7 6 5 4 Reserved = 0 3 2 1 Status Code 0 RSVD Figure 176. SCSI Status Byte. Format of the SCSI STATUS byte.
PAGE 192
28h 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
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.
PAGE 194
If an unsupported message is received, the drive will send the MESSAGE REJECT message to the initiator. If at the time the unsupported message is received a valid nexus exists, the drive will continue with the command. If no valid nexus exists, the drive will go to BUS FREE. 10.1.1 TASK COMPLETE (00h) The drive sends this message to the initiator to indicate that the execution of a command has been terminated and that valid status has been sent to the initiator.
PAGE 195
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.
PAGE 196
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.
PAGE 197
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
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 message to the Initiator with the transfer width exponent equal to 1 (E = 01h).
PAGE 199
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.
PAGE 200
If DT_REQ is set to one and IU_REQ is set to zero, the following values are used. Initiator Request Target Response Target Transfer Period (ns) Transfer Rate 0 <= Mi <= 9 Mt = 09h 12.5 Fast-80 10 <= Mi <= 10 Mt = 0Ah 25 Fast-40 11 <= Mi <= 12 Mt = 0Ch 50 Fast-20 13 <= Mi <= 25 Mt = 19h 100 Fast-10 26 <= Mi <= 255 Mt = 19h (Asynch Mode) Asynch Figure 188.
PAGE 201
! HOLD_MCS (Hold Margin Control Settings) is used to negotiate if any margin control settings which has been set with the margin control subpage of the port control mode page is retained. ! QAS_REQ (Quick Arbitration and Selection Enable Request) is used to negotiate if QAS is enabled. The drive supports QAS when IU_REQ is negotiated to be effective. ! DT_REQ (DT Clocking Enable Request) is used to negotiate if DT DATA phase is enabled. The drive supports DT_REQ.
PAGE 202
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. Pending data and status for other logical unit and initiators will not be cleared.
PAGE 203
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. 10.1.15 TARGET RESET (0Ch) This message is sent from an initiator to direct the drive to clear all current commands.
PAGE 204
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. The previous executed command will not be terminated by this tagged command. This tagged command will wait until the previous command is completed.
PAGE 205
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.
PAGE 206
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.
PAGE 207
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. The drive will not attempt to reconnect to the initiator to complete the operation that was in progress when the error condition was detected.
PAGE 208
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. 10.4.
PAGE 209
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. 11.1.
PAGE 210
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. It is used to configure the bus when the drive ID's and LUN's are not known.
PAGE 211
! the command is permitted to execute if the conditions to execute concurrently are met. (See Section 11.5, “Concurrent I/O Process.
PAGE 212
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. ! The log page parameters have been cleared by LOG SELECT command with PCR bit.
PAGE 213
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. 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.
PAGE 214
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 REQUEST SENSE Executed.
PAGE 215
Command (w/Option) Response REQUEST SENSE Executed. The drive may return Sense KCQ 020401h (NOT READY, IN PROCESS OF BECOMING READY) INQUIRY Executed REPORT LUNS Executed TEST UNIT READY Executed and CHECK CONDITION is returned with Sense KCQ 020401h (NOT READY, IN PROCESS OF BECOMING READY) START STOP UNIT (Start) Executed - Success: GOOD status is returned.
PAGE 216
Command (w/Option) Response REQUEST SENSE Executed. The drive may return Sense KCQ 020400h (NOT READY, START SPINDLE MOTOR FAIL) INQUIRY Executed REPORT LUNS Executed TEST UNIT READY Executed and CHECK CONDITION is returned with Sense KCQ 020400h (NOT READY, START SPINDLE MOTOR FAIL) START STOP UNIT (Start) Executed - Success: Good status is returned.
PAGE 217
Command (w/Option) Response REQUEST SENSE Executed. The drive may return Sense KCQ 020402h (NOT READY, INITIALIZE COMMAND REQUIRED) INQUIRY Executed REPORT LUNS Executed TEST UNIT READY Executed and CHECK CONDITION is returned with Sense KCQ 020402h (NOT READY, INITIALIZE COMMAND REQUIRED) START STOP UNIT (Start) Executed - Success: Good status is returned.
PAGE 218
Command (w/Option) Response REQUEST SENSE Executed.
PAGE 219
Command (w/Option) Response REQUEST SENSE Executed. The drive may return Sense KCQ 023100h (NOT READY, FORMAT CORRUPTED) or Sense KCQ 033100h (MEDIUM ERROR, FORMAT CORRUPTED) REQUEST SENSE INQUIRY Executed REPORT LUNS Executed TEST UNIT READY Executed and CHECK CONDITION is returned with Sense Key 023100h (NOT READY, FORMAT CORRUPTED) FORMAT UNIT Executed - Success: GOOD Status is returned.
PAGE 220
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
! 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. A single initiator may queue up to 128 commands, if no other initiator has more than one command in the queue, although at times this maximum may be reduced as the drive can reserve command blocks for internal use. 11.3.
PAGE 222
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. This function will improve total throughput of the drive. 11.
PAGE 223
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. 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.. 11.
PAGE 224
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
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 maintained 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. 11.14.
PAGE 226
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. 11.16.
PAGE 227
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. Note: The bring-up operation, having already completed, is not rerun.
PAGE 228
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. 11.17.1 Power on Diagnostics See Section 11.16.2 "Power On Reset" on page 210 for the description of the bring-up operation. 11.17.
PAGE 229
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
! 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. It writes data to a certain area in the reserved area and read it from the same area to validate. Head 0 is used for this test. ! ECC circuit test is a test for ECC circuit if errors can be corrected by the circuit.
PAGE 231
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.
PAGE 232
12.2 Sense Data Description 12.2.1 Valid (Bit 7 of byte 0) 0 1 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) 70h 71h Current Error. This indicates an error for the current command. Deferred Error. This indicates that the error is for a previous command that has already returned a GOOD status.
PAGE 233
without altering the medium. If an invalid parameter is found in parameters supplied as data, the drive might have altered the medium. 6h 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 9h Vendor Specific Ah Not used Bh Aborted command The drive aborted the command. Ch-Dh Not Implemented Eh MISCOMPARE Indicates that the source of data did not watch the data read from the medium.
PAGE 234
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. Key Code Qual Description 0 0 0 No error 0h 5Dh 00h No sense. Predictive Failure Analysis threshold reached 1h 01h 00h Recovered write error. No index 1h 02h 00h Recovered no seek comp 1h 03h 00h Recovered write error. Write fault 1h 0Bh 01h Temperature Warning 1h 0Ch 01h Recovered write error.
PAGE 235
Key Code Qual Description 2h 04h 00h Not ready. Start spindle motor fail. 2h 04h 01h Not ready. In process of becoming ready. 2h 04h 02h Not ready. Initializing command (START STOP UNIT command) required 2h 04h 04h Not ready. Format in progress. 2h 04h 09h Not ready. Self-test in progress. 2h 31h 00h Not ready. Medium format corrupted. 2h 40h 80h Diag Fall - Bring-Up failure or degraded mode. 2h 40h 85h Diag Fall - RAM microcode not loaded. 2h 65h 00h Not ready.
PAGE 236
Key Code Qual Description 5h 1Ah 00h Illegal request. Parameter list length error. The number of parameters supplied is not equal to the value expected. 5h 20h 00h Illegal request. Illegal command operation code. This command is also returned when an unsupported command code is received. 5h 21h 00h Illegal request. Logical block address out of range. 5h 24h 00h Illegal request. Invalid field in CDB 5h 25h 00h Illegal request. Invalid LUN 5h 26h 00h Illegal request.
PAGE 237
Key Code Qual Description Bh 43h 00h 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 Bh 44h 00h Aborted command. Buffer CRC Error in reading from buffer to host. Bh 47h 00h Aborted command. SCSI parity error Bh 48h 00h Aborted command. Initiator detected error message received.
PAGE 238
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. Bit Byte 7 6 5 15 SKSV C/D 16 17 (MSB) Field Pointer 4 Reserved 3 BPV 2 1 0 Bit Pointer (LSB) Figure 204.
PAGE 239
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. Bit Byte 7 15 16 17 6 5 4 SKSV 3 2 1 0 Reserved (MSB) Actual Retry Count (LSB) Figure 205. Actual Retry Count SKSV Sense-key specific valid 0 1 Actual ERP Retry Count Actual ERP Retry Count is not valid. Actual ERP Retry Count is valid. Actual EPR step number used to recover from the error condition. 12.2.10.
PAGE 240
12.2.11 Vendor Unique Error Information (Byte 18 through 19) This field gives detailed information about errors.
PAGE 241
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). 12.2.12.
PAGE 242
Sense Data Byte 22 Description 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
Sense Date Byte 23 Description 01h HDC Test Failure 02h Sector Buffer RAM Test Failure 03h EEPROM Read Failure 08h AE Write Failure 09h Channel Calibration Failure 0Ah Head Load Failure 10h POR Only Fail 11h Spin-Up Failure 12h Reserved Area Table Failure 13h RAM Code Read Failure 14h RAM Code Signature Failure 15h Overlay Code Read Failure 16h Read-Only Table Read Failure 17h Head Test Failure 21h Primary Defect List Read Failure 22h Grown Defect List Read Failure 23h Mod
PAGE 244
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 Byte 20 Description (Status) Bit 7 Sector Count Over Bit 6 ECC Error on LBA Bit 5 Not used Bit 4 Uncorrectable Error Bit 3 Over Symbol Bit 2 Correctable Error Preparation Bit 1 Error On Bit 0 Drive On Figure 212.
PAGE 245
Sense Data Byte 22 Description (Status) 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
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.
PAGE 247
Index A E Acoustics, 43 Actuator, 7 Altitude, 30 Attention Condition, 190 Automatic Rewrite/Reallocate, 207 Auxiliary connector, 68-pin model, 25 Average latency, 14 Average seek time, 13 ECC on the fly correction, 34 Electrical interface specification, 21 Electromagnetic compatibility, 45 Equipment errors, 34 Equipment Status, 17 Error recovery procedure, 17 F Failure prediction ( PFA / S.M.A.R.T.
PAGE 248
Mechanical specifications, 36 Mounting, 39 Multiple Initiator Environment, 209 N Non-arbitrating systems, 208 Non-operating conditions, 30 O Operating conditions, 30 Option jumper block, 26 P Performance characteristics, 12 Persistent Reservation, 116 P-List, 19 Power connector, 21 Power requirements, 32 Priority commands, 204 Probability of uncorrectable data error rate, 34 Product ID, 10 SCSI Message System, 177 SCSI Protocol, 193 SCSI SENSE DATA, 215 SCSI signal connector - 68-pin, 22 SCSI Signal Con
PAGE 249
ibm ® © International Business Machines Corporation 2002 www.ibm.com/harddrive IBM Technology Group Support Center Telephone: 888.426.5214 or 507.286.5825 Fax: 507.253.3748 E-mail: drive@us.ibm.com Singapore Technology Group Support Center Telephone: (65)6418.9595 or 1800.418.9595 E-mail: drive@sg.ibm.com UK Technology Group Support Center Telephone: 44.1475.898.125 E-mail: drive@uk.ibm.com Germany Technology Group Support Center Telephone: 49.7032.153050 E-mail: drive@de.ibm.