Page 1 C141-E167-01EN MAP3367, MAP3735, MAP3147 NP/NC SERIES MAS3367, MAS3735 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) May, 2002 — — Section(s) with asterisk (*) refer to the previous edition when those were deleted. C141-E167...
Page 4 This page is intentionally left blank.
Page 5 Preface This manual explains concerning the MAS3367, MAS3735, MAP3367, MAP3735, MAP3147 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 Preface 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...
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-E167...
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 3. Data Format 4. Installation Requirements 5. Installation Diagnostics and Maintenance Error Analysis Principle of Operation 1. SCSI Bus SCSI Physical Interface Specifications 2. SCSI Messages 3. Error Recovery SCSI Logical Interface Specifications 1.
Page 10 This page is intentionally left blank.
Page 11: Table Of Contents
Contents CHAPTER 1 Command Processing......................1-1 Command Format ..........................1-1 Status Byte .............................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.......................1-16 1.4.1 Untagged queuing.........................1-16 1.4.2 Tagged queuing ........................1-18 UNIT ATTENTION Condition ....................1-19...
Page 12 Contents CHAPTER 2 Data Buffer Management ....................2-1 Data Buffer............................ 2-1 2.1.1 Data buffer configuration and basic operation............... 2-1 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-8 2.2.3 Look-Ahead operation, Look-Ahead volume ................
Page 13 Contents 3.1.19 PERSISTENT RESERVE OUT (5E) ...................3-56 3.1.19.1 PERSISTENT RESERVE OUT service actions .............3-57 3.1.19.2 PERSISTENT RESERVE OUT parameter list ...............3-58 3.1.20 REPORT LUNS (A0) ......................3-60 3.1.21 REPORT DEVICE IDENTIFIER (A3) ................3-62 3.1.22 SET DEVICE IDENTIFIER (A4) ..................3-63 Data Access Commands ......................3-65 3.2.1 READ (08)..........................3-65 3.2.2...
Page 14 Contents 4.1.6 Caching parameters (page code = 8)..................4-21 4.1.7 Control mode parameters (page code = 0A) ............... 4-27 4.1.8 Notch parameter (page code = 0C) ..................4-31 4.1.9 Informational exceptions control page (page code = 1C) ............ 4-33 4.1.10 Additional error recovery parameters (page code = 21) ............4-36 Log Parameters ...........................
Page 15 Contents 4.2.8.4 Start-stop cycle counter (Page 0E, Code 0004) .............4-54 4.2.9 Application client page (X'0F').....................4-55 4.2.9.1 General usage application client parameter data (Page 0F, Code 0000-003F)....4-55 4.2.10 Self-test result page (X'10')....................4-56 4.2.10.1 Self-test result parameter data (Page 10, Code 0001-0014) ..........4-56 4.2.11 SMART status page (X'2F')....................4-57 4.2.12 SMART data page (X'38') ....................4-57 CHAPTER 5 Sense Data Error Recovery Methods ................5-1...
Page 16 Contents Illustrations Figures 6-Byte CDB Basic Format ......................1-1 10-Byte CDB Basic Format ......................1-2 12-Byte CDB Basic Format ......................1-2 Status Byte ............................ 1-6 Data space configuration......................1-31 Data buffer configuration (in the case of 8 cache segments) ............2-2 Example of data buffer operation during read ................
Page 17 Contents MODE SELECT parameters: read/write error recovery parameters ..........4-2 MODE SELECT parameters: disconnect/reconnect parameters..........4-10 MODE SELECT parameters: format parameters ...............4-14 MODE SELECT parameters: drive parameters................4-18 MODE SELECT parameters: verify error recovery parameters..........4-20 MODE SELECT parameters: caching parameters..............4-22 MODE SELECT parameters: control mode parameters .............4-28 MODE SELECT parameters: informal exception control page..........4-33 MODE SELECT parameters: additional error recovery parameters ..........4-36 Expanded sense data format ......................5-2...
Page 18 This page is intentionally left blank.
Page 19: Chapter 1 Command Processing
CHAPTER 1 Command Processing 1.1 Command Format 1.2 Status Byte 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 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 Furthermore, this field may be used with a different meaning, or it may not have any meaning at all, depending on the type of command. There are also some commands which allocate 3 or more bytes as the transfer data length field. Detailed specifications of these commands are described in the individual command specifications in Chapter 3.
Page 23 1.1 Command Format Note: It is possible that bits 7 and 6 of the control byte will be used in future product specifications as an inherent control field. It is recommended that zeros be specified in this field. 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 CHECK CONDITION status.
Page 24 Command Processing Status Byte Figure 1.4 shows status byte format and the type of status that 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. The status byte 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 Byte
1.2 Status Byte 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: Outline Of Command Processing
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: Command Link
1.3 Outline of Command Processing 6) When execution of the command is completed, the TARG reports the execution results by the status byte in the STATUS phase to the INIT. 7) The TARG reports the TASK COMPLETE message to the INIT in the MESSAGE IN phase and enters the BUS FREE phase.
Page 28: Responses To Link Specification Commands
Command Processing Table 1.1 Responses to Link Specification Commands Flag End Status Status Message Link Function Completed INTERMEDIATE LINKED TASK COMPLETE Effective Normally Completed INTERMEDIATE LINKED TASK COMPLETE WITH Effective Normally FLAG Completed CHECK CONDITION TASK COMPLETE Not Effective Abnormally Conditions Met INTERMEDIATE LINKED TASK COMPLETE...
Page 29: Disconnect/Reconnect Processing
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: Types Of Command And Disconnect Processing
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: Synchronous Mode Data Transfer/Wide Mode Data Transfer
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 Queuing Function
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: Tagged Queuing
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: Unit Attention Condition
1.5 UNIT ATTENTION Condition 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 released, it continues to execute the commands in the queue.
Page 38: Response And Release Condition At Unit Attention Condition Hold State
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] Registrations Preempted [=2A-05] Commands cleared by another INIT [=2F-00] Spindle synchronized [=5C-01]...
Page 40: Unit Attention Condition Multiple Hold
Command Processing The IDD executes the REQUEST SENSE command normally and sends the sense data which indicate the UNIT ATTENTION condition and are being held to the INIT. At this time, the UNIT ATTENTION condition for that INIT is cleared. 1.5.3 UNIT ATTENTION condition multiple hold If any UNIT ATTENTION condition is generated and a new UNIT ATTENTION condition is...
Page 41: Command Processing Exceptions
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: Illegal Lun Specification
1.7.3 Reserved operation code Group 7 command operation codes (X ‘E0’ 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]. The INIT should not issue commands which contain these operation codes.
Page 43: Sense Data In Not Ready State
1.7 Command Processing Exceptions • When reading of system information is not completed, or reading failed. 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: Error Recovery Processing
Command Processing 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). Operation if formatting is not completed normally While the FORMAT UNIT command is not being executed after a change in data format related parameters by the MODE SELECT command, if 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 45: Outline Of Scsi Bus Error Recovery Processing
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"Status...
Page 46: Reset Processing
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: Fatal Hardware Errors
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: Data Block Addressing
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: 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 cylinder (b-1) (b cylinders) Zone 1 Cylinder (a-1) Zone (x-1) Alternate (c cylinders) cylinder...
Page 50: Logical Block Addressing
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. Access to the data on the disk medium is performed in logical data block units and the INIT specifies the logical data block address that is its object during access.
Page 51: Chapter 2 Data Buffer Management
CHAPTER 2 Data Buffer Management 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 Configuration (In The Case Of 8 Cache Segments)
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: Example Of Data Buffer Operation During Read
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: Example Of Data Buffer Operation During Write
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 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
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 can be transferred to the INIT.
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 MODE SENSE MODE SENSE EXTENDED PERSISTENT RSV IN PERSISTENT RSV OUT READ BUFFER...
Page 59: Caching 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
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 bits 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 bits is one, product information called VPD (vital product data) is transferred to the application client.
Page 66: 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. (0,0,1): The specified logical unit shows the type of input/output device shown in the "Device Type Code"...
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: 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 media. When this is the case, a subsequent request for command support data may be successful. 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.
Page 73: Vpd Information: Vpd Identifier List
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: 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)
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) 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 * Set at shipping time 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 * Set at shipping time The IDD ignores this specification and operates with the settings specified at shipping. f) ACE (AIP checking enabled) This specifies whether or not it is permitted to check AIP (Asynchronous Information Protection). "1" (Permitted): Permitting check "0"*(Prohibited): Prohibiting check * Set at shipping time...
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: 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, 1C, 21 1, 2, 7, 8, A, C, 1C, 21 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: Mode Select Command (Group 0) Parameter Configuration
3.1 Control/Sense Commands Page Descriptor Byte Page Code Page Header Page Length Parameter Field Figure 3.8 MODE SELECT command (Group 0) parameter configuration a. Header Media type X '00' (default type) must be specified in this field. Byte 2 Bits 7 and 4 of this field have meaning only in the header transferred to the INIT by the MODE SENSE and MODE SENSE EXTENDED commands.
Page 86 Command Specifications If only the "Block descriptor" in this command is changed, the IDD changes the values in the "Sector count/track," Data byte length/physical sector," "Track skew factor" and "Cylinder skew factor," as well as the "Cylinder count" value in the drive parameters (Page 4) in accordance with the contents specified in 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: Mode Select Extended (55)
Command Specifications After changing anything in the "Block descriptor," "Format parameters (Page 3)" or "Drive parameters (Page 4)," with the MODE SELECT or MODE SELECT EXTENDED command, it is impossible to execute a command to access the data on the disk media until execution of the FORMAT UNIT command is completed, and a CHECK CONDITION status (MEDIUM ERROR [=3] / Medium format corrupted [=31-00]) is reported for all such commands.
Page 89 3.1 Control/Sense Commands Figure 3.9 shows the configuration of the parameter list (MODE SELECT parameters) transferred by this command from the INIT. Compared to the 4-byte header in the Group 0 MODE SELECT command, it is necessary for an 8-byte header to be transferred in this command.
Page 90: Mode Sense (1A)
Command Specifications Page Descriptor Byte Page Code Page Header Page Length Parameter Field Figure 3.9 MODE SELECT EXTENDED command (Group 2) parameter configuration 3.1.7 MODE SENSE (1A) Byte X‘1A’ 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 91 3.1 Control/Sense Commands 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 Verify Error Recovery Parameter...
Page 92: Mode Sense Data Type Specifications
Command Specifications 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 93: Mode Sense Command (Group 0) Parameter Configuration
3.1 Control/Sense Commands Header Byte Sense Data Length X‘00’ (Media Type) DPOFUA 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...
Page 94 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"...
Page 95 3.1 Control/Sense Commands Furthermore, when this command specifies to transfer the "Default" value and "Variable" value, the value shown in this field is X '00000000' (which means the maximum number of logical data blocks that it is possible to rank in the "User Space"). b.
Page 96: Mode Sense Extended (5A)
Command Specifications 3.1.8 MODE SENSE EXTENDED (5A) Byte X‘5A’ Page Code 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 97: Rezero Unit (01)
3.1 Control/Sense Commands 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 Length Parameter Field Figure 3.11 MODE SENSE EXTENDED command (Group 2) parameter configuration 3.1.9 REZERO UNIT (01)
Page 98: Start/Stop Unit (1B)
Command Specifications 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 99: Reserve (16)
3.1 Control/Sense Commands Depending on the value specified in the "Immed (immediate)" bit, bit 0 of CDB byte 1, the timing of completion (status byte report) of this command differs as shown below. a. In the case of the start specification ("Start" bit = "1") When the "Immed"...
Page 100 Command Specifications Together with the RELEASE command, this command controls exclusive access to the logical unit (IDD) under a multi-initiator environment. The IDD is reserved by this command for the INIT which issued this command or for some other SCSI device specified in the CDB. The INIT which issues this command must notify the IDD of its own SCSI ID when the SELECTION phase is executed..
Page 101 3.1 Control/Sense Commands 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 102: Reserve Extended (56)
Command Specifications INIT #A can issue INQUIRY, REQUEST SENSE, RELEASE and RESERVE commands to TARG #0, but other commands are rejected with a RESERVATION CONFLICT status. A RELEASE or RELEASE EXTENDED command issued by INIT #A releases TARG #0's reserved state. Also, a RESERVE or RESERVE EXTENDED command changes the reserve state of TARG #0.
Page 103: 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 it is no influence on the IDD's reserve state.
Page 104: Release Extended (57)
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 105 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 106: Log Select (4C)
Command Specifications Sense data cannot be sent due to a hardware error in the IDD An unrecoverable error is detected on the SCSI bus. 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 107 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 108 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 109 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 110: 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 111: 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 112: 3.1.18.1 Persistent Reserve In Service Actions
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 113: 3.1.18.1.2 Read Reservations
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 Scope value and type value Scope-specific address (only the Element scope) When the READ RESERVATION service action is executed, if no persistent reservation is held by...
Page 114: 3.1.18.3 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 115: 3.1.18.3.1 Persistent Reservation Scope
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 116: 3.1.18.3.2 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 117: 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 118: Persistent Reserve Out (5E)
Command Specifications 3.1.19 PERSISTENT RESERVE OUT (5E) Byte X'5E' 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 119: 3.1.19.1 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.
Page 120: 3.1.19.2 Persistent Reserve Out 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 121 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 122: 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 Element ignored ignored valid...
Page 123 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 124: Report Device Identifier (A3)
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" field can be specified only X'05'. The "Allocation Length"...
Page 125: Set Device Identifier (A4)
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 126 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 127: 3.2 Data Access Commands
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 128: Read Extended (28)
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 129: Write (0A)
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 130: Write Extended (2A)
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 131: Write And Verify (2E)
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 132: Verify (2F)
Command Specifications processing is not prohibited, even if a correctable data check is detected during the verify check, it is regarded as if the verify check succeeded. 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)
Page 133: Seek (0B)
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 134: Set Limits (33) (Not Supported)
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 135: 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 136: Synchronize Cache (35)
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 (*) READ LONG PRE-FETCH “WrInh”...
Page 137: 3.3 Format Commands
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. If bit 1 of CDB byte 1, the "Immed (immediate) bit, is "1,"...
Page 138 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 139 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.
Page 140: Format Unit Command Parameter List Configuration
Command Specifications Format parameters Figure 3.13 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 141 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. 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 following “DPRY”...
Page 142 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. “0”...
Page 143: Defect Descriptor: Byte Distance From Index Format
3.3 Format Commands Note: In order to specify an entire track as defective, X ‘FFFFFFFF’ must be specified as the byte distance from the index to the defect position. 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...
Page 144: 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.15 Defect descriptor: physical sector address format 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.
Page 145: Format Unit Command Defect Processing
3.3 Format Commands boundaries (User Space), and is recorded as the G List, but formatting processing is executed only for the User 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.
Page 146 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 147: Reassign Blocks (07)
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 148: 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 149 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...
Page 150: Read Defect Data (37)
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 151: Read Defect Data Command: 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 152 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 153 3.3 Format Commands Defect List Length field: The total number of bytes described in the “Defect List Format” specifying defect data included in the P List and G List. 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”...
Page 154: Maintenance, Diagnostic Commands
Command Specifications When data are in the “Byte Distance from the Index Format,” when the P List is reported, multiple defect position information may be reported for a single sector, or 2 defective sectors may be reported as a single item of defect position information due to defects which extend across sector boundaries.
Page 155: Error Recovery Control Flags During The Self-Diagnosis Test
‘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 156 Command Specifications Note: When “1” is specified in the “SelfTest (self test)” bit in this command, the command execution results are reported by the status byte and the sense data. Therefore, even if the RECEIVE DIAGNOSTIC RESULTS command is executed after this command, the self-diagnosis test execution results are not reported as response data.
Page 157: Send Diagnostic Command: Parameter List Configuration
3.4 Maintenance, Diagnostic Commands When a command other than the RECEIVE DIAGNOSTIC RESULTS command is linked to this command, the execution results (response data) may no longer be secure. Byte Page Code Header Page Parameter Length (MSB) Page Parameter Length (LSB) Page Parameter Parameter...
Page 158: Send Diagnostic Parameters: Page Code List
Command Specifications 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. Figure 3.19 shows the format of this parameter page. The page code list supported by the IDD is transferred to the INIT by the RECEIVE DIAGNOSTIC RESULTS command which is issued following the SEND DIAGNOSTIC command that specifies this parameter page (shown in Section 3.4.2 (1) )
Page 159 3.4 Maintenance, Diagnostic Commands 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 160: Receive Diagnostic Results (1C)
Command Specifications SELF-TEST Code Description 0,0,0 Refer to clause (2), Parameter Specification. 0,0,1 The device server shall start its short self-test routine in the background mode. 0,1,0 The device server shall start its extended self-test routine in the background mode. 0,1,1 Reserved 1,0,0...
Page 161: Receive Diagnostic Results Command: Response Data Configuration
3.4 Maintenance, Diagnostic Commands Notes: Exercise caution in the following points when using this command. In order to avoid damage to the results of SEND DIAGNOSTIC command execution (response data) from a command issued by another INIT during the interval until this command is issued, either this command should be linked to the SEND DIAGNOSTIC command when it is issued or the SEND DIAGNOSTIC command and this command should be executed after the IDD is reserved.
Page 162: Receive Diagnostic Results Response Data: Page Code List
Command Specifications Page parameter length This field shows the byte length of the page parameter after byte 4. Page parameter Data which show the execution results of the operation specified by the SEND DIAGNOSTIC command are reported in this field. Page code list This response data reports the “Page code”...
Page 163: Receive Diagnostic Results Response Data: Logical/Physical Address Conversion
3.4 Maintenance, Diagnostic Commands 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.23 RECEIVE DIAGNOSTIC RESULTS response data: logical/physical address conversion Note: The value of the “Page Parameter Length”...
Page 164: Write Buffer (3B)
Command Specifications The description of address information shown in bytes 6 to 13 is the same as the description specifications in the D List transferred from the INIT by the FORMAT UNIT command. For details, see the description of the FORMAT UNIT command (Section 3.3.1). Furthermore, When the logical block format is used, the address is shown in bytes 6 to 9 and zero is reported in the remaining byte positions.
Page 165: 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...
Page 166 Command Specifications Mode = 0, 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, 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 167 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” concerning the setting terminal. Mode = 0, 1, 0, 1 : Microcode download, with saving In this mode, the controller’s microcode or control information is transferred to the IDD’s control memory area and written to the disk.
Page 168 Command Specifications The "Transfer Byte Length" field specifies the maximum number of bytes that shall be present in the Data-Out Buffer to be stored in the specified buffer beginning at the buffer offset. The INIT should attempt to ensure that the parameter list length plus the buffer offset does not exceed the capacity of the specified buffer.
Page 169: Read Buffer (3C)
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 170: 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. Data transfer is completed at the point when the number of bytes of the header and data from the IDD’s data buffer, specified in the “Transfer byte length”...
Page 171: 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 172: 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 173: Read Long (3E)
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 174: Write Long (3F)
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. The TB flag is treated as if “1”...
Page 175: Write Same (41)
3.4 Maintenance, Diagnostic Commands Sense Key : 05 = ILLEGAL REQUEST Sense Code/Sub-sense Code : 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 176 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 177: 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 178: Mode Select Parameters: Read/Write Error Recovery Parameters
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‘E9’ (=233 bits) Variable X‘00’ X‘00’ (Head Offset Count) X‘00’...
Page 179 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 180 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 181 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.
Page 182 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 183: Combinations Of Error Recovery Flags
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 184 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 185 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 186: Disconnect/Reconnect Parameters (Page Code = 2)
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 187 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 188 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 189 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 190: Format Parameter (Page Code = 3)
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‘0054’ Variable X‘FFFF’...
Page 191 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 192 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 193: Drive Parameter (Page Code = 4)
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. RMB (removable medium) When this bit is "1,"...
Page 194: Mode Select Parameters: Drive Parameters
Parameter Data Formats Byte (See the X‘16’, X‘12’ or X‘0A’ (Page Length) "Note") Cylinder Count Default X‘00xxxx’ Variable X‘000000’ Number of Heads Default X‘00xx’ Variable X‘0000’ "Write Precompensation" Starting Cylinder Default X‘000000’ Variable X’000000’ 9-11 "Reduced Write Current" Starting Cylinder Default X‘000000’...
Page 195: Verify Error Recovery Parameters (Page Code = 7)
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 196: Mode Select Parameters: Verify Error Recovery Parameters
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‘E9’ (=233 bits) Variable X‘00’ X‘0000000000’ (Reserved) 10-11 Recovery Time Limit Default X‘7530’ Variable X‘FFFF’...
Page 197: Caching Parameters (Page Code = 8)
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 198: Mode Select Parameters: Caching Parameters
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 199 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 200 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 201 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. "1"...
Page 202 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. n.
Page 203: Control Mode Parameters (Page Code = 0A)
4.1 Mode Parameters cache segments are occupied by data to be retained. If the number is at least one, caching functions in the other 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 204 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 205 4.1 Mode Parameters Despite the commands whose specified LBAs are overlapped, the IDD conducts reordering operation. Therefore the INIT who specifies "1" in this field shall ensure Data Integrity itself. The IDD disregards "1" in this field and operates as if "0" were specified. When “F”...
Page 206 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 207: Notch Parameter (Page Code = 0C)
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 208 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 209: Informational Exceptions Control Page (Page Code = 1C)
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. This field indicates the ending of the active notch or, if the active notch is zero, the ending of the logical unit (IDD).
Page 210 Parameter Data Formats The log errors bit (LogErr) of zero indicates that the logging of informational exception conditions within a target is vendor specific. A LogErr bit of one indicates the target logs informational exception conditions. A Test bit of one creates a false device failure at the next interval time, if the DExcpt bit is not set. When the Test bit is one, the MRIE and Report count fields apply as if the Test bit were zero.
Page 211 4.1 Mode Parameters 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 212: Additional Error Recovery Parameters (Page Code = 21)
4.1.10 Additional error recovery parameters (page code = 21) The page descriptor format of this MODE SELECT parameter is shown in Figure 4.9 [Fujitsu unique parameter] Byte X‘02’ (Page Length) Number of retries during a Seek Error...
Page 213: Log Parameters
RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit. Log Parameters This clause describes the log page structure and the log pages that are applicable to all SCSI devices.
Page 214: Supprot Log Page (X'00')
Parameter Data Formats 4.2.1 Supprot log page (X'00') The supported log page returns the list of log pages implemented by the drive. Byte X‘00’ (Reserved) X'00' (Parameter Length) X'0C' (Parameter Length) X'00' (Supported Page) X'01' (Supported Page) X'02' (Supported Page) X'03' (Supported Page) X'05' (Supported Page) X'06' (Supported Page)
Page 215: Buffer Overrun / Underrun Page (X'01')
4.2 Log Parameters 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 216: Write Error Count Page (X'02')
Parameter Data Formats 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. Data Overrun Count of data overruns which occur during read operation when a buffer full condition prevents continued transfer of data from the media to the buffer.
Page 217: Write Errors Recovered With Possible Delays (Page 02, Code 0001)
4.2 Log Parameters 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 218: Total Posted Recoverable Write Errors (Page 02, Code 0003)
Parameter Data Formats 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 219: Total Posted Unrecoverable Write Errors (Page 02, Code 0006)
4.2 Log Parameters 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 220: Read Errors Recovered Without Delays (Page 03, Code 0000)
Parameter Data Formats 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 that would not be reported to the initiator during read operations, because no delay is incurred.
Page 221: Total Posted Read Errors (Page 03, Code 0002)
4.2 Log Parameters 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 222: Total Read Bytes Processed (Page 03, Code 0005)
Parameter Data Formats 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 Write 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 223: Verify Error Count Page (X'05')
4.2 Log Parameters 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 224: Vefiry Errors Recovered With Possible Delays (Page 05, Code 0001)
Parameter Data Formats 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 225: Total Posted Recoverable Verify Errors (Page 05, Code 0003)
4.2 Log Parameters 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 226: Total Posted Unrecoverable Verify Errors (Page 05, Code 0006)
Parameter Data Formats 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 227: Temperature Page (X'0D')
4.2 Log Parameters 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 228: Reference Temperature (Page 0D, Code 0001)
Parameter Data Formats 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 229: Date Of Manufacture (Page 0E, Code 0001)
4.2 Log Parameters 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 230: Specified Cycle Count Over Device Lifetime (Page 0E, Code 0003)
Parameter Data Formats 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 231: Application Client Page (X'0F')
4.2 Log Parameters 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 232: Self-Test Result Page (X'10')
Parameter Data Formats 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 233: Smart Status Page (X'2F')
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 234 This page is intentionally left blank.
Page 235: Chapter 5 Sense Data Error Recovery Methods
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 236: Sense Data Basic Information
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 Sense Code Sub-sense Code X‘00’ SKSV Sense Key Inherent Information IDD SCSI ID CDB Operation Code Additional Detailed Information...
Page 237 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 238 Sense Data Error Recovery Methods Sense code, sub-sense code 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 239 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 240: Sense And Subsense Codes
Sense Data Error Recovery Methods Table 5.2 Sense and subsense codes (1 of 5) Sense Name Explanation No additional sense No specific 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 241 5.1 Sense Data Table 5.2 Sense and subsense codes (2 of 5) Sense Name Explanation Sync Byte not found for SB (Sync Byte) could not be detected in the Data area. 1, 3, B Data field Record entity not found Expected data from a sector was undetected.
Page 242 Sense Data Error Recovery Methods Table 5.2 Sense and subsense codes (3 of 5) Sense Name Explanation Partial Defect List Transfer Read Defect Data command (37h) cannot transfer all the Defect data in the target because the numbers of defect exceeded the maximum. Invalid command CDB byte 0 (operation code) is illegal.
Page 243 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 244 Invalid message error An unsupported or inappropriate message was received. Logical unit failed self- The IDD's initial setup failed. ('nn' is a Fujitsu unique code) configuration • A1: SA Read error (any 3/11/** error during SA read) • A3: SA Read error (any 3/13/** error during SA read) •...
Page 245: Sense Data Additional Information
5.2 INIT Error Recovery Methods (Recommended) 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 246: Analysis Of The Termination Status
Sense Data Error Recovery Methods Command issue status received ? Normal end GOOD BUS FREE error ? To item (1) BUSY Timeout ? QUEUE 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 To Section 5.3.2...
Page 247 5.2 INIT Error Recovery Methods (Recommended) 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 248: Sense Data Analysis And Error Recovery Methods
Sense Data Error Recovery Methods 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 249 5.2 INIT Error Recovery Methods (Recommended) Table 5.3 Sense data error classification (2 of 4) Recovery Method Outline of Error (See Table 4.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 250 Sense Data Error Recovery Methods Table 5.3 Sense data error classification (3 of 4) Recovery Method Outline of Error (See Table 4.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 251: Error Recovery Processing Procedures
5.2 INIT Error Recovery Methods (Recommended) Table 5.3 Sense data error classification (4 of 4) Recovery method Error contents (See Table 4.4.) Peripheral device write fault Need Unrecovered read error Sync byte not found for data field Record not found Mechanical positioning error Message error Need...
Page 252 Sense Data Error Recovery Methods 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 253 5.2 INIT Error Recovery Methods (Recommended) 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 254 Sense Data Error Recovery Methods 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 255: Error Logging
5.2 INIT Error Recovery Methods (Recommended) 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 256: Disk Drive Error Recovery Processing
Sense Data Error Recovery Methods 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 257: Auto Alternate Block Allocation Processing
5.3 Disk Drive Error Recovery Processing 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 258 Sense Data Error Recovery Methods 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 259: Error Recovery Processing Control
5.3 Disk Drive Error Recovery Processing 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 260: Disk Drive Errors And Number Of Retries
Sense Data Error Recovery Methods 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) Number of retries during seek error (See Table 5.5) Table 5.5 Disk drive errors and number of retries...
Page 261: Chapter 6 Disk Media 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 262 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 263: Disk Media Initialization
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 264 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 265: 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 266: 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 267: 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 268 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 269: Glossary
Glossary Axial acceleration Acceleration in the recording layer along the line perpendicular to the disk reference surface at a specified rotation speed. Axial acceleration is detected by optical means. Bus Condition This is an asynchronous condition for changing the status transition on the SCSI bus.
Page 270 Glossary Initiator (INIT) This is a SCSI device which initiates input and output operations on the SCSI bus. In this manual, initiator has been abbreviated to "INIT." Logical Unit This is the device unit which is the object of input/output operations on the SCSI bus.
Page 271: Sense Key
Glossary 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. Status This is 1 byte of information reported to the initiator by the target device when execution of each command is completed, which displays the command's...
Page 272 This page is intentionally left blank.
Page 273: 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 274 This page is intentionally left blank.
Page 275 46-8-626-6711 FAX: 886-2-717-4644 FUJITSU ITALIA S.p.A. FUJITSU SYSTEMS BUSINESS (MALAYSIA) SDN. BHD. Via Nazario Sauro, 38 20099 Sesto S. Giovanni (MI), ITALY Fujitsu Plaza, 1A, Jalan Tandang 204, P.O. Box 636 Pejabat Pos TEL: 39-2-26294-1 Jalan Sultan FAX: 39-2-26294-201 46770 Petaling Jaya, Selangor Darul Ehsan, Malaysia...
Page 276 This page is intentionally left blank.
Page 277: Index
Index 10-byte CDB basic format 1-2 12-byte CDB basic format 1-2 6-byte CDB basic format 1-1 basic disconnect processing procedure 1-13 bit 6 1-4 bit 7 1-4 block descriptor 3-23, 3-32, 6-4 accounting date 4-53 length 3-23, 3-32 ACE 3-18 buffer data 3-103, 3-108 active notch 4-32 buffer descriptor 3-109...
Page 278 Index changing reserve condition 3-39 length 3-24, 3-33 CHECK CONDITION status 1-7 verification method 6-6 C list 3-76, 6-1 data buffer 2-1 clocking field 3-8 configuration 2-2 CmdDt 3-3 management 2-1 command configuration and basic operation 2-1 support data 3-9 data byte length/physical sector 4-16 cleared by another INIT 1-20 data defect list 3-88...
Page 279 Index disconnect processing 1-11, 1-12 error state and retry processing procedure exception 1-14 5-22 procedure after COMMAND phase error verification 6-7 execution 1-13 ETC 3-47 procedure after data transfer EVPD 3-3 execution 1-13 EWASC 4-34 disconnect/reconnect parameter 4-10 example of data buffer operation disconnect time limit 4-12 during read 2-3 disk drive error...
Page 280 Index handling illegal CDB 1-5 hard sectoring 4-17 LBCSS 4-26 header 3-16, 3-22, 3-32, 3-78, 3-89 LBIN 3-47 header + data link 1-4 with address specification 3-108 list parameter 3-47 without address specification look-ahead cache feature 2-6 3-103, 3-107 logical block head offset count 4-5 address 1-3 HSEC 4-17...
Page 281 Index mode=0, 0, 1, 1 3-109 operation mode 3-12 mode=0, 1, 0, 0 3-104 setting 2-5 mode=0, 1, 0, 1 3-105 other internal IDD error 5-23 mode=0, 1, 1, 0 3-105 outline of mode=0, 1, 1, 1 3-106 command processing 1-8 mode=1, 0, 1, 0 3-106, 3-110 disk drive error recovery mode=1, 0, 1, 1 3-110...
Page 282 Index parameter specification 3-94 parameter specifying sector format 4-16 RAC 4-30 track format 4-15 RAERP, UAAERP, EAERP, READY ARE PER 4-4, 4-20 HOLDOFF PERIOD 4-30 Perf 4-34 RC 4-3 persistent reservation type 3-54 RCD 4-23 code 3-55 READ 3-65 PERSISTENT RESERVE IN 3-49 READ BUFFER 3-107 parameter data for READ KEYS command 3-108, 3-109, 3-110...
Page 283 RESERVATION CONFLICT status 1-8, parameter 3-96 5-13 sense and subsense code 5-6 to 5-10 RESERVE 3-37 sense code 5-4 reserved by Fujitsu 4-37 sense command 3-1 reserved operation code 1-24 sense data 5-1 RESERVE EXTENDED 3-40 additional information 5-10 reserve right and third party reserve function...
Page 284 Index spindle motor start delay time 3-18 total read bytes processed 4-46 SSEC 4-16 total verify bytes processed 4-49 standard INQUIRY data 3-3, 3-4 total write bytes processed 4-42 starting boundary 4-33 track count/zone 4-15 start specification 3-37 track skew factor 4-16 start-stop cycle counter 4-54 transfer block 4-3 page 4-52...
Page 285 Index WP bit 3-32 WRITE 3-67 X'00' 4-38 WRITE AND VERIFY 3-69, 4-20 X'01' 4-39 WRITE BUFFER 3-102 X'02' 4-40 command 3-103 X'03' 4-43 write cache 2-10 X'05' 4-47 enable 4-23 X'06' 4-50 write error count page 4-40 X'0D' 4-51 write errors recovered X'0E' 4-52 without delay 4-40...
Page 286 This page is intentionally left blank.
Page 287 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 288 This page is intentionally left blank.

This manual is also suitable for:

Map3735 Map3367 Np/nc series Mas3367 Mas3735 Mas3367np ... Show all

Fujitsu MAP3147 Scsi Logical Interface Specifications

CHAPTER 1 Command Processing

CHAPTER 2 Data Buffer Management

CHAPTER 3 Command Specifications

CHAPTER 4 Parameter Data Formats

CHAPTER 5 Sense Data Error Recovery Methods

CHAPTER 6 Disk Media Management

Glossary

Abbreviations

Index

Quick Links

Related Manuals for Fujitsu MAP3147

Summary of Contents for Fujitsu MAP3147