manualshive.com logo in svg

Fujitsu MAU3036RC SERIES, Technical Manual

The Fujitsu MAU3036RC SERIES Product/Maintenance Manual is a comprehensive guide that provides users with all the necessary information for the optimal use and maintenance of their Fujitsu MAU3036RC SERIES product. This manual is available for free download from manualshive.com and ensures hassle-free product understanding and long-term reliability.

Share
Download
background image

Serial Attached SCSI (SAS) Interface 

 

1-50 

C141-C009 

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 

CLOSE 

This confirms that the connection has been closed. 

Close Timeout 
timer expires 

The originating phy shall attempt to break the connection. 

 

Figure 1.16 shows example sequences for closing a connection.  

 

CLOSE primitive

sequence

CLOSE primitive

sequence

time

time

transmitter

receiver

CLOSE primitive

sequence

CLOSE primitive

sequence

time

time

transmitter

receiver

Example 2: CLOSEs sent simultaneously

Example 1: CLOSEs sent one at a time

 

 

Figure 1.16  Closing a connection example  

Summary of Contents for MAU3036RC SERIES

Page 1: ...C141 C009 01EN MAU3036RC MAU3073RC MAU3147RC SERIES MAV2036RC MAV2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS ...

Page 2: ...utic or space systems mass transport vehicle operating controls medical devices for life support or weapons firing controls where particularly high reliability requirements exist where the pertinent levels of safety are not guaranteed or where a failure or operational error could threaten a life or cause a physical injury hereafter referred to as mission critical use Customers considering the use ...

Page 3: ...C141 C009 Revision History 1 1 Edition Date Revised section 1 Added Deleted Altered Details 01 2005 02 20 1 Section s with asterisk refer to the previous edition when those were deleted ...

Page 4: ...This page is intentionally left blank ...

Page 5: ...vided on a subsequent page Please use these other manuals along with this manual as necessary The organization of this manual related reference manual and conventions for alert messages follow Overview of Manual This manual consists of the following six chapters glossary abbreviation and index Chapter 1 SAS Interface This chapter describes the topology physical and electrical requirements interfac...

Page 6: ... error recovery to be executed through host system software and retry processing Chapter 6 Disk Media Management This chapter describes the procedure for initializing the disk media methods of treating media defects and data recovery methods Glossary The glossary explains technical terms which are necessary to the reader s understanding when reading this manual Acronyms and Abbreviations This list...

Page 7: ...ize 3 3 5 inch 2 2 5 inch Type AU 3 5 inch height 15 000rpm AT 3 5 inch height 10 025rpm AV 2 5 inch height 10 025rpm Decimal numbers are represented normally Hexadecimal numbers are represented as shown in the following examples X 17B9 17B9h 17B9H or 17B9H Binary number is represented as 010 010b An X is used to represent mode parameters that are ignored by the MODE SELECT and MODE SELECT EXTENDE...

Page 8: ...orrectly This alert signal also indicates that damages to the product or other property may occur if the user does not perform the product correctly This indicates information that could help the user use the product more efficiently In the text the alert signal is centered followed below by the indented message A wider line space precedes and follows the alert message to show where the alert mess...

Page 9: ...tions This Manual 1 Serial Attached SCSI SAS Interface 2 Command Processing 3 Data Buffer Management 4 Command Specifications 5 Sense Data and Error Recovery Methods 6 Disk Media Management Maintenance Manual 1 Specifications and Equipment Configuration 2 Maintenance and Diagnosis 3 Troubleshooting 4 Removal and Replacement Procedures 5 Operating Theory MANUAL ORGANIZATION ...

Page 10: ...d SCSI 1 1 SAS 1 1 American national Standards Institute ANSI T10 1236D Revision 20 Information technology SCSI Primary Commands 2 SPC 2 American national Standards Institute ANSI T10 996D Revision 8C Information Technology SCSI 3 Block Commands SBC American national Standards Institute ANSI T10 1157D Revision 24 Information technology SCSI 3 Architecture Model SAM 2 American national Standards In...

Page 11: ...onditions of the link reset sequence 1 13 1 3 4 Out of band OOB signals 1 13 1 3 5 SAS OOB sequency 1 16 1 3 5 1 Exception handling in the OOB sequence 1 18 1 3 6 SAS speed negotiation sequence 1 18 1 3 6 1 Phy reset sequence after devices are attached 1 22 1 3 6 2 When the speed negotiation sequence is successful 1 23 1 3 6 3 Exception handling in the speed negotiation sequence 1 23 1 3 7 Phy lay...

Page 12: ...36 1 4 4 5 NAK negative acknowledgement 1 36 1 4 4 6 RRDY 1 36 1 4 4 7 SOF Start of frame 1 36 1 4 5 Clock skew management 1 37 1 4 6 Idle physical link 1 37 1 4 7 Scrambling 1 38 1 5 Address frames 1 39 1 5 1 Address frames overview 1 39 1 5 2 IDENTIFY address frame 1 40 1 5 3 OPEN address frame 1 42 1 5 4 Identification and hard reset sequence 1 45 1 5 5 Connections 1 46 1 5 5 1 Connections over...

Page 13: ... 2 5 RESPONSE information unit 1 72 1 6 3 Sequences of SSP frames 1 76 1 6 4 Exceptional event processing of a drive 1 79 CHAPTER 2 Command Processing 2 1 2 1 Command Format 2 1 2 2 Status Byte 2 6 2 3 Command Queuing Function 2 8 2 4 UNIT ATTENTION Condition 2 9 2 4 1 Generation of the UNIT ATTENTION condition 2 9 2 4 2 Response and release condition at UNIT ATTENTION condition hold state 2 10 2 ...

Page 14: ...e 3 4 3 2 1 Caching operation 3 4 3 2 2 Caching parameters 3 6 3 2 3 Look Ahead operation Look Ahead volume 3 7 CHAPTER 4 Command Specifications 4 1 4 1 Control Sense Commands 4 1 4 1 1 TEST UNIT READY 00 4 1 4 1 2 INQUIRY 12 4 2 4 1 3 READ CAPACITY 25 4 16 4 1 4 MODE SELECT 15 4 17 4 1 5 MODE SELECT EXTENDED 55 4 69 4 1 6 MODE SENSE 1A 4 71 4 1 7 MODE SENSE EXTENDED 5A 4 78 4 1 8 REZERO UNIT 01 4...

Page 15: ...XTENDED 2A 4 140 4 2 5 WRITE AND VERIFY 2E 4 141 4 2 6 VERIFY 2F 4 142 4 2 7 SEEK 0B 4 143 4 2 8 SEEK EXTENDED 2B 4 144 4 2 9 SYNCHRONIZE CACHE 35 4 145 4 3 Format Commands 4 146 4 3 1 FORMAT UNIT 04 4 146 4 3 2 REASSIGN BLOCKS 07 4 157 4 3 3 READ DEFECT DATA 37 4 161 4 3 4 READ DEFECT DATA B7 4 166 4 4 Maintenance Diagnostic Commands 4 167 4 4 1 SEND DIAGNOSTIC 1D 4 167 4 4 2 RECEIVE DIAGNOSTIC R...

Page 16: ...ry methods 5 16 5 2 3 Error logging 5 24 5 3 Disk Drive Error Recovery Processing 5 24 5 3 1 Error states and retry processing procedures 5 24 5 3 2 Auto alternate block allocation processing 5 26 5 3 3 Error recovery processing control 5 28 CHAPTER 6 Disk Media Management 6 1 6 1 Defect Management 6 1 6 2 Disk Media Initialization 6 4 6 2 1 Initialization during installation 6 4 6 2 2 Re initiali...

Page 17: ...re 1 15 Connection request timeout example 1 49 Figure 1 16 Closing a connection example 1 50 Figure 1 17 Interlocked frames 1 55 Figure 1 18 Non interlocked frames with the same tag 1 56 Figure 1 19 Non interlocked frames with different tags 1 56 Figure 1 20 Closing an SSP connection example 1 57 Figure 1 21 Example of XFER_RDY frames 1 68 Figure 1 22 Example of TASK frame 1 76 Figure 1 23 Exampl...

Page 18: ...uirement 1 37 Table 1 17 Scrambling for different data dword types 1 38 Table 1 18 Address frame format 1 39 Table 1 19 IDENTIFY address frame format 1 40 Table 1 20 DEVICE TYPE field 1 40 Table 1 21 OPEN address frame format 1 42 Table 1 22 PROTOCOL field 1 42 Table 1 23 CONNECTION RATE field 1 43 Table 1 24 ARBITRATION WAIT TIME field 1 44 Table 1 25 Connection responses 1 47 Table 1 26 Arbitrat...

Page 19: ...upport 4 10 Table 4 7 VPD information 4 11 Table 4 8 VPD information VPD identifier list 4 11 Table 4 9 VPD information device serial No 4 12 Table 4 10 VPD information device unique information 4 13 Table 4 11 VPD information operation mode 4 15 Table 4 12 READ CAPACITY data 4 17 Table 4 13 MODE SELECT command Group 0 parameter configuration 4 21 Table 4 14 MODE SELECT parameters 4 24 Table 4 15 ...

Page 20: ...8 Table 4 41 Page code 4 89 Table 4 42 Page descriptor 4 89 Table 4 43 Page Code assignment for the log pages 4 92 Table 4 44 Support log page X 00 4 93 Table 4 45 Buffer overrun underrun page X 01 4 94 Table 4 46 Write error count page X 02 4 95 Table 4 47 Write errors recovered without delays page 02 code 0000 4 96 Table 4 48 Write errors recovered with possible delays page 02 code 0001 4 96 Tab...

Page 21: ...ice lifetime page 0E code 0003 4 109 Table 4 75 Start stop cycle counter page 0E code 0004 4 110 Table 4 76 Application client page X 0F 4 111 Table 4 77 General usage application client parameter data page 0F code 0000 003F 4 111 Table 4 78 Self test result page X 10 4 112 Table 4 79 Self test result parameter data page 10 code 0001 0014 4 112 Table 4 80 Self test results values 4 113 Table 4 81 ...

Page 22: ...C parameters page code list 4 172 Table 4 113 SEND DIAGNOSTIC parameters logical physical address conversion 4 173 Table 4 114 Specifying address format 4 173 Table 4 115 SELF TEST 4 174 Table 4 116 RECEIVE DIAGNOSTIC RESULTS command response data configuration 4 176 Table 4 117 RECEIVE DIAGNOSTIC RESULTS response data page code list 4 177 Table 4 118 RECEIVE DIAGNOSTIC RESULTS response data logic...

Page 23: ...S Interface 1 1 Topologies in SAS Interface 1 2 Names and identifiers 1 3 Phy layer 1 4 Link layer 1 5 Address frames 1 6 Transport layer This chapter describes the topology interface protocol and operation of the SAS interface ...

Page 24: ...ection SAS HBA INIT SAS Drive SSP Serial SCSI Protocol SAS Expander s SAS HBAs INIT STP SSP SSP SMP SAS Drive SAS Drive SATA Drive SAS Drive SAS Drive SATA Drive Figure 1 1 SAS drive connection patterns SAS supports the three protocols listed below Among these protocols SAS drives support only SSP Serial SCSI Protocol SSP Serial ATA Tunneling Protocol STP Serial Management Protocol SMP ...

Page 25: ...ed 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 Wide port control Transport layer Frame control Application layer SCSI commands mode pages and log pages Physical layer Phy layer Link layer Port layer Transport layer Application layer Figure 1 2 SAS control layers ...

Page 26: ...phy is the phy to which a phy is attached over a physical link A device may contain one or more phys Each phy has a phy identifier which is unique within the device Phy Transceiver Physical link Differential signal pair Differential signal pair Receiver Transmitter Phy Transceiver Transmitter Receiver Figure 1 3 Physical links and phys 1 1 3 Ports narrow ports and wide ports A port contains one or...

Page 27: ...ft transmit SAS addresses of B only phys attached to the same SAS addresses become part of the same ports The set of phys with SAS address B attached to the set of phys with SAS address D become one port while the set of phys with SAS address B attached to the set of phys with SAS address E become another port Narrow port Wide port Wide port Narrow port Wide port Wide port Physical link SAS addres...

Page 28: ...row 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 Figure 1 5 shows examples of SAS devices with different port and phy configurations Wide port SAS Device SAS Device SAS Device Phy Phy Wide port Phy Phy Wide port Phy Phy Narrow port Narrow port Phy Phy Figure 1 5 SAS devices ...

Page 29: ... be using the same physical link rate A pathway is a set of physical links between a SAS INIT phy and a SAS TARG phy being used by a connection Figure 1 6 shows examples of potential pathways Phy Phy Phy Expander device Phy Phy Phy Phy Phy Phy Phy Physical link Potential pathway Figure 1 6 Example of potential pathways A partial pathway is the set of physical links participating in a connection re...

Page 30: ... TARG phy established through the connection request Every phy shall support a 1 5 Gbps connection rate regardless of its physical link rate One connection may be active on a physical link at a time If the connection is an SSP or SMP connection and there are no dwords to transmit associated with that connection idle dwords are transmitted The number of connections established by a SAS port shall n...

Page 31: ...ned in SPC 3 The SAS address shall be worldwide unique A SAS address of 00000000_00000000h indicates an invalid SAS address Table 1 1 SAS address format Bit Byte 7 6 5 4 3 2 1 0 0 MSB 1 2 IEEE COMPANY ID 3 LSB MSB 4 5 6 7 LSB SAS addresses represent any of three types of WWNs a device SAS address representing a device address a port SAS address representing Port A or a port SAS address representin...

Page 32: ...ocquenghem BCH 63 39 9 codes Table 1 2 lists the parameters for the code Table 1 2 Hashed SAS address code parameter Parameter Value Number of bits per codeword 63 Number of data bits 39 Number of redundant bits 24 Minimum distance of the code 9 The generator polynomial for this code is G x x 6 x 1 x 6 x 4 x 2 x 1 x 6 x 5 x 2 x 1 x 6 x 3 1 After multiplication of the factors the generator polynomi...

Page 33: ...5 ALIGN and most primitives that are defined in SAS ALIGN K28 6 SATA_ERROR used on the physical link layer of SATA Not used Dxx y Data Data A single data dword is a dword that starts with a data character Running disparity shall be maintained separately on each physical link During a connection expander devices shall convert incoming 10 bit characters to 8 bit bytes and generate the 10 bit charact...

Page 34: ...character and dword alignment on the incoming bit stream 1 3 2 Link reset sequence The link reset sequence consists of the phy reset sequence and the identification sequence The phy reset sequence consists of the out of band OOB sequence and speed negotiation sequence The hard reset sequence is performed only when the HARD_RESET primitive is detected after the completion of the speed negotiation T...

Page 35: ...mitted During the burst time ALIGN 0 primitives are transmitted repeatedly The signals are differentiated by the length of idle time between the burst times Table 1 4 OOB signal timing specifications Parameter Minimum Nominal Maximum Comments OOB interval OOBI 1 666 600 ps 666 666 ps 666 733 ps The time basis for burst times and idle times used to create OOB signals Based on 1 5 Gbps clock toleran...

Page 36: ...he detection circuitry as required for any signaling that may be A C coupled If G2 ALIGNs are used the number of ALIGNs doubles compared with G1 ALIGNs A SAS transmitter should transmit ALIGNs at the G1 physical link rate to create the burst portion of the OOB signal but may transmit ALIGNs at its lowest supported physical link rate if it is not able to transmit at the G1 physical link rate and sh...

Page 37: ...bes the OOB signal receiver requirements for detecting negation times assuming Tidle is the length of the detected idle time Table 1 8 OOB signal receiver negation time detection requirements Signal Detection requirements COMINIT COMRESET Tidle 525 ns COMSAS Tidle 1575 ns A receiver shall detect an OOB signal after receiving four consecutive idle time burst time pairs It is not an error to receive...

Page 38: ...both have received the COMSAS signal from each other the OOB sequence is recognized as having been performed successfully Depending on the power on timing reception of the COMINIT signal from the other side may not be detected In such a case however the OOB sequence is recognized as having been performed successfully if the COMINIT and COMSAS signals have been sent by the time the COMSAS signal fr...

Page 39: ...tarts SAS OOB sequence A B Time 0 Time z COMINIT COMINIT COMSAS COMSAS Phy A Tx Phy B Rx Phy A Rx Phy B Tx Scenario 3 SAS phy B misses SAS phy A s COMINIT COMINIT COMSAS B A Phy A Tx Phy B Rx Phy A Rx Phy B Tx Time 0 Time z COMINIT COMSAS A SAS phy A power on B SAS phy B power on Time 0 SAS phy reset sequence begins Time z SAS speed negotiation sequence begins Figure 1 10 SAS to SAS OOB sequence ...

Page 40: ...ive sends the COMSAS signal but the COMSAS signal from the other side cannot be detected the drive waits for the reception of the COMSAS signal from the INIT or expander until the hot plug timeout time 500 ms elapses If the hot plug timeout time elapses before the COMSAS signal from the other side has been received the drive sends the COMSAS signal again to start a new link reset sequence 1 3 6 SA...

Page 41: ... is transmitted at each physical link rate during the speed negotiation sequence Derived from OOBI x 4096 x 40 Speed negotiation lock time SNLT 153 600 OOBI The maximum time during the speed negotiation window for a transmitter to reply with ALIGN 1 Derived from OOBI x 3840 x 40 Speed negotiation window time 913 840 OOBI The duration of a speed negotiation window Derived from RCDT SNTT The speed n...

Page 42: ...then proceed to the next speed negotiation window A phy shall participate in all speed negotiation windows a up to its highest supported physical link rate plus one or b until it runs a speed negotiation window that does not detect a valid physical link rate after having detected a valid physical link rate in a previous speed negotiation window If the phy has detected a valid physical link rate in...

Page 43: ...ation sequence fails Figure 1 13 shows the same speed negotiation sequence as in Figure 1 12 when phy B does not obtain dword synchronization during the final speed negotiation window If this occurs the handshake is not complete and the OOB sequence shall be retried starting with COMINIT forcing the phy to retry the whole reset sequence Hot Plug Timeout delay Phy A Tx Phy B Rx Phy A Rx Phy B Tx RC...

Page 44: ...are attached some time before phy B s second hot plug timeout occurs Phy B s OOB detection circuitry detects a COMINIT after the attachment and therefore phy B transmits COMSAS since it has both transmitted and received a COMINIT Upon receiving COMSAS phy A transmits its own COMSAS The SAS speed negotiation sequence follows A Phy A Tx COMINIT COMINIT COMINIT COMSAS Hot Plug Timeout Hot Plug Timeou...

Page 45: ...apses When the hot plug timeout time elapses before the signal has been received from the other side the drive sends the COMINIT signal again to start a new link reset sequence At the same time the value in the PHY RESET PROBLEM field of the Protocol Specific log page page 18 is incremented when synchronization cannot be established at the last negotiated rate 1 3 7 Phy layer dword synchronization...

Page 46: ...ED WAITING ON PARTIAL NoConn I E T single Supported 1 ALIGN 0 ALL I E T I E T single supported supported ALIGN 1 ALL I E T I E T single supported supported ALIGN 2 ALL I E T I E T single supported supported ALIGN 3 ALL I E T I E T single supported supported BREAK ALL I E T I E T redundant supported supported BROADCAST CHANGE NoConn I E I E T redundant supported ignored BROADCAST RESERVED CHANGE 0 ...

Page 47: ...N NoConn E I T single supported supported OPEN_REJECT CONNECTION RATE NOT SUPPORTED NoConn I E T I T single supported supported OPEN_REJECT NO DESTINATION NoConn E I T single supported supported OPEN_REJECT RESERVED INITIALIZE 0 NoConn I T single OPEN_REJECT RESERVED INITIALIZE 1 NoConn I T single OPEN_REJECT PATHWAY BLOCKED NoConn E I T single supported supported OPEN_REJECT RESERVED STOP 0 NoCon...

Page 48: ...upported NAK RESERVED 0 Conn I T single ignored NAK RESERVED 1 Conn I T single ignored NAK RESERVED 2 Conn I T single ignored RRDY NORMAL Conn I T I T single supported supported RRDY RESERVED 0 Conn I T single ignored RRDY RESERVED 1 Conn I T single ignored SOF Conn I T I T single supported supported 1 These primitives are received as AIP primitives 2 When this primitive is received the connection...

Page 49: ...nection request is being processed and specify the status of the connection request A drive performs the following processing when an AIP primitive is received 1 When the drive receives an AIP primitive after sending the OPEN frame the drive initializes the open timer held in the drive and restarts it 2 When the drive receives an AIP primitive before sending the OPEN frame the received AIP primiti...

Page 50: ...received within 1 ms the connection is regarded as having been closed After the BREAK primitive is sent when any primitives and or frames other than the BREAK primitive are received all of these except NOTIFY primitives are discarded When the BREAK primitive is not received within 1 ms of sending the BREAK primitive a drive may start the link reset sequence 1 4 3 4 BROADCAST BROADCASTs are used to...

Page 51: ...receives an invalid dword or an ERROR When a drive receives an ERROR primitive the drive discards it When a received address frame contains the ERROR primitive the whole address frame is discarded even if CRC is correct When a drive receives an SSP frame containing the ERROR primitive the drive discards the whole SSP frame even if CRC is correct and sends the NAK primitive 1 4 3 8 HARD_RESET HARD_...

Page 52: ...eated as the wakeup for the START STOP UNIT command received through SAS TARG port B The NOTIFY RESERVED 0 NOTIFY RESERVED 1 and NOTIFY RESERVED 2 primitives are ignored by all devices 1 4 3 10 OPEN_ACCEPT The OPEN_ACCEPT primitive indicates the acceptance of a connection request The recipient of an OPEN frame must send the OPEN_ACCEPT primitive within 1 ms when it can accept the connection reques...

Page 53: ...itive again the drive cancels the connection request and aborts the TASK command OPEN_REJECT PROTOCOL NOT SUPPORTED Destination phy If the driver receives this OPEN_REJECT primitive it cancels the connection request and aborts the TASK command OPEN_REJECT RESERVED ABANDON 0 Unknown Performs the same processing as the OPEN_REJECT WRONG DESTINATION OPEN_REJECT RESERVED ABANDON 0 Unknown Performs the...

Page 54: ...COUNT field in the OPEN frame OPEN_REJECT RESERVED CONTINUE 0 Unknown Performs the same processing as the OPEN_REJECT RETRY OPEN_REJECT RESERVED CONTINUE 1 Unknown Performs the same processing as the OPEN_REJECT RETRY OPEN_REJECT RESERVED INITIALIZE 0 Unknown Performs the same processing as the OPEN_REJECT NO DESTINATION OPEN_REJECT RESERVED INITIALIZE 1 Unknown Performs the same processing as the...

Page 55: ... from a ninth initiator the drive sends the OPEN_REJECT RETRY primitive 6 A dual port drive may process requests from up to four INITs at a time for each port When a dual port drive holds commands from four INITs for one of its ports and if it receives a connection request from a fifth INIT through the same port the drive sends the OPEN_REJECT RETRY primitive 7 When the drive cannot receive an SSP...

Page 56: ...primitive instead of an RRDY primitive After sending the CREDIT_BLOCKED primitive the drive must wait until the connection is closed before it can send an RRDY primitive Meanwhile when a drive receives the CREDIT_BLOCKED primitive from the initiator the drive performs any of the following processing 1 At the time of the receipt of the CREDIT_BLOCKED primitive if the drive holds credits that have b...

Page 57: ...ve sends an OPEN frame and establishes connection and it becomes that there are no frame to be sent the drive sends the DONE NORMAL primitive 2 When credit timeout is detected before the drive sends an SSP frame the drive sends the DONE CREDIT TIMEOUT primitive 3 When the drive receives the CREDIT_BLOCKED primitive during an inside connection the drive sends the DONE CREDIT TIMEOUT primitive durin...

Page 58: ...detects a CRC error after checking the CRC field in the SSP frame the drive sends the NAK primitive If a received SSP frame contains the ERROR primitive or an invalid dword the drive sends the NAK primitive even if the CRC field in the SSP field is correct 1 4 4 6 RRDY During connection when a drive detects the state where it can receive an SSP frame the drive sends an RRDY primitive to indicate t...

Page 59: ...n needed in an internal buffer this is called an underrun To solve this problem transmitting devices insert ALIGNs or NOTIFYs in the dword stream A phy that is the original source for the dword stream i e a phy that is not an expander phy forwarding dwords from another expander phy shall insert one ALIGN or NOTIFY for clock skew management as described in Table 1 16 Table 1 16 Clock skew managemen...

Page 60: ...the EOAF SSP frame After an SOF all data dwords shall be scrambled until the EOF Inside SSP connection SSP idle dword When there are no other dwords to transmit vendor specific scrambled data dwords shall be transmitted To generate scrambled values that are to be encoded and transferred on the physical link layer dwords to be sent are XOR ed with the predefined pattern If there is no transmission ...

Page 61: ...yte 7 6 5 4 3 2 1 0 0 ADDRESS FRAME TYPE 1 27 Frame Type dependent bytes 28 MSB 31 CRC LSB The ADDRESS FRAME TYPE field indicates the type of the address frame as follows An ADDRESS FRAME TYPE field value of 0 indicates an IDENTIFY address frame An ADDRESS FRAME TYPE field value of 1 indicates an OPEN address frame The CRC field contains the CRC value calculated for all the data of an address fram...

Page 62: ... ADDRESS FRAME TYPE 0h 1 Restricted for OPEN address frame 2 Reserved SSP INITIATOR PORT STP INITIATOR PORT SMP INITIATOR PORT Restricted for Open address frame 3 Reserved SSP TARGET PORT STP TARGET PORT SMP TARGET PORT Restricted for Open address frame 4 11 Restricted for Open address frame 12 19 SAS ADDRESS 20 PHY IDENTIFIYR 21 27 Reserved 28 MSB 31 Reserved LSB The DEVICE TYPE field specifies t...

Page 63: ...es the device name of the expander device transmitting the IDENTIFY address frame The PHY IDENTIFIER field specifies the phy identifier of the phy transmitting the IDENTIFY address frame A wide port shall set the DEVICE TYPE field SSP INITIATOR PORT bit STP INITIATOR PORT bit SMP INITIATOR PORT bit SSP TARGET PORT bit STP TARGET PORT bit and SMP TARGET PORT bit to the same set of values on each ph...

Page 64: ... ADDRESS 12 19 SOURCE SAS ADDRESS 20 COMPATIBLE FEATURES 21 PATHWAY BLOCKED COUNT 22 MSB 23 ARBITRARION WAIT TIME LSB 24 27 MORE COMPATIBLE FEATURES 28 MSB 31 CRC LSB An INITIATOR PORT bit set to one specifies that the source port is acting as a SAS INIT port An INITIATOR PORT bit set to zero specifies that the source port is acting as a SAS TARG port The PROTOCOL field specifies the protocol for ...

Page 65: ...rom the SAS TARG port the INITIATOR CONNECTION TAG field is set to FFFFh If the initiator port requires field support the INITIATOR CONNECTION TAG field should be set to the value that is peculiar to the SAS TARG port When the SAS TARG port issues a connection request to the SAS INIT port the SAS TARG port must set the INITIATOR CONNECTION TAG field to any of the following the last received value ...

Page 66: ...r For values from 0000h to 7FFFh the Arbitration Wait Time timer increments in one microsecond steps For values from 8000h to FFFFh the Arbitration Wait Time timer increments in one millisecond steps The maximum value represents 32767 ms 32768 µs Table 1 24 describes several values of the ARBITRATION WAIT TIME field Table 1 24 ARBITRATION WAIT TIME field Code Description 0000h 0 µs 0001h 1 µs 7FFF...

Page 67: ...h it is attached The combination of a phy reset sequence an optional hard reset sequence and an identification sequence is called a link reset sequence See Section 1 3 2 If a device supports more than one phy it shall transmit the same SAS address on all phys for which it is capable of sharing within a port If a device detects the same SAS address incoming on different phys it shall consider those...

Page 68: ...make a connection request the source port shall transmit an OPEN address frame through an available phy The source phy shall transmit idle dwords after the OPEN address frame until it receives a response or aborts the connection request with BREAK After transmitting an OPEN address frame the source phy shall initialize and start a 1 ms Open Timeout timer Whenever an AIP is received the source phy ...

Page 69: ...imitive or an OPEN_REJECT primitive must be sent If an AIP primitive has not been detected yet this indicates that two connection requests have crossed over the physical link At this time arbitration fairness is used to determine which request should take priority BREAK The destination port or expander port may reply with BREAK indicating the connection is not being established Open Timeout timer ...

Page 70: ...limits the amount of unfairness and helps prevent livelocks The expander port that receives an OPEN address frame shall set the Arbitration Wait Time timer to the value of the incoming ARBITRATION WAIT TIME field and start the Arbitration Wait Time timer as it arbitrates for internal access to the outgoing expander port When the expander device transmits the OPEN address frame out another expander...

Page 71: ... 27 Abort connection responses Response Description BREAK This confirms that the connection request has been aborted Break Timeout timer expires The originating phy shall assume the connection request has been aborted Figure 1 15 shows the sequence for a connection request where the Open Timeout timer expires Open address frame Reset Open Timeout timer AIP Transmit BREAK primitive sequence AIP Tra...

Page 72: ...lose connection responses Response Description CLOSE This confirms that the connection has been closed Close Timeout timer expires The originating phy shall attempt to break the connection Figure 1 16 shows example sequences for closing a connection CLOSE primitive sequence CLOSE primitive sequence time time transmitter receiver CLOSE primitive sequence CLOSE primitive sequence time time transmitt...

Page 73: ...quence In addition to a BREAK a connection is considered broken due to loss of dword synchronization The following shall be the responses by an SSP phy to a broken connection a Received frames having no CRC error may be considered valid regardless of whether an ACK has been transmitted in response to the frame prior to the broken connection b Transmitted frames for which an ACK has been received p...

Page 74: ...ll stop inserting ALIGNs and or NOTIFYs for rate matching after a transmitting the first dword in a CLOSE b transmitting the first dword in a BREAK c receiving an OPEN_REJECT for a connection request or d losing arbitration to a received OPEN address frame 1 5 6 SSP link layer An SSP phy that accepts an OPEN address frame shall transmit at least one RRDY in that connection within 1 ms of transmitt...

Page 75: ...holding RRDY because it needs to transmit a frame itself It may refuse to provide credit for other reasons e g temporary buffer full conditions When the drive sends an OPEN frame and then receives the OPEN_ACCEPT primitive from the initiator due to abort processing in the drive e g when receiving the TASK frame the drive sends the CREDIT_BLOCKED primitive instead of an RRDY primitive In this way t...

Page 76: ... interlocked frames After sending a non interlocked frame an SSP phy may send another non interlocked frame with the same tag if credit is available The SSP phy must not send the following frames until all SSP frames have been acknowledged with ACK or NAK even if credit is available a a non interlocked frame with a different tag or b an interlocked frame Interlocking does not prevent sending and r...

Page 77: ...be inserted in SSP frames sent from the drive are as follows a ACK b NAK c RRDY d CREDIT_BLOCKED Figure 1 17 shows an example of the transfer of interlocked frames Figure 1 18 shows an example of the transfer of non interlocked frames with the same tag Figure 1 19 shows an example of the transfer of non interlocked frames with different tags Interlocked frame Interlocked frame ACK or NAK ACK or NA...

Page 78: ...r NAK ACK or NAK ACK or NAK ACK or NAK ACK or NAK Non interlocked frame tag C Non interlocked frame tag A Non interlocked frame tag A Non interlocked frame tag A Non interlocked frame tag A Non interlocked frame tag A time time transmitter receiver 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 The...

Page 79: ...and receives a CREDIT_BLOCKED it may transmit either DONE NORMAL or DONE CREDIT TIMEOUT After transmitting DONE the transmitting phy initializes and starts a 1 ms DONE Timeout timer After transmitting DONE the transmitting phy shall not transmit any more SSP frames during this connection However the phy may transmit ACK NAK RRDY and CREDIT_BLOCKED as needed after transmitting DONE if the other phy...

Page 80: ... header part information unit part and CRC Table 1 32 SSP frame format Bit Byte 7 6 5 4 3 2 1 0 0 FRAME TYPE 1 MSB 3 HASHED DESTINATION SAS ADDRESS LSB 4 Reserved 5 MSB 7 HASHED SOURCE SAS ADDRESS LSB 8 Reserved 9 Reserved 10 Reserved RETRY DATA FRAMES RETRA NSMIT CHANGING DATA POINTER 11 Reserved NUMBER OF FILL BYTES 12 Reserved 13 15 Reserved 16 MSB 17 TAG LSB 18 MSB 19 TARGET PORT TRANSFER TAG ...

Page 81: ...to one this bit specifies that the SSP INIT port may retry write DATA frames that fail The RETRANSMIT bit is set to one for TASK frames RESPONSE frames and XFER_RDY frames and shall be set to zero for all other frame types This bit specifies that the frame is a retransmission after the SSP port failed in its previous attempt to transmit the frame The CHANGING DATA POINTER bit is set to one for DAT...

Page 82: ...data context when receiving a write DATA frame i e determine the command to which the write data corresonds SSP TARG ports may set the TARGET PORT TRANSFER TAG field to any value when transmitting any SSP frame SSP TARG ports that use this field should set the TARGET PORT TRANSFER TAG field in every XFER_RDY frame to a value that is unique for the L_Q portion of the I_T_L_Q nexus i e that is uniqu...

Page 83: ...ines the command IU The COMMAND frame is sent by an SSP INIT port to request that a command be processed by the device server in a logical unit Table 1 34 COMMAND information unit Bit Byte 7 6 5 4 3 2 1 0 0 MSB 7 LOGICAL UNIT NUMBER LSB 8 Reserved 9 ENABLE FIRST BURST Reserved TASK ATTRIBUTE 10 Resered 11 ADDITIONAL CDB LENGTH n dwords Reserved 12 MSB 27 CDB LSB 28 27 n x 4 ADDITIONAL CDB BYTES Th...

Page 84: ... byte long COMMAND frame The CDB and ADDITIONAL CDB BYTES fields together contain the CDB to be interpreted by the addressed logical unit The contents of the CDB are defined in the SCSI command standards e g SPC 3 When a drive receives a COMMAND frame the following items are checked HASHED DESTINATION SAS ADDRESS field When this field contains a value different from the Hashed SAS address of the d...

Page 85: ...drive receives a command when the queue is full the drive sends the ACK primitive to temporarily close the connection Then after re establishing a connection the drive reports the QUEUE FULL status LOGICAL UNIT NUMBER field TASK ATTRIBUTE field CDB field Refer to Chapter 2 Command Processing and Chapter 4 Command Specification Reserved field The drive ignores the Reserved fields except the CDB fie...

Page 86: ...a logical unit Table 1 36 TASK information unit Bit Byte 7 6 5 4 3 2 1 0 0 MSB 7 LOGICAL UNIT NUMBER LSB 8 Reserved 9 Reserved 10 TASK MANAGEMENT FUNCTION 11 Reserved 12 MSB 13 TAG OF TASK TO BE MANAGED LSB 14 27 Reserved The LOGICAL UNIT NUMBER field contains the address of the logical unit Table 1 37 contains the definition of the TASK MANAGEMENT FUNCTION field However drives do not support the ...

Page 87: ...rts TASK MANAGEMENT FUNCTION SUCCEEDED When not maintaining a task that matches with respect to I T L Q reports TASK MANAGEMENT FUNCTION COMPLETE All others Reserved If TASK MANAGEMENT FUNCTION is set to ABORT TASK or QUERY TASK the TAG OF TASK TO BE MANAGED field specifies the TAG value from the COMMAND frame that contained the task to be aborted or checked For all other task management functions...

Page 88: ...SK SET LOGICAL UNIT RESET or QUERY TASK the drive sets the response code to TASK MANAGEMENT FUNCTION NOT SUPPORTED 0x04 and sends the RESPONSE frame of RESPONSE DATA 1 6 2 3 XFER_RDY information unit Table 1 38 defines the transfer ready IU The XFER_RDY frame is sent by an SSP TARG port to request write data from the SSP INIT port Table 1 38 XFER_RDY information unit Bit Byte 7 6 5 4 3 2 1 0 0 MSB...

Page 89: ...ord multiple write data length When the drive sends a XFER_RDY 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 Always set to zero TAG field The tag value of the COMMAND frame is set TARGET PORT TRANSFER TAG field The drive ...

Page 90: ...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 Figure 1 21 shows an example case where multiple XFER_RDY frames are sent Figure 1 21 Example of XFER_RDY frames ...

Page 91: ...lue in the MAXIMUM BURST SIZE field on the Disconnect Reconnect mode page is not zero the maximum amount of data that is transferred at one time by an SSP TARG port per I_T_L_Q nexus is limited by the value in the MAXIMUM BURST SIZE field Drives do not support the MAXIMUM BURST SIZE field However the maximum data amount a drive can request with a single XFER_RDY frame is limited to 64 Kbytes An SS...

Page 92: ...ifferent from the SOURCE SAS ADDRESS field of the OPEN frame the drive sends the CREDIT_BLOCKED primitive and discards the DATA frame CRC field When a CRC error is detected the drive sends the NAK primitive and discards the DATA frame At this time the SENSE DATA for INFORMATION UNIT iuCRC ERROR DETECTED is reported Frame length When the IU length is greater than 1024 bytes the drive discards the D...

Page 93: ...while when a drive sends a read DATA 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 If the transferred bytes in the last DATA frame for the command are not aligned on a four byte boundary the number of the extra bytes 4 th...

Page 94: ...12 15 Reserved 16 MSB 19 SENSE DATA LENGTH n bytes LSB 20 MSB 23 REPONSE DATA LENGTH m bytes LSB 24 RESPONSE DATA DATAPRES 01h 23 m 24 m SENSE DATA DATAPRES 10b 23 m n Table 1 42 defines the DATAPRES field Table 1 42 DATAPRES field Code Name Description 00b NO_DATA The SENSE DATA LENGTH field is zero and the RESPONSE DATA LENGTH is zero 01b RESPONSE_DATA The SENSE DATA LENGTH field is zero and the...

Page 95: ...o and the RESPONSE DATA LENGTH field to zero c the SSP TARG port shall not include the SENSE DATA field and the RESPONSE DATA field RESPONSE information unit RESPONSE_DATA format If the DATAPRES field is set to RESPONSE_DATA then a the SSP TARG port shall set the STATUS field to zero and the SENSE DATA LENGTH field to zero b the SSP TARG port shall not include the SENSE DATA field c the SSP TARG p...

Page 96: ...NOT SUPPORTED 05h TASK MANAGEMENT FUNCTION FAILED 08h TASK MANAGEMENT FUNCTION SUCCEEDED 09h INVAILD LOGICAL UNIT NUMBER All others Reserved RESPONSE information unit SENSE_DATA format If the DATAPRES field is set to SENSE_DATA then a The STATUS field contains the status code for a command whose processing has ended b The RESPONSE DATA LENGTH field is set to zero c No RESPONSE DATA field exists d ...

Page 97: ...e sends a RESPONSE frame the drive resends the RESPONSE frame with this bit set to 1 TAG field The tag value of the COMMAND frame is set TARGET PORT TRANSFER TAG field This field is set to 0xFFFF by the drive DATA OFFSET field Set to zero DATAPRES field Refer to Table 1 44 STATUS field The SCSI status byte is set see Chapter 2 SENSE DATA LENGTH field When sense data is sent this field is set to 0x...

Page 98: ...n any order when multiple commands and or task management functions are outstanding Frames may be transmitted during one or more connections e g the COMMAND frame could be transmitted in a connection originated by the SSP INIT port and the DATA frames and RESPONSE frame transmitted in one or more connections originated by the SSP TARG port Figure 1 22 shows the sequence of SSP frames for a task ma...

Page 99: ...er C141 C009 1 77 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 ...

Page 100: ...Serial Attached SCSI SAS Interface 1 78 C141 C009 Figure 1 25 shows the sequence of SSP frames for a bidirectional command Figure 1 25 Example of bidirectional command ...

Page 101: ...tional event occurs the CREDIT_BLOCKED primitive instead of an RRDY primitive is sent to stop SSP frames from the initiator 2 The connection is temporarily closed 3 The recovery processing for the exceptional event abort processing is started 4 If the recovery processing has not been completed the OPEN_REJECT RETRY primitive is sent in response to the connection request from the initiator 5 After ...

Page 102: ...tached SCSI SAS Interface 1 80 C141 C009 Figure 1 26 shows an example of the processing sequence a drive performs for an exceptional event Figure 1 26 Example of the processing sequence for an exceptional event ...

Page 103: ...EMENT FUNCTION SUCCEEDED TASK frame CLEAR ACA Reports TASK MANAGEMENT FUNCTION NOT SUPPORTED TASK management TASK frame LUN 0 Reports INVALID LOGICAL UNIT NUMBER Overlapped TAG Reports for TAGGED OVERLAPPED COMMANDS 0B 4D nn or 0B 4E 00 Queue full Reports the QUEUE FULL status DATA OFFSET error Reports for DATA OFFSET ERROR 0B 4B 05 DATA overrun Reports for TOO MUCH WRITE DATA 0B 4B 02 DATA frame ...

Page 104: ...orts for NAK RECEIVED 0B 4B 04 Transmitting system Buffer CRC error in DATA frame sending Reports for ERROR TOO LONG TO CORRECT 03 11 02 When Check Status is reported with the setting of Qerr 01 Reports and aborts all the commands in the Queue When Check Status is reported with the setting of Qerr 10 Reports and aborts all the commands in the Queue When Preemp Abort is ServiceAction at Persistent ...

Page 105: ...particularly clear distinction is necessary 2 1 Command Format Input Output commands from the INIT Initiator to the IDD are executed by the CDB Command Descriptor Block The CDB is information which is transmitted from the INIT to the TARG in the CMND frame In a number of commands other than the CDB specifications parameters which are necessary in executing a command are specified in the DATA frame...

Page 106: ... Address 3 Logical Block Address LSB 4 Transfer Data Length 5 Control Byte Table 2 2 10 Byte CDB basic format Bit Byte 7 6 5 4 3 2 1 0 0 Operation Code 1 Reserved 0 0 0 0 0 2 Logical Block Address MSB 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address LSB 6 0 0 0 0 0 0 0 0 7 Transfer Data Length MSB 8 Transfer Data Length LSB 9 Control Byte ...

Page 107: ...d below Depending on the type of command the basic format of the CDB and the definition and meaning of a field may differ Details are described in the specifications for individual commands in Chapter 4 1 Operation code Table 2 4 Operation code Bit 7 6 5 4 3 2 1 0 Group Code Command Code The top byte of all CDBs shows the format and type of command that is being executed a Group code The group cod...

Page 108: ...a blocks or the number of bytes In subsequent descriptions the former is called the Number of Transfer Blocks and the latter is called the Transfer Byte Length or the Parameter List Length Furthermore depending on the command use of this field can have other meanings or no meaning at all There are also some commands which allocate 3 or more bytes as the transfer data length field Detailed standard...

Page 109: ...ormation The IDD transfers either the number of effective bytes of information specified by the command or the value specified in the Transfer Byte Length whichever value has the smaller number of bytes 4 Control byte Table 2 5 Control byte Bit 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 a Bits 7 6 vendor unique When any value other than 0 is specified for these bits the IDD terminates command processing with...

Page 110: ...Table 2 6 Status Status code Status 00h GOOD Status 02h CHECK CONDITION Status 04h CONDITION MET Status 08h BUSY Status 10h INTERMEDIATE Status 14h INTERMEDIATE CONDITION MET Status 18h RESERVATION CONFLICT Status 22h COMMAND TERMINATED Status 28h TASK SET FULL Status 1 GOOD status This status indicates that execution of the command ended normally 2 CHECK CONDITION status This status is reported i...

Page 111: ...DD reports the BUSY status when the WRITE BUFFER command is issued to download a microcode while the IDD has commands in its command queue that have not been executed yet 5 INTERMEDIATE status Not supported 6 INTERMEDIATE CONDITION MET Status Not supported 7 RESERVATION CONFLICT status This status indicates that the IDD is currently reserved by another INIT and use is impossible until the reservat...

Page 112: ...nd received with ORDERED specified are regardless of the INIT executed before the command received with ORDERED specified All the commands received with SIMPLE specified after a command received with ORDERED specified are executed after the command received with ORDERED specified Commands received with a HEAD OF QUEUE are registered at the top of the queue for waiting execution The IDD does not in...

Page 113: ... Condition The Unit Attention condition is a function for notifying the INIT asynchronously of events status changes which occur in the TARG or logical unit 2 4 1 Generation of the UNIT ATTENTION condition Events which cause the Unit Attention condition to be generated are any of the following events 1 When a Power On or RESET occurs If the IDD is reset by a power on HARD RESET or LOGICAL UNIT RES...

Page 114: ... the Unit Attention condition if it receives a command from an INIT which is the object of the hold one of the operations below depending on the type of command issued is performed by the IDD 1 Commands other than the INQUIRY REQUEST SENSE and REPORT LUNS commands The IDD reports the CHECK CONDITION status in response to the issued command Through the CHECK CONDITION status report the Unit Attenti...

Page 115: ...other Unit Attention condition occurs which is caused by other factors before the first Unit Attention condition is cleared by the INIT for which that condition is held those multiple Unit Attention conditions are held and the IDD reports multiple unit attention conditions in sequence 2 5 Sense Data Hold State If the status is the Check Condition status when the status is reported this IDD adds th...

Page 116: ...n the IDD receives NOTIFY ENABLE SPINUP it starts the motor The IDD enters the Active state after the motor is successfully started When the IDD receives a command that cannot be executed due to not ready while starting the motor the IDD reports the CHECK CONDITION status In this case NOT READY 02 LOGICAL UNIT IS IN PROCESS OF BECOMING READY 04 01 is reported as sense data When the IDD receives th...

Page 117: ... STOP UNIT command RESERVE or RESERVE EXTENDED command RELEASE or RELEASE EXTENDED command WRITE BUFFER command READ BUFFER command INQUIRY command REQUEST SENSE command When the IDD is in the sense data holding state and the REQUEST SENSE command is executed normally the IDD sends the sense data held at this time to the INIT When the IDD is not in the sense data holding state the IDD sends sense ...

Page 118: ...opped 1 Flashes in 0 5 s intervals Formatting in progress 1 Flashes in 1 0 s intervals 1 These display items take priority over display items caused by power conditions Even if a command is received while Motor being started or stopped or Formatting in progress is displayed the LED display stays unchanged 2 8 Command Processing Exceptions 2 8 1 Overlapping commands The IDD recognizes that commands...

Page 119: ...applicable without dependence on the type of command that was issued second For example even if the command that was issued second is an INQUIRY or REQUEST SENSE command the IDD reports the CHECK CONDITION status and terminates both commands abnormally 2 8 2 Illegal LUN specification The IDD supports only the logical unit number LUN LUN 0 If a LUN other than this is specified the IDD operates in o...

Page 120: ...xecuted by the IDD is shown below 1 Recovery procedures for disk drive errors The IDD executes error recovery processing like that shown in Table 2 8 for errors detected during data access on the disk medium Caution is necessary when performing these recovery processing procedures because they are accompanied by rotational delays for repositioning data blocks on the disk medium or by added command...

Page 121: ...s completed 2 8 5 Abort processing Abort measures which can be performed by the INIT are as shown below HARD RESET LOGICAL UNIT RESET CLEAR TASK SET ABORT TASK SET ABORT TASK Table 2 9 Comparison between SAS and SCSI about definition Definition by SAS Definition by SCSI HARD RESET Comparable to SRST LOGICAL UNIT RESET Bus Device Reset Message CLEAR TASK SET Clear Task Set Message ABORT TASK SET Ab...

Page 122: ... L nexus commands specified by an INIT Environment settings and conditions such as MODE SELECT parameters that have been specified in advance are not changed After this task is performed the unit attention condition for Command Cleared by Another INIT 06 2F 00 is generated for the INITs whose commands have been subject to abortion except for the INIT that has issued this task 4 ABORT TASK SET ABOR...

Page 123: ...necessary for the INIT to reissue the command REASSIGN BLOCKS At the point when processing of alternate blocks which are currently being assigned is completed execution of the command is halted Not all the alternate blocks specified for reassignment processing by the INIT will necessarily have been processed MODE SELECT MODE SELECT EXTENDED LOG SENSE Specifying parameter save If a parameter save o...

Page 124: ...s during execution of a command and termination processing such as a CHECK CONDITION status report cannot be executed the IDD may halt rotation of the spindle motor After this state occurs the IDD reports the CHECK CONDITION status for all input output operation requests except the REQUEST SENSE command The sense data reported at this time indicate HARDWARE ERROR 4 Internal target failure 44 nn Fo...

Page 125: ...tors on the disk medium through IDD internal defect management data blocks for replacement are assigned in defective sector units Through this defect management the INIT can regard all the logical data blocks in the user space as error free and can access them For details concerning the data format on the disk medium cylinder configuration track format and sector format as well as details on defec...

Page 126: ... x 1 Zone 1 Cell 0 Cell Cell n 1 Cell Track 0 Track m 1 Track 1 Cylinder a 1 Cylinder 0 Cylinder 0 Cylinder 0 Track 0 Alternate cell b tracks c cylinders Last cylinder d 1 Last cylinder Alternate cylinder User space System space Figure 2 1 Data space configuration ...

Page 127: ...logical data blocks are allocated to sector numbers in ascending order 2 Within the same head of the same cell succeeding logical data blocks are allocated to the sectors in each track according to 1 in the ascending order of cylinder numbers 3 Within the next head of the same cell succeeding logical data blocks are allocated to the sectors in each track according to 1 and 2 in the ascending order...

Page 128: ...This page is intentionally left blank ...

Page 129: ... with one port allocated for transfers with the disk media and the other port for data transfers with the interface INIT Mutual ports operate asynchronously and since it is possible to efficiently absorb variations in data transfer speed between the ports the INIT can perform data transfer operations with the IDD while being virtually unaware of differences between the interface data transfer rate...

Page 130: ...k has been located the IDD reads the data form the disk media to the data buffer At this time if a recoverable error is detected the IDD performs error recovery processing according to the specification in the MODE SELECT parameter or corrects the data in the data buffer 3 When the IDD has read out to the data buffer the amount of data that the IDD itself has specified it performs reconnection pro...

Page 131: ...a buffer to the disk media If the target data block location operation is completed during the data pre fetch processing in 1 writing of data to the disk media is performed in parallel with the data pre fetch to the data buffer 3 If the data transfer speed of the INIT is lower than the data transfer speed of the disk drive since the data pre fetch of data that are to be written to that data block ...

Page 132: ...liminated and effective access time greatly reduced An INIT can prohibit the operation of this Look Ahead cache feature by setting the caching parameter described in section 3 2 2 1 Caching object commands Commands which execute caching operations are the commands shown below READ READ EXTENDED If all the data blocks which are objects of the processing specified in these commands or a portion of t...

Page 133: ...E and WRITE EXTENDED command are objects of caching d Data transferred from the INIT and written to the disk media by WRITE AND VERIFY command is not the objects of caching 3 Disabling caching data Various data which are objects of caching in the data buffer are disabled in the following cases a If any of the following commands is issued for the same data block as data which are the object of cach...

Page 134: ...XTENDED WRITE WRITE EXTENDED WRITE AND VERIFY VERIFY d If any of the following events occurs all the data which are objects of caching are disabled Receiving HARD RESET primitive Receiving ABORT TASK TASK IU 0x01 Receiving ABORT TASK SET TASK IU 0x02 Receiving CLEAR TASK SET TASK IU 0x04 Automatic alternate processing is executed Read Write is aborted in something causes 3 2 2 Caching parameters T...

Page 135: ...d operation is halted at the point when reading of the specified amount of data at the minimum pre fetch volume is completed then execution of the new command starts When there are no commands that need to be newly executed the data look ahead operation is continued even after the volume of data specified as the minimum amount of pre fetch data have been read until one of the following conditions ...

Page 136: ...This page is intentionally left blank ...

Page 137: ... UNIT READY 00 Bit Byte 7 6 5 4 3 2 1 0 0 X 00 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 This command checks the status of the disk drive If the IDD is in the ready state and it is possible for it to be used by the INIT initiator which issues this command a GOOD status is reported for this command If the IDD is not in the ready state it reports a CHE...

Page 138: ...IT ATTENTION condition is not cleared This command is also executed normally when the disk drive is not in the ready state A CHECK CONDITION status is reported for this command and it is terminated abnormally only in the case that one of the following conditions is detected There is an error in the specifications of the CDB It is impossible to send INQUIRY data because of an IDD hardware error App...

Page 139: ...he VPD information b If the EVPD bit is zero and the CmdDt bits is one this field specifies the operation code CDB byte 0 of commands generated command supported data 4 Transfer Byte Length Byte 4 of the CDB the Transfer Byte Length field shows the number of bytes of standard INQUIRY data or VPD information that the application client can receive by this command The IDD transfers data with the byt...

Page 140: ... Data Length 4 0 1 0 1 1 0 1 1 5 SCCS Reserved 0 0 0 0 0 0 0 0 SCSI 3 6 BQue EncServ Part MultiP MCHNGR Obsolete Addr16 SCSI 3 0 0 0 1 0 1 0 0 0 0 7 RelAdr obsolute Wbus16 Sync Linked TranDis CmdQue VS SCSI 3 0 0 0 0 0 0 1 0 8 9 15 FUJITSU Vendor ID ASCII 16 17 31 Product ID ASCII 32 33 34 35 Microcode Version No ASCII Product Revision ASCII 36 37 47 Device Serial No ASCII 48 55 X 00 Vendor Specif...

Page 141: ...eport this code 0 1 1 Shows that the specified logical unit is not supported When this code is reported it X 1F is shown in the Device Type Code field b Device type code 0 0 0 0 0 Direct access device 1 1 1 1 1 Undefined device c RMB bit When this bit is 1 it indicates that the storage media is a removable disk device The IDD is a fixed disk device so this bit is always reported as 0 d Version The...

Page 142: ...elow are the functions which the IDD supports are shown in the bit correspondence 1 indicates that that function is supported and 0 indicates that that function is not supported Byte 3 AERC Asynchronous event reporting capability Asynchronous condition notify function 0 NORMACA Normal ACA supported ACA support 0 HISUP Hierarchical support Defined the hierarchical addressing model to assign LUN 0 B...

Page 143: ...s of task tags supported 1 0 Basic task set model supported 1 1 Illegal combination of BQue and CmdQue bits VS Vendor specific Not defined 0 h 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 i Product ID field The product s model name is displayed in left justified ASC...

Page 144: ...d This field is provided for identifying upto eight standards to which the Device claims conformance The IDD shall be indicated as shown below Table 4 4 Version descriptor BYTE Code Description 58 to 59 OX00 OX40 SAM2 60 to 61 OX0B OXFC SAS 62 to 63 OX01 OX3C SPC ANSI 3 301 1997 64 to 65 OX01 OX9B SBC T10 0996 D rev08C 66 to 67 OX00 OX00 68 to 69 OX00 OX00 70 to 71 OX00 OX00 72 to 73 OX00 OX00 ...

Page 145: ...bit and 1 is specified in the CmdDt bit Table 4 5 Command support data Bit Byte 7 6 5 4 3 2 1 0 0 Qualifier Device Type Code 1 0 0 0 0 0 Support 2 Version 3 X 00 Reserved 4 X 00 Reserved 5 CDB Size m 5 6 m CDB Usage Data a Qualifier Device Type Code Version These fields are the same as those in the previously mentioned standard INQUIRY data b Support This field indicates the value defined in Table...

Page 146: ... for the operation code being queried and the size of the CDB Usage Data field in the return data d CDB usage data This field contains information about the CDB for the operation code being queried The first byte of the CDB usage data contains the operation code for the operation being queried All bytes except the first byte of the CDB usage data contains a usage map for bits in the CDB for the op...

Page 147: ...on C0 Operation mode Furthermore if page codes other than those shown above VPD information that is not supported by the IDD are specified in the CDB that command is terminated with a CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in CBD 24 00 The format and contents of each type of VPD information are shown below a Page code list This VPD information reports the page code list of VPD info...

Page 148: ...ice serial No This VPD information reports the device serial number of the IDD The format of this VPD information is shown in Table 4 9 Table 4 9 VPD information device serial No Bit Byte 7 6 5 4 3 2 1 0 0 Qualifier Device Type Code 1 X 80 Page Code 2 X 00 3 X 0C Page Length 4 5 Device Serial No ASCII 15 The values indicated in the Qualifier and Device Type Code fields in byte 0 are the same as th...

Page 149: ... 4 Protocol Identifier 0110b Code set 0001b 5 PIV 1b Reserv 0 b Association 00b Identifier type 0011 b 6 Reserved x 00 7 Identifier length x 08 8 LSB Identifier ID 15 LSB Protocol Identifier 6h Indicates that this page conforms to the SAS SCSI device specifications Code Set Indicates the type of the code shown in the Identifier ID field 0 and 3 Fh Reserved 1h The Identifier is a binary code 2h The...

Page 150: ...tion indicated in the Vendor ID Fujitsu recommends indicating the Product ID of the Standard INQUIRY followed by the serial number of VPD Page 80 2h Indicates a sixty four bit long IEEE extended unique ID EUI 64 This information includes a 48 bit long IEEE ID 3h FC PH FC PH3 or FC FS Name Identifier the rest is omitted 4h Used when Association is 1h the rest is omitted 5 Fh Reserved Identifier len...

Page 151: ... in byte 3 indicates the length byte length after byte 4 This value has no relationship to the specification in the Transfer Byte Length in the CDB but indicates the length of this VPD information and is always X 04 Total data length 8 bytes UNTATN UNIT ATTENTION Report Mode When the IDD is holding the Unit Attention condition this specifies methods of response to commands received from the INIT 1...

Page 152: ...is 1 the logical block address and block length byte length of data blocks which satisfy either of the following conditions is transferred to the INIT The data block on the track where the specified block exists which is just before the block where the first alternate sector processing not including defective block sector slip processing is implemented However when alternate sector processing is b...

Page 153: ...orms setting and changing of each type of parameter related to disk drive physical attributes data format timing of FC interface transferring processing and error recovery procedures etc 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 by using the MODE SENSE or MODE SENSE EXTENDED ...

Page 154: ...gth 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 The MODE SELECT parameters have specifically defined formats and lengths as explained by the descriptions of each page descriptor in this item and the INIT must always specify transfer t...

Page 155: ...lation between the three types of parameters Current Save and Default Block descriptor Pages 3 4 Remark When the drive is shipped from the factory there are not parameter page Save values except for Page 3 Format Parameters and Page 4 Drive Parameters Save values for the parameter pages specified in the MODE SELECT command are generated for the first time when that command is executed with 1 speci...

Page 156: ...description of each page descriptor in this item If the IDD performs rounding processing rounding up or rounding down of parameter values specified by the INIT in some cases a CHECK CONDITION status RECOVERED ERROR 1 Rounded parameter 37 00 is reported and in some cases it is not reported Whether or not the CHECK CONDITION status is reported depends on whether rounding up or rounding down is speci...

Page 157: ...pe 2 0 0 0 0 0 0 3 X 00 or X 08 Product Descriptor Length Block Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 Data Block Count MSB 1 Data Block Count 2 Data Block Count 3 Data Block Count LSB 4 X 00 5 Data Block Length MSB 6 Data Block Length 7 Data Block Length LSB Page Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 0 0 Page Code 1 Page Length 2 n Page Header Parameter Field ...

Page 158: ...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 The maximum logical block address is a value with 1 subtracted from the value in this field If only the Block descriptor in this command is changed accessible d...

Page 159: ...ied in a unit called a Page The individual Page descriptors in the MODE SELECT and MODE SELECT EXTENDED commands may be specified independently by the INIT and multiple Page descriptors may be specified continuously in the desired sequence Page code This field specifies a code Page No that indicates the type of Page descriptor SPF Sub Page Format When this bit is set to 0 this indicates that the P...

Page 160: ...the MODE SELECT parameters transferred in the command are disabled Table 4 14 MODE SELECT parameters Parameter Byte Length Header 4 Block Descriptor 8 or 0 Page Descriptor Page 1 Read Write Error Recovery Parameter 12 Page 2 Disconnect Reconnect Parameter 16 Page 3 Format Parameter 24 Page 4 Drive Parameter 24 Page 7 Verify Error Recovery Parameter 12 Page 8 Caching Parameter 20 Page A Control Mod...

Page 161: ...or not they can be changed 2 After changing anything in the Block descriptor Format parameters Page 3 or Drive parameters Page 4 with the MODE SELECT or MODE SELECT EXTENDED command it is impossible to execute a command to access the data on the disk media until execution of the FORMAT UNIT command is completed and a CHECK CONDITION status MEDIUM ERROR 3 Medium format corrupted 31 00 is reported f...

Page 162: ... 1 0 0 0 0 0 0 0 0 0 1 1 X 0A Page Length 2 AWRE ARRE TB RC ERR PER DTE DCR Default 1 1 0 0 1 0 0 0 Variable 1 1 1 1 1 1 1 1 3 Number of retries during READ Default X 3F Variable X FF 4 Correctable Bit Length Default X FF Variable X 00 5 X 00 Head Offset Count 6 X 00 Data Strobe Offset Count 7 X 00 Reserved 8 Number of retries during WRITE Default X 3F Variable X FF 9 X 00 Reserved 10 11 Recovery ...

Page 163: ...rocessing operation is specified during execution of a write operation 0 An automatic alternate block allocation processing operation is prohibited during execution of a write operation Automatic alternate block allocation processing is explained in Section 5 3 2 b ARRE automatic read reallocation enable 1 An automatic alternate block allocation processing operation is specified during execution o...

Page 164: ...possible The IDD disregards this bit and operates according to the default value 1 f PER post error 1 When several errors errors related to the disk drive which were recovered from normally through the IDD s error recovery processing have been detected a CHECK CONDITION status is reported when execution of that command is completed In the sense data generated at this time the sense key indicates R...

Page 165: ...executed the number specified here plus the number of internal retries The value specified in this parameter is applicable to the READ READ EXTENDED commands and the read test in the SEND DIAGNOSTIC command When the page length in Page 1 is specified as X 06 the value specified in this field is copied to the Number of retries during WRITE on this page and Number of retries during VERIFY on Page 7 ...

Page 166: ...ch logical block unit When zero is specified in this field retrying of writing to the disk is prohibited The value specified in this field is applicable to the WRITE command WRITE EXTENDED command write operation in the WRITE AND VERIFY command and write test in the SEND DIAGNOSTIC command When the page length in Page 1 is specified as X 06 the value specified in this field is not transferred from...

Page 167: ...are not reported 4 If unrecoverable errors have been detected execution of that command is terminated at that point 5 Transfer of data in blocks which include unrecoverable errors to the INIT is done in accordance with the specification in the TB bit read commands 0 0 1 0 Setting prohibited See 1 at the end of this table 0 0 1 1 Setting prohibited See 1 at the end of this table 0 1 0 0 1 Rereading...

Page 168: ... Verify Retry Count parameter If possible data correction is executed afterward according to the ECC 2 When error recovery has succeeded or even when recovery is impossible execution of the command is terminated with a CHECK CONDITION status at the point when error recovery processing is completed and the sense data indicate the data block address where that error occurred 3 Transfer to the INIT o...

Page 169: ...ited See 1 at the end of this table 1 1 0 0 1 When a correctable data check is detected immediately correction is executed according to the ECC For data checks which cannot be corrected rereading is tried repeatedly up to the number of times specified in the Read Retry Count Write Retry Count or Verify Retry Count parameter However if a correctable error is detected during reading data correction ...

Page 170: ...ssing is completed and the sense data indicate the data block address where that error occurred 3 Transfer to the INIT of data in blocks with recovered errors is done but transfer to the INIT of data blocks in which the errors were unrecoverable is done in accordance with the specification in the TB bit read commands 1 1 1 1 Setting prohibited See 1 at the end of this table 1 If a setting prohibit...

Page 171: ...lt X 0000 Variable X 0000 6 7 X 0000 8 9 Connect Time Limit Default X 0000 Variable X 0000 10 11 Maximum Burst Size Default X 0000 Variable X 0000 12 X 00 13 X 00 14 15 Burst Size During the Initialize Connection Default X 0000 Variable X 0000 a Bus inactivity ratio This parameter specifies the maximum period of time from the time of OPEN processing for the address frame during which the TARG exec...

Page 172: ...rs in the data frames between the OPEN processing for the address frame and the execution of the DONE CLOSE primitive as a multiple of 512 bytes The IDD ignores the value specified for this parameter d Burst size during the initial connection When the ENABLE FIRST BURST bit of the command frame is set to 1 this parameter specifies the maximum number of write data bytes that an INIT can transfer wi...

Page 173: ...6 MAUxxxx or X T B D MAUxxxx Variable X FFFF 6 7 Alternate Track Count Zone Default X 0000 Variable X 0000 8 9 Alternate Track Count Drive Default X xxxx Variable X 0000 10 11 Sector Count Track Default X xxxx Variable X 0000 12 13 Data Byte Length Physical Sector Default X xxxx Variable X FFFF 14 15 Interleave Factor Default X 0001 Variable X 0000 16 17 Track Skew Factor Default X xxxx Variable X...

Page 174: ...the number of spare sectors secured in each cell It is possible for the INIT to vary this parameter within a range of 0 to the maximum permissible value When a value which exceeds the maximum permissible value is specified the IDD performs rounding down of the parameter and sets a value equal to this parameter s maximum permissible value If the above rounding processing is performed a CHECK CONDIT...

Page 175: ...g and sets a byte length of 528 If an odd number of bytes is specified within the specified range the IDD performs rounding up processing If the above rounding processing is performed the IDD reports the CHECK CONDITION status RECOVERED ERROR 1 Rounded parameter 37 00 for that command If 0 is specified in this parameter the value calculated based on the value of the Data block length in the block ...

Page 176: ... disk media is soft sectoring However since the IDD uses only the hard sectoring method refer to previously shown item b this bit is disregarded Furthermore it is impossible to change this parameter HSEC hard sectoring When this bit is 1 it indicates that the data formatting method on the disk media is hard sectoring However since the IDD uses only the hard sectoring method this bit is disregarded...

Page 177: ... xx Variable X 00 6 8 Write Precompensation Starting Cylinder Default X 000000 Variable X 000000 9 11 Reduced Write Current Starting Cylinder Default X 000000 Variable X 000000 12 13 Drive Step Rate Default X 0000 Variable X 0000 14 16 Landing Zone Cylinder Default X 000000 Variable X 000000 17 0 0 0 0 0 0 RPL Default 0 0 0 0 0 0 0 0 Variable 0 0 0 0 0 0 0 0 18 Rotational Synchronization Offset De...

Page 178: ... is the same as the default value in it c Bytes 6 to 16 The parameter defined in bytes 6 to 16 of this page descriptor is a parameter that it is clearly not necessary for the INIT to specify The IDD disregards the values specified in this field d RPL rotational position locking These bits are used for rotational synchronization of the disk and can be specified The IDD disregards the value specifie...

Page 179: ... 1 0 0 0 0 0 0 0 1 1 1 1 X 0A Page Length 2 Reserved EER PER DTE DCR Default 0 0 0 0 1 0 0 0 Variable 0 0 0 0 1 1 1 1 3 Number of retries during VERIFY Default X 3F Variable X FF 4 Correctable Bit Length Default X FF Variable X 00 5 9 X 0000000000 Reserved 10 11 Recovery Time Limit Default X 7530 Variable X FFFF The error recovery parameters divided in this page descriptor are applicable for the f...

Page 180: ...specified in this field retrying to read data from the disk is prohibited c Correctable bit length This parameter indicates the burst error length bit length that can be applied for data corrections according to the ECC This parameter cannot be changed by the INIT However the IDD disregards the value specified in this parameter and operations according to the Default value d Recovery time limit Th...

Page 181: ...y Write Retention Priority Default 1 0 0 0 0 0 0 0 Variable 0 0 0 0 0 0 0 0 4 5 Pre fetch inhibit block count Default X FFFF Variable X 0000 6 7 Minimum pre fetch Default X 0000 Variable X 0000 8 9 Maximum pre fetch Default X xxxx Variable X 0000 10 11 Maximum pre fetch limit block count Default X FFFF Variable X 0000 12 FSW LBCSS DRA VS VS Reserved Default 1 0 0 0 0 0 0 0 Variable 0 0 0 0 0 0 0 0...

Page 182: ... READ EXTENDED command exists in the data buffer the IDD transfers that data without accessing the disk Also depending on the instructions for the bytes beyond byte 4 of the parameter page it reads ahead the data blocks after the requested data in the data buffer b MS multiple selection This bit specifies how to specify the minimum prefetch count bytes 6 and 7 and maximum prefetch count bytes 8 an...

Page 183: ...it and operates according to the Default value 0 e DISC discontinuity 1 Even if a track switch occurs during Look Ahead the Look Ahead operation continues without interruption 0 Look Ahead is terminated at the point where track switch occurs during Look Ahead This bit cannot be changed The IDD disregards the specification in this bit and operates according to the Default value 1 f IC initiator con...

Page 184: ...parameter is used to selectively prohibit data Look Ahead operations in the READ command or the READ EXTENDED command When the Transfer block count specified in the CDB of the READ command or the READ EXTENDED command is greater than the value in this parameter data Look Ahead operations are not executed in that command This bit cannot be changed The IDD disregards the specification in this bit an...

Page 185: ... 1 If the IDD writes multiple blocks this indicates that data are recorded on the disk media in the order in which they are transferred from the INIT 0 If the IDD writes multiple blocks this indicates that data are recorded on the disk media with their order changed in order to complete the command in the fastest time This bit cannot be changed The IDD disregards the specification in this bit and ...

Page 186: ...mmands are stored The biggest Cache Segment size is approximately 476 KB IDD does not support this parameter IDD disregards the specification of this field q Non cache buffer size If this field is greater than zero this field advises the device server how many bytes the application client requests that the device server allocate for a buffer function when all other cache segments are occupied by d...

Page 187: ... 0 0 0 0 0 0 1 1 3 Queue Algorithm Qualifier Reserved Qerr DQue Default 0 0 0 0 0 0 0 0 Variable 1 1 1 1 0 0 0 0 4 Reserve d RAC Reserved SWP RAERP UAAER P EAERP Default 0 0 0 0 0 0 0 0 Variable 0 0 0 0 0 0 0 0 5 X 00 Reserved 6 7 Ready Aer Holdoff Period Default X 0000 Variable X 0000 8 9 Busy Timeout Period Default X 0000 Variable X 0000 10 11 Extended Self Test Completion Time Default X xxxx Va...

Page 188: ...xecutes queued commands by the method selected by the IDD At this time the INIT must verify the correctness of the data through appropriate commands and QUEUE TAG messages 1111 The IDD prohibits to order queued commands When other value is specified in this parameter the IDD reports a CHECK CONDITION status ILLEGAL REQUEST 5 Invalid parameter in List 26 00 c GLTSD global logging target save disabl...

Page 189: ...he IDD is in the sense hold state Table 4 24 QErr Value Description 00b The IDD when it has been in any one of various sense hold states then that sense hold state is cleared continues executing the commands which are queued by normal methods 01b The IDD when it has been in any one of various sense hold states then that sense hold state is cleared clears the commands which are queued At this time ...

Page 190: ...ield specify the action method of asynchronous event reporting protocol The IDD is not supported these field Therefore the IDD always report 0 and ignore specified value j Extended self test completion time This field contains advisory data that an application client may use to determine the time in seconds that the device server requires to complete an extended self test when the device server is...

Page 191: ...t X xxxxxxxx Variable X 00000000 16 23 Page Notch Default X 0000000000000008 Variable X 0000000000000000 This page is used to report the top address and final address of each zone If the zone number 1 of the notching zone is set in the Active notch field and this parameter is issued the starting and ending address of the specified zone can be referred to by the MODE SENSE command Also if Page 3 an...

Page 192: ...ed for LPN active notch starting boundary and ending boundary 1 Since the device is in the notched state the starting boundary and ending boundary for the zone number 1 shown in the active notch is set in the format specified in the LPN Bit LPN Logical or Physical Notch 0 This shows that the boundary address is based on the physical address format At that time the higher order 3 bytes show the log...

Page 193: ... is notched The most significant bit of this field corresponds to page code 3Fh and the least significant bit corresponds to page code 00h If it is specified the IDD disregards this value 9 Port control parameter page code 19 This page is used to set parameters concerning data transfer of the drive and to refer to the current settings and maximum settings of these parameters Table 4 26 Port contro...

Page 194: ...7 LED display c Protocol Identifier 6h Indicates that this page conforms to the SAS SCSI device specifications d I_T NEXUS LOSS TIME Specifies the maximum time for which the IDD 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 v...

Page 195: ...ge Length n 3 7 NUMBER OF PHYS 8 First SAS phy mode descriptor n Last SAS phy mode descriptor a SPF 0 Indicates that the transfer data is in Short Page Format 1 Indicates that the transfer data is in Long Page Format b NUMBER OF PHYS Indicates the total number of phys the TARG maintains Single Port 1 Dual Port 2 The following shows the details of the SAS phy mode descriptor that is reported in Byt...

Page 196: ...PORT ATTACH SMP INIT PORT Reserved 0b 7 Reserved 0000 b ATTACH SSP TARGET PORT ATTACH STP TARGET PORT ATTACH SMP TARGET PORT Reserved 0b 8 15 SAS ADDRESS 16 23 ATTACHED SAS ADDRESS 24 ATTACHED PHY IDENTIFIER 25 31 Reserved 32 PROGRAMMED MINIMUM PHYSICAL LINK RATE 8h HARDWARE MINIMUM PHYSICAL LINK RATE 8h 33 PROGRAMMED MAXIMUM PHYSICAL LINK RATE 9h HARDWARE MAXIMUM PHYSICAL LINK RATE 9h 34 41 Reser...

Page 197: ...STP INIT value received from the INIT with an IDENTIFY address frame g ATTACHED SMP INITIATOR PORT Indicates the SMP INIT value received from the INIT with an IDENTIFY address frame h ATTACHED SSP TARGET PORT Indicates the SSP TARGET value received from the INIT with an IDENTIFY address frame i ATTACHED STP TARGET PORT Indicates the STP TARGET value received from the INIT with an IDENTIFY address ...

Page 198: ...E Indicates the minimum and maximum values of the PHYSICAL LINK RATE supported by a program Code Description 0h Unsupported 8h 1 5Gbps PROGRAMMED MINIMUM PHYSICAL LINK RATE 9h 3 0Gbps PROGRAMMED MAXIMUM PHYSICAL LINK RATE Others Reserved o HARDWARE MINIMUM MAXIMUM PHYSICAL LINK RATE Indicates the minimum and maximum values of PHYSICAL LINK RATE supported by hardware Code Description 8h 1 5Gbps HAR...

Page 199: ...is used to set the time over which the power condition state is transformed into the idle condition or standby condition state However because the IDD does not support the above states the parameter cannot be set on this page a Idle Specifies whether to permit the IDD to enter the Idle condition when the IDD does not receive a command within the time specified in the Idle Condition Timer field The...

Page 200: ...the value specified in this field by 100 ms 11 Informational exceptions control page page code 1C Table 4 30 MODE SELECT parameters informational exception control page Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 1 1 1 0 0 1 Page length X 0A 2 Perf 0 EBF EWASC DExcpt Test 0 LogErr Default 0 0 0 0 1 0 0 0 Variable 1 0 1 1 1 1 0 1 3 0 0 0 0 MRIE Default 0 0 0 0 0 0 0 0 Variable 0 0 0 0 0 1 1 1 4 7 Interval Tim...

Page 201: ...he method of reporting informational exceptions field is ignored when DExcpt is set to one d EWASC enable warning 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 bit is set to one is deter...

Page 202: ... CONDITION shall not be executed before the informational exception condition is reported X 03 Conditionally generate recovered error This method instructs the target to report informational exception conditions dependent on the value of the per bit of the error recovery parameters mode page by returning a CHECK CONDITION status on any command The sense key shall be set to RECOVERED ERROR and the ...

Page 203: ...cific h Interval timer This field indicates the period in 100 millisecond increments for reporting that an informational exception condition has occurred The target does not report informational exception conditions more frequency than the time specified by the Interval Timer field and as soon as possible after the timer interval has elapsed After the informational exception condition has been rep...

Page 204: ... error recovery parameters Fujitsu unique parameter Bit Byte 7 6 5 4 3 2 1 0 0 0 0 1 0 0 0 0 1 1 X 02 Page Length 2 0 0 0 0 Number of retries during a Seek Error Default 0 0 0 0 1 1 1 1 Variable 0 0 0 0 1 1 1 1 3 RFJ Default 0 0 0 0 0 0 0 0 Variable 0 0 0 0 0 0 0 0 a Number of retries during a seek error This parameter specifies the number of times repositioning is retried when a seek error is det...

Page 205: ...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 Table 4 34 shows the configuration of the parameter list MODE SELECT parameters transferred by this command from the INIT Compared to the 4 byte header in the Group 0 MODE SELECT command it is necessary for an 8 byte header to be transferre...

Page 206: ...X 00 5 X 00 6 X 00 Block Descriptor Length LSB 7 X 00 or X 08 block descriptor length MSB Block Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 Data Block Count MSB 1 Data Block Count 2 Data Block Count 3 Data Block Count LSB 4 X 00 5 Data Block Length MSB 6 Data Block Length 7 Data Block Length LSB Page Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 0 0 Page Code 1 Page Length 2 n Page Header Parameter Field ...

Page 207: ...descriptors which describe each type of parameter each of which will be described later in this item When 1 is specified in the DBD disable block descriptors bit of CDB byte 1 it indicates that a Block descriptor is not included in the MODE SENSE data transferred to the INIT by this command and the IDD transfers MODE SENSE data composed from the Header and the specified Page descriptor only to INI...

Page 208: ...he page code Also when X 00 is specified in the Page code field the Page descriptor is not transferred If page codes other than the above mentioned ones Page descriptors which are not supported by the IDD are specified the command is terminated with a CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in CDB 24 00 Also the PC page control field in CDB byte 2 specifies the type of parameter val...

Page 209: ...ns in each page descriptor and 0 is reported in the fields and bit positions which cannot be changed See the description of each page descriptor for the MODE SELECT command Section 4 1 4 concerning the variability of each parameter 10 Default Values Reports the Default value of each parameter See the description of each page descriptor for the MODE SELECT command Section 4 1 4 concerning the actua...

Page 210: ...aller When zero is specified in the Transfer Byte Length field this command is terminated without anything being transferred Table 4 37 lists the data configuration in the parameter list MODE SENSE data transferred to the INIT by this command The parameter list consists of a 4 byte header an 8 byte block descriptor and one or more page descriptors specified in the CDB which are transferred in orde...

Page 211: ...ype 2 WP 0 0 DPOFUA 0 0 0 0 3 X 00 or X 08 Block Descriptor Length Block Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 Data Block Count MSB 1 Data Block Count 2 Data Block Count 3 Data Block Count LSB 4 X 00 5 Data Block Length MSB 6 Data Block Length 7 Data Block Length LSB Page Descriptor Bi t Byte 7 6 5 4 3 2 1 0 0 PS 0 Page Code 1 Page Length 2 n Page Header Parameter Field ...

Page 212: ... it indicates that a write operation to the disk media is prohibited and when 0 is specified it indicates that a write operation is permitted d DPOFUA bit When this bit is 0 it indicates that the IDD does not supports the DPO and FUA bit When this bit is 1 it indicates that the IDD supports the DPO and FUA bits e Block descriptor length This field indicates the Block descriptor length byte length ...

Page 213: ...is 0 it indicates that this is a parameter which cannot be saved to the disk It is possible to save all the Page descriptors supported by the IDD However 1 is always indicated in this bit for all Page descriptors transferred by this command b 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 IDD alwa...

Page 214: ... the INIT The functions of this command are the same as those of the Group 0 MODE SENSE command Section 4 1 7 except that the format of data MODE SENSE data transferred to the INIT differs somewhat Table 4 38 lists the data configuration of the parameter list MODE SENSE data transferred to the INIT by this command Compared to the 4 byte header in the case of a Group 0 MODE SENSE command an 8 byte ...

Page 215: ...e 3 WP 0 0 DPOFUA 0 0 0 0 4 X 00 5 X 00 6 X 00 Block Descriptor Length MSB 7 X 00 or X 08 Block Descriptor Length LSB Block Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 Data Block Count MSB 1 Data Block Count 2 Data Block Count 3 Data Block Count LSB 4 X 00 5 Data Block Length MSB 6 Data Block Length 7 Data Block Length LSB Page Descriptor Bit Byte 7 6 5 4 3 2 1 0 0 PS 0 Page Code 1 Page Length 2 n Param...

Page 216: ...START STOP UNIT 1B Bit Byte 7 6 5 4 3 2 1 0 0 X 1B 1 0 0 0 0 0 0 0 Immed 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 LoEj Start 5 0 0 0 0 0 0 0 0 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 Issuing this command with the Start bit ...

Page 217: ...d 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 In this case the INIT has no means of detecting the timing when the power condition state becomes Active_Wait and there are no limitations on the time period in which the system waits the NOTIFY ENABLE SPINUP primitive Therefore...

Page 218: ...is command is maintained until any one of the following conditions occurs 1 Reserve is released by a RELEASE command from the INIT that issued this command 2 Receiving HARD RESET primitive from any INIT 3 Switching the IDD s power off or on When an IDD is reserved for any SAS device if this command is issued by an INIT that doesn t have the Reserve Right for that IDD this command is terminated wit...

Page 219: ...e right for the IDD If the 3rd Pty bit is 1 execution of this command is terminated with the CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in CDB 24 00 4 1 11 RESERVE EXTENDED 56 Bit Byte 7 6 5 4 3 2 1 0 0 X 56 1 0 0 0 3rd Pty 0 0 0 0 2 3 Third Party Device ID 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 7 8 9 0 0 0 0 0 0 0 0 Together with the RELEASE command this command control...

Page 220: ... to be specified by the INIT in this byte Also the value specified in CDB byte 3 to 4 reports CHECK CONDITION status 05 24 00 except for X 00 is specified 1 Release function This command releases a reserve state if a reserve state exists and if the INIT which issued this command has a reserve right for the entire IDD logical unit 2 Release object and third party release function The third party re...

Page 221: ... 1 14 REQUEST SENSE 03 Bit Byte 7 6 5 4 3 2 1 0 0 X 03 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 Transfer Byte Length 5 0 0 0 0 0 0 0 0 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 IDD has a length of 48 bytes The IDD generates sense data in any of the following cases and holds the sense...

Page 222: ...with a length that is specified in the Transfer Byte Length field or the IDD s own sense data length 48 bytes whichever is smaller When the value specified in the Transfer Byte Length shows 48 bytes or more 48 bytes of sense data are transferred and the command terminates with the GOOD status This command reports the CHECK CONDITION status and terminates abnormally only in the cases where the cond...

Page 223: ...LECT operation the drive will save all parameters to the disc medium A SP bit of zero specifies that parameters is not saved It is not an error to set the SP bit to one and to set the DS bit of a log parameter to one In this case the parameter value for that log parameter is not saved The Parameter Code Reset PCR bit of one and a Parameter list length of zero cause all implemented parameters to be...

Page 224: ...ults in the truncation of any log parameter the IDD terminates this command with CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in CDB 24 00 A Parameter List Length of zero indicates that no pages shall be transferred This condition shall not be considered an error The IDD does not support that the application client should send pages in ascending order by page code value if the Data Out B...

Page 225: ...ent Log Page Enable 10 Self Test Result Log Page Disable b Page length This field specifies the length in bytes of the following log parameters If the application client sends a page length that results in the truncation of any parameter the device server terminates the command with CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in parameter list 26 00 The log pages contain one or more spe...

Page 226: ...ith a SP bit of one 3 TSD Target Save Disable The IDD does not support this bit For LOG SENSE command See 4 1 16 the IDD always report zero Also for this command the IDD accepts this bit value of 1 but ignores its functionality 4 ETC Enable Threshold Comparison The IDD does not support this bit For LOG SENSE command See 4 1 16 the IDD always report zero Also for this command the IDD accepts this b...

Page 227: ...is 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 It is a complementary command to the LOG SELECT command The Parameter Pointer Control PPC bit is not supported It should be zero An Save Parameters SP bit of zero indicates the device server performs the specified this comman...

Page 228: ...lf Test Result Log Page Supported 18 SAS Protocol Log Page Ignored 2F SMART Status Page Ignored 38 SMART Data Page Ignored The Parameter Pointer field allows the application client to request parameter data beginning from s specific parameter code to the maximum allocation length or the maximum parameter code supported by the target whichever is less If the value of the Parameter Pointer field is ...

Page 229: ...and descriptor block 1 Support log page X 00 The supported log page returns the list of log pages implemented by the drive Table 4 44 Support log page X 00 Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 1 X 00 Reserved 2 X 00 Parameter Length 3 X 0D Parameter Length 4 X 00 Supported Page 5 X 01 Supported Page 6 X 02 Supported Page 7 X 03 Supported Page 8 X 05 Supported Page 9 X 06 Supported Page 10 X ...

Page 230: ...Basis Cause Type 5 0 0 0 0 0 0 0 0 DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 02 Parameter Length 8 9 X 0000 Data Underrun 10 X 00 Reserved Count Basis Cause Type 11 0 0 0 0 0 0 0 0 DU DS TSD ETC TMC LBIN LP 12 0 0 0 0 0 0 0 0 13 X 02 Parameter Length 14 15 X 0000 Data Overrun Cause 0h Undefined 1h SCSI bus busy optional 2h Transfer rate too slow optional 3h Fh Reserved The drive dose not sup...

Page 231: ...t support this field due to a hardware limitation Zero is always reported Data Overrun Count of data overruns which occur during read operation when a buffer full condition prevents continued transfer of data from the media to the buffer The drive does not support this field due to a hardware limitation Zero is always reported 3 Write error count page X 02 Table 4 46 Write error count page X 02 Bi...

Page 232: ...initiator during write operations because no delay is incurred The drive does not support this field due to a hardware limitation Zero is always reported Write errors recovered with possible delays page 02 code 0001 Table 4 48 Write errors recovered with possible delays page 02 code 0001 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0001 Parameter code Errors Recovered With Possible Delays LSB DU DS TSD ETC ...

Page 233: ...the interface during write operations Implementation If a write error is posted it will force a save of all error log pages information Total recoverable write errors posted to INIT page 02 code 0003 Table 4 50 Total recoverable write errors posted to INIT page 02 code 0003 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0003 Parameter code Total Posted Recoverable Errors LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 ...

Page 234: ...he Total Write Bytes Processed indicates the total processed bytes during write operations Total unrecoverable write errors posted to INIT page 02 code 0006 Table 4 52 Total unrecoverable write errors posted to INIT page 02 code 0006 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0006 Parameter code Total Posted Unrecoverable Errors LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 04 Parameter Length 8 MSB...

Page 235: ...f Parameter Pointer CDB 5 6 Read errors recovered without delays page 03 code 0000 Table 4 54 Read errors recovered without delays page 03 code 0000 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0000 Parameter code Errors Recovered Without Delays LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 04 Parameter Length 8 MSB 9 10 Counter Value 11 LSB The Counter Value indicates the count of all recovered read ...

Page 236: ...orted to the initiator during read operations because possible delay is incurred Total read errors posted page 03 code 0002 Table 4 56 Total read errors posted page 03 code 0002 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0002 Parameter code Total Posted Errors LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 04 Parameter Length 8 MSB 9 10 Counter Value 11 LSB The Counter Value indicates the count of al...

Page 237: ...x errors to the interface during read operations The value includes the count of all posted recovered verify errors page X 05 Parameter code X 0003 Total read bytes processed page 03 code 0005 Table 4 58 Total read bytes processed page 03 code 0005 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0005 Parameter code Total Bytes Processed LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 0A Parameter Length 8 ...

Page 238: ...8 MSB 9 10 Counter Value 11 LSB The Counter Value indicates the count of all posted unrecovered errors 03 xx xx to the interface during read operations The value includes the count of all posted unrecovered verify errors page X 05 Parameter code X 0006 5 Verify error count page X 05 Table 4 60 Verify error count page X 05 Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 0 1 1 X 00 Reserved 2 Page Length MSB...

Page 239: ...erify errors that would not be reported to the initiator during verify operations because no delay is incurred Vefiry errors recovered with possible delays page 05 code 0001 Table 4 62 Vefiry errors recovered with possible delays page 05 code 0001 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0001 Parameter code Errors Recovered With Possible Delays LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 04 Para...

Page 240: ... interface during verify operations Implementation If a verify error is posted it will force a save of all error log page information Total recoverable verify errors posted to INIT page 05 code 0003 Table 4 64 Total recoverable verify errors posted to INIT page 05 code 0003 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0003 Parameter code Total Posted Recoverable Errors LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 ...

Page 241: ... The Total Verify Bytes Processed indicates the total processed bytes during verify operation Total unrecoverable verify errors posted to INIT page 05 code 0006 Table 4 66 Total unrecoverable verify errors posted to INIT page 05 code 0006 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0006 Parameter code Total Posted Unrecoverable Errors LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 0 0 7 X 04 Parameter Length ...

Page 242: ...er Value 11 LSB The Counter Value indicates the count of all non medium errors 01 xx xx 02 xx xx 04 xx xx 05 xx xx 06 xx xx 07 xx xx 09 xx xx and 0B xx xx posted to the interface Implementation If a non medium error is posted it will force a save of all error log pages information 7 Temperature page X 0D Table 4 68 Temperature page X 0D Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 1 1 0 1 1 X 00 Reserved 2 ...

Page 243: ...emperature cannot be detected because of a sensor failure or other condition the value returned shall be FFh If EWASC mode page 1C is on comparison is performed between the temperature value specified in parameter 0000h and the reference temperature specified in parameter 0001h Reference temperature page 0D code 0001 Table 4 70 Reference temperature page 0D code 0001 Bit Byte 7 6 5 4 3 2 1 0 4 5 M...

Page 244: ...of manufacture page 0E code 0001 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0001 Parameter code Date of Manufacture LSB DU DS TSD ETC TMC LBIN LP 6 0 1 0 0 0 0 0 1 7 X 06 Parameter Length 8 MSB 9 10 Year of manufacture 4 ASCII characters 11 LSB 12 13 MSB Week of manufacture 2 ASCII characters LSB The year and week in the year that the device was manufactured shall be set in the parameter field defined by ...

Page 245: ...e using a LOG SELECT command to indicate when the device was placed in service If the parameter is not yet set or is not settable the default value placed in the parameter field shall be 6 ASCII blank characters 20h The field shall not be checked for validity by the device server Specified cycle count over device lifetime page 0E code 0003 Table 4 74 Specified cycle count over device lifetime page...

Page 246: ... byte binary number 11 LSB The Accumulated start stop cycles is a parameter provided by the device sever The accumulated start stop cycles parameter shall not be savable by the application client using the LOG SELECT command The parameter value is a 4 byte binary number The value indicates how many start stop cycles the device has detected since its date of manufacture For rotating magnetic storag...

Page 247: ... application client parameter data page 0F code 0000 003F Table 4 77 General usage application client parameter data page 0F code 0000 003F Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0000 X 003F Parameter code Application Client Parameter LSB DU DS TSD ETC TMC LBIN LP 6 1 0 0 0 0 0 1 1 7 X FC Parameter Length 8 MSB 9 258 General Usage Parameter Bytes 259 LSB The values stored in the General usage paramete...

Page 248: ... 5 6 Self test result parameter data page 10 code 0001 0014 Table 4 79 Self test result parameter data page 10 code 0001 0014 Bit Byte 7 6 5 4 3 2 1 0 4 5 MSB X 0001 X 0014 Parameter code Self Test Result Parameter LSB DU DS TSD ETC TMC LBIN LP 6 0 0 0 0 0 0 1 1 7 X 10 Parameter Length 8 Self Test Code 0 Self Test Result Value 9 Self Test Segment Number 10 11 MSB Time Stamp LSB 12 MSB Address of F...

Page 249: ...vice server was executing the self test and the device server was unable to complete the self test 4h The self test completed with a failure in a test segment and the test segment that failed is not known 5h The first segment of the self test failed 6h The second segment of the self test failed 7h Another segment of the self test failed see the SELF TEST SEGMENT NUMBER field 8h Eh Reserved Fh The ...

Page 250: ... 4 3 2 1 0 0 Page Code 18h 1 Reserved x 00 2 MSB 3 Parameter Length n 3 LSB 4 First Protocol log parameter m Nth Protocol log parameter This log page is used to report the information on an error that occurs on the SAS bus As to the log parameters reported in byte 4 and the subsequent bytes refer to Table 4 82 Log parameter format ...

Page 251: ...ER 0h or 1h 10 11 Reserved x 0000 12 Reserved 0b ATTACHED DEVICE TYPE 0 0 1 Reserved 0000 b 13 Reserved 0000 b NEGOTIATED PHYSICAL LINK RATE 8h or 9h 14 Reserved 0000 b ATTACH SSP INIT PORT ATTACH STP INIT PORT ATTACH SMP INIT PORT Reserved 0b 15 Reserved 0000 b ATTACH SSP TARGET PORT ATTACH STP TARGET PORT ATTACH SMP TARGET PORT Reserved 0b 16 23 SAS ADDRESS 24 31 ATTACHED SAS ADDRESS 32 ATTACHED...

Page 252: ...End Device is reported f NEGOTIATE PHYSICAL LINK RATE Indicates the physical link rate that has been established with a speed negotiation sequence For 1 5 Gbps X 8 is reported and for 3 0 Gbps X 9 is reported g ATTACHED SSP INITIATOR PORT Reports the SSP INIT value received from the INIT with an IDENTIFY address frame h ATTACHED STP INITIATOR PORT Reports the STP INIT value received from the INIT ...

Page 253: ...ess frame o ATTACHED PHY IDENTIFIER Reports the phy address received from the INIT with an IDENTIFY address frame p INVALID DWORD COUNT Reports the cumulative count of INVALID DWORD errors detected in a sequence of SP_WDS other than the PHY RESET sequence q RUNNING DISPARITY ERROR COUNT Reports the cumulative count of RUNNING DISPARITY errors received except in the PHY RESET sequence r LOSS OF DWO...

Page 254: ...ading out this page The Page Length field indicates the length byte length after byte 4 The SMART Status Parameter field is Fujitsu unique parameters The details of this field are outside the scope of this manual 13 SMART data page X 38 Table 4 84 SMART data page X 38 Fujitsu unique page Bit Byte 7 6 5 4 3 2 1 0 0 0 0 1 1 1 0 0 0 1 X 00 Reserved 2 Page Length MSB 3 Page Length LSB 4 Log Parameters...

Page 255: ...es this command the command is rejected with the report of the RESERVATION CONFLICT status When the reserved state implemented with the PERSISTENT RESERVATION command is valid this command is always executed normally The length of the PERSISTENT RESERVE IN parameter data that can be reported with this command is indicated in the parameter data When a byte count that is too small to transfer an ent...

Page 256: ... All the Reservation keys currently registered eight bytes for each key If multiple INITs have registered with the same key the key appears in the list once for the registration of each INIT and as many times as there are registered INITs keys appear in the list not in the order in which they have been registered in the drive but in ascending order of IDs starting with the last INITs that has regi...

Page 257: ...n When the PERSISTENT RESERVE IN command is executed the RESERVE or RELEASE Service Action of the PERSISTENT RESERVE OUT command is executed or the PERSISTENT RESERVE OUT command cannot be executed because of an error or RESERVATION CONFLICT this counter is not updated Regardless of the APTPL bit value the generation value shall be set to 0 in the power on reset process By referring to the value o...

Page 258: ...tion 3 LSB 4 MSB Additional Length n 7 7 LSB 8 n MSB Reservation descriptor s see below LSB The Generation field shall be as defined for the PERSISTENT RESERVE IN READ KEYS Service Action parameter data see 4 1 17 2 The Additional Length field contains the count of bytes in the Reservation Descriptors field after Byte 8 If the value specified in the Additional Length field by the PERSISTENT RESERV...

Page 259: ...onditions It also contains the Type and Scope reserve condition values specified by the PERSISTENT RESERVE OUT command The Reservation key field indicates the Reservation key registered with its reserve condition If each INIT uses a key specific to itself the application needs to know the association of the INIT that holds a reserve condition with a Reservation key If the Scope value is element re...

Page 260: ...ive that supports PERSISTENT RESERVE OUT must also support the Logical Unit scope b Element scope not supported This Scope field value indicates that reservation has been applied to the element specified in the Scope specific Address field of the PERSISTENT RESERVE OUT parameter list The support of Element Scope is optional Persistent reservations type The Type field value defines the reserve attr...

Page 261: ... 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 4h Reserved Reads Shared Any INIT can execute a read type command 5h Write Exclusive Registrants Only Writes Exclusive Any write type command issued by an INIT that has not registered the Reservation Conflict results in a Reservation Conflict Reads...

Page 262: ...g or illegal reserve conditions by using the PERSISTENT RESERVE IN command and if necessary an INIT can make new reserve conditions preempt these reserve conditions by using the PERSISTENT RESERVE OUT command Since set reserve conditions cannot be reset by processing such as TARGET RESET task PERSISTENT RESERVATION can be used to have multiple INITs share a device The PERSISTENT RESERVE OUT and PE...

Page 263: ...ains the fields for specifying different restrictions imposed according to the Service Action type of PERSISTENT RESERVATION the Scope to which PERSISTENT RESERVATION is applied and PERSISTENT RESERVATION For the definitions of the Type and Scope fields refer to the PERSISTENT RESERVE IN command If a Scope value that is not executed by the device is specified in the Scope field the drive reports t...

Page 264: ...servation key with the device server 01h RESERVE Gnerates a persistent reservation having a specified SCOPE and TYPE 02h RELEASE Releases persistent reservations 03h CLEAR Clears all reservation keys and all persistent reservations 04h PREEMPT Preempts persistent reservations from another initiator 05h PREEMPT ABORT Preempts persistent reservations from another initiator and aborts the task set fo...

Page 265: ...SERVE OUT command matches the Reservation Key registered by the INIT that has issued the command However if all the registered Reservation Keys are zero not registered the value specified in this field is ignored If a key that is different from the Reservation Key for the relevant INIT is specified by the PERSISTENT RESERVE OUT command the drive reports a RESERVATION CONFLICT status All the Reserv...

Page 266: ...ved by the drive is 1 the logical unit maintains all the PERSISTENT RESERVATIONs and Reservation Keys for all the INITs throughout power shutdown and re power on sequences the SA space is used to save the registration information The APTPL value which controls the logical unit behavior while the power is turned off is valid regardless of which INIT the bit value has been received from Table 4 93 e...

Page 267: ... This command normally operate under the reserve condition RESERVE or PERSISTENT RESERVE The Allocation Length should be at least 16 bytes If the Allocation Length is less than 16 bytes the IDD reports the CHECK CONDITION status ILLEGAL REQUEST 5 Invalid Field in CDB 24 00 If the Allocation Length is not sufficient to contain the entire logical unit inventory the device server shall report as many...

Page 268: ...field shall contain the length in bytes of the LUN list that is available to be transferred The LUN list length is the number of logical unit numbers in the logical unit inventory multiplied by eight If the allocation length in the command descriptor block is too small to transfer information about the entire logical unit inventory the LUN list length value shall not be adjusted to reflect the tru...

Page 269: ...ction field can be specified only X 05 The Allocation Length field indicates how much space has been reserved for the returned parameter data If the length is not sufficient to contain all the parameter data the first portion of the data shall be returned This shall not be considered an error The actual length of the parameter data is available in the Identifier Length field in the parameter data ...

Page 270: ... SET DEVICE IDENTIFIER command The Identifier field shall contain a vendor specific value The value reported shall be the last value written by a successful SET DEVICE IDENTIFIER command The value of the identifier shall be changed only by a SET DEVICE IDENTIFIER command The identifier value shall persist through resets power cycles media format operations and media replacement The target shall re...

Page 271: ...sense code shall be set to DEVICE IDENTIFIER CHANGED The Service Action field can be specified only X 06 The Allocation Length field specifies the length in bytes of the Identifier that shall be transferred from the application client to the device server The maximum value for this field shall be 512 bytes A parameter list length of zero indicates that no data shall be transferred and that subsequ...

Page 272: ...r block count field with the logical data block on the disk media specified in the Logical block address field in the CDB as the top The transfer block count can be specified up to a maximum of 256 logical data blocks When zero is specified in the Transfer block count field in byte 4 of the CDB it specifies transfer of 256 logical data blocks and when a value other than zero is specified it specif...

Page 273: ...nd are error free When a correctable error check is detected the IDD first corrects the data errors in the data buffer then transfers those data to the INIT If the Look Ahead cache feature is permitted a caching operation is performed using the IDD s data buffer by this command See Chapter 3 Data Buffer Management concerning details of data buffer operation and the Look Ahead cache feature 4 2 2 R...

Page 274: ... 4 2 3 WRITE 0A Bit Byte 7 6 5 4 3 2 1 0 0 X 0A 1 0 0 0 Logical Block Address MSB 2 Logical Block Address 3 Logical Block Address LSB 4 Transfer Block Count 5 0 0 0 0 0 0 0 0 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 Lo...

Page 275: ...xt If the write cache function is disabled a status byte is reported after writing to the disk media of all the data transferred from the INIT is completed then execution of the command is terminated 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...

Page 276: ... blocks with the logical data block on the disk media specified in the Logical block address field in the CDB as the top The functions of this command are the same as those of the Group 0 WRITE command Section 4 2 3 with the exception that it is possible to specify 4 byte logical block addresses and 2 byte transfer block counts However when zero is specified for the Transfer block count the comman...

Page 277: ...e block allocation function cannot be applied When zero is specified in the Transfer block count this command is terminated normally without performing seek or pre fetch The specification in bit 4 of CDB byte 1 is disabled in the IDD and the specified value is disregarded The VERIFY check executed by this command is the only the ECC data portion normalcy check Error recovery processing during exec...

Page 278: ...sfer block count the command is terminated normally without performing seek and pre fetch Bit 4 of CDB byte 1 is disabled in the IDD and the specified value is disregarded If 1 is specified in bit 1 of CDB byte 1 the BytChk bit the IDD performs a comparison check of the data read from the disk media and the data transferred from the INIT If the data do not match during this mode the command is ter...

Page 279: ...ical data block specified in the Logical block address field in the CDB exists When disconnect processing is permitted the IDD performs disconnect processing after receiving the CDB After that the IDD executes reconnect processing at the point when the seek operation is completed and reports the status When disconnect processing is not permitted the IDD executes the seek operation while still conn...

Page 280: ...ess LSB 6 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 0 0 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 ...

Page 281: ... the disk media When the write cache is used unwritten data held in the data buffer which are written to the disk media are written using this command The values specified in the Logical block address field and Block count field in the CDB are disregarded and if any unwritten data exist in the data buffer writing of all those data to the disk media is performed If bit 1 of CDB byte 1 the Immed imm...

Page 282: ... At the same time the IDD also implements defect management processing allocating alternate blocks for defective portions of the disk media in accordance with the specifications in this command Furthermore when the disk media is initialized with any of the following format attributes changed the INIT must issue the MODE SELECT or MODE SELECT EXTENDED command before issuing this command and specify...

Page 283: ...ocks detected in the data block verify operation Certification after initialization when the FORMAT UNIT command is executed The IDD generates this list internally when the FORMAT UNIT command is executed and adds it to the G List d G List grown defect list The defect information in this list contains defect position information specified by the NIT and position information on defective data block...

Page 284: ...ist are added to those of the previously existing G List The Defect List Format field specifies the format of the defect list D List transferred from the INIT when the FmtData format data bit is 1 Any one of the following formats can be specified for the defect list Table 4 97 Defect list format Defect List Format D List Format 0 0 0 Block Address Format 1 0 0 Byte Distance from the Index Format 1...

Page 285: ...ecified in the FmtData format data bit of the CDB Table 4 98 FORMAT UNIT command parameter list configuration Header Bit Byte 7 6 5 4 3 2 1 0 0 X 00 FOV DPRV DCRT STPF 1 0 0 0 0 0 0 Immed 0 1 0 1 0 1 2 Defect List Length MSB 3 Defect List Length LSB Defect List D List Bit Byte 7 6 5 4 3 2 1 0 0 1 x xx xx 1 xx x Defect Descriptor n Defect Descriptor 0 ...

Page 286: ...specified in the various control flags DPRY disable primary Default value 0 0 Specifies execution of format processing using the P List Alternate blocks are allocated as substitutes for sectors in which defects registered in the P List exist and logical data blocks are not positioned there 1 Specifies use of the P List in defect processing Even if this value is specified the P List itself is saved...

Page 287: ...point when transfer of the defect list is completed a GOOD status is reported 0 If 0 is specified in the Immed immediate bit the specified operation is executed and the status byte is reported at the point when that operation is completed then the command is terminated Defect list length This field specifies the total number of bytes in the Defect list transferred from the INIT following the heade...

Page 288: ...efect descriptor in this format specifies the cylinder number head track number and byte distance to the top byte of those data 8 bytes of the data which includes defective bits on the disk media One defect is treated as a defect with a length of 8 bytes 64 bits length Therefore for defects with a length which exceeds 8 bytes 2 or more defect descriptors must be specified When multiple defect desc...

Page 289: ...r No must be specified in the top position and the physical sector No in the bottom position with the defect positions listed in ascending order Sector numbers described in this format are physical sector numbers which to not apply the Track skew factor and the Cylinder skew factor Table 4 100 Defect descriptor physical sector address format Bit Byte 7 6 5 4 3 2 1 0 0 Cylinder No MSB 1 Cylinder No...

Page 290: ...but also the number of consecutive Slips Consequently the concrete Defect numbers cannot be described though the IDD guarantees 12 000 Slip Sectors and 3 000 Alternate Sectors at minimum If defect processing which exceeds this limit is specified in the FORMAT UNIT command that command is terminated with a CHECK CONDITION status HARDWARE ERROR 4 No defect spare location available 32 00 2 A defect d...

Page 291: ...existing G List 2 The previously existing G List is saved 1 0 Note 1 Note 2 Note 3 d d d 1 1 Zero 1 Alternate block allocation is performed for defects registered in the previously existing G List 2 The P List is saved but it is not used in defect processing 3 The previously existing G List is saved 1 1 Note 1 Note 2 d d d 0 1 0 0 Zero 1 Alternate block allocation is performed for defects register...

Page 292: ...rformed for defects registered in the P List and the defects described in the D List transferred from the INIT 2 The P List is saved but it is not used in defect processing 3 The previously existing G List is erased and it is not used in defect processing 4 The D List is added to the previously existing G List Note 1 ddd 0 0 0 D List in the block address format 1 0 0 D List in the byte distance fr...

Page 293: ...ata in the logical data blocks specified in the Defect data list to the allocated alternate data blocks is attempted If the data in logical data blocks which are specified in the Defect data list are correctable by ECC correction the corrected data are copied and those data which are not correctable by ECC are copied as is in the uncorrected state including the errors and in the case of other medi...

Page 294: ... after the header and must be a multiple of 4 Also when zero is specified in this field this command is terminated without transfer of the defect descriptor list and allocation processing of alternate blocks The Defect list length that can be specified for the IDD is 2 044 X 7FC bytes or less Therefore a maximum of 511 defective blocks can be specified in the REASSIGN BLOCKS command The logical bl...

Page 295: ...inherent information field in the sense data However if alternate block allocation processing of the defect descriptors for which alternate block allocation has not been implemented cannot be specified or if alternate block allocation of all the specified defect descriptors has been completed the Command inherent information field indicates X FFFFFFFF When alternate block allocation processing is ...

Page 296: ... in Section 5 2 in accordance with the contents of the sense data 1 Delete the defect descriptors which precede the defect descriptor that specifies the logical block address displayed in the Command inherent information field of the sense data from the defect descriptor list specified in this command and leave that defect descriptor in the list Logical block address that indicates the Command inh...

Page 297: ...t the time the disk drive was shipped from the factory On the other hand the G List shows the defect position information specified from the INIT by the REASSIGN BLOCKS command or automatic alternate block allocation processing or when executing the FORMAT UNIT command or defective data block positional information from alternate block allocation from Verify operation after initialization The INIT...

Page 298: ...ution of data transfer Table 4 105 lists the format of defect data transferred to the INIT by this command Table 4 105 READ DEFECT DATA command defect data configuration Bit Byte 7 6 5 4 3 2 1 0 0 X 00 1 0 0 0 PList GList Defect List Format 2 Defect List Length MSB 3 Defect List Length LSB 4 Defect Data n 1 Header a P List primary list bit When this bit is 1 it indicates that P List defect data ar...

Page 299: ...bytes 4 or 8 per defect descriptor quotient the INIT can know the number of defects on the disk media 2 Defect descriptor list The data transferred after the 4 byte header is the Defect descriptor list Defect data in which the defect position information are described with the type and format specified in the CDB One Defect descriptor has a length of 4 bytes when in the Block address format and a ...

Page 300: ...able 4 106 Defect data conditions Defect List Format PList GList Block Address Format 2 2 Byte Distance from the Index Format 1 1 3 Physical Sector Address Format 1 1 1 Regardless of the size of the User Space all the defect position information for the disk media other than the system space is reported Defect position information is also reported for areas which cannot be clearly accessed from th...

Page 301: ...ion information is not reported for defects which do not have an influence on data block read write operations When data are in the Byte Distance from the Index Format when the P List is reported multiple defect position information may be reported for a single sector or 2 defective sectors may be reported as a single item of defect position information due to defects which extend across sector bo...

Page 302: ...r Byte Length LSB 10 0 0 0 0 0 0 0 0 11 0 0 0 0 0 0 0 0 This command transfers the list containing the defect position information of disk media defect data to the INIT The command is the same as the READ DEFECT DATA command 37 described in Section 4 3 3 except for the following the transfer byte length can be specified in four bytes and the defect list length can be specified in four bytes in thi...

Page 303: ... List Length LSB 8 Defect Data n 4 4 Maintenance Diagnostic Commands 4 4 1 SEND DIAGNOSTIC 1D Bit Byte 7 6 5 4 3 2 1 0 0 X 1D 1 SELF TEST CODE PF 0 SelfTest DevOfl UnitOfl 2 0 0 0 0 0 0 0 0 3 Parameter List Length MSB 4 Parameter List Length LSB 5 0 0 0 0 0 0 0 0 This command executes self diagnosis tests which the IDD is equipped to perform and operation specified in the parameter list transferre...

Page 304: ...3 Disk Media CE Space Write Read Data Comparison Test Execution Object When the IDD completes all the specified self diagnosis tests normally it reports a GOOD status On the other hand when an error is detected in any of the specified self diagnosis tests a CHECK CONDITION status is reported and information related to the detected error is shown in the sense data For example when an error is detec...

Page 305: ...COVERED ERROR 1 is reported after the series of diagnostic tests is completed and the sense data show the contents of the last error to be successfully recovered from 1 1 When error recovery is successful or even when error recovery is impossible the diagnostic test is terminated with an error at the point when the permitted error recovery processing is completed and a CHECK CONDITION status is re...

Page 306: ...lfTest self test bit s specification is 0 When zero is specified in the Parameter list length field this command is terminated without anything being executed Also when the value specified in the Parameter list length field does not reach the specified length for the parameter list explained later and as a result not all the bytes in the parameter list can be received that command is terminated wi...

Page 307: ...s which can be specified by the INIT and their functions are as shown Table 4 111 Table 4 111 Page code Page Code Hex Function 00 Reports a list of the supported page codes 40 Logical Physical Address Conversion Page parameter length This field specifies the byte length of the page parameter after byte 4 The INIT must specify the same value as the length specified for each of the parameter pages w...

Page 308: ... in Section 4 4 2 1 Table 4 112 SEND DIAGNOSTIC parameters page code list Bit Byte 7 6 5 4 3 2 1 0 0 X 00 Page Code 1 0 0 0 0 0 0 0 0 2 X 00 Page parameter length 3 X 00 Page parameter length b 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 ...

Page 309: ...Index Format 1 0 1 Physical Sector Address Format 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 furthermore when the logical block address format is specified it must be described in b...

Page 310: ...d is terminated with a CHECK CONDITION status ILLEGAL REQUEST 5 Invalid field in CDB 24 00 The SELF TEST Code field specifies the type of executing Self Test by this command as Table 4 115 Table 4 115 SELF TEST Page code Hex Function 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 s...

Page 311: ...B 5 0 0 0 0 0 0 0 0 This command transfers data response data which show the results of executing the SEND DIAGNOSTIC command from the IDD to the INIT The format and content of response data are determined by the parameter list page code specified by the INIT in the SEND DIAGNOSTIC command The Transfer byte length field in the CDB shows the maximum number of bytes of response data that can be rece...

Page 312: ...nse data showing the execution results of the latest SEND DIAGNOSTIC command Also even if this command is executed the response data in not cleared and remains valid until the next SEND DIAGNOSTIC command is executed 3 If this command is issued when valid response data do not exist the IDD transfers a maximum of 4 bytes of X 00 data to the INIT Table 4 116 lists the format of response data transfe...

Page 313: ...he execution results of the operation specified by the SEND DIAGNOSTIC command are reported in this field 1 Page code list This response data reports the Page code list of the parameter page supported by the IDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command after byte 4 The format and contents of this response data are shown in Table 4 117 Table 4 117 RECEIVE DIAGNOSTIC...

Page 314: ...t Before Conversion 5 0 0 0 0 0 Address Format After Conversion 6 7 Logical or Physical Address 13 The value of the Page Parameter Length field in this response data is a variable length within the range of 2 8n in the FC specifications For example If multiple logical data blocks are located in 1 physical sector or if 1 logical data block is located in multiple physical sectors n address informati...

Page 315: ...mat 0 0 0 Logical Block Address Format 1 0 0 Byte Distance from the Index Format 1 0 1 Physical Sector Address Format The description of address information shown in bytes 6 to 13 is the same as the description specifications in the D List transferred from the INIT by the FORMAT UNIT command For details see the description of the FORMAT UNIT command Section 4 3 1 Furthermore When the logical block...

Page 316: ...code to the IDD The IDD stores data transferred from the INIT in accordance with the specifications in this command s CDB to in the data buffer in the IDD This command using buffer addresses with a range of X 000000 to X 693660 must specify data storage positions in 1 byte units and with 4 byte units addresses The INIT can know the IDD s buffer configuration and the units which addresses can be sp...

Page 317: ...so zero must be specified in the Buffer address field of the CDB The Transfer byte length field specifies the total number of bytes of data transferred form the INIT The transfer byte count specification includes the 4 bytes of the header The IDD stores the data transferred from the INIT with the header omitted Transfer byte length 4 bytes in the data buffer beginning in order from the top of the ...

Page 318: ...d in the CDB The Transfer byte length field in the CDB specifies the total number of bytes of data transferred by the INIT The transfer byte count specification includes the 4 bytes of the header The IDD stores data transferred from the INIT in a length in which the number of bytes in the header has been deleted from the data Transfer byte length 4 bytes in the data buffer beginning at the byte po...

Page 319: ...saving In this mode the controller s microcode or control information is transferred to the IDD s control memory area 0 must be specified in the Buffer ID field and the Buffer address field The Transfer byte length field specifies the total number of transfer bytes of data transferred from the INIT When downloading of microcode is completed the IDD generates a UNIT ATTENTION condition for all the ...

Page 320: ... the FLASH ROM the IDD may be severely damaged The worst case scenario in this event would be an inoperable drive 6 Mode 0 1 1 0 Microcode Download with offsets without saving In this mode the INIT may split the transfer of the controller s microcode or control information over two or more WRITE BUFFER commands If the last WRITE BUFFER command of a set of one or more commands completes successfull...

Page 321: ...he FLASH ROM of the media device and the microcode restarts the device When the last part of the microcode data is transferred and the complete and correct microcode is received in the buffer the IDD saves the microcode in the FLASH ROM If it has been saved correctly the IDD restarts itself using this microcode After the successful reboot of the IDD this command is completed with the GOOD status A...

Page 322: ... command each data byte position in the data buffer must be specified in 4 byte units using buffer addresses within the range X 000000 to X 693660 The functions of this command and the contents of the data transferred to the INIT are specified by the Mode field in the CDB and one of the transfer modes shown in Table 4 122 can be selected Table 4 122 READ BUFFER transfer mode Mode Bit 3 2 1 0 Trans...

Page 323: ...data transfer The format of the data transferred to the INIT when this mode is specified is shown in Table 4 123 Table 4 123 READ BUFFER command buffer data mode 0000 0001 Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 1 Effective Buffer Data Length MSB 2 Effective Buffer Data Length 3 Effective Buffer Data Length LSB 4 Buffer Data Byte 0 5 Buffer Data Byte 1 n Buffer Data Byte n 4 The Effective buffe...

Page 324: ...n the case of Mode 0 0 0 0 However the Effective buffer data length field in the header indicates the size byte length of the data from the byte position in the data buffer specified in the Buffer offset field in the CDB to the final byte position in the data buffer including that byte Also the length of the buffer data transferred to the INIT by this command is the value for the number of bytes i...

Page 325: ...ffer which can be specified in the WRITE BUFFER Command and the READ BUFFER Command as a Power when expressed as a Power of 2 The IDDs report X 02 2 2 indicating that it is possible to specify the address in 4 byte units Also the Buffer capacity field indicates the byte length of the size of the data buffer which can be operated by the WRITE BUFFER and READ BUFFER commands Exercise caution regardi...

Page 326: ... 4 125 Table 4 125 READ BUFFER command echo buffer descriptor Bit Byte 7 6 5 4 3 2 1 0 0 Reserved EBOS 1 Reserved 2 Reserved Echo Buffer Capacity MSB 3 Echo Buffer Capacity LSB The IDD return one in EBOS field and the IDD verifies that echo buffer data from each initiator is the same as that previously written by the same initiator The Buffer Capacity field returns the size of the echo buffer X 01...

Page 327: ...d in the Logical block address field in the CDB then is terminated without data being transferred to the INIT When a length other than zero which does not match the data format on the disk media is specified in the Transfer byte length field in the CDB this command is terminated with a CHECK CONDITION status without executing a data transfer to the INIT At this time the sense data indicate the fol...

Page 328: ...eration is only 1 data block Also the data transferred from the INIT by this command must have the same order and the same length as the data transferred to the INIT from the IDD by the READ LONG command The Transfer byte length field in the CDB indicates the number of bytes of data transferred from the INIT by this command When the Transfer byte length specification is zero this command is termin...

Page 329: ...E flag and DTE flag are not applied 4 4 7 WRITE SAME 41 Bit Byte 7 6 5 4 3 2 1 0 0 X 41 1 0 0 0 0 0 Pbdata Lbdata RelAdr 2 Logical Block Address MSB 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address LSB 6 0 0 0 0 0 0 0 0 7 Number of Blocks MSB 8 Number of Blocks LSB 9 0 0 0 0 0 0 0 0 This command requests that the device server write the single block of data transferred by th...

Page 330: ...0 A Relative Address RelAdr bit of zero indicates that the Logical Block Address field specifies the first logical block of the range of logical blocks for this command A RelAdr bit of one indicates that the Logical Block Address field is a two s complement displacement But the IDD is not supported this bit Therefore if this bit is one this command is terminated with CHECK CONDITION status ILLEGAL...

Page 331: ... detected in connection with the SAS interface and as a result the command that is currently being executed or the commands in the stack are cleared it generates sense data for the INIT that issued that command Sense data are returned to the INIT at the same time as the status is sent in response to the command 5 1 1 Sense data format The IDD s sense data is in the so called Expanded Sense Data fo...

Page 332: ... should be exercised with regard to the devices connected to the INIT and all the sense data of those devices should be read Table 5 1 Expanded sense data format Bit Byte 7 6 5 4 3 2 1 0 0 Valid X 70 or X 71 Error Code 1 X 00 2 0 0 ILI 0 Sense Key 3 MSB 4 5 Information 6 LSB 7 X 28 Additional Sense Data Length 8 MSB 9 10 Command Inherent Information 11 LSB 12 Additional Sense Code 13 Additional Se...

Page 333: ...ITE LONG command For details refer to the descriptions of these commands Sections 4 4 5 and 4 4 6 4 Sense key This field shows the cause of the sense data being generated More details reasons are indicated in the additional sense code field Byte 12 and the additional sense code qualifier field Byte 13 Table 5 3 shows a list of the meanings of sense keys 5 Information This field shows information r...

Page 334: ...tails of the information shown in this field 8 Additional Sense code Additional Sense code Qualifier The codes which indicate the reason for the error displayed by the sense key in detail are reported in these fields The INIT can decide procedures for error recovery according to the sense key and these fields The sense code and sub sense code are defined in Table 5 4 9 SKSV sense key specific vali...

Page 335: ...ey inherent information a Bit Byte 7 6 5 4 3 2 1 0 15 SKSV 0 0 0 0 0 0 0 16 X 00 17 Number of retries executed b Bit Byte 7 6 5 4 3 2 1 0 15 SKSV 0 0 0 0 0 0 0 16 MSB 17 LSB Progressing rate of formatting or Progressing rate of Self Test operation ...

Page 336: ...ferred in the CDB or the specification in the command Also an error in the LUN specification If the IDD detects an illegal parameter in the CDB it terminates the command without changing the contents of the disk media If an illegal parameter is detected in the parameters transferred from the INIT the contents of the disk media may be changed by that command 6 UNIT ATTENTION A UNIT ATTENTION condit...

Page 337: ...unit in process of becoming ready Disk drive is getting ready The spindle motor is not at its regular rotation speed or has reached its regular rotation speed but is still reading the information 2 02 Logical unit not ready Disk drive is in start command waiting state initializing command required 2 04 Logical unit not ready format in progress The drive cannot be accessed since it is being formatt...

Page 338: ...ead offset A data error was recovered by read retry with offsetting head to negative direction 1 06 Recovered data without ECC data auto reallocated Automatic alternate allocation was applied without ECC correcting a data error 1 17 08 Recovered data without ECC recommended rewrite Rewriting to the same sector was performed without ECC correcting a data error 1 18 00 Recovered Data with Error Corr...

Page 339: ...alue was specified 5 24 00 Invalid field in CDB There is an error in a specification in the CDB 5 25 00 Logical unit not supported An illegal LUN was specified 5 26 00 Invalid field in parameter list There is an error in the parameter list specifications transferred from the INIT during command execution 5 27 00 Write protected A write operation was attempted in a write protected area Or a write o...

Page 340: ...Rounding processing of the MODE SELECT parameter specified by the command was performed 1 03 Logical unit failed Self Test The test segment error occurred during the Self Test 4 3E 04 Logical unit unable to update The IDD failed to update the Self Test result log 4 01 Microcode has been changed Microcode was changed by another INIT 6 02 Changed operating definition Operating definition was changed...

Page 341: ...eout A response to a XFER_RDY frame or Data frame has not been detected for more than 1 ms B 04 NAK Received A NAK primitive is received for a XFER_RDY frame or Data frame B 05 Data Offset Error A Relative Offset error is detected in a Write Data frame B 4B 06 Initiator Response Timeout A response to a Data frame has not been detected for the Initiator Response Timeout in Mode Page 19 B 4C nn Logi...

Page 342: ...er resource 5 5D nn SMART predictive failure SMART related sense data 12 The read error rate attribute has reached the failure threshold 14 The frequency of grown defect allocation attribute has reached the failure threshold 41 The write error rate attribute has reached the failure threshold 43 The seek error rate attribute has reached the failure threshold 56 The spin up time attribute has reache...

Page 343: ...where the error occurred When sense data are generated without relation to the INIT issuing a command this field shows zero 3 Detailed information The information displayed in bytes 20 to 47 of sense data is information defined by Fujitsu for the specific product for the purpose of analyzing trouble and the contents of this information are not made public However the user should present this infor...

Page 344: ...ution termination state and recommended procedures for error recovery processing executed by the INIT in accordance with the results are explained 5 2 1 Termination status analysis and error recovery methods Figure 5 1 shows a model of the INIT s general processing flow from issuing of the command until reception of the termination status END status received Timeout See item 3 GOOD TASK FULL Yes Y...

Page 345: ... to the operating states of the other INITs in the system when deciding it Of the INIT which reserved the IDD falls into a state which it cannot recover from for any reason before the reserved state is released it will be impossible for other INITs to access the IDD because that reserved state will continue In such a case it is necessary for the INIT to take one of the following measures to forcib...

Page 346: ...very processing retried for an error that occurred on the SAS I F or in the disk drive command completion time will be longer than normal 5 2 2 Sense data analysis and error recovery methods The INIT can judge the procedure for error recovery by analyzing the contents of the sense data Table 5 5 the classifications of error information displayed in the sense data are shown and in Table 5 6 the pro...

Page 347: ...ssed 02 Logical unit not ready 2 04 04 Logical unit not ready format in progress None 11 The logical unit specified by the command is currently being formatted so access is impossible 3 03 xx Peripheral device write fault Need 7 Write error recommend reassignament 0C 03 Unrecoverred write error 11 xx Unrecovered read error Need 12 13 00 Sync Mark not found for data field 14 01 No record found Thes...

Page 348: ...ternate blocks exist on the disk drive 4 40 nn Diagnostic failure on component nn Need 13 An error was detected in the IDD s self diagnosis 4 44 nn Internal target failure Need 20 An internal hardware error or a microcode detection error was detected in the IDD 4 4C xx Calibration failed Need 10 C4 xx Drive failure The initial seek was terminated abnormally Or a serious error was detected in the d...

Page 349: ...te fault Need 12 11 xx Unrecovered read error 13 xx Sync byte not found for data field 14 xx Record not found 15 xx Mechanical positioning error B 0E 02 Information Unit Too Long 47 01 Information Unit iuCRC Error Detected Need 6 4B 01 Invalid Target Port Transfer Tag Received 4B 02 Too Much Write Data 4B 03 ACK NAK Time Out 4B 04 NAK Received 4B 05 Data Offset Error An unrecoverable SAS related e...

Page 350: ...al command Retry 2 If it doesn t recover after 10 retries perform recovery method 1 6 1 Reissue the original command Retry 2 If it doesn t recover after 10 retries perform recovery method 3 7 1 Reissue the original command Retry 2 If it doesn t recover after 10 retries perform recovery method 1 8 1 If the DTE flag in the MODE SELECT parameter is 0 perform recovery method 0 2 If the DTE flag in the...

Page 351: ...mmand is terminated abnormally perform recovery method 1 3 When the START STOP UNIT command is terminated normally reissue the original command Retry 11 1 Wait for formatting FORMAT UNIT command to be completed 2 Reissue the original command Retry 12 1 Set the Number of Retries value in the MODE SELECT parameters at the Default value 2 Reissue the original command Retry Note 3 If the error is not ...

Page 352: ...ogramming error of another INIT so when the value in the parameter read in is illegal recovery method 2 should be performed or the operations of the other INITs should be confirmed 17 If the PRIORITY RESERVE command issued by another INIT is proper in the system perform the necessary recovery processing in the system If not perform recovery method 2 18 1 Issue the MODE SENSE or MODE SENSE EXTENDED...

Page 353: ...the parameters read in are illegal recovery method 2 should be performed or the operations of the other INITs should be confirmed 24 1 Issue the READ or READ EXTENDED command and read the data for the block where the error occurred 2 Investigate the cause of the data not matching and perform data recovery processing from the INIT 25 Reissue the original command Retry It is desirable at this time t...

Page 354: ...ude the following information The source which issued the command and the ID of the device which was the target of the command The CDB which was issued The receiving status or when the status was that the command could not be received the code showing the type of error detected by the INIT and its content All bytes reported by the IDD 5 3 Disk Drive Error Recovery Processing This section explains ...

Page 355: ...SC ASCO indicates Sync Mark not found for data field 13 00 or Unrecovered read error 11 01 In this error retry processing rereading accompanied by head offset processing is performed 3 Correctable data read error This error is a correctable ECC error when data are being read Processing methods when this error is detected differ depending on the values specified in the EER flag and DCR flag in the ...

Page 356: ...ck for that data block and executes copying of the alternate block to the data area Alternate block allocation processing is the same as processing with the REASSIGN BLOCKS command Furthermore recovered data copied to the alternate block are data which are read out skipping the ID area if there is an ID area or they are data which have been corrected through the ECC This function is applied once o...

Page 357: ...e data field of the alternate block is verified and the required write data is written in the data field This alternate block allocation is applied with the same processing as that of the REASSIGN BLOCKS command If multiple data blocks are the target blocks of AWRE processing when a single command is executed this function applies to all of these data blocks If an unrecoverable media error MEDIUM ...

Page 358: ...o applied for the sector which has already been re assigned 5 3 3 Error recovery processing control The INIT can by specifying the MODE SELECT parameters can control the error recovery processing retries of the IDD with respect to each type of error related to the disk drive Table 5 7 shows the types of error and the method of specifying the number of retries for those errors for those items where...

Page 359: ...Page Code 21 Number of retries during seek error See Table 5 7 Table 5 7 Disk drive errors and number of retries Item Type of Error Number of Tries Specification Default value 1 Seek Error Number of Retries during a Seek Error 15 2 Data field Read Error of Data field Number of Retries during Read or 63 Number of Retries during Verify 3 Data field Write Error Number of Retries during Write 63 Remar...

Page 360: ...This page is intentionally left blank ...

Page 361: ...drive was shipped from the factory is recorded in this list The defective portions included in this list are permanent defects and when the disk media is initialized it is necessary that this list be used and alternate block processing be executed D List This list includes defect position information specified by the INIT in the FORMAT UNIT command when initializing the disk media C List This list...

Page 362: ...ithin the same cell Alternate cells This is an exclusive cells for allocation of alternate blocks Alternate cells are secured only in the specified quantity in order from the topmost cells Spare sectors in an alternate cell are used only in the case that the spare sectors within each cell are used up and alternate block allocation is not possible within the same cell b Alternate block allocation m...

Page 363: ...d initializing the disk media at times when a data block Verify Certification operation is not prohibited the IDD reads all the initialized data blocks and verifies their normalcy If a defective data block is detected during this processing the IDD generates the C List as defect position information and allocates alternate blocks by alternate sector processing for those defective data blocks In th...

Page 364: ...ued and the format attributes on the disk media are specified The necessary parameters at this time are as follows a Block descriptor The logical data block size byte length is specified in the Data block length field Also when desiring to clearly specify the logical data block count specify that value in the Data block count field If not zero may be specified in the Data block count field In that...

Page 365: ...en operated using the FORMAT UNIT command If it is necessary after reinitialization to restore the data that were stored on the disk media it is necessary to save the data before executing reinitialization then execute data restore using system software after reinitialization The INIT can change the size of the spare sector area and its location as well as the number of logical data blocks before ...

Page 366: ...ved and the defect position information for the defective data blocks detected in the Verify operation is added to the G List During initialization alternate blocks for which sector slip processing was applied for previously known defects are reallocated so optimization of the logical data block locations on the disk media can be expected b Specify 0 in the FmtData bit and in the CmpLst bit and 00...

Page 367: ...dure described below it next reads those data or verifies the data blocks by executing Verify 1 Setting parameters by the MODE SELECT command Issue the MODE SELECT or the MODE SELECT EXTENDED command and prohibit retry processing data correction and operation of the Read Ahead Cache feature The necessary parameter settings are as shown below a Read Write Error Recovery Parameters Page 1 AWRE 0 ARR...

Page 368: ...nate 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 The procedure for alternate block processing is shown below An attempt will be made to cop...

Page 369: ...registered as an addition to the defect list G List Therefore when reinitializing the hard disk with the FORMAT UNIT command see Section 6 2 2 if use of the G List is specified defect processing can be performed which reflects the operation results up to that time Also since Alternate sector processing is applied in alternate block allocation in the REASSIGN BLOCKS command the physical connectivit...

Page 370: ...This page is intentionally left blank ...

Page 371: ...itiates input and output operations on the FC bus In this manual initiator has been abbreviated to INIT Sense Data When several items of error information are included in a command s completion status this is information generated by the target for reporting detailed information on that status Sense Key This is a 4 bit code displayed in the sense data It contains information for classifying the ty...

Page 372: ...This page is intentionally left blank ...

Page 373: ...ect Current DCR Disable Correction DCRT Disable CeRtificaTion DE Disk Enclosure DEF DEFective block DevOfi Device Offine DPO Disable Page Out DPRY Disable PRimarY DSP Disable Saving Parameters DTDC Data Transfer Disconnect Control DTE Disable Transfer on Error E ECC Error Correction Code EER Enable Early Recovery EVPD Enable Vital Product Data F FC Fibre Channel FG Frame Ground FIFO First In First...

Page 374: ...Read Continuous RCD Read Cache Disable REQ Request RH Relative Humidity RMB ReMovaBle RST ReSeT RSV ReSerVed S S N Serial Number SBd Synchronized Byte data area SBi Synchronized Byte identifier area SCSI Small Computer System Interface SCT SeCTor SEL SELect SelfTest Self Test SG Signal Ground SP Save Page SPR SPaRe block SR Servo SSEC Soft sector STPF Stop sector SURF SURFace T TB Transfer Block T...

Page 375: ...t zone 4 38 alternate sector processing 6 2 alternate track count drive 4 38 alternate track count zone 4 38 analysis of termination status 5 14 application client page X 0F 4 111 arbitration fairness 1 47 arbitration in progress 1 27 ARRE 4 27 auto alternate block allocation processing 5 26 6 3 auto alternate block allocation processing during read operation 5 26 auto alternate block allocation p...

Page 376: ...on overview 1 46 connection request 1 46 connection request aborting 1 49 connection response 1 47 connection breaking 1 51 connection closing 1 50 control byte 2 5 control command 4 1 control mode parameter 4 51 correctable bit length 4 29 4 44 correctable data read error 5 25 correction of defect descriptor 4 160 count basis 4 95 CREDIT_BLOCKED 1 34 cylinder count 4 42 cylinder skew factor 4 40 ...

Page 377: ...e changed 2 9 DS 4 90 DTE 4 28 DU 4 90 DWS 1 23 E EAERP 4 54 EBF 4 65 echo buffer 4 185 4 189 echo buffer descriptor 4 190 EER 4 28 element scope 4 124 enable background function 4 65 enable early recovery 4 28 enable threshold comparison 4 90 enable vital product data 4 3 enable warning 4 65 end of address frame 1 29 end of frame 1 36 ending boundary 4 57 EOAF 1 29 EOF 1 36 ERROR 1 29 error code ...

Page 378: ...immediate 4 151 incorrect length indicator 5 3 information 5 3 information unit 1 61 information unit supported bit 4 8 informational exception control page 4 64 INIT error recovery method 5 14 initialization during installation 6 4 initiator control enable 4 47 INQUIRY 12 4 2 INQUIRY command 2 11 interleave factor 4 39 interlocked frame 1 53 INTERMEDIATE CONDITION MET status 2 7 INTERMEDIATE stat...

Page 379: ...meter configuration 4 70 MODE SELECT parameter 4 24 read write error recovery parameter 4 26 MODE SELECT parameter 4 37 4 41 4 43 4 45 4 51 4 55 4 64 4 68 MODE SELECT parameter of IDD 4 24 MODE SELECT parameter structure 4 19 MODE SENSE 1A 4 71 MODE SENSE command parameter configuration 4 75 MODE SENSE data type specification 4 73 MODE SENSE EXTENDED 5A 4 78 MODE SENSE EXTENDED command parameter c...

Page 380: ...ISTENT RESERVE IN 5E 4 119 PERSISTENT RESERVE IN parameter data for READ KEYS 4 121 PERSISTENT RESERVE IN parameter data for READ RESERVATIONS 4 122 PERSISTENT RESERVE IN service action 4 120 PERSISTENT RESERVE OUT 5F 4 126 PERSISTENT RESERVE OUT parameter list 4 129 PERSISTENT RESERVE OUT service action 4 128 PERSISTENT RESERVE OUT service action and valid parameter 4 130 PERSISTENT RESERVE OUT s...

Page 381: ...CEIVE DIAGNOSTIC RESULTS response data 4 177 4 178 recovery procedures for disk drive error 2 16 recovery time limit 4 30 4 44 reference temperature 4 107 re initialization 6 5 RELEASE 17 4 84 RELEASE EXTENDED 57 4 85 release function 4 84 release object 4 84 removable medium 4 40 report check 4 54 REPORT DEVICE IDENTIFIER A3 4 133 REPORT DEVICE IDENTIFIER parameter list 4 134 report log exception...

Page 382: ...nse key specific valid 5 4 SET DEVICE IDENTIFIER A4 4 135 SET DEVICE IDENTIFIER parameter list 4 136 setting parameter by MODE SELECT command 6 7 SIZE 4 47 size enable 4 47 SKSV 5 4 SMART data page X 38 4 118 SMART status page X 2F 4 118 SOAF 1 33 SOF 1 36 soft sectoring 4 40 soft write protect 4 54 spare sector area 6 2 spare sector within cell 6 2 specified cycle count over device lifetime 4 109...

Page 383: ...ck count 2 4 transfer byte length 2 5 4 3 transfer data length 2 4 transport layer 1 58 TSD 4 90 TST 4 52 U UAAERP 4 54 UNIT ATTENTION condition 2 9 UNIT ATTENTION condition multiple hold 2 11 unrecoverable hardware error 2 20 usage of special character 1 11 user space logical block address 2 23 V valid 5 3 vefiry error recovered with possible delay 4 103 vendor ID field 4 7 vendor unique 2 5 VERI...

Page 384: ...This page is intentionally left blank ...

Page 385: ...26294 1 FAX 39 2 26294 201 FUJITSU FRANCE S A 1 Place des Etats Unis SILIC 310 94588 Rungis Cedex FRANCE TEL 33 1 41 80 38 80 FAX 33 1 41 80 38 66 FUJITSU ICL ESPAÑA S A Almagro 40 28010 Madrid SPAIN TEL 34 91 581 8000 FAX 34 91 581 8300 FUJITSU AUSTRALIA LIMITED 2 Julius Avenue Cnr Delhi Road North Ryde N S W 2113 AUSTRALIA TEL 61 2 9776 4555 FAX 61 2 9776 4556 FUJITSU HONG KONG LTD 10 F Lincoln ...

Page 386: ...This page is intentionally left blank ...

Page 387: ...aluate overall quality of this manual by marking in the appropriate boxes Good Fair Poor Good Fair Poor Good Fair Poor Organization Use of examples Legibility Accuracy Index coverage Handiness Binding Clarity Cross referencing Others Figures tables General appearance Technical level Too high Appropriate Too low Overall rating of this publication Good Fair Poor FOR FUJITSU USE Overseas office Perso...

Page 388: ...This page is intentionally left blank ...

Page 389: ... MAV2036RC MAV2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS C141 C009 01EN MAU3036RC MAU3073RC MAU3147RC SERIES MAV2036RC MAV2073RC SERIES DISK DRIVES SERIAL ATTACHED SCSI INTERFACE SPECIFICATIONS C141 C009 01EN ...

Page 390: ...This page is intentionally left blank ...

Page 391: ......

Page 392: ......

Reviews:

No comments

Related manuals for MAU3036RC SERIES

Danfoss Native BACnet VLT HVAC Drive Operating Instructions Manual preview
Native BACnet VLT HVAC Drive
Brand: Danfoss Pages: 31
Cole Parmer MASTERFLEX L/S 7523-40 Operating Manual preview
MASTERFLEX L/S 7523-40
Brand: Cole Parmer Pages: 23
Nord Drivesystems SK 750E Series Manual preview
SK 750E Series
Brand: Nord Drivesystems Pages: 153
Siemens SINAMICS GM150 Operating And Installation Instructions preview
SINAMICS GM150
Brand: Siemens Pages: 258
Veichi SD710 Series User Manual preview
SD710 Series
Brand: Veichi Pages: 520
Altec Lansing HF DRIVER - REPAIR Repair preview
HF DRIVER - REPAIR
Brand: Altec Lansing Pages: 5
StepperOnline DM860N User Manual preview
DM860N
Brand: StepperOnline Pages: 12
SKS Sweden Bonfiglioli Vectron Agile Communications Manual preview
Bonfiglioli Vectron Agile
Brand: SKS Sweden Pages: 104
Metronix ARS 2320 FS Product Manual And Mounting Instructions preview
ARS 2320 FS
Brand: Metronix Pages: 84
YASKAWA Sigma-V JUSP-MD D A Series User Manual preview
Sigma-V JUSP-MD D A Series
Brand: YASKAWA Pages: 324
YASKAWA CACP-JU series User Manual preview
CACP-JU series
Brand: YASKAWA Pages: 340
WEG CFW-09 Installation Manual preview
CFW-09
Brand: WEG Pages: 2
Coolmay C100E Manual preview
C100E
Brand: Coolmay Pages: 99
Küenle KFU 2 Series Manual preview
KFU 2 Series
Brand: Küenle Pages: 254
ICAN SS57 User Manual preview
SS57
Brand: ICAN Pages: 15
Zenith SM-H-17-4 Service Manual preview
SM-H-17-4
Brand: Zenith Pages: 12
Xinje VB3 User Manual preview
VB3
Brand: Xinje Pages: 107
YASKAWA SGM series Safety Precautions preview
SGM series
Brand: YASKAWA Pages: 35

Brands by name

Popular brands

Load more brands