Download Print this page

Advertisement

C141-C010-01EN
MAW3073, MAW3147, MAW3300 NP/NC SERIES
MAX3036, MAX3073, MAX3147 NP/NC SERIES
DISK DRIVES
SCSI LOGICAL INTERFACE SPECIFICATIONS

Advertisement

   Also See for Fujitsu MAX3073NC - SCSI,80, Dell DC961,Hard Drive

   Related Manuals for Fujitsu MAX3073NC - SCSI,80, Dell DC961,Hard Drive

   Summary of Contents for Fujitsu MAX3073NC - SCSI,80, Dell DC961,Hard Drive

  • Page 1

    C141-C010-01EN MAW3073, MAW3147, MAW3300 NP/NC SERIES MAX3036, MAX3073, MAX3147 NP/NC SERIES DISK DRIVES SCSI LOGICAL INTERFACE SPECIFICATIONS...

  • Page 2

    "Important Alert Items" in this manual. Keep this manual handy, and keep it carefully. FUJITSU makes every effort to prevent users and bystanders from being injured or from suffering damage to their property. Use the product according to this manual.

  • Page 3: Revision History

    Revision History (1/1) Revised section (*1) Edition Date Details (Added/Deleted/Altered) August, 2005 — — Section(s) with asterisk (*) refer to the previous edition when those were deleted. C141-C010...

  • Page 4

    This page is intentionally left blank.

  • Page 5

    Preface This manual explains concerning the MAW3073NP/NC, MAW3147NP/NC, MAW3300NP/NC, MAX3036NP/NC, MAX3073NP/NC, MAX3147NP/NC series 3.5 inch hard disk drives with internal SCSI controller. The purpose of this manual is to provide specifications of each command and detailed explanations of their functions for use of these magnetic disk drives incorporated into user systems, and to present the information necessary for creating host system software.

  • Page 6: Acronyms And Abbreviations

    Preface Glossary The glossary explains technical terms which are necessary to the reader's understanding when reading this manual. Acronyms and Abbreviations This list shows the full spelling of abbreviations used in this manual. The model name of disk drives covered by this manual differs in its ending suffix (Note 1) depending on its device type (3 types), the electrical conditions of the SCSI interface used to connect the disk drive to the host system and its capacity and data format at the time it was shipped, but in this manual, except in cases where models need to be especially distinguished,...

  • Page 7: Conventions Used In This Manual

    Requesting for User’s Comments Please use the User’s Comment Form attached to the end of this manual to identify user comments including error, inaccurate and misleading information of this manual. Contact to your Fujitsu representative for additional comment forms if required. C141-C010...

  • Page 8

    Preface Related Standards Specifications and functions of products covered by this manual comply with the following standards. Standard (Text) No. Name Enacting Organization ANSI X3. 131-1986 American National Standard for American National Information Systems --- Small Computer Standards Institute System Interface (SCSI) (ANSI) ANSI X3.

  • Page 9

    MANUAL ORGANIZATION 1. General Description Product/ Maintenance Manual 2. Specifications (C141-E234/C141-E235) 3. Data Format 4. Installation Requirements 5. Installation 6. Diagnostics and Maintenance 7. Error Analysis SCSI Physical 1. SCSI Bus Interface Specifications 2. SCSI Message (C141-C011) 3. Error Recovery SCSI Logical Interface Specifications 1.

  • Page 10

    This page is intentionally left blank.

  • Page 11

    Contents CHAPTER 1 Command Processing........................1-1 Command Format ............................. 1-1 Status ................................ 1-6 Outline of Command Processing ......................1-8 1.3.1 Single commands ..........................1-8 1.3.2 Command link ........................... 1-9 1.3.3 Disconnect/reconnect processing ....................1-11 1.3.4 Synchronous mode data transfer/wide mode data transfer .............. 1-15 Command Queuing Function........................

  • Page 12: Table Of Contents

    Contents 2.1.2 Operation mode setting........................2-5 Look-Ahead Cache Feature ........................2-6 2.2.1 Caching operation..........................2-6 2.2.2 Caching parameters ........................... 2-9 2.2.3 Look-Ahead operation, Look-Ahead volume.................. 2-10 Write Cache ............................2-11 CHAPTER 3 Command Specifications ......................3-1 Control/Sense Commands......................... 3-1 3.1.1 TEST UNIT READY (00).........................

  • Page 13

    Contents 3.1.21 REPORT DEVICE IDENTIFIER (A3)................... 3-68 3.1.22 SET DEVICE IDENTIFIER (A4) ....................3-69 Data Access Commands ......................... 3-71 3.2.1 READ (08) ............................3-71 3.2.2 READ EXTENDED (28) ........................ 3-72 3.2.3 WRITE (0A)............................ 3-73 3.2.4 WRITE EXTENDED (2A)......................3-74 3.2.5 WRITE AND VERIFY (2E) ......................

  • Page 14: Table Of Contents

    Contents 4.1.10 Informational exceptions control page (page code = 1C)..............4-43 4.1.11 Background control mode parameter (page code = 1C/subpage = 01)..........4-47 4.1.12 Additional error recovery parameters (page code = 21) ..............4-48 Log Parameters ............................4-49 4.2.1 Supprot log page (X'00')........................4-49 4.2.2 Buffer overrun / underrun page (X'01') ...................

  • Page 15: Table Of Contents

    Contents 4.2.9.1 General usage application client parameter data (Page 0F, Code 0000-003F)......4-66 4.2.10 Self-test result page (X'10') ......................4-67 4.2.10.1 Self-test result parameter data (Page 10, Code 0001-0014)............4-67 4.2.11 Background medium scan page (X'15')................... 4-69 4.2.11.1 Background medium scan status parameter ................4-69 4.2.11.2 Background medium scan parameter ..................

  • Page 16: Table Of Contents

    Contents Illustrations Figures Figure 1.1 6-Byte CDB Basic Format......................... 1-1 Figure 1.2 10-Byte CDB Basic Format....................... 1-2 Figure 1.3 12-Byte CDB Basic Format....................... 1-2 Figure 1.4 Status ..............................1-6 Figure 1.5 Data space configuration ......................... 1-31 Figure 2.1 Data buffer configuration (in the case of 8 cache segments)............2-2 Figure 2.2 Example of data buffer operation during read...................

  • Page 17: Table Of Contents

    Contents Figure 4.1 MODE SELECT parameters: read/write error recovery parameters ..........4-2 Figure 4.2 MODE SELECT parameters: disconnect/reconnect parameters ............. 4-10 Figure 4.3 MODE SELECT parameters: format parameters ................4-14 Figure 4.4 MODE SELECT parameters: each parameters of pages 3, 4, and C in detail........ 4-17 Figure 4.5 MODE SELECT parameters: drive parameters................

  • Page 18

    This page is intentionally left blank.

  • Page 19: Figure 1.1 6-byte Cdb Basic Format

    Command Processing CHAPTER 1 1.1 Command Format 1.2 Status 1.3 Outline of Command Processing 1.4 Command Queuing Function 1.5 UNIT ATTENTION Condition 1.6 Sense Data Hold State 1.7 Command Processing Exceptions 1.8 Data Block Addressing This chapter describes the basic logical specifications of the IDD command processing functions. Note: The IDD operates as the target (TARG) on the SCSI bus.

  • Page 20: Figure 1.2 10-byte Cdb Basic Format, Figure 1.3 12-byte Cdb Basic Format

    Command Processing Byte Operation Code Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Data Length (MSB) Transfer Data Length (LSB) Control Byte Figure 1.2 10-Byte CDB Basic Format Byte Operation Code Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB)

  • Page 21

    1.1 Command Format Operation code Bit 7 Group Code Command Code The leading byte of all CDBs shows the format and type of command to be executed. a. Group code The group code specifies the number of bytes and format of the CDB. The groups of commands shown below are used in the IDD.

  • Page 22

    Command Processing Transfer data length In this field, the length of data to be transferred between INIT and TARG when the command is executed is specified by the number of logical data blocks or the number of bytes. In subsequent descriptions, the former is called the “transfer block count”...

  • Page 23

    1.1 Command Format Control byte Bit 7 Link a. Link Command link is specified by this bit is “1.” Details of the operation of the command link are described in Section 1.3.2. b. Bit 7, 6 (vendor unique) When 1 is specified in these bits, the command ends with a CHECK CONDITION status. Handling an illegal CDB If there is an error in the contents of a description (specification) in the CDB, or if there is an error in the specifications in parameters transferred from the INIT by CDB specifying, that command ends with a...

  • Page 24: Figure 1.4 Status

    Command Processing Status Figure 1.4 shows the type of status that the IDD supports. The status is one byte of information sent from the TARG to the INIT in the STATUS phase when one command is completed, and notifies the INIT of the results of the command’s execution. The status is also sent even in cases when the TARG is in a state which it makes it impossible for it to execute the command when it receives a request for an input/output operation.

  • Page 25

    1.2 Status CHECK CONDITION status This status is reported in the following cases a) to c). The IDD generates sense data when it reports this status and indicates the detailed cause. The INIT issues a REQUEST SENSE command when it receives this status and should sample sense data.

  • Page 26

    Command Processing INTERMEDIATE CONDITION MET Status This status is reported when it is possible to secure the cache memory area necessary to read all the logical data blocks specified in a PRE-FETCH command which specifies a link (in the case of “Immed = 1”), or when reading of all the specified logical data blocks is completed (in the case of “Immed = 0”).

  • Page 27

    1.3 Outline of Command Processing 4) The TARG executes the COMMAND phase and receives the CDB from the INIT. The TARG judges the length of the CDB by the group code in the first byte of the CDB and requests transfer of the necessary number of bytes.

  • Page 28: Table 1.1 Responses To Link Specification Commands

    Command Processing Table 1.1 Responses to Link Specification Commands End Status Status Message Link Function Completed INTERMEDIATE LINKED TASK COMPLETE Effective Normally Completed CHECK CONDITION TASK COMPLETE Not Effective Abnormally INTERMEDIATE CONDITION Conditions Met LINKED TASK COMPLETE Effective Unable to Start BUSY TASK COMPLETE Not Effective...

  • Page 29

    1.3 Outline of Command Processing 1.3.3 Disconnect/reconnect processing When processing is performed by the TARG during the command execution process which does not require operation on the SCSI bus, the TARG can return the SCSI bus to the BUS FREE phase temporarily by disconnect processing and execute command internally.

  • Page 30

    Command Processing Table 1.2 Types of Command and Disconnect Processing Commands with executing disconnect processing. (Note 2) Commands without executing disconnect processing. (Note 1) CHANGE DEFINITION (40) FORMAT UNIT (04) INQUIRY (12) LOG SELECT (4C) LOG SENSE (4D) MODE SELECT (15) MODE SELECT EXTENDED (55)

  • Page 31

    1.3 Outline of Command Processing Basic disconnect processing procedure Disconnect processing is executed basically by the following processing procedure. 1) If the IDD judges that it is possible for it to disconnect from the SCSI bus during execution of a command, it sends a DISCONNECT message to the INIT and enters the BUS FREE phase.

  • Page 32

    Command Processing Note: In disconnect processing in this case, transfer of all the data accompanying execution of the command is complete and there is actually no necessity for the SAVE DATA POINTER message. However, by issuing the SAVE DATA POINTER message, processing time increases due to the message transfer, but as a result of the pointer restore operation that is executed internally by the INIT during reconnection processing for the status report, the current data pointer can reflect the final results of the data transfer.

  • Page 33

    1.3 Outline of Command Processing 3) After the INIT that accepts the IDENTIFY message normally completes the pointer restore operation, it should make the ACK signal for the IDENTIFY message FALSE. If the ATTENTION condition does not exist when the ACK signal becomes FALSE during sending of the IDENTIFY message, the IDD regards the reconnection processing as having been normally completed and begins subsequent processing.

  • Page 34

    Command Processing The IDD maintains data transfer mode settings between itself and each INIT individually. Therefore, an INIT which uses asynchronous mode transfer and an INIT which uses synchronous mode transfer can both coexist on the same SCSI bus. Also, the parameters for synchronous mode transfers decided by the SYNCHRONOUS DATA TRANSFER REQUEST message can differ for each INIT and an INIT which uses the 8-bit width transfer mode can coexist with an INIT which uses the 16-bit width transfer mode.

  • Page 35

    1.4 Command Queuing Function When a command is in the queued state, if a RESET condition occurs, or if the IDD receives a TARGET RESET message from any INIT, it clears all the commands in the queue. At this time, the IDD generates on UNIT ATTENTION condition for all the INITs.

  • Page 36

    Command Processing When there is an error in the CDB, the IDD responds with a CHECK CONDITION status at the point when that command is fetched from the queue. If the IDD is in the not ready state at the point when the queued command is fetched, it responds with a CHECK CONDITION status.

  • Page 37

    1.5 UNIT ATTENTION Condition The INIT can specify the following error recovery options by the QErr bit of the control mode parameter (Page A) of the mode select parameters. When “00” is specified in the QErr bit, the IDD enters any one of a number of sense hold states, and when this state is released, it continues to execute the commands in the queue.

  • Page 38

    Command Processing When power on, RESET or TARGET RESET occurs If the IDD’s power is switched on, the IDD enters the RESET condition or is reset by a TARGET RESET message, this UNIT ATTENTION condition is generated for all the INITs, regardless of whether the disk drive is in the ready state or not.

  • Page 39

    1.5 UNIT ATTENTION Condition • Power on [=29-01] • Reset [=29-02] • TARGET RESET [=29-03] • Transciever Mode Changed to SINGLE-ENDED [=29-05] • Transciever Mode Changed to LVD [=29-06] • Mode parameters changed [=2A-01] • Reservations Preempted [=2A-03] • Reservations Released [=2A-04] •...

  • Page 40

    Command Processing 1.5.3 UNIT ATTENTION condition multiple hold If any UNIT ATTENTION condition is generated and a new UNIT ATTENTION condition is generated for a different reason before the INIT for which the first UNIT ATTENTION condition was held clears it, those UNIT ATTENTION conditions are held together, and the IDD reports these multiple UNIT ATTENTION conditions in sequence.

  • Page 41

    1.7 Command Processing Exceptions 1) If a command is issued to the logical unit in the sense data hold state by the INIT which is the object of sense data holding. – In the case of an untagged command REQUEST SENSE command: The sense data held by the IDD are transferred to the INIT and the sense hold state is released.

  • Page 42

    1.7.3 Reserved operation code Group 6 and Group 7 commands operation codes (X ‘C0’ to X ‘FF’) are reserved by Fujitsu. When any command is issued which includes these operation codes, the IDD does not always respond with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid command operation code [=20-00].

  • Page 43: Table 1.3 Sense Data In Not Ready State

    1.7 Command Processing Exceptions Also, if initialization of the disk media (formatting) has not been completed normally, it will be impossible to access data on the disk media. Processing of and response to commands received by the IDD when it is in the not ready state or in the initialization incomplete state are described below.

  • Page 44

    Command Processing REZERO UNIT command: If the spindle motor has reached the normal rotational speed, this • command is executed even if reading of system information failed. If the spindle motor has not reached the normal rotating speed, or if reading of system information is still in progress, a CHECK CONDITION status is reported as in item (1).

  • Page 45

    1.7 Command Processing Exceptions Table 1.4 Outline of SCSI Bus Error Recovery Processing Item Type of Error Error Recovery Processing MESSAGE OUT phase parity error Retry the erroneous phase up to 3 times max / "CHECK CONDTION" Status COMMAND phase parity error Retry the erroneous phase up to 3 times max / "CHECK CONDTION"...

  • Page 46

    Command Processing 1.7.6 Reset processing The INIT can reset the SCSI bus with following. • RESET condition • TARGET RESET message • CLEAR TASK SET message • ABORT TASK SET message • ABORT TASK message The RESET condition resets all the SCSI devices connected on the same SCSI bus. The IDD is initialized to the same state as when its power is switched on by the RESET condition, with the currently executed command as well as all the commands in the queue cleared.

  • Page 47: Table 1.6 Reset Processing During Write

    1.7 Command Processing Exceptions Table 1.6 Reset processing during write Type of command Halting process of command execution WRITE Data blocks which are currently being written are WRITE EXTENDED processed normally, including the ECC portion, and WRITE AND VERIFY execution of the command is terminated at the point when SEND DIAGNOSTIC (Write/Read Test) that processing is completed.

  • Page 48

    Command Processing After this state occurs, the IDD reports the CHECK CONDITION status for all input/output operation requests except the REQUEST SENSE command. The sense data reported at this time indicate HARDWARE ERROR [=4] / Internal target failure [=44-nn]. If this state is reported continuously for input/output operation requests, it is necessary for the INIT to generate a RESET condition or send a TARGET RESET message and attempt to recover from the error state.

  • Page 49: Figure 1.5 Data Space Configuration

    1.8 Data Block Addressing Physical cylinder [System space] Cylinder 0 Track 0 Cylinder 0 Track 1 Cell 0 Cylinder 0 Zone 0 Track (m-1) Cell 1 [User space] Track 0 Alternate cell Alternate cell (b-1) (b tracks) Zone 1 Cylinder (a-1) Zone (x-1) Alternate (c cylinders)

  • Page 50

    Command Processing 1.8.2 Logical block addressing The IDD uses logical data block addressing which is not dependent on the disk drive’s physical structure as the method of data access on the disk medium. The IDD makes correspondence between each physical sector and each logical data clock address during formatting.

  • Page 51

    Data Buffer Management CHAPTER 2 Data Buffer Look-Ahead Cache Feature Write Cache In this chapter, the configuration of the data buffer with which the IDD is equipped, its operation and the operation of the cache feature are described. Data Buffer 2.1.1 Data buffer configuration and basic operation The IDD is equipped with a data buffer, which makes it possible to efficiently execute data transfer...

  • Page 52

    Data Buffer Management Segment Segment 7 Segment 6 Segment 5 Segment 4 Segment 3 Segment 2 Segment 1 Segment 0 Disk Media Valid Data INIT Write→ Write→ ←Read ←Read Figure 2.1 Data buffer configuration (in the case of 8 cache segments) The basic functions and operations of the data buffer in a read operation and a write operation are shown below.

  • Page 53

    2.1 Data Buffer 6) When transfer of all the specified data is completed, the IDD reports the status and terminates the command. Note: In order to avoid frequent repetition of the disconnect/reconnect processing after data transfer starts on the SCSI bus, and avoid the occurrence of data overruns, it is necessary to set the buffer full ratio (see Section 2.1.2) of the MODE SELECT parameter so the difference in the data transfer rates between the INIT (SCSI bus) and the disk drive is maintained in a good balance.

  • Page 54

    Data Buffer Management 3) If the data transfer rate of the INIT (SCSI bus) is lower than the data transfer rate of the disk drive, since the data pre-fetch of data that are to be written to that data block is not completed, it may not be possible to write the data continuously to the disk (data underrun).

  • Page 55: Operation Mode Setting

    2.1 Data Buffer 2.1.2 Operation mode setting MODE SELECT parameter In order to make it possible to control from the INIT the reconnection processing start timing for executing data transfers with the SCSI bus in read and write operations, the IDD is provided with the MODE SELECT parameter (Disconnect/Reconnect Parameter: Page code = 2) shown in Figure 2.4.

  • Page 56: Look-ahead Cache Feature, Caching Operation

    Data Buffer Management b. Buffer empty ratio This parameter specifies the timing for the IDD to start reconnection when it is requested by the INIT to transfer data in the WRITE, WRITE EXTENDED or WRITE AND VERIFY command. In a write operation, after the IDD receives a command, the IDD begins transferring data (data pre-fetch) while locating the position of the target data blocks on the disk media in parallel.

  • Page 57

    2.2 Look-Ahead Cache Feature Caching object commands Commands which execute caching operations are the commands shown below: • READ • READ EXTENDED If all the data block groups which are objects of the processing specified in these commands, or a portion of the data blocks, including the top logical data block specified in these commands are relevant data (See item (2)) for caching in the data buffer (if they hit), when the IDD receives a command and performs disconnect processing, it immediately reconnects and sends the data on the data buffer which...

  • Page 58

    Data Buffer Management b) If any of the following commands is issued, all the data which are objects of caching are disabled. • CHANGE DEFINITION • FORMAT UNIT • LOG SELECT • LOG SENSE • MODE SELECT • MODE SELECT EXTENDED •...

  • Page 59: Caching Parameters, Figure 2.5 Cache Control Parameters

    2.2 Look-Ahead Cache Feature 2.2.2 Caching parameters The IDD supports the MODE SELECT parameters (caching parameters: page code = 8) shown in Figure 2.5 for controlling the cache feature. See Section 4.1 concerning details of the MODE SELECT parameters. [Caching Parameters (Page Code = 8)] Byte Page Length X‘0A’...

  • Page 60: Look-ahead Operation, Look-ahead Volume

    Data Buffer Management 2.2.3 Look-Ahead operation, Look-Ahead volume 1) Excluding the conditions in 3) and 4) for the amount of data specified as the minimum pre-fetch volume, data are read for look-ahead irrespective of track boundaries or cylinder boundaries. Commands which are already in the queue or commands which are newly received while a look- ahead operation is in progress, are executed after the look-ahead operation is completed.

  • Page 61: Write Cache

    2.3 Write Cache Write Cache The IDD is equipped with a write cache function in order to reduce the INIT's command processing time. If that operation is permitted by the MODE SELECT command (caching parameters: Page code = 8, WCE bit), at the point when the IDD completes the transfer of all data specified in the WRITE or WRITE EXTENDED command, it reports the GOOD status and terminates the command.

  • Page 62

    This page is intentionally left blank.

  • Page 63: Chapter 3 Command Specifications, Control/sense Commands, Test Unit Ready (00)

    CHAPTER 3 Command Specifications Control/Sense Commands Data Access Commands Format Commands Maintenance, Diagnostic Commands This chapter describes detailed specifications of the SCSI commands which the IDD is equipped with and how to use them. Control/Sense Commands 3.1.1 TEST UNIT READY (00) Byte X‘00’...

  • Page 64: Inquiry (12)

    Command Specifications 3.1.2 INQUIRY (12) Byte X‘12’ CmdDt EVPD Page Code/Operation Cpde Transfer Byte Length Link This command transfers the information showing the IDD's characteristics (INQUIRY data) to the application client. This command is executed immediately without queuing in a system which issues only commands with no tags or links.

  • Page 65

    3.1 Control/Sense Commands EVPD (Enable Vital Product Data) a) If the specification in this bit is zero, the IDD transfers the standard INQUIRY data or the command supported data, mentioned later, to the application client. b) If the specification in this bit is one, product information called VPD (vital product data) is transferred to the application client.

  • Page 66: Figure 3.1 Standard Inquiry Data

    RelAdr WBus32 WBus16 Sync Linked CmdQue SftRe SCSI-3 RelAdr Obsolete Wbus16 Sync Linked TranDis CmdQue FUJITSU ---- (Vendor ID: ASCII) (Product ID: ASCII) Microcode Version No. (ASCII) ---- (Product Revision: ASCII) Device Serial No. (ASCII) 48-55 X‘00’ (Vendor Specific) CCS/SCSI-2 X‘00’...

  • Page 67

    3.1 Control/Sense Commands a. Qualifier field (0,0,0): The specified logical unit shows the type of input/output device shown in the "Device Type Code" field. Even if this code is reported, it does not mean that that logical unit is in the ready state.

  • Page 68

    Command Specifications g. Supported functions The bit positions shown below are valid only when the CHANGE DEFINITION command is set so that the SCSI-2 or SCSI-3 mode INQUIRY data are transferred, and the functions which the IDD supports are shown in the bit correspondence. "1"...

  • Page 69

    Vendor ID field This field indicates the name of the product's supplier in left-justified ASCII code, and always indicates FUJITSU. The unused right end is space for the ASCII code. Product ID field The product's model name is displayed in left-justified ASCII code in this field.

  • Page 70

    Command Specifications k. Device Serial Number field The value following byte 4 of the device serial number in the VPD information is indicated in this field. Higher order digits which do not contain valid numbers are filled with ASCII code spaces (X '20').

  • Page 71: Figure 3.2 Command Support Data

    3.1 Control/Sense Commands Command Support Data Figure 3.2 shows the format and contents of the command support data transferred to the INIT by this command if "0" is specified in the "EVPD" bit and "1" is specified in the "CmdDt" bit. Byte Qualifier Device Type Code...

  • Page 72

    Command Specifications c. CDB size This field contains the number of bytes in the CDB for the operation code being queried, and the size of the "CDB Usage Data" field in the return data. d. CDB usage data This field contains information about the CDB for the operation code being queried. The first byte of the "CDB usage data"...

  • Page 73: Figure 3.3 Vpd Information: Vpd Identifier List, Figure 3.4 Vpd Information: Device Serial No

    3.1 Control/Sense Commands Byte Qualifier Device Type Code X‘00’ (Page Code) X‘00’ X‘03’ (Page Length) X‘00’ (Page Code List) X‘80’ (Device Serial No.) X‘C0’ (Operation Mode) Figure 3.3 VPD information: VPD identifier list The values indicated in the "Qualifier" and "Device Type Code" fields in byte 0 are the same as those in the previously mentioned standard INQUIRY data.

  • Page 74: Figure 3.5 Vpd Information: Operation Mode

    Command Specifications The values indicated in the "Qualifier" and "Device Type Code" fields in byte 0 are the same as those in the previously mentioned standard INQUIRY data. The "Page code" field in byte 1 indicates the page code (X '80') of this VPD information itself. Also, the "Page length" field in byte 3 indicates the length (byte length) after byte 4.

  • Page 75: Read Capacity (25)

    3.1 Control/Sense Commands 3.1.3 READ CAPACITY (25) Byte X‘25’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Link This command transfers information related to the disk drive's capacity and the data block size to the INIT.

  • Page 76: Change Definition (40), Figure 3.6 Read Capacity Data

    Command Specifications Byte Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Block Length (MSB) Block Length Block Length Block Length (LSB) Figure 3.6 READ CAPACITY data 3.1.4 CHANGE DEFINITION (40) Byte X‘40’ Save SCSI Level Parameter List Length Link This command changes the IDD's SCSI level and the operation mode.

  • Page 77

    3.1 Control/Sense Commands This command specifies a different SCSI level in the "SCSI level" field in SCB byte 3. The SCSI level is indicated by 1 byte of code as shown in the following table. If a code other than the following codes is specified, the command is terminated by a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00] and the SCSI level and operation mode are not changed.

  • Page 78

    Command Specifications Byte X‘00’ X‘00’ Header X‘00’ X‘04’ (Parameter Length) WDTR UNTAIN SDTR RSRTY PHSCRC Parameter List X‘xx’ (Spindle Motor Start Delay Time) X‘00’ (Reserved) Figure 3.7 CHANGE DEFINITION command: operation mode parametor The operation mode parameter is configured from a 4-byte parameter list following a 4-byte header. Header a) Bytes 0 to 2 X '00' must be specified in this field.

  • Page 79

    3.1 Control/Sense Commands b) UNTATN (UNIT ATTENTION report mode) This specifies the response method to commands received from the INIT when the IDD is holding a UNIT ATTENTION condition: "1"* (Report): The IDD reports a CHECK CONDITION status (Standard SCSI specification) in response to commands other than INQUIRY and REQUEST SENSE.

  • Page 80

    Command Specifications f) AGD (AIP generation disabled) This specifies whether or not it is permitted to generate AIP (Asynchronous Information Protection). "1" * (Prohibited): Prohibited generation "0" (Permitted): Permitted generation * Set at shipping time The IDD ignores this specification and operates with the settings specified at shipping.

  • Page 81: Mode Select (15)

    3.1 Control/Sense Commands 3.1.5 MODE SELECT (15) Byte X‘15’ Parameter List Length Link This command performs setting and changing of each type of parameter related to disk drive physical attributes, data format, timing of SCSI bus disconnect/reconnect processing and error recovery procedures, etc.

  • Page 82

    Command Specifications If a "Header," "Block Descriptor" or any "Page Descriptor" cannot be transferred with all the defined length because the total defined length of the MODE SELECT parameters actually transferred from the INIT do not match the value specified in the "Parameter List Length" field, or if the total of the MODE SELECT parameter's defined length transferred from the INIT exceeds the value specified in the "Parameter list length"...

  • Page 83: Figure 3.8 Mode Select Parameter Structure

    3.1 Control/Sense Commands Current values Save values Power-on RESET condition [Command to all INITs] [Command to all INITs] TARGET RESET MODE message SELECT Pages: Pages: MODE SELECT (SP=1) 1, 2, 7, 8, A, 19, 1C, 21 1, 2, 7, 8, A, C, 19, 1C, Power-on [Command to all INITs] [Command to...

  • Page 84

    Command Specifications If the IDD performs rounding processing ("rounding up" or "rounding down") of parameter values specified by the INIT, in some cases a "CHECK CONDITION" status (RECOVERED ERROR [=1] / Rounded parameter [37-00]) is reported, and in some cases it is not reported. Whether or not a "CHECK CONDITION"...

  • Page 85

    3.1 Control/Sense Commands Page Descriptor [Page 0 Format (Short Page Format)] Byte Page Code Page Header Page Length Parameter Field [Sub Page Format (Long Page Format)] Byte Page Code Sub Page Code Page Header Page Length Parameter Field Figure 3.9 MODE SELECT command (Group 0) parameter configuration a.

  • Page 86

    Command Specifications • Block descriptor length This field indicates the length (block count) of the "Block descriptor" which follows the header (not including the length of the "Page descriptor"). It is possible to define only 1 "Block descriptor" to the IDD, and either X '00' or X '08' must be specified in this field. When X '00' is specified in this field, it indicates that the "Block descriptor"...

  • Page 87

    3.1 Control/Sense Commands c. Page descriptor The "Page descriptor" is configured from a 2-byte page header followed by a parameter field and each parameter function attribute is classified in a unit called a "Page." The individual "Page descriptors" in the MODE SELECT and MODE SELECT EXTENDED commands may be specified independently by the INIT and multiple "Page descriptors"...

  • Page 88

    Command Specifications Parameter Byte Length Header Block Descriptor 8 or 0 Page Descriptor Page 1: Read/Write Error Recovery Parameter 8 or 12 Page 2 Disconnect/Reconnect Parameter 12 or 16 Page 3: Format Parameter Page 4: Drive Parameter 20 or 24 Page 7: Verify Error Recovery Parameter Page 8:...

  • Page 89: Mode Select Extended (55)

    3.1 Control/Sense Commands 3.1.6 MODE SELECT EXTENDED (55) Byte X‘55’ Parameter List Length (MSB) Parameter List Length (LSB) Link This command performs setting and changing of each type of parameter related to disk drive physical attributes, data format, timing of SCSI bus disconnect/reconnect processing and error recovery procedures, etc.

  • Page 90

    Command Specifications Header Byte X‘00’ X‘00’ X‘00’ (Medium Type) × × X‘00’ X‘00’ X '00' (Block Descriptor Length: LSB) X‘00’ or X‘08’ (block descriptor length: MSB) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X‘00’...

  • Page 91: Figure 3.10 Mode Select Extended Command (group 2) Parameter Configuration

    3.1 Control/Sense Commands Page Descriptor [Page 0 Format (Short Page Format)] Byte Page Code Page Header Page Length Parameter Field [Sub Page Format (Long Page Format)] Byte Page Code Page Sub Page Code Header Page Length Parameter Field Figure 3.10 MODE SELECT EXTENDED command (Group 2) parameter configuration C141-C010 3-29...

  • Page 92: Mode Sense (1a)

    Command Specifications 3.1.7 MODE SENSE (1A) ‘1A’ Page Code Byte Sub Page Code Transfer Byte Length Link This command reports the values for each type of parameter related to the disk drive's physical attributes, data format, timing for SCSI bus disconnect and reconnect processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.

  • Page 93

    3.1 Control/Sense Commands Page Byte Length Page Code: Page Descriptor Name SCSI-2 SCSI-3 Read/Write Error Recovery Parameter 8 bytes 12 bytes 12 bytes Disconnect/Reconnect Parameter 12 bytes 16 bytes 16 bytes Format Parameter 24 bytes 24 bytes 24 bytes Drive Parameter 20 bytes 24 bytes 24 bytes...

  • Page 94

    Command Specifications (Operations depending on page code and subpage code) Page code Subpage code Operation Vender Specific (No page format is required.) Reports the contents of the header (if required) and block descriptor. 01h – FFh Vender Specific (No page format is required.) Terminates with an error (5/24/00).

  • Page 95: Table 3.1 Mode Sense Data Type Specifications

    3.1 Control/Sense Commands Table 3.1 MODE SENSE Data Type Specifications Type of Parameter Transferred to the INIT 00 Current Values: Reports each "Current" parameter value. The "Current" values are either of the following values. • Values specified by a MODE SELECT or MODE SELECT EXTENDED command which is finally normally terminated.

  • Page 96: Figure 3.11 Mode Sense Command (group 0) Parameter Configuration

    Command Specifications Header Byte 0 Sense Data Length Media Type) ‘ ’ ( DPOFUA (Block Descriptor Length) ' or Block Descriptor Byte 0 Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) ‘ ’ Data Block Length (MSB) Data Block Length Data Block Length (LSB) Figure 3.11 MODE SENSE command (Group 0) parameter configuration (1 of 2)

  • Page 97

    3.1 Control/Sense Commands Page Descriptor [Page 0 Format (Short Page Format)] Byte Page Code Page Header Page Length Parameter Field [Sub Page Format (Long Page Format)] Byte Page Code Page Sub Page Code Header Page Length Parameter Field Figure 3.11 MODE SENSE command (Group 0) parameter configuration (2 of 2) C141-C010 3-35...

  • Page 98

    Command Specifications Header a. Sense data length This field indicates the length (number of bytes) of the parameter list (MODE SENSE data) which it is possible to transfer to the INIT by this command. The length of the "Sense data length" field itself is not included in this value.

  • Page 99

    3.1 Control/Sense Commands b. Data block length This field indicates the length (byte length) of 1 logical data block on the disk media. Page descriptor The "Page descriptor" is configured from a parameter field which follows a 2-byte (4-byte for the sub page format) page header, and is divided into units called "Page"...

  • Page 100: Mode Sense Extended (5a)

    Command Specifications 3.1.8 MODE SENSE EXTENDED (5A) X ‘5A’ Page Code Byte Transfer Byte Length (MSB) Transfer Byte Length (LSB) Link This command reports the values for each type of parameter related to the disk drive's physical attributes, data format, timing for SCSI bus disconnect and reconnect processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.

  • Page 101: Figure 3.12 Mode Sense Extended Command (group 2) Parameter Configuration

    3.1 Control/Sense Commands Header Byte 0 Sense Data Length (MSB) Sense Data Length (LSB) ‘ ’ (Media Type) DPOFUA ‘ ’ ‘ ’ ‘ ’ (Block Descriptor Length: MSB) or X ‘ ’ ‘ ’ (Block Descriptor Length: LSB) Block Descriptor Byte 0 Data Block Count Data Block Count (MSB)

  • Page 102

    Command Specifications Page Descriptor [Page 0 Format (Short Page Format)] Byte Page Code Page Header Page Length Parameter Field [Sub Page Format (Long Page Format)] Byte Page Code Page Sub Page Code Header Page Length Parameter Field Figure 3.12 MODE SENSE EXTENDED command (Group 2) parameter configuration (2 of 2) 3-40 C141-C010...

  • Page 103: Rezero Unit (01), Start/stop Unit (1b)

    3.1 Control/Sense Commands 3.1.9 REZERO UNIT (01) Byte X‘01’ Link This command moves the read/write heads of the disk drive to the initial position. A data block with the logical block address of zero exists at the initial position (cylinder 0 / track 0). Initialization of the disk drive's positioning control system and automatic adjustment are also performed by this command.

  • Page 104

    Command Specifications It is possible to select the disk drive's spindle motor starting mode through the setting terminal on the IDD. If prohibition of motor starting control is set by this command at the setting terminal, the spindle motor starts automatically when the IDD's power is switched on. It is also possible to delay the starting time through the specifications in the CHANGE DEFINITION command.

  • Page 105: Reserve (16)

    3.1 Control/Sense Commands 3.1.11 RESERVE (16) Byte X‘16’ 3rd Pty 3rd Pty Dev ID × × × × × × × × × × × × × × × × × × × × × × × × Link Together with the RELEASE command, this command controls exclusive access to the logical unit (IDD) under a multi-initiator environment.

  • Page 106

    Command Specifications Reserve right and third party reserve function If the "3rd Pty" bit in byte 1 of the CDB is "0," the IDD is reserved by the INIT which issued this command and that INIT has the Reserve right for the IDD. If the "3rd Pty"...

  • Page 107

    3.1 Control/Sense Commands 1. If INIT #A issues a RESERVE command which does not specify the third party reserve function to TARG #0, TARG #0 enters the reserved state from INIT #A and INIT #A has the reserve right with respect to TARG #0.

  • Page 108: Reserve Extended (56)

    Command Specifications 3.1.12 RESERVE EXTENDED (56) Byte X‘56’ 3rd Pty × × × × × × × × Third Party Device ID × × × × × × × × × × × × × × × × Link This command controls exclusive access to a logical unit (IDD) under a multi-initiator environment together with the RELEASE and RELEASE EXTENDED commands.

  • Page 109: Release (17)

    3.1 Control/Sense Commands 3.1.13 RELEASE (17) Byte X‘17’ 3rd Pty 3rd Pty Dev ID × × × × × × × × Link This command releases the reserve state of an IDD in relation to the INIT that issued this command. When a reserve state in relation to the INIT that issues this command, or an IDD in the type of reserve state which is the release object specified in the CDB of this command does not exist, or even when the IDD is reserved by another SCSI device, this command is terminated normally with a GOOD status, but...

  • Page 110: Release Extended (57), Request Sense (03)

    Command Specifications 3.1.14 RELEASE EXTENDED (57) Byte X‘57’ 3rd Pty × × × × × × × × Third Party Devices ID × × × × × × × × × × × × × × × × Link This command releases the reserve state of an IDD in relation to the INIT which issued this command. This command function is the same as that of the Group 0 RELEASE command (Section 3.1.13), except that it is also possible to specify the third party release function for SCSI devices with SCSI IDs 15 to 8.

  • Page 111

    3.1 Control/Sense Commands The length of the sense data in the IDD is 48 bytes. The "Transfer byte length" field in the CDB indicates the number of bytes of sense data which can be received by the INIT. The IDD transfers sense data to the INIT by either of the following two methods, depending on the specification in the CHANGE DEFINITION command (SCSI level).

  • Page 112: Log Select (4c)

    Command Specifications • A state appropriate to an overlapping command exception condition (see Section 1.7.1). In cases other than the above, the sense data currently being held, or, when there are no sense data being held, the sense data which indicate the state if an error occurred during execution of this command, are sent to the INIT and it is terminated with a GOOD status.

  • Page 113: Figure 3.13 Log, Select Command: Parameter List

    3.1 Control/Sense Commands Value Description Current threshold values Current cumulative values Default threshold values Default cumulative values The "PC" bits are ignored by the drive. The drive assumes that current cumulative parameters are selected. The "Parameter List Length" field specifies the length in bytes of the parameter list that is located in the Data-Out Buffer.

  • Page 114: Figure 3.14 Log Select Command: Log Parameter

    Command Specifications Page code This field indentifies which log page is being transferred. The log pages that can be transferred by this command are shown below. Page Code Description Changable Parameter Buffer Overrun / Underrun Page Disable Write Error Counter Page Enable Read Error Counter Page Enable...

  • Page 115

    3.1 Control/Sense Commands Paramter code This field identifies the log paramter being transferred for that log page. Byte 2 a) DU (Disable Update) "1" : The IDD does not update the log parameter value except in responce to a LOG SELECT command that specifies a new value for the parameter.

  • Page 116: Log Sense (4d)

    Command Specifications Parameter value This field indicates actual "threshold value" or "cumulative value". The size of this field differs in each log parameter. 3.1.17 LOG SENSE (4D) Byte X'4D' Page Code Parameter Pointer (MSB) Parameter Pointer (LSB) Parameter List Length (MSB) Parameter List Length (LSB) Link This command provides a means for the application client to retrieve statistical or other operational...

  • Page 117: Persistent Reserve In (5e)

    3.1 Control/Sense Commands Page Code Description Parameter Pointer Supported Log Pages Ignored Buffer Overrun / Underrun Page Supported Write Error Counter Page Supported Read Error Counter Page Supported Verify Error Counter Page Supported Non-medium Error Page Should be zero Temperature Page Supported Start-stop Cycle Counter Page Supported...

  • Page 118: Persistent Reserve In Service Actions, Read Keys

    Command Specifications The PERSISTENT RESERVE IN command obtains information about the reservation requirements and reservation keys that are valid in the target range. This command is used in combination with the PERSISTENT RESERVE OUT command (See Section 3.1.19). When this command is received, if the reservation in the target is enabled by the RESERVE command, the command is rejected and is returned with the RESERVATION CONFLICT status.

  • Page 119: Read Reservations, Persistent Reserve In Parameter Data For Read Keys

    3.1 Control/Sense Commands 3.1.18.1.2 READ RESERVATIONS In the READ RESERVATION service action, the drive transfers the following information to the initiator as a parameter data list. • Current generation value (See Section 3.1.18.2) • Reservation keys registered by initiators that keep persistent reservations •...

  • Page 120: Persistent Reserve In Parameter Data For Read Reservations

    Command Specifications This counter value is not incremented in the following cases: When the PERSISTENT RESERVE IN command is executed When the RESERVE or RELEASE service action of the PERSISTENT RESERVE OUT command is executed If the PERSISTENT RESERVE OUT command cannot be executed because of an error or a reservation conflict.

  • Page 121: Persistent Reservation Scope, Figure 3.17 Persistent Reserve In Reservation Descriptor

    3.1 Control/Sense Commands The "Additional Length" field contains a count of the number of bytes to follow in the "Reservation Descriptors" field. If the specified allocation length in the CDB of the PERSISTENT RESERVE IN command is not sufficient for containing the entire parameter list, a portion of the parameter list from byte 0 to the specified allocation length is transferred to the initiator.

  • Page 122: Persistent Reservations Type

    Command Specifications Code Name Description Logical Unit Persistent reservation applies to an entire logical unit Reserved Reserved Element Persistent reservation applies to the specified element (not supported) 3h-Fh Reserved Reserved 3.1.18.3.1.1 Logical Unit scope The "Scope" field value of the Logical Unit indicates that persistent reservations apply to the entire Logical Unit.

  • Page 123: Table 3.2 Persistent Reservation Type Codes

    3.1 Control/Sense Commands Table 3.2 Persistent reservation type codes Code Name Description Reserved Write Reads Shared: Any initiator can execute read commands Exclusive Writes Exclusive: Except by an initiator holding a persistent reservation, a write command executed by any initiator causes a reservation conflict.

  • Page 124: Persistent Reserve Out (5f)

    Command Specifications 3.1.19 PERSISTENT RESERVE OUT (5F) Byte X'5F' Service Action Scope Type (MSB) Parameter List Length (18h) (LSB) Control The PERSISTENT RESERVE OUT command reserves a logical unit for exclusive or shared use by a particular initiator. This command is used in combination with the PERSISTENT RESERVE IN command.

  • Page 125: Persistent Reserve Out Service Actions

    3.1 Control/Sense Commands The RESERVE, PREEMPT, and PREEMPT AND ABORT service actions of this command determine whether any conflict of Scope or Type specifications occurs between two reservation requirements: the new one provided by this command, and the other one already being held on the drive. If the reservation requirements conflict, the command is rejected and returned with the RESERVATION CONFLICT status.

  • Page 126: Persistent Reserve Out Parameter List, Figure 3.18 Persistent Reserve Out Command: Parameter List

    Command Specifications Table 3.3 PERSISTENT RESERVE OUT command service action codes Code Name Description REGISTER Registers a reservation key on the drive. RESERVE Generates a persistent reservation for the specified Scope and Type using the reservation key. RELEASE Releases the persistent reservation. CLEAR Clears all reservation keys and persistent reservations.

  • Page 127

    3.1 Control/Sense Commands For the "Reservation Key" field, an 8-byte key code provided by the application client is set in order to enable the drive to identify the initiator that is the source of the PERSISTENT RESERVE OUT command. The drive can then verify that the "Reservation Key" field in the PERSISTENT RESERVE OUT command matches the registered reservation key for the initiator that issues the command.

  • Page 128: Report Luns (a0)

    Command Specifications Table 3.4 PERSISTENT RESERVE OUT service actions and valid parameters Parameters Service Action Allowed Scope type Reservation Service Action Element Reservation Key Parameters REGISTER ignored ignored valid valid ignored REGISTER & ignored ignored valid ignored IGNORE EXISTING KEY Element ignored ignored...

  • Page 129: Figure 3.19 Report Luns Command: Parameter List

    3.1 Control/Sense Commands This command requests that the peripheral device logical unit inventory be sent to the application client. This command normally operate under the reserve condition (RESERVE or PERSISTENT RESERVE). The "Allocation Length" should be at least 16 bytes. If the "Allocation Length" is less than 16 bytes, the IDD reports the CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid Field in CDB [=24- 00]).

  • Page 130: Figure 3.20 Report Device Identifier: Parameter List

    Command Specifications 3.1.21 REPORT DEVICE IDENTIFIER (A3) Byte X ‘A3’ Service Action (X’ 05’) Allocation Length (MSB) Allocation Length Allocation Length Allocation Length (LSB) Link This command requests that the device server send device identification information to the application client. The "Service Action"...

  • Page 131

    3.1 Control/Sense Commands 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 shall not be adjusted to reflect the truncation. The identifier length shall initially equal zero, and shall be changed only by a successful SET DEVICE IDENTIFIER command.

  • Page 132: Figure 3.21 Set Device Identifer: Parameter List

    Command Specifications The "Allocation Length" field specifies the length in bytes of the Identifier that shall be transferred from the application client to the device server. The maximum value for this field shall be 512 bytes. A parameter list length of zero indicates that no data shall be transferred, and that subsequent REPORT DEVICE IDENTIFIER commands shall return an Identifier length of zero.

  • Page 133

    3.2 Data Access Commands Data Access Commands 3.2.1 READ (08) Byte X‘08’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Block Count Link This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count"...

  • Page 134

    Command Specifications 3.2.2 READ EXTENDED (28) Byte X‘28’ × Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) Link This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count"...

  • Page 135

    3.2 Data Access Commands 3.2.3 WRITE (0A) Byte X‘0A’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Block Count Link This command transfers the number of blocks of data specified in the "Transfer block count" field from the INIT and writes them in continuous logical data blocks with the logical data block on the disk media specified in the "Logical block address"...

  • Page 136

    Command Specifications Note: Even when there is an error in the specification in the CDB, or when a write operation to the disk media cannot be executed normally due to various other causes, the transfer of data (data is pre- fetched to the data buffer) from the INIT to the IDD may be executed.

  • Page 137

    3.2 Data Access Commands When this bit is "1", it indicated that the IDD shall access the media in performing the command prior to returning GOOD status. WRITE commands shall not return GOOD status until the logical blocks have actually been written on the media (i.e., the data is not write cached). 3.2.5 WRITE AND VERIFY (2E) Byte...

  • Page 138

    Command Specifications 3.2.6 VERIFY (2F) Byte X‘2F’ × BytChk Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) Link This command reads the number of continuous logical data blocks specified in the "Block count" field with the logical data block on the disk media which is specified in the "Logical block address"...

  • Page 139

    3.2 Data Access Commands 3.2.7 SEEK (0B) Byte X‘0B’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Link This command executes a seek operation of the cylinder/track where the logical data block specified in the "Logical block address" field in the CDB exists. When disconnect processing is permitted, the IDD performs disconnect processing after receiving the CDB.

  • Page 140

    Command Specifications This command executes a seek operation of the cylinder/track where the logical data block specified in the "Logical block address" field in the CDB exists. The functions and operation of this command are the same as those of the Group 0 SEEK command (Section 3.2.7), except that it is possible to specify 4-byte logical block addresses.

  • Page 141: Figure 3.22 Set Limits Command: Specifying The Range Where Access Is Permitted

    3.2 Data Access Commands Also, the size of the range where access is permitted, specified in this command in the "Block count" field in the CDB, specifies the number of logical data blocks from that starting point. However, when zero is specified in the "Block count" field, access to the final logical data block of the specified data space (User Space or CE Space), with the logical data block specified in the "Logical block address"...

  • Page 142

    Command Specifications Notes: Commands which come under restrictions in read operations or write operations when "1" is specified in the "RdInh" (read inhibit) or "WrInh" (write inhibit) flag are as follows. “RdInh” • READ • VERIFY (*) • READ EXTENDED (*) • WRITE AND VERIFY (*) •...

  • Page 143

    3.3 Format Commands The values specified in the "Logical block address" field and "Block count" field in the CDB are disregarded and if any unwritten data exist in the data buffer, writing of all those data to the disk media is performed.

  • Page 144

    Command Specifications Defect list In order to register or specify the positions of defects on the disk media in connection with defect management processing that can be specified from the INIT, the following types of “Defect List” are defined. a. P List: primary defect list Defect position information (permanent defects) is registered in this list at the time the disk drive is shipped from the factory.

  • Page 145: Index

    3.3 Format Commands Specifying the initialization method The INIT can specify the method of defect processing executed by this command in the “FmtData (format data)” bit and “CmpLst (complete list)” bit of CDB byte 1 and the “Defect List Format” field. When “1”...

  • Page 146: Figure 3.23 Format Unit Command Parameter List Configuration

    Command Specifications Format parameters Figure 3.23 shows the data format of the Format parameter transferred from the INIT when “1” is specified in the “FmtData (format data)” bit of the CDB. Header Byte X‘00’ DPRY DCRT STPF Immed × Defect List Length (MSB) Defect List Length (LSB) Defect List (D List) Byte...

  • Page 147

    3.3 Format Commands a. Header The top of the format parameter transferred from the INIT is a 4-byte header. The INIT can specify the method used for defect processing that is executed by this command by control flags within the header.

  • Page 148

    Command Specifications • Immed (Immediate) “1” : If “1” is specified in the Immed (immediate) bit, at the point when the CDB’s legality is confirmed, or at the point when transfer of the defect list is completed, a “GOOD” status is reported.

  • Page 149: Figure 3.24 Defect Descriptor: Byte Distance From Index Format

    3.3 Format Commands Note: Even if X’FFFFFFFF’ is specified as the byte distance from the index to the defect position, a whole track cannot be considered defective. Byte Cylinder No. (MSB) Cylinder No. Cylinder No. (LSB) Head No. Byte distance from index to defect position (MSB) Byte distance from index to defect position Byte distance from index to defect position Byte distance from index to defect position (LSB)

  • Page 150: Figure 3.25 Defect Descriptor: Physical Sector Address Format

    Command Specifications Byte Cylinder No. (MSB) Cylinder No. Cylinder No. (LSB) Head No. Physical sector No. of defective block (MSB) Physical sector No. of defective block Physical sector No. of defective block Physical sector No. of defective block (LSB) Figure 3.25 Defect descriptor: physical sector address format •...

  • Page 151

    3.3 Format Commands Space in the range specified in the “Block descriptor” and “Format parameters” (Page 3), and the “Drive parameters” (Page 4) of the MODE SELECT parameter. If a defect descriptor in the “Byte distance from the Index format” is specified in the D List, depending on the byte position of the specified defective byte, 1 sector may be processed as a defective sector with 2 or more defect descriptors.

  • Page 152

    Command Specifications Table 3.5 FORMAT UNIT command defect processing (2 of 3) CDB Byte 1 Header Defect FmtData CmpLst Defect list DPRY Defect Processing Method List format Length Neither the P List or the G List is d d d Zero used in defect processing (alternate block allocation...

  • Page 153

    3.3 Format Commands Table 3.5 FORMAT UNIT command defect processing (3 of 3) Note 1) ddd: 0,0,0= D List in the block address format. 1,0,0= D List in the byte distance from the index format. 1,0,1= D List in the physical sector address format. Note 2) The D List is not transferred from the INIT.

  • Page 154: Figure 3.26 Reassign Block Command: Defect Data List Configuration

    Command Specifications Note: Copying of the contents of data in the logical data blocks specified in the “Defect data” list to alternate blocks allocated by this command is attempted, but in some cases, copying cannot be done. Confirmation of the contents of the data in allocated alternate blocks, saving of data before issuing this command and restoring of data after this command is executed are the responsibility of the INIT.

  • Page 155

    3.3 Format Commands The logical block address of defective data blocks is described in 4-byte format in the defect descriptor. When multiple defect descriptors are specified, it is best for the INIT to describe defect descriptors in the ascending order of the logical data block addresses. Furthermore, if the addresses of logical data blocks specified in the defect descriptor list overlap each other, This command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in parameter list [=26-00] and none of the alternate block allocation processing in that...

  • Page 156

    Command Specifications 1. Delete the defect descriptors which precede the defect descriptor that specifies the logical block address displayed in the “Command inherent information” field of the sense data from the defect descriptor list specified in this command, and leave that defect descriptor in the list. Defect Descriptor List XXXX Logical block address that indicates the “Command inherent...

  • Page 157: Figure 3.27 Read Defect Data Command (37): Defect Data Configuration

    3.3 Format Commands PList GList Defect Data Type P List and G List P List only G List only 4-byte header information only (described in this section) Defect List Format Defect Data Format Block Address Format Byte Distance from the Index Format Physical Sector Address Format The “Transfer byte length”...

  • Page 158

    Command Specifications b. G List (grown list) bit When this bit is “1,” it indicates that G List defect data are included in the defect descriptor list that is actually transferred to the INIT. When it is “0,” it indicates that the G List defect data are not included.

  • Page 159

    3.3 Format Commands Even if defect data of the type specified in the CDB do not exist in the defect list (P List or G List) (if the defect list is empty), “1” is displayed in the “PList” bit and the “GList” bit in the header transferred to the INIT corresponding to the specification in the CDB.

  • Page 160

    Command Specifications In defect data in the block address format, all the physical defect position information on the disk media cannot be described universally. For example, defect position information in areas without block addresses (spare sectors, or cylinders which are not being used as User Space or CE Space) cannot be described.

  • Page 161: Figure 3.28 Read Defect Data Command (b7): Defect Data Configuration

    3.4 Maintenance, Diagnostic Commands Byte X‘00’ PList GList Defect List Format Reserved Header Reserved Defect List Length (MSB) Defect List Length (LSB) Defect Defect Data Descriptor List Figure 3.28 READ DEFECT DATA command (B7): Defect data configuration Maintenance, Diagnostic Commands 3.4.1 SEND DIAGNOSTIC (1D) Byte...

  • Page 162

    “Diagnostic failure on component ‘nn’ [=40-nn].” (nn is the code in the range X ‘80’ to X ‘FF,’ which shows the type of error. This code is a Fujitsu unique definition for the purpose of analysis when there is a failure, and its meaning is not released to the public.

  • Page 163

    3.4 Maintenance, Diagnostic Commands Table 3.6 Error recovery control flags during the self-diagnosis test PER DTE Diagnostic test operation The diagnostic test continues when error recovery is successful. The contents of recovered errors are not reported. When an error which cannot be recovered from is detected, the diagnostic test terminates at that point with an error.

  • Page 164: Figure 3.29 Send Diagnostic Command: Parameter List Configuration

    Command Specifications received, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST) [=5] / Invalid field in CDB [=24-00]). Figure 3.29 shows the format of the parameter list (called the parameter page) transferred from the INIT to the IDD by this command.

  • Page 165: Figure 3.30 Send Diagnostic Parameters: Page Code List

    3.4 Maintenance, Diagnostic Commands Page Code (Hex) Function Reports a list of the supported page codes. Logical/Physical Address Conversion • Page parameter length This field specifies the byte length of the page parameter after byte 4. The INIT must specify the same value as the length specified for each of the parameter pages, which will be explained later.

  • Page 166: Figure 3.31 Send Diagnostic Parameters: Logical/physical Address Conversion

    Command Specifications Byte X ‘40’ (Page Code) X ‘00’ (Page Parameter Length) X ‘0A’ (Page Parameter Length) Address Format Before Conversion Address Format After Conversion Logical or Physical Address Figure 3.31 SEND DIAGNOSTIC parameters: logical/physical address conversion The “Address Format Before Conversion” field shows the format of the address information specified in bytes 6 to 13.

  • Page 167

    3.4 Maintenance, Diagnostic Commands Logical unit Self-Test When "0" is specified in the "SelfTest" bit and the values other than zero is specified in the "SELF-TEST Code" field in CDB, the IDD executes the Self-Test specified in CDB. In this case, the INIT can read the executed results (page code= x10 : Self-Test Result Log Page) by the LOG SENSE command.

  • Page 168

    Command Specifications 3.4.2 RECEIVE DIAGNOSTIC RESULTS (1C) Byte X‘1C’ Transfer Byte Length (MSB) Transfer Byte Length (LSB) Link This command transfers data (response data) which show the results of executing the SEND DIAGNOSTIC command from the IDD to the INIT. The format and content of response data are determined by the parameter list (page code) specified by the INIT in the SEND DIAGNOSTIC command.

  • Page 169: Figure 3.32 Receive Diagnostic Results Command: Response Data Configuration

    3.4 Maintenance, Diagnostic Commands Figure 3.32 shows the format of response data transferred to the INIT from the IDD by this command. The response data are configured from a 4-byte “Page header” and the “Page parameters” which follow it. Byte Page Code Header Page Parameter Length (MSB)

  • Page 170: Figure 3.33 Receive Diagnostic Results Response Data: Page Code List

    Command Specifications Page code list This response data reports the “Page code” list of the parameter page supported by the IDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command after byte 4. The format and contents of this response data are shown in Figure 3.33. Byte X ‘00’...

  • Page 171

    3.4 Maintenance, Diagnostic Commands Note: The value of the “Page Parameter Length” field in this response data is a variable length within the range of [2 + 8n] in the SCSI specifications. For example, If multiple logical data blocks are located in 1 physical sector, or if 1 logical data block is located in multiple physical sectors, n address information items are reported as the address conversion results.

  • Page 172

    Command Specifications 3.4.3 WRITE BUFFER (3B) Byte X‘3B’ Mode Buffer ID Buffer Address (MSB) Buffer Address Buffer Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length (LSB) Link This command is used in combination with the READ BUFFER command to diagnose the normality of the IDD’s data buffer memory or the SCSI bus, or to download microcode to the IDD.

  • Page 173: Figure 3.35 Write Buffer Command: Buffer Data (mode = 000, 001)

    3.4 Maintenance, Diagnostic Commands “Mode Bit” Transfer Mode Header + Data, without Address Specification Header + Data, with Address Specification Data Only, with Address Specification Microcode Download, without Saving Microcode Download, with Saving Microcode Download with offset, without Saving Microcode Download with offset, and Saving Echo buffer Mode = 0, 0, 0, 0: Header + data, without address specification In this mode, a 4-byte header (with all zero’s specified for the contents) must be added to the top of the...

  • Page 174

    Command Specifications Mode = 0, 0, 0, 1: Header + data, with address specification The format of data transferred from the INIT in this mode must be the same as in the case of Mode = 0, 0, 0, 0, and the 4-byte header (with zero specified in all its contents) must be added to them. In this mode, the top address of the data buffer where the data transferred from the INIT are stored can be specified in the “Buffer address”...

  • Page 175

    3.4 Maintenance, Diagnostic Commands Note: Depending on the setting in the IDD, if done using the START/STOP command, it is necessary to issue the START command after issuing his command. See the description of the motor starting modes in Section 5.3.2 of the “Product Manual”...

  • Page 176

    Command Specifications The microcode or control information is written to the logical unit buffer starting at the location specified by the BUFFER Address field. If the IDD is unable to accept the specified buffer address, it shall return CHECK CONDITION status and it shall set the sense key to ILLEGAL REQUEST [=5] with an additional sense code of INVALID FIELD IN CDB [=24-00].

  • Page 177

    3.4 Maintenance, Diagnostic Commands 3.4.4 READ BUFFER (3C) Byte X‘3C’ Mode X‘00’ (Buffer ID) Buffer Offset (MSB) Buffer Offset Buffer Offset (LSB) Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length (LSB) Link This command is used in combination with the WRITE BUFFER command to diagnose the normalcy of the IDD’s data buffer memory and the SCSI bus.

  • Page 178: Figure 3.36 Read Buffer Command: Buffer Data (mode = 0000, 0001)

    Command Specifications The “Transfer byte count” field in the CDB specifies the total number of bytes of the header and buffer data which can be received by the INIT. The IDD reads the data from the data buffer from the top (Address X ‘000000’), then adds the 4-byte header to it and transfers it to the INIT.

  • Page 179: Figure 3.37 Read Buffer Command: Buffer Descriptor

    3.4 Maintenance, Diagnostic Commands The “Transfer byte length” field in the CDB specifies the total number of bytes of header and buffer data that can be received by the INIT. The IDD reads the data from the data buffer beginning from the byte position in the data buffer specified in the “Buffer offset”...

  • Page 180: Figure 3.38 Read Buffer Command: Echo Buffer Descriptor

    Command Specifications The "Addressing boundary" field in the buffer descriptor indicates the addressing boundary in the data buffer which can be specified in the WRITE BUFFER Command and the READ BUFFER Command as a "Power" when expressed as a "Power of 2." The IDDs report X'02' (=2 ), indicating that it is possible to specify the address in 4-byte units.

  • Page 181

    3.4 Maintenance, Diagnostic Commands 3.4.5 READ LONG (3E) Byte X‘3E’ CORRCT Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length (LSB) Link This command reads the logical data block data and its ECC byte, specified in the “Logical block address”...

  • Page 182

    Command Specifications Error recovery processing during execution of this command is in accordance with the specifications in (Page code 1: Read/Write Error Recovery Parameter, Page code 21: Additional error recovery parameters). • The ARRE flag and the DTE flag are not applied. •...

  • Page 183

    3.4 Maintenance, Diagnostic Commands • Sense key : 05 = ILLEGAL REQUEST • Additional sense code/ Additional sense code qualifier : 24-00 = Invalid field in CDB • “VALID” bit : “1” • “ILI” bit : “1” • Information field : (“Transfer byte length in the CDB) – (Original “Transfer byte length”) Remark The calculation formula for the information field expresses 1 logical data block as n physical sectors and n sub-sectors, and when negative, as a complement of 2.

  • Page 184

    Command Specifications The IDD is not supported a "PBdata" bit. Therefore, if "PBdata" bit is one, this command is terminated with CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00]). A "Relative Address (RelAdr)" bit of zero indicates that the "Logical Block Address" field specifies the first logical block of the range of logical blocks for this command.

  • Page 185: Chapter 4 Parameter Data Formats

    CHAPTER 4 Parameter Data Formats Mode Parameters Log Parameters This chapter describes detailed parameter data formats provided by the IDD and how to use them. Mode Parameters This clause describes the block descriptors and the pages used with MODE SELECT and MODE SENSE commands that are applicable to all SCSI devices.

  • Page 186

    Parameter Data Formats Byte X‘0A’ or X‘06’ (Page Length) (See the AWRE ARRE “Note”) Default Variable Number of retries during READ Default X‘3F’ (=63 times) Variable X‘FF’ Correctable Bit Length Default X 'FF' (MAWxxxx) / (MAXxxxx) (= over 255 bits) X‘00’...

  • Page 187

    4.1 Mode Parameters • READ • WRITE • READ EXTENDED • WRITE AND VERIFY (Write operation) • READ LONG • WRITE EXTENDED • SEND DIAGNOSTIC (Write/read test) • WRITE LONG a. AWRE (automatic write reallocation enabled) "1" : An "automatic alternate block allocation processing" operation is specified during execution of a write operation.

  • Page 188

    Parameter Data Formats f. PER (post error) "1" : When several errors (errors related to the disk drive), which were recovered from normally through the IDD's error recovery processing, have been detected, a CHECK CONDITION status is reported when execution of that command is completed. In the sense data generated at this time, the sense key indicates "RECOVERED ERROR [=1]"...

  • Page 189

    4.1 Mode Parameters Correctable bit length This parameter indicates the burst error length (bit length) which it is possible to apply data correction according to the ECC to. It is impossible to change this parameter from the INIT. The IDD disregards the value specified in this parameter and operates according to the "Default" value. k.

  • Page 190

    Parameter Data Formats n. Recovery time limit This parameter specifies the maximum time that can be used by the TARG for error recovery processing, as a 1ms constant. The value specified in this parameter is the maximum permissible time for error recovery processing for each individual command. When both this parameter and the "Number of retries"...

  • Page 191: Mode Parameters

    4.1 Mode Parameters Table 4.1 Combinations of error recovery flags (1 of 3) Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. If possible, data correction is executed afterward according to the ECC.

  • Page 192

    Parameter Data Formats Table 4.1 Combinations of error recovery flags (2 of 3) Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. If possible, data correction is executed afterward according to the ECC.

  • Page 193

    4.1 Mode Parameters Table 4.1 Combinations of error recovery flags (3 of 3) Error Recovery Procedure 1. When a correctable data check is detected, immediately, correction is executed according to the ECC. For data checks which cannot be corrected, rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count"...

  • Page 194

    Parameter Data Formats 4.1.2 Disconnect/reconnect parameters (page code = 2) The format of the page descriptor in this MODE SELECT parameter is shown in Figure 4.2. Byte (See the X‘0E’ or X‘0A’ (Page Length) "Note.") Buffer Full Ratio Default X‘00’ Variable X‘FF’...

  • Page 195

    4.1 Mode Parameters Note: If transfer of this page descriptor is required by the MODE SENSE or MODE SENSE EXTENDED command, the IDD reports X '0E' as the page length (byte 1). However, if either X '0E' or X '0A' is specified for the page length in the MODE SELECT command, the IDD regards it as if the correct page length was specified.

  • Page 196

    Parameter Data Formats Note: If the value specified for the "buffer full ratio" or the "buffer empty ratio" is not within double the integral boundary of the logical data block length, the IDD rounds up the specified value to the value which is the nearest data block boundary. Also, if zero is specified in any of these parameters.

  • Page 197

    4.1 Mode Parameters 00b= Perform disconnection according to the instructions of other parameters without using DTDC. 01b= When a data transfer by the command is started, the target will never try disconnection until transmission of all the data to be transferred by the command is completed.

  • Page 198

    Parameter Data Formats 4.1.3 Format parameter (page code = 3) The Page descriptor format of this MODE SELECT parameter is shown in Figure 4.3. Byte X‘16’ (Page Length) Track Count/Zone Default X‘xxxx’ Variable X‘0000’ Alternate Sector Count/Zone Default X '00F0' (MAWxxxx) or X '00C8' (MAXxxxx) Variable X‘FFFF’...

  • Page 199

    4.1 Mode Parameters a. Parameters for specifying alternate processing areas for defective blocks (bytes 2 to 9) The following 4 parameters specify the position and number of spare sectors for performing defective block alternate allocation processing on the disk media. See Chapter 3, "Data Format" of Product Manual for details of the IDD's alternate block processing.

  • Page 200

    Parameter Data Formats c. Parameters specifying sector format (bytes 12 to 19) • Data byte length/physical sectors This parameter specifies the data length per 1 physical sector as the number of bytes. In the IDD, the data byte length per 1 physical sector is the same as the data byte length in 1 logical data block.

  • Page 201: Figure 4.4 Mode Select Parameters: Each Parameters Of Pages 3, 4, And C In Detail

    4.1 Mode Parameters • HSEC (hard sectoring) When this bit is "1," it indicates that the data formatting method on the disk media is "hard sectoring." However, since the IDD uses only the "hard sectoring" method, this bit is disregarded. Furthermore, it is impossible to change this parameter. •...

  • Page 202

    Parameter Data Formats 4.1.4 Drive parameter (page code = 4) The page descriptor format of this MODE SELECT parameter is shown in Figure 4.5. Byte (See the X‘16’, X‘12’ or X‘0A’ (Page Length) "Note") Cylinder Count Default X‘xxxxxx’ Variable X‘000000’ Number of Heads Default X‘xx’...

  • Page 203

    4.1 Mode Parameters a. Cylinder count This parameter specifies the total number of cylinders configured in the user space on the disk media. This value includes the number of cylinders for alternate blocks specified in the "Alternate Track Count/Drive" parameter of the format parameters (Page code = 3). It is impossible to change this parameter.

  • Page 204

    Parameter Data Formats Byte (See the X‘0A’ (Page Length) Note.) (Reserved) Default Variable Number of retries during VERIFY. Default X‘3F’ Variable X‘FF’ Correctable Bit Length Default X 'FF' (MAWxxxx) / (MAXxxxx) (= over 255 bits) Variable X‘00’ X‘0000000000’ (Reserved) 10-11 Recovery Time Limit Default X‘7530’...

  • Page 205

    4.1 Mode Parameters b. Number of retries during VERIFY This parameter specifies the number of times reading of the disk media should be retried when a "Data Check" type error is detected in a read operation. the number of retries specified by this parameter is the maximum number of times reading of each individual data area in each logical data block is retried.

  • Page 206

    Parameter Data Formats Byte X‘0A’ or X‘12’ (Page Length) ABPF DISC SIZE Default Variable Demand Read Retention Priority Write Retention Priority Default Variable Pre-fetch inhibit block count Default X‘FFFF’ Variable X‘0000’ Minimum pre-fetch Default X‘0000’ Variable X‘0000’ Maximum pre-fetch Default X‘0000’...

  • Page 207

    4.1 Mode Parameters a. RCD (read cache disable) This bit can be specified, and its operation is as specified. This bit specifies whether or not to activate the cache operation for a read command. "1" : Prohibits operation of the Look-Ahead cache function. The IDD reads ahead all of the data requested by the READ command or READ EXTENDED command from the disk and transfers it to the INIT.

  • Page 208

    Parameter Data Formats d. SIZE (size enable) (not supported) "1" : Divides the data buffer in accordance with the value specified for the cache segment size (bytes 14, 15). "0" : Divides the data buffer in accordance with the value specified for the number of cache segments (byte 13).

  • Page 209

    4.1 Mode Parameters "F" : Data put into the cache during a WRITE or WRITE and VERIFY command was not replaced if there is ohter data in the cache that was placed into the cache by other means and it may be replaced.

  • Page 210

    Parameter Data Formats "1" : Requests that the device server not read into the buffer any logical blocks beyond the addressed logical blocks. "0" : The device server continues to read logical blocks into the buffer beyond the addressed logical blocks.

  • Page 211

    4.1 Mode Parameters segments need not be impacted by cache misses to perform the SCSI buffer function. The impact of this field equals 0 or the sum of this field plus this field greater than the buffer size is vendor- specific.

  • Page 212

    Parameter Data Formats a. TST (Task Set Type) This field specifies the type of task set defined below. Value Description 000b Task set per logical unit for all initiators 001b Task set per initiator per logical unit 010b-111b Reserved The IDD operates according to "000b". If other value is specified in this field, the IDD reports a "CHECK CONDITION"...

  • Page 213

    4.1 Mode Parameters d. RLEC (Report Log Exception Condition) (not supported) This bit controls operations in cases where the accumulated value log parameter reaches the maximum value. "1" : The IDD reports a CHECK CONDITION status (UNIT ATTENTION [=6] / Log counter at maximum [5B-02]).

  • Page 214

    Parameter Data Formats g. RAC (Report Check) (not supported) The IDD is not supported in this bit. Therefore, the IDD always report "0", and ignore specified value. h. SWP (Soft Write Protect) (not supported) This bit specifies whether or not to execute for the device server write operation to the medium. The IDD is not supported this bit.

  • Page 215

    4.1 Mode Parameters 4.1.8 Notch parameter (page code = 0C) Byte X‘16’ (Page Length) X‘00’ (Reserved) Default Variable X‘00’ (Reserved) Maximum number of notches Default X‘00xx’ Variable X‘0000’ Active Notch Default X‘0000’ Variable X‘FFFF’ 8-11 Starting Boundary Default X‘00000000’ Variable X‘00000000’...

  • Page 216

    Parameter Data Formats If this parameter is issued, only the format parameter of the zone specified by the MODE SENSE command can be referred to without changing the number of accessible blocks. Also, if a MODE SENSE command with a SP = "1" that includes a notch page is issued, the current value is reported for this page and the zone value which is the object is reported if Page 3 is notched, then the command is terminated normally.

  • Page 217: Figure 4.10 Mode Select Parameters: Port Control Parameter

    4.1 Mode Parameters • Starting Boundary This field is enabled by the MODE SENSE command. This field indicates the beginning of the active notch or, if the active notch is zero, the beginning of the logical unit (IDD). • Ending Boundary This field is valid in the MODE SENSE command.

  • Page 218

    Parameter Data Formats b. Protocol Identifier 1h: This shows that this page conforms to the SPI SCSI Device. c. Synchronous Transfer Timeout This specifies time monitoring starting and ending with the following events (time is specified in units of ms): The timer (count) is initialized and started when a new REQ is sent in a state in which the entire ACK response to an already sent REQ of the device has been completed.

  • Page 219

    4.1 Mode Parameters a. Subpage Code This shows the page code of a subpage used during Long Page Format specification. Subpage Code Parameter Support state Not allowed ------ Margin control subpage Supported Saved training configuration value subpage Supported Negotiated setting subpage Supported Report transfer capabilities subpage Supported...

  • Page 220

    Parameter Data Formats c. Protocol Specific Mode Parameters The subpage itself enters this area. (SubPage 01: Margin Control) Byte X ‘00’ (Reserved) Driver Strength Reserved Default Variable Driver Asymmetry Driver Precompensation Default Variable Driver Slew Rate Reserved Default Variable X ‘00’ (Reserved) Vendor Specific Default Variable...

  • Page 221

    4.1 Mode Parameters c. Driver Asymmetry (not supported) This shows the amplitude difference between the assert and negate signals sent from the driver. d. Driver Slew Rate This shows the result obtained by dividing the size difference between assertion and negation by the time difference between rising and falling.

  • Page 222

    Parameter Data Formats (SubPage 02: Saved Training Configuration) Byte X ‘00’ (Reserved) 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...

  • Page 223

    4.1 Mode Parameters (SubPage 03: Negotiated Setting) Byte Transfer Period Factor Default Variable X ' 00 '(Reserved) REQ/ACK Offset Default Variable Transfer Width Exponent Default Variable Protocol Option Bits Default Variable Reserved Transceiver SENT RCVD PCOMP_ PCOMP_ Mode Default Variable X ' 00 '(Reserved) This subpage is used to report the negotiation settings of the SCSI target port of the current I_T NEXAS.

  • Page 224

    Parameter Data Formats a. Transfer Period Factor This field indicates the transfer rate value for a transfer established by the current I_T NEXAS. Note: When an asynchronous transfer is established (REQ/ACK Offset is set to X'00'), the value reported by this parameter is not in effect and has no meaning. Period value Parameter 160 MHz...

  • Page 225

    4.1 Mode Parameters d. Protocol Option Bits This field indicates the protocol options established by the current I_T NEXAS. Bit name Parameter Precompensation enable PCOMP_EN (*1) Retain training information RD_STRM Read streaming and read flow control enable WR_FLOW Write flow control enable HOLD_MCS Hold margin control setting QAS_REQ...

  • Page 226

    Parameter Data Formats (SubPage 04: REPORT Transfer Capability) Byte Minimum Transfer Period Factor Default Variable X ‘00’ (Reserved) Maximum REQ/ACK Offset Default Variable Maximum Transfer Width Exponent Default Variable Protocol Option Bits Supported Default Variable X ‘00’ (Reserved) This subpage is used to report the transfer capability of the SCSI target port. Individual parameters cannot be changed by the Mode Select command.

  • Page 227: Informational Exceptions Control Page (page Code = 1c)

    4.1 Mode Parameters 4.1.10 Informational exceptions control page (page code = 1C) The page descriptor format of this MODE SELECT parameter is shown in Figure 4.9. Byte Page length (X’0A’) Perf EWASC DExcpt Test LogErr Default Variable MRIE Default Variable Interval Timer X‘00000000’...

  • Page 228

    Parameter Data Formats An enable warning (EWASC) bit of zero indicates the target disables reporting of the warning. The "MRIE" field is ignored when "DExcpt" is set to one and "EWASC" is set to zero. An "EWASC" bit of one indicates warning reporting is enabled. The method for reporting the warning when the "EWASC" bit is set to one is determined from the "MRIE"...

  • Page 229

    4.1 Mode Parameters Table 4.2 MRIE (Methods of reporting informational exception conditions) MRIE Descriptor X’00’ No reporting of informational exception conditions: This method instructs the target to not report informational exception conditions. X’01’ Asynchronous event reporting: This method instructs the target to report informational exception conditions by using the rules for asynchorous event reporting as described in the SCSI-3 Architecture Model and the relevant Protocol Standard.

  • Page 230

    Parameter Data Formats The "Interval Timer" field indicates the period in 100 millisecond increments for reporting that an informational exception condition has occurred. The target does not report informational exception conditions more frequency than the time specified by the "Interval Timer" field and as soon as possible after the timer interval has elapsed.

  • Page 231: Background Control Mode Parameter (page Code = 1c/subpage = 01)

    4.1 Mode Parameters 4.1.11 Background control mode parameter (page code = 1C/subpage = 01) Note: This parameter is not supported. When this parameter is set during MODE SELECT, this command is terminated with error. (ILLEGAL REQUEST [=5] / Invalid Field in Parameter List [=26/00] ) In MODE SENSE, this parameter is not transferred.

  • Page 232: Additional Error Recovery Parameters (page Code = 21)

    When zero is specified in this field, repositioning retries are prohibited. The value specified in this field is applicable for all commands which are accompanied by a seek operation. b. RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit. 4-48 C141-C010...

  • Page 233: Log Parameters, Supprot Log Page (x'00')

    4.2 Log Parameters Log Parameters This clause describes the log page structure and the log pages that are applicable to all SCSI devices. Pages specific to each device type are described in the command standard that applies to that device type. The LOG SENSE command returns a single log page specifed in the page code field of the command descriptor block.

  • Page 234: Buffer Overrun / Underrun Page (x'01')

    Parameter Data Formats 4.2.2 Buffer overrun / underrun page (X'01') Byte X‘00’ (Reserved) X'00' (Page Length) X'0C' (Page Length) X'00' (Reserved) Count Basis Cause Type LBIN X'02' (Parameter Length) X'0000' (Data Underrun) X'00' (Reserved) Count Basis Cause Type LBIN X'02' (Parameter Length) 14-15 X'0000' (Data Overrun) Cause...

  • Page 235: Write Error Count Page (x'02'), Write Errors Recovered Without Delays (page 02, Code 0000)

    4.2 Log Parameters • Data Underrun Count of data underruns which occur during write operation when a buffer empty condition prevents continued transfer of data to the media from the buffer. The drive does not support this field due to a hardware limitation. Zero is always reported. •...

  • Page 236: Write Errors Recovered With Possible Delays (page 02, Code 0001)

    Parameter Data Formats 4.2.3.2 Write errors recovered with possible delays (Page 02, Code 0001) Byte (MSB) X'0001' (Parameter code) (Errors Recovered With Possible Delays) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all recovered write errors that would not be reported to the initiator during write operations, because possible delay is incurred.

  • Page 237: Total Posted Recoverable Write Errors (page 02, Code 0003)

    4.2 Log Parameters 4.2.3.4 Total posted recoverable write errors (Page 02, Code 0003) Byte (MSB) X'0003' (Parameter code) (Total Posted Recoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all posted recovered (01/xx/xx) errors to the interface during write operations.

  • Page 238: Total Posted Unrecoverable Write Errors (page 02, Code 0006), Read Error Count Page (x'03')

    Parameter Data Formats 4.2.3.6 Total posted unrecoverable write errors (Page 02, Code 0006) Byte (MSB) X'0006' (Parameter code) (Total Posted Unrecoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all posted unrecovered errors (03/xx/xx) to the interface during write operations.

  • Page 239: Read Errors Recovered Without Delays (page 03, Code 0000)

    4.2 Log Parameters 4.2.4.1 Read errors recovered without delays (Page 03, Code 0000) Byte (MSB) X'0000' (Parameter code) (Errors Recovered Without Delays) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all recovered read errors. Because the IDD does not support this parameter, 0 is always reported.

  • Page 240: Total Posted Read Errors (page 03, Code 0002)

    Parameter Data Formats 4.2.4.3 Total posted read errors (Page 03, Code 0002) Byte (MSB) X'0002' (Parameter code) (Total Posted Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all posted errors to the interface during read operations. The value includes the count of all posted verify errors to the interface (page X'05', Parameter code X'0002').

  • Page 241: Total Read Bytes Processed (page 03, Code 0005)

    4.2 Log Parameters 4.2.4.5 Total read bytes processed (Page 03, Code 0005) Byte (MSB) X'0005' (Parameter code) (Total Bytes Processed) (LSB) LBIN X'0A' (Parameter Length) (MSB) Total Read Bytes Processed (10 bytes) (LSB) The Total Read Bytes Processed indicates the total processed bytes during read operation. The bytes includes the total processed bytes during verify operation.

  • Page 242: Verify Error Count Page (x'05'), Verify Errors Recovered Without Delays (page 05, Code 0000)

    Parameter Data Formats 4.2.5 Verify error count page (X'05') Byte X‘00’ (Reserved) Page Length (MSB) Page Length (LSB) All of the following parameters have this header. Page Length will be defined based on the value of Parameter Pointer. (CDB 5-6) 4.2.5.1 Verify errors recovered without delays (Page 05, Code 0000) Byte (MSB)

  • Page 243: Vefiry Errors Recovered With Possible Delays (page 05, Code 0001)

    4.2 Log Parameters 4.2.5.2 Vefiry errors recovered with possible delays (Page 05, Code 0001) Byte (MSB) X'0001' (Parameter code) (Errors Recovered With Possible Delays) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all recovered verify errors that would not be reported to the initiator during verify operations, because possible delay is incurred.

  • Page 244: Total Posted Recoverable Verify Errors (page 05, Code 0003)

    Parameter Data Formats 4.2.5.4 Total posted recoverable verify errors (Page 05, Code 0003) Byte (MSB) X'0003' (Parameter code) (Total Posted Recoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all posted recovered (01/xx/xx) errors to the interface during verify operations.

  • Page 245: Total Posted Unrecoverable Verify Errors (page 05, Code 0006), Non-medium Error Count Page (x'06')

    4.2 Log Parameters 4.2.5.6 Total posted unrecoverable verify errors (Page 05, Code 0006) Byte (MSB) X'0006' (Parameter code) (Total Posted Unrecoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) The Counter Value indicates the count of all posted unrecovered errors (03/xx/xx) to the interface during verify operations.

  • Page 246: Temperature Page (x'0d'), Temperature (page 0d, Code 0000)

    Parameter Data Formats The Counter Value indicates the count of all non-medium errors (01/xx/xx, 02/xx/xx, 04/xx/xx, 05/xx/xx, 06/xx/xx, 07/xx/xx, 09/xx/xx and 0B/xx/xx) posted to the interface. Implementation: If a non-medium error is posted, it will force a save of all error log pages information. 4.2.7 Temperature page (X'0D') Byte...

  • Page 247: Reference Temperature (page 0d, Code 0001), Start-stop Cycle Counter Page (x'0e')

    4.2 Log Parameters 4.2.7.2 Reference temperature (Page 0D, Code 0001) Byte (MSB) X'0001' (Parameter code) (Temperature) (LSB) LBIN X'02' (Parameter Length) X'00' (Reserved) Reference Temperature (degrees Celsius) The Reference Temperature reflect the maximum reported sensor temperature in degrees Celsius at which the device can operate continuously without degrading the device's operation or reliability outside the limits specified by the manufacturer of the device.

  • Page 248: Date Of Manufacture (page 0e, Code 0001), Accounting Date (page 0e, Code 0002)

    Parameter Data Formats 4.2.8.1 Date of manufacture (Page 0E, Code 0001) Byte (MSB) X'0001' (Parameter code) (Date of Manufacture) (LSB) LBIN X'06' (Parameter Length) (MSB) Year of manufacture (4 ASCII characters) (LSB) (MSB) Week of manufacture (2 ASCII characters) (LSB) The year and week in the year that the device was manufactured shall be set in the parameter field defined by parameter code 0001h.

  • Page 249: Specified Cycle Count Over Device Lifetime (page 0e, Code 0003)

    4.2 Log Parameters The Accounting date specified by parameter code 0002h is a parameter that may be savable using a LOG SELECT command to indicate when the device was placed in service. If the parameter is not yet set or is not settable, the default value placed in the parameter field shall be 6 ASCII blank characters (20h).

  • Page 250: Application Client Page (x'0f'), General Usage Application Client Parameter Data (page 0f, Code 0000-003f)

    Parameter Data Formats The Accumulated start-stop cycles is a parameter provided by the device sever. The accumulated start- stop cycles parameter shall not be savable by the application client using the LOG SELECT command. The parameter value is a 4-byte binary number. The value indicates how many start-stop cycles the device has detected since its date of manufacture.

  • Page 251: Self-test Result Page (x'10'), Self-test Result Parameter Data (page 10, Code 0001-0014)

    4.2 Log Parameters The values stored in the General usage parameter bytes represent data sent to the device server in a previous LOG SELECT command. If a previous LOG SELECT command has not occurred, the data is zero. 4.2.10 Self-test result page (X'10') Byte X‘00’...

  • Page 252: Table 4.3 Self-test Results Values

    Parameter Data Formats When the self-test is initiated, the value specified in the SELF-TEST CODE field in the CDB is reported to the SELF-TEST CODE field by a SEND DIAGNOSTICS command. The values reported to the “Self-Test Result Value” field are defined below. Table 4.3 Self-test results values Value...

  • Page 253: Background Medium Scan Page (x'15'), Background Medium Scan Status Parameter

    4.2 Log Parameters 4.2.11 Background medium scan page (X'15') Note: These parameters ("4.2.11.1 Background medium scan status parameter" and "4.2.11.2 Background medium scan parameter") are not supported. In LOG SENSE, these parameters are not transferred. Byte Page Length (MSB) Page Length (LSB) All of the following parameters have this header.

  • Page 254: Background Medium Scan Parameter

    Parameter Data Formats Value Description No medium scan Background medium scan in progress Pre-Scan in progress Halt the Medium Scan due to fatal error Halt the Medium Scan due to vendor specific pattern of errors Halt the Medium Scan due to medium formatted without the P-List Reserved Halt the Medium Scan due to Irregular Temperature condition Scan suspended until BMS Interval Timer...

  • Page 255: Smart Status Page (x'2f')

    IDD. The application client can check whether the IDD has predicted a drive failure by periodically reading out this page. The "Page Length" field indicates the length (byte length) after byte 4. The "SMART Status Parameter" field is Fujitsu unique parameters. The details of this field are outside the scope of this manual. C141-C010...

  • Page 256: Smart Data Page (x'38')

    This page reports data which the IDD collects for predicting drive failures. The "Page Length" field indicates the length (byte length) after byte 4. The "Log Parameters" field is Fujitsu unique parameters. The details of this field are outside the scope of this manual.

  • Page 257: Chapter 5 Sense Data Error Recovery Methods, Sense Data, Sense Data Format

    CHAPTER 5 Sense Data Error Recovery Methods Sense Data INIT Error Recovery Methods (Recommended) Disk Drive Error Recovery Processing In this chapter, the configuration and contents of sense data reported to the INIT (initiator) when an error occurs, etc., key information for interpreting error states, recommended procedures for error recovery processing that should be executed by software in the INIT and error recovery processing executed internally by the IDD are described.

  • Page 258: Sense Data Basic Information, Figure 5.1 Expanded Sense Data Format

    Sense Data Error Recovery Methods Byte Valid X ‘70’ or X ‘71’ (Error Code) X‘00’ Sense Key Information X ‘28’ (Additional Sense Data Length) Command Inherent Information Basic Information Additional Sense Code Additional Sense Code Qualifier X‘00’ SKSV Sense Key Inherent Information IDD SCSI ID CDB Operation Code Additional...

  • Page 259

    5.1 Sense Data Error code This field shows the format and type of sense data. The IDD always displays X ‘70’ (current error) or X ‘71’ (deferred error), which has the meaning “expanded sense data format” in this field. ILI (incorrect length indicator) When this bit is “1,”...

  • Page 260: Figure 5.2 Sense Key Inherent Information

    Sense Data Error Recovery Methods Additional sense code, additional sense code qualifier The codes which indicate the reason for the error displayed by the sense key in detail are reported in these fields. The INIT can decide procedures for error recovery according to the sense key and these fields.

  • Page 261

    5.1 Sense Data Table 5.1 Sense key Sense Name Explanation NO SENSE The specific sense key does not exist. RECOVERED 1) Indicates that the command which was executed last was terminated ERROR normally with a recovery operation by the IDD. If multiple errors which were successfully recovered from during processing of a single command occurred, the last error to have occurred is reported.

  • Page 262

    Sense Data Error Recovery Methods Table 5.2 Additional sense code and additional sense code qualifier (1 of 6) Sense Name Explanation No additional sense No specific additional sense code exists. information I/O process terminated I/O was interrupted by the Terminated I/O Process message. No index/sector signal The target sector was not detected by the sector counter within the specified time.

  • Page 263

    5.1 Sense Data Table 5.2 Additional sense code and additional sense code qualifier (2 of 6) Sense Name Explanation Unrecovered Read Error Unrecovered read error occurs during reading data field (LBA Miscompare Error detected by SCSI portion) Read retries exhausted Unrecovered error was detected during data read (retry out).

  • Page 264

    Sense Data Error Recovery Methods Table 5.2 Additional sense code and additional sense code qualifier (3 of 6) Sense Name Explanation Synchronous Data An errorr (timeout) was detected during synchronous data transfer Transfer Error on SCSI bus by Synchronous Transfer Timeout function. Primary defect list not found The defect list (P List) header is incorrect.

  • Page 265

    Operating definition was changed. definition Device identifier changed Device identifier was changed. Diagnostic failure on An error was detected in self-diagnosis. ("nn" is a Fujitsu unique component "nn" code) • 81: Buffer RAM compare error/bus error • 82: Program RAM compare error/bus error •...

  • Page 266

    Additional sense code and additional sense code qualifier (5 of 6) Sense Name Explanation Internal target failure An error was detected in self-diagnosis. ("nn" is a Fujitsu unique code) • 90: Next sector IDD compare error • 91: WCS RAM parity error • 92: Unexpected FMT interrupt •...

  • Page 267

    RELEASE EXTENDED commands cannot be executed. Drive Failure A serious error was detected in the drive's control system. ('nn' is a Fujitsu unique code) • 00: Abnormal Rotation of Spindle Motor • 01: Any error at Spindle Motor Start • 30: On track failure...

  • Page 268: Sense Data Additional Information, Init Error Recovery Methods (recommended)

    Sense Data Error Recovery Methods 5.1.3 Sense data additional information Bytes 18 to 47 of sense data are defined as a Fujitsu unique field, and indicate the additional information which is explained below. IDD SCSI ID This field shows the SCSI ID of the very IDD which generated the sense data.

  • Page 269: Figure 5.3 Analysis Of The Termination Status

    5.2 INIT Error Recovery Methods (Recommended) Command issue status received ? Normal end GOOD BUS FREE error ? To item (1) BUSY Timeout ? TASK SET To item (1) FULL PRESERVATION To item (2) CONFLICT See item (3). See item (4). Issue of REQUEST SENSE command To Section 4.3.2...

  • Page 270

    Sense Data Error Recovery Methods RESERVATION CONFLICT status This status shows, under a multi-initiator environment, that the IDD is currently reserved by another INIT, and cannot be used until that reserved status is released. The period over which the reserved status continues should be managed by the system, but normally, an INIT that receives this status reissues the original command after waiting an appropriate length of time.

  • Page 271: Sense Data Analysis And Error Recovery Methods

    5.2 INIT Error Recovery Methods (Recommended) The cause of this error is the occurrence of an unrecoverable error on the SCSI bus, the occurrence of a serious protocol error, etc. For details concerning the causes of errors, see Chapter 3, "SCSI Bus Error Recovery Processing"...

  • Page 272

    Sense Data Error Recovery Methods Table 5.3 Sense data error classification (2 of 4) Recovery Method Outline of Error (See Table 5.4.) Unrecovered read error Need Sync byte not found for data field No record found These errors were detected during accessing of the disk media, but they were errors which could not be recovered from through the IDD's retry processing.

  • Page 273

    5.2 INIT Error Recovery Methods (Recommended) Table 5.3 Sense data error classification (3 of 4) Recovery Method Outline of Error (See Table 5.4.) Invalid command operation code None Logical block address out of range Invalid field in CDB Logical unit not supported Invalid field in parameter list There is an error in the command specification contents.

  • Page 274

    Sense Data Error Recovery Methods Table 5.3 Sense data error classification (4 of 4) Recovery method Error contents (See Table 5.4.) Overlapped commands attempted None Before execution of a command was completed, a new command was issued by the same INIT. Tagged overlapped commands Miscompare during verify operation None...

  • Page 275

    5.2 INIT Error Recovery Methods (Recommended) Table 5.4 Error recovery processing procedures (2 of 5) Recovery Recovery Processing Procedure Method After waiting about 1 second, reissue the original command (Retry). If it doesn't recover after 10 retries, perform recovery method 1. Reissue the original command.

  • Page 276

    Sense Data Error Recovery Methods Table 5.4 Error recovery processing procedures (3 of 5) Recovery Recovery processing procedure method Set the "Number of Retries" value in the MODE SELECT parameters at the "Default" value. Reissue the original command (Retry). (Note) If the error is not recovered from after the first retry, issue the REZERO UNIT command.

  • Page 277

    5.2 INIT Error Recovery Methods (Recommended) Table 5.4 Error recovery processing procedures (4 of 5) Recovery Recovery processing procedure method Issue the MODE SENSE or MODE SENSE EXTENDED command and confirm the values of the disk media data format related parameters (Block descriptor, Page 3: Format parameters, Page 4: Drive parameters).

  • Page 278: Error Logging

    Sense Data Error Recovery Methods Table 5.4 Error recovery processing procedures (5 of 5) Recovery Recovery processing procedure method Issue the LOG SENSE command and read the "Current" values of the LOG SELECT parameters. Search for any parameter values which exceed the threshold value or have reached the maximum value, then issue the LOG SELECT command from the INIT and perform resetting.

  • Page 279: Disk Drive Error Recovery Processing, Error States And Retry Processing Procedures

    5.3 Disk Drive Error Recovery Processing Disk Drive Error Recovery Processing This section explains concerning error recovery processing methods and procedures executed by the IDD for each type of disk drive related error. The INIT can control the error recovery processing methods executed by the IDD using the MODE SELECT parameters.

  • Page 280: Auto Alternate Block Allocation Processing

    Sense Data Error Recovery Methods If error correction is permitted but immediate correction is not permitted (DCR = 0, EER = 0), reading of data as in item (2) is retried up to the number of times specified in the other MODE SELECT parameters ("Number of Retries during Read"...

  • Page 281

    5.3 Disk Drive Error Recovery Processing Remark: When this function is specified (ARRE = "1"), the EER flag's specification in the MODE SELECT parameter is made invalid and Read retry processing is performed up to the number of times specified in the "Number of Retries during Read" parameter. If "0" is specified in the DCR flag, correction processing of the data is performed afterward (see Section 5.3.1 (3)).

  • Page 282: Error Recovery Processing Control

    Sense Data Error Recovery Methods Sectors to be made AWRE shall be following: • the sector where the error occurs and the latter sectors and, • the sectors whose data are logically continual and stored in Cache, • the sectors which will be processed in this Write command and, •...

  • Page 283

    5.3 Disk Drive Error Recovery Processing b. Verify Error Recovery Parameters (Page Code = 7) • (enable early recovery) • (post error) • (disable transfer on error) • (disable correction) • Number of retries during verify (See Table 5.5) c. Additional Error Recovery Parameters (Page Code = 21) •...

  • Page 284

    Sense Data Error Recovery Methods This page is intentionally left blank.

  • Page 285: Chapter 6 Disk Media Management, Defect Management

    CHAPTER 6 Disk Media Management Defect Management Disk Media Initialization Data Block Verification Methods (Recommended) Alternate Block Allocation Processing In this chapter, disk media defect management methods, treatment methods for media defects which occur during operation, reinitialization procedures and other disk media management methods are discussed. Furthermore, see Chapter 3, "Data Format"...

  • Page 286

    Disk Media Management Alternate block allocation Alternate data blocks are allocated in defective sector units for defective data blocks (= sectors) on the disk media by the IDD's internal defect management methods. a. Spare sector area Spare sectors for allocation as alternate blocks are secured in both of the following areas or alternate cell.

  • Page 287: Disk Media Initialization, Initialization During Installation

    6.2 Disk Media Initialization • Alternate block allocation processing during FORMAT UNIT command execution With the FORMAT UNIT command, alternate block allocation is done by sector slip processing until all the spare sectors within the same cell have been used up for defective sectors included in the type of defect list (P, G or D) specified in the command.

  • Page 288

    Disk Media Management Issuing the MODE SELECT command The MODE SELECT or MODE SELECT EXTENDED command is issued and the format attributes on the disk media are specified. The necessary parameters at this time are as follows. a. Block descriptor The logical data block size (byte length) is specified in the "Data block length"...

  • Page 289: Re-initialization

    6.2 Disk Media Initialization 6.2.2 Re-initialization The INIT can reinitialize the disk drive after it has been operated using the FORMAT UNIT command. Note: If it is necessary after reinitialization to restore the data that were stored on the disk media, it is necessary to save the data before executing reinitialization, then execute data restore using system software after reinitialization.

  • Page 290: Data Block Verification Methods (recommended)

    Disk Media Management Data Block Verification Methods (Recommended) The recommended procedure for verifying from the INIT the normalcy of logical data blocks located on the disk media is as shown below. It is desirable for the INIT to verify the data blocks after initialization of the disk media is completed or when executing alternate block allocation processing by the REASSIGN BLOCKS command.

  • Page 291: Alternate Block Allocation Processing

    6.4 Alternate Block Allocation Processing Reading and verification of data Issue the READ, READ EXTENDED or VERIFY command and verify that the data written to the disk media in item (2) were read correctly. To verify reading of data, it is recommended that reading of the same data block be done at lease 2 times, but the number of times verification is performed is determined by the conditions on the system.

  • Page 292

    Disk Media Management The alternate block allocation history (defect position information) is registered as an addition to the defect list (G List). Therefore, when reinitializing the hard disk with the FORMAT UNIT command (see Section 6.2.2), if use of the G List is specified, defect processing can be performed which reflects the operation results up to that time.

  • Page 293: Glossary

    Glossary Additional Sense Code This is a 1-byte code displayed in the sense data and is information which specifies the type of error that was detected. Axial acceleration Acceleration in the recording layer along the line perpendicular to the disk reference surface at a specified rotation speed.

  • Page 294

    Glossary Disconnect This is processing which temporarily frees the connected state of the target with the SCSI bus and the initiator at the point in the target's command processing execution process when operations on the SCSI bus are not needed. Initiator (INIT) This is a SCSI device which initiates input and output operations on the SCSI bus.

  • Page 295

    Glossary Sense Data When several items of error information are included in a command's completion status, this is information generated by the target for reporting detailed information on that status. Sense Key This is a 4-bit code displayed in the sense data. It contains information for classifying the type of error that was detected.

  • Page 296

    This page is intentionally left blank.

  • Page 297: Acronyms And Abbreviations

    Acronyms and Abbreviations Acknowledge Least significant byte Attention Logical unit number American Wire Gauge Most significant byte Busy Message Control/data Original equipment manufacturer Common command set Common descriptor block Request Reset Data bus Data Bus Parity Direct current SCSI Small Computer System Interface SDTR Synchronous data transfer request Select...

  • Page 298

    This page is intentionally left blank.

  • Page 299

    Index 10-byte cdb basic format........1-2 background control mode parameter ....4-47 12-byte cdb basic format........1-2 background medium scan page......4-69 6-byte cdb basic format........1-1 background medium scan parameter ....4-70 background medium scan status parameter ..4-69 basic disconnect processing procedure .... 1-13 bit 6 ..............

  • Page 300

    Index changed operating definition......1-20 management ..........2-1 CHECK CONDITION status ......1-7 data byte length/physical sector .......4-16 clocking field............3-8 data defect list ..........3-82 CmdDt ..............3-3 data only, with address code specification ........3-112, 3-117 0000 ............4-51 data overrun .............4-51 0001 ............4-52 data space configuration........1-31 0002 ............4-52 data strobe offset count ........4-5 0003 ............4-53...

  • Page 301

    Index disconnecting during a data transfer ....1-13 discontinuity.............4-24 fair arbitration ..........4-13 disk drive error fatal hardware error.......... 1-29 and number of retry ........5-27 force sequential write........4-26 recovery processing ........5-23 force unit access..........3-72 disk media format command ..........3-81 initialization..........6-3 format option valid...........

  • Page 302

    Index informational exception control .......4-43 microcode download informational exceptions control page .....4-43 with offset, with saving ......3-114 INIT error recovery method ......5-12 with offsets, without saving......3-113 initialization during installation......6-3 with saving ..........3-113 initiator control enable ........4-24 minimum pre-fetch...........4-25 INQUIRY ............3-2 mode = 0, 0, 0, 0 .........3-111, 3-115 command ............1-21 mode = 0, 0, 0, 1 .........3-112, 3-116...

  • Page 303

    Index parameter related to device type ...... 4-16 parameter specification ........3-101 operation code ..........1-3, 3-3 parameter specifying operation if formatting is not completed sector format..........4-16 normally ............1-26 track format ..........4-15 operation mode........3-12, 3-16 paramter code........... 3-53 setting ............2-5 PER ..............

  • Page 304

    ......3-44 read continuous ..........4-3 reserve right and third party reserve READ DEFECT DATA ........3-94 function ............3-44 command (37)..........3-95 reserved by Fujitsu ...........4-48 command (B7) ..........3-99 reserved operation code ........1-24 READ DEFECT DATA (B7)......3-98 reset processing ..........1-28 read error during write ..........1-29...

  • Page 305

    Index command ..........3-102 superseding reserve.......... 3-44 parameter ........3-103, 3-104 support ............... 3-9 sense command ..........3-1 supported function ..........3-6 sense data ............5-1 supprot log page..........4-49 additional information ........5-12 SURF ............... 4-17 analysis and error recovery method....5-15 surface addressing..........4-17 basic information ..........5-2 SWP ..............

  • Page 306

    Index WP bit ..............3-36 WRITE.............3-73 Unit Attention condition WRITE AND VERIFY ........3-75 multiple hold..........1-22 WRITE BUFFER ...........3-110 UNIT ATTENTION condition......1-19 command ..........3-111 UNIT ATTENTION report mode ....3-17 write cache ............2-11 unrecoverable hardware error......1-29 enable ............4-23 untagged queuing ..........1-16 write error count page ........4-51 UNTATN ............3-17 write error recovered user space logical block address.......1-32...

  • Page 307

    Your comments or suggestions on this document are cordially solicited. For any comments and suggestions you may have, please complete and submit this form to your FUJITSU representative. The comments and suggestions will be used in planning future editions. Thank you for your cooperation.

  • Page 308

    This page is intentionally left blank.

Comments to this Manuals

Symbols: 0
Latest comments: