Page 1 MAA3182SC, MAB3091SC INTELLIGENT DISK DRIVES OEM MANUAL – SCSI LOGICAL INTERFACE SPECIFICATIONS – C141-E039-01EN...
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 damange to their property. Use the product according to this manual.
Page 3 COMMON COMMAND SET (CCS) of American National the Small Computer System Interface Standards Institute (SCSI) (ANSI) X3T9.2 855D Rev 12 WORKING DRAFT Information American National Technology SCSI-3 Parallel Interface Standards Institute (ANSI) All Rights Reserved, Copyright © 1997 Fujitsu, Limited C141-E039-01EN...
Page 4 REVISION RECORD Edition Date Revised contents published May.,1997 Specification No.: C141-E039-**EN The contents of this manual is subject to change without prior notice. All Rights Reserved. Copyright © 1997 FUJITSU LIMITED C141-E039-01EN...
Page 6: Chapter 4 Sense Data And Error Recovery Methods
PREFACE This manual explains concerning the MAA3182SC and MAB3091SC 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 7 Glossary The glossary explains technical terms which are necessary to the reader’s understanding when reading this manual. List of 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 8 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-E039-01EN...
Page 10 Manual Organization 1. Outline Product Manual 2. Specifications 3. Data Format 4. Installation Conditions 5. Installation Procedure 6. Diagnosis and Maintenance 1. SCSI Bus SCSI Physical 2. SCSI Messages Interface Specifications 3. SCSI Bus Error Recovery Processing SCSI Logical Interface 1.
Page 12: Table Of Contents
CONTENTS page CHAPTER 1 COMMAND PROCESSING............1-1 Command Format ......................1-1 Status Byte ........................1-7 Outline of Command Processing ..................1-10 1.3.1 Single Commands......................1-10 1.3.2 Command Link........................1-11 1.3.3 Disconnect/Reconnect Procedure..................1-13 1.3.4 Synchronous Mode Data Transfer/Wide Mode Data Transfer..........1-17 Command Queuing Function ..................1-19 1.4.1 Untagged Queuing......................1-19 1.4.2...
Page 13 Look-ahead Cache Mechanism ..................2-7 2.2.1 Caching Operation......................2-7 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)....................3-1 3.1.2 INQUIRY (12) .......................3-2 3.1.3 READ CAPACITY (25) ....................3-11 3.1.4 CHANGE DEFINITION (40) ..................3-13 3.1.5...
Page 14 Maintenance, Diagnostic Commands................3-113 3.4.1 SEND DIAGNOSTIC (1D).....................3-113 3.4.2 RECEIVE DIAGNOSTIC RESULTS (1C)..............3-119 3.4.3 WRITE BUFFER (3B)....................3-123 3.4.4 READ BUFFER (3C)......................3-127 3.4.5 READ LONG (3E) ......................3-131 3.4.6 WRITE LONG (3F) .......................3-133 CHAPTER 4 SENSE DATA AND ERROR RECOVERY METHODS ... 4-1 Sense Data ........................
Page 15 List of Figures and Tables < Figures > Fig. 1.1 Basic Format of 6-byte CDB......................1-2 Fig. 1.2 Basic Format of 10-byte CDB....................1-2 Fig. 1.3 Status Byte..........................1-7 Fig. 1.4 Data Space Configuration......................1-38 Fig. 2.1 Data Buffer Configuration (In the case of 4 cache se gments)............2-2 Fig.
Page 16 Fig. 3.26 SEND DIAGNOSTIC Parameters: Page Code List..............3-117 Fig. 3.27 SEND DIAGNOSTIC Parameters: Logical/Physical Address Conversion......... 3-117 Fig. 3.28 RECEIVE DIAGNOSTIC RESULTS Command: Response Data Configuration .......3-120 Fig. 3.29 RECEIVE DIAGNOSTIC RESULTS Response Data: Page Code List........3-121 Fig. 3.30 RECEIVE DIAGNOSTIC RESULTS Response Data: Logical/Physical Address Conversion..................3-121 Fig.
Page 18: Chapter 1 Command Processing
CHAPTER 1 COMMAND PROCESSING Command Format Status Byte Outline of Command Processing Command Queuing Function UNIT ATTENTION Conditions Sense Data Maintenance State Command Processing Exceptions 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 19 Byte Operation Code Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Data Length Control Byte Fig. 1.1 6 Byte CDB Basic Format 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...
Page 20 Operation code Bit 7 Group Code Command Code The top 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 21 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” and the latter is called the “transfer byte length”...
Page 22 Control Byte Bit 7 Flag Link a. Link Command link is specified by this bit is “1.” Details of the operation of the command link are described in item 1.3.2. b. Flag This bit is valid only when “1” is specified in the Link bit. If “0” is specified in the Link bit, “1”...
Page 23 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, that command ends with a CHECK CONDITION status. In the case of a command to change the data on the disk media, when there is an error in the CDB’s specifications, the disk media is not changed by that command, but when there is an error in the parameters transferred in the DATA OUT phase, the contents of the disk media in the range specified by the command may be changed.
Page 24: Status Byte
Status Byte Fig. 1.3 shows status byte format and the type of status the IDD supports. The status byte 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.
Page 25 GOOD Status This status indicates that execution of the command ended normally. 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 displays the detailed cause. The INIT issues a REQUEST SENSE command when it receives this status and should sample sense data.
Page 26 INTERMEDIATE Status This status indicates that a command which specifies a link (except the final command in a group of linked commands with “1” as its Link bit) has been completed normally. If a command which specifies a link is completed abnormally and the CHECK CONDITION status or RESERVATION CONFLICT status is reported, the command link is broken an the subsequent linked commands are not executed.
Page 27: Outline Of Command Processing
Outline of Command Processing 1.3.1 Single Commands Some processing examples of single commands which are the most basic operations on the SCSI bus are shown below. Furthermore, if disconnect processing is permitted, it may be accompanied by disconnect/reconnect processing during the interval until execution is completed, depending on the type of command, but this operation is omitted in the following explanation.
Page 28: Command Link
1.3.2 Command Link The command link function is a function which causes the TARG to execute continuous processing of multiple commands. Some examples of command link processing are shown below. 1) The INIT sets the command’s initial values in the command pointer, data pointer and status pointer.
Page 29 Table 1.1 Responses to Link Specification Commands Flag End Status Status Message Link Function Completed INTERMEDIATE LINKED COMMAND Effective Normally COMPLETE Completed INTERMEDIATE LINKED COMMAND Effective Normally COMPLETE WITH FLAG × Completed CHECK COMMAND COMPLETE Not Effective Abnormally CONDITION Conditions Met INTERMEDIATE LINKED COMMAND Effective...
Page 30 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 temporarily returns the SCSI bus to the BUS FREE phase by disconnect processing, making it possible for the TARG to execute the command internally.
Page 31 Table 1.2 Types of Command and Disconnect Processing (1 / 2) Commands which execute disconnect processing. (Note 2) Commands which are not objects of disconnect processing. (Note 1) CHANGE DEFINITION (40) FORMAT UNIT (04) INQUIRY (12) LOG SENSE (4D) MODE SELECT (15) MODE SELECT EXTENDED (55)
Page 32 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 33 Note In disconnect processing in this case, transfer of all the data accompanying execution of the command is completely 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 34: Synchronous Mode Data Transfer/Wide Mode Data Transfer
For further details, refer to CHANGE DEFINITION parameter list (Reselection Retry, Reselection Time-out Delay) in item 3.1.4 and SCSI Bus (RESELECTION Phase) in Chapter 1 of “SCSI Physical Interface Specifications” and SCSI Bus Error Recovery Processing in Chapter 3. 1.3.4 Synchronous Mode Data Transfer/Wide Mode Data Transfer The IDD is equipped with a synchronous mode data transfer function and wide mode data transfer function for processing high speed data transfers (DATA IN and DATA OUT phases)
Page 35 Note: When the INIT issues the first command after the TARG’s power is switched on, or after a RESET condition occurs, it can send the WIDE DATA TRANSFER REQUEST message and the SYNCHRONOUS DATA TRANSFER REQUEST message. However, when the TARG is set internally on a data transfer mode established previously by a BUS DEVICE RESET message issued by another INIT, generally, the INIT is not aware of it.
Page 36: Command Queuing Function
Command Queuing Function The IDD is equipped with a command queuing function. Through queuing of commands, the IDD can receive multiple commands in advance and execute them. There are two methods used in the queuing function, tagged and untagged. In tagged queuing, it is possible for the IDD to receive multiple commands from each INIT.
Page 37 • If disconnect processing is impossible. If disconnect processing is impossible because the INIT which issued the command does not meet the conditions for permitting a disconnect (see item 1.3.3), or if the DISCONNECT message is rejected by the INIT even though it meets the conditions for permitting a disconnect, when another command is already being executed, or if another command is already being executed or queuing is currently being executed, or when the initial self- diagnosis is being executed, except in cases covered in 1), the IDD responds with a BUSY...
Page 38: Tagged Queuing
1.4.2 Tagged Queuing Through the tagged queuing function, the IDD can receive multiple commands from the same INIT or from different INITs until the command queue is full. The number of commands that it is possible to receive by the IDD is 128 maximum, without relation to the INIT. When the IDD receives a new command, if the command queue is full, it responds to the new command with the QUEUE FULL status.
Page 39 The INIT can specify 2 error recovery options by the QErr bit of the control mode parameter (Page A) of the mode select parameters. When “0” is specified in the QErr bit, the IDD enters any one of a number of sense hold states, and when this state is cleared, it continues to execute the commands in the queue.
Page 40: Unit Attention Condition
UNIT ATTENTION Condition The UNIT ATTENTION condition is a function used to notify the INIT asynchronously of an event (status change) that has occurred in the TARG or logical unit. 1.5.1 Generation of the UNIT ATTENTION Condition Events which cause a UNIT ATTENTION condition to be generated are one of the following. When Power on, RESET or BUS DEVICE RESET occurs If the IDD’s power is switched on, enters the RESET condition or is reset by a BUS DEVICE RESET message, this UNIT ATTENTION condition is generated for all the INITs, regardless...
Page 41 RPL (rotational position locking) Status Change If one of the events below related to disk rotational synchronization occurs, the UNIT ATTENTION condition is generated for all INITs. • Spindle synchronized When rotational synchronization, started by the specification in the MODE SELECT or MODE SELECT EXTENDED command (Page 4: Drive parameter), is completed.
Page 42: And Cancellation Conditions
1.5.2 Response to the UNIT ATTENTION Condition Hold State and Cancellation Conditions A UNIT ATTENTION condition generated by the IDD by the occurrence of the previously mentioned events is held individually for each INIT and it is held until it is cleared by the INIT it is held for issuing the commands specified below.
Page 43: Unit Attention Condition Multiple Hold
REQUEST SENSE Command One or the other of the following operations is performed depending on whether or not the IDD is in the sense data hold state (shown in item 1.6). a. In the case of a Sense Data Hold State The IDD executes the REQUEST SENSE command normally and sends the sense data which are being held to the INIT.
Page 44: Sense Data Hold State
Sense Data Hold State 1.6.1 Sense Data Hold Condition The IDD generates sense data if any of the following conditions occurs and enters the sense data hold state until the conditions for cancellation, described in item 1.6.2, are established. The sense data which are generated, are held for each individual INIT that issued the applicable command.
Page 45: Response To The Sense Data Hold State And Cancellation Conditions
1.6.2 Response to the Sense Data Hold State and Cancellation Conditions state The response of the IDD when it receives a new command while it is in the sense data hold state, and conditions for canceling the sense data hold state are shown below. 1) If issued for the logical unit in the sense data hold state by the INIT which is the object of sense data holding.
Page 46: Command Processing Exceptions
Command Processing Exceptions 1.7.1 Overlapping Commands If the following state occurs, the IDD recognizes that overlapping commands have been generated and the command is terminated abnormally. 1) If the IDD is executing an untagged command, or an untagged command is in the queue, and the initiator that issued that command issues either an untagged command or a tagged command before execution of the previous command is completed.
Page 47: Illegal Lun Specification
1.7.3 Reserved Operation Code Group 7 command operation codes (X ‘EO’ to X ‘FF’) are reserved by Fujitsu. When any command is issued which includes these operation codes, the IDD always must respond with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid command operation code [=20-00].
Page 48 General Response when in the Not Ready State The IDD reports a CHECK CONDITION status for a command, except in cases where the command is one of the commands in item (2). The sense data generated at this time depends on the state of the IDD, as shown in Table 1.3.
Page 49: Error Recovery Processing
Operation if Formatting is Not Completed Normally If, while the FORMAT UNIT command is not being executed following a change in data format related parameters by the MODE SELECT command, the FORMAT UNIT command is terminated abnormally for any reason (Example: power cut off or RESET condition), the data on the disk media cannot be accessed normally.
Page 50 Recovery Processing for Errors on the SCSI Bus The IDD does not perform recovery processing for error detected on the SCSI bus. When error recovery is impossible, or when a major error related to SCSI bus protocols is detected, the IDD may transfer the SCSI bus forcibly to the BUS FREE phase and clear the command that is currently being executed.
Page 51: Reset Processing
1.7.6 Reset Processing The means which the INIT can use to reset the SCSI bus are shown below. • RESET Condition • BUS DEVICE RESET Message • CLEAR QUEUE Message • ABORT Message • ABORT TAG 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 52: Table 1.6 Reset Processing During Write
Table 1.6 Reset Processing During Write Type of Command Processing to Halt 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 SEND DIAGNOSTIC (Write/Read Test) when that processing is completed.
Page 53: Fatal Hardware Errors
1.7.7 Fatal Hardware Errors Self-diagnostic Errors If a fatal error is detected in the hardware in the initial self-diagnosis, in off-line self diagnosis or in on-line self-diagnosis (SEND DIAGNOSTIC command), rotation of the spindle motor will be halted. When in this state, the IDD reports the CHECK CONDITION status for all input/output operation requests except the REQUEST SENSE command.
Page 54: Data Block Addressing
Data Block Addressing 1.8.1 Definition of Data Space The IDD manages the data storage area on the disk drive in the following 2 types of data space. • User Space: User Data Storage Area • System Space: IDD Exclusive Area Of these 2 areas the user can clearly access the user space.
Page 55 Sector 0 1 2 3 Cylinder -22 System cylinder x = 14 System space Cylinder -9 System cylinder 1 Track 0 Track 1 Cylinder 0 Spare sectors for each cylinder Primary cylinder = 0 Cylinder 1 Primary cylinder = 1 User space Primary cylinder = p-q Cylinder p-q...
Page 56: Logical Block Addressing
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 adds correspondence between each physical sector and each logical data clock address during formatting.
Page 58: Chapter 2 Data Buffer Management
CHAPTER 2 DATA BUFFER MANAGEMENT Data Buffer Read-Ahead Cache Mechanism 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 496 Kbyte data buffer, which makes it possible to efficiently...
Page 59 Data Buffer (512 KB FIFO) Buffer 3 Buffer 2 Buffer 1 Buffer 0 Disk Media Valid Data INIT Write→ Write→ ←Read ←Read (If data buffer 0 is selected) Figure 2.1 Data Buffer Configuration (In the case of 4 cache segments) The basic functions and operations of the data buffer in a read operation and a write operation are shown below.
Page 60 Note: In order to avoid frequent repetition of the disconnect/reconnect processing after data transfer starts on the SCSI bus, and escape the occurrence of data overruns, it is necessary to set the buffer full ratio (see item 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 61 4) After disconnect processing, if all the blocks of data specified in the command have not yet been transferred by the INIT, as writing of data to the disk media progresses, at the point when the empty space in the data buffer reaches the amount specified in the buffer empty ratio in the MODE SELECT parameter, the IDD performs reconnection processing and begins transferring the succeeding data (data pre-fetch).
Page 62: Setting The Operating Mode
2.1.2 Setting the Operation Mode 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 Fig.
Page 63 For example, if a read operation of 16 blocks with a logical data block length of 512 bytes (8 Kbytes) is requested, when the value specified in this parameter is 32, reconnection processing is performed when it becomes possible to transfer 2 blocks of data [16 x (32/256)], from the data buffer.
Page 64: Caching Operation
Look-Ahead Cache Feature In order to use the data buffer more effectively and improve the disk drive's effective access speed, the IDD is equipped with a simple cache feature called a "Look-Ahead Cache Feature." The Look-Ahead cache feature is an effective, simple cache function for an INIT which reads data block groups on the disk media sequentially using multiple commands.
Page 65 b) Data which have been hit by the READ or READ EXTENDED command and transferred to the INIT once are also objects of caching as long as they are not invalidated. c) Data transferred from the INIT and written to the disk media by the WRITE, WRITE EXTENDED, WRITE AND VERIFY or other data writing command are not objects of caching.
Page 66: Caching Parameters
2.2.2 Caching Parameters The IDD supports the MODE SELECT parameters (caching parameters: page code = 8) shown in Fig. 2.5 for controlling the cache feature. See item 3.1.5 concerning details of the MODE SELECT parameters. [Caching Parameters (Page Code = 8)] Byte Page Length X‘0A’...
Page 67: Look-Ahead Operation, Look-Ahead Volume
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 68: 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 statement and terminates the command.
Page 70: Chapter 3 Command Specifications
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 71: Inquiry (12)
3.1.2 INQUIRY (12) Byte X‘12’ EVPD Page Code Transfer Byte Length Flag Link This command transfers the information showing the IDD's characteristics (INQUIRY Data) to the INIT. This command is executed immediately without queueing in a system which issues only commands with no tags or links. This command is executed normally even in cases where the UNIT ATTENTION condition is held, and the UNIT ATTENTION condition is not cleared.
Page 72 If bytes 1 and 0, the "EVPD (enable vital product data)" bits, and byte 2, the "Page code" field in the CDB are enabled only in the case that transfer of the SCSI-2 mode's INQUIRY data is specified. In the case of the SCSI-1/CCS Mode, zero must be set in these bits and in this field. If the specification in the "EVPD"...
Page 73 (*1) RelAdr WBus32 WBus16 Sync Linked CmdQue SftRe (*2) FUJITSU (vendor ID: ASCII) (Product ID: ASCII) Microcode Version No. (ASCII) (Product Revision: ASCII) Device Serial No. (ASCII) X‘00’ X‘00’ *1 If set to transfer SCSI-1/CCS Mode INQUIRY data by the CHANGE DEFINITION command.
Page 74 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. (0,0,1): The specified logical unit shows the type of input/output device shown in the "Device Type Code"...
Page 75 f. Response Data Format Field This field displays the code which shows the INQUIRY data format. The definition of the code is as shown below. The IDD reports either (0,0,0,1) or (0,0,1,0), depending on the specification in the CHANGE DEFINITION command. "Response Data Format"...
Page 76 Vendor ID Field This field indicates the name of the product's supplier in left-justified ASCII code, and always displays FUJITSU. The unused right end is space for the ASCII code. j. Product ID Field The product's model name is displayed in left-justified ASCII code in this field. The model name display is one of the following.
Page 77 VPD Information When "1" is specified in the "EVPD" bits of the CDB, the VPD information described below is transferred to the INIT by this command. The INIT specifies the type of VPD information required in the "Page code" field of the CDB. The type of VPD information supported by the IDD and its page code number are as shown below.
Page 78 b. Device Serial No. This VPD information reports the device serial number of the IDD. The format of this VPD information is shown in Fig. 3.3. Byte Qualifier Device Type Code X‘80’ (Page Code) X‘00’ X‘0C’ (Page Length) Device Serial No. (ASCII) Figure 3.3 VPD Information: Device Serial No.
Page 79 c. Operation Mode This VPD information reports the IDD's current operation mode. The format of this VPD information is shown in Fig. 3.4. Byte Qualifier Device Type Code X‘C0’ (Page Code) X‘00’ X‘04’ (Page Length) WDTR UNTAIN SDTR RSRTY X‘xx’ (Spindle Motor Start Delay Timing) X‘00’...
Page 80: Read Capacity (25)
3.1.3 READ CAPACITY (25) Byte X‘25’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Flag Link This command transfers information related to the disk drive's capacity and the data block size to the INIT. When bit 0 "PMI (partial medium indicator)"...
Page 81 By using this command with the "PMI" bit specified as "1", the INIT can search for usable data space continuously without being interrupted by data transfers for alternate sector processing or switching of cylinders. The format of the data transferred to the INIT by this command is shown in Fig. 3.5. Byte Logical Block Address (MSB) Logical Block Address...
Page 82: Change Definition (40)
3.1.4 CHANGE DEFINITION (40) Byte X‘40’ Save SCSI Level Parameter List Length Flag Link This command changes the IDD's SCSI level and the operation mode. The INIT can know the SCSI level and operation mode that the IDD is currently using by the INQUIRY command (Standard Inquiry Data and VPD Information - Operation Mode Page: Page code X 'C0').
Page 83 If zero is specified in the "SCSI Level" field, the IDD operates at the current SCSI level without changing the SCSI level. However, if the correct operation mode parameter (described later) is transferred at the same time, the IDD changes its operation mode. The total byte length of the operation mode parameter transferred by the INIT with this command is specified in the "Parameter List Length"...
Page 84 Header a) Bytes 0 to 2 X '00' must be specified in this field. b) Parameter Length The parameter list length in byte 4 and subsequent bytes which follows the header must be specified in this field. The parameter list length supported by the IDD is X '04' and the INIT must not specify a value other than X '04' in this field.
Page 85 c) SDTR (synchronous data transfer request) Specifies whether or not it is permitted for the TARG to request a synchronous mode data transfer. "1" (Permitted) : After the power is switched on, after a RESET condition occurs or when the first command is received following reception of a BUS DEVICE RESET message, if a synchronous data transfer request (SDTR) message is not sent by the INIT, the IDD sends the SDTR message and attempts to establish synchronous mode data transfer.
Page 86: Mode Select (15)
3.1.5 MODE SELECT (15) Byte X‘15’ Parameter List Length Flag 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. The INIT can know the types of parameters, the current settings of each parameter and the types of parameters which can be changed, and the ranges for such changes, etc.
Page 87 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 88 Current values Save values Power-on RESET condition [Common to all INITs] BUS DEVICE RESET MODE [Common to all INITs] message SELECT Page: Page: 1, 2, 7, 8, A, C, 1C, 21 1, 2, 7, 8, A, 1C, 21 MODE SELECT (SP=1) MODE SELECT EXTENDED [Common to...
Page 89 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 90 Header Byte X‘00’ X‘00’ (Media Type) × × X‘00’ or X‘08’ (Product Descriptor Length) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X‘00’ Data Block Length (MSB) Data Block Length Data Block Length (LSB) Page Descriptor Byte Page Code...
Page 91 a. Header • Media Type X '00' (default type) must be specified in this field. • Byte 2 Byte 7 and byte 4 of this field have meaning only in the header transferred to the INIT by the MODE SENSE and MODE SENSE EXTENDED commands. The values specified in these bits are disregarded in the MODE SELECT and MODE SELECT EXTENDED commands.
Page 92 • Data Block Count This field specifies the total number of logical data blocks (the block length is specified in "Data block length) allocated in the "User Space" on the disk media. The maximum logical block address is a value with 1 subtracted from the value in this field.
Page 93 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 94 Notes: The MODE SELECT parameter is ordinarily different in its configuration depending on the input/output device and the type of controller. It is also possible that current definitions may be expanded in accordance with the expansion of the functions of the IDD in the future.
Page 95 Read/Write Error Recovery Parameters (Page Code = 1) Fig. 3.8 shows the format of the page descriptor of this MODE SELECT parameter. Byte X‘0A’ or X‘06’ (Page Length) (Note) AWRE ARRE Default Variable Number of retries during READ (=32 Default X‘20’...
Page 96 Error recovery parameters defined in this page descriptor are applicable for the following commands, except in cases where it is specifically pointed out. • READ • WRITE • READ EXTENDED • WRITE AND VERIFY (Write operation) • READ LONG • WRITE EXTENDED •...
Page 97 e. EER (enable early recovery) "1" : When a correctable data check has been detected, data correction according to the ECC is applied immediately without executing retry (rereading) up to the number of times specified in the "Number of retries during READ" parameter. "0"...
Page 98 i. Number of Retries during READ This parameter specifies the number of retries that should be executed for "Data Check" type errors detected in read operations on the disk media. The number of retries specified in this parameter is the maximum number of times reading is retried for each individual portion of data in each logical data block.
Page 99 l. Recovery Time Limit This parameter specifies the maximum time that can be used by the TARG for error recovery processing, as a 1 (s constant. The value specified in this parameter is the maximum permissible time for error recovery processing for each individual logical data block.
Page 100 Table 3.1 Combinations of Error Recovery Flags (2 of 4) 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. Data correction is not executed according to the ECC. 2.
Page 101 Table 3.1 Combinations of Error Recovery Flags(3 of 4) 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 102 Table 3.1 Combinations of Error Recovery Flags (4 of 4) 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 103 Disconnect/Reconnect Parameters (Page Code = 2) The format of the page descriptor in this MODE SELECT parameter is shown in Fig. 3.9. Byte X‘0E’ or X‘0A’ (Page Length) (See the "Note." Buffer Full Ratio Default X‘20’ (63.5 KB) Variable X‘FF’ Buffer Empty Ratio Default X‘20’...
Page 104 a. Buffer Full Ratio This parameter specifies the timing for the IDD to start reconnection processing in order to transfer data to the INIT by the READ or READ EXTENDED command. The value specified in this parameter (n) shows the amount of data read to the IDD's data buffer from the disk media as a proportion [n/256] of the total capacity of the data buffer until reconnection processing with the SCSI bus is started.
Page 105 c. Bus Inactivity Limit This parameter indicates the maximum time that the TARG is permitted to keep the SCSI bus in the Busy state (BSY Signal = TRUE) without executing a REQ/ACK handshake, in multiples of 100 µs. In the IDD, this value is 100 µs during normal operation. It is impossible for this parameter to be changed by the INIT.
Page 106 Format Parameter (Page Code = 3) The Page descriptor format of this MODE SELECT parameter is shown in Fig. 3.10. Byte X‘16’ (Page Length) Alternate Track Count/Zone (= 1 Cylinder) Default X‘000x’ Variable X‘0000’ Alternate Sector Count/Zone (= 20 Sectors) Default X‘0014’...
Page 107 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 "OEM Manual VOL. 1, Product Specifications/Installation Procedures"...
Page 108 c. Parameters which Specify the 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 109 d. Parameters Related to Device Type (Byte 20) • SSEC (soft sectoring) When this bit is "1," it indicates that the data formatting method on the disk media is "soft sectoring." However, since the IDD uses only the "hard sectoring" method (refer to previously shown item b), this bit is disregarded.
Page 110 Drive Parameter (Page Code = 4) The page descriptor format of this MODE SELECT parameter is shown in Fig. 3.11. Byte (See the X‘16’, X‘12’ or X‘0A’ (Page Length) "Note") Cylinder Count Default X‘00xxxx’ Variable X‘FFFFFF’ Number of Heads Default X‘00xx’...
Page 111 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), so caution should be used.
Page 112 b. Number of Heads This parameter indicates the number of data Read/Write heads in the disk drive. It is impossible to change this parameter. If zero or a value which differs from the "Default" value is specified in this parameter field, the IDD performs rounding processing of the parameter, setting a value which is the same as the default value in it.
Page 113 Verify Error Recovery Parameters (Page Code = 7) The page descriptor format of this MODE SELECT parameter is shown in Fig. 3.12. Byte (See X‘0A’ (Page Length) (Reserved) Note.) Default Variable Number of retries during VERIFY. (=32 Default X‘20’ times) Variable X‘FF’...
Page 114 a. Error Recovery Flags • EER (enable early recovery) • PER (post error) • DTE (disable transfer on error) • DCR (disable correction) The definitions and functions of these control flags are the same as for the Read/Write Error Recovery Parameters. See item (1) concerning the details. b.
Page 115 Caching Parameters (Page Code = 8) The page descriptor format of this MODE SELECT parameter is shown in Fig. 3.13. Byte X‘0A’ or X‘12’ (Page Length) (ABPF) (CAP) DISC SIZE Default Variable X‘00’ (Reserved) Pre-fetch inhibit block count Default X‘FFFF’ Variable X‘0000’...
Page 116 The parameters defined in this page descriptor control the range of look-ahead data in the Look-Ahead cache feature and enable or disable the caching operation. See 2.2, "Look-Ahead Cache Feature" and 2.3, "Write Cache" concerning details of the Look-Ahead cache feature and parameter setting methods.
Page 117 Sequential writing is performed without waiting for rotation. "0" : This prohibits operation of the WRITE cache function. WRITE DATA remains in the buffer memory, the cache is not made the object even for a read command, and as soon as all the data has been written to the disk, "GOOD" status is reported. d.
Page 118 i. Maximum Pre-fetch This parameter specifies the maximum quantity of logical data blocks pre-fetched to the data buffer with the READ command or READ EXTENDED command. The IDD varies the pre-fetch volume according to the volume of data requested by the READ command or READ EXTENDED command.
Page 119 Mode Select Parameter (Page 8-Byte 13) Cache Segment Length 496 KB 248 KB 165 KB 4 (default) 124 KB 99 KB 82 KB 70 KB 62 KB 55 KB 49 KB 45 KB 41 KB 38 KB 35 KB 33 KB 31 KB 3 - 50 C141-E039-01EN...
Page 120 Control Mode Parameters (Page Code = 0A) The page descriptor format of this MODE SELECT parameter is shown in Fig. 3.14. Byte X‘06’ (Page Length) (Reserved) RLEC Default Variable Queue Algorithm Qualifier (Reserved) QErr DQue Default Variable EECA (Reserved) Default Variable X‘00’...
Page 121 b. Queue Algorithm Qualifier This parameter controls the execution order algorithm of a command issued together with a SIMPLE QUEUE TAG message. When "0" is specified in this parameter, the IDD executes commands queued from each INIT in the order in which they were received. However, the command execution order for the READ, READ EXTENDED and PRE-FETCH commands may be changed.
Page 122 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’ 12-15 Ending Boundary Default X‘00000000’...
Page 123 Note Normally, the number of tracks (logical heads) per cylinder is set in the track count/zone, but in the case of notching only, the total track count (number of cylinders in the zone x number of logical heads) of the affected zone is reported. 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.
Page 124 • Starting Boundary This field is enabled by the MODE SENSE command. This field is enabled when ND=1 and the top address of the zone (+1) indicated by the active notch shows the logical/physical block format. • Ending Boundary This field is valid in the MODE SENSE command. It is valid when ND=1, and the final address of the zone (+1) shown by the active notch is indicated in the physical/logical block format.
Page 125 RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit. 3 - 56 C141-E039-01EN...
Page 126: Mode Select Extended (55)
3.1.6 MODE SELECT EXTENDED (55) Byte X‘55’ Parameter List Length (MSB) Parameter List Length (LSB) Flag 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 127 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 128: Mode Sense (1A)
3.1.7 MODE SENSE (1A) Byte X‘1A’ Page Code Transfer Byte Length Flag 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 129 When the value specified in the "Page code" field is other than X '3F', the specified "Page descriptor" only is transferred to the INIT, and when X '3F' is specified, all the "Page descriptors" supported by the IDD are transferred to the INIT in the ascending order of the page code, but if SCSI-1/CCS is specified by the CHANGE DEFINITION command (SCSI level), Page code 7, Page code 8 and Page code A are not transferred.
Page 130 Table 3.2 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 131 Header Byte Sense Data Length X‘00’ (Media Type) X‘00’ or X‘08’ (Block Descriptor Length) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X‘00’ Data Block Length (MSB) Data Block Length Data Block Length (LSB) Page Descriptor Byte Page...
Page 132 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. Also, a value for a portion of data with a length that is supported by the IDD is reported in this field for a parameter list of the type specified in the CDB regardless of the specification of the "Transfer byte length"...
Page 133 Page Descriptor The "Page descriptor" is configured from a parameter field which follows a 2-byte page header, and is divided into units called "Page" for each parameter's functional attributes. See the description of the MODE SELECT command (item 3.1.5) concerning the configuration of each page descriptor and their contents.
Page 134: Mode Sense Extended (5A)
3.1.8 MODE SENSE EXTENDED (5A) Byte X‘5A’ Page Code Transfer Byte Length (MSB) Transfer Byte Length (LSB) Flag 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 135 Header Byte Sense Data Length (MSB) Sense Data Length (LSB) X‘00’ (Media Type) X‘00’ X‘00’ X‘00’ (Block Descriptor Length: MSB) X‘00’ or X‘08’ (Block Descriptor Length: LSB) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X‘00’...
Page 136: Rezero Unit (01)
3.1.9 REZERO UNIT (01) Byte X‘01’ Flag Link This command moves the read and 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 137: Start/Stop Unit (1B)
3.1.10 START/STOP UNIT (1B) Byte X‘1B’ Immed × Start Flag Link This command controls starting and stopping of the disk drive's spindle motor. Control of the spindle motor is performed through the "Start" bit in bit 0 of the CDB byte 4. The spindle motor can be stopped if this command is issued with the "Start"...
Page 138 a. In the case of the Start Specification ("Start" bit = "1") • When the "Immed" bit is "1," simply by instructing starting of the spindle motor, a GOOD status is reported without waiting until the disk drive is in the Ready state, and command execution is completed.
Page 139: Reserve (16)
3.1.11 RESERVE (16) Byte X‘16’ 3rd Pty 3rd Pty Dev ID × × × × × × × × × × × × × × × × × × × × × × × × Flag Link Together with the RELEASE command, this command controls exclusive access to the logical unit (IDD) under a multi-initiator environment.
Page 140 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 141 Changing the Reserve Conditions (Superseding Reserve) The INIT which has the reserve right for an IDD (the INIT which has issued this command in the past and has established the IDD reserve state) can change the IDD's reserve conditions by issuing a another RESERVE command (Superseding Reserve).
Page 142 2. If INIT #A issues a RESERVE command which specifies the third party reserve function ("3rd Pty Dev ID" = TARG/INIT#1), TARG #0 becomes reserved from TARG/INIT #1, but INIT #A has the reserve right. In this case, • TARG/INIT #1 has an exclusive monopoly of TARG #0. However, if TARG/INIT#1 issues a RESERVE command, that command is rejected with a RESERVATION CONFLICT status.
Page 143: Reserve Extended (56) (Not Supported)
3.1.12 RESERVE EXTENDED (56) (Not Supported) Byte X‘56’ 3rd Pty × × × × × × × × Third Party Device ID × × × × × × × × × × × × × × × × Flag 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 144: Release (17)
3.1.13 RELEASE (17) Byte X‘17’ 3rd Pty 3rd Pty Dev ID × × × × × × × × Flag 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 it is no influence on the IDD's reserve state.
Page 145 Release Function This command releases a reserve state if a reserve state exists, and if the INIT which issued this command has a reserve right for the entire IDD (logical unit). See Reserve Right and Third Party Reserve Function in "RESERVE Command" (item 3.1.11) concerning the definition of "Reserve Right."...
Page 146: Release Extended (57) (Not Supported)
3.1.14 RELEASE EXTENDED (57) (Not Supported) Byte X‘57’ 3rd Pty × × × × × × × × Third Party Devices ID × × × × × × × × × × × × × × × × Flag Link This command releases the reserve state of an IDD in relation to the INIT which issued this command.
Page 147: Request Sense
3.1.15 REQUEST SENSE (03) Byte X‘03’ Transfer Byte Length Flag Link This command transfers sense data to the INIT. This command is executed immediately without queueing in a system which issues only commands with no tags or links. 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.
Page 148 Note: See Section 1.6, "Sense Data Hold State" concerning details of the sense data hold state and see Section 4.1, "Sense Data" concerning the format of sense data transferred by this command from the IDD to the INIT, and its contents. If this command is issued while the IDD is holding the UNIT ATTENTION condition, if the IDD is not in the sense data hold state at that point, sense data indicating the UNIT ATTENTION condition are sent to the INIT by this command and the UNIT ATTENTION...
Page 149: 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 Flag Link This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count" field with the logical data block on the disk media specified in the "Logical block address"...
Page 150: Read Extended (28)
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) Flag Link This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count"...
Page 151: Write (0A)
3.2.3 WRITE (0A) Byte X‘0A’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Block Count Flag 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 152 The IDD does not perform data transfer immediately after receiving the CDB, but after performing automatic disconnect processing once, it executes pre-fetching of data. If disconnect processing is permitted, the IDD either completes transfer of all the data specified in the command or, at the point when the empty space in the data buffer runs out, disconnect processing is executed.
Page 153: Write Extended (2A)
3.2.4 WRITE EXTENDED (2A) Byte X‘2A’ × Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) Flag 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 154: Write And Verify (2E)
WRITE AND VERIFY (2E ) 3.2.5 Byte X‘2E’ × Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) Flag 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 155: Verify (2F)
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) Flag Link This command reads the number of continuous logical data blocks specified in the "Block count"...
Page 156: Seek (0B)
3.2.7 SEEK (0B) Byte X‘0B’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Flag 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 157: Seek Extended (2B)
3.2.8 SEEK EXTENDED (2B) Byte X‘2B’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Flag 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. The functions and operation of this command are the same as those of the Group 0 SEEK command (item 3.2.7), except that it is possible to specify 4-byte logical block addresses.
Page 158 3.2.9 SET LIMITS (33) (Not Supported) Byte X‘33’ RdInh WrInh Logical Block Address (MSB Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) Flag Link This command specifies the address range of logical data blocks on an ID which it is possible to access by commands which follow this command and which are linked to it, and to specify the type of operations which it is possible to execute.
Page 159 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 160 When access to logical data blocks outside the address range defined by this command by linked commands which follow this command is specified, or when a prohibited type of access operation is specified, that command is terminated with a CHECK CONDITION status without being executed.
Page 161: Synchronize Cache (35)
3.2.10 SYNCHRONIZE CACHE (35) Byte X‘35’ Immed Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Block Count (MSB) Block Count (LSB) Flag Link This command matches the logical block data in the data buffer with the same logical block data recorded on the disk media.
Page 162: Format Commands
Format Commands 3.3.1 FORMAT UNIT (04) Byte X‘04’ FmtDat CmpLst Defect List Format Interleave factor (MSB) Interleave factor (LSB) Flag Link This command initializes (formats) the entire area of the disk media that can be accessed from the INIT (User Space). At the same time, the IDD also implements defect management processing, allocating alternate blocks for defective portions of the disk media in accordance with the specifications in this command.
Page 163 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 164 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” is specified in the “FmtData (format data) bit, it indicates that the format parameters (header and defect list), described later, are transferred from the INIT when this command is executed.
Page 165 Format Parameters Figure 3.20 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’ DPRV DCRT STPF Immed × Defect List Length (MSB) Defect List Length (LSB) Defect List (D List) Byte...
Page 166 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. • FOV (format option valid) Indicates that the INIT does not specially specify concerning the functions specified by the control flags in bits 6 to 4 of byte 1 (see items b.
Page 167 • STPF (stop format): Default value: “1” When the defect list (P List or G List) necessary for executing the defect processing specified in this command, cannot be read from the disk media, this bit indicates whether to continue (“0” is specified) or terminate (“1” is specified) command processing, but in the IDD, this bit’s specification is disabled, and the specified value is disregarded.
Page 168 • Byte Distance from the Index Format Defect Descriptor Fig. 3.21 shows this description format of the defect descriptor. Defect descriptor in this format specifies the cylinder number, head (track) number and byte distance to the top byte of those data (8 bytes), of the data which includes defective bits, on the disk media.
Page 169 • Physical Sector Address Format Defect Descriptor Fig. 3.22 shows this description format of the defect descriptor. A defect descriptor with this format specifies the physical sector number of the data block which includes the defect on the disk media together with the cylinder No. and the head (track) No. When specifying multiple defect descriptors, the cylinder No.
Page 170 Cautions in Specifying the D List The P List, containing defect position information, is always recorded on the IDD when it is shipped from the factory. Also, information on defect positions for which alternate block processing has been implemented during operation are recorded as the G List. The function which specifies defect position information as the D List when the FORMAT UNIT command is executed, is prepared mainly to specify initial defect position information of the disk media which does not have the P List recorded on it.
Page 171 Defect Processing During Initialization Table 3.3 shows each combination of control flag specification values and the contents of processing executed by the IDD. Furthermore, see Chapter 3 “Data Format” of the “Product Manual” concerning alternate block allocation processing methods. Table 3.3 FORMAT UNIT command Defect Processing (1/2) CDB Byte 1 Header...
Page 172 Table 3.3 FORMAT UNIT command Defect Processing (2/2) CDB Byte 1 Header Defect FmtData CmpLst Defect list DPRY Defect Processing Method List format Length Alternate block allocation is 1 0 0 >0 performed for defects registered in 1 0 1 the previously existing G List and the defects described in the D List transferred from the INIT.
Page 173: Reassign Blocks (07)
3.3.2 REASSIGN BLOCKS (07) Byte X‘07’ Flag Link This command allocates alternate data blocks for defective data blocks specified in the “Defect Data” list transferred form the INIT. See Chapter 3, “Product Specifications/Installation Procedures” in the “OEM Manual, Vol. 1 concerning alternate block processing methods implemented by this command.
Page 174 The format of the “Defect Data” list transferred from the INIT by this command is shown in Fig. 3.23. Byte X‘00’ X‘00’ Header Defect List Length (m) (MSB) Defect List Length (m) (LSB) Defective Block Logical Block Address (MSB) Defective Block Logical Block Address Defect Defective Block Logical Block Address Descriptor...
Page 175 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...
Page 176 Note: Precautions for use of command If this command is terminated with a CHECK CONDITION status, the sense code/sub-sense code in the sense data is other than “No defect spare location available [=32-00], and a valid logical block address (other than X ‘FFFFFFFF’) is displayed in the “Command inherent information”...
Page 177: Read Defect Data (37)
3.3.3 READ DEFECT DATA (37) Byte X‘37’ PList GList Defect List Format Transfer Byte Length (MSB) Transfer Byte Length (LSB) Flag Link This command transfers the list described in the defect position information of the disk media (defect data) to the INIT. There are two types of defect data, the P List (primary defect list) and the G list (grown defect list).
Page 178 The “Transfer byte length” field in the CDB specifies the defect data length (number of bytes) that can be received by the INIT. The IDD terminates data transfer when transfer of the length of defect data specified in the “Transfer byte length” field is completed or when transfer of all the defect data of the specified type is completed.
Page 179 Header a. P List (primary list) Bit When this bit is “1,” it indicates that P 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 P List defect data are not included.
Page 180 Notes: Precautions for use of command When “1” is specified in both the “P List” bit and the “G List” bit in the CDB, and transfer of both the P List and G List is requested, the IDD first of all transfers the P List, then transfers the G List afterward (merging of the defect information in the two lists is not performed).
Page 181 The number of defects reported by this command differs depending on the defect data format. • When data are in the “Block Address Format,” defect position information is not reported for portions which cannot be clearly accessed from the INIT. •...
Page 182: Maintenance, Diagnostic Commands
Maintenance, Diagnostic Commands 3.4.1 SEND DIAGNOSTIC (1D) Byte X‘1D’ SelfTest DevOfl UnitOfl Parameter List Length (MSB) Parameter List Length (LSB) Flag Link This command executes self-diagnosis tests which the IDD is equipped to perform and operation specified in the parameter list transferred from the INIT. Self-Diagnosis Test When the “SelfTest (self test)”...
Page 183 “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. The user should present the value displayed in this sense data as repair information to the Fujitsu representative.)
Page 184 Parameter Specification When “0” is specified in the “SelfTest (self test) bit in the CDB, the IDD executes the operations specified in the parameter list transferred from the INIT by this command. In this case, the IDD reports a GOOD status and terminates this command at the point when preparation of the “response data”...
Page 185 Byte Page Code Header Page Parameter Length (MSB) Page Parameter Length (LSB) Page Parameter Paramete Figure 3.25 SEND DIAGNOSTIC Command: Parameter List Configuration • Page Code This field specifies the code which identifies the type of parameter page being transferred from the INIT and the operation that should be executed.
Page 186 a. Page Code List This parameter page specifies transfer of the “Page code” list of the parameter page supported by the IDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command to the INIT. Fig. 3.26 shows the format of this parameter page.
Page 187 Figure 3.27 SEND DIAGNOSTIC Parameter: Logical/Physical Address Conversion The “Address Format Before Conversion” field shows the format of the address information specified in bytes 6 to 13. The IDD converts that address information to the expression format specified in the “Address Format After Conversion” field. the following codes can be specified as the “Address Format.”...
Page 188: Receive Diagnostic Results (1C)
3.4.2 RECEIVE DIAGNOSTIC RESULTS (1C) Byte X‘1C’ Transfer Byte Length (MSB) Transfer Byte Length (LSB) Flag 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 189 Fig. 3.28 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 Parameter Length (LSB) Page Parameters...
Page 190 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 Fig 3.29. Byte X ‘00’...
Page 191 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 192: Write Buffer (3B)
3.4.3 WRITE BUFFER (3B) Byte X‘3B’ Mode Buffer Address (MSB) Buffer Address Buffer Address Buffer Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length (LSB) Flag 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 193 Mode = 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 data transferred from the INIT. Also, zero must be specified in the “Buffer address” field of the CDB.
Page 194 Mode = 0, 0, 1 : Header + Data, without 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, and the 4-byte header (with zero specified in all its contents) must be added to them.
Page 195 Mode = 1, 0, 0 : Microcode Download, without Saving In this mode, the controller’s microcode or control information is transferred to the IDD’s control memory area. “0” must be specified in the “Buffer ID” field and the “Buffer address” field.
Page 196: Read Buffer (3C)
3.4.4 READ BUFFER (3C) Byte X‘3C’ Mode X‘00’ (Buffer ID) Buffer Address (MSB) Buffer Address Buffer Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length (LSB) Flag 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 197 Mode = 0 0 0: Header + Data, without Address Specification When this mode is specified, the data stored in the IDD’s data buffer are transferred to the INIT after the 4-byte header. Zero must be specified in the “Buffer address” field in the CDB. The “Transfer byte count”...
Page 198 Mode = 0, 0, 1: Header + Data, with Address Specification The format of the data transferred to the INIT when this mode is specified is the same as the format of the data in the case of Mode = 0, 0, 0, with the data stored in the IDD’s data buffer transferred to the INIT following the 4-byte header.
Page 199 Mode = 0, 1, 1: Buffer Descriptor When this mode is specified, the IDD transfers only the 4-byte buffer descriptor to the INIT. the IDD’s data buffer attributes are indicated in the 4-byte buffer descriptor. Zero must be specified in the “Buffer address” field in the CDB when this mode is specified. The IDD transfers the data length specified in the “Transfer byte length”...
Page 200: Read Long (3E)
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) Flag Link This command reads the logical data block data and its ECC byte, specified in the “Logical block address”...
Page 201 When “0” is specified in bit 1 of CDB byte 1, the “CORRCT (Corrected)” bit, the IDD does not implement ECC correction processing of data read from the disk media. When “1” is specified in the “CORRCT (Corrected)” bit, data errors that can be corrected by ECC are transferred to the INIT after being corrected in the IDD’s data buffer.
Page 202: Write Long (3F)
3.4.6 WRITE LONG (3F) Byte X‘3F’ CORRCT Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length (LSB) Flag Link This command writes the data block data transferred from the INIT, together with the ECC to form bytes, in the logical data blocks on the disk media specified in the “Logical block address”...
Page 203 If a value specifying a length (other than zero) that does not match the data format on the disk media is specified in the “Transfer byte length” field in the CDB, that command is terminated with a CHECK CONDITION status without data being transferred to the INIT. The sense data at this time indicate the following contents and the INIT can determine the correct “Transfer byte length”...
Page 204: Sense Data
CHAPTER 4 SENSE DATA ERROR RECOVERY METHODS Sense Data INIT Error Recovery Methods (Recommended) Disk Drive Error Recovery Methods 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 205 Byte Valid X ‘70’ or X ‘71’ (Error Code) X‘00’ Sense Key Information X ‘28’ (Additional Sense Data Length) Command Inherent Information Basic Informatio Sense Code Sub-sense Code X‘00’ SKSV Sense Key Inherent Information IDD SCSI ID CDB Operation Code Additional Detailed Information Informatio...
Page 206: Sense Data Basic Information
4.1.2 Sense Data Basic Information Bytes 0 to 17 of the sense data are basic information which show the contents of the error that has occurred. The INIT can know the contents of the error and the key information that is necessary for recovery processing by analyzing this basic information.
Page 207 Additional Sense Data Length This field indicates the length (number of bytes) after byte 8 of the sense data. The value shown in this field shows the length of sense data provided by the IDD without relation to the value specified in the “Transfer byte length” in the CDB of the REQUEST SENSE command. The length of the IDD’s sense data is fixed at 48 bytes and this field always indicates X ‘28’...
Page 208 Table 4.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 ERROR terminated 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 209 Table 4.2 Sense and subsense codes (1 of 7) Name Explanation Sense 00 No additional sense No specific sense code exists. information. Writing to a write protected area was attempted. 06 I/O process terminated I/O was interrupted by the Terminated I/O Process message. 00 No index/sector signal The target sector was not detected by the sector counter within the specified time.
Page 210 Table 4.2 Sense and subsense codes (2 of 7) Sense Name Explanation 01 Mechanical positioning error A seek error occurred in the drive. 1, 4 02 Positioning error detected The cylinder address in the ID area did not match. 1, 4 by read of medium 80 Off-track detected Went off-track while it was on track.
Page 211 Table 4.2 Sense and subsense codes (3 of 7) Sense Name Explanation 00 Defect list not found The defect management information header is incorrect. 01 Primary defect list not The defect list (P List) header is incorrect. found 02 Grown defect list not The defect list (G List) header is incorrect.
Page 212 Diagnostic failure on An error was detected in self-diagnosis. ("nn" is a component "nn" Fujitsu unique code (80 to FF)) • 80: RAM DATA compare error • 81: RAM parity error • 82: TEC register error •...
Page 213 Explanation nn Internal target failure An internal hardware error was detected in the IDD. ("nn" is a Fujitsu unique code (80 to FF)) • 80: Divide by zero was executed. • 81: The MPU fetched an undefined command. • 82: Parity error in the MPU or Buffer CRC error (SCSI) •...
Page 214 Sense and subsense codes (6 of 7) Sense Name Explanation nn Logical unit failed self- The IDD's initial setup failed. ('nn' is the Fujitsu unique configuration code (80 to FF)) 00 Overlapped commands 1) Before execution of an untagged command was...
Page 215 Explanation 11 Drive failure A serious error was detected in the drive's control system. ('nn' is a Fujitsu unique code (00 to FF) nn Microprogram detected A logical contradiction or similar error in the IDD's microcode was detected. ('nn' is a Fujitsu unique code (80 to FF).) •...
Page 216: Sense Data Additional Information
4.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 217 4.2.1 Termination Status Analysis and Error Recovery Methods Fig. 4.3 shows a model of the INIT's general processing flow from issuing of the command until reception of the termination status. In the figure, a "BUS FREE Error" is the case where the SCSI bus entered the BUS FREE phase at a point not intended by the INIT (at a point when entering the BUS FREE phase was not permitted by the SCSI bus protocol specification), and normally, it is an error detected by the host system's (INIT's) SCSI...
Page 218 BUSY/QUEUE FULL Status This status indicates that the IDD is currently executing processing of another command and that a new command cannot be received. The INIT that receives this status can reissue the original command. Under a multi-initiator environment, when an INIT receives this status, the time until the IDD can receive the next command depends on the operating state with other INITs, so ordinarily, it cannot be predicted.
Page 219: Sense Data Analysis And Error Recovery Method
Command Completion Wait Time-out This error is a state where the completed status for a command is not reported within the time expected by the INIT that issued the command. One cause of this error occurring, besides a malfunction of the IDD, is that the command was cleared by some method which the INIT that issued the command cannot clearly detect, such as a BUS DEVICE RESET message, or the command was cleared when an unrecoverable error was detected in reconnection processing executed by the IDD, etc.
Page 220 Table 4.3 Sense data error classification (1 of 4) Recovery Method Outline of Error (See Table 4.4.) No sense data showing the error contents are held. None 01 Write error recovered with auto reallocation Need 00 ID CRC or ECC error 00 Sync byte not found for ID field 00 Sync byte not found for data field xx Positioning error...
Page 221 Table 4.3 Sense data error classification (2 of 4) Recovery Method Outline of Error (See Table 4.4.) xx SA information error Need xx SA information error not found The information recorded in (SA) on the disk media cannot be read correctly. 00 Medium format corrupted Need 01 FORMAT command failed...
Page 222 Table 4.3 Sense data error classification (3 of 4) Recovery Method Outline of Error (See Table 4.4.) 00 Invalid command operation code None 00 Logical block address out of range 00 Invalid field in CDB 00 Logical unit not supported 00 Invalid field in parameter list 00 Command sequence error There is an error in the command specification...
Page 223 Table 4.3 Sense data error classification (4 of 4) Recovery method Error contents (See Table 4.4.) 02 Spindle not synchronized None Rotational synchronization deviated. 00 Read protected None 00 Write protected Access to a read protected or write protected area was attempted. 00 Command sequence error None The SET LIMITS command was issued 2...
Page 224 Table 4.4 Error Recovery Processing Procedures (1 of 4) Recovery Recovery Processing Procedure Method Error recovery processing is impossible. Terminate processing. This is a programming error and error recovery processing is impossible. Terminate processing and correct the error in the system (INIT) programming. This is an error in the SCSI protocol and error recovery processing is impossible.
Page 225 Table 4.4 Error recovery procedure (2 of 4) Recovery Recovery processing procedure method Issue the START instruction using the START/STOP UNIT command ("Immed" = 0). When the START/STOP UNIT command is terminated abnormally, perform recovery method 1. When the START/STOP UNIT command is terminated normally, reissue the original command (Retry).
Page 226 Table 4.4 Error recovery procedure (3 of 4) Recovery Recovery processing procedure method Issue the LOG SENSE command and read the "Current" values in the LOG SELECT parameters. If the parameters' values are appropriate, reissue the original command. Note This error could also be caused by a UNIT ATTENTION condition being generated, caused by a programming error of another INIT, so when the value in the parameter read in ( is illegal, recovery method 2 should be performed, or the operations of the other INITs should be confirmed.
Page 227 Table 4.4 Error recovery procedure (4 of 4) Recovery Recovery processing procedure method Issue the READ or READ EXTENDED command and read the data for the block where the error occurred. Investigate the cause of the data not matching and perform data recovery processing from the INIT.
Page 228: Error Logging
4.2.3 Error Logging In order to collect information that is effective in maintenance, it is desirable for the INIT to accumulate (log) error information related to the SCSI bus which it has detected itself (BUS FREE errors, command completion wait time-out, etc.) and error information reported by the IDD.
Page 229: 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. 4.3.1 Error States and Retry Processing Procedures Seek Error...
Page 230 Correctable Data Read Error This error is a correctable ECC error when data are being read. Processing methods when this error is detected differ depending on the values specified in the EER flag and DCR flag in the MODE SELECT parameters. If immediate correction of errors is permitted (DCR = 0, EER = 1), the IDD immediately makes error corrections in the data buffer and sends the corrected data to the INIT.
Page 231 4.3.2 Auto Alternate Block Allocation Processing The IDD is equipped with a function which automatically executes alternate block allocation processing for defective data blocks detected during execution of the WRITE, WRITE EXTENDED, WRITE AND VERIFY, READ and READ EXTENDED commands. Auto Alternate Block Allocation Processing during a Write Operation This function is enabled by specifying "1"...
Page 232 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.
Page 233: Error Recovery Processing Control
4.3.3 Error Recovery Processing Control The INIT can, by specifying the MODE SELECT parameters, can control the error recovery processing (retries) of the IDD with respect to each type of error related to the disk drive. Table 4.5 shows the types of error and the method of specifying the number of retries for those errors.
Page 234 c. Additional Error Recovery Parameters (Page Code = 21) • Number of retries during seek error (See Table 4.5) Table 4.5 Disk Drive Errors and Number of Retries Item Type of Error Number of Tries Specification [Default value] Seek Error Number of Retries during a Seek Error [15] Data Read Error...
Page 236: Chapter 5 Disk Media Management
CHAPTER 5 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.
Page 237 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 one or both of the following areas.
Page 238 • 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 cylinder have been used up for defective sectors included in the type of defect list (P, G or D) specified in the command.
Page 239: Disk Media Initialization
Disk Media Initialization 5.2.1 Initialization During Installation The disk drive is initialized for the inherent (default) data format for each respective model name (model class) when it is shipped from the factory, so ordinarily, it is not necessary to initialized (format) the disk media when it is installed in a system. However, in cases where data attributes which differ from the default format are necessary, initialization (formatting) of the entire disk media by the following procedures is necessary.
Page 240 Issuing the FORMAT UNIT Command Issue the FORMAT UNIT command and initialize the entire disk media surface. In this FORMAT UNIT command, the entire disk media surface is initialized using the P List, then after initialization, the data blocks are verified. If any defective blocks are detected in the Verify operation, alternate blocks are allocated for those data blocks.
Page 241: Re-Initialization
5.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 242: Data Block Verification Method (Recommended)
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 243 Writing a Data Pattern Write a data pattern for verification in the data block which is the object. The recommended data pattern at this time is X '0123456789ABCDEF' repeated. The WRITE, WRITE EXTENDED or WRITE SAME command can be used to write data. 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.
Page 244: Alternate Block Allocation Processing
Alternate Block Allocation Processing If errors on the disk media which cannot be recovered from are detected, or if a recoverable error occurs repeatedly in the same data block, it is necessary for the INIT to allocate an alternate block for the data block where the error occurred using the REASSIGN BLOCKS command.
Page 246: Glossary
Glossary Bus Condition ..This is an asynchronous condition for changing the status transition on the SCSI bus. There are two types, the ATTENTION condition and the RESET condition. Bus Phase....This is the name given to the SCSI bus state. The SCSI bus is in one state or another, the BUS FREE phase, the ARBITRATION phase, the SELECT phase, the RESELECTION phase or the INFORMATION TRANSFER phase.
Page 247 SCSI ......Small Computer System Interface The standardized input/output interface of the American National Standards Institute (ANSI). [Standard No.: ANSI X3. 131-1986] SCSI Device..... The general name given to a device which is connected to the SCSI bus (input/output device, I/O controller, host adapter, etc.). SCSI ID....
Page 248 Abbreviation Acknowledge Attention Original equipment manufacturer American Wire Gauge Request Busy Reset Control/data SCSI Small Computer System Interface Common command set SDTR Synchronous data transfer request Common descriptor block Select Data bus TARG TARGet Data Bus Parity Terminator Direct current Engineering Industries Association Ground Input/output...
Page 249 211-88, Japan FAX: 34-1-581-8125 TEL: 044-754-8632 FAX: 044-754-8634 FUJITSU AUSTRALIA LIMITED 475 Victoria Avenue, Chatswood, 2067 N.S.W, AUSTRALIA FUJITSU COMPUTER PRODUCTS OF AMERICA, INC. TEL: 61-2-410-4555 2904 Orchard Parkway, San Jose, FAX: 61-2-411-8603, 8362 California 95134-2009, U.S.A. TEL: 1-408-432-6333 FUJITSU HONG KONG LIMITED...
Page 250 FUJITSU LIMITED Reader Comment Form We would appreciate your comments and suggestions for improving this publication. Publication No. Rev. Letter Title Current Date How did you use this publication? Is the material presented effectively? Learning Sales Installing Fully Well Well...

This manual is also suitable for:

Mab3091sc

Fujitsu MAA3182SC Oem Manual

Chapter 4 Sense Data and Error Recovery Methods

Chapter 1 Command Processing

Command Format

Status Byte

Outline of Command Processing

Command Queuing Function

UNIT ATTENTION Condition

Sense Data Hold State

Command Processing Exceptions

Data Block Addressing

Chapter 2 Data Buffer Management

Data Buffer

Write Cache

Chapter 3 Command Specifications

Control/Sense Commands

Data Access Commands

Format Commands

Maintenance, Diagnostic Commands

Sense Data

INIT Error Recovery Methods (Recommended)

Disk Drive Error Recovery Processing

Chapter 5 Disk Media Management

Defect Management

Disk Media Initialization

Data Block Verification Method (Recommended)

Alternate Block Allocation Processing

Glossary

Quick Links

Related Manuals for Fujitsu MAA3182SC

Summary of Contents for Fujitsu MAA3182SC

This manual is also suitable for:

Table of Contents