1. DL manuals
  2. Quantum
  3. Storage
  4. LTO-4 (Model B)
  5. User Manual

Quantum LTO-4 (Model B) User Manual

Manual is about: Quantum LTO 3: User Guide

Summary of LTO-4 (Model B)

  • Page 2

    Copyright © 2008 quantum. All rights reserved document number: 200201090-001 revision b quantum and the quantum logo are trademarks of quantum. Other product names are trademarks or registered trademarks of their owners. Linear tape-open, lto, the lto logo, ultrium, and the ultrium logo are trademar...

  • Page 3

    Important information about this manual all information contained in or disclosed by this document is proprietary to quantum. By accepting this material, the recipient agrees that this material and the information contained therein are held in confidence and in trust and will not be used, reproduced...

  • Page 4: Contents

    Contents page iii contents important information about this manual ........................................................................................................................... Ii contents.....................................................................................................

  • Page 5

    Contents page iv 3.1.1 scsi command conventions ...................................................................................................................... 23 3.2 scsi command descriptor blocks ..................................................................................................

  • Page 6

    Contents page v 3.10.3 mode parameter header .............................................................................................................................. 80 3.10.4 mode select block descriptor.............................................................................................

  • Page 7

    Contents page vi 3.19.4 echo buffer descriptor .............................................................................................................................. 143 3.19.5 echo buffer...........................................................................................................

  • Page 8

    Contents page vii 3.31.7 supported key formats page..................................................................................................................... 188 3.31.8 data encryption management capabilities page...............................................................................

  • Page 9: 1  Introduction

    Introduction page 1 1 introduction the quantum lto drives are designed for computer environments requiring high performance, ultra-high capacity data storage. The drives are available in 5.25-inch internal configurations or as an external subsystem. Quantum lto drives incorporate an embedded control...

  • Page 10

    Introduction page 2 added an additional tapealert in log page 0x2e for lto-4 tape alert 0x07 media life report density support data: lto3 will report formats of lto1, lto2 & lto3 lto4 will report formats of lto2, lto3 & lto4 security protocol in command only supported by lto4. Security protocol out ...

  • Page 11: 2  Interface Overview

    Scsi interface overview page 3 2 interface overview this chapter discusses interface elements as they pertain to drive functions. Three interfaces are offered. Depending upon the model selected the quantum lto drives interface to either the small computer system interface (scsi) bus, or the serial a...

  • Page 12

    Scsi interface overview page 4 data transfers at 300 megabytes per second sas differential signaling provides high noise immunity one sas port using single bidirectional phy full duplex operation sas target phy transport layer error handling 2.2.2 sas protocol serial attached scsi communicates using...

  • Page 13

    Scsi interface overview page 5 when spacing, locating, or generally performing any tape motion when data cannot be transferred on the scsi bus. During the time the target is disconnected for one of these functions, the bus is free for use by other devices. The target initiates both disconnect and re...

  • Page 14

    Scsi interface overview page 6 message hex code definition extended message 01h see page 11 for a description of extended message support identify 80h+ an identify in message is sent to the initiator during reconnect to indicate which logical unit is reconnecting. The disconnect privilege and luntar...

  • Page 15

    Scsi interface overview page 7 message hex code definition no operation 08h this message has no effect and is ignored. 2.3.6 extended messages the following table lists extended scsi messages and their definitions. Hex code message definition synchronous data transfer request 01h this message negoti...

  • Page 16

    Scsi interface overview page 8 state or phase description arbitration phase the drive does not detect nor react to parity errors on the scsi bus while arbitration is being performed. Selection phase the drive does not detect nor react to parity errors on the scsi bus while the drive is being selecte...

  • Page 17

    Scsi interface overview page 9 an initiator that accommodates disconnect/reconnect can indicate this capability to the tape drive during the selection phase by asserting both its own initiator scsi id bit as well as the tape drive’s scsi id bit (allows the tape drive to know with which initiator to ...

  • Page 18

    Scsi interface overview page 10 in phase during which atn is raised message save data pointers (02h) restore pointers (03h) disconnect (04h) reject message (07h) identify (80h) command complete (00h) ignore wide residue (23h) else 5 if no status, 5 else 5 else 13 else 5 else 5 nop (08h) 9 9 9 9 9 2 ...

  • Page 19

    Scsi interface overview page 11 2.3.9.1 action codes in message exception handling tables 1. Disconnect message case - the drive will not disconnect for the rest of the command. Ppr message case - both the initiator and the drive go to asynchronous mode and 8-bit narrow. Sdtr message case - both the...

  • Page 20

    Scsi interface overview page 12 2.4 fibre channel interface overview the drive’s fibre channel protocol, (fcp), interface consists of two independent nl_ports, each of which is a bi-directional 1.0625, 2.125, or 4.250 ghz serial connection. The ports perform automatic speed negotiation to operate at...

  • Page 21

    Scsi interface overview page 13 read link error status block (rls) registered state change notification (rscn) report node capabilities information (rnc) report node fc-4 types (rnft) report port speed capabilities (rpsc) request node identification data (rnid) read port list (rpl) read port status ...

  • Page 22

    Scsi interface overview page 14 2.5 standards conformance the small computer system interface and fibre channel interface are is described in standards including several versions and a number of individual documents. The original small computer system interface standard, x3.131-1986, is referred to ...

  • Page 23

    Scsi interface overview page 15 serial attached scsi – 1.1 (sas-1.1) incits 417-2006 serial attached scsi – 2 (sas-2) in development 2.5.2 incits technical committee t11 (device level interfaces) standards fibre channel – arbitrated loop – 2 amendment (fc-al-2) ncits.332:1999 fibre channel – arbitra...

  • Page 24

    Scsi interface overview page 16 2.7 general behaviors 2.7.1 reset condition when a reset is issued to the tape drive, the drive clears all uncompleted commands, releases all scsi device reservations, and sets the tape drive to default modes. The parallel scsi drive returns to the bus free phase. 2.7...

  • Page 25

    Scsi interface overview page 17 2.7.4 buffered mode buffered mode allows the most efficient operation of a tape drive. The drive defaults to buffered mode. In this mode, the drive signals command complete when all requested data for a write command has been transferred from the host to the tape driv...

  • Page 26

    Scsi interface overview page 18 1. The command completes with a check condition and a 40h sense data indicating eom and no sense key. 2. Subsequent write commands write data and complete with check condition with eom status and no sense key until the physical tape end is encountered. 2.7.8 error rep...

  • Page 27

    Scsi interface overview page 19 the tape with different block sizes in the fixed mode. Also, the host may change the block size after bom, allowing on-the-fly block-size changes. The read command fixed bit also specifies fixed or variable mode. When reading in variable mode, the host must know the s...

  • Page 28

    Scsi interface overview page 20 only power on situations, but also how cleaning tapes, incompatible tapes and firmware tapes are handled. • powering on or power cycling while the tape is inside the drive. • cleaning tape has finished the cleaning cycle. • unsupported data tape has been loaded. • uns...

  • Page 29

    Scsi interface overview page 21 and is defined in the adc-2 standard. The automation device configures bridging via the adc device server presented on the adt port..

  • Page 30: 3  Scsi Commands

    Scsi commands: 13bscsi command set page 22 3 scsi commands this chapter describes the scsi commands for the lto tape drive. 3.1 scsi command set the following table shows the scsi commands for sequential access devices implemented by the drive. Group code service action command page 0 00h test unit ...

  • Page 31

    Scsi commands: 14bscsi command descriptor blocks page 23 5 a3h 05h report device identifier 158 5 a3h 0ch report supported operation codes 162 5 a3h 0dh report supported task management functions 166 5 a4h 06h set device identifier 209 5 b4h security protocol out (lto4 drives) 195 3.1.1 scsi command...

  • Page 32

    Scsi commands: 14bscsi command descriptor blocks page 24 byte bits 7 6 5 4 3 2 1 0 8 command dependent 9 control scsi 12-byte command descriptor blocks are arranged in the format shown in the following table. Byte bits 7 6 5 4 3 2 1 0 0 operation code 1 ignored lun service action 2 command dependent...

  • Page 33

    Scsi commands: 14bscsi command descriptor blocks page 25 3.2.2 scsi command operation code format byte bits 7 6 5 4 3 2 1 0 0 group code command code 3.2.2.1 scsi command field descriptions field byte bits description group code 0 5-7 the scsi command group. Command code * 0 0-4 the scsi command cod...

  • Page 34

    Scsi commands: 15bscsi command status page 26 3.3 scsi command status when the tape drive competes a command it responds with a status byte. The format of the status byte is shown below. 3.3.1 scsi status byte format byte bits 7 6 5 4 3 2 1 0 0 reserved status code 3.3.1.1 scsi status byte field des...

  • Page 35

    Scsi commands: 16berase page 27 3.4 erase the erase command marks the tape, from the current position to the end of tape, as erased. 3.4.1 erase command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (19h) 1 ignored lun reserved immed long 2 reserved 3 reserved 4 reserved 5 control 3.4....

  • Page 36

    Scsi commands: 16berase page 28 3.4.2 erase completion status code message description 00h good status • the drive remains in any previously set modes. • the drive is ready to perform any appropriate command. Note: if immed is one, then good status only indicates that the command is valid. 02h check...

  • Page 37

    Scsi commands: 17binquiry page 29 3.5 inquiry the inquiry command requests that the drive return information about itself. If an inquiry command is received from an initiator with a pending unit attention condition (before the drive reports check condition status), the drive performs the inquiry com...

  • Page 38

    Scsi commands: 17binquiry page 30 if the enable vital product data (evpd) and command support data (cmddt) bits are clear and the page code is zero, standard inquiry data is returned. If the enable vital product data (evpd) flag is set and the page code is zero, the supported vital product data page...

  • Page 39

    Scsi commands: 17binquiry page 31 field bytes bits description naca 3 5 0 = normal aca (naca) is not supported (parallel scsi drives) 1 = normal aca (naca) is supported (sas & fibre channel drives) hisup 3 4 always 0, indicating hierarchical support is not supported. Response data format 3 0-3 alway...

  • Page 40

    Scsi commands: 17binquiry page 32 the standard inquiry data is based on the scsi 3 standard for standard inquiry data. This allows for setting certain bits in byte 6 to indicate features that were non-standard in scsi 2. The only supported scsi 3 field is multi port (multip). The multi-port (multip)...

  • Page 41

    Scsi commands: 17binquiry page 33 field bytes bit s description supported vital product data page code 4 always 00h, the page code of the supported vital product data inquiry page unit serial number page code 5 always 80h, the page code of the unit serial number page device identification page code ...

  • Page 42

    Scsi commands: 17binquiry page 34 field bytes bits description page length 3 lto3 full height form factor drives always 0ch to indicate 12 additional bytes of data. Lto3 half height form factor drives always 0eh to indicate 14 additional bytes of data. Drive serial number 4-18 14 bytes of ascii data...

  • Page 43

    Scsi commands: 17binquiry page 35 3.5.5.3 device identification page field descriptions field bytes bits description code set 0 0-3 1 = identification descriptor contains binary data. 2 = identification descriptor contains ascii data. Identifier type 1 0-3 1 = identification descriptor is vendor id ...

  • Page 44

    Scsi commands: 17binquiry page 36 3.5.6.1 sequential access device capabilities page field descriptions field bytes bits description peripheral qualifier 0 5-7 always 000b. Peripheral device type 0 0-4 01h, indicating a sequential access device. Page code 1 b0h = sequential access device capabilitie...

  • Page 45

    Scsi commands: 17binquiry page 37 field bytes bits description date 49–72 24 bytes of ascii data, “yyyy/mm/dd” yyyy = 4 digits of year mm = 2 digits of month dd = 2 digits of day variant 73–95 23 bytes of ascii data 3.5.8 drive component serial number page (c2, c3, c4, c5, c6h) the drive component s...

  • Page 46

    Scsi commands: 17binquiry page 38 byte bits 7 6 5 4 3 2 1 0 3 reserved 4 reserved 5 cdb size (n-5) 6 cdb usage data n cdb usage data 3.5.9.1 command support data field descriptions field bytes bits description peripheral qualifier 0 5-7 always 000b. Peripheral device type 0 0-4 normally 01h to indic...

  • Page 47

    Scsi commands: 18bload unload page 39 3.6 load unload the load unload command may be used to load or unload a cartridge. This command may also be used to request that the retension function be performed. 3.6.1 load unload command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (1bh) 1 ig...

  • Page 48

    Scsi commands: 18bload unload page 40 3.6.1.2 medium loadable position hold reten load description 0 0 0 no action taken, good status is returned. 0 0 1 load the medium to the loaded position. The medium will be ready at bom. 0 1 0 check condition, sense data 02/3a/03. 0 1 1 load the medium to the l...

  • Page 49

    Scsi commands: 18bload unload page 41 if the immediate (immed) bit is one, then the drive validates the command and waits for any previous command from any host to complete, including any immediate commands currently being processed, and for any buffered data to be flushed to tape. It will then repo...

  • Page 50

    Scsi commands: 19blocate page 42 3.7 locate the locate command moves to a specified position on the tape. Before the locate operation is performed, all buffered data and filemarks are transferred to tape. On completion, the logical position is before the specified location. 3.7.1 locate command desc...

  • Page 51

    Scsi commands: 19blocate page 43 3.7.2 locate completion status code message description 00h good status the tape is positioned to the logical block address specified. The drive remains in any previously set mode. The drive is ready to perform any appropriate command. Note: if immed is one, then goo...

  • Page 52

    Scsi commands: 20blog select page 44 3.8 log select the log select and log sense commands work in conjunction to allow the host to control and obtain statistical information about cartridge usage and error rates. This information consists of counters of particular events. The log select command is u...

  • Page 53

    Scsi commands: 20blog select page 45 field bytes bits description parameter list length 7-8 always 0. Specifies the length (in bytes) of the parameter list to be transferred during the data out phase. A 0 length indicates that no parameter data is to be transferred. Reserved all reserved bits must b...

  • Page 54

    Scsi commands: 20blog select page 46 3.8.2.3 log parameters field descriptions field bytes bits description parameter code 0-1 identifies the log parameter. Log parameters are always in ascending order. Disable update (du) 2 7 0 = enables update of accumulated value when the corresponding event occu...

  • Page 55

    Scsi commands: 20blog select page 47 log page see page tape device statistics log page (3eh) 77 3.8.2.4 log parameter maximum counts the maximum value of each counter depends on the size of the counter in bytes. When the maximum count is reached, the du bit in the parameter control byte for the coun...

  • Page 56

    Scsi commands: 21blog sense page 48 3.9 log sense the log select and log sense commands work in conjunction to allow the host to control and obtain statistical information about cartridge usage and error rates. This information consists of counters of particular events. Log sense data is obtained by...

  • Page 57

    Scsi commands: 21blog sense page 49 field bytes bits description page code 2 0-5 00h = requests supported log pages log 02h = requests write error counters log 03h = requests read error counters log 0ch = requests sequential access device log 0dh = requests temperature log 12h = requests tape alert ...

  • Page 58

    Scsi commands: 21blog sense page 50 if the parameter pointer field is set to 0, all parameters for that particular page are returned up to the maximum number of bytes specified in the allocation length. Regardless of the starting parameter code specified in the parameter pointer field, the page head...

  • Page 59

    Scsi commands: 21blog sense page 51 3.9.3.1 log page header byte bits 7 6 5 4 3 2 1 0 0 reserved page code 1 reserved 2 (msb) 3 page length (lsb) 3.9.3.2 log page field descriptions field bytes bits description page code 0 0-5 identifies the page being returned. Page length 2-3 indicates the length ...

  • Page 60

    Scsi commands: 21blog sense page 52 list parameter (lp) 2 0 always 0, indicating that all log parameters are data counters. Parameter length 3 n – 3, indicating the length of the parameter value. Parameter value 4 – n the parameter value is the actual data requested. Reserved always 0. 3.9.4 support...

  • Page 61

    Scsi commands: 21blog sense page 53 3.9.4.1 supported log page field descriptions field bytes bits description page code 0 0-5 page length 2-3 always 10h, indicating the page length. Supported log pages log 4 always 00h, the page code of the supported log pages log page write error counters log 5 al...

  • Page 62

    Scsi commands: 21blog sense page 54 3.9.5 write error counters log page (02h) the write error counters log page records write errors. The parameters on this page can be reset to zero with the log select command. Page code page length 02h 38h parameter description length 0 errors corrected without su...

  • Page 63

    Scsi commands: 21blog sense page 55 3.9.6 read error counters log page (03h) the read error counters log page records read errors. The parameters on this page can be reset to zero with the log select command. Page code page length 03h 38h parameter description length 0 errors corrected without subst...

  • Page 64

    Scsi commands: 21blog sense page 56 3.9.8 temperature log page (0dh) the temperature log page reports the drive temperature at the time the log sense command is issued. The maximum operating temperature is also reported as the reference temperature. The parameters may not be set to zero or changed w...

  • Page 65

    Scsi commands: 21blog sense page 57 3.9.9 tapealert response log page (12h) the tapealert response log page supports the automation/drive interface standards to provide the tapealert flags also reported in log page 2eh. The parameters may not be set to zero or changed with the use of a log select co...

  • Page 66

    Scsi commands: 21blog sense page 58 3.9.10 device statistics log page (14h) the device statistics log page defines data counters associated with utilization of the tape drive. All parameters are persistent across a power cycle. The parameters may not be set to zero or changed with the use of a log s...

  • Page 67

    Scsi commands: 21blog sense page 59 notes: 1. Drives support their native medium type and density code and the types of the previous two lto specifications. The supported worm types will also be reported. 2. Temperature parameter codes are only reported on drives with temperature sensors. 3. Paramet...

  • Page 68

    Scsi commands: 21blog sense page 60 3.9.10.3.1 medium type parameter bit byte 7 6 5 4 3 2 1 0 0 reserved 1 reserved 2 density code 3 medium type 4 (msb) 7 media motion hours (lsb) 3.9.10.4 temperature type log parameter bit byte 7 6 5 4 3 2 1 0 0 (msb) 1 parameter code (8002h) (lsb) 2 du (0b) obsole...

  • Page 69

    Scsi commands: 21blog sense page 61 indicating multiple error events. Up to sixteen parameters are reported; each one has a different parameter code, from zero to fifteen. The error events are recorded in non-volatile memory and can be retrieved even after the drive has been reset or power cycled. I...

  • Page 70

    Scsi commands: 21blog sense page 62 multi-byte numeric fields are in big-endian format. Each field records the specified data at the time the event occurred. If the repeat bit is set, then the parameter indicates that the specified event occurred multiple times in succession without any other event ...

  • Page 71

    Scsi commands: 21blog sense page 63 3.9.12 protocol specific port log page (18h) - sas drives only the protocol specific port log page is used to report errors that have occurred on the sas target device’s phy(s). Page code page length 18h 38h bits byte 7 6 5 4 3 2 1 0 0 reserved page code (18h) 1 r...

  • Page 72

    Scsi commands: 21blog sense page 64 bits byte 7 6 5 4 3 2 1 0 51 (lsb) 52 (msb) 55 loss of dword synchronization (lsb) 56 (msb) 59 phy reset problem (lsb) multi-byte numeric fields are in big-endian format. Each field records the specified data at the time the event occurred. If the repeat count is ...

  • Page 73

    Scsi commands: 21blog sense page 65 invalid dword count 44-47 number of invalid dwords that have been received outside of phy reset sequences running disparity error count 48-51 number of dwords containing running disparity errors that have been received outside of phy reset sequences loss of dword ...

  • Page 74

    Scsi commands: 21blog sense page 66 3.9.13 tapealert log page (2eh) the tapealert log page provides information about errors and the status of the drive and media. Page code page length 2eh 140h all parameters are one byte long. Each parameter is either zero to indicate the corresponding condition h...

  • Page 75

    Scsi commands: 21blog sense page 67 num b er flag type required host message cause 7 media life w the tape cartridge has reached the end of its calculated useful life: 1. Copy any data you need to another tape. 2. Discard the old tape. The media has exceeded its specified life. 9 write protect c you...

  • Page 76

    Scsi commands: 21blog sense page 68 num b er flag type required host message cause 20 clean now c the tape drive needs cleaning: 1. If the operation has stopped, eject the tape and clean the drive. 2. If the operation has not stopped, wait for it to finish and then clean the drive. Check the tape dr...

  • Page 77

    Scsi commands: 21blog sense page 69 num b er flag type required host message cause 51 tape directory invalid at unload w the tape directory on the tape cartridge just unloaded has been corrupted. File search performance will be degraded. The tape directory can be rebuilt by reading all the data. Err...

  • Page 78

    Scsi commands: 21blog sense page 70 flag condition setting flag condition clearing flag flag name 6 asc/ascq per error list rewind or unload write failure 7 media life threshold breech of lifetime specified loads or lifetime specified usage hours. Media removal media life 9 received one of the follo...

  • Page 79

    Scsi commands: 21blog sense page 71 flag condition setting flag condition clearing flag flag name 22 cleaning tape cartridge out of cleaning tape successful clean cycle expired cleaning media 23 cleaning tape mic: page bad; not supported; not recognized media removal invalid cleaning tape 26 detecte...

  • Page 80

    Scsi commands: 21blog sense page 72 as c/as cq drive m o de fl ag 3 hard error fl ag 5 read fa ilure fl ag 6 write fa ilure description 03/03/02 write x x excessive write errors 03/09/00 read x x track following error 03/09/00 write x x track following error 03/09/00 position x track following error...

  • Page 81

    Scsi commands: 21blog sense page 73 page code page length 30h 5ah parameter description length 1 thread count 4 2 total data sets written 8 3 total write retries 4 4 total un-recovered write errors 2 5 total suspended writes 2 6 total fatal suspended writes 2 7 total data sets read 8 8 total read re...

  • Page 82

    Scsi commands: 21blog sense page 74 3.9.16 data compression log page (32h) the data compression log page records compression information. The parameters on this page can be reset to zero with the log select command page code page length 32h 4ch parameter description length 0 read compression ratio i...

  • Page 83

    Scsi commands: 21blog sense page 75 each event is 82 bytes in length, including the four-byte parameter header, as shown below. Bits byte 7 6 5 4 3 2 1 0 0 (msb) 1 parameter code (lsb) 2 du (0) ds (1) tsd (0) etc (0) tmc (00b) lbin (1) lp (0) 3 parameter length (4eh) 4 (msb) 7 power on hours (lsb) 8...

  • Page 84

    Scsi commands: 21blog sense page 76 message code 2 the message code reported for the event. These values are defined in this manual in appendix a: message codes. Repeat count 4 the number of times in succession that this event occurred without a different event occurring. Thread count 4 the number o...

  • Page 85

    Scsi commands: 21blog sense page 77 3.9.20 tape device statistics log page (3eh) the tape device statistics log page defines data counters associated with both the tape drive and the tape cartridge. All drive parameters are persistent across a power cycle. All media parameter follow the currently lo...

  • Page 86

    Scsi commands: 22bmode select page 78 3.10 mode select the mode select command allows the host to assign device parameters to the drive. After a power-on or scsi reset condition, the drive sets its device parameters to the default values. By issuing a mode select command, the host can change the dev...

  • Page 87

    Scsi commands: 22bmode select page 79 field bytes bits description parameter list length 4 specifies the number of bytes in the mode select parameter list to be transferred from the host to the drive. A value of 0 is a valid entry and indicates no data. Reserved all reserved bits must be 0. Control ...

  • Page 88

    Scsi commands: 22bmode select page 80 3.10.2 mode select parameters the mode select parameter list, for both the mode select(6) and mode select(10) commands is in the following general format: mode parameter header the mode parameter header is required. Block descriptor the block descriptor is optio...

  • Page 89

    Scsi commands: 22bmode select page 81 3.10.3.3 mode select(10) parameter header byte bits 7 6 5 4 3 2 1 0 0 (msb) 1 mode data length (lsb) 2 medium type 3 wp buffered mode speed 4 reserved 5 reserved 6 (msb) 7 block descriptor length (lsb) 3.10.3.4 mode select(10) parameter header field descriptions...

  • Page 90

    Scsi commands: 22bmode select page 82 3.10.4.1 block descriptor field descriptions field bytes bits description default = 7fh lto4 drive lto3 drive lto2 = 42h (read only) lto1 = 40h (read only) lto3 = 44h lto2 = 42h lto4 = 46h lto3 = 44h density code 0 no change = 00h block length 5-7 0 = variable l...

  • Page 91

    Scsi commands: 22bmode select page 83 3.10.5.1 mode parameter pages field descriptions field bytes bits description page code 0 0-5 02h = disconnect/reconnect mode page 0ah = control mode page 0fh = data compression control mode page 10h = device configuration mode page 18h = protocol specific logic...

  • Page 92

    Scsi commands: 22bmode select page 84 3.10.6 disconnect/reconnect mode page (02h) 3.10.6.1 disconnect/reconnect mode page (02h) for sas the sas disconnect/reconnect mode page contains the following parameters. Byte bits 7 6 5 4 3 2 1 0 0 reserved page code (02h) 1 additional page length (0eh) 2 rese...

  • Page 93

    Scsi commands: 22bmode select page 85 field bytes bits description maximum burst size 10-11 for read data, the value in the maximum burst size field contains the maximum amount of data that is transferred during a connection by an ssp target port per i_t_l_q nexus without transferring at least one f...

  • Page 94

    Scsi commands: 22bmode select page 86 the sas disconnect/reconnect mode page parameters are listed below. Field bytes bits description page code 0 0-5 always 02h, indicating the disconnect/reconnect page additional page length 1 always 0eh, indicating that 14 parameter bytes follow the page length b...

  • Page 95

    Scsi commands: 22bmode select page 87 3.10.6.3 disconnect/reconnect mode page (02h) for spi the spi, (scsi parallel interface), disconnect/reconnect mode page contains the following parameters. Byte bits 7 6 5 4 3 2 1 0 0 reserved page code (02h) 1 additional page length (0eh) 2 reserved 3 reserved ...

  • Page 96

    Scsi commands: 22bmode select page 88 3.10.7 control mode page (0ah) the control mode page specifies whether the drive generates a check condition when any log parameter reaches maximum. (refer to the log select command and the log sense command.) it also specifies whether tagged queuing is used and...

  • Page 97

    Scsi commands: 22bmode select page 89 field byte s bits description rac 4 6 always 0, indicating that drive may return long busy condition in place of report a check condition. Swp 4 3 always 0, indicating unsupported software write protect. Auto load mode 5 0-2 000b = load inserted medium for full ...

  • Page 98

    Scsi commands: 22bmode select page 90 3.10.8 data compression control mode page (0fh) the data compression control mode page specifies whether or not data is compressed during write commands and whether or not data is decompressed during read commands. Byte bits 7 6 5 4 3 2 1 0 0 reserved page code ...

  • Page 99

    Scsi commands: 22bmode select page 91 3.10.9 sequential access device configuration mode page (10h) the device configuration mode page specifies the appropriate sequential access device configuration. The following table illustrates this page. Byte bits 7 6 5 4 3 2 1 0 0 reserved page code (10h) 1 a...

  • Page 100

    Scsi commands: 22bmode select page 92 field bytes bits description rew 8 0 always 0, indicating that report early warning for read type commands is not supported. Gap size 9 always 0, indicating that there is no concept of inter-block gaps in the lto format. Eod defined 10 5-7 always 0, indicating t...

  • Page 101

    Scsi commands: 22bmode select page 93 3.10.10protocol-specific logical unit mode page (18h) the protocol-specific logical unit mode page is implemented for fibre channel and sas drives. The implementation differs according to the protocol. 3.10.10.1 fibre channel logical unit mode page (18h) the fib...

  • Page 102

    Scsi commands: 22bmode select page 94 3.10.10.2.1 sas logical unit page field descriptions field bytes bits description page code 0 0-5 18h, indicating the fibre channel logical unit control mode page. Page length 1 06h, indicating that six parameter bytes follow the page length byte. Protocol ident...

  • Page 103

    Scsi commands: 22bmode select page 95 3.10.11protocol-specific port mode page (19h) 3.10.11.1 protocol-specific port mode page (19h) for fcp the fibre channel port control mode page contains those parameters that select fcp_port operation options. The page is implemented by lun 0 of the drive. Some ...

  • Page 104

    Scsi commands: 22bmode select page 96 field bytes bits description rr_tov units 6 0-3 units, in seconds, of thesequence initiative resource recovery timeout value field. 000b = no timer is specified. The value in rr_tov seq_int is ignored and the drive default value of 2000msec is used. 001b = 0.001...

  • Page 105

    Scsi commands: 22bmode select page 97 field bytes bits description initiator response timeout 6-7 the time in milliseconds that the drive waits for the receipt of a frame before aborting the command associated with that frame. The default is 30000. A 0000h setting means the drive waits forever. Rese...

  • Page 106

    Scsi commands: 22bmode select page 98 byte bits 7 6 5 4 3 2 1 0 55 3.10.11.3.1 sas control and discover subpage field descriptions field bytes bits description page code 0 0-5 19h, indicating a port control mode page. Spf 0 6 sub page format. 0 = page_0 mode page format 1 = sub_page format parameter...

  • Page 107

    Scsi commands: 22bmode select page 99 field bytes bits description attached ssp target port 15 3 1b = an ssp target port is present. Sas address 16-23 the sas address of this port. Attached sas address 24-31 the sas address of the port attached to this port. Hardware minimum physical link rate 40 0-...

  • Page 108

    Scsi commands: 22bmode select page 100 field bytes bits description ebf 2 5 parallel scsi interface: always 0. Fibre channel interface: 0 = background function is disabled. 1 = background function is enabled. Ewasc 2 4 always 1, indicating that tapealert warning flags are reported. Dexcept 2 3 0 = e...

  • Page 109

    Scsi commands: 22bmode select page 101 3.10.13medium configuration mode page (1dh) the medium configuration mode page specifies any special considerations the tape drive shall use when processing commands that access the medium. The worm mode (wormm) bit shall be set to one when the drive is operati...

  • Page 110

    Scsi commands: 22bmode select page 102 3.10.14drive capabilities control mode page (21h) the drive capabilities control mode page controls the capabilities of the lto drive. A single copy of this page is maintained for all initiators. New inquiry string control, firmware test control, and data compr...

  • Page 111

    Scsi commands: 22bmode select page 103 field bytes bits description inquiry string control 5 0 = standard inquiry string (default) 1 = factory test only inquiry string 1 2 = factory test only inquiry string 2 3 = factory test only inquiry string 3 firmware test control 6 0 = disable factory test mod...

  • Page 112

    Scsi commands: 22bmode select page 104 3.10.15interface control mode page (22h) the interface control mode page controls the operation of the primary port as well as parameters of the library serial interface. A single copy of this page is maintained for all initiators. Next selection id and target ...

  • Page 113

    Scsi commands: 22bmode select page 105 3.10.15.1 interface control page field descriptions field bytes bits description page code 0 0-5 22h, indicating the interface control mode page. Additional page length 1 always 0eh, indicating that fourteen parameter bytes follow the page length byte. Jumpered...

  • Page 114

    Scsi commands: 23bmode sense page 106 3.11 mode sense the mode sense command allows the host to determine various drive parameters. These parameters are sent from the drive to the host as data formatted in a parameter list. This command is complementary to the mode select command that sets device pa...

  • Page 115

    Scsi commands: 23bmode sense page 107 3.11.1 mode sense command descriptor block 3.11.1.1 mode sense (6) command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (1ah) 1 ignored lun rsvd dbd reserved 2 pc page code 3 reserved 4 allocation length 5 control 3.11.1.2 mode sense (6)field desc...

  • Page 116

    Scsi commands: 23bmode sense page 108 3.11.1.3 mode sense(10) command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (5ah) 1 ignored lun rsvd dbd reserved 2 pc page code 3 reserved 4 reserved 5 reserved 6 reserved 7 (msb) 8 allocation length (lsb) 9 control 3.11.1.4 mode sense(10)field ...

  • Page 117

    Scsi commands: 23bmode sense page 109 field bytes bits description allocation length 7-8 specifies the number of bytes the host has allocated for returned mode sense data. The drive will not return more than this amount of data. A value of 0 is a valid entry and indicates no data. Reserved all reser...

  • Page 118

    Scsi commands: 23bmode sense page 110 field bytes bits description block descriptor length 3 0 = no block descriptor follows. 8 = 8-byte block descriptor follows. Reserved all reserved bits must be 0. When buffered mode is 1, a write command is terminated when the data is transferred to the internal...

  • Page 119

    Scsi commands: 23bmode sense page 111 3.11.4 mode sense block descriptor byte bits 7 6 5 4 3 2 1 0 0 density code 1 reserved 2 reserved 3 reserved 4 reserved 5 (msb) 6 7 block length (lsb) 3.11.4.1 block descriptor field descriptions field bytes bits description lto4 drive lto3 drive lto2 = 42h (rea...

  • Page 120

    Scsi commands: 23bmode sense page 112 3.11.6 mode sense completion status code message description 00h good status • the drive is ready to perform any appropriate command. • the drive remains in any previously set mode. Mode sense does not set or change any modes. • the tape position is not changed....

  • Page 121

    Scsi commands: 24bpark unpark page 113 3.12 park unpark the park unpark command with the park bit set requests that the drive park the load arm in preparation for transport. The park unpark command with the park bit not set requests that the drive load arm be unparked. This is not usually necessary ...

  • Page 122

    Scsi commands: 25bpersistent reserve in page 114 3.13 persistent reserve in the persistent reserve in command is used to obtain information about persistent reservations and reservation keys that are active within a device server. This command is used in conjunction with the persistent reserve out c...

  • Page 123

    Scsi commands: 25bpersistent reserve in page 115 3.13.1.2 persistent reserve in parameter data for read keys byte bits 7 6 5 4 3 2 1 0 0 (msb) 3 generation (lsb) 4 (msb) 7 additional length (lsb) reservation key list 8 (msb) 15 first reservation key (lsb) . . . N-7 (msb) n last reservation key (lsb)...

  • Page 124

    Scsi commands: 25bpersistent reserve in page 116 field bytes bits description initiator holding the persistent reservation that requests a transfer from the initiator to the storage medium or cache of the logical unit shall be terminated with reservation conflict status. 3h = exclusive access reads ...

  • Page 125

    Scsi commands: 26bpersistent reserve out page 117 3.14 persistent reserve out the persistent reserve out command is used to request service actions that reserve a logical unit or element for the exclusive or shared use of a particular initiator. The command uses other service actions to manage and r...

  • Page 126

    Scsi commands: 26bpersistent reserve out page 118 3.14.1.2 persistent reserve out service action codes code name description generation field incremented 00h register register a reservation key with the device server. Yes 01h reserve creates a persistent reservation having a specified scope and type...

  • Page 127

    Scsi commands: 26bpersistent reserve out page 119 3.14.1.4 persistent reserve out service actions and valid parameters parameters service action allowed scope type reservation key service action reservation key scope- specific address register ignored ignored valid valid ignored register and ignore ...

  • Page 128

    Scsi commands: 27bprevent allow medium removal page 120 3.15 prevent allow medium removal the prevent allow medium removal command requests that the target enable or disable the removal of the medium from the drive. The drive will not allow medium removal if any initiator currently has medium remova...

  • Page 129

    Scsi commands: 27bprevent allow medium removal page 121 3.15.2 prevent allow medium removal completion status code message description 00h good status • the drive is ready to perform any appropriate command. • the drive remains in any previously set mode. • the tape position is not changed. 02h chec...

  • Page 130

    Scsi commands: 28bread page 122 3.16 read the read command transfers one or more bytes or blocks from the drive to the initiator beginning with the next block on tape. If the fixed bit is zero and transfer length is not zero, then a single block of the length in transfer length is transferred. If th...

  • Page 131

    Scsi commands: 28bread page 123 3.16.1.1 read command field descriptions field bytes bits description operation code 0 the operation code for read is 08h. Ignored logical unit 1 5-7 the lun field is vestigial from the scsi-1 standard and is ignored. Sili 1 1 0 = return check status when an incorrect...

  • Page 132

    Scsi commands: 28bread page 124 is encountered before the sequence is complete, the blocks up to that block are returned followed by all of that block and check condition status. The current position is set after the last block that was returned or partially returned. If the transfer length field is...

  • Page 133

    Scsi commands: 28bread page 125 3.16.2.4 end of medium (eom) or end-of-partition (eop) when the end-of-medium or end-of-partition position is encountered, the command terminates with a check condition and medium error (03h) sense key. The valid bit (byte 0, bit 7) and the eom bit (byte 2, bit 6) are...

  • Page 134

    Scsi commands: 28bread page 126 the drive reports the incorrect length error based on the suppress incorrect length indicator (sili) bit as follows: if the actual block length exceeds the cdb transfer length, the incorrect length error is reported. If the actual block length is smaller than the cdb ...

  • Page 135

    Scsi commands: 28bread page 127 3.16.2.9 variable mode residual data when the fixed bit is zero, the residual data is always set to the cdb transfer length. For example, assume the following: the drive is currently positioned before block n. Block n + 1 contains 512 bytes. The host issues a read com...

  • Page 136

    Scsi commands: 29bread attribute page 128 3.17 read attribute the read attribute command allows the application client to read attribute values from medium auxiliary memory. 3.17.1 read attribute command descriptor block bits byte 7 6 5 4 3 2 1 0 0 operation code 8ch 1 reserved service action 2 (msb...

  • Page 137

    Scsi commands: 29bread attribute page 129 3.17.2 read attribute service action codes the service actions defined for the read attribute command are shown in the table below. Code name description 00h attribute values return attribute values 01h attribute list return a list of available attribute ide...

  • Page 138

    Scsi commands: 29bread attribute page 130 bits byte 7 6 5 4 3 2 1 0 0 (msb) 3 available data (n-3) (lsb) attribute identifiers 4 (msb) 5 attribute identifier 0 (lsb) . . . (msb) n attribute identifier x (lsb) the available data contains the number of bytes of attribute identifier data in the paramet...

  • Page 139

    Scsi commands: 29bread attribute page 131 bits byte 7 6 5 4 3 2 1 0 2 first partition number 3 number of partition available the available data contains two. The first partition number field indicates the first partition available on the specified volume number. It contains zero as there is only one...

  • Page 140

    Scsi commands: 29bread attribute page 132 3.17.8 attributes supported by the drive 3.17.8.1 device type attributes device type attributes are maintained and updated by the device server when the medium and associated medium auxiliary memory are present. All supported medium type attributes have a st...

  • Page 141

    Scsi commands: 29bread attribute page 133 assigning organization (id 0005h): the assigning organization attribute identifies the organization responsible for the specifications defining the values in the formatted density code attribute. The assigning organization attribute contains the ascii text l...

  • Page 142

    Scsi commands: 29bread attribute page 134 bits byte 7 6 5 4 3 2 1 0 0 (msb) 5 current amount of data written* ¹ (lsb) 6 (msb) 11 current write retries count ¹ (lsb) 12 (msb) 17 current amount of data read* ¹ (lsb) 18 (msb) 23 current read retries count ¹ (lsb) 24 (msb) 29 previous amount of data wri...

  • Page 143

    Scsi commands: 29bread attribute page 135 3.17.8.2 medium type attributes medium type attributes are stored in the medium auxiliary memory by the media manufacturer. All supported medium type attributes have a status of read only. Attribute identifier name attribute length format 0400h medium manufa...

  • Page 144

    Scsi commands: 29bread attribute page 136 medium type (id 0408h): and medium type information (id 0400h): give information about non-data media and other types of media. The medium type information attribute is interpreted according to the type of medium indicated by the medium type as shown in the ...

  • Page 145

    Scsi commands: 29bread attribute page 137 text localization identifier (id 0805h): defines the character set used for attributes with a text format. Note: refer to scsi-3 primary commands for a list of text localization identifier meanings. Barcode (id 0806h): is contents of a barcode associated wit...

  • Page 146

    Scsi commands: 29bread attribute page 138 3.17.9 read attribute completion status code message description 00h good status • the drive is ready to perform any appropriate command. • the drive remains in any previously set mode. • the tape position is not changed. 02h check condition use the request ...

  • Page 147

    Scsi commands: 30bread block limits page 139 3.18 read block limits the read block limits command requests that the drive return the maximum and minimum block sizes that it supports. The minimum block length is always reported as 1 byte, the maximum as 2 24 -1 bytes. 3.18.1 read block limits command...

  • Page 148

    Scsi commands: 30bread block limits page 140 3.18.2.1 read block limits data field descriptions field bytes bits description reserved all reserved bits must be 0. Maximum block length 1-3 always ffffffh, indicating a maximum block length of 2 24 -1 bytes. Minimum block length 4-5 always 0001h, indic...

  • Page 149

    Scsi commands: 31bread buffer page 141 3.19 read buffer the read buffer command reads data from the memory on the drive and sends it to the initiator. This command is used in conjunction with the write buffer command as a diagnostic function for testing the drive buffer memory and confirming the scs...

  • Page 150

    Scsi commands: 31bread buffer page 142 a mode of 00h requests that the data returned consists of a 4-byte descriptor header followed by the data from the buffer. The 4-byte header is included in the number of bytes specified by the allocation length. The buffer id and buffer offset fields are reserv...

  • Page 151

    Scsi commands: 31bread buffer page 143 byte bits 7 6 5 4 3 2 1 0 0 offset boundary 1 (msb) 2 3 buffer capacity (lsb) 3.19.3.1 read buffer descriptor field descriptions field bytes bits description offset boundary 0 always 0h, indicating byte boundaries buffer capacity 1-3 the capacity of the drive’s...

  • Page 152

    Scsi commands: 31bread buffer page 144 3.19.6 mam page definitions the following section details the pages available in the mam. Refer to the relevant ultrium specification documents for the current mam data. An ultrium specification exists for each media generation. 3.19.6.3 mam pages the table bel...

  • Page 153

    Scsi commands: 32bread position page 145 3.20 read position the read position command reports the block address of the current data block. The current data block is the first data block that would be read from the current tape partition if a read command were issued. 3.20.1 read position command des...

  • Page 154

    Scsi commands: 32bread position page 146 3.20.2 read position data the read position command returns a block of read position data. The following table shows the fields in the read position data when the long and tclp bits are set to zero. Byte bits 7 6 5 4 3 2 1 0 0 bop eop reserved bpu reserved 1 ...

  • Page 155

    Scsi commands: 32bread position page 147 field bytes bits description number of blocks in buffer 13-15 this field is not supported and is always 0. Number of bytes in buffer 16-19 this field is not supported and is always 0. Reserved all bits are 0. The first block location and the last block locati...

  • Page 156

    Scsi commands: 32bread position page 148 3.20.2.2 read position long form field descriptions field bytes bits description bop 0 7 0 = the current logical position is not at bop. 1 = the current logical position is at beginning-of-partition (bop). Eop 0 6 0 = the current logical position is not betwe...

  • Page 157

    Scsi commands: 33breceive diagnostic results page 149 3.21 receive diagnostic results the receive diagnostic results command requests that the results of a previously executed send diagnostic command be sent to the initiator. 3.21.1 receive diagnostic results command descriptor block byte bits 7 6 5...

  • Page 158

    Scsi commands: 33breceive diagnostic results page 150 byte bits 7 6 5 4 3 2 1 0 6 diagnostic parameter 7 diagnostic parameter (lsb) 3.21.2.2 field descriptions – pcv not set field bytes description page code 0 identifies the type of diagnostic page being returned. Reserved 1 all reserved bits must b...

  • Page 159

    Scsi commands: 33breceive diagnostic results page 151 3.21.4.1 field descriptions – pcv not set field bytes bits description page code 0 identifies the type of diagnostic page being returned. Reserved 1 all reserved bits must be 0. Page length 2-3 indicates the number of bytes of data to be returned...

  • Page 160

    Scsi commands: 34brelease page 152 3.22 release the release command releases a current drive reservation, if the command is received from the initiator that established the reservation. Any release command that arrives from other than the originating requester is ignored and good status is returned ...

  • Page 161

    Scsi commands: 34brelease page 153 byte bits 7 6 5 4 3 2 1 0 8 reserved 9 control 3.22.1.4 release(10) command field descriptions field bytes bits description operation code 0 the operation code for the 10-byte version of release is 57h. Ignored logical unit 1 5-7 the lun field is vestigial from the...

  • Page 162

    Scsi commands: 35breport density support page 154 3.23 report density support the report density support command returns details about the tape formats supported by the drive. The data is returned as a header and a series of descriptor blocks. If the media bit is set, then one descriptor block is re...

  • Page 163

    Scsi commands: 35breport density support page 155 byte bits 7 6 5 4 3 2 1 0 3 reserved 3.23.2.2 report density support header field descriptions field bytes bits description available density descriptor length 0-1 the total amount of data that is available to be returned excluding this field. Reserv...

  • Page 164

    Scsi commands: 35breport density support page 156 3.23.2.4 report density support descriptor field descriptions field bytes bits description lto4 drive lto3 drive 42h indicating ultrium 2 (read only) 40h indicating ultrium 1 (read only) 44h indicating ultrium 3 42h indicating ultrium 2 primary densi...

  • Page 165

    Scsi commands: 35breport density support page 157 field bytes bits description density name 24-31 8 bytes of ascii data. Can be one of the following: for ultrum 4 “u416 ” for ultrium 3: “u316 ” for ultrium 2: “u-28 ” for ultrium 1: “u-18 ” description 32-51 20 bytes of ascii data. Can be one of the ...

  • Page 166

    Scsi commands: 36breport device identifier page 158 3.24 report device identifier the host uses this command to retrieve the device identifier. The device identifier is set using the set device identifier command and shall persist through power cycles. 3.24.1 report device identifier command descrip...

  • Page 167

    Scsi commands: 36breport device identifier page 159 3.24.2.1 field descriptions field bytes bits description identifier length 0-3 the identifier length field indicates the length in bytes of the identifier field. The identifier length shall initially equal zero, and shall be changed only by a succe...

  • Page 168

    Scsi commands: 37breport luns page 160 3.25 report luns the host uses this command to retrieve information about which logical units the drive supports. The allocation length shall be at least 16 bytes. If this is not the case, drive will return check condition status and provide a sense key of ille...

  • Page 169

    Scsi commands: 37breport luns page 161 byte bits 7 6 5 4 3 2 1 0 7 reserved 8-15 lun 0 3.25.2.1 report luns data field descriptions field bytes bits description lun list length 0-3 always 8, indicating the length of the lun list, starting in byte 8. Reserved 4-7 all reserved bits must be 0. Lun 0 8-...

  • Page 170

    Scsi commands: 38breport supported operation codes page 162 3.26 report supported operation codes the host uses this command to retrieve information on the commands that the drive supports. The host may request a list of all operation codes and service actions supported or the command support data f...

  • Page 171

    Scsi commands: 38breport supported operation codes page 163 field bytes bits description requested operation code 3 the requested operation code field specifies the operation code of the one command data to be returned. Requested service action 4-5 the requested service action field specifies the se...

  • Page 172

    Scsi commands: 38breport supported operation codes page 164 field bytes bits description servactv 5 0 the service action valid bit: 0 = indicates operation code does not have service actions and service action field contents are reserved. 1 = indicates operation code has service actions and contents...

  • Page 173

    Scsi commands: 38breport supported operation codes page 165 3.26.3 report supported operation codes completion status code message description 00h good status • the drive is ready to perform any appropriate command. • the drive remains in any previously set mode. • the drive accepts commands from an...

  • Page 174

    Scsi commands: 39breport supported task management functions page 166 3.27 report supported task management functions the host uses this command to report information on the task management functions that the drive supports. 3.27.1 report supported task management functions command descriptor block ...

  • Page 175

    Scsi commands: 39breport supported task management functions page 167 3.27.2.1 report supported task management functions data field descriptions field bytes bits description wakes 0 0 set indicates a \wakeup task management function is supported by drive. Trs 0 1 set indicates a target reset task m...

  • Page 176

    Scsi commands: 40brequest sense page 168 3.28 request sense the request sense command returns the status of the last command. Sense data is updated with each command; therefore, the sense data only reports the status of the immediately previous command. If a check condition status results, a request...

  • Page 177

    Scsi commands: 40brequest sense page 169 3.28.2 request sense command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (03h) 1 ignored lun reserved 2 reserved 3 reserved 4 allocation length 5 control 3.28.2.1 request sense command field descriptions field bytes bits description operation ...

  • Page 178

    Scsi commands: 40brequest sense page 170 byte bits 7 6 5 4 3 2 1 0 21 reserved cln reserved 22-29 vendor unique1 (reserved) 30-33 vendor unique2 (reserved) 34-37 vendor unique3 (reserved).

  • Page 179

    Scsi commands: 40brequest sense page 171 3.28.3.1 request sense data field descriptions field bytes bits description valid 0 7 0 = the information field does not contain valid information 1 = the information field contains valid information this is always 0 for deferred errors. Error code 0 0-6 70h ...

  • Page 180

    Scsi commands: 40brequest sense page 172 field bytes bits description c/d 15 6 0 = the first error was encountered in the data-out phase. 1 = the first error was encountered in the command descriptor block. Bpv 15 3 1 = the bit pointer field indicates the bit field in error. Bit pointer 15 0-2 if bp...

  • Page 181

    Scsi commands: 40brequest sense page 173 3.28.3.3 additional sense codes and code qualifiers additional sense codes and additional sense codes qualifiers are returned in the request sense data in bytes 12 and 13. These codes are loaded whenever a check condition is returned for a scsi command. The p...

  • Page 182

    Scsi commands: 40brequest sense page 174 sense key byte 2 asc byte 12 ascq byte 13 message explanation 02h 04h 10h logical unit not ready auxiliary memory not accessible unable to read tape cartridge memory. 02h 30h 00h incompatible medium installed tape cartridge generation not supported or unsuppo...

  • Page 183

    Scsi commands: 40brequest sense page 175 sense key byte 2 asc byte 12 ascq byte 13 message explanation 03h 30h 00h incompatible medium installed inserted cartridge is incompatible, cleaning tape or other. 03h 30h 02h cannot read medium incompatible format an operation could not be completed because ...

  • Page 184

    Scsi commands: 40brequest sense page 176 sense key byte 2 asc byte 12 ascq byte 13 message explanation 04h 40h 85h mon task diagnostic failed during post or diagnostics the mon task reported an error. Refer to the vscq for more information about the cause. 04h 40h 86h lib task diagnostic failed duri...

  • Page 185

    Scsi commands: 40brequest sense page 177 sense key byte 2 asc byte 12 ascq byte 13 message explanation 05h 55h 04h insufficient registration resource unable to complete persistent reservation request because all resources are used. 06h unit attention 06h 04h 10h auxiliary memory not accessible an ac...

  • Page 186

    Scsi commands: 40brequest sense page 178 sense key byte 2 asc byte 12 ascq byte 13 message explanation 07h 74h 02h unencrypted data found while decrypting unencrypted block detected while reading or verifying in decrypt or raw mode. 07h 74h 03h incorrect data encryption key no valid decryption key a...

  • Page 187

    Scsi commands: 40brequest sense page 179 sense key byte 2 asc byte 12 ascq byte 13 message explanation 0bh 5ah 01h operator medium removal request the command was aborted because the eject button was pressed. 0bh 74h 06h digital signature validation error firmware update aborted because the new firm...

  • Page 188

    Scsi commands: 41breserve page 180 3.29 reserve the reserve command reserves the drive for exclusive use of the requesting initiator. The drive reservation once established remains in effect until one of the following occurs: another reserve command arrives from the same initiator that requested the...

  • Page 189

    Scsi commands: 41breserve page 181 3.29.1.3 reserve(10) command descriptor block byte bits 7 6 5 4 3 2 1 0 0 operation code (56h) 1 ignored lun reserved 2 reserved 3 ignored third party device id 4 reserved 5 reserved 6 reserved 7 reserved 8 reserved 9 control 3.29.1.4 reserve(10) command field desc...

  • Page 190

    Scsi commands: 42brewind page 182 3.30 rewind the rewind command requests that the medium be positioned to the beginning of tape (bom). Prior to performing the rewind operation, the buffered data and filemarks are written to the tape and an eod marker is recorded. The rewind operation is done at hig...

  • Page 191

    Scsi commands: 42brewind page 183 code message description 02h check condition use the request sense command to retrieve status information. Possible sense keys are: code message description 02h not ready no cartridge is in the drive. 03h media error unrecoverable data error encountered. 04h hardwar...

  • Page 192

    Scsi commands: 43bsecurity protocol in page 184 3.31 security protocol in the security protocol in command is used to retrieve security protocol information or the results of one or more security protocol out commands. This command is supported only in lto4 drives and later. 3.31.1 security protocol...

  • Page 193

    Scsi commands: 43bsecurity protocol in page 185 3.31.2 supported security protocol list if the security protocol field is set to security protocol information (00h) and the security protocol specific field is set to security protocol information (0000h), then the supported security protocol list is ...

  • Page 194

    Scsi commands: 43bsecurity protocol in page 186 byte bits 7 6 5 4 3 2 1 0 12 (msb) 13 data encryption management capabilities page code (0012h) (lsb) 14 (msb) 15 data encryption status page code (0020h) (lsb) 16 (msb) 17 next block encryption status page code (0021h) (lsb) 18 (msb) 19 random number ...

  • Page 195

    Scsi commands: 43bsecurity protocol in page 187 byte bits 7 6 5 4 3 2 1 0 0 algorithm index (00h) 1 reserved 2 (msb) 3 descriptor length (14h) (lsb) 4 avfmv sdk_c mac_c ded_c decrypt_c encrypt_c 5 avfclp nonce_c reserved ukafd akadf 6 (msb) 7 maximum unauthenticated key-associated bytes (lsb) 8 (msb...

  • Page 196

    Scsi commands: 43bsecurity protocol in page 188 field bytes bits description avfclp 5 6-7 algorithm valid for current logical position: 00b = current logical position is not applicable to the encryption algorithm validity or no volume is loaded. 10b = the encryption algorithm being specified is vali...

  • Page 197

    Scsi commands: 43bsecurity protocol in page 189 byte bits 7 6 5 4 3 2 1 0 7 reserved aitn_c local_c public_c 8 15 reserved 3.31.8.1 data encryption management capabilities field descriptions field bytes bits description lock_c 4 0 1 = device server supports the lock bit in the set data encryption pa...

  • Page 198

    Scsi commands: 43bsecurity protocol in page 190 field bytes bits description encryption mode 5 value from the encryption mode in the saved data encryption parameters currently associated with the i_t nexus on which this command was received. Decryption mode 6 value from the decryption mode in the sa...

  • Page 199

    Scsi commands: 43bsecurity protocol in page 191 3.31.10next block encryption status page the next block encryption status page reports the encryption parameters of the next logical object (logical block or filemark). Byte bits 7 6 5 4 3 2 1 0 0 (msb) 1 page code (0021h) (lsb) 2 (msb) 3 page length (...

  • Page 200

    Scsi commands: 43bsecurity protocol in page 192 field bytes bits description encryption status 12 0-3 0h = the device server is incapable of determining if the logical object referenced by the logical object number field has been encrypted. 1h = the device server is capable of determining if the log...

  • Page 201

    Scsi commands: 43bsecurity protocol in page 193 if the currently-loaded volume does not support encryption or if no volume is loaded, then the fields of the next block encryption status page shall have the following values: field value page length 000ch logical object number 0h encryption status 0h ...

  • Page 202

    Scsi commands: 43bsecurity protocol in page 194 byte bits 7 6 5 4 3 2 1 0 12 (msb) 13 public key length (n-9) (lsb) 14 (msb) n public key (lsb) 3.31.13.1 public key type field descriptions code description key format 00000000h rsa 2048 rsa 2048 public keys 00000001h-0000000fh reserved 00000010h ecc ...

  • Page 203

    Scsi commands: 44bsecurity protocol out page 195 3.32 security protocol out the security protocol out command is used to send data to the logical unit. The data sent specifies one or more operations to be performed by the logical unit. The format and function of the operations depends on the content...

  • Page 204

    Scsi commands: 44bsecurity protocol out page 196 field bytes bits description security protocol specific 2-3 0010h = set data encryption page inc_512 4 7 always 0, indicating that the allocation length is expressed in bytes. Transfer length 6-9 length of data-out in bytes. Reserved all reserved bits...

  • Page 205

    Scsi commands: 44bsecurity protocol out page 197 if the encryption mode is encrypt, then the key-associated data descriptors list may contain one descriptor with twelve bytes of authenticated key-associated data (a-kad). It may also contain one descriptor with sixteen bytes of unauthenticated key-as...

  • Page 206

    Scsi commands: 44bsecurity protocol out page 198 field bytes bits description rdmc raw decryption mode control 5 4-5 00= each encrypted block is marked per the default setting for the algorithm. 01= reserved 10= each encrypted block is marked in a format specific manner as enabled for raw decryption...

  • Page 207

    Scsi commands: 44bsecurity protocol out page 199 field bytes bits description key length 18-19 32 = length of key, when included. If any other non-zero value, then the device server shall terminate the command with check condition status, with the sense key set to illegal request, and the additional...

  • Page 208

    Scsi commands: 44bsecurity protocol out page 200 3.32.2.2.1 wrapped key field descriptions field bytes bits description parameter set 0-1 0000h = rsa 2048 0010h = ecc 521 label length 2-3 label length specifies the length of the label field in bytes. Label 4-n label contains public information assoc...

  • Page 209

    Scsi commands: 44bsecurity protocol out page 201 field bytes bits description key descriptor type 0 00h = unauthenticated key-associated data (u-kad). Authenticated 1 0-2 data-out: reserved (0h) data-in: 2h = no attempt has been made to authenticate the value in the key descriptor field. Key descrip...

  • Page 210

    Scsi commands: 44bsecurity protocol out page 202 byte bits 7 6 5 4 3 2 1 0 4 (msb) 67 key descriptor (lsb) 3.32.3.3.1 metadata key-associated key field descriptions field bytes bits description key descriptor type 0 xxh = metadata descriptor. Authenticated 1 0-2 data-out: reserved (0h) data-in: 2h =...

  • Page 211

    Scsi commands: 44bsecurity protocol out page 203 code message description 02h check condition use the request sense command to retrieve status information. Possible sense keys are: code message description 04h hardware error parity error on the scsi bus or drive hardware failure. 05h illegal request...

  • Page 212

    Scsi commands: 45bsend diagnostic page 204 3.33 send diagnostic the send diagnostic command requests the drive to perform self diagnostic operations. The diagnostic tests are part of the drive’s resident firmware. The receive diagnostic results command may be used to retrieve the result of the diagn...

  • Page 213

    Scsi commands: 45bsend diagnostic page 205 3.33.1.1.1 diagnostic page format byte bits 7 6 5 4 3 2 1 0 0 page code 1 reserved 2 (msb) 3 page length (n-3) (lsb) 4 (msb) n diagnostic parameters (lsb) 3.33.1.1.2 supported diagnostic pages page code description 00h supported diagnostic pages (receive di...

  • Page 214

    Scsi commands: 45bsend diagnostic page 206 3.33.2 send diagnostic completion status code message description 00h good status • the drive is ready to perform any appropriate command. • the drive remains in any previously set mode. • the tape position is not changed. 02h check condition use the reques...

  • Page 215

    Scsi commands: 46bset capacity page 207 3.34 set capacity the set capacity command sets the available medium for a volume to a proportion of the total capacity of that volume. Any excess space is unavailable on the volume after successful completion of this command until reset by a new set capacity ...

  • Page 216

    Scsi commands: 46bset capacity page 208 field bytes bits description capacity proportion value 3-4 this field specifies the portion of the total tape capacity to be made available for use. The capacity proportion value is the numerator of a fraction with a denominator of 65535. The resulting availab...

  • Page 217

    Scsi commands: 47bset device identifier page 209 3.35 set device identifier the host uses this command to set the device identifier. The device identifier is retrieved using the report device identifier command and shall persist through power cycles. Upon successful completion of the set device iden...

  • Page 218

    Scsi commands: 47bset device identifier page 210 3.35.2.1 set device identifier data field descriptions field bytes bits description identifier 0-3 the identifier field shall contain a vendor specific value. The identifier value shall persist through power cycling. The drive supports a maximum ident...

  • Page 219

    Scsi commands: 48bspace page 211 3.36 space the space command uses three methods to move the tape. This command moves the position: forward or backward a specified number of blocks. Forward or backward a specified number of filemarks. Forward to the end of recorded data (eod). If the target block or...

  • Page 220

    Scsi commands: 48bspace page 212 eod is detected before the requested logical position, then the logical position is set to that position. If the code field is 001b, then the logical position is moved the number of file marks indicated by the count field. If bom or eod is detected before the request...

  • Page 221

    Scsi commands: 48bspace page 213 3.36.3 space to eod the count field is ignored in the space-to-eod function. In the space-to-eod function, the tape is positioned such that a subsequent write command appends data to the last recorded information on the tape. This positioning is done at high search s...

  • Page 222

    Scsi commands: 49btest unit ready page 214 3.37 test unit ready the test unit ready command provides a means to check that the drive is ready. If the drive is able to accept a medium-access command without returning a check condition status, then the test unit ready command will result in good statu...

  • Page 223

    Scsi commands: 50bverify page 215 3.38 verify the verify command verifies one or more blocks of data beginning with the next block from the tape unit. The command terminates after the specified number of bytes or blocks are verified or when the drive encounters a filemark, the eod, the eom, or an un...

  • Page 224

    Scsi commands: 50bverify page 216 3.38.2 verify command operation when the fixed bit is set, the verify length specifies the number of contiguous blocks to be verified on the tape. When the fixed bit is cleared, the verify length specifies the number of bytes in the block to verify. Verification sta...

  • Page 225

    Scsi commands: 51bwrite page 217 3.39 write the write command transfers one or more data blocks from the initiator to the drive. If the transfer length is zero, no data is transferred, and the current position of the tape is not changed. This condition is not considered an error. 3.39.1 write comman...

  • Page 226

    Scsi commands: 51bwrite page 218 is encountered. Any write command issued within early warning and successfully completed finishes with a check condition and the eom bit set. 3.39.2 write completion status code message description 00h good status • the scsi data has been transferred to the data buff...

  • Page 227

    Scsi commands: 52bwrite attribute page 219 3.40 write attribute the write attribute command allows the application client to write attribute values to medium auxiliary memory. Refer to the read attribute command, section 3.17.8 attributes supported by the drive. For a listing of defined medium auxil...

  • Page 228

    Scsi commands: 52bwrite attribute page 220 3.40.2 write attribute parameter list format the write attribute command parameter list format is shown in the table below. Bits byte 7 6 5 4 3 2 1 0 0 (msb) 3 parameter data length (n-3) (lsb) attribute(s) 4 (msb) attribute 0 (lsb) . . . (msb) n attribute ...

  • Page 229

    Scsi commands: 53bwrite buffer page 221 3.41 write buffer the write buffer command is used in conjunction with the read buffer command as a diagnostic function for testing the data buffer memory of the drive and confirming the scsi bus or fibre channel interface integrity. The medium is not accessed...

  • Page 230

    Scsi commands: 53bwrite buffer page 222 a mode field of 00h indicates that the data to be written will be preceded with a four- byte header. This write buffer data header is reserved and must be set to all zeros. The header will not be placed into buffer memory. A mode field of 01h indicates that da...

  • Page 231

    Scsi commands: 53bwrite buffer page 223 3.41.2 echo buffer mode 0ah will cause data to be written to the echo buffer. Data shall be sent aligned on four-byte boundaries. The buffer id and buffer offset fields are ignored in this mode. The capacity of the echo buffer may be determined by the buffer c...

  • Page 232

    Scsi commands: 54bwrite filemarks page 224 3.42 write filemarks the write filemarks command causes the specified number of filemarks to be written to tape. This command can be used to force all remaining buffered data blocks to be written to tape without appending filemarks by specifying zero filema...

  • Page 233

    Scsi commands: 54bwrite filemarks page 225 3.42.2 write filemarks completion status code message description 00h good status • the filemarks have been sent to the buffer. • the drive remains in any previously set mode. Note: if immed is one, then good status only indicates that the command is valid....

  • Page 234

    4 appendix a: message codes this table lists the vendor unique message codes that are returned by the request sense command in the field pointer field (bytes 16-17) when the sksv bit is 0. Good_status 00h general all seems well busy_status 01h general busy illegal_command_status 02h general illegal ...

  • Page 235

    Scsi_rb_no_room 33h scsi ring buffer should have enough room scsi_main_not_found 34h scsi pmainroutine not found scsi_xferdone_not_found 35h scsi pxferdoneroutine not found scsi_compdone_not_found 36h scsi scsi task completion routine not found scsi_pdetect_not_found 37h scsi pdetect routine not fou...

  • Page 236

    Manager dsm_drive_not_ready 5ch data set manager dsm_unknown_command 5dh data set manager dsm_cmpr_interrupt_no_ds 5eh data set manager dsm_format_error_dsn 5fh data set manager dsm_format_error_record_count 60h data set manager dsm_format_error_fmk_count 61h data set manager dsm_format_error_total_...

  • Page 237

    Dsm_write_flush_error 7ah data set manager dsm_write_error 7bh data set manager dsm_null_ds_detected_during_flush 7ch data set manager dsm_cant_flush_compressor_not_halted 7dh data set manager dsm_not_in_write_mode_cant_flush 7eh data set manager dsm_be_pended_flush_cmd_lost 7fh data set manager dsm...

  • Page 238

    Tape_ds_in_out_sequence a6h tape write: data set in out of sequence. Tape_ds_dn_out_sequence a7h tape write: data set done out of sequence. Tape_read_blank_tape a8h tape read: blank tape tape_illegal_speed a9h tape tp_set_vco(): illegal speed. Tape_vco_lock_err aah tape tp_set_vco(): vco_lock error....

  • Page 239

    Srv_divider_timeout dch servo fw timed out waiting for hardware divider srv_servo_timeout ddh servo servo firmware time out srv_find_index_failed deh servo find drive motor index failed srv_cal_slot_failed dfh servo calibrate slot command failed srv_goto_point_invalid e0h servo target point to close...

  • Page 240

    Auxiliary memory mic_page_does_not_exist 10dh medium auxiliary memory the page id requested does not exist in the page descriptor table. Mic_page_crc_bad 10eh medium auxiliary memory the crc calculated on the page is not valid. Mic_page_locked_60sec 10fh medium auxiliary memory a lock is on the page...

  • Page 241

    Memory mic_bad_pg_tbl 121h medium auxiliary memory page table corrupted mic_bad_pg_id 122h medium auxiliary memory page id incorrect mic_bad_pg_len 123h medium auxiliary memory page length incorrect mic_invalid_copies 124h medium auxiliary memory too many/little copies of a page mic_malt_init_failed...

  • Page 242

    Mic_clean_cart_new_ucc 135h medium auxiliary memory clean cart is uninitialized universal clean cart tape shall send cm_init_pg & init some mic_clean_cart_ucc 136h medium auxiliary memory universal clean cart was initialized tape shall clean head calib_busy_status 137h calibration mon_cmd_overlapped...

  • Page 243

    Mon_desc_errors 16dh monitor despcriptor errors detected mon_crc_error 16eh monitor crc checking error mon_invalid_parameters 16fh monitor invalid parameters field in cmd packet mon_no_cartridge_inserted 170h monitor no cartridge inserted mon_servo_margin_data_is_not_available 171h monitor servo mar...

  • Page 244

    Srv_reel_motorpoweroff_api_busy_reject 199h servo api call motorpoweroff failed. Srv_reel_timeout_user_abort_state 19ah servo timeout message received in user_abort_state. Srv_reel_timeout_user_abort_tape_state 19bh servo timeout message received in user_abort_tape_state. Srv_movetape_timeout_ramp_u...

  • Page 245

    Scsi_status_diag_dma_write_dmaperr 1c2h scsi scsi_status_diag_dma_write_rdparerr 1c3h scsi scsi_status_diag_dma_write_mpaccerr 1c4h scsi scsi_status_diag_dma_write_counter_erro r 1c5h scsi scsi_status_diag_dma_write_data_compare _error 1c6h scsi scsi_status_diag_dma_read_interrupt_faile d 1c7h scsi ...

  • Page 246

    Elivered scsi_pcmd_lost_in_lib_start_xfer 1f4h scsi scsi_pcmd_lost_in_lib_send_command_comp lete 1f5h scsi scsi_pcmd_lost_in_lib_send_data_in_and_go od_status 1f6h scsi scsi_wrong_signal_node 1f7h scsi scsi_unable_alloc_dtd 1f8h scsi scsi_unknown_fc_msg 1f9h scsi scsi_xferstop_not_found 1fah scsi sc...

  • Page 247

    Scsi_create_sense_failed 22ah scsi scsi task failed to creaate microcode changed sense scsi_initalize_sense_failed 22bh scsi scsi_unknown_cm_eeprom_state 22ch scsi scsi_invalid_log_parameter 22dh scsi scsi_invalid_log_page 22eh scsi scsi_invalid_log_page_control 22fh scsi scsi_page_out_of_range 230h...

  • Page 248

    Own_at_lpos_from_cruise_control_revers e in reverse direction. Srv_movetape_invalid_direction_in_ramp_do wn_at_lpos_from_cruise_control 24eh servo tape not moving srv_movetape_lpos_received_before_track ing_in_ramp_up_state 24fh servo lpos notification received before ramp up completed. Srv_cmdproc_...

  • Page 249

    Srv_step_thread_tape_error14 275h servo expecting mech_delay2_done srv_step_thread_tape_error15 276h servo load arm stalled pulling pin from cartridge srv_step_thread_tape_error16 277h servo while removing the hysteresis from the load arm (hooking the pin) the bi-cell va srv_step_thread_tape_error17...

  • Page 250

    Srv_step_gofrom_hub_topark_default 2a5h servo an unexpected state occurred in the cartridge load task. Srv_step_thread_tape_error26 2a6h servo expected serial eeprom done srv_step_unthread_tape_error3 2a7h servo expecting steps done srv_step_no_active_pwr_recovery_thread_ retry_isr 2a8h servo an une...

  • Page 251

    Srv_step_retry2_error3 2d5h servo expecting sns13 low srv_step_retry2_error4 2d6h servo expecting steps done srv_step_retry2_error5 2d7h servo failed to remove slack srv_step_retry2_error6 2d8h servo the load arm failed while moving to home position (in front of the guides) durin srv_step_retry2_err...

  • Page 252

    Ror9 srv_step_pwr_recovery_unthread_tape_er ror10 307h servo expecting sns13 high srv_step_pwr_recovery_unthread_tape_er ror11 308h servo motor stall waiting for engaged_leader srv_step_pwr_recovery_unthread_tape_er ror12 309h servo expecting steps done srv_step_pwr_recovery_unthread_tape_de fault 3...

  • Page 253

    Rtos_status_queue_id_error 33ah rtos rtos_status_queue_full 33bh rtos rtos_status_partition_id_error 33ch rtos rtos_status_invalid_configuration_parame ter 33dh rtos rtos_status_invalid_input_parameter 33eh rtos rtos_status_task_pending_on_queue 33fh rtos rtos_status_event_flag_group_and_virtua l_ti...

  • Page 254

    Dsm_read_put_terminus_failed 35ch data set manager dsm_illegal_write_terminated_condition 35dh data set manager dsm_cmpr_skip_add_ds_failed 35eh data set manager dsm_cmpr_skip_dsit_c1_error 35fh data set manager dsm_cmpr_skip_unexpected_underrun 360h data set manager dsm_cmpr_skip_fmk_encountered 36...

  • Page 255

    Manager dsm_wr_mic_eod_update_with_null_ds 37bh data set manager dsm_write_located_but_no_append_ds 37ch data set manager dsm_write_read_paused_but_no_append_ds 37dh data set manager dsm_got_read_when_position_unknown 37eh data set manager dsm_space_eod_ds_not_eod 37fh data set manager dsm_mic_read_...

  • Page 256

    D tape_read_illegal_switch_wrap_idle_state 3ach tape read: idle state tape_read_illegal_switch_wrap_underrun_ state 3adh tape read: underrun state tape_read_switch_wrap_bad_eod_page 3aeh tape read: eod must be valid tape_read_illegal_switch_wrap_backward _mode 3afh tape read: must be in forward mode...

  • Page 257

    Srv_off_track 3cdh servo tracking servo detected off track event srv_no_pes_found 3ceh servo no valid pes event srv_vcm_shock_error 3cfh servo tracking servo detected shock vibration error srv_tracking_target_outrange 3d0h servo tracking servo detected unreachable track error srv_tracking_sample_err...

  • Page 258

    Srv_motor_por_stuck_1 3f4h servo can't clear reel motor por flag on startup srv_motor_por_stuck_2 3f5h servo can't clear reel motor por flag after pf clear srv_motor_pwr_fail 3f6h servo can't clear reel motor power fail condition on startup srv_statem_autoload_command_rejected_n o_cart_in_drive 3f7h...

  • Page 259

    Srv_cmdproc_manufacturer_id_not_availab le 41eh servo manufacturer id not available srv_cmdproc_lp1_not_available 41fh servo lp1 value not available srv_cmdproc_mfr_data_not_available_tape _not_read 420h servo manufacturer id not available. Srv_cmdproc_mfr_data_not_available_tape _not_ready 421h ser...

  • Page 260

    Ect_during_findzero srv_findzero_null_function_in_table 449h servo null function pointer in table lookup srv_findzero_invalid_message_received 44ah servo invalid message received by reel task during findzero operation srv_cmdproc_invalid_drive_state_on_unloa d_cmd 44bh servo invalid drive state on u...

  • Page 261

    Srv_tcnt_runaway 46dh servo asic tcnt register detects that the tape is running much higher than 4.15 meter/ srv_closed_loop_stepper_failed_to_find_p es_going_backwards 46eh servo closed loop stepper failed to find pes while in backwards mode srv_lpos_set_candidate_tape_not_moving 46fh servo an atte...

  • Page 262

    Out_during_searching_for_pes pes. Srv_head_stepper_offset_calibration_time out_during_found_pes 48dh servo timeout during head stepper offset calibration found pes. Srv_head_stepper_offset_calibration_time out_during_stopping_after_found_pes 48eh servo timeout during head stepper offset calibration ...

  • Page 263

    Srv_timeout_during_head_stepper_move_un til_reference_sensor_high 4a8h servo timeout during head stepper move until reference sensor high. Srv_timeout_during_head_stepper_move_un til_reference_sensor_low 4a9h servo timeout during head stepper move until reference sensor low. Srv_timeout_during_head_...

  • Page 264

    Adius_calc_cart_type cartridge type calcula srv_cm_lp1_and_lp6_not_within_lto_spec 4c9h servo cartridge memory lp1 and lp6 values don't fall within lto specification. Srv_seq_invalid_lpos_distance_in_calculat e_optimal_backward_speed 4cah servo invalid lpos distance (negative) calculated in repositi...

  • Page 265

    Scsi_pcmd_lostinfehead_34 4fbh scsi scsi_pcmd_lostinfehead_35 4fch scsi scsi_pcmd_lostinfehead_36 4fdh scsi scsi_pcmd_lostinfehead_37 4feh scsi scsi_pcmd_lostinfehead_38 4ffh scsi scsi_pcmd_lostinfehead_39 500h scsi scsi_pcmd_lostinfehead_40 501h scsi scsi_pcmd_lostinbehead_01 502h scsi scsi_pcmd_lo...

  • Page 266

    Scsi_unknown_be_state_09 534h scsi scsi_unknown_be_state_10 535h scsi scsi_unknown_be_state_lib_dispatch_set_m odes 536h scsi scsi_lib_dispatch_unload_unknown_tape_st ate 537h scsi scsi_unknown_be_state_lib_dispatch_unloa d 538h scsi scsi_lib_dispatch_load_and_hold_unknown _tape_state 539h scsi scsi...

  • Page 267

    Scsi_unknown_fe_state_04 56bh scsi unknown fe state scsi_unknown_fe_state_05 56ch scsi unknown fe state scsi_unknown_fe_state_06 56dh scsi unknown fe state scsi_null_thread_table_ptr_01 56eh scsi scsi_null_thread_table_ptr_02 56fh scsi scsi_null_thread_table_ptr_03 570h scsi scsi_unknown_task_manage...

  • Page 268

    Cm_bad_usage_info_3 584h medium auxiliary memory usage information 3 cm_bad_clean_usage_0 585h medium auxiliary memory cleaning usage 0 cm_bad_clean_usage_1 586h medium auxiliary memory cleaning usage 1 cm_bad_clean_usage_2 587h medium auxiliary memory cleaning usage 2 cm_bad_clean_usage_3 588h medi...

  • Page 269

    Auxiliary memory eep_bad_cart_stat_3 599h medium auxiliary memory cartridge status & tape alert flags 3 eep_bad_cart_usage_0 59ah medium auxiliary memory cartridge usage info 0 eep_bad_cart_usage_1 59bh medium auxiliary memory cartridge usage info 1 eep_bad_cart_usage_2 59ch medium auxiliary memory ...

  • Page 270

    Memory eep_bad_error_event_11 5adh medium auxiliary memory error event 11 eep_bad_error_event_12 5aeh medium auxiliary memory error event 12 eep_bad_error_event_13 5afh medium auxiliary memory error event 13 eep_bad_error_event_14 5b0h medium auxiliary memory error event 14 eep_bad_error_event_15 5b...

  • Page 271

    Eep_bad_exception_event_15 5c1h medium auxiliary memory exception event 15 eep_bad_por_count 5c2h medium auxiliary memory power on reset count eep_bad_retry_history 5c3h medium auxiliary memory retry history eep_bad_app_spec 5c4h medium auxiliary memory application specific scsi_sc_transfer_done_no_...

  • Page 272

    Dsm_be_wr_outstanding_ds_count_cant_go _negative 5ech data set manager dsm_be_read_stop_missing_ds 5edh data set manager dsm_failure_occurred_with_good_status 5eeh data set manager dsm_locate_terminated_with_good_status 5efh data set manager dsm_degraded_space_locate 5f0h data set manager dsm_cant_c...

  • Page 273

    Alid_state range). Srv_cmdproc_cmd_reject_sequencer_busy_ and_buffer_full 613h servo command rejected since the sequencer was processing an error and the polled buff srv_cannot_insert_into_lpos_notify_table_ until_scr_and_wp_found_lp1 614h servo lpos values in the notification table are dependent on...

  • Page 274

    Rection srv_step_head_expecting_stopping_after_s earching_for_servo_band 634h servo expecting stopping after searching for servo bundle srv_step_head_expecting_stopping_after_f ailing_search_for_servo_band 635h servo expecting stopping after failing search for servo bundle srv_step_head_expecting_st...

  • Page 275

    _signal_issues srv_servo_signals_not_within_acquiring_wi ndow_due_to_servo_signal_issues 651h servo servo signals not within acquiring window due to servo signal issues. Srv_failure_during_tracking_band_lock_d ue_to_servo_signal_issues 652h servo failure during tracking band lock due to servo signal...

  • Page 276

    Unthread and will tr srv_unthread_retry_put_away_pin 671h servo exception: something prevented putting away the pin into the cartridge during un srv_unthread_retry_going_home 672h servo exception: something prevented the load arm from going to home position after pu srv_unthread_retry_stuck_on_guide...

  • Page 277

    Scsi_sts_rc_reserved_by_other_id 6a2h scsi scsi_sts_rc_reserved_cannot_issue_persis tent_reserve 6a3h scsi scsi_sts_rc_third_party_id_conflict 6a4h scsi srv_mon_too_many_variables 6a5h servo srv_mon_no_word_count 6a6h servo srv_mon_invalid_parameter 6a7h servo scsi_sapi_did_not_set_skey_ascq 6a8h sc...

  • Page 278

    Scsi_failed_status_40 6d9h scsi scsi internal status only - not reported srv_unthread_retry_pivot_track_engage 6dah servo exception: not able to engage lower track during unthread. Will try again. Srv_thread_retry_pivot_track_engage 6dbh servo exception: not able to engage lower track during thread....

  • Page 279

    Calib_illegal_heracles_reg 708h calibration attempt to access a heracles (pre-lto2hh) or mouri (lto2hh and up) register not srv_reel_unexpected_message_in_fast_rep osition_state 709h servo calib_gain_done_warning_low_head_output 70ah calibration srv_cannot_calculate_servo_band_id_beca use_both_servo...

  • Page 280

    _non_register_iid scsi_sts_rc_exclusive_access_reg_prevent _non_zero_prevent_bit 732h scsi scsi_sts_rc_non_zero_pr_key 733h scsi scsi_sts_rc_pr_key_no_match 734h scsi scsi_sts_rc_iid_not_registered_yet 735h scsi scsi_sts_rc_type_scope_no_match 736h scsi scsi_sts_rc_pr_reserved_exist 737h scsi scsi_s...

  • Page 281

    Calib_rsv_761 761h calibration calib_rsv_762 762h calibration calib_rsv_763 763h calibration calib_rsv_764 764h calibration calib_rsv_765 765h calibration calib_rsv_766 766h calibration calib_rsv_767 767h calibration calib_rsv_768 768h calibration calib_rsv_769 769h calibration calib_rsv_76a 76ah ca...

  • Page 282

    Manager dsm_mic_inquiry_returned_invalid_cartridg e_gen 795h data set manager mic firmware task returned illegal cartridge generation srv_reel_active_function_is_null 796h servo scsi_cmd_refs_exhausted_24 797h scsi scsi task command references exhausted at checkpoint 24 scsi_cmd_refs_exhausted_25 79...

  • Page 283

    Srv_hw_divider_divide_by_zero 7cch servo srv_hw_divider_overflow 7cdh servo srv_timeout_during_head_stepper_moving_t o_position_cl_far 7ceh servo srv_timeout_during_head_stepper_moving_t o_position_cl_near 7cfh servo srv_thr_load_arm_at_old_sensor7 7d0h servo notification that load arm has passed th...

  • Page 284

    Tape_cmd_retry 7f9h tape write: unable to service the receiving command at this point, ask sender to retr srv_no_data_band_id 7fah servo not enough good top and bottom pes to extract databand id. Srv_seq_drive_not_initialized 7fbh servo scsi_reserved_7fc 7fch scsi cm_write_failed 7fdh medium auxilia...

  • Page 285

    Srv_thr_unthread_stuck_on_guides_exceed ed_retries 81eh servo load arm stuck between corner and end of guides during unthread. Srv_unthread_last_ditch_failed_to_put_pin _away 81fh servo cannot unthread srv_var_speed_ramp_up_requires_read_or_ write_tracking_mode 820h servo srv_thr_load_arm_moving_to_...

  • Page 286

    Srv_head_stepper_searching_for_servo_ba nd 844h servo thr_diag_unknown_command 845h general threader task received unknown diagnostic command srv_no_open_loop_head_position_prior_to_ closed_loop 846h servo thr_seq_bicell_unknown_parameter 847h general bicell select command had an unknown parameter t...

  • Page 287

    Srv_ext_interface_busy 874h servo controller fw is processing previous alert or cmd response srv_gaio_asic_in_pwrfail 875h servo on power up gaio asic is in power fail mode svr_m1_coarse_sweep_failed 876h general drive reel fail for coarse sweep svr_m1_fine_sweep_failed 877h general svr_m1_dead_band...

  • Page 288

    Grabber srv_unthread_missed_pin_grabber 8a1h servo srv_thread_unable_to_lock_drive_hub 8a2h servo srv_thread_drive_hub_may_not_be_locked 8a3h servo srv_thr_drive_hub_not_locked 8a4h servo unable to lock drive hub inner hub to outer hub. Srv_thread_unable_to_lock_drive_flange 8a5h servo unable to loc...

  • Page 289

    Srv_ext_dac_not_calibrated 8d3h servo external dac is not calibrated, use default value srv_head_azimuth_max_mean_exceeded 8d4h servo srv_head_azimuth_max_stdev_exceeded 8d5h servo srv_head_azimuth_max_fwd_rev_delta_mea n_exceeded 8d6h servo srv_thr_tray_load_already_at_tray_in 8d7h servo cart tray ...

  • Page 290

    N_one srv_vcm_hall_sensor_is_not_calibrated_us e_default 902h servo exception when hall sensor is not calibrated srv_unthread_unpick_exceeded_retries 903h servo unable to unpick cartridge pin srv_reel_screen_test_rejected_cart_inser ted 904h servo reel motor screen test rejected because cartridge is...

  • Page 291

    Scsi_detected_worm_cm_conflict 92ah scsi the cm worm indicators do not agree with each other. Srv_thr_reel_motor_change_tension_erro r 92bh servo threader exception while calling reel_motor_position_move_change_tension_pcc() srv_reel_position_hold_not_at_target 92ch servo use for exception dsm_cmpr_...

  • Page 292

    Tape_worm_bad_cm 952h tape the cm is not readable and the smw indicates worm cartridge tape_worm_bad_cm_and_fid_mismatch 953h tape the cm is not readable, the smw indicates rd/wr cartridge and the fid indicates srv_vcm_hall_damping_factor_not_within_ range 954h servo damping factor has to be between...

  • Page 293

    Srv_trk_msg_in_process 977h servo tracking isr is busy srv_head_stepper_illegal_state_sensor_st ate_machine 978h servo srv_head_stepper_illegal_state_open_loo p_state_machine 979h servo srv_head_stepper_illegal_state_closed_lo op_state_machine 97ah servo srv_head_stepper_illegal_state_find_serv o_ba...

  • Page 294

    Srv_flange_unlocked_without_cartridge 099bh servo flange is unlocked but there's no cartridge present srv_servo_enum_speed_obsolete 099ch servo servo speed enum (2-7) will not be supported for gen3hh or later scsi_drive_mode_does_not_allow_read_wri te_access_to_worm_media 099dh scsi worm control is ...

  • Page 295

    Hub. Srv_unthread_pull_no_stall 09c7h servo pulling tape to the cart reel didn't stall srv_unthread_pull_unexpected_stall 09c8h servo pulling tape to cart reel stalled before the pin could reach the grabber mover. Srv_reel_hw_did_not_detect_stop 09c9h servo this is an exception when hw does not dete...

  • Page 296

    Fc_interface_ctio_crcerrorautogood 09f2h scsi sdram crc error occurred after autogood sent. Fc_interface_ctio_ctiom0pcberr 09f3h scsi sfc_fcp_tgt_ctiom0start out of resources fc_interface_ctio_confirmrecpcberr 09f4h scsi sfc_confirmrec out of resources fc_interface_ctio_dmaparityerror 09f5h scsi dma...

  • Page 297

    Srv_pin_grabber_init_no_c1 0a22h servo cannot move pin grabber from zone a to zone c1 during initialization srv_pg_hall_cal_out_of_limit 0a23h servo at least one hall sensor calibration parameter is out of limit srv_load_unload_stuck 0a24h servo errors encountered at both load and unload direction, ...