Page 1 C141-C012-01EN MAX3036RC, MAX3073RC, MAX3147RC SERIES MAY2036RC, MAY2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI 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) 2005.10.31 — — *1 Section(s) with asterisk (*) refer to the previous edition when those were deleted. C141-C012...
Page 4 This page is intentionally left blank.
Page 5 Preface This manual explains concerning the 3.5 inch hard disk drives with internal Serial Attached SCSI (SAS) controller. The purpose of this manual is to provide the specifications and functions of SAS for use of these magnetic disk drives incorporated into user systems, and to present the information necessary for creating host system software.
Page 6: Chapter 5 Sense Data And Error Recovery Methods
Preface Chapter 5 Sense Data and Error Recovery Methods This chapter describes the configuration and contents of sense data which report to the host system when an error occurs, etc., key information necessary for error recovery, recommended procedures for error recovery to be executed through host system software and retry processing.
Page 7: Conventions Used In This Manual
Preface CONVENTIONS USED IN THIS MANUAL The model names of the disk drives covered by this manual differ depending on their device types and capacity (*1). In addition, these disk drives are called Intelligent Disk Drive (IDD), "drive" or "device" in this manual. Note: Model Name M AX 3 147 RC Interface type...
Page 8 Preface Conventions for Alert Messages This manual uses the following conventions to show the alert messages. An alert message consists of an alert signal and alert statements. The alert signal consists of an alert symbol and a signal word or just a signal word. The following are the alert signals and their meanings: This indicates a hazardous situation likely to result in serious personal injury if the user does not perform...
Page 9 Preface MANUAL ORGANIZATION Product Manual 1. Outline 2. Specifications 3. Data Format 4. Installation Conditions 5. Installation Procedure 6. Diagnosis and Maintenance Interface Specifications 1. Serial Attached SCSI (SAS) Interface (This Manual) 2. Command Processing 3. Data Buffer Management 4. Command Specifications 5.
Page 10 Preface REFERENCED STANDARDS The product specifications and functions described in this manual conform to the following standards: Specification Concerned Name (document) number organization T10/1562-D Serial Attached SCSI (SAS) American national Revision 05 Standards Institute (ANSI) T10/1601-D Serial Attached SCSI-1.1 (SAS-1.1) American national Revision 07 Standards Institute...
Page 11: Table Of Contents
Contents CHAPTER 1 SAS Interface ................1-1 1.1 Topologies in SAS Interface ..............1-2 1.1.1 SAS Layering ..................1-3 1.1.2 Physical links and phys ............... 1-4 1.1.3 Ports (narrow ports and wide ports) ............ 1-4 1.1.4 SAS devices..................1-6 1.1.5 Pathways....................1-7 1.1.6 Connections..................
Page 12 Contents 1.4.3.3 BREAK....................1-28 1.4.3.4 BROADCAST ................... 1-28 1.4.3.5 CLOSE....................1-29 1.4.3.6 EOAF (End of address frame)............1-29 1.4.3.7 ERROR....................1-29 1.4.3.8 HARD_RESET.................. 1-29 1.4.3.9 NOTIFY..................... 1-30 1.4.3.10 OPEN_ACCEPT ................1-30 1.4.3.11 OPEN_REJECT ................1-30 1.4.3.12 SOAF (Start of address frame) ............1-33 1.4.4 Primitives used only inside SSP and SMP connections ....
Page 13 Contents 1.5.6 SSP link layer ..................1-52 1.5.6.1 SSP frame transmission and reception..........1-53 1.5.6.2 SSP flow control................1-53 1.5.6.3 Interlocked frames................1-53 1.5.6.4 Closing an SSP connection ............... 1-56 1.6 Transport layer ..................1-58 1.6.1 SSP frame format ................1-58 1.6.2 Information units................
Page 14 Contents 2.8.3 Reserved operation code..............2-16 2.8.4 Error recovery processing ..............2-16 2.8.5 Abort processing................2-17 2.8.6 Fatal hardware errors................. 2-20 2.9 Data Block Addressing................2-20 2.9.1 Definition of data space..............2-20 2.9.2 Logical block addressing..............2-23 CHAPTER 3 Data Buffer Management ............3-1 3.1 Data Buffer ....................
Page 15 Contents 4.1.16 LOG SENSE (4D)................4-95 4.1.17 PERSISTENT RESERVE IN (5E) ..........4-126 4.1.18 PERSISTENT RESERVE OUT (5F)..........4-133 4.1.19 REPORT LUNS (A0)............... 4-138 4.1.20 REPORT DEVICE IDENTIFIER (A3) ........... 4-140 4.1.21 SET DEVICE IDENTIFIER (A4)............ 4-142 4.2 Data Access Commands............... 4-143 4.2.1 READ (08) ..................
Page 16 Contents CHAPTER 5 Sense Data and Error Recovery Methods ......5-1 5.1 Sense Data ....................5-1 5.1.1 Sense data format ................5-1 5.1.2 Sense data basic information............... 5-3 5.1.3 Sense data additional information ............. 5-13 5.2 INIT Error Recovery Methods (Recommended) ........5-14 5.2.1 Termination status analysis and error recovery methods ....
Page 17 Contents Illustrations Figures Figure 1.1 SAS drive connection patterns............. 1-2 Figure 1.2 SAS control layers ................1-3 Figure 1.3 Physical links and phys ................ 1-4 Figure 1.4 Ports (narrow ports and wide ports)............. 1-5 Figure 1.5 SAS devices ..................1-6 Figure 1.6 Example of potential pathways............
Page 18 Contents Tables Table 1.1 SAS address format ................1-9 Table 1.2 Hashed SAS address code parameter ..........1-10 Table 1.3 Usage of special characters ..............1-11 Table 1.4 OOB signal timing specifications............1-13 Table 1.5 OOB signal transmitter requirements..........1-14 Table 1.6 OOB signal receiver burst time detection requirements .....1-15 Table 1.7 OOB signal receiver idle time detection requirements .......1-15 Table 1.8 OOB signal receiver negation time detection requirements....1-15 Table 1.9 SAS speed negotiation sequence timing specifications ......1-19...
Page 19 Contents Table 1.42 DATAPRES field ................1-72 Table 1.43 RESPONSE DATA field..............1-74 Table 1.44 RESPONSE CODE field..............1-74 Table 1.45 Exceptional event processing of a drive..........1-81 Table 2.1 6-Byte CDB basic format ..............2-2 Table 2.2 10-Byte CDB basic format ..............2-2 Table 2.3 12-Byte CDB basic format ..............
Page 20 Contents Table 4.30 MODE SELECT parameters: informational exception control page ..................4-66 Table 4.31 MRIE ....................4-68 Table 4.32 Interval timer ..................4-69 Table 4.33 MODE SELECT parameters: background control mode parameter...................4-70 Table 4.34 MODE SELECT parameters: additional error recovery parameters ..................4-72 Table 4.35 MODE SELECT EXTENDED command (group 2) parameter configuration ..................4-74 Table 4.36 Mode page ..................4-76 Table 4.37 MODE SENSE data type specifications..........4-77...
Page 21 Contents Table 4.63 Verify errors recovered with possible delays (page 05, code 0001) ...............4-107 Table 4.64 Total verify errors posted (page 05, code 0002)......4-108 Table 4.65 Total recoverable verify errors posted to INIT (page 05, code 0003) ...............4-108 Table 4.66 Total verify bytes processed (page 05, code 0005) ......4-109 Table 4.67 Total unrecoverable verify errors posted to INIT (page 05, code 0006) ...............4-109 Table 4.68 Non-medium error count page (X'06')..........4-110...
Page 22 Contents Table 4.101 REPORT DEVICE IDENTIFIER parameter list ......4-141 Table 4.102 SET DEVICE IDENTIFIER parameter list........4-143 Table 4.103 Defect list format ................4-155 Table 4.104 FORMAT UNIT command parameter list configuration....4-156 Table 4.105 Defect descriptor: byte distance from index format.....4-159 Table 4.106 Defect descriptor: physical sector address format......4-160 Table 4.107 FORMAT UNIT command defect processing ......4-162 Table 4.108 REASSIGN BLOCK command: defect data list configuration .................4-165...
Page 23: Chapter 1 Sas Interface
CHAPTER 1 SAS Interface Topologies in SAS Interface Names and identifiers Phy layer Link layer Address frames Transport layer This chapter describes the topology, interface protocol, and operation of the SAS interface. C141-C012...
Page 24: Topologies In Sas Interface
SAS Interface 1.1 Topologies in SAS Interface As shown in Figure 1.1, SAS drives have two connection patterns: point-to- point connection and expander connection. SAS HBA (INIT) SATA Drive Drive Drive Drive SSP (Serial SCSI Protocol) SAS HBAs (INIT) SAS Expander (s) SATA Drive Drive...
Page 25: Sas Layering
1.1 Topologies in SAS Interface 1.1.1 SAS Layering As shown in Figure 1.2, for SAS, the following six control layers are defined: • Physical layer: Electric properties related to cables, connectors, and signals • Phy (transceiver) layer: 8B/10B code, OOB, and speed negotiation •...
Page 26: Physical Links And Phys
SAS Interface 1.1.2 Physical links and phys A physical link is a set of four wires used as two differential signal pairs. One differential signal transmits in one direction while the other differential signal transmits in the opposite direction. Data may be transmitted in both directions simultaneously.
Page 27: Figure 1.4 Ports (Narrow Ports And Wide Ports)
1.1 Topologies in SAS Interface A wide port is created if there is more than one phy in the port. A narrow port is a port with only one phy. A wide link is the set of physical links that attach a wide port to another wide port.
Page 28: Sas Devices
SAS Interface 1.1.4 SAS devices A SAS device contains one or more SAS ports, each containing one or more phys (i.e., a SAS port may be a narrow port or a wide port). Each single HDD unit is a separate SAS device. Usually, it is a single port or dual port device, but does not use a wide port.
Page 29: Pathways
1.1 Topologies in SAS Interface 1.1.5 Pathways A potential pathway is a set of physical links between a SAS INIT phy and a SAS TARG phy. When a SAS INIT phy is directly attached to a SAS TARG phy, there is one potential pathway. When there are expander devices between a SAS INIT phy and a SAS TARG phy, there are multiple potential pathways, each consisting of a set of physical links between the SAS INIT phy and the SAS TARG phy.
Page 30: Connections
SAS Interface 1.1.6 Connections A connection is a temporary association between a SAS INIT port and a SAS TARG port. During a connection all dwords from the SAS INIT port are forwarded to the SAS TARG port, and all dwords from the SAS TARG port are forwarded to the SAS INIT port.
Page 31: Names And Identifiers
1.2 Names and identifiers 1.2 Names and identifiers Device names are worldwide unique names for devices within a transport protocol. Port names are worldwide unique names for ports within a transport protocol. Port identifiers are the values by which ports are identified within a domain, and are used as SAS addresses.
Page 32: Hashed Sas Address
SAS Interface 1.2.2 Hashed SAS address SSP frames include a hashed version of the SAS address to provide an additional level of verification of proper frame routing. The code used for the hashing algorithm is a cyclic binary Bose, Chaudhuri, and Hocquenghem (BCH) (63, 39, 9) codes.
Page 33: Phy Layer
1.3 Phy layer 1.3 Phy layer In the phy layer, 8b10b coding and the link reset sequence are defined. 1.3.1 8b10b coding All information transferred in SAS is encoded into 10-bit characters using 8b10b encoding. Information includes data bytes representing data in a frame and control characters used for frame delimiters.
Page 34: Link Reset Sequence
SAS Interface Such encoding also greatly increases the likelihood of detecting any single or multiple bit errors that may occur during transmission and reception of information. In addition, some of the control characters of the transmission code contain a distinct and easily recognizable bit pattern called a comma pattern which assists a receiver in achieving character and dword alignment on the incoming bit stream.
Page 35: Start Conditions Of The Link Reset Sequence
1.3 Phy layer 1.3.3 Start conditions of the link reset sequence Drives start the link reset sequence when they detect any of the following conditions: • The power is turned on. • A loss of signal is detected (OOB from the INIT). •...
Page 36: Figure 1.8 Oob Signal Transmission
SAS Interface Table 1.5 OOB signal transmitter requirements Signal Burst time Idle time Negation time COMINIT/RESET 160 OOBI 480 OOBI 800 OOBI COMSAS 160 OOBI 1440 OOBI 2400 OOBI To transmit an OOB signal, a transmitter shall repeat these steps six times: 1) transmit D.C.
Page 37: Table 1.6 Oob Signal Receiver Burst Time Detection Requirements
1.3 Phy layer Table 1.6 describes the OOB signal receiver requirements for detecting burst times, assuming Tburst is the length of the detected burst time. The burst time is not used to distinguish between signals. Table 1.6 OOB signal receiver burst time detection requirements Detection requirements Signal may detect...
Page 38: Sas Oob Sequency
SAS Interface Figure 1.9 describes SAS OOB signal detection by the SP receiver. COMRESET/COMINIT COMINIT Any transitions negation COMINIT detected COMSAS COMSAS Any transitions negation COMSAS idle idle/Burst pair detected idle/Burst pair ALIGN burst Figure 1.9 OOB signal detection 1.3.5 SAS OOB sequency During the OOB sequence, the INIT and the drive first send the COMINIT signal to each other, then the COMSAS signal.
Page 39: Figure 1.10 Sas To Sas Oob Sequence
1.3 Phy layer Scenario 1: Both SAS phys start SAS OOB sequence at same time COMINIT COMSAS Phy A Tx/ Phy B Rx Time=0 Time=z Phy A Rx/ Phy B Tx COMINIT COMSAS Scenario 2: SAS phy A starts SAS OOB sequence COMINIT COMSAS Phy A Tx/...
Page 40: Exception Handling In The Oob Sequence
SAS Interface 1.3.5.1 Exception handling in the OOB sequence • When the COMINIT signal cannot be detected When a drive sends the COMINIT signal but the COMINIT signal from the other side cannot be detected, the drive waits for the reception of the COMINIT signal from the INIT or expander until the hot-plug timeout time (500 ms) elapses.
Page 41: Figure 1.11 Sas Speed Negotiation Window
1.3 Phy layer ALIGN(0)s ALIGN(1)s Speed negotiation lock time(SNLT) Speed negotiation transmit time(SNTT) Rate change delay time (RCDT) Speed negotiation window Figure 1.11 SAS speed negotiation window Table 1.9 defines the timing specifications for the SAS speed negotiation sequence. Table 1.9 SAS speed negotiation sequence timing specifications Parameter Time Comments...
Page 42 SAS Interface If the phy supports the physical link rate, it shall attempt to synchronize on an incoming series of dwords at that rate for the SNLT. The received dwords may be ALIGN (0) or ALIGN (1) primitives. If the phy achieves dword synchronization within the SNLT, it shall change from transmitting ALIGN (0) primitives to transmitting ALIGN (1) primitives for the remainder of the SNTT (i.e., the remainder of the speed negotiation window).
Page 43: Figure 1.12 Sas Speed Negotiation Sequence (Example 1)
1.3 Phy layer dword no dword no dword dword sync sync sync sync SNTT SNTT SNTT SNTT Phy A Tx/ Phy B Rx dword dword sync sync SNTT SNTT SNTT SNTT Phy A Rx/ Phy B Tx Not supported Not supported by phy B by phy B G2 rate...
Page 44: Phy Reset Sequence After Devices Are Attached
SAS Interface 1.3.6.1 Phy reset sequence after devices are attached Since SAS signal cable connector does not include power lines, it is not possible to detect the physical insertion of the signal cable connector onto a plug. Non- cabled environments may similarly not have a way to detect physical insertion of a device.
Page 45: When The Speed Negotiation Sequence Is Successful
1.3 Phy layer 1.3.6.2 When the speed negotiation sequence is successful When the speed negotiation sequence is successful, the identification sequence (sending and receiving the IDENTIFY frame) is performed subsequently. However, the INIT may have started the hard reset sequence at the time when the drive starts the identification sequence.
Page 46: Link Layer
SAS Interface 1.4 Link layer The link layer defines primitives, address frames, and connections. 1.4.1 Primitives Table 1.10 defines the primitives not specific to the type of connection. Table 1.10 Primitives not specific to type of connection (1/2) From Sequence SAS 1.1 rev7 FJ supported Primitive...
Page 47 1.4 Link layer Table 1.10 Primitives not specific to type of connection (2/2) From Sequence SAS 1.1 rev7 FJ supported Primitive USE (*4) supported prim prim Type EOAF NoConn single supported supported ERROR single supported supported HARD RESET NoConn redundant supported supported NOTIFY (ENABLE SPINUP)
Page 48: Table 1.11 Primitives Used Only Inside Ssp And Smp Connections
SAS Interface Table 1.11 Primitives used only inside SSP and SMP connections From Sequence SAS 1.1 rev7 FJ supported Primitive USE (*4) supported prim prim Type Conn single supported supported CREDIT_BLOCKED Conn single supported supported DONE (NORMAL) Conn single supported supported DONE (RESERVED 0) ↑...
Page 49: Primitive Sequences
1.4 Link layer 1.4.2 Primitive sequences Table 1.12 summarizes the types of primitive sequences. Table 1.12 Primitive sequences Number of times the transmitter Number of times the receiver Primitive transmits the primitive to transmit receives the primitive to detect the sequence type the primitive sequence primitive sequence...
Page 50: Break
SAS Interface Phys shall use ALIGN (0) to construct OOB signals as described in 6.6. Phys shall use ALIGN (0) and ALIGN (1) during the speed negotiation sequence as described in 6.7.4.2. Phys shall rotate through ALIGN (0), ALIGN (1), ALIGN (2), and ALIGN (3) for all ALIGNs sent after the phy reset sequence.
Page 51: Close
1.4 Link layer 1.4.3.5 CLOSE A CLOSE primitive is used to close a connection. When a CLOSE primitive is sent, the close timer (1 ms) is started. If a CLOSE primitive is not received within 1 ms of sending CLOSE primitive, the BREAK primitive is sent. The recipient must send a CLOSE primitive within 1 ms of receiving a CLOSE primitive.
Page 52: Notify
SAS Interface 1.4.3.9 NOTIFY The NOTIFY (ENABLE SPINUP) primitive is sent by a SAS INIT device or expander device. When receiving the NOTIFY (ENABLE SPINUP) primitive in the active wait state of SCSI power conditions, a drive enters the active state. A NOTIFY primitive is sometime used as a substitute for an ALIGN primitive, and it is sent by the initiator or expander at regular intervals.
Page 53: Table 1.13 Open_Reject Abandon Primitives
1.4 Link layer Table 1.13 OPEN_REJECT abandon primitives Processing by the drive that receives the OPEN_REJECT Primitive Issuer primitive OPEN_REJECT Expander Cancels the connection request, and aborts the TASK (BAD DESTINATION) (command). OPEN_REJECT Any phy 1) When the physical link rate is 3.0 Gbps and the connection (CONNECTION RATE NOT link rate is 3.0 Gbps, the drive changes the connection rate to SUPPORTED)
Page 54: Table 1.14 Open_Reject Retry Primitives
SAS Interface Table 1.14 OPEN_REJECT retry primitives Processing by the drive that receives the OPEN_REJECT Primitive Issuer primitive OPEN_REJECT Expander 1) If the I_Tnexus loss timer is working, the drive leaves the (NO DESTINATION) timer working. If the I_Tnexus loss timer has expired, the drive aborts all the commands of the relevant initiator.
Page 55: Soaf (Start Of Address Frame)
1.4 Link layer 3) When the CONNECTION RATE field in the received OPEN frame is not "1.5G or 3.0G", the drive sends the OPEN_REJECT (CONNECTION RATE NOT SUPPORTED) primitive. 4) When, in contradiction to the fact that the physical link rate is 1.5 Gbps, the CONNECTION RATE field in a received OPEN frame is 3.0G, the drive sends the OPEN_REJECT (CONNECTION RATE NOT SUPPORTED) primitive.
Page 56: Primitives Used Only Inside Ssp And Smp Connections
SAS Interface 1.4.4 Primitives used only inside SSP and SMP connections 1.4.4.1 ACK (acknowledge) The ACK primitive indicates that an SSP frame is received normally. When a drive receives an SSP frame, and the CRC field in the received SSP frame is correct, the drive sends the ACK primitive within 1 ms.
Page 57: Table 1.15 Done Primitives
1.4 Link layer Table 1.15 DONE primitives primitive Description When the sender of an SSP frame does neither receive the DONE ACK nor the NAK primitive after sending the SSP frame, the (ACK/NAK TIMEOUT) sender sends the DONE (ACK/NAK TIMEOUT) primitive. DONE This primitive is processed in the same manner as the DONE (RESERVED TIMEOUT 0)
Page 58: Eof (End Of Frame)
SAS Interface Meanwhile, when a drive receives the DONE primitive, the drive performs the following processing: 1) If the drive has SSP frames to send at the time of the receipt of the DONE primitive from the initiator, the drive can send as many SSP frames as there are credits being held at this time.
Page 59: Clock Skew Management
1.4 Link layer 1.4.5 Clock skew management The internal clock for a device is typically based on a PLL with its own clock generator and is used when transmitting dwords on the physical link. When receiving, however, dwords need to be latched based on a clock derived from the input bit stream itself.
Page 60: Scrambling
SAS Interface 1.4.7 Scrambling Scrambling is used to reduce the probability of long strings of repeated patterns appearing on the physical link. All data dwords are scrambled. Table 1.17 lists the scrambling for different types of data dwords. Table 1.17 Scrambling for different data dword types connection state Data dword type Description of scrambling...
Page 61: Address Frames
1.5 Address frames 1.5 Address frames 1.5.1 Address frames overview Address frames are used for the identification sequence and for connection requests. The address frame follows an SOAF and ends with an EOAF. Address frames shall only be sent outside connections. Address frames shall not be terminated early.
Page 62: Identify Address Frame
SAS Interface 1.5.2 IDENTIFY address frame Table 1.19 defines the IDENTIFY address frame format used for the identification sequence. The IDENTIFY address frame is sent after the phy reset sequence completes if the physical link is a SAS physical link. Table 1.19 IDENTIFY address frame format Byte Restricted...
Page 63 1.5 Address frames The ADDRESS FRAME TYPE field shall be set to 0h. An SSP INITIATOR PORT bit set to one specifies that an SSP INIT port is present. An SSP INITIATOR PORT bit set to zero specifies that an SSP INIT port is not present.
Page 64: Open Address Frame
SAS Interface 1.5.3 OPEN address frame Table 1.21 defines the OPEN address frame format used for connection requests. Table 1.21 OPEN address frame format Byte INITIATO PROTOCOL ADDRESS FRAME TYPE (1h) R PORT FEATURES CONNECTION RATE (MSB) INITIATOR CONNECTION TAG (LSB) DESTINATION SAS ADDRESS SOURCE SAS ADDRESS...
Page 65: Table 1.23 Connection Rate Field
1.5 Address frames The ADDRESS FRAME TYPE field shall be set to 1h. The FEATURES field shall be set to zero. The CONNECTION RATE field specifies the connection rate being requested between the source and destination, and is defined in Table 1.23. Table 1.23 CONNECTION RATE field Code Description...
Page 66: Table 1.24 Arbitration Wait Time Field
SAS Interface The COMPATIBLE FEATURES field is set to zero. The destination device ignores the COMPATIBLE FEATURES field. The PATHWAY BLOCKED COUNT field specifies the number of times the port has retried this connection request due to receiving OPEN_REJECT (PATHWAY BLOCKED).
Page 67: Identification And Hard Reset Sequence
1.5 Address frames • DESTINATION SAS ADDRESS: The SAS address when an initiator makes a connection request • SOURCE SAS ADDRESS: The SAS address of the drive • PATHWAY BLOCKED COUNT: At the time of the first connection request, this field is set to 0h. Otherwise, it indicates how many times the OPEN_REJECT (PATHWAY BLOCKED) primitive has been received.
Page 68: Connections
SAS Interface 1.5.5 Connections 1.5.5.1 Connections overview A connection is opened between a SAS INIT port and a SAS TARG port before communication begins. A connection is established between one SAS INIT phy in the SAS INIT port and one SAS TARG phy in the SAS TARG port. SSP INIT ports open SSP connections to transmit SCSI commands, task management functions, or transfer data.
Page 69: Connection Responses
1.5 Address frames 1.5.5.3 Connection responses Table 1.25 lists the responses to an OPEN address frame being transmitted. Table 1.25 Connection responses Response Description Arbitration in progress. When an expander device is trying to open a connection to the selected destination port, it returns an AIP to the source phy.
Page 70: Table 1.26 Arbitration Priority For Open Address Frames Passing On A Physical Link
SAS Interface Each SAS port and expander port shall include an Arbitration Wait Time timer which counts the time from the moment when the port makes a connection request until the request is accepted or rejected. The Arbitration Wait Time timer shall count in microseconds from 0 µs to 32 767 µs and in milliseconds from 32 768 µs to 32 767 ms + 32 768 µs.
Page 71: Aborting A Connection Request
1.5 Address frames 1.5.5.5 Aborting a connection request BREAK may be used to abort a connection request. The source phy shall transmit a BREAK after the Open Timeout timer expires or if it chooses to abort its request for any other reason. After transmitting BREAK, the source phy shall initialize a Break Timeout timer to 1 ms and start the Break Timeout timer.
Page 72: Closing A Connection
SAS Interface 1.5.5.6 Closing a connection CLOSE is used to close a connection of any protocol. After transmitting CLOSE, the source phy shall initialize a Close Timeout timer to 1 ms and start the Close Timeout timer. Table 1.28 lists the responses to a CLOSE being transmitted. Table 1.28 Close connection responses Response Description...
Page 73: Breaking A Connection
1.5 Address frames 1.5.5.7 Breaking a connection In addition to aborting a connection request, BREAK may also be used to break a connection, in cases where CLOSE is not available. After transmitting BREAK, the originating phy shall ignore all incoming dwords except for BREAKs. After transmitting BREAK, the source phy shall initialize a Break Timeout timer to 1 ms and start the Break Timeout timer.
Page 74: Ssp Link Layer
SAS Interface Table 1.30 Rate matching ALIGN and/or NOTIFY insertion requirements Physical Connection Requirement link rate rate 1,5 Gbps 1,5 Gbps None One ALIGN or NOTIFY within every 2 dwords that are not 1,5 Gbps clock skew management ALIGNs or NOTIFYs (i.e., every 3,0 Gbps overlapping window of 2 dwords) 3,0 Gbps...
Page 75: Ssp Frame Transmission And Reception
1.5 Address frames 1.5.6.1 SSP frame transmission and reception During an SSP connection, SSP frames are preceded by SOF and followed by EOF. The last data dword after the SOF prior to the EOF always contains a CRC. An SSP phy checks the frame length and validity of the CRC. Receiving phys must acknowledge ACK or NAK within 1 ms if there is no condition for discarding frames.
Page 76: Table 1.31 Ssp Frame Interlock Requirements
SAS Interface Table 1.31 SSP frame interlock requirements SSP frame type Interlock requirement COMMAND Interlocked TASK Interlocked XFER_RDY Interlocked DATA Non-interlocked RESPONSE Interlocked Before transmitting an interlocked frame, an SSP phy shall wait for all SSP frames to be acknowledged with ACK or NAK, even if credit is available. After transmitting an interlocked frame, an SSP phy shall not transmit another SSP frame until it has been acknowledged with ACK or NAK, even if credit is available.
Page 77: Figure 1.17 Interlocked Frames
1.5 Address frames Of the primitives that may be inserted in SSP frames sent from the SSP INIT port and expander port, a drive can detect the following: a) ACK b) NAK c) RRDY d) CREDIT_BLOCKED e) NOTIFY f) BREAK g) ERROR Meanwhile, the primitives that may be inserted in SSP frames sent from the drive are as follows:...
Page 78: Closing An Ssp Connection
SAS Interface transmitter receiver Non-interlocked frame ACK or NAK ACK or NAK Non-interlocked frame ACK or NAK All non- ACK or NAK interlocked ACK or NAK frames in this ACK or NAK example have the same tag time time Figure 1.18 Non-interlocked frames with the same tag transmitter receiver Non-interlocked frame tag A...
Page 79: Figure 1.20 Closing An Ssp Connection Example
1.5 Address frames b) DONE (CREDIT TIMEOUT) specifies that the transmitter still has SSP frames to transmit but did not receive an RRDY granting frame credit within 1 ms, or the transmitter has received a CREDIT_BLOCKED and has consumed all RRDYs received; and c) DONE (ACK/NAK TIMEOUT) specifies that the transmitter transmitted an SSP frame but did not receive the corresponding ACK or NAK within 1 ms.
Page 80: Transport Layer
SAS Interface 1.6 Transport layer 1.6.1 SSP frame format This layer defines the processing of each of a COMMAND frame, TASK frame, DATA frame, XFER_RDY frame and RESPONSE frame. Table 1.32 contains the definitions of the SSP frame format. An SSP frame consists of the header part, information unit part, and CRC.
Page 81: Table 1.33 Frame Type Field
1.6 Transport layer Table 1.33 defines the FRAME TYPE field. Table 1.33 FRAME TYPE field Information unit size Code Name of frame Information Unit Originator (bytes) DATA frame DATA INIT or TARG 1 to 1024 XFER_RDY Transfer ready SSP TARG port frame COMMAND Command...
Page 82 SAS Interface The TAG field contains a value that allows the SSP INIT port to establish a context for commands and task management functions. For COMMAND frames and TASK frames, the SSP INIT port shall set the TAG field to a value that is unique for the I_T nexus established by the connection. An SSP INIT port shall not reuse the same tag when transmitting COMMAND frames or TASK frames to different LUNs in the same SSP TARG port.
Page 83: Information Units
1.6 Transport layer If necessary, fill bytes are placed after the INFORMATION UNIT field so that the CRC field is aligned on a four-byte boundary. The number of the fill bytes is specified by the NUMBER OF FILL BYTES field. If the transferred bytes in the last DATA frame are not aligned on a four byte boundary, this field is set to the number of the extra bytes (4 - the remainder of (the number of transferred bytes/4) bytes).
Page 84: Table 1.35 Task Attribute Field
SAS Interface ATTRIBUTE code is specified, a drive will treat the task as one with the SIMPLE task attribute. Table 1.35 TASK ATTRIBUTE field Code Task attribute 000b SIMPLE 001b HEAD OF QUEUE 010b ORDERED 011b Reserved 100b ACA (not supported) 101b-111b Reserved The ADDITIONAL CDB LENGTH field contains the length of the...
Page 85 1.6 Transport layer • TAG field The drive checks for duplication of tags. If a tag is found to be duplicated in the SAS address of the port, the drive sends the ACK primitive to temporarily close the connection. Then, after re-establishing a connection, the drive reports the CHECK CONDITION status with the OVERLAPPED COMMANDS DETECTS error.
Page 86: Task Information Unit
SAS Interface 1.6.2.2 TASK information unit Table 1.36 defines the task management function IU. The TASK frame is sent by an SSP INIT port to request that a task management function be processed by the task manager in a logical unit. Table 1.36 TASK information unit Byte (MSB)
Page 87: Table 1.37 Task Management Function Field
1.6 Transport layer Table 1.37 TASK MANAGEMENT FUNCTION field TAG OF Task LOGICAL TASK TO BE Code Management UNIT Description MANAGED function NUMBER field Field Aborts a task that matches with ABORT TASK respect to I-T-L-Q. Aborts all the tasks that match ABORT TASK SET with respect to I-T-L.
Page 88: Xfer_Rdy Information Unit
SAS Interface • TAG field The drive checks for duplication of tags between multiple TASK frames or between a COMMAND frame and a TASK frame. If a tag is found to be duplicated in the INIT, the drive sends the ACK primitive to temporarily close the connection.
Page 89 1.6 Transport layer always zero for the first XFER_RDY frame of a command (drives do not support the ENABLE FIRST BURST field of the COMMAND frame). If any additional XFER_RDY frames are required, the REQUESTED OFFSET field must be set to the value of the REQUESTED OFFSET in the previous XFER_RDY frame plus the value of the WRITE DATA LENGTH field in the previous XFER_RDY frame.
Page 90: Figure 1.21 Example Of Xfer_Rdy Frames
SAS Interface Table 1.39 An example of requested offset WRITE DATA XFER_RDY frame REQUESTED OFFSET LENGTH First frame 0000h 0400h Second frame 0400h 0400h Third frame 0800h 0400h • WRITE DATA LENGTH field This field is used to set the number of data bytes that the drive can receive. The WRITE DATA LENGTH field indicates the actual number of data bytes to be received by the drive, and may not be divisible by four.
Page 91: Data Information Unit
1.6 Transport layer 1.6.2.4 DATA information unit Table 1.40 defines the data IU. The DATA frame is sent by an SSP INIT port to deliver write data (i.e., a write DATA frame) and is sent by an SSP TARG port to deliver read data (i.e., a read DATA frame).
Page 92 SAS Interface The initial read DATA frame for a given command shall set the DATA OFFSET field to zero. If any additional read DATA frames are required, the DATA OFFSET field shall be set to the value of the previous read DATA frame’s data offset plus the previous read DATA frame’s data length.
Page 93 1.6 Transport layer • DATA OFFSET field The DATA OFFSET field is used to check whether frames are being transferred in the correct order. When the drive receives a frame with an offset value that the drive does not expect, the drive sends the ACK primitive and CREDIT_BLOCKED primitive, and discards the DATA frame.
Page 94: Response Information Unit
SAS Interface 1.6.2.5 RESPONSE information unit Table 1.41 defines the response IU. The RESPONSE frame is sent by an SSP TARG port to deliver SCSI status (e.g., GOOD or CHECK CONDITION) and sense data, or to deliver SSP-specific status (e.g., illegal frame format). The maximum size of the RESPONSE frame is the maximum size of any IU in an SSP frame.
Page 95 1.6 Transport layer The SSP TARG port shall return a RESPONSE frame with the DATAPRES field set to RESPONSE_DATA in response to every TASK frame and in response to errors that occur while the transport layer is processing a COMMAND frame. The SSP TARG port shall return a RESPONSE frame with the DATAPRES field set to SENSE_DATA if a command completes with sense data to return (e.g., CHECK CONDITION status).
Page 96: Table 1.43 Response Data Field
SAS Interface Table 1.43 RESPONSE DATA field Byte Reserved Reserved Reserved RESPONSE CODE Table 1.44 defines the RESPONSE CODE field, which specifies the error condition or the completion status of a task management function. Table 1.44 RESPONSE CODE field Code Description TASK MANAGEMENT FUNCTION COMPLETE INVAILD FRAME...
Page 97 1.6 Transport layer When the drive sends a RESPONSE frame, the following values are set: • HASHED DESTINATION SAS ADDRESS field The hashed SAS address of the COMMAND frame is set. • HASHED SOURCE SAS ADDRESS field The hashed SAS address of the drive is set. •...
Page 98: Sequences Of Ssp Frames
SAS Interface 1.6.3 Sequences of SSP frames Figure 1.22, Figure 1.23, Figure 1.24, and Figure 1.25 show examples of the sequences of frames for single task management functions and commands. Frames may be interleaved in any order when multiple commands and/or task management functions are outstanding.
Page 99: Figure 1.23 Example Of Write Command
1.6 Transport layer Figure 1.23 shows the sequence of SSP frames for a write command. Figure 1.23 Example of write command Figure 1.24 shows the sequence of SSP frames for a read command. Figure 1.24 Example of read command C141-C012 1-77...
Page 100: Figure 1.25 Example Of Bidirectional Command
SAS Interface Figure 1.25 shows the sequence of SSP frames for a bidirectional command. Figure 1.25 Example of bidirectional command 1-78 C141-C012...
Page 101: Exceptional Event Processing Of A Drive
1.6 Transport layer 1.6.4 Exceptional event processing of a drive If an exceptional event of the SAS protocol system (refer to Table 1.45) occurs in a drive, the drive temporarily rejects an SSP frame from the SSP INIT port due to recovery processing (abort processing).
Page 102: Figure 1.26 Example Of The Processing Sequence For An Exceptional Event
SAS Interface Figure 1.26 shows an example of the processing sequence a drive performs for an exceptional event. Figure 1.26 Example of the processing sequence for an exceptional event 1-80 C141-C012...
Page 103: Table 1.45 Exceptional Event Processing Of A Drive
1.6 Transport layer Table 1.45 lists the events for which a drive performs exceptional event processing. Table 1.45 Exceptional event processing of a drive (1/2) Exceptional event Processing TASK TASK frame Aborts a task that matches with respect to I-T-L-Q, and reports management (ABORT TASK) TASK MANAGEMENT FUNCTION COMPLETE.
Page 104 SAS Interface Table 1.45 Exceptional event processing of a drive (2/2) Exceptional event Processing Transmitting Ack timeout in XFER_RDY Reports for ACK/NAK TIMEOUT (0B/4B/03). system sending NAK reception in Reports for NAK RECEIVED (0B/4B/04). XFER_RDY sending ACK timeout in DATA Reports for ACK/NAK TIMEOUT (0B/4B/03).
Page 105: Chapter 2 Command Processing
CHAPTER 2 Command Processing Command Format Status Byte Command Queuing Function UNIT ATTENTION Condition Sense Data Hold State Power Condition LED Display Command Processing Exceptions Data Block Addressing In this chapter, the basic theory and specifications concerning IDD command processing functions are described. The IDD operates as the target (TARG).
Page 106: Table 2.1 6-Byte Cdb Basic Format
Command Processing Table 2.1 6-Byte CDB basic format Byte Operation Code Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Data Length Control Byte Table 2.2 10-Byte CDB basic format Byte Operation Code Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB)
Page 107: Table 2.3 12-Byte Cdb Basic Format
2.1 Command Format Table 2.3 12-Byte CDB basic format Byte Operation Code Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Data Length (MSB) Transfer Data Length (LSB) Transfer Data Length (MSB) Transfer Data Length (LSB) Control Byte The meanings of each of the fields in the CDB are explained below.
Page 108 Command Processing Group 3 (“011”): Reserved Operation Code (Shown in Section (6)) Group 4 (“100”): 16-byte CDB Group 5 (“101”): 12-byte CDB (Shown in Section 2.3) Group 6 (“110”): Vendor unique CDB (shown in Section 2.8.3) Group 7 (“111”): Vendor unique CDB (shown in Section 2.8.3) b.
Page 109: Table 2.5 Control Byte
2.1 Command Format b. Transfer byte length or parameter list length When the transfer data length is specified as the “Transfer Byte Length” or “Parameter List Length”, this field specifies the length of the data transferred between the INIT and IDD by that command in number of bytes. When zero is specified in this field, data transfer is not executed, except in cases where it is particularly stipulated in the specifications for individual commands in Chapter 4.
Page 110: Status Byte
Command Processing 2.2 Status Byte The format of the status byte and the types of status which the IDD supports are shown in Table 2.6. The status byte is 1 byte of information in the RESP (response) frame which notifies the INIT from the TARG after a command is completed, and which shows the results of executing the command.
Page 111 2.2 Status Byte b) If the sense key in the sense data shows UNIT ATTENTION [= 6], it shows that the IDD is being kept in the Unit Attention state. For details of the Unit Attention state, see item 2.4. c) Any cases other than the above indicate that it was impossible to execute the command or the command ended abnormally.
Page 112: Command Queuing Function
Command Processing 2.3 Command Queuing Function The IDD is equipped with the command queuing function. Through command queuing, the IDD can receive multiple commands in advance and can execute them. Through the tagged queuing function, the IDD can receive multiple commands from the same INIT or from different INITs until the command queue is full.
Page 113: Unit Attention Condition
2.4 UNIT ATTENTION Condition The RESERVE, RELEASE, RESERVE EXTENDED, and RELEASE EXTENDED commands should be issued with the specification of ORDERED QUEUE. If any of these commands is issued with the specification of HEAD OF QUEUE, the command may cause the duplicated reserved status with a command that has been issued before.
Page 114: Response And Release Condition At Unit Attention Condition Hold State
Command Processing (4) Commands cleared by another INIT If the following events have occurred, the command which is currently being executed and commands in the queue are cleared, and this Unit Attention condition is generated. • The CLEAR TASK SET is issued by any INIT. •...
Page 115: Unit Attention Condition Multiple Hold
2.5 Sense Data Hold State (2) INQUIRY command The INQUIRY command is executed normally, but the Unit Attention condition is not cleared. (3) REQUEST SENSE command The IDD executes the REQUEST SENSE command normally, and sends the sense data which show the Unit Attention condition which is currently being held to the INIT.
Page 116: Power Condition
Command Processing 2.6 Power Condition The IDD has three power condition states: Active, Active_Wait, and Stopped. Powered_On Active_Wait Active NOTIFY (ENABLE SPINUP) Stopped STOP STOP START • Active_Wait state In this state, the IDD is waiting for motor start with NOTIFY (ENABLE SPINUP).
Page 117 2.6 Power Condition REQUIRED [= 04-02]" is reported as sense data. When the IDD receives the START command, it enters the Active_Wait state. The IDD enters the Active_Wait state after the power is turned on. When the spindle motor reaches the state of steady rotation with NOTIFY for the first time after the power is turned on, the IDD reads the "System Information"...
Page 118: Led Display
Command Processing 2.7 LED Display Table 2.7 lists the items displayed by the IDD READY LED. Table 2.7 LED display Mode Page 19 Ready LED Meaning a) On when a command is not being executed. Active state (power b) Flashes when a condition) a) Off when a command command is being...
Page 119: Illegal Lun Specification
2.8 Command Processing Exceptions The IDD terminates abnormally all commands and tasks (which are being executed or are being queued) which it has already received from an overlapping INIT and also terminates abnormally both the command or task that caused the overlap, in the order described below.
Page 120: Reserved Operation Code
Command Processing 2.8.3 Reserved operation code Group 6, 7 command operation codes (X‘C0’ ~ X‘FF’) are reserved by Fujitsu. When any command which has these operation codes is issued, the IDD may not necessarily respond with the CHECK CONDITION status (ILLEGAL REQUEST [= 5] Invalid command operation code [= 20-00]).
Page 121: Abort Processing
2.8 Command Processing Exceptions The start of execution timing for this automatic readjustment operation is ordinarily impossible for the INIT to predict. The automatic readjustment operation is performed when there is no command being executed or waiting in the queue, but execution of commands issued immediately after the IDD starts a readjustment operation is caused to wait until the readjustment operation is completed.
Page 122 Command Processing (1) HARD RESET HARD RESET is used to abort all commands and to initialize the IDD to restore it to the same state as at the time of power-on. After this reset operation, the UNIT ATTENTION condition with SCSI Reset Occurred [= 06-29-02] is generated for all the INITs.
Page 123: Table 2.10 Reset Processing During Write
2.8 Command Processing Exceptions Table 2.10 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 SEND DIAGNOSTIC (Write/Read Test) point when that processing is completed.
Page 124: Fatal Hardware Errors
Command Processing 2.8.6 Fatal hardware errors (1) Self-diagnostic errors If a fatal error was detected in the hardware through an initial self-diagnosis, off- line self-diagnosis or on-line self diagnosis (SEND DIAGNOSTIC Command), turning of the spindle motor is stopped. When in this state, the IDD reports the CHECK CONDITION status for all Input/Output operation requests except the REQUEST SENSE command.
Page 125 2.9 Data Block Addressing A spare sector area (replacement area) is assured in the user space for replacement of defective sectors. The user can (using the MODE SELECT or MODE SELECT EXTENDED command), allocate several sectors in the final track of each cylinder and several cylinders (replacement cylinders) inside the user space (replacement cylinders) as the replacement area.
Page 126: Figure 2.1 Data Space Configuration
Command Processing Physical cylinder [System space] Cylinder 0 Track 0 Cylinder 0 Track 1 Cell 0 (Cell) Cylinder 0 Zone 0 Track (m-1) Cell n-1 (Cell) [User space] Track 0 Alternate cell (b tracks) Zone 1 Cylinder (a-1) Zone (x-1) Alternate (c cylinders) cylinder...
Page 127: Logical Block Addressing
2.9 Data Block Addressing 2.9.2 Logical block addressing The IDD uses logical data block addressing which is not dependent on the disk drive’s physical structure as the method of data access on the disk medium. The IDD makes correspondence between each physical sector and each logical data clock address during formatting.
Page 128 This page is intentionally left blank.
Page 129: Chapter 3 Data Buffer Management
CHAPTER 3 Data Buffer Management Data Buffer Look-Ahead Cache Feature 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. 3.1 Data Buffer 3.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 operations between INIT (initiator) and a disk drive.
Page 130: Figure 3.1 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 3.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 131 3.1 Data Buffer 5) If the number of blocks specified in the command to be transferred is larger than the capacity of a cache segment and if the data transfer speed of the INIT is lower than the data transfer speed of the disk drive, the empty space in the data buffer disappears from step 3) and the IDD may soon not be able to read data from the disk media (data overrun).
Page 132: Look-Ahead Cache Feature
Data Buffer Management 3.2 Look-Ahead Cache Feature In order to use the data buffer more effectively and improve the disk drive's effective access speed, the IDD is equipped with a simple cache feature called a "Look-Ahead Cache Feature." The Look-Ahead cache feature is an effective, simple cache function for an INIT which reads data blocks on the disk media sequentially using multiple commands.
Page 133 3.2 Look-Ahead Cache Feature a) Data read by a READ or a READ EXTENDED command and which have been read to the data buffer by Look-Ahead are data which are objects of caching. Depending on the timing for halting Look-Ahead, it is possible that data read by the READ command will be overwritten by Look-Ahead.
Page 134: Caching Parameters
Data Buffer Management − MODE SELECT EXTENDED − MODE SENSE EXTENDED − READ CAPACITY − READ DEFECT DATA (12) − REASSIGN BLOCKS − RELEASE EXTENDED − RESERVE EXTENDED − WRITE BUFFER − WRITE SAME c) If the data buffer where data which are objects of caching are stored is used by any of the following commands, the data existing in that data buffer which are objects of caching are disabled.
Page 135: Look-Ahead Operation, Look-Ahead Volume
3.2 Look-Ahead Cache Feature 3.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 136 This page is intentionally left blank.
Page 137: Chapter 4 Command Specifications
CHAPTER 4 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. 4.1 Control/Sense Commands 4.1.1 TEST UNIT READY (00) Byte X‘00’...
Page 138: Inquiry (12)
Command Specifications 4.1.2 INQUIRY (12) Byte X‘12’ CmdDt EVPD Page Code/Operation Code Transfer Byte Length This command transfers the information showing the IDD's characteristics (INQUIRY data) to the application client. This command is executed normally even in cases where the UNIT ATTENTION condition is held, and the UNIT ATTENTION condition is not cleared.
Page 139 4.1 Control/Sense Commands (1) 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 INIT. b) If the specification in this bits is one, product information called VPD (vital product data) is transferred to the INIT.
Page 140: Table 4.1 Standard Inquiry Data
MultiP MCHNGR Obsolete Addr16 SCSI-3 RelAdr obsolute Wbus16 Sync Linked TranDis CmdQue SCSI-3 FUJITSU (Vendor ID: ASCII) ---- (Product ID: ASCII) Microcode Version No. (ASCII) ---- (Product Revision: ASCII) Device Serial No. (ASCII) 48-55 X‘00’ (Vendor Specific) Reserved CLOCKING SCSI-3 X‘00’...
Page 141: Table 4.2 Version Field
4.1 Control/Sense Commands Qualifier field (0,0,0): The specified logical unit shows the type of input/output device shown in the "Device Type Code" field. Even if this code is reported, it does not mean that that logical unit is in the ready state.
Page 142 Command Specifications Response data format field This field shows the code which shows the standard INQUIRY data format. The definition of the code is (0,0,0,1) for SCSI-1/CCS mode or (0,0,1,0) for SCSI-2 or SCSI-3 mode. Additional data length This field shows the length of the INQUIRY data (byte length) after byte 5. This value shows the length in the INQUIRY data held by the IDD without relation to the specification in the transfer byte length field in the CDB, and is always X‘5B’...
Page 143: Table 4.3 Command Queuing
Not defined 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 144: Table 4.4 Version Descriptor
Command Specifications Clocking field "0" as Reserved. m. QAS (Quick Arbitrate Supported) bit "0" as Reserved. IUS (Information unit supported) bit "0" as Reserved. Version Descriptor field This field is provided for identifying up to eight standards to which the Device claims conformance.
Page 145: Table 4.5 Command Support Data
4.1 Control/Sense Commands (6) Command support data Table 4.5 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. Table 4.5 Command support data Byte Qualifier...
Page 146: Table 4.6 Support
Command Specifications Table 4.6 Support "Support" Bit Description Data about the requested SCSI operation code is not currently available. The device server does not support the tested SCSI operation code. All data after byte 1 is undefined. Reserved The device server supports the tested SCSI operation code in conformance with an SCSI standard.
Page 147: Table 4.7 Vpd Information
4.1 Control/Sense Commands (7) VPD information When "1" is specified in the "EVPD" bits of the CDB, the VPD information described below is transferred to the INIT by this command. The INIT specifies the type of VPD information required in the "Page code" field of the CDB.
Page 148: Table 4.9 Vpd Information: Device Serial No
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 '00') of this VPD information itself. Also, the "Page length" field in byte 3 indicates the length (byte length) after byte 4.
Page 149: Table 4.10 Vpd Information: Device Unique Information
4.1 Control/Sense Commands Device unique information This VPD information reports the IDD unique information. The format of this VPD information is shown in Table 4.10. Table 4.10 VPD information: device unique information (1/2) Byte Qualifier Device Type Code X’83’ (Page Code) X’00’...
Page 150 Command Specifications Table 4.10 VPD information: device unique information (2/2) Byte Identifier length (X’04’) Reserved Reserved (MSB) Relative target port identifier (X’0001’ or X’0002’) (LSB) Target device name PROTOCOL IDENTIFIER (0h) CODE SET (3h) Reserved Association Identifier type (8h) (’0b’) (’0’b) (’10b’) Reserved...
Page 151 The first eight bytes are the Vender ID(SPC-2 Annex C). The rest of the data depends on the organization indicated in the Vender ID. Fujitsu recommends indicating the Product ID of the Standard INQUIRY followed by the serial number of VPD Page 80. "2h": Indicates a 64 bit long IEEE extended unique ID(EUI-64) "3h":...
Page 152: Table 4.11 Vpd Information: Operation Mode
Command Specifications h. IDENTIFIER for the target port Indicates the SAS address. Relative target port identifier Indicates the relative port identifier of the target port on which the INQUIRY command was received. "0001h": Relative port 1, historically known as portA. "0002h": Relative port 2, historically known as portB.
Page 153 4.1 Control/Sense Commands − UNTATN (UNIT ATTENTION Report Mode) When the IDD is holding the Unit Attention condition, this specifies methods of response to commands received from the INIT. "1" (Report): Report the "CHECK CONDITION" status (SCSI standard specifications) for commands other than the INQUIRY and REQUEST SENSE commands.
Page 154: Read Capacity (25)
Command Specifications 4.1.3 READ CAPACITY (25) Byte X‘25’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) This command transfers information related to the disk drive's capacity and the data block size to the INIT. When bit 0 "PMI (partial medium indicator)"...
Page 155: Mode Select (15)
4.1 Control/Sense Commands Table 4.12 READ CAPACITY data 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) 4.1.4 MODE SELECT (15) Byte X‘15’ Parameter List Length This command performs setting and changing of each type of parameter related to disk drive physical attributes, data format, timing of FC interface transferring processing and error recovery procedures, etc.
Page 156 Command Specifications When the "PF (page format)" bit in CDB byte 1 is "1," it indicates that the MODE SELECT parameters transferred from the INIT by this command are in the "Page Descriptor" format. The IDD disregards the value specified in this bit and regards the MODE SELECT parameters transferred from the INIT as being in the "Page Descriptor"...
Page 157: Figure 4.1 Mode Select Parameter Structure
4.1 Control/Sense Commands The IDD has a common set of "Current", "Save" and "Default" values of all the MODE SELECT parameters for all the INITs. When the IDD's power is switched on, when HARD RESET is received, LOGICAL UNIT RESET TASK is received, the "Current" MODE SELECT parameter values are changed to the "Save"...
Page 158 Command Specifications The MODE SELECT parameters include parameters which can be changed by the INIT as desired, parameters which the INIT cannot change, which whose values are determined by the IDD unilaterally and parameters which can be changed by the INIT within certain appropriate limits. The IDD also contains parameter fields which are applicable for rounding processing ("rounding up"...
Page 159: Table 4.13 Mode Select Command (Group 0) Parameter Configuration
4.1 Control/Sense Commands Table 4.13 MODE SELECT command (Group 0) parameter configuration Header Byte X‘00’ X‘00’ (Media Type) × × X‘00’ or X‘08’ (Product Descriptor Length) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X‘00’...
Page 160 Command Specifications 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 161 4.1 Control/Sense Commands If less than 512 bytes is specified in this field, the IDD performs rounding processing (there is a rounding processing report), setting the data block length at 512 bytes. If more than 528 bytes is specified, rounding processing is performed (there is a rounding processing report), setting the data block length at 528 bytes.
Page 162: Table 4.14 Mode Select Parameters
Command Specifications d. MODE SELECT parameters of the IDD The parameter list configuration and its length that can be transferred to the IDD by the INIT in the MODE SENSE or MODE SENSE EXTENDED command are as shown in Table 4.14. If a "Page descriptor" that is not supported by the IDD is specified, the command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in parameter list [=26-00]), and all the MODE SELECT parameters transferred in the...
Page 163 4.1 Control/Sense Commands 1) The MODE SELECT parameter is ordinarily different in its configuration depending on the input/output device and the type of controller. It is also possible that current definitions may be expanded in accordance with the expansion of the functions of the IDD in the future.
Page 164: Table 4.15 Mode Select Parameters: Read/Write Error Recovery Parameters
Command Specifications (1) Read/Write error recovery parameters (page code = 1) Table 4.15 lists the format of the page descriptor of this MODE SELECT parameter. Table 4.15 MODE SELECT parameters: read/write error recovery parameters Byte X‘0A’ (Page Length) AWRE ARRE Default Variable Number of retries during READ...
Page 165 4.1 Control/Sense Commands Error recovery parameters defined in this page descriptor are applicable for the following commands, except in cases where it is specifically pointed out. • READ • READ EXTENDED • READ LONG • SEND DIAGNOSTIC (Write/read test) • WRITE •...
Page 166 Command Specifications TB (transfer block) "1": Data blocks which contain errors that are impossible to correct are transferred to the INIT during a read operation. "0": Data blocks which contain errors that are impossible to correct are not transferred to the INIT during a read operation. d.
Page 167 4.1 Control/Sense Commands h. DCR (disable correction) "1": Even when a correctable data check has been detected, data correction according to the ECC is prohibited. However, On-the-fly correction processing is not prohibited. "0": When a correctable data check has been detected, data correction according to the ECC is applied.
Page 168 Command Specifications Data strobe offset count (not supported) This field specifies in two's-complement notation an incremental position to where the recovered data strobe is adjusted from its nominal setting. Any value specified in this field does not preclude the device server from using positive or negative data strobe offset during error recovery.
Page 169: Table 4.16 Combination Of Error Recovery Flags
4.1 Control/Sense Commands Table 4.16 Combination of error recovery flags (1/4) Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. If possible, data correction is executed afterward according to the ECC.
Page 170 Command Specifications Table 4.16 Combinations of error recovery flags (2/4) Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. Data correction is not executed according to the ECC. 2.
Page 171 4.1 Control/Sense Commands Table 4.16 Combinations of error recovery flags (3/4) Error Recovery Procedure 1. When a correctable data check is detected, immediately, correction is executed according to the ECC. For data checks which cannot be corrected, rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count"...
Page 172 Command Specifications Table 4.16 Combinations of error recovery flags (4/4) Error Recovery Procedure 1. When a correctable data check is detected, immediately, correction is executed according to the ECC. For data checks which cannot be corrected, rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count"...
Page 173: Table 4.17 Mode Select Parameters: Disconnect/Reconnect Parameters
4.1 Control/Sense Commands (2) Disconnect/reconnect parameters (page code = 2) The format of the page descriptor in this MODE SELECT parameter is shown in Table 4.17. Table 4.17 MODE SELECT parameters: disconnect/reconnect parameters Byte X ' 0E ' (Page Length) X ' 00 ' X ' 00 ' Bus Inactivity Ratio...
Page 174 Command Specifications Connect time limit This parameter specifies the maximum period of time for which the open state of the connection can be maintained before the TARG starts the closing processing as a multiple of 100 µs. This value of the IDD is infinite. This parameter cannot be changed by INITs.
Page 175: Table 4.18 Mode Select Parameters: Format Parameters
4.1 Control/Sense Commands (3) Format parameters (page code = 3) The Page descriptor format of this MODE SELECT parameter is shown in Table 4.18. Table 4.18 MODE SELECT parameters: format parameters Byte X‘16’ (Page Length) Track Count/Zone Default X‘xxxx’ Variable X‘0000’...
Page 176 Command Specifications 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 177 4.1 Control/Sense Commands b. Parameters specifying track format (bytes 10, 11) − Sector count/track This parameter specifies the number of physical sectors per 1 track. In the IDD, the number of physical sectors in a track is set unilaterally according to the data format specified by the "Data Block Length" parameter in the block descriptor or the "Data byte length/Physical sector"...
Page 178 Command Specifications The IDD disregards the value specified in this field and sets the optimum track skew value in the specified data block length. See Chapter 3, "Data Format" in the Product Manual for details about track skew. This parameter indicates the value of zone specified in active notch of Page C. If it is 0, this parameter indicates the value in zone 0.
Page 179: Table 4.19 Mode Select Parameters: Drive Parameters
4.1 Control/Sense Commands (4) Drive parameters (page code = 4) The page descriptor format of this MODE SELECT parameter is shown in Table 4.19. Table 4.19 MODE SELECT parameters: drive parameters Byte X‘16’ (Page Length) Cylinder Count Default X‘xxxxxx’ Variable X‘000000’...
Page 180 Command Specifications 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 181: Table 4.20 Mode Select Parameters: Verify Error Recovery Parameters
4.1 Control/Sense Commands (5) Verify error recovery parameters (page code = 7) The page descriptor format of this MODE SELECT parameter is shown in Table 4.20. Table 4.20 MODE SELECT parameters: verify error recovery parameters Byte X‘0A’ (Page Length) (Reserved) Default Variable Number of retries during VERIFY.
Page 182 Command Specifications Error recovery flags − EER (enable early recovery) − PER (post error) − DTE (disable transfer on error) − DCR (disable correction) The definitions and functions of these control flags are the same as for the read/write error recovery parameters. See item (1) concerning the details. b.
Page 183: Table 4.21 Mode Select Parameters: Caching Parameters
4.1 Control/Sense Commands (6) Caching parameters (page code = 8) The page descriptor format of this MODE SELECT parameter is shown in Table 4.21. Table 4.21 MODE SELECT parameters: caching parameters Byte X‘12’ (Page Length) ABPF DISC SIZE Default Variable Demand Read Retention Priority Write Retention Priority Default...
Page 184 Command Specifications The parameters defined in this page descriptor control the range of look-ahead data in the Look-Ahead cache feature and enable or disable the caching operation. See Section 3.2, "Look-Ahead Cache Feature" and Section 3.3, "Write Cache" concerning details of the Look-Ahead cache feature and parameter setting methods.
Page 185 4.1 Control/Sense Commands "1": This enables the write cache. Write data remains in the buffer memory, the cache is made the object even for a read command, and when all of the write data has been received, "GOOD" status is reported without waiting for writing data to the disk media.
Page 186 Command Specifications "1": Data put into the cache via a READ command was replaced sooner than data placed into the cache by other means. "0": Indicates the device server was not distinguish between retaining the indicated data and data placed into the cache memory by other means. h.
Page 187 4.1 Control/Sense Commands Maximum pre-fetch control block count (not supported) This parameter specifies the maximum quantity of logical data blocks pre- fetched to the data buffer with the READ command or READ EXTENDED command. In the IDD the maximum pre-fetch quantity cannot be limited. This parameter cannot be changed.
Page 188 Command Specifications This parameter indicates the same value for all initiators and if it is changed by any initiator, a UNIT ATTENTION condition (UNIT ATTENTION [=6] / Mode select parameter changed [=2A-01]) is generated for all the initiators that did not change it. This parameter can be changed though the IDD disregards the specification of this field.
Page 189: Table 4.22 Mode Select Parameters: Control Mode Parameters
4.1 Control/Sense Commands (7) Control mode parameters (page code = 0A) The page descriptor format of this MODE SELECT parameter is shown in Table 4.22. Table 4.22 MODE SELECT parameters: control mode parameters Byte X‘0A’ (Page Length) (Reserved) GLTSD RLEC Default Variable Queue Algorithm Qualifier...
Page 190: Table 4.23 Tst
Command Specifications TST (task set type) This field specifies the type of task set defined below. Table 4.23 TST 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".
Page 191: Table 4.24 Qerr
4.1 Control/Sense Commands Since the IDD does not support the reporting function of exception condition, the IDD disregards the specification in this bit. DQue (disable queuing) This bit specifies whether the IDD will execute processing of tagged commands or not. "1": The IDD prohibits tagged queuing processing.
Page 192 Command Specifications 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.
Page 193: Table 4.25 Mode Select Parameters: Notch Parameters
4.1 Control/Sense Commands (8) Notch parameters (page code = 0C) Table 4.25 MODE SELECT parameters: notch parameters Byte X‘16’ (Page Length) X‘00’ (Reserved) Default Variable X‘00’ (Reserved) Maximum number of notches Default X‘0012’ Variable X‘0000’ Active Notch Default X‘0000’ Variable X‘FFFF’...
Page 194 Command Specifications Note: Normally, the number of tracks (logical heads) per cell is set in the track count/zone, but in the case of notching only, the total track count (number of cylinders in the zone x number of logical heads) of the affected zone is reported.
Page 195: Table 4.26 Port Control Parameter: Page 0 Format (Short Page Format)
4.1 Control/Sense Commands • Starting Boundary This field is enabled by the MODE SENSE command. This field indicates the beginning of the active notch or, if the active notch is zero, the beginning of the logical unit (IDD). • Ending Boundary This field is valid in the MODE SENSE command.
Page 196 Command Specifications "0": Indicates that the transfer data is in Short Page Format. "1": Indicates that the transfer data is in Long Page Format. b. Ready LED Meaning Specifies the LED display mode when the drive is not executing a command. Depending on the power condition states, the items displayed by the LED are as follows: 0: Active state:...
Page 197: Table 4.27 Port Control Parameter: Sub Page Format (Long Format)
4.1 Control/Sense Commands Table 4.27 Port control parameter: Sub Page Format (Long Format) Byte SPF (1) SUBPAGE CODE (01h) (MSB) Page Length (n-3) (LSB) Reserved x '0000' Reserved NUMBER OF PHYS First SAS phy mode descriptor … … Last SAS phy mode descriptor "0": Indicates that the transfer data is in Short Page Format.
Page 198: Table 4.28 Sas Phy Mode Descriptor Format
Command Specifications Table 4.28 SAS phy mode descriptor format [This page cannot be modified] Byte Reserved (x'00') PHY IDENTIFIER (0h or 1h) PHY OPERATION CODE Reserved (x'00') Reserved ATTACHED DEVICE TYPE Reserved (0b) (0, 0, 1) ('0000'b) Reserved NEGOTIATED PHYSICAL LINK RATE ('0000'b) (8h or 9h) ATTACH...
Page 199 4.1 Control/Sense Commands b. PHY OPERATION CODE The operation code specified by SMP PHY CONTROL is set. ATTACHED DEVICE TYPE "001": Indicates that the device type is End device. d. NEGOTIATE PHYSICAL LINK RATE Indicates the physical link rate value that has been established through a speed negotiation sequence.
Page 200 Command Specifications ATTACHED SAS ADDRESS Indicates the SAS address received from the INIT with an IDENTIFY address frame. m. ATTACHED PHY IDENTIFIER Indicates the phy address received from the INIT with an IDENTIFY address frame. n. PROGRAMMED MINIMUM/MAXIMUM PHYSICAL LINK RATE Indicates the minimum and maximum values of the PHYSICAL LINK RATE supported by a program.
Page 201 4.1 Control/Sense Commands (10) Power condition parameter (page code = 1A) Table 4.29 Power condition parameter: Page 0 Format (Short Page Format) Byte X ' 0A ' (Page Length) X ' 00 ' (Reserved) Idle Standby Default Variable Idle Condition Timer Default X ' FFFF ' Variable...
Page 202: Control Page
Command Specifications Standby (unsupported) Specifies whether to permit the IDD to enter the Standby condition if the IDD does not receive a command within the time specified in the "Standby Condition Timer" field. If "1" is specified, the IDD is permitted to enter the Standby condition after the elapse of the time specified in the "Standby Condition Timer"...
Page 203 4.1 Control/Sense Commands b. TEST "1": If "0" is set for DExcpt, a failure prediction is reported with a failure prediction reporting condition that is generated when the time specified with Interval Timer has elapsed. The method and number of times of this reporting are determined according to the specifications in the MRIE and Report Count fields.
Page 204: Table 4.31 Mrie
Command Specifications Table 4.31 MRIE (1/2) 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 asynchronous event reporting as described in the SCSI-3 Architecture Model and the relevant Protocol Standard.
Page 205: Table 4.32 Interval Timer
4.1 Control/Sense Commands Table 4.31 MRIE (2/2) MRIE Descriptor X’05’ Generate no sense: This method instructs the target to report informational exception conditions by returning a CHECK CONDITION status on any command. The sense key shall be set to NO SENSE and the additional sense code shall indicate the cause of the informational exception condition.
Page 206: Table 4.33 Mode Select Parameters: Background Control Mode Parameter
Command Specifications The "Report Count" field indicates the number of timer to report an informational exception conditions to the application client. A value of zero in the Report Count field indicates there is no limit on the number of timers the target shall report an information exception condition. (12) Background control mode parameter (page code = 1C/subpage = 01) Table 4.33 MODE SELECT parameters: background control mode parameter Byte...
Page 207 4.1 Control/Sense Commands EN_PS (Enable Pre-Scan) "1": a background medium scan operation shall not start until after the pre-scan operation is halted or completed. The BMS interval time shall occur before a background medium scan operation is started. "0": Pre-Scan is disabled. The background pre-scan feature is enabled by setting the EN_PS bit in the Background Control mode page, then setting the EN_PS bit and power cycling the device.
Page 208: Table 4.34 Mode Select Parameters: Additional Error Recovery Parameters
The value specified in this field is applicable for all commands which are accompanied by a seek operation. b. RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit. 4-72...
Page 209: Mode Select Extended (55)
4.1 Control/Sense Commands 4.1.5 MODE SELECT EXTENDED (55) Byte X‘55’ Parameter List Length (MSB) Parameter List Length (LSB) This command performs setting and changing of each type of parameter related to disk drive physical attributes, data format, and error recovery procedures, etc. This command's function is the same as that of the Group 0 MODE SELECT command (Section 4.1.4), except that the format of its data transferred by the INIT differs partially from that of the (MODE SELECT) data format.
Page 210 Command Specifications Table 4.35 MODE SELECT EXTENDED command (group 2) parameter configuration Header Byte X‘00’ X‘00’ X‘00’ (Medium Type) × × X‘00’ X‘00’ X '00' (Block Descriptor Length: LSB) X‘00’ or X‘08’ (block descriptor length: MSB) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB)
Page 211: Mode Sense (1A)
4.1 Control/Sense Commands 4.1.6 MODE SENSE (1A) Byte X‘1A’ Page Code Transfer Byte Length This command reports the values for each type of parameter related to the disk drive's physical attributes, data format, timing for FC interface Loop OPEN/CLOSE processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.
Page 212: Table 4.36 Mode Page
Command Specifications Table 4.36 Mode page Page Code Page Descriptor Name SCSI-3 Byte Read/Write Error Recovery Parameter 12 bytes Disconnect/Reconnect Parameter 16 bytes Format Parameter 24 bytes Drive Parameter 24 bytes Verify Error Recovery Parameter 12 bytes Read Caching Parameter 20 bytes Control Mode Parameter 12 bytes...
Page 213: Table 4.37 Mode Sense Data Type Specifications
4.1 Control/Sense Commands Table 4.37 MODE SENSE data type specifications Type of Parameter Transferred to the INIT 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 214 Command Specifications The "Transfer Byte Length" field in the CDB specifies the total number of bytes of MODE SENSE data which can be transferred to the INIT by this command. The IDD transfers the number of bytes of all the MODE SENSE data specified in the "Page code"...
Page 215: Table 4.38 Mode Sense Command (Group 0) Parameter Configuration
4.1 Control/Sense Commands Table 4.38 MODE SENSE command (group 0) parameter configuration 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’...
Page 216 Command Specifications (1) Header Sense data length This field indicates the length (number of bytes) of the parameter list (MODE SENSE data) which it is possible to transfer to the INIT by this command. The length of the "Sense data length" field itself is not included in this value. Also, a value for a portion of data with a length that is supported by the IDD is reported in this field for a parameter list of the type specified in the CDB regardless of the specification of the "Transfer byte length"...
Page 217 4.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 '000000' (which means the maximum number of logical data blocks that it is possible to rank in the "User Space").
Page 218: Mode Sense Extended (5A)
Command Specifications 4.1.7 MODE SENSE EXTENDED (5A) Byte X‘5A’ Page Code Transfer Byte Length (MSB) Transfer Byte Length (LSB) This command reports the values for each type of parameter related to the disk drive's physical attributes, data format, timing for FC interface Loop OPEN/CLOSE processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.
Page 219: Table 4.39 Mode Sense Extended Command (Group 2) Parameter Configuration
4.1 Control/Sense Commands Table 4.39 MODE SENSE EXTENDED command (group 2) parameter configuration Header Byte Sense Data Length (MSB) Sense Data Length (LSB) X‘00’ (Media Type) DPOFUA X‘00’ X‘00’ X‘00’ (Block Descriptor Length: MSB) X‘00’ or X‘08’ (Block Descriptor Length: LSB) Block Descriptor Byte Data Block Count (MSB)
Page 220: Rezero Unit (01)
Command Specifications 4.1.8 REZERO UNIT (01) Byte X‘01’ This command moves the read/write heads of the disk drive to the initial position (physical cylinder 0 / physical track 0). A data block with the physical block address of zero exists at the initial position. Initialization of the disk drive's positioning control system and automatic adjustment are also performed by this command.
Page 221 4.1 Control/Sense Commands Bit 1 (LoEj (load/eject) of byte 4 of the CDB is the exclusive bit which controls devices with replaceable recording media, and it has no meaning for the IDD. The IDD disregards the value specified in this bit and controls the Power Condition in accordance with the "Start"...
Page 222: Reserve (16)
Command Specifications 4.1.10 RESERVE (16) Byte X‘16’ 3rd Pty 3rd Pty Dev ID × × × × × × × × × × × × × × × × × × × × × × × × Together with the RELEASE command, this command controls exclusive access to the logical unit (IDD) under a multi-initiator environment.
Page 223: Reserve Extended (56)
4.1 Control/Sense Commands (2) Reserve right and third party reserve function The third party reserve function is not supported by the drive. If the 3rd Pty bit of CDB byte 1 is "0," the IDD is reserved for the INIT that has issued this command.
Page 224: Release (17)
Command Specifications 4.1.12 RELEASE (17) Byte X‘17’ 3rd Pty 3rd Pty Dev ID × × × × × × × × 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 does not exist, this command is terminated normally with a GOOD status.
Page 225: Release Extended (57)
4.1 Control/Sense Commands 4.1.13 RELEASE EXTENDED (57) Byte X‘57’ 3rd Pty × × × × × × × × Third Party Devices ID × × × × × × × × × × × × × × × × Same as RELEASE command. 4.1.14 REQUEST SENSE (03) Byte X‘03’...
Page 226 Command Specifications If this command is executed when the IDD is holding the Unit Attention condition, at that point, if the IDD is not in the sense data hold state, sense data showing the Unit Attention condition are created by this command and are sent to the INIT, and the Unit Attention condition is cleared.
Page 227: Log Select (4C)
4.1 Control/Sense Commands 4.1.15 LOG SELECT (4C) Byte X'4C' Parameter List Length (MSB) Parameter List Length (LSB) This command provides a means for an application client to manage statistical information maintained by the IDD about IDD. The INIT can know the types of statistical information and the current maintaining of each statistical information by using the LOG SENSE command.
Page 228: Table 4.40 Pc (Page Control)
Command Specifications Table 4.40 PC (page control) 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 229: Table 4.42 Page Code
4.1 Control/Sense Commands Page code This field identifies which log page is being transferred. The log pages that can be transferred by this command are shown in Table 4.42. Table 4.42 Page code Page Code Description Changeable Parameter Buffer Overrun/Underrun Page Disable Write Error Counter Page Enable...
Page 230 Command Specifications a. Parameter code This field identifies the log parameter being transferred for that log page. b. Byte 2 1) DU (Disable Update) "1": The IDD does not update the log parameter value except in response to a LOG SELECT command that specifies a new value for the parameter. "0": The IDD updates the log parameter value to reflect all events that are noted by that parameter.
Page 231: Log Sense (4D)
4.1 Control/Sense Commands 7) LP (List Parameter) "1": The parameter is a data counter. "0": The parameter is a list parameter. If these bits are specified by LOG SELECT command, the IDD terminates normally. But the IDD's action is not changed. For LOG SENSE command, these bits always report value defined in each log page (see 4.2).
Page 232: Table 4.44 "Page Code" Assignment For The Log Pages
Command Specifications The "PC" bits are ignored by the drive. The drive assumes that current cumulative parameters are selected. The "Page Code" field identifies which page of data is being requested. If the page code is reserved or not implemented, the device server terminates the command with CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00]).
Page 233: Table 4.45 Support Log Page (X'00')
4.1 Control/Sense Commands • Log parameters This clause describes the log page structure and the log pages that are applicable to all devices. Pages specific to each device type are described in the command standard that applies to that device type. The LOG SENSE command returns a single log page specified in the page code field of the command descriptor block.
Page 234: Table 4.46 Buffer Overrun/Underrun Page (X'01')
Command Specifications (2) Buffer overrun/underrun page (X'01') Table 4.46 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)
Page 235: Table 4.47 Write Error Count Page (X'02')
4.1 Control/Sense Commands • Count Basis : Undefined : Per command, optional : Per failed reconnect, optional : Per unit of time, optional 4h-7h : Reserved The drive does not support this field. Zero is always reported. • 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.
Page 236 Command Specifications • Write errors recovered without delays (page 02, code 0000) Table 4.48 Write errors recovered without delays (page 02, 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 write errors that would not be reported to the initiator during write operations, because no delay is incurred.
Page 237: Table 4.50 Total Write Errors Posted (Page 02, Code 0002)
4.1 Control/Sense Commands • Total write errors posted (page 02, code 0002) Table 4.50 Total write errors posted (page 02, 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 write operations.
Page 238: Table 4.52 Total Write Bytes Processed (Page 02, Code 0005)
Command Specifications • Total write bytes processed (page 02, code 0005) Table 4.52 Total write bytes processed (page 02, 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 Write Bytes Processed indicates the total processed bytes during write operations.
Page 239: Table 4.54 Read Error Count Page (X'03')
4.1 Control/Sense Commands (4) Read error count page (X'03') Table 4.54 Read error count page (X'03') 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) •...
Page 240: Table 4.57 Total Read Errors Posted (Page 03, Code 0002)
Command Specifications • Read errors recovered with possible delays (page 03, code 0001) Table 4.56 Read errors recovered with possible delays (page 03, code 0001) Byte (MSB) X'0001 (Parameter code) (Errors Recovered With Possible Delays) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB)
Page 241: Table 4.59 Total Read Bytes Processed (Page 03, Code 0005)
4.1 Control/Sense Commands • Total recoverable read errors posted to INIT (page 03, code 0003) Table 4.58 Total recoverable read errors posted to INIT (page 03, code 0003) Byte (MSB) X'0003 (Parameter code) (Total Posted Recoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB)
Page 242: Table 4.61 Verify Error Count Page (X'05')
Command Specifications • Total unrecoverable read errors posted to INIT (page 03, code 0006) Table 4.60 Total unrecoverable read errors posted to INIT (page 03, code 0006) Byte (MSB) X'0006' (Parameter code) (Total Posted Unrecoverable Errors) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB)
Page 243: Table 4.62 Verify Errors Recovered Without Delays (Page 05, Code 0000)
4.1 Control/Sense Commands • Verify errors recovered without delays (page 05, code 0000) Table 4.62 Verify errors recovered without delays (page 05, 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 verify errors that would not be reported to the initiator during verify operations, because no delay is...
Page 244: Table 4.64 Total Verify Errors Posted (Page 05, Code 0002)
Command Specifications • Total verify errors posted (page 05, code 0002) Table 4.64 Total verify errors posted (page 05, 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 verify operations.
Page 245: Table 4.66 Total Verify Bytes Processed (Page 05, Code 0005)
4.1 Control/Sense Commands • Total verify bytes processed (page 05, code 0005) Table 4.66 Total verify bytes processed (page 05, code 0005) Byte (MSB) X'0005' (Parameter code) (Total Bytes Processed) (LSB) LBIN X'0A' (Parameter Length) (MSB) Total Verify Bytes Processed (10 bytes) (LSB) The Total Verify Bytes Processed indicates the total processed bytes during verify operation.
Page 246: Table 4.68 Non-Medium Error Count Page (X'06')
Command Specifications (6) Non-medium error count page (X'06') Table 4.68 Non-medium error count page (X'06') Byte X‘00’ (Reserved) X'00' (Page Length) X'08' (Page Length) (MSB) X'0000' (Parameter code) (Non-medium Error Count) (LSB) LBIN X'04' (Parameter Length) (MSB) Counter Value (LSB) 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.
Page 247: Table 4.70 Temperature (Page 0D, Code 0000)
4.1 Control/Sense Commands • Temperature (page 0D, code 0000) Table 4.70 Temperature (page 0D, code 0000) Byte (MSB) X'0000' (Parameter code) (Temperature) (LSB) LBIN X'02' (Parameter Length) X'00' (Reserved) Temperature (degrees Celsius) The Temperature sensed in the device at the time the LOG SENSE command is performed shall be returned in the parameter code 0000h.
Page 248: Table 4.72 Start-Stop Cycle Counter Page (X'0E')
Command Specifications (8) Start-stop cycle counter page (X'0E') Table 4.72 Start-stop cycle counter page (X'0E') 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) •...
Page 249: Table 4.74 Accounting Date (Page 0E, Code 0002)
4.1 Control/Sense Commands • Accounting date (page 0E, code 0002) Table 4.74 Accounting date (page 0E, code 0002) Byte (MSB) X'0002' (Parameter code) (Accounting Date) (LSB) LBIN X'06' (Parameter Length) (MSB) Accounting date Year (4 ASCII characters) (LSB) (MSB) Accounting date week (2 ASCII characters) (LSB) 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...
Page 250: Table 4.76 Start-Stop Cycle Counter (Page 0E, Code 0004)
Command Specifications The Specified cycle count over device lifetime is a parameter provided by the device sever. The specified cycle count over device lifetime parameter shall not be savable by the INIT using the LOG SELECT command. The parameter value is a 4-byte binary number.
Page 251: Table 4.77 Application Client Page (X'0F')
4.1 Control/Sense Commands (9) Application client page (X'0F') Table 4.77 Application client page (X'0F') 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) •...
Page 252: Table 4.79 Self-Test Result Page (X'10')
Command Specifications (10) Self-test result page (X'10') Table 4.79 Self-test result page (X'10') 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) •...
Page 253: Table 4.81 Self-Test Results Values
4.1 Control/Sense Commands When the self-test is initiated, the value specified in the SELF-TEST CODE field in the CDB is reported to the SELF-TEST CODE field by a SEND DIAGNOSTICS command. The values reported to the “Self-Test Result Value” field are defined in Table 4.81.
Page 254: Table 4.82 Background Medium Scan Page (X'15')
Command Specifications (11) Background medium scan page (X'15') Note: These parameters (Table 4.83, "Background medium scan status parameter" and Table 4.85, "Background medium scan parameter") are not supported. In LOG SENSE, these parameters are not transferred. Table 4.82 Background medium scan page (X'15') Byte Page Length (MSB) Page Length (LSB)
Page 255: Table 4.84 Bms Status
4.1 Control/Sense Commands The accumulated power-on time (unit: minute) at processing the LOG SENSE command is shown in the "Time Stamp" field. The values reported to the "BMS Status" field are defined below. Table 4.84 BMS status Value Description No medium scan Background medium scan in progress Pre-Scan in progress Halt the Medium Scan due to fatal error...
Page 256: Table 4.85 Background Medium Scan Parameter
Command Specifications Table 4.85 Background medium scan parameter Byte (MSB) X'0001' - X'0800' (Parameter code) (LSB) LBIN X'14' (Parameter Length) (MSB) Time Stamp (LSB) Reassign Status Sense Key Additional Sense Code Additional Sense Code Qualifier Vender Specific (0x00) (MSB) (LSB) The values reported to the "Reassign Status"...
Page 257: Table 4.87 Sas Protocol Log Page Format
4.1 Control/Sense Commands (12) SAS protocol log page (page code = 18) Table 4.87 SAS protocol log page format Byte Page Code (18h) Reserved (x'00) (MSB) Parameter Length (n-3) (LSB) First Protocol log parameter Nth Protocol log parameter This log page is used to report the information on an error that occurs on the SAS bus.
Page 258: Table 4.88 Log Parameter Format
Command Specifications • Details of the log parameter Table 4.88 Log parameter format Byte (MSB) Parameter Code (LSB) LBIN (0, 0) Parameter Length (x'34') Reserved ('0000'b) PROTOCOL IDENTIFIER ('0110b') Reserved (x'0000') NUMBER OF PHYS Reserved (x'00') PHY IDENTIFIER (0h or 1h) Reserved (x'0000') Reserved ATTACHED DEVICE TYPE...
Page 259 4.1 Control/Sense Commands Parameter Code Indicates the port number of a transferred log parameter. For port A, "0001" is reported, and for port B, "0002" is reported. b. PROTOCOL IDENTIFIER "6h" is set. NUMBER OF PHYS Indicates the number of SAS phy log descriptors that follow. d.
Page 260 Command Specifications ATTACHED SMP TARGET PORT Reports the SMP TARGET value received from the INIT with an IDENTIFY address frame. m. SAS ADDRESS Reports the port SAS address of the IDD. - port SAS address (Port-A): 5CCC CCCX XXXX XXX 2 - port SAS address (Port-B): 5CCC CCCX XXXX XXX 3 C: Company ID...
Page 261: Table 4.89 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 262: Persistent Reserve In (5E)
Command Specifications 4.1.17 PERSISTENT RESERVE IN (5E) Byte X'5E' Service Action Allocation Length (MSB) Allocation Length (LSB) The PERSISTENT RESERVE IN command is used to obtain information on the reserve conditions that are valid within a target and information concerning a Reservation Key.
Page 263: Table 4.91 Persistent Reserve In Service Actions
4.1 Control/Sense Commands (1) PERSISTENT RESERVE IN service actions In each Service Action, the drive needs to be in the ready state for accessing reserve conditions and registered information. When the drive is not in the ready state, the drive reports the CHECK CONDITION status. The sense key is set to NOT READY [= 2], and sense data similar to data reported with the TEST UNIT READY command is set.
Page 264: Table 4.92 Persistent Reserve In Parameter Data For Read Keys
Command Specifications (2) PERSISTENT RESERVE IN parameter data for READ KEYS The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the READ KEYS service action is shown in Table 4.86. Table 4.92 PERSISTENT RESERVE IN parameter data for READ KEYS Byte (MSB) Generation...
Page 265: Table 4.93 Persistent Reserve In Parameter Data For Read Reservations
4.1 Control/Sense Commands specified byte count are transferred to the INIT. Even if the rest of the list is discarded without being transferred, the "Additional Length" field indicates the total number of bytes in the valid Reservation Key list (this is not considered to be an error).
Page 266: Table 4.94 Format Of Reservation Descriptors
Command Specifications Table 4.94 Format of reservation descriptors Byte (MSB) Reservation Key (LSB) (MSB) Scope-specific Address (LSB) X'00' (Reserved) Scope Type 14-15 X'00' (Reserved) The Reservation Descriptor in the parameter data contains the information on each reserve condition held in the logical unit. The Descriptor contains the Reservation key of the INIT that holds the reserve conditions.
Page 267: Table 4.95 Persistent Reservations Scope
4.1 Control/Sense Commands • Persistent reservations scope The value in the "Scope" field shall indicate whether a persistent reservation applies to an entire logical unit or to an element. The values in the "Scope" field are defined in Table 4.95. Table 4.95 Persistent reservations scope Code Name...
Page 268: Table 4.96 Persistent Reservations Type Codes
Command Specifications Table 4.96 Persistent reservations type codes Code Name Description Reserved Write Reads Shared: Any INIT can execute a read-type command. Exclusive Writes Exclusive: Any write-type command that is issued by an INIT other than the INIT holding this reservation state results in a Reservation Conflict.
Page 269: Persistent Reserve Out (5F)
4.1 Control/Sense Commands 4.1.18 PERSISTENT RESERVE OUT (5F) Byte X'5F' Service Action Scope Type Parameter List Length (MSB) Parameter List Length (LSB) This command is used for reserving so that the particular initiator can use the logical unit exclusively or share with others. The command shall be used in conjunction with the PERSISTENT RESERVE IN command and shall have no relevance to the RESERVE and RELEASE commands.
Page 270 Command Specifications [= 5], and the sense data is set to INSUFFICIENT REGISTRATION [= 55-04]. (However, this sense data is not reported for a SCSI device.) For RESERVE, PREEMPT, and PREEMPT and ABORT Service Actions of this command, it is determined whether a reserve condition to be newly set by this command conflicts with the reserve conditions already held in the drive, regarding the setting of the Scope and Type.
Page 271: Table 4.97 Persistent Reserve Out Service Action Codes
4.1 Control/Sense Commands (1) PERSISTENT RESERVE OUT service actions When processing the PERSISTENT RESERVE OUT service actions, the device server shall update the generation value as specified in 4.1.17 (2). The PERSISTENT RESERVE OUT command service actions are defined in table 4.97.
Page 272: Table 4.98 Persistent Reserve Out Parameter List
Command Specifications (2) PERSISTENT RESERVE OUT parameter list The parameter list of the PERSISTENT RESERVE OUT command is shown in Table 4.98. Some fields of the parameter list of a particular Service Action and scope values may be invalid, but all the fields must always be transferred. Table 4.98 PERSISTENT RESERVE OUT parameter list Byte (MSB)
Page 273: Table 4.99 Persistent Reserve Out Service Action And Valid Parameters
4.1 Control/Sense Commands registered, the drive reports the RESERVATION CONFLICT status. For the Service Actions listed below, the value specified in this field is ignored. When the Scope value indicates Element Reservation, an element address (with the high byte filled with zeroes) is set in the Scope-specific Address field. If the Service Action is REGISTER, REGISTER and IGNORE EXISTING KEY, or CLEAR, or if the Scope indicates LU Reservation, set zero in the Scope-specific Address field.
Page 274: Report Luns (A0)
Command Specifications 4.1.19 REPORT LUNS (A0) Byte X'A0' Allocation Length (MSB) Allocation Length Allocation Length Allocation Length (LSB) This command requests that the peripheral device logical unit inventory be sent to the application client. This command normally operates under the reserve condition (RESERVE or PERSISTENT RESERVE).
Page 275: Table 4.100 Report Luns Parameter List
4.1 Control/Sense Commands Table 4.100 REPORT LUNS parameter list Byte (MSB) LUN List Length (N-7) (LSB) Header (MSB) Reserved (LSB) (MSB) First LUN (LSB) LUN List (MSB) Last LUN (LSB) The "LUN List Length" field shall contain the length in bytes of the LUN list that is available to be transferred.
Page 276: Report Device Identifier (A3)
Command Specifications 4.1.20 REPORT DEVICE IDENTIFIER (A3) Byte X'A3' Service Action (X’ 05’) Allocation Length (MSB) Allocation Length Allocation Length Allocation Length (LSB) 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 277: Table 4.101 Report Device Identifier Parameter List
4.1 Control/Sense Commands Table 4.101 REPORT DEVICE IDENTIFIER parameter list Byte (MSB) Identifier Length (n-4) (LSB) (MSB) Identifier (LSB) 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.
Page 278: Set Device Identifier (A4)
Command Specifications 4.1.21 SET DEVICE IDENTIFIER (A4) Byte X'A4' Service Action (X’ 06’) Allocation Length (MSB) Allocation Length Allocation Length Allocation Length (LSB) This command requests that the device identifier information in the logical unit be set to the value received in the SET DEVICE IDENTIFIER parameter list. On successful completion of this command a unit attention shall be generated for all initiators except the one that issued the service action.
Page 279: Data Access Commands
4.2 Data Access Commands Table 4.102 SET DEVICE IDENTIFIER parameter list Byte (MSB) Identifier (LSB) The "Identifier" field shall be a vendor specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands. 4.2 Data Access Commands 4.2.1 READ (08) Byte X‘08’...
Page 280: Read Extended (28)
Command Specifications When the specifications in the "Logical block address" field and "Transfer block count" field in the CDB exceed the maximum logical block address in the IDD, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Logical block address out of range [=21-00]) and the reading of data from the disk media is not executed.
Page 281: Write (0A)
4.2 Data Access Commands The functions of this command are the same as those of the Group 0 READ command (Section 4.2.1) with the exception that it is possible to specify 4-byte logical block addresses and 2-byte transfer block counts. However, when zero is specified for the "Transfer block count,"...
Page 282 Command Specifications When the specifications in the "Logical block address" field and "Transfer block count" field in the CDB exceed the maximum logical block address in the IDD, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Logical block address out of range [=21-00]) and writing of data to the disk media is not executed.
Page 283: Write Extended (2A)
4.2 Data Access Commands 4.2.4 WRITE EXTENDED (2A) Byte X‘2A’ × Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) This command transfers the number of blocks of data specified in the "Transfer block count"...
Page 284: Write And Verify (2E)
Command Specifications 4.2.5 WRITE AND VERIFY (2E) Byte X‘2E’ × BytChk Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) This command transfers the number of blocks of data specified in the "Transfer block count"...
Page 285: Verify (2F)
4.2 Data Access Commands 4.2.6 VERIFY (2F) Byte X‘2F’ × BytChk Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) This command reads the number of continuous logical data blocks specified in the "Block count"...
Page 286: Seek (0B)
Command Specifications 4.2.7 SEEK (0B) Byte X‘0B’ Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) 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 287: Seek Extended (2B)
4.2 Data Access Commands 4.2.8 SEEK EXTENDED (2B) Byte X‘2B’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) 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 4.2.7), except that it is possible to specify 4-byte logical block addresses.
Page 288: Synchronize Cache (35)
Command Specifications 4.2.9 SYNCHRONIZE CACHE (35) Byte X‘35’ Immed Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Block Count (MSB) Block Count (LSB) This command matches the logical block data in the data buffer with the same logical block data recorded on the disk media.
Page 289: Format Commands
4.3 Format Commands 4.3 Format Commands 4.3.1 FORMAT UNIT (04) Byte X‘04’ FmtData CmpLst Defect List Format Interleave factor (MSB) Interleave factor (LSB) This command initializes (formats) the entire area of the disk media that can be accessed from the INIT (User Space). At the same time, the IDD also implements defect management processing, allocating alternate blocks for defective portions of the disk media in accordance with the specifications in this command.
Page 290 Command Specifications (1) 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. 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 291: Table 4.103 Defect List Format
4.3 Format Commands (2) Specifying the initialization method The INIT can specify the method of defect processing executed by this command in the “FmtData (format data)” bit and “CmpLst (complete list)” bit of CDB byte 1 and the “Defect List Format” field. When “1”...
Page 292: Table 4.104 Format Unit Command Parameter List Configuration
Command Specifications (3) Format parameters Table 4.104 lists the data format of the Format parameter transferred from the INIT when “1” is specified in the “FmtData (format data)” bit of the CDB. Table 4.104 FORMAT UNIT command parameter list configuration Header Byte X‘00’...
Page 293 4.3 Format Commands Header The top of the format parameter transferred from the INIT is a 4-byte header. The INIT can specify the method used for defect processing that is executed by this command by control flags within the header. −...
Page 294 Command Specifications − STPF (stop format): Default value: “1” When the defect list (P List or G List) necessary for executing the defect processing specified in this command, cannot be read from the disk media, this bit indicates whether to continue (“0” is specified) or terminate (“1”...
Page 295: Table 4.105 Defect Descriptor: Byte Distance From Index Format
4.3 Format Commands b. Defect list (D List) The defect list (D List) contains defect position information about the disk media specified by the INIT and is configured from one or more “Defect descriptors.” “Defect descriptors must be described in the format specified in the “Defect List Format”...
Page 296: Table 4.106 Defect Descriptor: Physical Sector Address Format
Command Specifications − Physical sector address format defect descriptor Table 4.106 lists this description format of the defect descriptor. A defect descriptor with this format specifies the physical sector number of the data block which includes the defect on the disk media together with the cylinder No.
Page 297 4.3 Format Commands − Cautions in specifying the D list The P List, containing defect position information, is always recorded on the IDD when it is shipped from the factory. Also, information on defect positions for which alternate block processing has been implemented during operation is recorded as the G List.
Page 298: Table 4.107 Format Unit Command Defect Processing
Command Specifications (4) Defect processing during initialization Table 4.107 shows each combination of control flag specification values and the contents of processing executed by the IDD. Furthermore, see Chapter 3 “Data Format” of the “Product Manual” concerning alternate block allocation processing methods.
Page 299 4.3 Format Commands Table 4.107 FORMAT UNIT command defect processing (2/2) CDB Byte 1 Header Defect Processing Method FmtData CmpLst Defect list DPRY Defect format List Length 1 0 0 >0 1) Alternate block allocation is performed for defects registered in the previously 1 0 1 existing G List and the defects described in the D List transferred...
Page 300: Reassign Blocks (07)
Command Specifications 4.3.2 REASSIGN BLOCKS (07) Byte X‘07’ This command allocates alternate data blocks for defective data blocks specified in the “Defect Data” list transferred form the INIT. The INIT specifies the logical block address of one or more defective data blocks in the “Defect Data”...
Page 301: Table 4.108 Reassign Block Command: Defect Data List Configuration
4.3 Format Commands The format of the “Defect Data” list transferred from the INIT by this command is shown in Table 4.108. Table 4.108 REASSIGN BLOCK command: defect data list configuration Byte X‘00’ X‘00’ Header Defect List Length (m) (MSB) Defect List Length (m) (LSB) Defective Block Logical Block Address (MSB) Defective Block Logical Block Address...
Page 302 Command Specifications The IDD allocates alternate blocks to the specified data blocks in order from the top of the defect descriptor list. When all the usable spare sectors have been used up, and it is impossible to allocate alternate blocks, execution of this command is terminated at that point and a CHECK CONDITION status is reported.
Page 303: Figure 4.2 Correction Of The Defect Descriptor
4.3 Format Commands If this command is terminated with a CHECK CONDITION status, the additional sense code/additional sense code qualifier in the sense data is other than “No defect spare location available [=32- 00], and a valid logical block address (other than X ‘FFFFFFFF’) is displayed in the “Command inherent information”...
Page 304: Read Defect Data (37)
Command Specifications 4.3.3 READ DEFECT DATA (37) Byte X‘37’ PList GList Defect List Format Transfer Byte Length (MSB) Transfer Byte Length (LSB) This command transfers the list described in the defect position information of the disk media (defect data) to the INIT. There are two types of defect data, the P List (primary defect list) and the G list (grown defect list).
Page 305: Table 4.110 Defect Data Format
4.3 Format Commands Table 4.110 Defect data format Defect List Format Defect Data Format Block Address Format Byte Distance from the Index Format Physical Sector Address Format The “Transfer byte length” field in the CDB specifies the defect data length (number of bytes) that can be received by the INIT.
Page 306 Command Specifications Defect list format This field indicates the description format of the defect descriptor list that is actually transferred to the INIT. It is possible for the IDD to transfer defect data in 3 different formats which it can specify in the CDB, and the values in this field are the same as the values specified in the “Defect List Format”...
Page 307: Table 4.112 Defect Data Conditions
4.3 Format Commands 3. Even if defect data of the type specified in the CDB do not exist in the defect list (P List or G List) (if the defect list is empty), “1” is displayed in the “PList” bit and the “GList” bit in the header transferred to the INIT corresponding to the specification in the CDB.
Page 308 Command Specifications 6. The number of defects reported by this command differs depending on the defect data format. − When data are in the “Block Address Format,” defect position information is not reported for portions which cannot be clearly accessed from the INIT.
Page 309: Read Defect Data (B7)
4.3 Format Commands 4.3.4 READ DEFECT DATA (B7) Byte X ‘B7’ PList GList Defect List Format Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length Transfer Byte Length (LSB) This command transfers the list containing the defect position information of disk media (defect data) to the INIT.
Page 310: Maintenance, Diagnostic Commands
Command Specifications Table 4.113 READ DEFECT DATA command (B7): defect data configuration Byte X‘00’ PList GList Defect List Format Reserved Header Reserved Defect List Length (MSB) Defect List Length (LSB) Defect Defect Data Descriptor List 4.4 Maintenance, Diagnostic Commands 4.4.1 SEND DIAGNOSTIC (1D) Byte X‘1D’...
Page 311: Table 4.114 Self-Diagnosis Test
[=40-nn].” (nn is the code in the range X ‘80’ to X ‘FF,’ which shows the type of error. This code is a Fujitsu unique definition for the purpose of analysis when there is a failure, and its meaning is not released to the public. The user should present the value displayed in this sense data as repair information to the Fujitsu representative.)
Page 312: Table 4.115 Error Recovery Control Flags During The Self-Diagnosis Test
Command Specifications • The AWRE, ARRE and TB flags are not applied. • The PER and DTE flags are as shown in Table 4.115. Table 4.115 Error recovery control flags during the self-diagnosis test Diagnostic test operation The diagnostic test continues when error recovery is successful. The contents of recovered errors are not reported.
Page 313 4.4 Maintenance, Diagnostic Commands (2) Parameter specification When “0” is specified in the “SelfTest (self test) bit in the CDB, the IDD executes the operations specified in the parameter list transferred from the INIT by this command. In this case, the IDD reports a GOOD status and terminates this command at the point when preparation of the “response data”...
Page 314: Table 4.116 Send Diagnostic Command: Parameter List Configuration
Command Specifications Table 4.116 SEND DIAGNOSTIC command: parameter list configuration Byte Page Code Header Page Parameter Length (MSB) Page Parameter Length (LSB) Page Parameter Parameter • Page code This field specifies the code which identifies the type of parameter page being transferred from the INIT and the operation that should be executed.
Page 315: Table 4.118 Send Diagnostic Parameters: Page Code List
4.4 Maintenance, Diagnostic Commands Page code list This parameter page specifies transfer of the “Page code” list of the parameter page supported by the IDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command to the INIT. Table 4.118 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...
Page 316: Table 4.119 Send Diagnostic Parameters: Logical/Physical Address Conversion
Command Specifications Table 4.119 SEND DIAGNOSTIC parameters: logical/physical address conversion 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 The “Address Format Before Conversion” field shows the format of the address information specified in bytes 6 to 13.
Page 317: Table 4.121 Self-Test
4.4 Maintenance, Diagnostic Commands Details of the address conversion algorithm executed when this parameter page is specified and the data format, etc. of the conversion results reported to the INIT are explained in RECEIVE DIAGNOSTIC RESULTS command (Section 4.4.2). (3) Logical unit Self-Test When "0"...
Page 318: Receive Diagnostic Results (1C)
Command Specifications The Self-Test executes the following test segments in ascending order by number: 1. Buffer RAM test 2. Flash ROM test 3. Pre-SMART test 4. Low Level Format test 5. Random seek test 6. Sequential seek test 7. Data compare test 8.
Page 319 4.4 Maintenance, Diagnostic Commands Exercise caution in the following points when using this command. 1. 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 executed after the IDD is reserved.
Page 320: Table 4.123 Receive Diagnostic Results Response Data: Page Code List
Command Specifications • Page code This field is the same value as the page code specified in the parameter list transferred form the INIT by the SEND DIAGNOSTIC command executed last, and shows a code which identifies the type of response data reported in this command.
Page 321 4.4 Maintenance, Diagnostic Commands (2) Logical/physical address conversion This response data reports the execution results of address conversion specified in the “Logical/Physical Address Conversion” parameter in the SEND DIAGNOSTIC command in bytes after byte 4. The format and contents of this response data are shown in Table 4.124.
Page 322: Table 4.125 Address Format
Command Specifications The “Address Format Before Conversion” field in byte 4 and the “Address Format After Conversion” field in byte 5 are the same values as the codes which show the expression format for address information specified by the SEND DIAGNOSTIC command parameters.
Page 323: Write Buffer (3B)
4.4 Maintenance, Diagnostic Commands 4.4.3 WRITE BUFFER (3B) Byte X‘3B’ Mode X ’00’ (Buffer ID) Buffer Address (MSB) Buffer Address Buffer Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length Transfer Byte Length (LSB) This command is used in combination with the READ BUFFER command to diagnose the normality of the IDD’s data buffer memory or the SAS interface, or to download microcode to the IDD.
Page 324: Table 4.126 Write Buffer Transfer Mode
Command Specifications Table 4.126 WRITE BUFFER transfer mode “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 (1) Mode = 0, 0, 0, 0: Header + data, without address specification...
Page 325: Table 4.127 Write Buffer Command: Buffer Data (Mode = 000, 001)
4.4 Maintenance, Diagnostic Commands Table 4.127 WRITE BUFFER command: buffer data (mode = 000, 001) Byte Header Buffer Data (Byte 0) Buffer Data (Byte 1) Data Buffer Data (Byte n–4) (2) Mode = 0, 0, 0, 1: Header + data, with address specification The format of data transferred from the INIT in this mode must be the same as in the case of Mode = 0, 0, 0, 0, and the 4-byte header (with zero specified in all its contents) must be added to them.
Page 326 Command Specifications (3) Mode = 0, 0, 1, 0: Data only, with address specification In this mode, data transfer from the INIT includes buffer data only without the 4- byte header being added. The top address of the data buffer where the data transferred from the INIT are to be stored can be specified in the “Buffer address”...
Page 327 4.4 Maintenance, Diagnostic Commands When abnormal termination for reasons other than ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00] or ILLEGAL REQUEST [=5] / Invalid field in parameter list [=26-00] occurs, the IDD indicates that downloading of the new microcode failed, and it is therefore necessary for the INIT to quickly download the new microcode.
Page 328 Command Specifications and it shall set the sense key to ILLEGAL REQUEST [=5] with an additional sense code of INVALID FIELD IN CDB [=24-00]. 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.
Page 329: Read Buffer (3C)
4.4 Maintenance, Diagnostic Commands 4.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) This command is used in combination with the WRITE BUFFER command to diagnose the normalcy of the IDD’s data buffer memory and the SAS interface.
Page 330: Table 4.129 Read Buffer Command: Buffer Data (Mode = 0000, 0001)
Command Specifications (1) Mode = 0, 0, 0, 0: Header + data, without address specification When this mode is specified, the data stored in the IDD’s data buffer are transferred to the INIT after the 4-byte header. Zero must be specified in the “Buffer offset”...
Page 331 4.4 Maintenance, Diagnostic Commands (2) Mode = 0, 0, 0, 1: Header + data, with address specification The format of the data transferred to the INIT when this mode is specified is the same as the format of the data in the case of Mode = 0, 0, 0, 0, with the data stored in the IDD’s data buffer transferred to the INIT following the 4-byte header.
Page 332: Table 4.130 Read Buffer Command: Buffer Descriptor
Command Specifications (4) Mode = 0, 0, 1, 1: Buffer descriptor When this mode is specified, the IDD transfers only the 4-byte buffer descriptor to the INIT. the IDD’s data buffer attributes are indicated in the 4-byte buffer descriptor. Zero must be specified in the “Buffer offset” field in the CDB when this mode is specified.
Page 333: Read Long (3E)
4.4 Maintenance, Diagnostic Commands (6) Mode = 1, 0, 1, 1 : Echo buffer descriptor In this mode, a maximum of four bytes of READ BUFFER descriptor information is returned. The device server shall return the descriptor information for the echo buffer.
Page 334 Command Specifications This command reads the logical data block data and its ECC byte, specified in the “Logical block address” field in the CDB, from the disk media and transfers it to the INIT. Normally, this command is used in combination with the WRITE LONG command to perform checks of the ECC function.
Page 335: Write Long (3F)
4.4 Maintenance, Diagnostic Commands 4.4.6 WRITE LONG (3F) Byte X‘3F’ Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length (LSB) This command writes the data block data transferred from the INIT, together with the ECC to form bytes, in the logical data blocks on the disk media specified in the “Logical block address”...
Page 336: Write Same (41)
Command Specifications • Sense Key : 05 = ILLEGAL REQUEST • Additional sense code/ : 24-00 = Invalid field in CDB Additional sense code qualifier • “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,...
Page 337 4.4 Maintenance, Diagnostic Commands A "Pbdata" bit of one requests that the IDD replace the first eight bytes of the data to be written to the current physical sector with the physical address of the sector currently being written using the physical sector format. The IDD is not supported a "Pbdata"...
Page 338 This page is intentionally left blank.
Page 339: Sense Data Format
CHAPTER 5 Sense Data and 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 340: Table 5.1 Expanded Sense Data Format
Sense Data and Error Recovery Methods 2) In the REQUEST SENSE command, even if a Transfer byte length that is shorter than the length of the sense data supported by the device which is the object of the command, the command will terminate normally, but in that case, some of the sense data only will be received and the remaining information will be lost.
Page 341: Sense Data Basic Information
5.1 Sense Data 5.1.2 Sense data basic information Bytes 0 to 17 of the sense data are basic information which show the contents of the error that has occurred. The INIT can know the contents of the error and the key information that is necessary for recovery processing by analyzing this basic information.
Page 342 Sense Data and Error Recovery Methods (6) Additional sense data length This field indicates the length (number of bytes) after byte 8 of the sense data. The value shown in this field shows the length of sense data provided by the IDD without relation to the value specified in the “Transfer byte length”...
Page 343: Table 5.2 Sense Key Inherent Information
5.1 Sense Data Table 5.2 Sense key inherent information Byte SKSV X‘00’ Number of retries executed Byte SKSV [MSB] Progressing rate of formatting or Progressing rate of Self-Test operation [LSB] C141-C012...
Page 344: Table 5.3 Sense Key
Sense Data and Error Recovery Methods Table 5.3 Sense key Sense Name Explanation NO SENSE The specific sense key does not exist. RECOVERED ERROR 1) Indicates that the command which was executed last was terminated normally with a recovery operation by the IDD. If multiple errors which were successfully recovered from during processing of a single command occurred, the last error to have occurred is reported.
Page 345: Table 5.4 Additional Sense Code And Additional Sense Code Qualifier
5.1 Sense Data Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (1/6) Sense Name Explanation No additional sense No specific sense code exists. information No index/sector signal The target sector was not detected by the sector counter within the specified time.
Page 346 Sense Data and Error Recovery Methods Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (2/6) Sense Name Explanation Information Unit Too Short The received write data is shorter than the stipulated length. Information Unit Too Long The received write data is longer than the stipulated length. Read retries exhausted Unrecovered error was detected during data read (retry out).
Page 347 5.1 Sense Data Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (3/6) Sense Name Explanation Primary defect list not found The defect list (P List) header is incorrect. Grown defect list not found The defect list (G List) header is incorrect. SA information list not found The SA information (MODE SELECT parameter) header is incorrect.
Page 348 Microcode was changed by another INIT. Changed operating definition Operating definition was changed. Device identifier changed Device identifier was changed. Diagnostic failure on An error was detected in self-diagnosis. ("nn" is a Fujitsu component "nn" unique code) • 81: Buffer RAM compare error/bus error •...
Page 349 Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (5/6) Sense Name Explanation Internal target failure An error was detected in self-diagnosis. ("nn" is a Fujitsu unique 4, B code) • 90: Next sector IDD compare error • 91: WCS RAM parity error •...
Page 350 • FF: The drive is in test mode. Drive Failure A serious error was detected in the drive's control system. ('nn' is a Fujitsu unique code) • 00: Abnormal Rotation of Spindle Motor • 01: Any error at Spindle Motor Start •...
Page 351: Sense Data Additional Information
5.1 Sense Data 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. (1) PORT The Port bit indicates the connected port. Port-A: '0'; Port-B: '1'...
Page 352: Init Error Recovery Methods (Recommended)
Sense Data and Error Recovery Methods 5.2 INIT Error Recovery Methods (Recommended) When a single command or a series of linked commands are not terminated with a status reported, the INIT should execute error recovery processing corresponding to the state in which the command was terminated. Here, the procedure for analyzing the command execution termination state and recommended procedures for error recovery processing executed by the INIT in accordance with the results are explained.
Page 353 5.2 INIT Error Recovery Methods (Recommended) (1) TASK SET FULL status This status indicates that the IDD is currently executing processing of another command and that a new command cannot be received. The INIT that receives this status can reissue the original command. Under a multi-initiator environment, when an INIT receives this status, the time until the IDD can receive the next command depends on the operating state with other INITs, so ordinarily, it cannot be predicted.
Page 354: Sense Data Analysis And Error Recovery Methods
Sense Data and Error Recovery Methods • Since the command stack feature exists (see Section 1.4), even if the IDD accepts a command normally, if a command issued by another INIT is being executed, or if there are other commands in the stack, execution of the command is caused to wait until all the other commands have been processed.
Page 355: Table 5.5 Sense Data Error Classification
5.2 INIT Error Recovery Methods (Recommended) Table 5.5 Sense data error classification (1/3) Recovery Method Outline of Error (See Table 5.6.) No sense data showing the error contents are held. None Sync Mark not found for data field Need Positioning error Recovered data without ECC Recovered data with error correction applied.
Page 356 Sense Data and Error Recovery Methods Table 5.5 Sense data error classification (2/3) Recovery Method Outline of Error (See Table 5.6.) Medium form at corrupted Need FORMAT command failed The data format on the disk media is not correct. The data format on the disk media is not correct. Peripheral device write fault Need This is an error of the disk drive’s write system.
Page 357 5.2 INIT Error Recovery Methods (Recommended) Table 5.5 Sense data error classification (3/3) Recovery Method Outline of Error (See Table 5.6.) Power on, reset, or HARD RESET occurred None The IDD was initialized by a Power on or HARD RESET sequence.
Page 358: Table 5.6 Error Recovery Processing Procedures
Sense Data and Error Recovery Methods Table 5.6 Error recovery processing procedures (1/4) Recovery Recovery Processing Procedure Method It is not necessary to perform the error recovery processing. Continue processing. Error recovery processing is impossible. Terminate processing. This is a programming error and error recovery processing is impossible. Terminate processing and correct the error in the system (INIT) programming.
Page 359 5.2 INIT Error Recovery Methods (Recommended) Table 5.6 Error recovery processing procedures (2/4) Recovery Recovery Processing Procedure Method 1) Issue the MODE SENSE command and when a RECOVERED ERROR is reported, read the "Current" value in the changed MODE SELECT or MODE SELECT EXTENDED parameter.
Page 360 Sense Data and Error Recovery Methods Table 5.6 Error recovery processing procedures (3/4) Recovery Recovery Processing Procedure Method 1) Execute a HARD RESET sequence. 2) After waiting 2 seconds or longer, reissue the original command (Retry), and if the spindle motor's start mode is set on "Start by Command," issue the START instruction by the NOTIFY Primitive (ENABLE SPINUP) before retrying.
Page 361 5.2 INIT Error Recovery Methods (Recommended) Table 5.6 Error recovery processing procedures (4/4) Recovery Recovery Processing Procedure Method Initialize the entire disk media surface. It is desirable at this time to increase the number of spare sectors as much as possible. If this error occurs repeatedly, it is necessary to perform alternate block allocation processing through the system (shown in Chapter 5) or reconfirm the use conditions of the disk drive, such as the installation environment.
Page 362: Disk Drive Error Recovery Processing
Sense Data and Error Recovery Methods 5.2.3 Error logging In order to collect information that is effective in maintenance, it is desirable for the INIT to accumulate (log) error information related to the SAS interface which it has detected itself (error frame detection, command completion wait time-out, etc.) and error information reported by the IDD.
Page 363 5.3 Disk Drive Error Recovery Processing If the error cannot be recovered from even when retry processing is executed the specified number of times, the IDD terminates the command which is currently being executed with a CHECK CONDITION status. The sense key in the sense data at this time is "HARDWARE ERROR [=4]"...
Page 364: Auto Alternate Block Allocation Processing
Sense Data and Error Recovery Methods (4) Other internal IDD errors If an irrecoverable error other than those in items (1) to (3) above is detected internally in the IDD, the IDD terminates the command that is currently being executed with a CHECK CONDITION status.
Page 365 5.3 Disk Drive Error Recovery Processing 2. When errors in the data area are recovered from by ECC correction processing, before implementing alternate block allocation processing, rewriting of the recovered data and a verify check (rereading) are performed. If data are recovered by rewriting, alternate block allocation of that data block is not performed.
Page 366: Error Recovery Processing Control
Sense Data and Error Recovery Methods (3) Auto alternate block allocation processing during a write operation 2 (servo auto alternate) This function is enabled by specifying "1" in the AWRE flag in the MODE SELECT parameters. Furthermore, this function is applicable to the following commands only.
Page 367: Table 5.7 Disk Drive Errors And Number Of Retries
5.3 Disk Drive Error Recovery Processing − AWRE (automatic write reallocation enabled) − ARRE (automatic read reallocation enabled) − TB (transfer block) − EER (enable early recovery) − PER (post error) − DTE (disable transfer on error) − DCR (disable correction) −...
Page 368 This page is intentionally left blank.
Page 369: 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.
Page 370 Disk Media Management The P List and G List are recorded in the system space on the disk media. The INIT can read the contents of these lists by the READ DEFECT DATA command. (2) 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.
Page 371 6.1 Defect Management Alternate block allocation processing Alternate block allocation processing is implemented by the FORMAT UNIT command, REASSIGN BLOCKS command or "Auto Alternate Block Allocation Processing." In sector slip processing, the defective sectors re excluded and logical data blocks are located in physically consecutive sectors, but when alternate block processing is performed, the affected logical data blocks are located in spare sectors which are not physically consecutive with the previous and following logical data blocks which are physically...
Page 372: Initialization During Installation
Disk Media Management 6.2 Disk Media Initialization 6.2.1 Initialization during installation The disk drive is initialized for the inherent (default) data format for each respective model name (model class) when it is shipped from the factory, so ordinarily, it is not necessary to initialized (format) the disk media when it is installed in a system.
Page 373: Re-Initialization
6.2 Disk Media Initialization (2) Issuing the FORMAT UNIT command Issue the FORMAT UNIT command and initialize the entire disk media surface. In this FORMAT UNIT command, the entire disk media surface is initialized using the P List, then after initialization, the data blocks are verified. If any defective blocks are detected in the Verify operation, alternate blocks are allocated for those data blocks.
Page 374 Disk Media Management (2) FORMAT UNIT command Issue the FORMAT UNIT command in either of the following two formats and initialize the entire disk media surface. a) Specify "1" in the "FmtData" bit, "0" in the "CmpLst" bit and "000" in the "Defect List Format"...
Page 375 6.3 Data Block Verification Methods (Recommended) 6.3 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 376: Alternate Block Allocation Processing
Disk Media Management (3) 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 377 6.4 Alternate Block Allocation Processing 3) If the REASSIGN BLOCKS command is terminated normally, verify that logical data block according to the procedure in Section 6.3. If that data block is judged to be correct, allocate an alternate block and terminate processing.
Page 378 This page is intentionally left blank.
Page 379: Glossary
Glossary Additional Sense Code This is a 1-byte code displayed in the sense data and is information which specifies the type of error that was detected. Command Descriptor Block A series of data which describes commands related to input/output operations, sent from the initiator to the target.
Page 380 This page is intentionally left blank.
Page 381: Acronyms And Abbreviations
Acronyms and Abbreviations Disable Transfer on Error ACKnowledge Asynchoronous Event Notification Error Correction Code ALTernated (block) Enable Early Recovery ARRE Automatic Read Reallocation EVPD Enable Vital Product Data Enabled ASCII American Standard Code for Information Interchange Fibre Channel ASiGned block Frame Ground ATTeNtion FIFO...
Page 382 Acronyms and Abbreviations SCSI Small Computer System Interface SeCTor Original Equipment Manufacturer SELect SelfTest Self Test Signal Ground P list Primary defect list Save Page Parts/Number SPaRe block PBdata Physical Block data Servo PC board Printed Circuit board SSEC Soft sector Printed Circuit Assembly STPF Stop sector...
Page 383 Index 10-Byte CDB basic format ......2-2 application client page (X'0F') ....4-115 12-Byte CDB basic format ......2-3 arbitration fairness........1-47 6-Byte CDB basic format ......2-2 arbitration in progress ......1-27 8b10b coding..........1-11 ARRE ............4-29 auto alternate block allocation processing........5-26, 6-3 auto alternate block allocation abort processing ........2-17 processing during read...
Page 384 Index byte 2..........4-24, 4-94 connection.........1-8, 1-46 byte 6 to 16..........4-44 connection overview........1-46 byte distance from index format connection request ........1-46 defect descriptor....... 4-159 connection request, aborting....1-49 connection response.........1-47 connection, breaking........1-51 C list ..........4-154, 6-1 connection, closing ........1-50 cache segment count ....... 4-51 control byte..........2-5 cached command........
Page 385 Index defect data type ........4-168 DU ............4-94 defect descriptor......4-159, 4-160 DWS ............1-23 defect descriptor list.......4-170 defect list......4-154, 4-159, 6-1 defect list format ......4-155, 4-170 EAERP ............ 4-56 defect list length......4-158, 4-170 EBF............4-67 defect management ........6-1 echo buffer........4-192, 4-196 defect processing during echo buffer descriptor ......
Page 386 Index HSEC ............4-42 fatal hardware error ......... 2-20 force sequential write ......4-51 IC ............4-49 format command ........4-153 identification and hard reset format of reservation descriptor.... 4-130 sequence ..........1-45 format option valid........ 4-157 IDENTIFY address frame .......1-40 format parameter ....4-39, 4-156, 6-4 idle physical link........1-37 FORMAT parameter .........
Page 387 Index LOG SELECT (4C) .........4-91 mode = 0, 1, 1, 0........4-191 LOG SELECT command mode = 0, 1, 1, 1........4-192 parameter configuration......4-92 mode = 1, 0, 1, 0......4-192, 4-196 LOG SENSE (4D)........4-95 mode = 1, 0, 1, 1........4-197 LogErr ............4-66 mode page ..........
Page 388 Index number of retry during read ....4-31 parameter for specifying alternate processing area for defective number of retry during seek error ... 4-72 block ...........4-40 number of retry during VERIFY..... 4-46 parameter list configuration....4-178 number of retry during write....4-32 parameter list length ........2-5 parameter related to device type....4-42 parameter specification......4-177...
Page 389 Index port (narrow port and wide port)....1-4 read error count page (X'03')....4-103 post error ..........4-30 read error in uncorrectable data....5-25 power condition ........2-12 read error recovered with possible delay ........4-104 pre-fetch inhibit block count....4-50 read error recovered without delay ..4-103 pre-scan timeout value ......4-71 READ EXTENDED (28) ......
Page 390 Index RESERVE EXTENDED (56) ....4-87 self-test result parameter data....4-116 RESERVE (16) ........4-86 self-test result value.......4-117 reserve right and third party SEND DIAGNOSTIC (1D) ....4-174 reserve function........4-87 SEND DIAGNOSTIC command...4-178 reserved operation code ......2-16 SEND DIAGNOSTIC reset processing during write ....2-19 parameter .......4-179, 4-180 response and release condition at sense command..........4-1...
Page 391 Index SSP connection, closing......1-56 total read error posted......4-104 SSP flow control ........1-53 total recoverable read error posted to INIT..........4-105 SSP frame format........1-58 total recoverable verify error SSP frame transmission and posted to INIT ........4-108 reception ..........1-53 total recoverable write error posted SSP frame, sequence........1-76 to INIT..........
Page 392 Index verify error recovery parameter ..... 4-45, write cache enable ........4-48 5-29, 6-7 write error count page (X'02')....4-99 version ..........4-5, 4-9 write error recovered with possible version descriptor ........4-8 delay ..........4-100 version descriptor field......4-8 write error recovered without delay ..........4-100 VPD identifier list ........
Page 393 211-8588, Japan FAX: 34-91-581-8300 TEL: 81-44-754-2130 FAX: 81-44-754-8346 FUJITSU AUSTRALIA LIMITED 2 Julius Avenue (Cnr Delhi Road) North Ryde N.S.W. 2113, FUJITSU COMPUTER PRODUCTS OF AMERICA, INC. AUSTRALIA 2904 Orchard Parkway, San Jose, TEL: 61-2-9776-4555 California 95134-2009, U.S.A. FAX: 61-2-9776-4556 TEL:...
Page 394 This page is intentionally left blank.
Page 395 Too high Appropriate Too low Overall rating of this publication: Good Fair Poor FOR FUJITSU USE Overseas office: Person in charge: Note) Local representative should pass this form to the section in charge of distribution in FUJITSU. Reply FUJITSU LIMITED...
Page 396 This page is intentionally left blank.
Page 397 MAX3036RC, MAX3073RC, MAX3147RC SERIES MAY2036RC, MAY2073RC SERIES DISK DRIVES C141-C012-01EN SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS MAX3036RC, MAX3073RC, MAX3147RC SERIES C141-C012-01EN MAY2036RC, MAY2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS...

This manual is also suitable for:

Max3073rc series Max3147rc series May2036rc series May2073rc series

Fujitsu MAX3036RC SERIES Specifications

CHAPTER 5 Sense Data and Error Recovery Methods

CHAPTER 1 SAS Interface

CHAPTER 2 Command Processing

CHAPTER 3 Data Buffer Management

CHAPTER 4 Command Specifications

Quick Links

Related Manuals for Fujitsu MAX3036RC SERIES

Summary of Contents for Fujitsu MAX3036RC SERIES