Page 1 C141-C013-01EN MBA3073RC, MBA3147RC, MBA3300RC SERIES, MBB2073RC, MBB2147RC SERIES, MBC2036RC, MBC2073RC 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) 2007.02.28 — — *1 Section(s) with asterisk (*) refer to the previous edition when those were deleted. C141-C013...
Page 4 This page is intentionally left blank.
Page 5 Preface This manual explains concerning the 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 Preface Chapter 6 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 Hard Disk Drive (HDD), "drive" or "device" in this manual. Note: Model Name M BA 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 Maintenance 1. General Description Manual 2. Specifications 3. Data Format 4. Installation Requirements 5. Installation 6. Diagnostics and Maintenance 7. Error Analysis Interface Specifications 1. Serial Attached SCSI (SAS) Interface (This Manual) 2. Command Processing 3. Data Buffer Management 4.
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 10 Standards Institute...
Page 11: Table Of Contents
Contents CHAPTER 1 SAS Interface ................21 Topologies in SAS Interface ..............22 1.1.1 SAS Layering ..................23 1.1.2 Physical links and phys .................24 1.1.3 Ports (narrow ports and wide ports) ............24 1.1.4 SAS devices...................26 1.1.5 Pathways....................27 1.1.6 Connections ...................28 Names and identifiers................29 1.2.1 SAS addresses ..................29 1.2.2...
Page 12 Contents 1.4.3.3 BREAK....................48 1.4.3.4 BROADCAST ..................48 1.4.3.5 CLOSE....................49 1.4.3.6 EOAF (End of address frame) .............. 49 1.4.3.7 ERROR....................49 1.4.3.8 HARD_RESET..................49 1.4.3.9 NOTIFY....................50 1.4.3.10 OPEN_ACCEPT ................50 1.4.3.11 OPEN_REJECT ................. 50 1.4.3.12 SOAF (Start of address frame)............53 1.4.4 Primitives used only inside SSP and SMP connections .......
Page 13 Contents 1.5.6 SSP link layer ..................72 1.5.6.1 SSP frame transmission and reception ..........73 1.5.6.2 SSP flow control..................73 1.5.6.3 Interlocked frames .................73 1.5.6.4 Closing an SSP connection..............76 Transport layer ..................78 1.6.1 SSP frame format ..................78 1.6.2 Information units ...................81 1.6.2.1 COMMAND information unit...............81 1.6.2.2 TASK information unit................84 1.6.2.3 XFER_RDY information unit ...............86 1.6.2.4 DATA information unit.................89...
Page 14 Contents 2.8.3 Reserved operation code..............118 2.8.4 Error recovery processing..............118 2.8.5 Abort processing................. 119 2.8.6 Fatal hardware errors ................122 Data Block Addressing................122 2.9.1 Definition of data space ..............122 2.9.2 Logical block addressing ..............125 CHAPTER 3 Data Buffer Management ............
Page 15 Contents 4.1.16 LOG SENSE (4D) ................192 4.1.17 PERSISTENT RESERVE IN (5E)............194 4.1.18 PERSISTENT RESERVE OUT (5F) ..........201 4.1.19 REPORT LUNS (A0)................207 4.1.20 REPORT DEVICE IDENTIFIER (A3)..........209 4.1.21 SET DEVICE IDENTIFIER (A4)............211 Data Access Commands.................213 4.2.1 READ (08) ..................213 4.2.2 READ EXTENDED (28) ..............215 4.2.3 WRITE (0A)..................216 4.2.4...
Page 16 Contents 5.1.3 Format Parameters (Page Code = 3) ........... 289 5.1.4 Drive Parameters (Page Code = 4) ............. 294 5.1.5 Verify Error Recovery Parameters (Page Code = 7) ......296 5.1.6 Caching Parameters (Page Code = 8) ..........298 5.1.7 Control Mode Parameters (Page Code = 0A) ........
Page 17 Contents 6.2.1 Termination status analysis and error recovery methods ....372 6.2.2 Sense data analysis and error recovery methods .........374 6.2.3 Error logging ..................382 Disk Drive Error Recovery Processing ..........382 6.3.1 Error states and retry processing procedures........382 6.3.2 Auto alternate block allocation processing..........384 6.3.3 Error recovery processing control ............386 CHAPTER 7...
Page 18 Contents SMART (Self-Monitoring Analysis and Reporting Technology)..410 7.6.1 Overview .................... 410 7.6.2 Data analysis..................411 7.6.3 Failure prediction method..............412 7.6.4 Reporting function ................416 Glossary ......................417 Acronyms and Abbreviations ................419 Index ......................... 421 C141-C013...
Page 19 Contents Illustrations Figures Figure 1.1 SAS drive connection patterns ............. 22 Figure 1.2 SAS control layers................23 Figure 1.3 Physical links and phys ................ 24 Figure 1.4 Ports (narrow ports and wide ports) ............. 25 Figure 1.5 SAS devices ..................26 Figure 1.6 Example of potential pathways ............
Page 20 Contents Table 1.5 OOB signal transmitter requirements ........... 34 Table 1.6 OOB signal receiver burst time detection requirements....... 35 Table 1.7 OOB signal receiver idle time detection requirements......35 Table 1.8 OOB signal receiver negation time detection requirements ....35 Table 1.9 SAS speed negotiation sequence timing specifications......
Page 21 Contents Table 2.4 Operation code ................... 105 Table 2.5 Control byte..................107 Table 2.6 Status ....................108 Table 2.7 LED display ..................116 Table 2.8 Outline of disk drive error recovery processing......... 118 Table 2.9 Comparison between SAS and SCSI about definition ....... 119 Table 2.10 Reset processing during write ............
Page 22 Contents Table 4.36 Defect list format................226 Table 4.37 FORMAT UNIT command parameter list configuration ....227 Table 4.38 Defect descriptor: byte distance from index format ......230 Table 4.39 Defect descriptor: physical sector address format ......231 Table 4.40 FORMAT UNIT command defect processing ........233 Table 4.41 REASSIGN BLOCK command: defect data list configuration..
Page 23 Contents Table 5.10 MODE SELECT parameters: notch parameters........ 308 Table 5.11 Port control parameter: Page 0 Format (Short Page Format) ..... 311 Table 5.12 Port control parameter: Sub Page Format (Long Format)....312 Table 5.13 SAS phy mode descriptor format ............313 Table 5.14 Power condition parameter: Page 0 Format (Short Page Format)....................
Page 24 Contents Table 5.44 Total unrecoverable verify errors posted to INIT (page 05, code 0006) ..................341 Table 5.45 Non-medium error count page (X'06')..........342 Table 5.46 Temperature page (X'0D') ..............342 Table 5.47 Temperature (page 0D, code 0000) ............ 343 Table 5.48 Reference temperature (page 0D, code 0001) ........
Page 25: 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-C013...
Page 26: 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. Figure 1.1 SAS drive connection patterns SAS supports the three protocols listed below. Among these protocols, SAS drives support only SSP.
Page 27: 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 Link layer: Primitives, address frames, and connection control Port layer:...
Page 28: 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 29: 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 30: 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 31: 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 32: 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 33: 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 34: 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 35: 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 36: Link Reset Sequence
SAS Interface 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 37: 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). A loss of sync is detected.
Page 38: 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 39: 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 40: 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 detected idle/Burst pair 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 41: 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 42: 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 43: 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 44 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 45: 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 46: 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 47: 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 48: 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 FJ supported Primitive...
Page 49 1.4 Link layer Table 1.10 Primitives not specific to type of connection (2/2) From Sequence SAS 1.1 FJ supported Primitive USE (*4) rev. 10 prim supported prim Type EOAF NoConn single supported supported ERROR single supported supported HARD RESET NoConn redundant supported supported...
Page 50: 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 FJ supported Primitive USE (*4) rev. 10 prim supported prim Type Conn single supported supported CREDIT_BLOCKED Conn single supported supported DONE (NORMAL) Conn single supported supported DONE (RESERVED 0)
Page 51: 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 52: 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 53: 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 54: 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 55: 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 56: 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 57: Soaf (Start Of Address Frame)
1.4 Link layer 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. 5) A dual port drive may process requests from up to four INITs at a time for each port.
Page 58: 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 59: 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 60: 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 61: 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 62: 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 63: 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 64: 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 65 1.5 Address frames 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. Expander devices shall set the SSP INITIATOR PORT bit to zero. An SSP TARGET PORT bit set to one specifies that an SSP TARG port is present.
Page 66: 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 67: 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 68: 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 69: 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 70: 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 71: 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 72: 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 73: 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 74: 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 75: 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 76: 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 77: 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 78: 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 79: 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 80: Closing An Ssp Connection
SAS Interface Figure 1.18 Non-interlocked frames with the same tag Figure 1.19 Non-interlocked frames with different tags 1.5.6.4 Closing an SSP connection DONE shall be exchanged prior to closing an SSP connection. There are several versions of the DONE primitive indicating additional information about why the SSP connection is being closed: a) DONE (NORMAL) specifies normal completion;...
Page 81: 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 82: 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 83: 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 84 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 85: 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 86: 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 87 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 88: 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 89: 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 90: Xfer_Rdy Information Unit
SAS Interface 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. Then the drive reports the RESPONSE CODE of the OVERLAPPED TAG ATTEMPTED (0x0A).
Page 91: Table 1.39 An Example Of Requested Offset
1.6 Transport layer 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 92: Figure 1.21 Example Of Xfer_Rdy Frames
SAS Interface 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 93: 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 94 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 95 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 96: 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 97 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 98: 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 99 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. NUMBER OF FILL BYTES field Set to zero.
Page 100: Sequences Of Ssp Frames
SAS Interface 1.6.3 Sequences of SSP frames Figure 1.22, Figure 1.23, and Figure 1.24 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 101: 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-C013...
Page 102: Exceptional Event Processing Of A Drive
SAS Interface 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 103: Figure 1.25 Example Of The Processing Sequence For An Exceptional Event
1.6 Transport layer Figure 1.25 shows an example of the processing sequence a drive performs for an exceptional event. Figure 1.25 Example of the processing sequence for an exceptional event C141-C013...
Page 104: Table 1.45 Exceptional Event Processing Of A Drive
SAS Interface 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 105 1.6 Transport layer 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 frame Reports for ACK/NAK TIMEOUT (0B/4B/03).
Page 106 SAS Interface C141-C013...
Page 107: 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 HDD command processing functions are described. The HDD operates as the target (TARG).
Page 108: 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 109: 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 110 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 Table 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 111: 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 HDD 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 112: Status Byte
Command Processing 2.2 Status Byte The format of the status byte and the types of status which the HDD 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 113 2.2 Status Byte c) Any cases other than the above indicate that it was impossible to execute the command or the command ended abnormally. (3) CONDITION MET Status Not supported. (4) BUSY status This status indicates that the HDD is busy, and it cannot accept a new command. Usually, an INIT that has received this status re-issues the same command after an adequate period of time.
Page 114: Command Queuing Function
Command Processing 2.3 Command Queuing Function The HDD is equipped with the command queuing function. Through command queuing, the HDD can receive multiple commands in advance and can execute them. Through the tagged queuing function, the HDD can receive multiple commands from the same INIT or from different INITs until the command queue is full.
Page 115: 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 116: 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. An INIT reports an error when the QErr bits of MODE SELECT parameter page A are set to "01'.
Page 117: 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 HDD 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 118: Power Condition
Command Processing 2.6 Power Condition The HDD 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 HDD is waiting for motor start with NOTIFY (ENABLE SPINUP).
Page 119: Led Display
2.7 LED Display The HDD 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 HDD reads the "System Information"...
Page 120: Led Display
Command Processing 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 executed (50 ms/ON, is not being executed.
Page 121: Illegal Lun Specification
2.8 Command Processing Exceptions The HDD 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 122: 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 HDD may not necessarily respond with the CHECK CONDITION status (ILLEGAL REQUEST [= 5] Invalid command operation code [= 20-00]).
Page 123: 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 HDD starts a readjustment operation is caused to wait until the readjustment operation is completed.
Page 124 Command Processing (1) HARD RESET HARD RESET is used to abort all commands and to initialize the HDD 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 125: 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 point SEND DIAGNOSTIC (Write/Read Test) when that processing is completed.
Page 126: 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 HDD reports the CHECK CONDITION status for all Input/Output operation requests except the REQUEST SENSE command.
Page 127 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 128: Figure 2.1 Data Space Configuration
Command Processing Physical cylinder [System space] Cylinder 0 Head 0 Cylinder Cylinder 1 Cell 0 Head 1 (Cell) Cylinder 0 Zone 0 Head (a-1) [User space] Cell n-1 (Cell) Zone 1 Zone (x-1) Alternate cell Alternate cylinder Last cylinder Figure 2.1 Data space configuration C141-C013...
Page 129: Logical Block Addressing
2.9 Data Block Addressing 2.9.2 Logical block addressing The HDD 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 HDD makes correspondence between each physical sector and each logical data clock address during formatting.
Page 130 Command Processing (2) Alternate area The alternate area in user space (spare sectors within each cell and alternate cells) are excluded from the abovementioned logical data block addresses. Access to allocated sectors as alternate blocks within the alternate area is performed automatically by the HDD's defect management (sector slip processing and alternate block processing), so it is not particularly necessary for the user to access the alternate area.
Page 131: 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 HDD 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 HDD is equipped with a data buffer, which makes it possible to efficiently execute data transfer operations between INIT (initiator) and a disk drive.
Page 132: 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 W rite W rite 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 133 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 HDD may soon not be able to read data from the disk media (data overrun).
Page 134: 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 HDD 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 135 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 136 Data Buffer Management MODE SENSE EXTENDED READ CAPACITY READ DEFECT DATA (12) REASSIGN BLOCKS RELEASE EXTENDED RESERVE EXTENDED WRITE BUFFER WRITE SAME PERSISTENT RESERVE IN PERSISTENT RESERVE OUT REPORT DEVICE IDENTIFIER SET DEVICE IDENTIFIER 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 137: Caching Parameters
3.2 Look-Ahead Cache Feature 3.2.2 Caching parameters The HDD supports the MODE SELECT parameters (caching parameters: page code = 8) for controlling the cache feature. See Chapter 5 concerning details of the MODE SELECT parameters. 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.
Page 138 This page is intentionally left blank.
Page 139: 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 HDD is equipped with and how to use them. 4.1 Control/Sense Commands 4.1.1 TEST UNIT READY (00) Byte X'00' This command checks the status of the disk drive.
Page 140: 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 HDD'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 141 4.1 Control/Sense Commands (1) EVPD (Enable Vital Product Data) a) If the specification in this bits is zero, the HDD 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 142: Table 4.1 Standard Inquiry Data
BQue EncServ MultiP MCHNGR Obsolete Addr16 Obsolute Obsolute Wbus16 Sync Linked Obsolute CmdQue FUJITSU (Vendor ID: ASCII) (Product ID: ASCII) Microcode Version No. (ASCII) (Product Revision: ASCII) Device Serial No. (ASCII) 48-55 X'00' (Vendor Specific) Reserved CLOCKING X'00' (Reserved) 58-73...
Page 143: 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 144 Command Specifications Response data format field This field shows the code which shows the standard INQUIRY data format. 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 HDD without relation to the specification in the transfer byte length field in the CDB, and is always X'5B' (total data length = 96 bytes).
Page 145: 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 146: Table 4.4 Version Descriptor
Command Specifications 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. The HDD shall be indicated as shown below. Table 4.4 Version descriptor BYTE Code...
Page 147: 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 148: 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 149: Table 4.7 Vpd Information
4.1 Control/Sense Commands 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 150: 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 151: Table 4.10 Vpd Information: Device Unique Information
4.1 Control/Sense Commands Device unique information This VPD information reports the HDD 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' X'48' (Page Length) Logical unit identifier...
Page 152 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 (NAA format) PROTOCOL IDENTIFIER (6h) CODE SET (1h) Reserved Association Identifier type (3h) ('1b') ('0'b) ('10b')
Page 153 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 154 Command Specifications Identifier length Indicates the Identifier length. Even when a value that is insufficient for transferring all the Identifiers is specified for the Transfer Byte Length of the CDB, this value indicates the actual byte length IDENTIFIER for the logical unit Indicates the device unique WWN.
Page 155: Read Capacity (25)
4.1 Control/Sense Commands 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 156: Table 4.11 Read Capacity Data
Command Specifications Table 4.11 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) C141-C013...
Page 157: Mode Select (15)
4.1 Control/Sense Commands 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 SAS interface transferring processing and error recovery procedures, etc. The INIT can know the types of parameters, the current settings of each parameter and the types of parameters which can be changed, and the ranges for such changes, etc.
Page 158 Command Specifications The "Parameter length" field of the CDB specifies the total byte length of the MODE SELECT parameters transferred from the INIT by this command. If zero is specified in the "Parameter length" field, this command is terminated normally without data transfer being executed with the INIT.
Page 159: Figure 4.1 Mode Select Parameter Structure
4.1 Control/Sense Commands Current values Save values Power-on RESET condition [Command to all INITs] [Command to all INITs] MODE SELECT Pages: Pages: MODE SELECT (SP=1) 1, 2, 7, 8, A, 19, 1C, 1, 2, 7, 8, A, C, 19, 1C, 1A, 21 1A, 21 Power-on...
Page 160 Command Specifications If the HDD performs rounding processing ("rounding up" or "rounding down") of parameter values specified by the INIT, in some cases a "CHECK CONDITION" status (RECOVERED ERROR [=1] / Rounded parameter [37-00]) is reported, and in some cases it is not reported. Whether or not the CHECK CONDITION status is reported depends on whether "rounding up"...
Page 161: Table 4.12 Mode Select Command (Group 0) Parameter Configuration
4.1 Control/Sense Commands Table 4.12 MODE SELECT command (Group 0) parameter configuration (1/2) Header Byte X'00' X'00' (Media Type) × × X'00' or X'08' (Product Descriptor Length) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X'00' Data Block Length (MSB)
Page 162 Command Specifications Table 4.12 MODE SELECT command (Group 0) parameter configuration (2/2) Sub Page Descriptor Byte Page Code Page Sub Page Code Header Page Length Parameter Field Header − Media type X '00' (default type) must be specified in this field. −...
Page 163 4.1 Control/Sense Commands Block descriptor The logical attributes of the data format on the disk media are described in the 8-byte long "Block descriptor." − Data block count This field specifies the total number of logical data blocks (the block length is specified in "Data block length") allocated in the user space on the disk media.
Page 164 Command Specifications Page descriptor The "Page Descriptor" consists of a two-byte page header (or four-byte page header when using subpage format) followed by a parameter field. It is classified based on the parameter function attribute into units called "Pages." The individual "Page descriptors" in the MODE SELECT and MODE SELECT EXTENDED commands may be specified independently by the INIT and multiple "Page descriptors"...
Page 165: Table 4.13 Mode Select Parameters
4.1 Control/Sense Commands Table 4.13 MODE SELECT parameters Parameter Byte Length Header Block Descriptor 8 or 0 Page Descriptor Page 1: Read/Write Error Recovery Parameter Page 2 Disconnect/Reconnect Parameter Page 3: Format Parameter Page 4: Drive Parameter Page 7: Verify Error Recovery Parameter Page 8: Caching Parameter Page A:...
Page 166 Command Specifications 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 HDD in the future.
Page 167: 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 168 Command Specifications Table 4.14 MODE SELECT EXTENDED command (group 2) parameter configuration (1/2) Header Byte X'00' X'00' X'00' (Medium Type) × × X'00' X'00' X '00' (Block Descriptor Length: MSB) X'00' or X'08' (Block Descriptor Length: LSB) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count...
Page 169 4.1 Control/Sense Commands Table 4.14 MODE SELECT EXTENDED command (group 2) parameter configuration (2/2) Sub Page Descriptor Byte Page Code Page Sub Page Code Header Page Length Parameter Field C141-C013...
Page 170: Mode Sense (1A)
Command Specifications 4.1.6 MODE SENSE (1A) Byte X'1A' Page Code Sub 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 of SAS interface transferring processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.
Page 171: Table 4.15 Mode
4.1 Control/Sense Commands Table 4.15 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 172: Table 4.16 Mode Sense Data Type Specifications
Command Specifications Table 4.16 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 173 4.1 Control/Sense Commands 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 HDD transfers the number of bytes of all the MODE SENSE data specified in the "Page code"...
Page 174: Table 4.17 Mode Sense Command (Group 0) Parameter Configuration
Command Specifications Table 4.17 MODE SENSE command (group 0) parameter configuration (1/2) Header Byte Sense Data Length X'00' (Media Type) DPOFUA X'00' or X'08' (Block Descriptor Length) Block Descriptor Byte Data Block Count (MSB) Data Block Count Data Block Count Data Block Count (LSB) X'00' Data Block Length (MSB)
Page 175 4.1 Control/Sense Commands Table 4.17 MODE SENSE command (group 0) parameter configuration (2/2) Sub Page Descriptor Byte Page Code Page Sub Page Code Header Page Length Parameter Field (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.
Page 176 Command Specifications Block descriptor length This field indicates the "Block descriptor" length (byte length) which follows after the header. The "Page descriptor" length is not included in this value. The HDD always reports X '08' in this field if "0" is specified in the DBD bit of this command's CDB, and thus indicates that one "Block descriptor"...
Page 177 4.1 Control/Sense Commands Page length This field indicates the length of the parameter field (number of bytes) from byte 2, excluding the page header of that "Page descriptor." The HDD always shows a value in this field which is the same as the length defined in that "Page descriptor"...
Page 178: Mode Sense Extended (5A)
Command Specifications 4.1.7 MODE SENSE EXTENDED (5A) Byte X'5A' Page Code Sub 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 of SAS interface transferring processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.
Page 179 4.1 Control/Sense Commands Table 4.18 MODE SENSE EXTENDED command (group 2) parameter configuration (1/2) 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 180 Command Specifications Table 4.18 MODE SENSE EXTENDED command (group 2) parameter configuration (2/2) Sub Page Descriptor Byte Page Code Page Sub Page Code Header Page Length Parameter Field C141-C013...
Page 181: Rezero Unit (01)
4.1 Control/Sense Commands 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 182: Start/Stop Unit (1B)
Command Specifications 4.1.9 START/STOP UNIT (1B) Byte X'1B' Immed LoEj Start This command controls the power condition of the disk drive. For the power condition, see Chapter 2, "Power Condition." The control of the power condition is performed with the Start bit in bit 0 of the CDB byte 4.
Page 183 4.1 Control/Sense Commands − When the Immed bit is "0," the power condition state becomes Active_Wait, and the spindle motor is started after the NOTIFY (ENABLE SPINUP) primitive has been received. Then, when the disk drive enters the ready state, the status byte is reported and command execution is completed.
Page 184: 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 (HDD) under a multi-initiator environment.
Page 185 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 HDD is reserved for the INIT that has issued this command.
Page 186: Reserve Extended (56)
Command Specifications 4.1.11 RESERVE EXTENDED (56) Byte X'56' 3rd Pty × × × × × × × × Third Party Device ID × × × × × × × × × × × × × × × × Together with the RELEASE command, this command controls exclusive access to the HDD under a multi-initiator environment.
Page 187: Release (17)
4.1 Control/Sense Commands 4.1.12 RELEASE (17) Byte X'17' 3rd Pty 3rd Pty Dev ID × × × × × × × × This command releases the reserve state of an HDD in relation to the INIT that issued this command. When a reserve state in relation to the INIT that issues this command, or an HDD does not exist, this command is terminated normally with a GOOD status.
Page 188: Release Extended (57)
Command Specifications 4.1.13 RELEASE EXTENDED (57) Byte X'57' 3rd Pty × × × × × × × × Third Party Devices ID × × × × × × × × × × × × × × × × Same as RELEASE command. C141-C013...
Page 189: Request Sense (03)
4.1 Control/Sense Commands 4.1.14 REQUEST SENSE (03) Byte X'03' Transfer Byte Length This command transfers sense data to the INIT. This command is executed in any state other than a CDB specification error. The sense data of the HDD has a length of 48 bytes. The HDD generates sense data in any of the following cases and holds the sense data for the INIT that has issued the relevant command: If this command is executed when the HDD is holding the Unit Attention...
Page 190 Command Specifications 1) When sending of sense data is impossible due to an HDD hardware error. 2) When an irrecoverable error is detected on the SAS interface. 3) If an overlapped command occurs. In cases other than the above, this command sends sense data to the INIT and terminates with the "GOOD"...
Page 191: 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 HDD about HDD. The INIT can know the types of statistical information and the current maintaining of each statistical information by using the LOG SENSE command.
Page 192: Table 4.19 Pc (Page Control)
Command Specifications Table 4.19 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 193: Table 4.21 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.21. Table 4.21 Page code Page Code Description Changeable Parameter Buffer Overrun/Underrun Page Disable Write Error Counter Page Enable...
Page 194: Table 4.22 Log Parameter
Command Specifications Table 4.22 Log parameter Byte Parameter Code (MSB) Parameter Code (LSB) LBIN Parameter Length Parameter Value a. Parameter code This field identifies the log parameter being transferred for that log page. b. Byte 2 1) DU (Disable Update) "1": The HDD does not update the log parameter value except in response to a LOG SELECT command that specifies a new value for the parameter.
Page 195 4.1 Control/Sense Commands 5) TMC (Threshold Met Criteria) This field is ignored when "ETC" bit is 0. For LOG SELECT command (See 4.1.15), the HDD accepts this field value of other than "00b", but ignores its functionality. 6) LBIN This bit is only valid if the "LP" bit is one. If the "LP" bit is one and this bit is zero then the list parameter is a string of ASCII graphic codes.
Page 196: Log Sense (4D)
Command Specifications 4.1.16 LOG SENSE (4D) Byte X'4D' Page Code Parameter Pointer (MSB) Parameter Pointer (LSB) Parameter List Length (MSB) Parameter List Length (LSB) This command provides a means for the application client to retrieve statistical or other operational information maintained by the device about the device or its logical units.
Page 197: Table 4.23 "Page Code" Assignment For The Log
4.1 Control/Sense Commands Table 4.23 "Page Code" assignment for the log pages Page Code Description Parameter Pointer Supported Log Pages Ignored Buffer Overrun / Underrun Page Supported Write Error Counter Page Supported Read Error Counter Page Supported Verify Error Counter Page Supported Non-medium Error Page Should be zero...
Page 198: Persistent Reserve In (5E)
Command Specifications CHAPTER 4 Command Specifications 4.1 Control/Sense Commands 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 199: Table 4.24 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 200: Table 4.25 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.25. Table 4.25 PERSISTENT RESERVE IN parameter data for READ KEYS Byte (MSB) Generation...
Page 201: Table 4.26 Persistent Reserve In Parameter Data For Read Reservations
4.1 Control/Sense Commands The "Additional Length" field contains a count of the number of bytes in the Reservation key list. If the Allocation Length value specified by the PERSISTENT RESERVE IN command is too small to transfer the entire valid parameter list, the bytes starting at byte 0 of the list and numbering as many as the specified byte count are transferred to the INIT.
Page 202: Table 4.27 Format Of Reservation Descriptors
Command Specifications The format of the Reservation descriptors is defined in Table 4.27. Table 4.27 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.
Page 203: Table 4.28 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.28. Table 4.28 Persistent reservations scope Code Name Description...
Page 204: Table 4.29 Persistent Reservations Type Codes
Command Specifications Table 4.29 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 205: 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 206 Command Specifications If illegal drive resources exist when this command is issued, the drive reports the CHECK CONDITION status. The sense key is set to ILLEGAL REQUEST [= 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...
Page 207: Table 4.30 Persistent Reserve Out Service Action Codes
4.1 Control/Sense Commands A logical unit uses the SA space to maintain PERSISTENT RESERVATION and registered keys (across a power shutdown). If the drive is not in the Ready state when the Activate Persist Through Power Loss mechanism (this mechanism maintains reserve conditions during a power shutdown) is enabled by the PERSISTENT RESERVE OUT command, the drive reports the CHECK CONDITION status.
Page 208: Table 4.31 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.31. 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.31 PERSISTENT RESERVE OUT parameter list Byte (MSB)
Page 209 4.1 Control/Sense Commands The specification of the "Service Action Reservation Key" field is necessary for the REGISTER, PREEMPT, and PREEMPT and ABORT Service Actions. For the REGISTER Service Action, a Reservation Key to be newly registered is set in this field.
Page 210: Table 4.32 Persistent Reserve Out Service Action And Valid Parameters
Command Specifications Table 4.32 PERSISTENT RESERVE OUT service action and valid parameters Parameters Service Allowed type Reservation Reservation Service Action Scope- Action Scope Specific Address Register ignored ignored valid valid ignored Register And ignored ignored ignored valid ignored Ignore Existing Key Reserve Logical Unit valid...
Page 211: Report Luns (A0)
4.1 Control/Sense Commands 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 212: Table 4.33 Report Luns Parameter Data
Command Specifications Table 4.33 REPORT LUNS parameter data 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 213: Report Device Identifier (A3)
4.1 Control/Sense Commands 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 214: Table 4.34 Report Device Identifier Parameter Data
Command Specifications Table 4.34 REPORT DEVICE IDENTIFIER parameter data 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 215: Set Device Identifier (A4)
4.1 Control/Sense Commands 4.1.21 SET DEVICE IDENTIFIER (A4) Byte X'A4' Service Action (X' 06') Parameter List Length (MSB) Parameter List Length Parameter List Length Parameter List 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.
Page 216: Table 4.35 Set Device Identifier Parameter Data
Command Specifications Table 4.35 SET DEVICE IDENTIFIER parameter data Byte (MSB) Identifier (LSB) The "Identifier" field shall be a vendor specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands. C141-C013...
Page 217: Data Access Commands
4.2 Data Access Commands 4.2 Data Access Commands 4.2.1 READ (08) Byte X'08' Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Block Count This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count"...
Page 218 Command Specifications If the Look-Ahead cache feature is permitted, a caching operation is performed using the HDD's data buffer by this command. See Chapter 3, "Data Buffer Management," concerning details of data buffer operation and the Look-Ahead cache feature. C141-C013...
Page 219: Read Extended (28)
4.2 Data Access Commands 4.2.2 READ EXTENDED (28) Byte X'28' Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Block Count (MSB) Transfer Block Count (LSB) This command reads the number of blocks of data in continuous logical data blocks specified in the "Transfer block count"...
Page 220: Write (0A)
Command Specifications 4.2.3 WRITE (0A) Byte X'0A' Logical Block Address (MSB) Logical Block Address Logical Block Address (LSB) Transfer Block Count This command transfers the number of blocks of data specified in the "Transfer block count" field from the INIT and writes them in continuous logical data blocks with the logical data block on the disk media specified in the "Logical block address"...
Page 221 4.2 Data Access Commands Even when there is an error in the specification in the CDB, or when a write operation to the disk media cannot be executed normally due to various other causes, the transfer of data (data is pre-fetched to the data buffer) from the INIT to the HDD may be executed.
Page 222: Write Extended (2A)
Command Specifications 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 223: Write And Verify (2E)
4.2 Data Access Commands 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 224: Verify (2F)
Command Specifications 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 225: Seek (0B)
4.2 Data Access Commands 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 HDD performs disconnect processing after receiving the CDB.
Page 226: Seek Extended (2B)
Command Specifications 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 227: Synchronize Cache (35)
4.2 Data Access Commands 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 228: Format Commands
Command Specifications 4.3 Format Commands 4.3.1 FORMAT UNIT (04) Byte X'04' FmtData CmpLst Defect List Format 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 HDD also implements defect management processing, allocating alternate blocks for defective portions of the disk media in accordance with the specifications in this command.
Page 229 4.3 Format Commands (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 230: Table 4.36 Defect List Format
Command Specifications (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 231: Table 4.37 Format Unit Command Parameter List Configuration
4.3 Format Commands (3) Format parameters Table 4.37 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.37 FORMAT UNIT command parameter list configuration Header Byte X'00'...
Page 232 Command Specifications Header The top of the format parameter transferred from the INIT is a 4-byte header. The INIT can specify the method used for defect processing that is executed by this command by control flags within the header. FOV (format option valid) 0: Indicates that the INIT does not specially specify concerning the functions specified by the control flags in bits 6 to 4 of byte 1 (see following "DPRY"...
Page 233 4.3 Format Commands STPF (stop format) 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 234: Table 4.38 Defect Descriptor: Byte Distance From Index Format
Command Specifications 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 235: Table 4.39 Defect Descriptor: Physical Sector Address Format
4.3 Format Commands Physical sector address format defect descriptor Table 4.39 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 236 Command Specifications Cautions in specifying the D list The P List, containing defect position information, is always recorded on the HDD 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 237: Table 4.40 Format Unit Command Defect Processing
4.3 Format Commands (4) Defect processing during initialization Table 4.40 shows each combination of control flag specification values and the contents of processing executed by the HDD. Furthermore, see Chapter 3 "Data Format" of the "Product Manual" concerning alternate block allocation processing methods.
Page 238 Command Specifications Table 4.40 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 from...
Page 239: Reassign Blocks (07)
4.3 Format Commands 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 240: Table 4.41 Reassign Block Command: Defect Data List Configuration
Command Specifications The format of the "Defect Data" list transferred from the INIT by this command is shown in Table 4.41. Table 4.41 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 Defect...
Page 241 4.3 Format Commands The HDD 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 242: Figure 4.2 Correction Of The Defect Descriptor
Command Specifications 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 243: Read Defect Data (37)
4.3 Format Commands 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 244: Table 4.43 Defect Data Format
Command Specifications Table 4.43 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. The HDD terminates data transfer when transfer of the length of defect data specified in the "Transfer byte length"...
Page 245 4.3 Format Commands 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 HDD 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 246: Table 4.45 Defect Data Conditions
Command Specifications 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 247 4.3 Format Commands 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 248: Read Defect Data (B7)
Command Specifications 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 249: Table 4.46 Read Defect Data Command (B7): Defect Data Configuration
4.3 Format Commands Table 4.46 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 C141-C013...
Page 250: Maintenance, Diagnostic Commands
Command Specifications 4.4 Maintenance, Diagnostic Commands 4.4.1 SEND DIAGNOSTIC (1D) Byte X'1D' SELF-TEST CODE SelfTest DevOfl UnitOfl Parameter List Length (MSB) Parameter List Length (LSB) This command executes self-diagnosis tests which the HDD is equipped to perform and operation specified in the parameter list transferred from the INIT. (1) Self-diagnosis test When the "SelfTest (self test)"...
Page 251: Table 4.47 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 252: Table 4.48 Error Recovery Control Flags During The Self-Diagnosis Test
Command Specifications Table 4.48 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. When an error which cannot be recovered from is detected, the diagnostic test terminates at that point with an error. The diagnostic test continues when error recovery is successful.
Page 253 4.4 Maintenance, Diagnostic Commands The "Parameter list length" field in the CDB shows the length (number of bytes) of the parameter list that is transferred from the INIT when the "SelfTest (self test)" bit's specification is "0." When zero is specified in the "Parameter list length"...
Page 254: Table 4.49 Send Diagnostic Command: Parameter List Configuration
Command Specifications Table 4.49 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. The parameter pages which can be specified by the INIT and their functions are as shown Table 4.50.
Page 255: Table 4.51 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 HDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command to the INIT. Table 4.51 shows the format of this parameter page.
Page 256: Table 4.52 Send Diagnostic Parameters: Phy Test Function
Command Specifications Table 4.52 SEND DIAGNOSTIC parameters: PHY Test function Byte X'3F' (page code) X'6' (Protocol Identifier) X'001C' (page parameter length) PHY Identifier PHY Test Function PHY Test Pattern PHY Test Pattern Physical Link Rate X'0000' (Reserved) PHY Test Pattern DWORD Control PHY Test Pattern DWORDS X'0000' (Reserved) Protocol Identifier...
Page 257 4.4 Maintenance, Diagnostic Commands PHY Identifier Specify the PHY that will become the operation target of the PHY Test function. If a value other than either of the values below is specified, HDD processing ends with a failure with CHECK CONDITION status "ILLEGAL REQUEST [=5]/ Invalid field in parameter list [=26-00]".
Page 258 Command Specifications PHY Test Pattern Physical Link Rate Specify the Link Rate when INIT sends the PHY Test Pattern. If a value other than any of the values below is specified, HDD processing ends with a failure with CHECK CONDITION status "ILLEGAL REQUEST [=5]/ Invalid field in parameter list [=26-00]".
Page 259: Table 4.53 Send Diagnostic Parameters: Logical/Physical Address Conversion
4.4 Maintenance, Diagnostic Commands Logical/physical address conversion This parameter page specifies conversion of the address information expressed in either the "Logical Block Address," "Physical Sector Address" or "Byte Distance from the Index" format to another expression format. Table 4.53 shows this parameter page format. The INIT can specify the address information that should be converted in this parameter page of the SEND DIAGNOSTIC command, and can read the conversion results by the RECEIVE DIAGNOSTIC RESULTS command (see Section 4.4.2 (2)).
Page 260 Command Specifications The description format of the address information specified in bytes 6 to 13 is the same as the description specification of the D List transferred from the INIT by the FORMAT UNIT command. For details, see the description of the FORMAT UNIT command (Section 4.3.1).
Page 261: Table 4.55 Self-Test
4.4 Maintenance, Diagnostic Commands Table 4.55 SELF-TEST Page code Function (Hex) 0,0,0 Refer to clause (2), Parameter Specification. 0,0,1 The device server shall start its short self-test routine in the background mode. 0,1,0 The device server shall start its extended self-test routine in the background mode.
Page 262: Receive Diagnostic Results (1C)
Command Specifications 4.4.2 RECEIVE DIAGNOSTIC RESULTS (1C) Byte X'1C' Transfer Byte Length (MSB) Transfer Byte Length (LSB) This command transfers data (response data) which show the results of executing the SEND DIAGNOSTIC command from the HDD to the INIT. The format and content of response data are determined by the parameter list (page code) specified by the INIT in the SEND DIAGNOSTIC command.
Page 263 4.4 Maintenance, Diagnostic Commands Table 4.56 RECEIVE DIAGNOSTIC RESULTS command: response data configuration Byte Page Code Header Page Parameter Length (MSB) Page Parameter Length (LSB) Page Parameters Parameter 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 264: Table 4.57 Receive Diagnostic Results Response Data: Page Code List
Command Specifications (1) Page code list This response data reports the "Page code" list of the parameter page supported by the HDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command after byte 4. The format and contents of this response data are shown in Table 4.57.
Page 265 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.58.
Page 266: Table 4.59 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 267: 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 HDD's data buffer memory or the SAS interface, or to download microcode to the HDD.
Page 268: Table 4.60 Write Buffer Transfer Mode
Command Specifications Table 4.60 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 269: Table 4.61 Write Buffer Command: Buffer Data (Mode = 000, 001)
4.4 Maintenance, Diagnostic Commands Table 4.61 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 270 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 271 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 HDD indicates that downloading of the new microcode failed, and it is therefore necessary for the INIT to quickly download the new microcode.
Page 272 Command Specifications The microcode or control information is written to the logical unit buffer starting at the location specified by the BUFFER Address field. If the HDD is unable to accept the specified buffer address, it shall return CHECK CONDITION status and it shall set the sense key to ILLEGAL REQUEST [=5] with an additional sense code of INVALID FIELD IN CDB [=24-00].
Page 273 4.4 Maintenance, Diagnostic Commands (8) Mode = 1, 0, 1, 0 : Echo buffer In this mode the HDD transfers data from the INIT and stores it in the echo buffer. The BUFFER ID and BUFFER OFFSET fields are ignored in this mode. C141-C013...
Page 274: Read Buffer (3C)
Command Specifications 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 HDD's data buffer memory and the SAS interface.
Page 275: Table 4.63 Read Buffer Command: Buffer Data (Mode = 0000, 0001)
4.4 Maintenance, Diagnostic Commands (1) Mode = 0, 0, 0, 0: Header + data, without address specification When this mode is specified, the data stored in the HDD's data buffer are transferred to the INIT after the 4-byte header. Zero must be specified in the "Buffer offset"...
Page 276 Command Specifications (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 HDD's data buffer transferred to the INIT following the 4-byte header.
Page 277: Table 4.64 Read Buffer Command: Buffer Descriptor
4.4 Maintenance, Diagnostic Commands (4) Mode = 0, 0, 1, 1: Buffer descriptor When this mode is specified, the HDD transfers only the 4-byte buffer descriptor to the INIT. the HDD's data buffer attributes are indicated in the 4-byte buffer descriptor.
Page 278: Table 4.65 Read Buffer Command: Echo Buffer Descriptor
Command Specifications (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. The "Buffer Offset" field is reserved in this mode. The allocation length should be set to four or greater.
Page 279: Read Long (3E)
4.4 Maintenance, Diagnostic Commands 4.4.5 READ LONG (3E) Byte X'3E' CORRCT Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Byte Length (MSB) Transfer Byte Length (LSB) This command reads the logical data block data and its ECC byte, specified in the "Logical block address"...
Page 280 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 when negative, as a complement...
Page 281: 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 282 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 283: Write Same (41)
4.4 Maintenance, Diagnostic Commands 4.4.7 WRITE SAME (41) Byte X'41' Pbdata Lbdata RelAdr Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Number of Blocks (MSB) Number of Blocks (LSB) This command requests that the device server write the single block of data transferred by the application client to the medium multiple times to consecutive multiple logical blocks.
Page 284 Command Specifications The "Number of Blocks" field specifies the number of contiguous logical blocks to be written. A "Number of Blocks" field of zero requests that all the remaining logical blocks on the medium be written. C141-C013...
Page 285: Chapter 5 Parameter Data Format
CHAPTER 5 Parameter Data Format Mode Parameters Log Parameters This chapter describes the HDD-provided detailed parameter data formats and how to use these formats. 5.1 Mode Parameters This section describes the pages used by the MODE SELECT, MODE SELECT EXTENDED, MODE SENSE, and MODE SENSE EXTENDED commands, which are applicable to any SAS devices.
Page 286: Read/Write Error Recovery Parameters (Page Code = 1)
Parameter Data Format 5.1.1 Read/Write Error Recovery Parameters (Page Code = 1) Table 5.1 lists the format of the page descriptor of this MODE SELECT parameter. Table 5.1 MODE SELECT parameters: read/write error recovery parameters Byte X'0A' (Page Length) AWRE ARRE Default Variable...
Page 287 5.1 Mode Parameters 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 288 Parameter Data Format 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. RC (read continuous) This bit specifies continuous transfer of all the data requested by a command unaccompanied by a delay for executing error recovery processing.
Page 289 5.1 Mode Parameters DCR (disable correction) "1": Even when a correctable data check has been detected, data correction according to the ECC is prohibited. "0": When a correctable data check has been detected, data correction according to the ECC is applied. The HDD disregards this bit and operates according to the default value (=0).
Page 290: Table 5.2 Combinations Of Error Recovery Flags
Parameter Data Format This parameter specifies the maximum time that can be used by the TARG for error recovery processing, as a 1ms constant. The value specified in this parameter is the maximum permissible time for error recovery processing for each individual command.
Page 291: Disconnect/Reconnect Parameters (Page Code = 2)
5.1 Mode Parameters 5.1.2 Disconnect/Reconnect Parameters (Page Code = 2) The format of the page descriptor in this MODE SELECT parameter is shown in Table 5.3. Table 5.3 MODE SELECT parameters: disconnect/reconnect parameters Byte X ' 0E ' (Page Length) X ' 00 ' X ' 00 ' Bus Inactivity Limit...
Page 292 Parameter Data Format 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 HDD is infinite. This parameter cannot be changed by INITs.
Page 293: Format Parameters (Page Code = 3)
5.1 Mode Parameters 5.1.3 Format Parameters (Page Code = 3) The Page descriptor format of this MODE SELECT parameter is shown in Table 5.4. Table 5.4 MODE SELECT parameters: format parameters Byte X'16' (Page Length) Track Count/Zone Default X'xxxx' Variable X'0000' Alternate Sector Count/Zone Default...
Page 294 Parameter Data Format 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 HDD's alternate block processing.
Page 295 5.1 Mode Parameters Parameters specifying track format (bytes 10, 11) − Sector count/track This parameter specifies the number of physical sectors per 1 track. In the HDD, 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 296 Parameter Data Format − SSEC (soft sectoring) When this bit is "1," it indicates that the data formatting method on the disk media is "soft sectoring." However, since the HDD uses only the "hard sectoring" method (refer to previously shown item b), this bit is disregarded.
Page 297: Table 5.5 Details Of Parameters On Mode Select Parameter
5.1 Mode Parameters Table 5.5 Details of parameters on MODE SELECT parameter: pages 3, 4, and C Page C Page 3 Page 4 LPN=0 (Default) LPN=1 Byte Byte Byte Byte Byte Byte Byte Byte Byte Byte 10-11 8-11 12-15 8-11 12-15 Number of Number of...
Page 298: Drive Parameters (Page Code = 4)
Parameter Data Format 5.1.4 Drive Parameters (Page Code = 4) The page descriptor format of this MODE SELECT parameter is shown in Table 5.6. Table 5.6 MODE SELECT parameters: drive parameters Byte X'16' (Page Length) Cylinder Count Default X'xxxxxx' Variable X'000000' Number of Heads Default...
Page 299 5.1 Mode Parameters 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).
Page 300: Verify Error Recovery Parameters (Page Code = 7)
Parameter Data Format 5.1.5 Verify Error Recovery Parameters (Page Code = 7) The page descriptor format of this MODE SELECT parameter is shown in Table 5.7. Table 5.7 MODE SELECT parameters: verify error recovery parameters Byte X'0A' (Page Length) (Reserved) Default Variable Number of retries during VERIFY.
Page 301 5.1 Mode Parameters 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 Section 5.1.1 concerning the details. Number of retries during VERIFY This parameter specifies the number of times reading of the disk media should be retried when a "Data Check"...
Page 302: Caching Parameters (Page Code = 8)
Parameter Data Format 5.1.6 Caching Parameters (Page Code = 8) The page descriptor format of this MODE SELECT parameter is shown in Table 5.8. Table 5.8 MODE SELECT parameters: caching parameters Byte X'12' (Page Length) ABPF DISC SIZE Default Variable Demand Read Retention Priority Write Retention Priority Default...
Page 303 5.1 Mode Parameters 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" concerning details of the Look- Ahead cache feature and parameter setting methods. RCD (read cache disable) This bit can be specified, and its operation is as specified.
Page 304 Parameter Data Format "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 305 5.1 Mode Parameters "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. Write retention priority (not supported) This field advises the device server the retention priority to assign for data written into the cache that has also been transferred from the cache memory to...
Page 306 Parameter Data Format This parameter cannot be changed. The HDD disregards the specification in this field. Maximum pre-fetch ceiling This parameter specifies the maximum quantity of logical data blocks pre- fetched to the data buffer with the READ command or READ EXTENDED command.
Page 307 5.1 Mode Parameters This parameter can be changed though the HDD disregards the specification of this field. The HDD divided the Cache Segments according to the inherent algorithm. That is, the Cache Segment size is best tuned per the request data size of Host command.
Page 308: Control Mode Parameters (Page Code = 0A)
Parameter Data Format 5.1.7 Control Mode Parameters (Page Code = 0A) The page descriptor format of this MODE SELECT parameter is shown in Table 5.9. Table 5.9 MODE SELECT parameters: control mode parameters Byte X'0A' (Page Length) (Reserved) GLTSD RLEC Default Variable Queue Algorithm Qualifier...
Page 309 5.1 Mode Parameters TST (task set type) This field specifies the type of task set defined below. Value Description 000b Task set per logical unit for all initiators 001b Task set per initiator per logical unit 010b-111b Reserved The HDD operates according to "000b". If other value is specified in this field, the HDD reports a "CHECK CONDITION"...
Page 310 Parameter Data Format "0": The HDD executes the command which is issued next normally. Since the HDD does not support the reporting function of exception condition, the HDD disregards the specification in this bit. DQue (disable queuing) (not supported) This bit specifies whether the HDD will execute processing of tagged commands or not.
Page 311 5.1 Mode Parameters RAC (report check) (not supported) The HDD is not supported in this bit. Therefore, the HDD always report "0", and ignore specified value. SWP (soft write protect) (not supported) This bit specifies whether or not to execute for the device server write operation to the medium.
Page 312: Notch Parameters (Page Code = 0C)
Parameter Data Format 5.1.8 Notch Parameters (Page Code = 0C) Table 5.10 MODE SELECT parameters: notch parameters Byte X'16' (Page Length) X'00' (Reserved) Default Variable X'00' (Reserved) Maximum number of notches Default X'001D' Variable X'0000' Active Notch Default X'0000' Variable X'FFFF' 8-11 Starting Boundary...
Page 313 5.1 Mode Parameters 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 314: Port Control Parameter (Page Code = 19)
Parameter Data Format 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 (HDD). Ending Boundary This field is valid in the MODE SENSE command. This field indicates the ending of the active notch or, if the active notch is zero, the ending of the logical unit (HDD).
Page 315: Table 5.11 Port Control Parameter: Page 0 Format (Short Page Format)
5.1 Mode Parameters Table 5.11 Port control parameter: Page 0 Format (Short Page Format) Byte SPF (0) X ' 06 ' (Page Length) Ready Reserved PROTOCOL IDENTIFIER Default Variable X'00' (Reserved) I_T NEXUS LOSS TIME Default X ' 07D0 ' Variable X ' FFFF ' INITIATOR RESPONSE TIMEOUT...
Page 316: Table 5.12 Port Control Parameter: Sub Page Format (Long Format)
Parameter Data Format I_T NEXUS LOSS TIME Specifies the maximum time for which the HDD performs error recovery processing for I_T Nexus Loss as a multiple of 1 ms. CODE DESCRIPTION 0000h Vender-specific 0001h to FFFEh Specifies the maximum time for error recovery processing as a multiple of 1 ms (recommended value: 2,000 ms).
Page 317: Table 5.13 Sas Phy Mode Descriptor Format
5.1 Mode Parameters NUMBER OF PHYS Indicates the total number of phys the TARG maintains. The following shows the details of the SAS phy mode descriptor that is reported in Byte 8 and subsequent bytes: Table 5.13 SAS phy mode descriptor format [This page cannot be modified] Byte Reserved (x'00')
Page 318 Parameter Data Format PHY IDENTIFIER Indicates the reported number for a Primary/Secondary Port. For a Primary Port, X'00' is set, and for a Secondary Port, X'01' is set. PHY OPERATION CODE The operation code specified by SMP PHY CONTROL is set. ATTACHED DEVICE TYPE Indicates the "Device Type"...
Page 319 5.1 Mode Parameters SAS ADDRESS Indicates the Port SAS ADDRESS of the TARGET. port SAS address (Port-A): 5CCC CCCX XXXX XXX 2 port SAS address (Port-B): 5CCC CCCX XXXX XXX 3 C: Company ID X: Serial number for WWN ATTACHED SAS ADDRESS Indicates the SAS address received from the INIT with an IDENTIFY address frame.
Page 320: Power Condition Parameter (Page Code = 1A)
Parameter Data Format 5.1.10 Power Condition Parameter (Page Code = 1A) Table 5.14 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 321: Informational Exceptions Control Page (Page Code = 1C)
5.1 Mode Parameters If "1" is specified, the HDD is permitted to enter the Standby condition after the elapse of the time specified in the "Standby Condition Timer" field. If "0" is specified, the HDD is prohibited from entering the Standby condition. Standby Condition Timer (unsupported) Specifies the time before the HDD enters the Standby condition.
Page 322 Parameter Data Format This bit of zero indicates the target disables reporting of the warning. The "MRIE" field is ignored when "DExcpt" is set to one and "EWASC" is set to zero. An "EWASC" bit of one indicates warning reporting is enabled. The method for reporting the warning when the "EWASC"...
Page 323 5.1 Mode Parameters EBACKERR (Enable Background Error) "0": Background self-test and Background Scan errors are not reported. "1": Background self-test and Background Scan errors are reported. However, the reporting means is determined depending on the value of the "MRIE" bit, and the values in the Interval timer and Report Count fields are ignored.
Page 324: Table 5.16 Mrie
Parameter Data Format Table 5.16 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 325: Table 5.17 Interval Timer
5.1 Mode Parameters Table 5.16 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 326: Background Control Mode Parameter (Page Code = 1C/Subpage = 01)
Parameter Data Format Report Count This 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. 5.1.12 Background Control Mode Parameter (Page Code = 1C/subpage = 01) Table 5.18 MODE SELECT parameters: background control mode parameter Byte...
Page 327 5.1 Mode Parameters S_L_FULL (Suspended on Log FULL) "1": Scanning is interrupted if the BMS Result Log Medium Scan Parameter indicates full status. "0": Scanning continues even if the BMS Result Log Medium Scan Parameter indicates full status. LOWIR (Log Only When Intervention Required) "1": Error information is stored in the BMS Result Log Medium Scan Parameter only when the host requires information for error...
Page 328 Parameter Data Format Pre-Scan Timeout Value This parameter specifies the maximum time, in hours, for a pre-scan operation to complete. If the pre-scan operation does not complete within the specified time then it is halted. A value of zero specifies an unlimited timeout value. Minimum IDLE TIME before Background Scan Displays the time from IDLE status to start of BMS (unit: milliseconds).
Page 329: Additional Error Recovery Parameters (Page Code = 21)
The value specified in this field is applicable for all commands which are accompanied by a seek operation. RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit. C141-C013...
Page 330: Table 5.20 Mode Parameter Default Values
Parameter Data Format Table 5.20 Mode parameter default values Default Value (MODE SENSE Ex DBD=1, Page=3F, SubPage=FF) xx: Device capacity dependent parameter, zz: Device type dependent parameter Header 01 32 00 00 00 00 00 08 Page01 81 0A C8 3F FF 00 00 00 3F 00 75 30 Page02 82 0E 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Page03...
Page 331: Log Parameters
5.2 Log Parameters 5.2 Log Parameters This section describes the log page structure and log pages that can be used for all SAS devices. Pages that are specific to each device format are described in the command standard that applies to the pertinent device format. The LOG SENSE command reports the log page that is specified in the page code field of the command descriptor block.
Page 332 Parameter Data Format The HDD does not support this bit. It always reports "0" in response to the LOG SENSE command (see Section 4.1.15). The LOG SELECT command will be accepted when this bit value is "1." However, the HDD will save the target with a specific algorithm, ignoring the value specified in the command.
Page 333: Support Log Page (X'00')
5.2 Log Parameters 5.2.1 Support Log Page (X'00') The supported log page returns the list of log pages implemented by the drive. Table 5.22 Support log page (X'00') Byte X'00' (Reserved) X'00' (Parameter Length) X'0E' (Parameter Length) X'00' (Supported Page) X'01' (Supported Page) X'02' (Supported Page) X'03' (Supported Page)
Page 334: Buffer Overrun/Underrun Page (X'01')
Parameter Data Format 5.2.2 Buffer Overrun/Underrun Page (X'01') Table 5.23 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...
Page 335: Write Error Count Page (X'02')
5.2 Log Parameters • 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 336 Parameter Data Format • Write errors recovered without delays (page 02, code 0000) Table 5.25 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 337: Table 5.27 Total Write Errors Posted (Page 02, Code 0002)
5.2 Log Parameters • Total write errors posted (page 02, code 0002) Table 5.27 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 338: Table 5.29 Total Write Bytes Processed (Page 02, Code 0005)
Parameter Data Format • Total write bytes processed (page 02, code 0005) Table 5.29 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 339: Read Error Count Page (X'03')
5.2 Log Parameters 5.2.4 Read Error Count Page (X'03') Table 5.31 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 340: Table 5.33 Read Errors Recovered With Possible Delays (Page 03, Code 0001)
Parameter Data Format • Read errors recovered with possible delays (page 03, code 0001) Table 5.33 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 341: Table 5.35 Total Recoverable Read Errors Posted To Init (Page 03, Code 0003)
5.2 Log Parameters • Total recoverable read errors posted to INIT (page 03, code 0003) Table 5.35 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 342: Verify Error Count Page (X'05')
Parameter Data Format • Total unrecoverable read errors posted to INIT (page 03, code 0006) Table 5.37 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 343: Table 5.39 Verify Errors Recovered Without Delays (Page 05, Code 0000)
5.2 Log Parameters • Verify errors recovered without delays (page 05, code 0000) Table 5.39 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 incurred.
Page 344: Table 5.41 Total Verify Errors Posted (Page 05, Code 0002)
Parameter Data Format • Total verify errors posted (page 05, code 0002) Table 5.41 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 345: Table 5.43 Total Verify Bytes Processed (Page 05, Code 0005)
5.2 Log Parameters • Total verify bytes processed (page 05, code 0005) Table 5.43 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 346: Non-Medium Error Count Page (X'06')
Parameter Data Format 5.2.6 Non-Medium Error Count Page (X'06') Table 5.45 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...
Page 347: Table 5.47 Temperature (Page 0D, Code 0000)
5.2 Log Parameters • Temperature (page 0D, code 0000) Table 5.47 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 348: Start-Stop Cycle Counter Page (X'0E')
Parameter Data Format 5.2.8 Start-Stop Cycle Counter Page (X'0E') Table 5.49 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 349: Table 5.51 Accounting Date (Page 0E, Code 0002)
5.2 Log Parameters • Accounting date (page 0E, code 0002) Table 5.51 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 350: Table 5.53 Start-Stop Cycle Counter (Page 0E, Code 0004)
Parameter Data Format 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 351: Application Client Page (X'0F')
5.2 Log Parameters 5.2.9 Application Client Page (X'0F') Table 5.54 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 352: Self-Test Result Page (X'10')
Parameter Data Format 5.2.10 Self-Test Result Page (X'10') Table 5.56 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 353: Table 5.58 Self-Test Results Values
5.2 Log Parameters 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 5.58. Table 5.58 Self-test results values Value Description...
Page 354: Background Medium Scan Page (X'15')
Parameter Data Format 5.2.11 Background Medium Scan Page (X'15') Note: These parameters (Table 5.60, "Background medium scan status parameter" and Table 5.62, "Background medium scan parameter") are not supported. In LOG SENSE, these parameters are not transferred. Table 5.59 Background medium scan page (X'15') Byte Page Length (MSB) Page Length (LSB)
Page 355: Table 5.61 Bms Status
5.2 Log Parameters 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 5.61 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 356: Table 5.62 Background Medium Scan Parameter
Parameter Data Format Table 5.62 Background medium scan parameter Byte (MSB) X'0001' - X'0400' (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 357: Protocol Specific Port Log Page (X'18')
5.2 Log Parameters 5.2.12 Protocol Specific Port Log Page (X'18') Table 5.64 Protocol specific port 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 358: Table 5.65 Log Parameter Format
Parameter Data Format • Details of the log parameter Table 5.65 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 359 5.2 Log Parameters Parameter Code Indicates the port number of a transferred log parameter. For port A, "0001" is reported, and for port B, "0002" is reported. PROTOCOL IDENTIFIER "6h" is set. NUMBER OF PHYS Indicates the number of SAS phy log descriptors that follow. PHY IDENTIFIER Indicates the number of ports the TARG has minus one.
Page 360 Parameter Data Format 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 HDD. - port SAS address (Port-A): 5CCC CCCX XXXX XXX 2 - port SAS address (Port-B): 5CCC CCCX XXXX XXX 3 C: Company ID...
Page 361: Smart Status Page (X'2F')
This page reports data which the HDD 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 362 This page is intentionally left blank.
Page 363: Chapter 6 Sense Data And Error Recovery Methods
CHAPTER 6 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 HDD are described.
Page 364: Table 6.1 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 365: Sense Data Basic Information
6.1 Sense Data 6.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 366 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 HDD without relation to the value specified in the "Transfer byte length"...
Page 367: Table 6.2 Sense Key Inherent Information
6.1 Sense Data Table 6.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-C013...
Page 368: Table 6.3 Sense Key
Sense Data and Error Recovery Methods Table 6.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 HDD. If multiple errors which were successfully recovered from during processing of a single command occurred, the last error to have occurred is reported.
Page 369: Table 6.4 Additional Sense Code And Additional Sense Code Qualifier
6.1 Sense Data Table 6.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 370 Sense Data and Error Recovery Methods Table 6.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 371 6.1 Sense Data Table 6.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 372 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 unique component "nn" code) 81: Buffer RAM compare error/bus error 83: HDC register check error...
Page 373 Table 6.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 HDD compare error • 91: WCS RAM parity error •...
Page 374 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) Abnormal Rotation of Spindle Motor Any error at Spindle Motor Start On track failure...
Page 375: Sense Data Additional Information
6.1 Sense Data 6.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 376: Init Error Recovery Methods (Recommended)
Sense Data and Error Recovery Methods 6.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 377 6.2 INIT Error Recovery Methods (Recommended) (1) TASK SET FULL status This status indicates that the HDD 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 HDD can receive the next command depends on the operating state with other INITs, so ordinarily, it cannot be predicted.
Page 378: Sense Data Analysis And Error Recovery Methods
Sense Data and Error Recovery Methods Since the command stack feature exists (see Section 2.4), even if the HDD 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 379: Table 6.5 Sense Data Error Classification
6.2 INIT Error Recovery Methods (Recommended) Table 6.5 Sense data error classification (1/3) Recovery Method Outline of Error (See Table 6.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 380 Sense Data and Error Recovery Methods Table 6.5 Sense data error classification (2/3) Recovery Method Outline of Error (See Table 6.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 381 6.2 INIT Error Recovery Methods (Recommended) Table 6.5 Sense data error classification (3/3) Recovery Method Outline of Error (See Table 6.6.) Power on, reset, or HARD RESET occurred None The HDD was initialized by a Power on or HARD RESET sequence.
Page 382: Table 6.6 Error Recovery Processing Procedures
Sense Data and Error Recovery Methods Table 6.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 383 6.2 INIT Error Recovery Methods (Recommended) Table 6.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 384 Sense Data and Error Recovery Methods Table 6.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 385 6.2 INIT Error Recovery Methods (Recommended) Table 6.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 7) or reconfirm the use conditions of the disk drive, such as the installation environment.
Page 386: Error Logging
Sense Data and Error Recovery Methods 6.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 HDD.
Page 387 6.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 HDD terminates the command which is currently being executed with a CHECK CONDITION status. The sense key in the sense data at this time is "MEDIUM ERROR [=3]"...
Page 388: Auto Alternate Block Allocation Processing
Sense Data and Error Recovery Methods judges that correction is possible, it regards verification as being successful and continues processing of subsequent data blocks. (5) Other internal HDD errors If an irrecoverable error other than those in items (1) to (4) above is detected internally in the HDD, the HDD terminates the command that is currently being executed with a CHECK CONDITION status.
Page 389 6.3 Disk Drive Error Recovery Processing even if "1" is specified in the ARRE flag, auto alternate block allocation processing will not be executed for errors in the data area. 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.
Page 390: Error Recovery Processing Control
Sense Data and Error Recovery Methods If error recovery is completed by rewriting the data to the data block, alternate block allocation is not performed for this data block. The data block is removed as the target of AWRE processing. (3) Auto alternate block allocation processing during a write operation 2 (servo auto alternate) This function is enabled by specifying "1"...
Page 391: Table 6.7 Disk Drive Errors And Number Of Retries
6.3 Disk Drive Error Recovery Processing EXTENDED command as necessary and select the error recovery flags and the number of retries. Read/Write Error Recovery Parameters (Page Code = 1) 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)
Page 392 Sense Data and Error Recovery Methods In processing of data blocks for which alternate sector processing is completed, the number of retries on the defective sectors is calculated separately from the number of retries on the alternate sectors. C141-C013...
Page 393: Chapter 7 Disk Media Management
CHAPTER 7 Disk Media Management Defect Management Disk Media Initialization Alternate Block Allocation Processing Background Media Scan (BMS) Drive Self-Test (DST) SMART (Self-Monitoring Analysis and Reporting Technology) 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 394 Disk Media Management (2) Alternate block allocation Alternate data blocks are allocated in defective sector units for defective data blocks (= sectors) on the disk media by the HDD's internal defect management methods. Spare sector area Spare sectors for allocation as alternate blocks are secured in one or both of the following areas.
Page 395 7.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 396: Disk Media Initialization
Disk Media Management 7.2 Disk Media Initialization 7.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 397: Re-Initialization
7.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 398 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 399: Alternate Block Allocation Processing
7.3 Alternate Block Allocation Processing 7.3 Alternate Block Allocation Processing If errors on the disk media which cannot be recovered from are detected, or if a recoverable error occurs repeatedly in the same data block, it is necessary for the INIT to allocate an alternate block for the data block where the error occurred using the REASSIGN BLOCKS command.
Page 400: Background Media Scan (Bms)
Disk Media Management 7.4 Background Media Scan (BMS) 7.4.1 Overview This function performs a background task that verifies the entire media surface by scanning it during idle time based on the specification on Mode Page 0x1C SubPage 0x01 (Background Control mode Page). During the scan, automatic alternate processing is performed based on what is specified by the Retry Parameter.
Page 401: Write Command Operation During A Pre-Scan
7.4 Background Media Scan (BMS) If a scan ends with an error, the next Pre-Scan operation will begin with LBA 0. If the Write command is issued to an LBA that was not scanned, this LBA will be verified after data is written to it. (For further information, see the next section.) 7.4.2.3 Write command operation during a Pre-Scan If the Write command is issued to an LBA that has yet to be scanned, the Write command will function as a Write&Verify command during the Pre-Scan period.
Page 402: Mode Page
Disk Media Management 7.4.3 Mode Page Table 7.1 Mode Page 0x1C SubPage 0x01 (Background Control Mode Page) Byte Subpage Code = 01 Subpage Length S_L_FULL Reserved LOWIR EN_BMS Default Variable Reserved EN_PS Default Variable BMS Interval Time Default X '0018' Variable X 'FFFF' PRE-SCAN Timeout Value...
Page 403 7.4 Background Media Scan (BMS) EN_BMS (Enable Background Media Scan) When this bit is set to "1," the Background Media Scan (BMS) function is enabled. Media scan processing will begin at the time determined by the BMS Interval Time (bytes 6-7) specification. When this bit is cleared to "0,"...
Page 404: Background Media Scan Log Page
Disk Media Management 7.4.4 Background Media Scan Log Page The Background Media Scan log page includes one BMS Status parameter and up to 1024 medium scan parameters. The table below shows the Background Scan Result Log Page format. Table 7.2 Background Media Scan Log Page format Page code (0 Byte 0 Page length (...
Page 405: Table 7.3 Bms Status Parameter Format
7.4 Background Media Scan (BMS) Table 7.3 BMS Status parameter format Byte 0 (MSB) Parameter Code (0x0000) (LSB) LBIN Parameter Length (0x0C) (MSB) Time Stamp (LSB) Reserved BMS Status (MSB) Number of Scan Performed (MSB) Medium Scan Progress (LSB) Reserved The "Time Stamp"...
Page 406: Table 7.4 Medium Scan Parameter Format
Disk Media Management The "Number of Scans Performed" field reports the number of times scanning has been performed. The "Medium Scan Progress" field reports the scan progress in percentage. The table below shows the (xxxx/10000h) Medium Scan parameter format. Table 7.4 Medium Scan parameter format Byte 0 (MSB) Parameter Code (0x0001 to 0400h)
Page 407 7.4 Background Media Scan (BMS) The values that may be reported in the "Reassign Status" field are as follows: "0h" Reassignment has not been performed. "1h" The Reassign or Write command issued by the initiator is being awaited. "2h" Automatic alternate processing has been performed. "3h"...
Page 408: Drive Self-Test (Dst)
Disk Media Management 7.5 Drive Self-Test (DST) 7.5.1 Overview This function supports two types of self-tests based on the specification in the "SELF-TEST CODE" field of the SEND DIAGNOSTICS command as follows: Short self-test Extended self-test A short self-test is conducted to quickly verify whether the HDD contains a defect, whereas an extended self-test is a more comprehensive test conducted by the HDD without INIT intervention.
Page 409: Self-Test Modes
7.5 Drive Self-Test (DST) 7.5.2 Self-test modes Self-tests of each type are conducted in either of the following two modes: Foreground mode Background mode The subsequent sections explain both modes in detail. 7.5.2.1 Foreground mode Before the INIT initiates a self-test in foreground mode, the HDD should be reserved.
Page 410: Background Mode
Disk Media Management 7.5.2.2 Background mode If the HDD receives a SEND DIAGNOSTICS command that specifies the execution of a self-test in background mode, it will report the status immediately after verifying the CDB. The HDD reports the status in response to the SEND DIAGNOSTICS command that specifies the execution of a self-test in background mode, and then initializes the self-test result log page as follows: Filling in the "Self-Test Code"...
Page 411: Matters That Are Common To Both Modes
7.5 Drive Self-Test (DST) 7.5.3 Matters that are common to both modes During a self-test, the INIT can obtain the progress of the self-test by referencing the "sense key specific information" field (bytes 16-17), which is returned in response to the REQUEST SENSE command. When the self-test has encountered no error, the HDD terminates the command with CHECK CONDITION status (NOT READY [=2]/LOGICAL UNIT NOT READY, SELF-TEST IN PROGRESS [04-09]).
Page 412 Disk Media Management b. Flash ROM test This test segment conducts a sumcheck test on each block of program code contained in flash ROM. If a sumcheck error is detected on one block, Hardware Error [=4]/F/W Header/Check SUM Error [=40-84] is reported on the self-test result log page.
Page 413 7.5 Drive Self-Test (DST) Data compare test This test segment compares data by performing write/read processing on the internal-test cylinder using all heads. If it encounters an error while performing data compare processing, Miscompare [=E]/Miscompare During Self Configuration [=1D-80] is reported on the self-test result log page. If this test segment encounters an error while performing processing other than data compare processing, error information that indicates the cause of error is reported on the self-test result log page.
Page 414: Smart (Self-Monitoring Analysis And Reporting Technology)
Disk Media Management 7.6 SMART (Self-Monitoring Analysis and Reporting Technology) 7.6.1 Overview The SMART function of the HDD monitors events that represent signs of HDD deterioration or failure. The HDD monitors the following metrics (attributes): Read error rate Write error rate Seek error rate Number of remaining alternate sectors Spin-up time...
Page 415: Data Analysis
7.6 SMART (Self-Monitoring Analysis and Reporting Technology) (5) At certain time intervals (nearly hourly). If the state where there is no command to execute does not last for one second or longer, a log save operation may be postponed until the appropriate condition is fulfilled. (6) When a reset condition is generated (7) When the REZERO UNIT command is executed (8) When the STOP UNIT command is executed...
Page 416: Failure Prediction Method
Disk Media Management Table 7.5 SMART ASC/ASCQ ASCQ Description The value of the read error rate attribute has reached its threshold. The value of the G-list update frequency attribute has reached its threshold. The value of the write error rate attribute has reached its threshold.
Page 417 7.6 SMART (Self-Monitoring Analysis and Reporting Technology) Sample size 1,000,000 read sectors Threshold 300 errors Target READ READ, READ LONG, VERIFY, verify processing for commands WRITE AND VERIFY, media validation read during automatic alternate processing, media validation read during FORMAT UNIT command execution, user data area read during Drive Self Test/Background Media Scan b.
Page 418 Disk Media Management d. Number of remaining alternate sectors The HDD monitors the number of remaining alternate sectors. If the number of spare sectors that can be allocated as alternatives drops below the threshold for a physical reason or due to the size of a control table within the HDD, the HDD considers that a failure prediction reporting condition has developed.
Page 419: Table 7.6 Smart Thresholds
7.6 SMART (Self-Monitoring Analysis and Reporting Technology) h. DE temperature The HDD measures the device temperature at one-minute intervals. It also measures the temperature under one of the following conditions: When the LOG SENSE command is executed (Log Page 0D or 2F) When the REQUEST SENSE command is executed When retry processing is performed If the EWASC bit (MODE SELECT parameter on Page 1C) is set and the...
Page 420: Reporting Function
Disk Media Management 7.6.4 Reporting function If failure is predicted, the HDD notifies the INIT of failure prediction at the specified time intervals by the reporting method specified by the MODE SELECT parameter on Page 1C as described in Section 5.1.11. This reporting to the INIT begins when failure is predicted.
Page 421: 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 422 This page is intentionally left blank.
Page 423: Acronyms And Abbreviations
Acronyms and Abbreviations Disable Transfer on Error ACKnowledge Asynchoronous Event Notification Error Correction Code Arbitration In Progress primitive Enable Early Recovery ALTernated (block) EOAF End Of Address Frame primitive ARRE Automatic Read Reallocation End Of Frame primitive Enabled EVPD Enable Vital Product Data ASCII American Standard Code for Information Interchange...
Page 424 Acronyms and Abbreviations SCSI Small Computer System Interface SeCTor Original Equipment Manufacturer SELect Out Of Band SelfTest Self Test Signal Ground SOAF Start Of Address Frame primitive P list Primary defect list Start Of Frame primitive Parts/Number Save Page PBdata Physical Block data SPaRe block PC board Printed Circuit board Servo...
Page 425: Index
Index 10-Byte CDB basic format......104 arbitration fairness ........67 12-Byte CDB basic format......105 arbitration in progress......... 47 6-Byte CDB basic format......104 ARRE ............283 8b10b coding..........31 auto alternate block allocation processing........384, 391 auto alternate block allocation processing during read abort processing ........119 operation..........
Page 426 Index control byte ..........107 control command ........135 cache segment count........302 control mode parameter ......304 cache segment size ........302 correctable bit length ......285, 297 cached command ........130 correctable data read error ......383 cached data ..........130 correction of defect descriptor ....238 caching operation ........130 count basis ..........
Page 427 Index demand read retention priority ....300 EN_BMS ..........323 detailed information ........371 EN_PS ............323 details of parameters on MODE enable background function ..... 317 SELECT parameter ......293 enable early recovery........ 284 device serial No.........146, 147 enable threshold comparison ....190 device serial number field ......141 enable vital product data......
Page 428 Index FORMAT UNIT command information unit .......... 81 parameter list configuration ....227 information unit supported bit ....142 FOV............228 informational exception control FSW............302 page............317 INIT error recovery method...... 372 initialization during installation ....392 initiator control enable......300 G list ..........225, 389 INQUIRY (12)..........
Page 429 Index look-ahead cache feature......130 MODE SELECT parameter..289, 294, 296, 298, 304, 308, 317, 322, 325 look-ahead operation.........133 MODE SELECT parameter of look-ahead volume ........133 HDD ............ 160 LP .............191 MODE SELECT parameter LPN ............309 structure..........155 MODE SENSE (1A)......... 166 MODE SENSE command maintenance command......246 parameter configuration ......
Page 430 Index PERSISTENT RESERVE IN parameter data for READ P list...........225, 240, 389 RESERVATIONS ....... 197 page code...137, 160, 189, 192, 250, 259 PERSISTENT RESERVE IN page code = 0A..........304 service action ........195 page code = 0C..........308 PERSISTENT RESERVE OUT page code = 1..........282 (5F) ............
Page 431 Index queue algorithm qualifier ......305 reference temperature ....... 343 queue error management ......306 re-initialization ......... 393 quick arbitrate supported bit .....142 RELEASE (17)......... 183 RELEASE EXTENDED (57)....184 release function......... 183 release object ..........183 RAC ............307 removable medium ........292 rate matching..........71 report check ..........
Page 432 Index SAS drive connection pattern......22 soft sectoring..........292 SAS interface..........21 soft write protect ........307 SAS interface, topology ......22 spare sector area........390 SAS layering ..........23 spare sector within cell ......390 SAS OOB sequency ........36 specified cycle count over device lifetime..........
Page 433 Index TASK SET FULL status ....109, 373 user space logical block address....125 task set type..........305 TB 284 temperature..........343 valid ............361 temperature page (X'0D') ......342 vendor ID field ......... 141 termination status analysis ......372 vendor unique ........... 107 TEST ............318 VERIFY (2F)..........
Page 434 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 435 This page is intentionally left blank.
Page 436 MBA3073RC, MBA3147RC, MBA3300RC SERIES, MBB2073RC, MBB2147RC SERIES, MBC2036RC, MBC2073RC SERIES DISK C141-C013-01EN DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS MBA3073RC, MBA3147RC, MBA3300RC SERIES, MBB2073RC, C141-C013-01EN MBB2147RC SERIES, MBC2036RC, MBC2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS...

This manual is also suitable for:

Mbc2036rc series Mbc2073rc series Mba3300rc series Mbb2073rc series Mbb2147rc series Mba3147rc - enterprise 147 gb hard drive

Fujitsu MBA3073RC SERIES Technical Manual

CHAPTER 1 SAS Interface

CHAPTER 2 Command Processing

CHAPTER 3 Data Buffer Management

CHAPTER 4 Command Specifications

Quick Links

Related Manuals for Fujitsu MBA3073RC SERIES

Summary of Contents for Fujitsu MBA3073RC SERIES