HP LTO Ultrium 6 Tape Drives Technical Reference Manual

HP LTO Ultrium 6 Tape Drives Technical Reference Manual

HP LTO Ultrium 6 Tape Drives Technical

Reference Manual

Volume 1: Hardware Integration

Abstract

This is one of five volumes that document HP LTO Ultrium 6 tape drives (Fibre Channel and SAS). This volume provides hardware integration information. See

“Support and other resources” (page 127)

for details of the other guides.

HP Part Number: n/a

Published: October 2012

Edition: First

© Copyright 2012 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgements

Windows is a U.S. registered trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

Warranty

WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty

Contents

1 Physical dimensions....................................................................................7

Fixing dimensions.....................................................................................................................7

Full-height drives..................................................................................................................7

Half-height drives.................................................................................................................7

2 Electrical and environmental requirements......................................................9

Electrical fit..............................................................................................................................9

Power requirements..............................................................................................................9

Voltage and current requirements...........................................................................................9

Full-height drives..............................................................................................................9

Half-height drives............................................................................................................9

Airflow requirements...............................................................................................................10

Measuring internal drive temperatures..................................................................................10

Extracting internal temperature information.......................................................................10

Optional fan plate.............................................................................................................11

3 Front panel and LEDs................................................................................12

Front panel features................................................................................................................12

Full-height drives................................................................................................................12

Reset switch..................................................................................................................12

Half-height drives...............................................................................................................13

Usual meaning of LEDs............................................................................................................13

LED patterns...........................................................................................................................14

Full-height drives................................................................................................................14

Half-height drives...............................................................................................................16

During firmware upgrade....................................................................................................18

Replacing the front panel.........................................................................................................18

Parts needed.....................................................................................................................18

Replacing the front panel on an full-height LTO Ultrium drive....................................................18

Replacing the front panel on a half-height LTO Ultrium drive.....................................................19

4 Rear panel and connectors........................................................................20

Rear panel components—full-height drives.................................................................................21

Rear panel components—half-height drives................................................................................23

LEDs.....................................................................................................................................24

Power-on self-test failure......................................................................................................24

Port initialized...................................................................................................................24

Port activity.......................................................................................................................25

Fibre Channel addressing........................................................................................................25

Connectors............................................................................................................................26

Fibre Channel connector.....................................................................................................26

SAS connector...................................................................................................................26

Automation and remote LED connector.................................................................................26

Connector pins.............................................................................................................26

ACI operation..........................................................................................................26

ADI operation..........................................................................................................27

Remote LEDs.................................................................................................................28

Automation and remote LED connector schematic..............................................................28

iADT (Ethernet) port.......................................................................................................29

Diagnostic Serial Port connector...........................................................................................30

Fan control connector.........................................................................................................30

Contents 3

5 Cartridges...............................................................................................31

Choosing cartridges................................................................................................................31

Labeling cartridges.................................................................................................................31

Write-protecting cartridges.......................................................................................................31

Cartridge life.........................................................................................................................32

Caring for cartridges...............................................................................................................32

Avoiding condensation.......................................................................................................32

Conditions in use..........................................................................................................32

Conditions in storage.....................................................................................................32

Maximizing tape life......................................................................................................32

LTO Cartridge Memory............................................................................................................33

LTO Cartridge Memory issues..............................................................................................33

More information...............................................................................................................34

6 Planning your system configuration.............................................................35

Modes of usage.....................................................................................................................35

Optimizing performance.........................................................................................................35

Dedicated bus...................................................................................................................35

System performance...........................................................................................................35

Data rate matching............................................................................................................35

Performance checklist.........................................................................................................35

7 Installing and replacing drives....................................................................37

Installing in a server................................................................................................................37

Identifying the model..........................................................................................................37

Standards and safety.........................................................................................................37

Requirements.....................................................................................................................38

Mounting requirements..................................................................................................38

Server connections........................................................................................................38

Supported bus types.................................................................................................38

Connecting the drive..........................................................................................................39

SAS connector..............................................................................................................39

Backup software................................................................................................................39

Installing in a tape array..........................................................................................................40

Appropriate HP rack-mount systems......................................................................................40

Airflow requirements..........................................................................................................40

Identifying the drive............................................................................................................40

Modes of usage................................................................................................................40

Attaching to SAS...............................................................................................................40

Connecting to a Fibre Channel router or by SAS to a server or router........................................40

Fibre Channel connection...............................................................................................40

Server SAS connection...................................................................................................40

Replacing a drive...............................................................................................................41

Installing in a library...............................................................................................................41

Rear panel and connectors..................................................................................................41

Installing standalone drives......................................................................................................42

Identifying the drive............................................................................................................42

Connecting the drive..........................................................................................................42

SAS connection.............................................................................................................42

Moving drives....................................................................................................................42

8 Operating the drive..................................................................................43

Power-on self-test.....................................................................................................................43

Loading a cartridge................................................................................................................44

Unloading a cartridge.............................................................................................................45

Cleaning...............................................................................................................................45

4 Contents

Resetting drives in a library......................................................................................................46

9 Troubleshooting........................................................................................47

Emergency unload (forced eject)...............................................................................................47

General guidelines.................................................................................................................47

Diagnosing the problem..........................................................................................................48

Problems with the host computer..........................................................................................48

Computer does not boot up............................................................................................48

Computer boots, but does not recognize the drive.............................................................48

Problems with the drive and cartridge...................................................................................48

Tape drive does not power up.........................................................................................48

The application does not recognize the drive....................................................................49

The cartridge will not eject.............................................................................................49

The drive will not accept a cartridge................................................................................49

The computer no longer recognizes the drive in a tape array..............................................50

Problems with cleaning.......................................................................................................50

10 Special features for automation.................................................................51

Introduction............................................................................................................................51

Backup software................................................................................................................51

Drive Model ID String....................................................................................................51

Front panel for automation use.................................................................................................52

Full-height drives................................................................................................................52

Front panel for use in autoloaders....................................................................................53

Half-height drives...............................................................................................................54

Automation interface...............................................................................................................54

Automation Control Interface (ACI).......................................................................................55

Automation/Drive Interface (ADI).........................................................................................56

Internet Automation Device interface (iADT)...........................................................................56

Fan interface.....................................................................................................................58

Configuring autoload and library-controlled loads......................................................................58

Cartridge positions during load and unload..........................................................................59

Load scenarios..................................................................................................................60

Load scenario 1: Autoload..............................................................................................60

Load scenario 2: Library controlled.............................................................................60

Unload scenario 1: Autoload.....................................................................................60

Unload scenario 2: Library controlled..........................................................................60

Load/unload forces............................................................................................................61

Using Cartridge Memory (LTO-CM) in libraries...........................................................................61

Current libraries — barcodes...............................................................................................61

11 Drive error codes.....................................................................................62

Generic module (from 0000h)..................................................................................................62

Automation Control Interface (from 0400h)................................................................................62

Buffer manager (from 0800h)...................................................................................................65

Diagnostic control (from 1800h)................................................................................................66

Drive control (from 1C00h)......................................................................................................68

Drive monitor (from 2000h).....................................................................................................70

External interfaces (from 2400h)...............................................................................................70

Front panel interface (from 2800h)............................................................................................71

Host interface (from 2C01h).....................................................................................................71

Logical formatter (from 3000h).................................................................................................78

Logical media (from 3400h).....................................................................................................82

Logical pipeline control (from 3800h)........................................................................................83

Mechanism control (from 3C00h).............................................................................................83

Non-volatile data manager (from 4000h)..................................................................................84

Contents 5

Operating system (from 4400h)................................................................................................88

Physical formatter (from 4C00h)...............................................................................................88

Physical pipeline control (from 5000h).......................................................................................89

Physical side error recovery (from 5400h)..................................................................................91

Read/write control (from 5800h)..............................................................................................91

System architecture (from 6400h)..............................................................................................93

Tight integ (from 6800h)..........................................................................................................93

Trace logger (from 6C00h)......................................................................................................93

Mechanical interface (from 7400h)...........................................................................................94

Exception handler (from 7800h).............................................................................................108

SPI interface (from 7C00h).....................................................................................................108

Cartridge Memory (from 8000h)............................................................................................108

Fault log manager section (from 8400h)..................................................................................109

Infrastructure section (from 8800h)..........................................................................................110

Critical section (from 8C00h).................................................................................................111

SCSI module (from 9400h).....................................................................................................111

Automation/Drive Interface (from 9800h)................................................................................118

Management API (from 9C00h)..............................................................................................120

Servo (from A000h)..............................................................................................................121

Certificate manager (from A400h)..........................................................................................125

Cryptographic algorithms (from A800h)..................................................................................125

Master channel (from 3C00h)................................................................................................126

Hyper-drive (from F400h).......................................................................................................126

12 Support and other resources...................................................................127

Related documents................................................................................................................127

Documents specific to HP LTO Ultrium drives........................................................................127

Documentation map.........................................................................................................127

Drives—general..........................................................................................................127

Installation and configuration........................................................................................127

Operation..................................................................................................................127

Cartridges..................................................................................................................128

Interface....................................................................................................................128

Maintenance and troubleshooting.................................................................................128

Dealing with errors......................................................................................................128

LTO Ultrium features.....................................................................................................128

General documents and standardization.............................................................................130

Glossary..................................................................................................131

Index.......................................................................................................135

6 Contents

1 Physical dimensions

For the physical specification of the drive, see Chapter 1, “Physical Specification” in Specifications,

Volume 4 of the HP LTO Ultrium Technical Reference Manual.

Fixing dimensions

All screws should be M3 threaded. Do not use spring washers.

The recommended mounting torque is:

Full-height drives: 5.8 0.5 lb-in (0.60–0.70 Nm)

Half-height drives: 2.4 0.5 lb-in (0.24–0.30 Nm)

HP recommends 0.3 mm mounting clearance around all covers for isolation mounting movement.

Full-height drives

The recommended screw length depends on the thickness of the rails or enclosure into which the drive is mounted:

Server or Rail Thickness

> 1.5 mm 2.0 mm

> 1.0 mm 1.5 mm

1.0 mm

Recommended Screw Length

M3 x 6.0 mm

M3 x 6.0 mm

M3 x 5.0 mm

Mounting Points

Side

Bottom

Maximum Screw Penetration

5 mm

5 mm

For the dimensions of full-height drives, see the following figures in the HP LTO Ultrium 6 Tape

Drives Technical Reference Manual, Volume 4: Specifications:

Rear panel

Figure 4 Full-height Fibre

Channel

Full-height SAS

Bottom panel

Figure 1

Figure 1

Side panel

Figure 2

Figure 2

Front panel

Figure 3

Figure 3

Full-height FC drives: Volume 4, Specifications, figures 1, 2 and

Full-height SAS drives: Volume 4, Specifications, figure 2

Half-height drives

Figure 5

Mounting Points

Side

Bottom

Maximum Screw Penetration

3 mm

2.1 mm

Fixing dimensions 7

For the dimensions of half-height drives, see the following figures in the HP LTO Ultrium 6 Tape

Drives Technical Reference Manual, Volume 4: Specifications:

Half-height Fibre

Channel

Half-height SAS

Bottom panel

Figure 6

Figure 6

Side panel

Figures 7 and 8

Figures 7 and 9

Front panel

Figure 10

Figure 10

Rear panel

Figure 11

Figure 12

8 Physical dimensions

2 Electrical and environmental requirements

Electrical fit

Power requirements

NOTE: SAS drives do not have a regular 4-pin power connector and should be powered through the SAS connector.

The following are the PSU requirements for FC and SAS full-height and half-height drives:

Voltage

5V

12V

Specification

Max voltage

Min voltage

Max steady-state current

Max transient current

Max steady-state power

Max transient power

Max noise/ripple

Half-height drives

Typical Current

3.50A

0.60A

5V

5.25V

4.75V

3.44A

3.75A

17.20W

18.75W

150 mVpp

FC Drives

12V

13.2V

10.8V

0.54A

2.01A

7.20W

24.12W

150 mVpp

Maximum Current

<4.10A

<2.60A

See also details in Chapter 2, “Electrical Requirements” in Specifications, Volume 4 of the HP LTO

Ultrium Technical Reference Manual.

The drive is specified to operate at 5V 5% and 12V 10%.

Voltage and current requirements

Voltage and current requirement are as follows:

Full-height drives

5V

5.25V

4.75V

TBD A

TBD A

TBD W

TBD W

150 mVpp

SAS Drives

12V

13.2V

10.8V

TBD A

TBD A

TBD W

TBD W

150 mVpp

Specification

Max voltage

Min voltage

Max steady-state current

Max transient current

Max steady-state power

5V

5.25V

4.75V

3.51A

3.85A

17.55W

FC Drives

12V

13.2V

10.8V

0.66A

1.90A

7.92W

5V

5.25V

4.75V

TBD A

TBD A

TBD W

SAS Drives

12V

13.2V

10.8V

TBD A

TBD A

TBD W

Electrical fit 9

Specification

Max transient power

Max noise/ripple

5V

19.25W

150 mVpp

FC Drives

12V

22.80W

150 mVpp

5V

TBD W

150 mVpp

SAS Drives

12V

TBD W

150 mVpp

Airflow requirements

HP LTO Ultrium drives require forced airflow to ensure that components never exceed critical temperatures.

Airflow should be from front to back. The required flow depends on the ambient air temperature:

6.0 cfm (0.17 cubic meters per minute or 10.19 cubic meters per hour) (0.015 inches H

2

O supplied pressure drop) for 35°C ambient air temperature.

8.0 cfm (0.23 m

3

/min. or 13.60 m

3

/h) (0.026 inches H

2

O supplied pressure drop) for 40°C ambient air temperature.

These requirements and the operating temperature specification should keep the internal temperature around the media to less than 45°C and ensure reliable operation.

The airflow does not require filtering if the air contamination specifications are met. See “Climatics” in Chapter 4, “Environmental Specification” in Specifications, Volume 4 of the HP LTO Ultrium

Technical Reference Manual.

CAUTION: Care must be taken that empty bays in the server have the appropriate blanking plates installed so that airflow is maintained. Refer to your server documentation.

Measuring internal drive temperatures

The recommended method of measuring the temperature of critical components is to load a data cartridge, set the drive stream-writing at maximum data rate for a minimum of one hour, and then read the drive-reported maximum temperature since cartridge loaded (MaxTempSinceCartLoaded) value. This is the peak maximum temperature that the Primary Temperature Sensor has reached since the load event. It correlates closely with the temperature of the most critical components, and the tape path.

The following example is of a full-height LTO-6 FC drive in 25°C ambient conditions:

1.

After one hour of writing to the drive at the maximum data transfer rate,

MaxTempSinceCartLoaded = 47.

2.

This gives a Primary Temperature Sensor reading of 47–25 = 22°C temperature rise over ambient.

3.

This correlates to the 6.1 cfm airflow rate, which is sufficient for operation up to 35°C ambient.

If this application is to run at 40°C ambient, additional airflow is required.

Extracting internal temperature information

You can extract the maximum temperature since cartridge loaded (MaxTempSinceCartLoaded) reading via a host command (FC or SAS), or via the ACI send_scsi command as follows:

1.

Send a SEND DIAGNOSTICS command:

1D 11 00 00 08 00 with the following data out

93 00 00 04 00 00 20 2A

2.

Send a RECEIVE DIAGNOSTICS command:

1C 01 93 00 44 00

10 Electrical and environmental requirements

3.

The MaxTempSinceCartLoaded value is ASCII encoded in bytes 22–29 of the incoming data.

Example SCSI trace:

SendDiagnostic |1D 11 00 00 08 00 |00008|00|00|

Data Out |93 00 00 04 00 00 20 2A |

ReceiveDiagResults |1C 01 93 01 00 00 |0009C|00|00|

Data In |93 00 00 98 30 30 30 30 31 41 31 32 20 30 30 30 |

Data In |30 31 41 31 32 20 30 30 30 30 31 41 37 34 20 30 |

Data In |30 30 30 31 39 31 37 20 0D 0A 30 30 30 30 30 30 |

Data In |30 30 20 30 30 30 30 30 30 30 30 20 30 30 30 30 |

Data In |33 32 30 30 20 30 30 30 30 30 35 30 30 20 0D 0A |

Data In |46 46 46 46 38 30 30 30 20 46 46 46 46 38 30 30 |

Data In |30 20 46 46 46 46 38 30 30 30 20 46 46 46 46 38 |

Data In |30 30 30 20 0D 0A 46 46 46 46 38 30 30 30 20 46 |

Data In |46 46 46 38 30 30 30 20 30 30 30 30 30 35 30 30 |

Data In |20 30 30 30 30 30 35 30 30 20 0D 0A |

4.

Translate each character received from ASCI to hex numbers.

For the example above: 30 30 30 30 31 41 37 34 = 00001A74h

5.

Convert this number to decimal = 6772

6.

Divide this number by 256 to give the temperature in °C = 26.4°C

Optional fan plate

If the airflow requirements cannot be met by the existing fans in a server then the optional fan plate may be required. This a plastic plate with an embedded fan that fits on the back of a half-height drive. The fan plugs into the Fan Connector (see

“Rear panel components—half-height drives”

(page 23)

and

“Fan control connector” (page 30)

) and the drive controls this fan to self-manage its own internal temperature, turning the fan on and off as needed. For details of the optional Fan

Plate, contact your HP Technical Support Representative.

Airflow requirements 11

3 Front panel and LEDs

HP LTO Ultrium 6 products have three front panel designs:

System, for use in servers, rack mounts and other non-automation applications—see “Front panel features” below

Automation, for use when the drive is embedded in automation applications—see

“Front panel for automation use” (page 52)

A third front panel allowing drives to be used in autoloaders where the front panel cannot exceed the drive form factor in height and width—see

“Front panel for use in autoloaders”

(page 53)

The drive is not designed to operate without a front panel (even in automation applications). The front panel was designed to meet Section 508 of the Rehabilitation Act accessibility guidelines.

Front panel features

Full-height drives

Figure 1 Front panel for full-height LTO-6 drives

1. Eject button

3. LEDs

2. Access hole for emergency reset switch

Reset switch

The emergency reset switch allows you to reset the drive without powering off the drive if the drive stops responding. Access to the switch is through a small hole. It can be activated by a thin object, such as the end of a straightened paper-clip.

NOTE: Only full-height drives have a reset switch.

12 Front panel and LEDs

Half-height drives

Figure 2 Front panel for half-height LTO-6 drives

1. LEDs 2. Eject button

Usual meaning of LEDs

The five LEDs, Ready, Drive Error, Tape Error, Clean and Encryption usually have the following meanings:

Ready

Drive Error

Tape Error

Clean

Encryption

Green. Indicates power and activity:

Off

Power off or self-test failure

On

Powered on and ready for use, but no activity

Flashing

Fast flash

Engaged in activity, such as responding to Read, Write or Space commands or performing a self-test

Downloading new firmware.

Repeating pattern

A repeating pattern of short and long flashes indicates that the drive is in

OBDR mode.

Orange. Indicates drive problems:

Off

Flashing

No fault

Unrecoverable hardware failure. A power cycle or successful tape load will turn the LED off, but the LED will start flashing again if the same operation is performed and the hardware fault is still present

Orange. Indicates tape problems:

Off

No fault

Flashing

Current tape is faulty, such as unreadable cartridge memory or unsupported type. Do not use the cartridge; replace it. The LED will go out when a tape load begins.

Orange. Indicates whether the drive needs cleaning.

Off

Cleaning not required

On

Cleaning cartridge being used. The Ready LED flashes.

Flashing

Cleaning needed. The LED continues to flash if the drive is power cycled, and will only go out after a supported cleaning tape has been used.

Blue/orange. Indicates whether encryption is enabled or not.

Off

On (Blue)

Flashing

(Blue/Orange)

No key is present in the drive. Encryption and decryption are not enabled.

A key is present in the drive. Encryption and decryption are enabled.

Encryption/decryption error.

Usual meaning of LEDs 13

LED patterns

There are other patterns usually involving several LEDs, which have the following meanings.

NOTE: The Encryption LED is not included in these tables because it operates independently of the other four LEDs. Its states are given in the description above.

Full-height drives

LEDs Cause Action required

All LEDs OFF.

Drive may not have power, may be faulty or may have been power cycled or reset during a firmware upgrade.

1.

Ensure the drive is switched on.

2.

If the green LED on the power switch is not on, check the power cable and replace it if necessary.

3.

If the drive has just been switched on or reset, the LED pattern should change after 1 second.

If not, the drive has Firmware Image Corruption

(caused by being switched off or reset during firmware upgrade). Return it to the factory for repair or reprogramming.

4.

If power is present and all LEDs remain off, try performing an interface operations (SCSI or

ACI). If the drive does not respond, or power-cycle the drive.

5.

If it still fails, call for service.

Ready and Clean OFF. Drive Error and Tape Error

FLASHING.

The drive has failed to execute power-on self test

(POST).

Power cycle or reset the drive.

If the condition reappears, call for service.

Ready ON.

The drive is ready for operation.

None. This is normal.

14 Front panel and LEDs

Firmware is being reprogrammed.

Ready FLASHES twice, then pauses ON, then

FLASHES twice.

The drive is in OBDR mode.

None.

If the drive is upgrading firmware, do not reset or power cycle it.

If you need to exit OBDR mode, power cycle or reset the drive.

NOTE: OBDR is not supported in all versions of the drive.

LEDs Cause

Clean FLASHING. (Other LEDs may be on or flashing.)

The drive requires cleaning.

Ready FLASHING and Clean ON. (Other LEDs may be on or flashing.)

Cleaning is in progress.

Action required

Load an LTO Ultrium Universal cleaning cartridge to clean the heads. See

“Cleaning” (page 45)

for instructions.

If the Clean LED is still flashing when you load a new or known data cartridge after cleaning, call for service.

None. The cleaning cartridge will eject on completion.

The cleaning cycle can take up to 5 minutes .

Tape Error FLASHING. (Other LEDs may be on or flashing.)

The drive believes the current tape or the tape just ejected is faulty.

Unload the tape cartridge. Make sure that it is a valid format: an LTO Ultrium data cartridge or LTO

Ultrium Universal cleaning cartridge.

Reload the cartridge. If the Tape Error LED still flashes or starts flashing during the next backup, load a new or known, good cartridge.

If the Tape Error LED is now off, discard the

‘suspect’ tape cartridge. If it is still on, call for service.

Tape ejects immediately and Tape Error FLASHES.

(Other LEDs may be on or flashing.)

The tape cartridge memory (CM) may be faulty.

Write-protect the cartridge by sliding the red switch on the cartridge. The tape can be loaded and the data read. Once the data is recovered, discard the cartridge.

Drive Error FLASHING. (Other LEDs may be on or flashing.)

The drive mechanism has detected an error.

Load a new cartridge. If the error persists, power cycle or reset the drive.

If the Drive Error LED remains on, call for service.

Drive Error, Tape Error and Ready FLASH.

There is a firmware download problem.

Insert a cartridge to clear the LED sequence; the drive will continue using the old firmware. If the condition persists, call for service.

Drive Error and Ready ON with Tape Error and

Clean OFF. Sequence alternates repeatedly.

The drive has a firmware error.

Power cycle or reset the drive. If the sequence reoccurs, upgrade the firmware. If the condition persists, call for service.

LED patterns 15

Half-height drives

LEDs Cause Action required

All LEDs OFF.

Drive may not have power, may be faulty or may have been power cycled or reset during a firmware upgrade.

1.

Ensure the drive is switched on.

2.

If the green LED on the power switch is not on, check the power cable and replace it if necessary.

3.

If the drive has just been switched on or reset, the LED pattern should change after 1 second.

If not, the drive has Firmware Image

Corruption (caused by being switched off or reset during firmware upgrade). Return it to the factory for repair or reprogramming.

4.

If power is present and all LEDs remain off, try performing an interface operations (SCSI or ACI). If the drive does not respond, or power-cycle the drive.

5.

If it still fails, call for service.

Ready and Clean OFF. Drive Error and Tape

Error FLASHING.

The drive has failed to execute power-on self test (POST).

Power cycle or reset the drive.

If the condition reappears, call for service.

Ready ON.

The drive is ready for operation.

None. This is normal.

Ready FLASHING.

The drive is carrying out a normal activity (read, write).

None.

If the drive is upgrading firmware, do not reset or power cycle it.

Ready FLASHES twice, then pauses ON, then

FLASHES twice.

The drive is in OBDR mode.

If you need to exit OBDR mode, power cycle or reset the drive.

NOTE: OBDR is not supported in all versions of the drive.

Ready FLASHING fast. (Other LEDs may be on or flashing.)

The drive is downloading firmware.

None.

Do not reset or power-cycle the drive.

16 Front panel and LEDs

LEDs Cause

Ready OFF, others ON.

Firmware is being reprogrammed.

Action required

None.

Do not reset or power-cycle the drive.

Clean FLASHING. (Other LEDs may be on or flashing.)

The drive requires cleaning.

Load an LTO Ultrium Universal cleaning cartridge to clean the heads. See

“Cleaning” (page 45)

for instructions.

If the Clean LED is still flashing when you load a new or known data cartridge after cleaning, call for service.

Ready FLASHING and Clean ON. (Other LEDs may be on or flashing.)

Cleaning is in progress.

None. The cleaning cartridge will eject on completion.

The cleaning cycle can take up to 5 minutes .

Tape Error FLASHING. (Other LEDs may be on or flashing.)

The drive believes the current tape or the tape just ejected is faulty.

1.

Unload the tape cartridge. Make sure that it is a valid format: an LTO Ultrium data cartridge or LTO Ultrium Universal cleaning cartridge.

2.

Reload the cartridge. If the Tape Error LED still flashes or starts flashing during the next backup, load a new or known, good cartridge.

3.

If the Tape Error LED is now off, discard the

‘suspect’ tape cartridge. If it is still on, call for service.

Tape ejects immediately and Tape Error

FLASHES. (Other LEDs may be on or flashing.)

Write-protect the cartridge by sliding the red switch on the cartridge. The tape can be loaded

LED patterns 17

LEDs Cause Action required

The tape cartridge memory (CM) may be faulty.

and the data read. Once the data is recovered, discard the cartridge.

Drive Error FLASHING. (Other LEDs may be on or flashing.)

The drive mechanism has detected an error.

Load a new cartridge. If the error persists, power cycle or reset the drive.

If the Drive Error LED remains on, call for service.

Drive Error and Ready ON with Tape Error and

Clean OFF. Sequence alternates repeatedly.

The drive has a firmware error.

Power cycle or reset the drive. If the sequence reoccurs, upgrade the firmware. If the condition persists, call for service.

During firmware upgrade

CAUTION: Do not reset or power-cycle the drive until the firmware upgrade is complete, otherwise the drive will be not be able to operate.

If a firmware upgrade is successful, the LEDs light in sequence during the download as shown in the table above.

If a corrupt or incompatible image is downloaded from tape, the Ready LED will remain on steadily and the Tape Error LED will flash until a tape load is started. The other LEDs will be off.

Replacing the front panel

CAUTION: At all times please observe ESD precautions as indicated in the installation manual supplied with the tape drive. Static electricity can damage electronic components. Touch a bare metal part of the computer, such as a back plate, before you attempt to install or remove the drive.

Parts needed

Replacement front panel

Small bladed screwdriver (125x5 slotted or smaller)

Replacing the front panel on an full-height LTO Ultrium drive

1.

Use the screwdriver to release the tabs at the top of the chassis and underneath.

18 Front panel and LEDs

2.

Pull the front panel towards you and away from the drive.

To replace the panel, line up the four tabs with the chassis and push the panel firmly into place. There will be a slight click when the lugs are located in the chassis.

Replacing the front panel on a half-height LTO Ultrium drive

1.

Use the screwdriver to release the tab on the right side of the chassis (next to the red warranty sticker).

2.

Swing the front panel out slowly, pulling it gently to the left, so that the lugs release on the left side of the chassis.

NOTE:

Do not swing the panel too far out or pull too hard, as the lugs are quite delicate.

3.

To replace the panel, line up the lugs on the left side of the chassis and swing the panel firmly into place.

There will be a slight click when the lug is located on the right side of the chassis.

Replacing the front panel 19

4 Rear panel and connectors

The rear panel contains the connector interface that allows the tape drive to communicate with a tape library or host computer system. The panel includes the following connectors:

Two SFP duplex-LC optical fibre connectors (though only one might be installed)

Or: An SAS connector

Combined ACI/ADI and remote LED connector

Diagnostic serial port

Fan connector (SAS drives only)

Power connector (Fibre Channel drives only)

• iADT (Ethernet) connector

20 Rear panel and connectors

Rear panel components—full-height drives

Figure 3 Rear panel components for a full-height Fibre Channel drive

1. iADT Ethernet (10-pin)

3. Port 1 (B) slot for optional transceiver

5. ADI/ACI LEDs (16-pin)

7. Port 0 (A) LED

9. Diagnostic serial port (4-pin)

2. 8 GB FC transceiver module, port 0 (A) (by default only the port 0 slot is filled)

4. Power

6. AL_PA jumpers (may not be loaded)

8. Port 1 (B) LED

Position of pin 1 (which may be different from previous generation drives)

For the dimensions of the rear panel of full-height FC drives, see Figure 4 in the HP LTO Ultrium 6

Tape Drives Technical Reference Manual, Volume 4: Specifications.

Rear panel components—full-height drives 21

Figure 4 Rear panel components for a full-height SAS drive

1. Diagnostic serial port (4-pin)

3. iADT Ethernet (10-pin)

5. ADI/ACI, LEDs (16-pin)

7. Host secondary port LED

2. External fan support (6-pin)

4. SAS SFF 8482 connector (includes power)

6. Active SAS management port (9-pin)

8. Host primary port LED

Position of pin 1 (which may be different from previous generation drives)

For the dimensions of the rear panel of full-height SAS drives, see Figure 5 in the HP LTO Ultrium

6 Tape Drives Technical Reference Manual, Volume 4: Specifications.

22 Rear panel and connectors

Rear panel components—half-height drives

Figure 5 Rear panel components for a half-height FC drive

1. ADI/ACI LEDs (16-pin)

3. Port 0 (A) LED

5. iADT Ethernet (10-pin)

2. Diagnostic serial port (4-pin)

4. DIP switch (4-pin) (may not be loaded)

6. 8 GB FC transceiver module, port 0 (A). Empty Port 1

(B) slot below. By default only the port 0 slot is filled.

8. Dual-channel FC cage 7. Port 1 (B) LED

9. Molex Microfit power

Position of pin 1 (which may be different from previous generation drives)

For the dimensions of the rear panel of half-height FC drives, see Figure 11 in the HP LTO Ultrium

6 Tape Drives Technical Reference Manual, Volume 4: Specifications.

Rear panel components—half-height drives 23

Figure 6 Rear panel components for a half-height SAS drive

1. ADI/ACI LEDs (16-pin)

3. Host secondary LED

5. Host primary LED

7. External fan support (6-pin)

2. Active SAS management port (9-pin)

4. SAS connector (includes power)

6. Diagnostic serial port (4-pin)

8. iADT Ethernet (10-pin)

Position of pin 1 (which may be different from previous generation drives)

For the dimensions of the rear panel of half-height SAS drives, see Figure 12 in the HP LTO Ultrium

6 Tape Drives Technical Reference Manual, Volume 4: Specifications.

LEDs

The rear panel has two LEDs. In Fibre Channel drives, they indicate Port 0 and Port 1. In SAS drives, they indicate the Primary and Secondary ports.

Power-on self-test failure

If the firmware encounters a Power-On Self-Test failure, the drive will not initialize the ports and so will not respond over the FC or SAS interface. The two port LEDs will flash together at 1 cycle/second until the drive is reset or power-cycled.

Port initialized

Once the self-test in complete, the FC Port LEDs indicate whether the respective ports have been initialized, in other words, whether successful speed negotiation and loop initialization/old port mode has occurred.

24 Rear panel and connectors

Fibre Channel drives:

Port 0 LED

Off

On

Off

On

SAS drives:

Port 1 LED

Off

Off

On

On

Meaning

Neither port is initialized

Only port 0 is initialized

Only port 1 is initialized

Both ports are initialized

Primary Port LED

Off

On

Off

On

Secondary Port LED

Off

Off

On

On

Meaning

Neither port is initialized

Only port 0 is initialized

Only port 1 is initialized

Both ports are initialized

Port activity

When there is activity on a port, the appropriate port LED will flash with a periodicity of 1/10 second.

Fibre Channel addressing

The drive’s hard AL_PA can be configured through an ACI Set Drive Configuration command or

ADI Mode Select command

The value set is the Loop ID, an 8-bit value which is translated by the drive into a 7-bit Arbitrated

Loop Physical Address (AL_PA) according to Table 1:

Table 1 AL_PA and Loop ID look-up table

AL_PA Loop ID

76h

75h

74h

73h

72h

71h

7Ah

79h

78h

77h

7Dh

7Ch

7Bh

18h

1Bh

1Dh

1Eh

1Fh

23h

08h

0Fh

10h

17h

00h

01h

02h

04h

AL_PA

34h

35h

36h

39h

2Eh

31h

32h

33h

3Ah

3Ch

43h

45h

46h

47h

60h

6Fh

5Eh

5Dh

5Ch

5Bh

64h

63h

62h

61h

68h

67h

66h

65h

Loop ID AL_PA

59h

5Ah

5Ch

63h

53h

54h

55h

56h

65h

66h

67h

69h

6Ah

6Bh

Loop ID

4Eh

4Dh

4Ch

4Bh

52h

51h

50h

4Fh

4Ah

49h

48h

47h

46h

45h

AL_PA Loop ID

34h

33h

32h

31h

30h

2Fh

38h

37h

36h

35h

3Ch

3Bh

3Ah

39h

88h

8Fh

90h

97h

98h

9Bh

80h

81h

82h

84h

76h

79h

7Ah

7Ch

AL_PA

B1h

B2h

B3h

B4h

ABh

ACh

ADh

AEh

B5h

B6h

B9h

BAh

BCh

C3h

Loop ID AL_PA

DAh

DCh

E0h

E1h

E2h

E4h

D4h

D5h

D6h

D9h

CEh

D1h

D2h

D3h

1Dh

1Ch

1Bh

1Ah

19h

18h

21h

20h

1Fh

1Eh

25h

24h

23h

22h

Loop ID

Bh

Ah

9h

8h

Fh

Eh

Dh

Ch

7h

6h

5h

4h

3h

2h

Fibre Channel addressing 25

Table 1 AL_PA and Loop ID look-up table (continued)

26h

27h

29h

2Ah

2Bh

2Ch

2Dh

AL_PA

25h

Loop ID

70h

6Fh

6Eh

6Dh

6Ch

6Bh

6Ah

69h

AL_PA

49h

4Ah

4Bh

4Ch

4Dh

4Eh

51h

52h

Loop ID AL_PA

5Ah 6Ch

59h

58h

57h

6Dh

6Eh

71h

56h

55h

54h

53h

72h

73h

74h

75h

Loop ID

44h

43h

42h

41h

40h

3Fh

3Eh

3Dh

9Eh

9Fh

A3h

A5h

A6h

A9h

AAh

AL_PA

9Dh

Loop ID

2Eh

2Dh

2Ch

2Bh

2Ah

29h

27h

26h

AL_PA

C5h

C6h

C7h

C9h

CAh

CBh

CCh

CDh

Loop ID

17h

16h

15h

14h

13h

12h

11h

10h

AL_PA

E8h

EFh

Loop ID

1h

Connectors

Fibre Channel connector

FC drives are equipped with two SFP duplex-LC short-wave 8 Gb/s fibre connectors. The drives are capable of switched fabric attach, public loop or private loop and operate at 8 Gb/s, 4 Gb/s or 2 Gb/s after auto-speed negotiation.

SAS connector

SAS drives are equipped with a standard internal SAS connector. LTO-6 SAS drives do not have a regular power connector and should be powered via the SAS connector.

Automation and remote LED connector

The combined Automation and Remote LED Connector is a 16-pin wafer surface-mount right-angle connector. 10 pins are used for the ACI/ADI interface and 6 pins for the remote LEDs.

Connector pins

ACI operation

When used for ACI communications, the pins of the ACI connector are as follows:

5

6

3

4

Pin

1

2

7

ID

ACI_RX+

ACI_RX-

GND

ACI_TX-

ACI_TX+

ACI_DRV_SEN_L

Function

RS-422 Receive (+ side of the differential RS-422 line)

RS-422 Receive (– side of the differential RS-422 line)

Ground

RS-422 Transmit (– side of the differential RS-422 line)

RS-422 Transmit (+ side of the differential RS-422 line)

Drive Sense. It is tied low in the drive so that a library can sense the presence of the drive.

The library should have a pull-up resistor on this line.

Low: Drive present

High: Drive not present (3.3 volts)

ACI_LIB_SEN_L

Library Sense. The drive will not appear on the bus until commanded when low. The line is pulled up to 5V in the tape drive. The automation controller should pull this pin low.

Low: Drive is connected to an automation controller

High: Drive is standalone (3.3 volts)

26 Rear panel and connectors

Pin

8

9

ID

ACI_RST_L

ACI_ATN_L

Function

Tape drive reset. The line is pulled up to 3.3V in the drive. The drive will perform a Drive

Reset when this line is pulled low.

The drive sets this pin low to indicate to the automation controller that certain configured conditions have arisen, such as a SCSI Surrogate CDB.

No connection 10 —

Supported Baud rates

Baud Rate

9600

19200

38400

57600

115200

Notes

Default rate

For details of ACI commands, see Chapter 5 “Supporting LTO Ultrium Features” of the Software

Integration Guide, Volume 2 of the HP LTO Ultrium Technical Reference Manual.

ADI operation

When used for ADI communications, the pins of the ADI connector are as follows:

7

8

5

6

9

10

2

3

4

Pin

1

ID

+Tx a

–Rx d

–Tx a

–Rx d

Ground

–Tx d

–Rx a

+Tx d

–Rx a

Sense d

Sense d

Reset d

Signal aux

Function

RS-422 Receive from automation controller

RS-422 Receive from automation controller

Ground

RS-422 Transmit from tape drive

RS-422 Transmit from tape drive

Tied low in the drive so that a library can sense the presence of the drive.

The drive will not appear on the bus until commanded when low.

Hard reset (active low)

Reserved for future use

No connection

The ID names correlate with the descriptions in the T10 Automation/Drive Interface Transport

Protocol (ADT).

Supported Baud rates

Baud Rate

9600

19200

38400

57600

76800

Notes

Default rate

Connectors 27

Baud Rate

115200

153600

230400

460800

921600

Notes

Remote LEDs

The pins for the remote LED connector are as follows:

Pin 11

Pin 12

Pin 13

Pin 14

Pin 15

Pin 16

Ground

SAS Secondary Port and FC Port A Status LED output

SAS Primary Port and FC Port B Status LED output

Host controlled (Beacon) LED output

Encryption LED output

5V supply

Automation and remote LED connector schematic

Figure 7 ADI-LED connector schematic

Notes:

The maximum LED current supported is 25 mA.

There should be a current limiting resistor on each LED output.

The maximum off voltage on the transistor collector must not exceed 5.5V.

The maximum on voltage for the transistor is 0.4V.

The same circuit configuration as shown in

“LED driver circuit” (page 29)

is used for all LED ports.

The library-controlled or Beacon LED is driven by the AMI_LED_OUT signal.

28 Rear panel and connectors

Figure 8 LED driver circuit

iADT (Ethernet) port

Figure 9 iADT port schematic

Notes:

The maximum LED current supported is 25 mA.

There should be a current limiting resistor on each LED output.

The maximum off voltage on the transistor collector must not exceed 5.5V.

The maximum on voltage for the transistor is 0.4V.

The same circuit configuration as shown in

“LED driver circuit” (page 29)

is used for all LED ports.

Connectors 29

Diagnostic Serial Port connector

Figure 10 Diagnostic Serial Port connector schematic

Fan control connector

Figure 11 Fan connector schematic

Notes:

FAN SENSE is used to detect fan rotation.

FAN PRESENT is used to detect that a fan has been connected to the drive. A fan is deemed to be present when this line is grounded. To achieve this, it is recommended that pins 5 and

6 are tied together on the mating half of the connector.

The power supply to the fan is a steady 12V.

The fan speed is controlled via a PWM signal (pin3).

A four-wire fan is required.

NOTE: If you intend to plug a fan into this connector to provide the necessary airflow through the drive, consult your HP Technical Support Representative for details of the fan specification required.

30 Rear panel and connectors

5 Cartridges

Choosing cartridges

HP recommends HP LTO-6 Ultrium 6.25 TB (2.5:1 compression) cartridges.

HP LTO Ultrium drives will also support other lower capacity HP and non-HP LTO Ultrium cartridges but the performance of your drive may be restricted. Data transfer rates will be slower on LTO

Ultrium 5 3000 GB (2:1 compression) cartridges compared to LTO Ultrium 6 6.25 TB (2.5:1 compression) cartridges. Do not use HP DLTIIItape or DLTIVtape cartridges. The size and shape of

LTO Ultrium media is very similar to that of DLT cartridges in order to make it easy for automation/library vendors to integrate LTO Ultrium into existing DLT libraries. Compatible media can be recognized by the LTO Ultrium logo, which is the same as the logo on the front of your drive.

NOTE: HP LTO Ultrium 6 tape drives are not compatible with LTO Ultrium 1, 2 or 3 media, which will be rejected as unsupported. The Tape Error LED will light.

HP recommends HP LTO Ultrium cartridges as follows:

LTO Ultrium 6 6.25 TB (2.5:1 compression) RW for multiple reading and writing

LTO Ultrium 6 6.25 TB (2.5:1 compression) WORM cartridges. WORM (Write-Once,

Read-Many) cartridges guard against accidental or malicious alteration of data on the tape cartridge. You can append data to a WORM data cartridge to use the full capacity but not erase or overwrite existing data. WORM data cartridges have a distinctive, two-tone cartridge color. To check whether your backup or archive software application supports WORM cartridges, refer to the web site: www.hp.com/go/connect .

Labeling cartridges

The label and write-protect switch are on the rear face of the cartridge, as illustrated.

Never use non-standard labels, and never stick anything to the cartridge other than in the label area.

Write-protecting cartridges

If you want to protect the data on a cartridge from being altered or overwritten, you can write-protect the cartridge. Do this before you load the cartridge into the drive. If you slide the write-protect tab after the cartridge is inserted in the drive, the change will not take effect until the cartridge is ejected and reloaded, and you will damage the tape drive.

CAUTION: Write-protection will not prevent a cartridge being erased by bulk-erasure or degaussing. Do not bulk erase LTO Ultrium format cartridges. This will destroy pre-recorded servo information and render the cartridge unusable.

To write-protect a cartridge, slide the write-protect tab by the label area on the rear face of the cartridge to close the hole.

Note the padlock on the tab that indicates that the cartridge is protected.

To write-enable a cartridge, slide the write-protect tab back so that the hole is open, before loading the cartridge into the drive.

Choosing cartridges 31

Cartridge life

It is recommended that cartridges are used for no more than 260 full backup operations. Under severe environmental conditions, particularly where the tape drive is used at low humidity or if certain areas of the tape are accessed frequently, the number of backup operations should be limited even further.

Caring for cartridges

Avoiding condensation

Condensation is a problem for tape drives and cartridges. To minimize the chance of condensation, stay within the specifications for using and storing cartridges below and observe the following guidelines:

Position the drive where the temperature is relatively stable—away from open windows, heat sources and doors.

Avoid leaving cartridges in severe temperature conditions, for example, in a car standing in bright sunlight.

Avoid transferring data (reading from and writing to cartridges) when the temperature is changing by more than 1°C (1°F) per hour.

If you bring a cold tape drive or tape cartridge into a warm room, allow time for it to warm to room temperature before using it. For example, if you have moved the drive from a cold car to a warm room, allow time for the drive to reach room temperature (up to 24 hours if the temperature change is extreme).

Conditions in use

Only use LTO Ultrium cartridges in temperatures within the tape drive’s operating range from 10°C to 40°C (50°F to 104°F) and 20 to 80% relative humidity (non-condensing). If you expose cartridges to temperatures outside the operating limits, stabilize them before you use them. To do this, leave the cartridges in the operating environment for 24 hours.

Conditions in storage

LTO Ultrium cartridges will preserve the integrity of stored data for up to 30 years if proper storage conditions are observed.

For short-term storage, keep cartridges at temperatures between 16°C and 32°C (61°F and

90°F) with a relative humidity between 20% and 80%.

For long-term archival storage, keep cartridges between 5°C and 23˚°C (41°F and 73°F) with a relative humidity between 20% and 60%. Wet bulb temperature should not exceed 26°C

(78°F).

Always keep the cartridges in a clean environment.

Always store cartridges in their plastic cases on their side when not in use.

Maximizing tape life

Do not touch the tape surface.

Do not attempt to clean the tape path or tape guides inside the cartridge.

Do not leave cartridges in excessively dry or humid conditions.

Do not leave cartridges in direct sunlight or in places where magnetic fields are present (for example, under telephones, next to monitors or near transformers).

32 Cartridges

Do not drop cartridges or handle them roughly.

Stick labels onto the label area only.

LTO Cartridge Memory

Linear Tape Open—Cartridge Memory (LTO-CM) is an EEPROM that is embedded in every LTO

Ultrium tape cartridge. It is non-volatile and is contactless in that it is read by inductive coupling rather than electrical contact.

The Cartridge Memory is used to store the tape directory and diagnostic and log information.

Because of the speed at which it can be read, load and unload times are reduced, information is found on the tape more quickly and fewer tape passes are needed, increasing tape reliability.

The memory is primarily designed to speed up internal operations in the drive, but it also contains free space that can be used by application software. This may be used to store “common” information (shared by all software vendors) and “vendor-unique” information (specific to the application).

Hosts can use this free space using the SCSI Write Attribute and Read Attribute commands. For information on these commands, see Chapter 4 of the Host Interface Guide, Volume 3 of this

HP LTO Ultrium Technical Reference Manual.

To support CM fully, software vendors should ensure that their company names are registered with

ANSI T10 or the National Committee for Information Technology Standards (NCITS) as they are now known. The list of Vendor IDs is displayed at http://www.t10.org/lists/vid-alph.htm

, which also contains details of how to get a new name assigned.

Cartridge Memory adheres to the Media Auxiliary Memory (MAM) standard. “MAM” indicates that the access method applies to all types of media, not just LTO Ultrium.

The MAM standard provides for the storage and access of information held as a set of pre-defined and user-definable attributes that are divided into six main sections:

Media Common Section—hard-coded by the media manufacturer. For example: manufacturer’s name, cartridge serial number, length, media type

Drive Common Section—updated by the drive every time it accesses the media. For example: maximum and remaining tape capacity, TapeAlert flags

Host Common Section—updated by the host’s software application every time it uses the media. For example: software application vendor’s name and version, media text label, date last written

Media Vendor Unique Section—optional information written by the media vendor for their own purposes. Unique to the media vendor.

Media Vendor Unique Section—optional information written by the media vendor for their own purposes. Unique to the media vendor.

Host Vendor Unique Section—space reserved for use by software applications for their own purposes. Unique to the software vendor. Approximately 1 kilobyte.

For details of use of LTO-CM in library applications, see

“Using Cartridge Memory (LTO-CM) in libraries” (page 61)

.

LTO Cartridge Memory issues

The LTO Cartridge Memory stores identification and usage information such as the number of times the cartridge has been loaded, location of the EOD (End of Data) marker, and error logs. In the unlikely event of the Cartridge Memory becoming damaged, you may experience difficulty with the cartridge.

LTO Cartridge Memory 33

Use the following table to resolve LTO Cartridge Memory problems:

Problem Cause Solution

A new data cartridge that is write-enabled is rejected by the drive.

LTO Cartridge Memory has failed or is damaged.

Replace the data cartridge.

A new data cartridge that is write-protected is rejected in several known good drives.

LTO Cartridge Memory has failed and the drive has found no data to recover.

Replace the data cartridge.

A cartridge that has data written to it and is write-enabled is rejected by the drive.

LTO Cartridge Memory has failed or is damaged.

The data can still be recovered.

Contact the tape library supplier for more information. After data recovery, replace the cartridge.

A cartridge that has data written to it and is write-protected restores very slowly.

LTO Cartridge Memory has failed and the drive cannot use the tape directory information to recover the data.

The data can still be recovered but may take longer than normal.

More information

The latest version of the specification is incorporated into SCSI SPC-3.

The access specification can be found at http://www.t10.org/ .

34 Cartridges

6 Planning your system configuration

Modes of usage

HP LTO Ultrium tape drives and arrays can be used in different system configurations. They can be used in a standalone (direct attach) or network environments (both Local Area Network and

Storage Area Network).

Network users may need to take additional steps to ensure that their system is configured for optimum performance.

Optimizing performance

Various factors can affect tape drive performance, particularly in a network environment or if the drive is not on a dedicated bus. If your tape drive is not performing as well as expected, consider the following points before contacting HP Support at www.hp.com/support .

Dedicated bus

For optimum performance, we recommend that the tape drive is the only device on the bus.

System performance

Drives can write data at 160 MB/s (native) or 400 MB/s (2.5:1 compression). However, to get this performance it is essential that your whole system can deliver this performance.

Typical areas where bottlenecks can occur are:

Disk system (a single hard disk drive will not be able to deliver 400 MB/s transfer rates).

Some file systems are able to transfer data faster than others.

The type of data being backed up can affect backup performance (for example, file sizes and compressibility).

Some backup software performs better than others.

To improve performance you may like to consider a RAIDed disk solution with a large number of physical hard disks.

Some enterprise class backup applications can be made to interleave data from multiple sources, such as clients or disks, to keep the tape drive working at optimum performance.

Data rate matching

Data Rate Matching (DRM) enables the drive to “stream” data at variable tape speed, which means that it maintains a continuous data flow to tape even when the transfer speed from the host varies.

This is automatically managed by the drive to keep the drive running at best performance. When using LTO Ultrium 6 cartridges, the drive is able to keep streaming between 54 and 160 MB/s

(native), so, if possible data transfer should remain within this range. In most cases, the backup application will provide details of the average time taken at the end of the backup.

NOTE: For optimum performance always use Ultrium 6 6.25 TB (2.5:1 compression) cartridges.

Performance checklist

The following list summarizes factors that can affect performance. They provide guideline only of areas that may need further investigation. They do not attempt to explain how to configure individual systems. For a more detailed discussion, including information about tools that allow you to test

Modes of usage 35

performance, refer to our white papers on www.hp.com

. (Select the product first and look at the

Information Library.)

Is the tape drive reading and writing data at the correct speed?

Is the source system (hard disk) transferring data at the correct speed?

Is the backup application writing buffers at the correct speed? You may need to tune the transfer, buffer and block size settings to optimize the speed that the application writes data to the tape drive. HP LTO-6 Ultrium drives have an internal buffer of 512 MB.

Is the operating system tuned for performance? You may need to adjust the data transfer packet size.

If you are using an SAS drive or array in a SAN environment, are you are using one of the recommended fibre channel/SAS routers?

Are user applications, such as Exchange or database servers, optimized for backup performance?

Are there other factors that could be affecting performance, such as interference or fibre channel infrastructure?

36 Planning your system configuration

7 Installing and replacing drives

If you are installing the tape drive on a UNIX system, refer to the UNIX Configuration Guide,

Volume 5 of the HP LTO Ultrium Technical Reference Manual.

Installing in a server

Full details of how to install an internal LTO Ultrium tape drive into a server drive bay is given in the Getting Started Guide.

Identifying the model

The model name is on the front panel and the product and serial numbers are on a label on the top of the drive.

Standards and safety

Use the drive only in equipment where the suitability of the combination has been determined by an appropriate certification organization (such as Underwriters Laboratories Inc. or the Canadian

Standards Association in North America, and the British Standards Institution or Verband Deutscher

Elektrotechniker in Europe). Other considerations include the following:

1.

A drive must be installed in an enclosure to limit an operator’s access to live parts, to provide system stability, and to give the drive the necessary grounding integrity.

2.

A drive must only be supplied by a Safety-Extra-Low-Voltage (secondary) circuit in accordance with DIN VDE 0805. During incorporation of the equipment, all requirements of DIN VDE

0805 must be observed and obeyed.

NOTE: The drives are only fused to protect them from excessive currents.

Installing in a server 37

Requirements

Mounting requirements

Half-height drives require one industry standard 5¼-inch, half-height bay.

Full-height drives require one industry standard 5¼-inch, full-height bay.

HP recommends 0.3 mm mounting clearance around all covers to allow the Flexible Mounting

Points (FMP) to operate correctly.

For many servers, no mounting tray or rails are required. Devices simply slide into the computer’s chassis and are fixed with screws. Other servers have built-in trays or rails. Yet others require a special mounting tray or rails to fix the drive into the empty bay.

Refer to your server documentation for details on how to install drives.

Server connections

You need a properly installed and configured SAS host bus adapter (HBA) or a built-in SAS controller on the server.

The SAS drives have a 6 GB SAS interface, and are designed to work with most SAS devices. The

6 GB SAS interface supports a maximum bus speed of 600 MB/s, as opposed to the 150 MB/s of the 1.5 GB SAS interface. Therefore, installing the drive onto a 1.5 GB bus is not recommended as this may restrict performance.

For optimum performance, use a dedicated host bus adapter for the tape drive.

Do not connect to a RAID controller channel; these are for disk drives only. Consult your supplier for details.

For a SAS internal drive, you will need:

6 GB SAS host bus adapter or the server’s embedded HBA

SAS-compliant cable

Mounting hardware, if required

Backup software that supports the tape drive

Supported bus types

SAS buses

SAS Bus Type

1.5 Gbps

3.0 Gbps

6.0 Gbps

Transfer Speed

Up to 150 MB/s

Up to 300 MB/s

Up to 600 MB/s

Supported

Yes

Yes

Yes. This is the recommended configuration.

38 Installing and replacing drives

Connecting the drive

SAS connector

For the location of the rear panel SAS connector, see

Figure 4 (page 22)

The SAS drive is equipped with a 6 Gbps SAS plug connector as defined in SFF8482 [5.2.3.2].

A SAS drive is hot pluggable but the connector location is not as defined in SFF8482.

NOTE: HP LTO-6 SAS tape drives do not have a normal power connector and must be powered via the SAS connector.

The rear connections of an SAS drive are as follows:

Combined automation and remote LED connector port (for libraries)

Standard internal SAS plug connector

• iADT (Ethernet) connector

Fan connector

Diagnostic Serial Port, see

“Diagnostic Serial Port connector” (page 30)

(contact HP for further details on this diagnostic port and its function)

Backup software

You need backup software that supports the HP LTO Ultrium drive within your system’s configuration.

In a direct attach configuration, where the tape drive is attached to a standalone server, you can use backup software that is designed for a single server environment. In network and SAN configurations, you will need backup software that supports enterprise environments. As a general rule, native backup applications (such as NTBackup and tar) do not provide the required data streaming rate to get the full performance of your drive. For the latest list of backup packages that support HP LTO Ultrium drives, please consult our World Wide Web site ( www.hp.com/go/ connect ).

Applications usually recognize tape drives by their manufacturers’ ID string rather than their model number, so check the table below for the appropriate reference.

Drive Model

LTO Ultrium 2 drive

LTO Ultrium 3 drive

LTO Ultrium 4 drive

LTO Ultrium 5 drive

LTO Ultrium 6 drive

ID String

HP Ultrium 2-SCSI

HP Ultrium 3-SCSI

HP Ultrium 4-SCSI

HP Ultrium 5-SCSI

HP Ultrium 6-SCSI

Installing in a server 39

Installing in a tape array

Appropriate HP rack-mount systems

HP LTO Ultrium removable tape drives can be used with any compatible rack-mount tape array system.

The tape array is designed to be installed into any compatible 19” rack-mount systems. It must be properly installed and configured. Refer to your tape array documentation for further details.

Airflow requirements

As long as the tape array is fully populated, it will provide adequate airflow for HP LTO Ultrium drives.

If you have unused bays in the tape array, you must install the blanking plates provided with the tape array. This ensures that there is adequate airflow to the drives. See the documentation with the tape array for details on installing blanking plates.

You should ensure that ventilation is adequate at the front and rear of the tape array.

HP LTO Ultrium drives require forced airflow. The required airflow depends on the ambient air temperature and should be from back to front:

6 cfm for ambient air temperatures fluctuating in the range 10°C–35°C.

8 cfm for ambient air temperatures fluctuating in the range 10°C–40°C.

For details of how to test if the airflow is adequate, see

“Airflow requirements” (page 10)

.

Identifying the drive

The model name is on the front panel and the product and serial numbers are on a label attached to the drive.

Modes of usage

Tape arrays can be used in different system configurations; direct attach, network attach and attached to a Storage Area Network (SAN). For details of these see

“Modes of usage” (page 35)

.

Attaching to SAS

HP LTO Ultrium SAS drives are high performance 6 GB SAS devices. When installed in a tape array in a compatible rack mount system they can be connected to a SAS connection on a server or to an expander as part of a larger SAS network. To get the optimum performance from your tape drive you need a SAS topology that can transfer data at a rate that supports the tape drive’s maximum transfer speed.

Connecting to a Fibre Channel router or by SAS to a server or router

Individual SAS tape drives are connected to their hosts via the SAS connectors on the back of the tape array. They do not require any SAS cables to plug into the tape array. However, you do need cables to connect the tape array with the SAS host or expander.

Fibre Channel connection

If you are using your tape drive on a fibre channel (FC) network, you will need a FC/SAS router.

If you are attaching your tape drive to a SAN environment supplied by HP, refer to your SAN solution collateral or configuration guides for further details.

Server SAS connection

If you are attaching the drive to a server, you need a properly installed and configured SAS host bus adapter (HBA) or a built-in SAS controller on your server with a spare SAS port. For optimum

40 Installing and replacing drives

performance, your tape drive should only be connected to a 6 GB SAS host bus adapter or SAS controller, but the drive will also function with a 3 or 1.5 GB SAS connection.

Replacing a drive

HP LTO Ultrium removable drives can be removed and replaced without powering down the tape array and without interrupting operations to the other drives in the array. However, note the following:

In Berkeley mode, the tape position will remain unchanged by a device close operation.

In AT&T mode, a device close operation will cause the tape to be repositioned just after the next tape filemark (the start of the next file).

If all drives in the tape array are powered up when the system is turned on, the host will be aware of those drives. You can remove any drive and replace it with another without disrupting the system.

If a drive is not powered up or you place a drive in an empty slot after the system has been powered up, the system will have to be reset before the host will recognize the drive.

Removable drives allow modules to be replaced while powered up as long as no data is being transmitted from the system to the module or vice versa.

Installing in a library

Rear panel and connectors

CAUTION: LTO Ultrium tape drives are not installable or replaceable by end-users, so the attachment or removal of FC, SAS, power and other cables between the tape drive and the tape library should only be carried out be service-trained personnel authorized by the tape library supplier. The connectors are not field upgradeable.

The rear panel contains the connectors that allows the tape drive to communicate with the tape library and host computer system. The panel includes the following connectors:

Combined automation and remote LED connector (for automation use)

For details of the combined automation and remote LED connector, see

“Automation and remote LED connector” (page 26) . For details of the use of the ADI connector in libraries, see

“Automation interface” (page 54) .

Diagnostic serial port connector

The proprietary serial HP LTO diagnostic port. To access this port via RS232 requires an HP

LTO Diagnostic Interface Card. Diagnostic information from the drive can be accessed by connecting to the serial communications port on a computer. Contact HP for further details on this diagnostic port and its function.

On Fibre Channel drives only:

Power connector (FC drives only)

Full-height drives use a standard 4-pin power connector to supply the 5V and 12V power the tape drive. Half-height drives use a Molex microfit 4-pin power connector to supply the 5V and 12V power to the tape drive.

Fibre Channel connectors

Two Small Form-factor Pluggable (SFP) duplex-LC fibre channel transceivers. Depending on the specific configuration, only one SFP FC transceiver may be installed.

Installing in a library 41

On SAS drives:

A standard internal SAS connector.

SAS drives do not have a normal power connector and should be powered via the SAS connector.

Installing standalone drives

If you are installing the tape drive on a UNIX system, refer to the UNIX, Linux, and OpenVMS

Configuration Guide, Volume 5 of the HP LTO Ultrium Technical Reference Manual.

Identifying the drive

The model name is on the front panel and the product and serial numbers are on a label on the bottom of the drive.

Connecting the drive

SAS connection

The rear panel connections of external SAS standalone drives consist of a mains power connector and a Mini-SAS connector. The drive should be connected to the host server/expander with a good quality external SAS cable that is as short as possible. If you are attaching a SAS drive to a server, you need a properly installed and configured SAS host bus adapter (HBA) or a built-in

SAS controller on your server with a spare SAS port. For optimum performance your tape drive should only be connected to a 6 Gbps SAS host bus adapter or SAS controller, but the drive will also work with a 1.5 or 3 Gbps SAS bus.

Moving drives

If there is a tape in the drive, unload it before powering down and moving the drive. When the drive is powered down, there is no physical lock on the tape reels. If you leave a tape threaded in the drive with the power off, the reels could rotate, causing a loop of tape to occur in the tape path. When the drive is next powered up, the tape could then fall off the guides and be damaged.

If for any reason you must move a drive with a tape threaded, move it slowly and carefully, making no sudden movements that could cause the reels to rotate.

42 Installing and replacing drives

8 Operating the drive

Power-on self-test

When powered-on, the tape drive will run its hardware self-test:

In a server, internal drives are powered on when you switch on your computer.

In a tape array, removable drives are powered on when you switch on your tape array and computer.

In a tape library, installed drives are controlled through the tape library operator panel. Refer to the tape library documentation for details. See also

“Resetting drives in a library” (page 46)

.

For standalone drives, switch on external drives using the power switch on the front panel, and then switch on the host computer.

During the test the ‘Ready’ LED flashes and all the other LEDs are off. On successful completion the

‘Ready’ LED is on. If the self-test fails, the ‘Drive Error’ and ‘Tape Error’ LEDs flash, while the ‘Ready’ and ‘Clean’ LEDs are off. This continues until the drive is reset.

If you have just installed the drive, check the installation for loose connections, reset the drive and repeat the self-test.

Try

“Troubleshooting” (page 47)

to determine what the problem is.

If the fault condition persists, call for assistance.

Power-on self-test 43

Loading a cartridge

NOTE: This section describes loading a cartridge in a standalone drive. The procedure is the same for internal drives and those in tape arrays and libraries.

Full-height drives: Half-height drives:

1. Arrow indicating leading direction

2. Cartridge label area

1. Arrow indicating leading direction

2. Drive door

3. Cartridge label area

NOTE: Use HP LTO Ultrium cartridges.

1.

Insert the cartridge into the slot in front of the drive with the arrow uppermost and facing the drive door.

2.

Apply gentle pressure on the rear of the cartridge until the drive takes the cartridge and loads it.

The Ready LED flashes green while the drive performs its load sequence. When the cartridge is loaded, the Ready LED shows steady green.

Do not try to force the cartridge if it does not load properly. The drive will eject the cartridge after about 10 seconds so you can load it again.

44 Operating the drive

Unloading a cartridge

NOTE: This section describes unloading a cartridge from a standalone drive. The procedure is the same for internal drives and those in tape arrays and libraries.

Full-height drives: Half-height drives:

1. Eject button 1. Eject button

1.

Press the Eject button on the front panel.

nl

During the unload sequence the READY LED flashes green. The drive completes any task it is currently performing, winds the tape to the beginning and ejects the cartridge. Once the tape has rewound, the eject cycle will take less than 13 seconds.

2.

Remove the cartridge and store it in its plastic case in a cool, dry atmosphere.

Cleaning

When the drive needs cleaning:

The orange ‘Clean’ LED on the front of the tape drive will flash. Only insert a cleaning cartridge into the tape drive when the LED flashes.

The drive’s TapeAlert feature will send a message to your backup application.

In a library or tape array, the drive also tells the automation controller that a cleaning tape needs to be used via the ADI connector.

See the

“Automation interface” (page 54)

for details.

CAUTION: It is essential to use only LTO Ultrium Universal cleaning cartridges C7978A (Orange) with HP LTO Ultrium tape drives as other format cleaning cartridges will not load and run. Use of

HP cleaning media will ensure your tape drive is fully protected. Do not use swabs or other means of cleaning the heads.

LTO Ultrium Universal cleaning cartridges can be used up to 50 times.

To clean the heads:

1.

Insert a cleaning cartridge into the drive. The tape drive automatically loads the cartridge and cleans the heads.

If the cleaning cartridge ejects or returns to the ready-to-eject position immediately with the

Tape Error LED on, it has expired or it is not an LTO Ultrium cleaning cartridge (or is an older unsupported LTO Ultrium cleaning cartridge). In this case, discard the cleaning cartridge and repeat the operation with a new one.

The cleaning cycle can take up to 5 minutes, during which the orange ‘Clean’ LED will be on steadily and the green ‘Ready’ LED will flash. When it has finished, the drive ejects the cartridge or returns the cartridge to the ready-to-eject position.

Unloading a cartridge 45

2.

Remove the cleaning cartridge from the drive.

Resetting drives in a library

The tape drive can be reset by the automation controller via the automation connector or by pulling the ACI_RST_L line low (see

“Automation interface” (page 54)

).

There are two levels of reset via the automation connector:

ACI reset—resets the ACI port and all SAS/Fibre Channel ports

Drive reset—equivalent to a power-on reset

Either reset method will interrupt the interface between the drive and host, and a reset may result in no End of Data mark being written. As a result, it is strongly recommended that a reset command is not sent unless all other recovery methods have failed. Note that certain automation commands

(Load, Unload, Set Drive Configuration, Reset and Set Baud Rate) can be queued behind outstanding

SCSI commands giving the impression that the drive has stopped responding over the ADI connector.

(All command packages will be still be ack’ed even though the command will be queued.)

Following a Reset command with reset control set to Drive Reset or after pulling the ACI_RST_L line low, the drive will behave as if it has powered up and will go off bus and lose all automation connector configurations.

An FCP reset will not affect the automation interface.

Note that following an upgrade of the drive firmware the drive will be reset as if it had been powered up.

46 Operating the drive

9 Troubleshooting

Emergency unload (forced eject)

If a cartridge fails to eject using the normal unload procedure, press and hold the Eject button for

5 seconds. This instructs the drive mechanics to perform an emergency unload. Wait for the cartridge to be ejected. This may take up to 15 minutes (the maximum rewind time).

If the cartridge is still jammed, for full-height drives press the emergency reset button (see

“Front panel features” (page 12)

or

“Front panel for automation use” (page 52) ), or pull pin 8 of the

Automation and Remote LED Connector low (see

“Automation and remote LED connector”

(page 26)

). For half-height drives perform an emergency reset by pressing and holding the Eject button for at least 35 seconds, and the drive will reset once the button is released. Wait for the drive to reset and recover the tape to the loaded position. This may take up to 15 minutes. Again press and hold the Eject button for 5 seconds to perform a second forced eject and emergency unload if required.

General guidelines

If you experience problems when using the tape drive, you need to isolate the cause of the problem.

For example, if you have just installed a new host bus adapter and your system will not start, the cause of the problem is likely to be the adapter.

When installing multiple items of hardware and software, we recommend that you install each in turn and restart the system each time. Similarly if you have already installed multiple devices and software and you experience problems, remove or uninstall each in turn to establish which one is causing the problem.

Remember that the system recognizes devices during boot-up. If you swap or connect a product when your system is running, you will need to reboot the system. Rebooting the system will reset devices and will often resolve problems. It is good practice to reboot every time you add a driver or install firmware.

Most modern host bus adapters locate and display attached devices when the system is booting up. On Windows systems, if you swap or connect a product when your system is running, you will need to reboot the system. IA32 systems also usually need to be rebooted. UNIX systems may have pluggable drivers, which allow drives to be attached to a running system and detected without rebooting.

If the device is not detected on boot up, there is probably a problem with the physical hardware: cables, termination, connections, power or the host bus adapter. If the device is displayed during boot up but cannot be found in the operating system, this is more likely to be a software problem.

Emergency unload (forced eject) 47

Diagnosing the problem

The first step in problem-solving is establishing whether the problem lies with the cartridge, the drive, the host computer and its connections, or with the way the system is being operated.

NOTE: If the drive is installed in a library, refer to troubleshooting information provided with the tape library, the host or the backup software if the problem seems to lie in one of these areas.

If none of the following advice helps you solve the problem, contact your tape library supplier.

Problems with the host computer

Most modern host bus adapters locate and display attached devices when the system is booting up. If the device is not detected at this stage, there is probably a problem with the physical hardware: cables, termination, connections, power or the HBA itself.

If your drive is found on system boot up but cannot be found in the operating system, this is more likely to be a software problem.

Computer does not boot up

Possible Cause Potential Solution

You have installed an additional host bus adapter and its resources are clashing with an existing adapter.

Remove the new host bus adapter and check the server documentation.

You have disconnected the power or cable from the computer’s boot disk during the drive installation process.

Check that the cables to all devices are firmly connected.

Computer boots, but does not recognize the drive

Possible Cause

The power or interface cable is not connected properly.

Potential Solution

Check that the cables to the tape drive are firmly connected. Ensure that the cable is compliant and that it is not damaged. Replace, if necessary.

Problems with the drive and cartridge

Tape drive does not power up

Possible Cause

The power cable is not connected properly.

Potential Solution

1.

Check that the cables to the tape drive are firmly connected.

2.

Make sure that the power cable is firmly connected.

3.

Try another power connector.

Note: For standalone drives, the power on/off switch incorporates a green LED. If this is not on, check the power cable connection and replace the cable if necessary. You can use the power cable from your monitor or another device to check that the connection is working.

4.

If the power supply is present and all LEDs remain off, call support

The self-test fails (Ready LED is off and the other LEDs are on steadily).

If there is a cartridge in the drive, remove it. Power down the drive and power it up again. If the self-test still fails, call support.

48 Troubleshooting

The application does not recognize the drive

Possible Cause

Some applications require drivers to be loaded.

Potential Solution

The application does not support the tape drive.

Check the drive is installed properly. Refer to our World Wide Web site

( www.hp.com/go/connect ) for details of backup applications that support

HP LTO Ultrium tape drives. Load any service packs as necessary.

Check the correct drivers are installed. Consult the backup application’s installation notes for details.

The cartridge will not eject

Possible Cause Potential Solution

The cartridge is jammed in the drive, or the backup application cannot eject the cartridge. This is most likely to be a communication problem between the drive and the system.

1.

Check there is power to the drive.

2.

The Prevent Media Removal function may be enabled. This is on a per-host basis, but all hosts must allow media removal for any of them to do so. Check each host for the status of the PMR function.

3.

Press and hold the Eject button for 10 seconds. Allow the drive up to

15 minutes to eject (this is the maximum rewind time of the cartridge.)

4.

If the cartridge is still jammed, for full height drives press the emergency reset button (see

“Reset switch” (page 12)

) or for half height drives perform an emergency reset by pressing and holding the Eject button for 20 seconds, and the drive will reset. Wait for the drive to reset and get back to the loaded position. This may take up to 15 minutes. Again press and hold the Eject button to perform a second forced eject and emergency unload if required.

5.

If the cartridge is still jammed, call for support

The drive will not accept a cartridge

Possible Cause Potential Solution

The cartridge is not compatible with your tape drive.

1.

Check you are using LTO Ultrium 4, 5 or 6 media. LTO Ultrium 6 drives do not accept LTO Ultrium 1, 2 or 3, or other non-LTO Ultrium media.

2.

Check the orientation of the cartridge when loading into the drive.

The cartridge has been damaged.

The tape drive is faulty.

1.

Check the cartridge case is not cracked or split.

2.

Check the leader pin is not damaged. If it is, discard the cartridge.

3.

Check the cartridge teeth are not damaged. If they are, discard the cartridge.

4.

If the drive will still not accept the cartridge, try using a new or known good cartridge. If it loads, the original cartridge is faulty and should be discarded.

5.

If the original cartridge is accepted in another tape drive, the original tape drive may be at fault. Check the interface connection and that the tape drive is recognized by the backup application.

1.

Check the drive is powered on.

2.

If the drive still will not accept the cartridge, there may be a problem with the drive’s cartridge memory. Call for support.

Diagnosing the problem 49

The computer no longer recognizes the drive in a tape array

Possible Cause

You powered up the drive or added it to the tape array after the host system was turned on.

Potential Solution

Most modern host bus adapters/host systems will only locate and display attached devices when the system is booting up. Try rebooting your host system after the tape array is powered up.

The drive is not inserted correctly.

Check the drive is properly inserted into the tape array so that it mates with the connections at the rear of the enclosure. The extraction lever should be pushed in, locking the drive in position.

There is a fault with the host system.

1.

Make sure that the system is configured to recognize the device.

2.

Ensure that the correct driver for the tape drive is installed. Look at the host adapter documentation and backup software documentation for further advice.

Problems with cleaning

Use the following table to resolve cleaning problems:

Problem

Recurring cleaning message.

Solution

Clean the drive with an LTO Universal Cleaning Cartridge as instructed in the tape library documentation. If the message reappears, replace the cleaning cartridge with a new one.

If the message reappears when a particular data cartridge is used, verify that the data cartridge is readable by clearing the message and reading the tape again.

If the data cartridge can be read, back up the data to another cartridge and then discard the damaged one.

The cleaning cartridge is ejected immediately after loading.

Make sure that you are using an approved LTO Ultrium Universal cleaning cartridge and that the cleaning cartridge is not expired.

If the drive is installed in a library:

Problem

A brand new data cartridge is used, and the library operator panel indicates that cleaning is required.

Solution

Clean the outside of the data cartridge with a barely damp, clean, lint-free cloth.

Clean the drive as instructed by your tape library documentation.

If the operator panel indicates cleaning is required within a short period of time, replace the data cartridge.

50 Troubleshooting

10 Special features for automation

Introduction

This chapter contains information that relates to placing an HP LTO Ultrium drive in an automated device, such as an autochanger or a tape library:

Drives for use in libraries have different front panels from drives mounted individually in servers and standalone drives. There is also a special front panel for use in autoloaders. These are described in

“Front panel for automation use” (page 52)

.

For notes on the requirements and other details for the installation of drives into libraries, see

“Installing in a library” (page 41)

.

For notes on the operation of drives in libraries, see

“Resetting drives in a library” (page 46) .

For troubleshooting information, see

“Troubleshooting” (page 47)

.

This chapter contains information about using special features of LTO Ultrium drives in libraries:

The “Automation interface” (ACI/ADI), or the iADT (Ethernet) interface, allows the activities of the drive to be coordinated within a library. See

“Automation interface” (page 54)

for details.

“Configuring autoload and library-controlled loads” (page 58)

allows you to configure whether automatic or ACI/ADI-controlled loads and unloads occur.

LTO Cartridge Memory (LTO-CM) or Cartridge Memory is EEPROM memory that is embedded in every LTO Ultrium tape cartridge. It is non-volatile and is contactless in that it is read by RF coupling rather than electrical contact.

For suggestions of how to make use of cartridge memory in libraries, see

“Using Cartridge

Memory (LTO-CM) in libraries” (page 61)

.

Drives for inclusion in automated devices have different front panels from individual drives.

Backup software

You need backup application software that supports your LTO Ultrium drive and tape library.

Suitable backup applications will include driver software that establishes the interface between the tape drive and the software. Applications usually recognize tape drives by their manufacturers’

ID string rather than their model numbers, so check the following table for the appropriate reference.

Drive Model ID String

LTO-6 FC drive

LTO-6 SAS drive

“HP Ultrium 6-SCSI”

“HP Ultrium 6-SCSI”

Introduction 51

Front panel for automation use

Full-height drives

1. Eject button

3. Holes for optical sensors

2. Access hole for emergency reset switch

4. LEDs

The automation front panel has the following features:

There is an eject button for manually ejecting a cartridge. Press this for approximately ten seconds to start a “forced eject” for recovering a cartridge manually. See

“Emergency unload

(forced eject)” (page 47)

for details.

Indicator LEDs provide a visible indicator of the state of health of the drive. See

“LED patterns”

(page 14)

for details.

There is no door. Instead there are two fixed guides to guide the cartridge into the drive.

The indent for a label on the left just under the cartridge opening is left blank, exposing two holes. These can be used to provide a target for the optical position sensor of a library picker.

There are additional holes around the cartridge opening to allow a throat to be fitted if necessary, to help the smooth loading of cartridges.

52 Special features for automation

Front panel for use in autoloaders

A special front panel is available for autoloader applications. The front panel fits within the drive form factor in height and width:

1. Access to Eject button

3. LEDs

2. Access hole for emergency reset switch

4. Access to datum surfaces on the front of the drive

The autoloader front panel has the following features:

Simple one-piece plastic design

Pinhole access to the eject switch on the drive for manually ejecting a cartridge. Press this for approximately ten seconds to start a “forced eject” for recovering a cartridge manually. See

“Emergency unload (forced eject)” (page 47)

for details.

Indicator LEDs provide a visible indicator of the state of health of the drive. See

“LED patterns”

(page 14)

for details. The LEDs are viewed through holes in the autoloader front panel; no light pipes are present.

Clearance for picker finger access to the right-side cartridge-handling notch

Two square holes through the panel to provide access to a datum surface on the front of the drive

Cartridge lead-in features to improve cartridge load and unload operations

Front panel for automation use 53

Half-height drives

The half-height automation panel has very similar features to the full-height version. The exterior dimensions of the panel are smaller than those of the equivalent panels for drives designed for installing on servers and panels for standalone drives, in order to allow the whole drive to be fitted into the half-height form factor with no overlap.

Figure 12 Automation bezel for half-height drives

The bezel is 4.1 mm thick.

Automation interface

The HP LTO-6 tape drive supports connection to an automation device via the serial ADI port or via an Ethernet port. The ADI port supports the HP proprietary ACI protocol for connection to legacy libraries and the sADT protocol. The Ethernet port supports the Internet ADT (iADT) and iADT

Discovery (iADT_DISC) protocols defined in the ADT-2 draft standard.

NOTE: The sADT protocol is covered by two standards:

For ADT-2, see the T10 ADT-2 Standard and the relevant ANSI standard when it is released.

For ADC-3, see the T10 ADC-3 Standard and the relevant ANSI standard when it is released.

As the Ethernet port can be connected to devices outside the library, the drive provides support for security in the form of optional authenticated connections. Authentication makes use of X.509

certificates which are installed in the drive via SCSI commands defined in the proprietary Security

Configuration Protocol.

The serial automation controller connection supports a HP proprietary Automation Controller

Interface (ACI) protocol and the Automation/Drive Interface (ADI) transport protocol (ADT). Because of the differences in these two protocols it is not possible to interleave ACI and ADI frames/commands. It is therefore necessary for the serial automation controller connection to operate in either ACI or ADI Mode. The tape drive defaults to ACI Mode after a power-on or hard reset if the Sensea/ACI_LIN_SEN_L input is activated on the ADI/ACI connector. Otherwise the drive defaults to ADI Mode. See

“Automation interface” (page 54) .

Connections between the library and the drive may use either or both of the physical connections:

• sADT only

• iADT only

• iADT and sADT

The drive also supports ADI bridging as defined in the INCITS T10 ADC-3 standard over both sADT and iADT.

54 Special features for automation

Table 2 Automation ports and ADT ports available on LTO-6 drives

Port

ACI

ADI

DTI iADI iAMI

Automation Control Interface or

Autochanger Interface

Automation/Drive Interface

Diagnostic Tools Interface

Protocol

HP Proprietary

T10 standard sADT

T10 standard sADT

T10 standard iADT-TLS

TCP/IP Port

# Comments

N/A The ACI protocol was developed before the emergence of the T10 standard ADT protocol and is no longer being actively developed.

N/A

N/A

4169

Primary automation interface over

RS-422 serial link.

The same physical port as the diagnostic serial test port, but using the ADT protocol instead of the HP

Proprietary diagnostic protocol.

Ethernet equivalent of the ADI port.

Internet Automation/Drive

Interface

Internet Automation

Management Interface iDTI-A iDTI-B

Internet Diagnostic Tools

Interface

Internet Diagnostic Tools

Interface iDTI-C Internet Diagnostic Tools

Interface iADI-TLS Internet Automation/Drive

Interface using Transport Layer

Security iAMI-TLS Internet Automation

Management Interface using

Transport Layer Security

T10 standard iADT-TLS

T10 standard iADT-TLS

T10 standard iADT-TLS

T10 standard iADT-TLS

T10 standard iADT-TLS

T10 standard iADT-TLS

4168

4167

53670

53671

9614

8614

Auxiliary automation port used for

Key Management and Host Access

Control.

Ethernet equivalent of the DTI port.

Ethernet equivalent of the DTI port.

Ethernet equivalent of the DTI port.

Secure Ethernet equivalent of the iADI port.

Secure Ethernet equivalent of the iAMI port.

Automation Control Interface (ACI)

The Automation Control Interface (ACI) allows the activities of the drive to be coordinated within a library. The protocol has been designed so that it can be made into a standard feature of tape drives. It provides a rich and extensible functionality to allow automation manufactures to add value in their application of it.

The interface is a serial bus with additional control lines, designed to connect the LTO Ultrium tape drive to an automation controller in a tape library. Each tape drive position has a separate automation controller. The RS-422 serial port on the rear of the drive allows for ACI connection.

The ACI protocol provides the following fundamental functions:

Coordinating the automation controller and the tape drive for Load and Unload operations

Allowing the automation controller to retrieve information from the tape drive

Setting tape drive configuration information

In addition, the following functions may be supported depending on the way that the tape library is configured:

Providing upload and download of firmware images

Providing access to the contents of the Cartridge Memory

Automation interface 55

Providing a protocol for passing SCSI commands to the tape drive

Providing a protocol for passing SCSI commands from the host to the library (surrogate SCSI).

NOTE: These notes refer to the “standard” automation drive variant.

For details of using ACI commands and the ACI protocol, see Chapter 5 of the Software Integration

Guide, volume 2 of the HP LTO Ultrium Technical Reference Manual.

Automation/Drive Interface (ADI)

The INCITS T10 (SCSI) committee has a working group devoted to the development of a common

Automation-Drive Interface (ADI). ADI consists of two standards:

Automation/Drive Interface—Commands (ADC-3), ANSI INCITS TBD, which specifies the SCSI command set used over ADI.

Automation/Drive Interface—Transport Protocol (ADT-2), ANSI INCITS TBD, which specifies a transport protocol for ADI.

The drive operates in either ACI or ADI mode. It is not possible to interleave ACI and ADI commands because they are handled very differently. The drive defaults to ACI mode after a power-on or hard reset. The Automation Controller can then instruct the tape drive to switch to ADI mode by sending a Port Login frame under the following conditions:

1.

No ACI commands are outstanding. This not only means that the tape drive must have received acknowledgement for all responses to all ACI commands received, but also that all immediate response commands have also finished. For example, if an Automation Controller initiates an immediate response Load command (see section 5.3 of ACI specification), it cannot issue an

ADI command until the tape drive has finished physically loading the cartridge. If an ACI command is outstanding when an ADI frame is received the drive will transmit an ACI <NAK> character in response.

2.

An Encoded ADI frame received when the tape drive is in ACI Mode must not exceed the

Receive Buffer size (see section 5.16 of the ACI Specification for details) and the frame must be received within the ACI Transmission Period (see section 4.6.6.3.2 of the ACI Specification).

If either of these conditions is exceeded the tape drive will transmit a <NAK> character.

3.

ADI frames received in ACI Mode must be Port Login frames otherwise the tape drive will revert to ACI Mode after transmitting the appropriate ADI response.

4.

The ADI protocol must be enabled; see the Set Drive Configuration command (section 5.6 of the ACI Specification) for details. If the tape drive receives an ADI frame when the ADI protocol has been disabled the drive will transmit a <NAK> character.

When the tape drive is in ADI Mode it will not acknowledge or respond to any ACI command until the ADI port becomes logged out, either with an explicit Port Logout frame or an ADI reset.

When the tape drive transitions from one mode to the other (ACI to ADI or ADI to ACI) it will not implicitly change the drive’s configuration. However, Automation/Drive Interface (ADC-3) SCSI mode parameters only apply when the tape drive is in ADI mode, so the tape drive behavior may change after transitioning between the two modes.

HP recommends that the drive is used in either exclusively ACI or ADI modes of operation. Avoid mixing operation of the two modes.

Internet Automation Device interface (iADT)

The iADT or Ethernet port provides all the same functionality as the ACI/ADI port but can also be used for:

• drive management

• encryption control/key management

• diagnostic extraction

56 Special features for automation

The iADT port supports the following network services via the 10/100 Mbpa Ethernet port:

Service Name iADT iADI-TLS iADT-DISC iDTI

Port Number/Base Protocol

4169/TCP

9614/TCP

4169/TCP

4167/TCP

Description

Internet Automation Device Interface using non-secure ADT protocol over TCP (see ADT-2).

Internet Automation Device Interface using secure ADT protocol over TCP (see ADT-2).

iADT Discovery over UDP (see ADT-2).

Internet Diagnostic Tools Interface using non-secure ADT protocol over TCP.

How the LTO-6 drive will be configured depends upon the overall configuration of the data storage site. The site consists of a number of entities:

Host computers performing backups

Tape libraries (automation devices)

LTO-6 tape drives installed in tape libraries (drives may provide connectivity between the library and hosts)

Management hosts performing security configuration

Encryption key managers (EKMs)

Hosts accessing the drives for debugging information

It may be necessary for a drive to communicate directly with a network entity, such as an external

Key Manager, which requires network traffic to pass through a router on the edge of the library.

This requires careful configuration of the router to ensure security of the network inside the library.

The network inside a library is configured using techniques unique to that library. This section only gives guidance on the goals of that configuration. The library network configuration has two purposes:

To permit communication among the library, all drives, and any other entities.

To ensure the security of those communications.

If the network connects only the library and drives, there should be no physical connection between the network and any network outside the library. If this is not feasible, then IP packets to or from the following port numbers should be blocked:

• iADT (TCP/4169)

• iADT-TLS (TCP/9614)

• iADT-DISC (UDP/4169)

If an external host (such as an external Key Manager) requires access to the library only and the library has two Ethernet ports with a firewall between them, then one port should be used only for external access and the other for internal access. This is effectively the same as the situation in the previous paragraph.

If an external host requires access to drives, only the minimum number of protocols should be allowed to pass into and out of the library, and any connections carrying SCSI commands should be secured either by using IKEv2-SCSI and ESPSCSI on the iADI port or by using the iADI-TLS port.

Either of these will require security configuration to be performed on the drive.

Public Key Infrastructure (PKI) credentials used by the HP LTO-6 drives consist of three classes of

X.509 certificates: root certification authority (CA), device, and management host. If the drive has

Automation interface 57

not received a root CA certificate and a device certificate, then SSL/TLS connections (such as iADT-TLS) will not be accepted.

The root CA certificate is stored in non-volatile memory in the drive and is used to verify credentials presented to the drive in the course of the TLS and IKEv2-SCSI protocols. To permit this, it is used to sign the other certificates.

The device certificate stored in non-volatile memory identifies the drive and contains the public key programmed into the drive during manufacturing. The subject name field of the certificate is provided by the system administrator during certificate creation.

The management host certificates are stored in volatile memory, and are used to verify and authorize security configuration operations.

Use of PKI credentials requires the system administrator to replace compromised and expired certificates, and (when certificate validity dates are checked) ensure that the drive’s real-time clock is valid. The LTO-6 drive does not support certificate revocation lists (CRLs). In some circumstances, you can disable the checking of certificate validity dates.

Fan interface

HP Ultrium LTO-6 SAS drives have the capability to control an external fan. The purpose of this is to provide the necessary airflow through the drive to keep the internal temperatures within normal parameters. For details of the Fan Connector, see

“Fan control connector” (page 30)

. When the drive detects a fan is present it will control the fan as required. Any fan used for this purpose should be able to meet the following criteria:

12V supply

4-wire fan (Power, Ground, Speed Control and Fan Speed)

Minimum airflow requirements as detailed in the environmental specification

The enclosure used to house the fan and drive must be designed in such a way as to ensure that the airflow generated by the fan is only pulled through the drive. There should be no path outside the drive.

NOTE: If you intend to plug a fan into this connector to provide the necessary airflow through the drive, consult your HP Technical Support Representative for details of the fan specification required.

Configuring autoload and library-controlled loads

HP LTO Ultrium tape drives can be configured so that loads either occur automatically or under the control of the library. A SCSI MODE SELECT command can set the Autoload field to do this.

The field is byte 5, bits 0–2 of the Control Mode page, 0Ah.

If the Autoload field = 0, Autoload is set and the drive automatically loads a cartridge when it is inserted and threads the tape so that it is ready for use.

If the Autoload field = 1 or 2, the drive pulls the cartridge into the drive but does not thread the tape. In this position, the LTO-Cartridge Memory can be read. The drive requires a Load command to thread the tape and make it ready for use.

58 Special features for automation

Cartridge positions during load and unload

The following diagrams show the positions of importance during load and unload.

Figure 13 Load and unload positions for full-height drives

Figure 14 Load and unload positions for half-height drives

NOTE: Drives for library use the automation front panel, which has no door. The illustration shows a standalone drive.

Eject Point Cartridges are ejected to this point, which is 72.5 mm from the drive mounting points on full–height drives, and 73.6 mm from the drive mounting points for half-height drives. The

Configuring autoload and library-controlled loads 59

Load Point 1

Load Point 2 position tolerance is 1 mm. The automation controller cannot configure the location of this position.

If Autoload is set (Autoload field = 0), the drive will start to load the cartridge when it reaches this point.

If Autoload is not set (Autoload field = 1 or 2), the library must insert the cartridge into the drive to a position between Load Point 1 and Load Point 2. The library can then issue a

Load command over the ADI connector to instruct the drive to load and thread the cartridge.

Load Point 1 is the recommended minimum load point for commanded loads.

The maximum distance a cartridge can be inserted for optimal loading performance, so that autoload or a Load command can load the cartridge. The automation controller cannot configure the location of this position.

The maximum speed for inserting a cartridge into the drive is 80 mm/s.

There is one other point of note, the ready-to-eject position. If Auto-Eject is not set then when an unload command is received by the drive, the tape will be rewound and unthreaded. The drive will then wait at this point until it is commanded to eject the cartridge by the ACI Unload command.

Load scenarios

The following scenarios describe the operation during the various types of load.

Load scenario 1: Autoload

1.

The library sends a Set Configuration command to enable Autoload. This is only necessary after a drive power-on.

2.

The host sends a Move Medium command to the robotics.

3.

The picker gets a cartridge from a storage slot.

4.

The picker inserts the cartridge into the drive aperture.

5.

The picker lets go of the cartridge and pushes the cartridge to between Load Point 1 and Load

Point 2.

6.

The drive automatically takes the cartridge, loads it and threads it.

Load scenario 2: Library controlled

1.

The host sends a Move Medium command to the robotics.

2.

The picker gets a cartridge from a storage slot.

3.

The picker inserts the cartridge to between Load Point 1 and Load Point 2.

4.

The picker lets go of the cartridge.

5.

The library sends a Load command to the drive.

6.

The drive takes the cartridge, then loads and threads it.

Unload scenario 1: Autoload

1.

The library sends a Set Configuration command to enable Auto-Eject. This is only necessary after a drive power-on.

2.

The host sends an Unload command to the tape drive.

3.

The drive rewinds, unthreads and ejects the cartridge to Eject Point.

4.

The host sends a Move Medium command to the robotics.

5.

The picker takes the cartridge from the tape drive and places it in its storage slot.

Unload scenario 2: Library controlled

1.

The host sends an Unload command to the drive.

2.

The drive rewinds and unthreads the tape. It then pauses with the cartridge at ready-to-eject position.

3.

The library sends an Unload command to eject the cartridge.

60 Special features for automation

4.

The drive ejects the tape to Eject Point.

5.

The picker takes the cartridge from drive and places it in its storage slot.

Load/unload forces

The load force varies according to the speed at which the cartridge is inserted into the drive. The peak load force occurs when the cartridge begins to accelerate the drive carrier and only lasts for a short time. In any automation environment, it is recommended that the cartridge is inserted into the drive with a speed of between a minimum of 25 mm/s and a maximum of 80 mm/s, but it is recommended that a speed of 55 mm/s is used and that the cartridge is inserted to Load Point 1

+8 mm. Going outside this range, or not inserting the cartridge far enough raises the possibility that the Autoload may not trigger and increases the risk of damaging the load mechanism.

The unload force is 5.8N maximum; this is the force that an external mechanism must exert to remove a fully ejected cartridge from the drive.

Using Cartridge Memory (LTO-CM) in libraries

Cartridge memory offers possibilities for use in libraries as an adjunct to or replacement for barcodes. The following diagram shows the architecture required.

Current libraries — barcodes

Many libraries use sticky labels with barcodes on cartridges to identify them. These are read by a barcode reader attached to the picker arm. The application then needs to hold information as to the contents of the tape to which it can relate the bar code.

Cartridge Memory can be used as a substitute for these barcodes. No human interaction is needed to fix barcode labels, reducing errors, though cartridges may still need labels that humans can read. A cartridge can be identified by its serial number.

However, because Cartridge Memory has space that can be written by applications, it can hold details of the contents and nature of the tape. This obviates the need for this information to be held by the application. HP is working with other industry leaders, both hardware and software, on an

Industry Common Implementation Guide.

Using Cartridge Memory (LTO-CM) in libraries 61

11 Drive error codes

The following error codes may be reported in bytes 16 and 17 of the Request Sense data and also reported in ACI Get Error Info RDATA, bytes 3 and 4. See the REQUEST SENSE command in Chapter 4 of the Host Interface Guide, Volume 3 of the HP LTO Ultrium Technical Reference

Manual.

Generic module (from 0000h)

Code

0000h

0001h

0002h

0003h

0004h

0005h

0006h

0007h

Description

Good.

Bad.

Done.

Aborted.

Invalid configuration values.

Invalid configuration name.

Place holder until real status is known.

Invalid parameter supplied to function.

Automation Control Interface (from 0400h)

Code

0401h

0402h

0403h

0404h

0405h

0406h

0407h

0408h

0409h

040Ah

040Bh

040Ch

040Dh

040Eh

040Fh

0410h

0411h

0412h

Description

Unsupported command opcode.

Busy—command rejected.

RAMBIST failed.

Invalid command checksums.

Invalid baud rates.

Invalid command while load/unload pending.

Time-out waiting to end immediate command.

RAM framing error.

RAM overrun error.

Invalid command length .

Byte buffer framing error.

Byte buffer overrun error.

Command active abort rejected.

Invalid response acknowledgement.

Transmission time-out.

Did not receive ETX.

Cancel command packet timer error.

Custom byte error.

62 Drive error codes

Code

0413h

0414h

041Ch

041Dh

041Eh

041Fh

0420h

0421h

0422h

0423h

0415h

0416h

0417h

0418h

0419h

041Ah

041Bh

0424h

0425h

0426h

0427h

0428h

0429h

042Ah

042Bh

042Ch

042Dh

042Eh

042Fh

0430h

0431h

0432h

0433h

0434h

0435h

0436h

Description

Response acknowledgement time-out.

Cancel response acknowledgement timer error.

Unexpected byte received.

Zero length command.

Invalid command reserved field.

RAMBIST did not complete.

Ignored a byte received while transmitting response.

Invalid CDB data length.

Firmware image too big.

ACI response is longer than the available buffer.

Did not receive acknowledgement to program flash.

Attempt to create a polling object instance without a polling function.

Attempted to create more polling object instances than the maximum allowed.

Attempted to access a polling object instance that does not exist.

ACI command length is greater than the available buffer.

ACI has run out of CRAM.

ACI has received a firmware image larger than expected.

An ACI command parameter contains an invalid value.

ACI acMalloc() failed, insufficient memory available to process command.

ACI Control queue is full.

ACI Response queue is full.

ACI Control queue is empty.

ACI Response queue is empty.

ACI Response packet was NAKed.

ACI attempted to execute an unsupported PPL command.

ACI has detected a command with a parameter out of range.

ACI attempted to execute a PPL command before the previous command completed.

ACI received more raw data than expected; see the Write Buffer PPL command.

Internal status indicating a slow ACI command rather than a fast one.

Internal status indicating an operation has initiated a DMA transfer.

Internal status indicating that a firmware image has been downloaded so the firmware should have been upgraded.

Internal status indicating that a firmware image download has been aborted.

Surrogate SCSI command terminated due to a SCSI reset/abort for the LUN.

ACI has not been allocated the amount of DRAM it requires.

ACI has not been allocated the amount of CRAM it requires.

An ACI surrogate SCSI command packet contained an invalid Exchange ID.

Automation Control Interface (from 0400h) 63

0443h

0444h

0445h

0446h

0447h

0448h

0449h

044Ah

044Bh

044Ch

044Dh

044Eh

044Fh

0450h

0451h

0452h

0453h

0454h

Code

0437h

0438h

0439h

043Ah

043Bh

043Ch

043Dh

043Eh

043Fh

0440h

0441h

0442h

Description

A CDB contained an invalid exchange ID.

ACI Surrogate SCSI queue is full.

ACI Surrogate SCSI queue is empty.

A request for an invalid entry in Surrogate SCSI queue has been made.

ACI has received an acSurrogateNotifyOp with an unknown SCSI CDB type.

The SCSI Data Length parameter has changed unexpectedly.

Internal status indicating a PPL Command is being executed.

ACI too busy for fast command. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy for immediate command. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy for slow command. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy for SCSI command. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy because of overlapped commands. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy because of comms resync. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy because upgrading. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI too busy because out of memory. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

ACI is resynchronizing comms with library after persistent comms failure.

SCSI opcode is not supported in this firmware release.

Internal status indicating an ACI reset is required.

Internal status indicating a full drive reset is required.

Command contains an invalid Memory ID.

All Command Control Blocks have been allocated.

The returned or referenced Command Control Block is invalid.

Response Time-out — command aborted and response sent.

Response Time-out — response sent but command allowed to continue.

Response Time-out — ACI failed to send response within the Response Period.

ACI too busy because the CCB queue is full. Used in tracepoints to identify the cause of

AC_BUSY_CMD_REJECTED error.

ACI command contains the sequence number of the previous command. The command is ignored.

Internal status indicating a slow ACI command being executed before Drive Ready event.

Failed to transmit ACK/NAK within the Packet Acknowledgement period.

Internal status indicating a direct ACI command rather than a fast or slow one.

64 Drive error codes

Code

0455h

0456h

0457h

0458h

0459h

045Ah

045Bh

045Ch

045Dh

0480h

0481h

0482h

0483h

0484h

0485h

0486h

0487h

0488h

Description

ACI too busy for a direct command. Used in tracepoints to identify cause of

AC_BUSY_CMD_REJECTED error.

Cannot perform operation because the SCSI burst size is zero or unknown.

Command not supported because the primary interface has not been enabled.

Unable to get a new task object.

An ADI frame has been received while one or more ACI commands are outstanding.

An SOF was received in ACI Mode which was not a valid frame.

The SSC device has not requested the amount of data supplied with the ACI SCSI command.

The specified automation port is not supported.

A function will send a response when it has finished.

ACI self-test failure — ACI should not be executing a direct Command while performing the self-test.

ACI self-test failure — ACI should not be executing a slow Command while performing the self-test.

ACI self-test failure — if ACI is idle, the Control queue should be empty.

ACI self-test failure — if ACI is idle, the Response queue should be empty.

ACI self-test failure — if ACI is idle, the Surrogate SCSI queue should be empty.

ACI self-test failure — if ACI is idle, only the self-test command should be allocated in the small

Data Region.

ACI self-test failure — if ACI is idle, no memory from the Large Data Region should be allocated.

ACI self-test failure — if ACI is idle, no CRAM memory should be allocated.

ACI self-test failure — if ACI is idle, only one CCB should be allocated.

Buffer manager (from 0800h)

Code

0800h

0801h

0802h

0803h

0804h

0805h

0806h

0807h

0808h

0809h

080Ah

Description

The buffer manager failed to initialize correctly.

No Buffer Allocation description exists for the supplied Module ID

The request queue has overflowed.

The priority request queue has overflowed.

Dataset index error: BMMDataSetIdxToAddr() has been passed an invalid Idx.

Dataset information table index error: BMMDataSetIdxToDSITAddr() has been passed an invalid

Idx

.

ACN index error: BMMDataSetIdxToACNandLPOSAddr() has been passed an invalid Idx.

Wrap index error: BMMDataSetIdxToWrapAddr() has been passed an invalid dataset Idx.

The Notification queue has overflowed. See BMMXferComplete().

The notification was not SDL signal for DSIT read. See BMMXferComplete().

The Notification queue has underflowed. See BMMXferComplete().

Buffer manager (from 0800h) 65

1820h

1821h

1822h

1823h

1830h

1831h

1840h

1841h

1809h

180Ah

180Bh

180Ch

180Dh

180Eh

180Fh

1810h

Code

1800h

1801h

1802h

1803h

1804h

1805h

1806h

1807h

1808h

1842h

1843h

1844h

1845h

1846h

1847h

1848h

1849h

184Ah

184Bh

Diagnostic control (from 1800h)

Description

No errors.

Invalid command.

Invalid parameters.

Drive not ready.

Command failed.

Command aborted.

Too few parameters.

Too many parameters.

Command denied.

Operation code not supported in diagnostic CDB command.

Page code not supported in diagnostic CDB command.

Buffer code not supported in read/write buffer command.

Parity error on serial receive.

Framing error on serial receive.

Overflow error on serial receive.

Excessive input length, exceeding 220 characters.

Power-on self-test not executed.

Error detected during the Register Walking 1 test.

Built-in self-test failure.

No test available for the parameters provided.

Error detected during the Memory test.

Power-on self-test failed the processor internal SRAM data bus test.

Power-on self-test failed the processor internal SRAM address bus test.

Power-on self-test failed the DRAM MPU Port test.

Power-on self-test failed the DRAM Data Bus test.

Power-on self-test failed the DRAM Addr Bus test.

Power-on self-test failed the Formatter ASIC Register test.

Power-on self-test failed the Formatter ASIC built-in self-test).

Power-on self-test failed the Firmware Image Checksum.

Power-on self-test failed the CRAM Data Bus test.

Power-on self-test failed the CRAM Address Bus test.

Power-on self-test failed the SCSI ASIC Register test.

Power-on self-test failed the SCSI ASIC Buffer Data Bus test.

Power-on self-test failed the SCSI ASIC Buffer Address Bus test.

Internal status instructing DI to exit Data Collection Mode.

66 Drive error codes

Code

184Ch

184Dh

184Eh

184Fh

1850h

1851h

1852h

1853h

1854h

1855h

1856h

1857h

1858h

1859h

1860h

1861h

1862h

1863h

1864h

1865h

1866h

185Ah

185Bh

185Ch

185Dh

185Eh

185Fh

1867h

1868h

1869h

186Ah

186Bh

186Ch

186Dh

186Eh

186Fh

Description

Internal status instructing DI to execute the command as a Slow command.

Diagnostic Control has rejected a command because it is already executing a command.

Attempted to release Diagnostic Results memory that has not been allocated.

Unable to perform a Diagnostic command as the Diagnostic Results memory is already reserved.

Diagnostic Results data has overflow the memory allocated for results.

DI has received an unsupported SCSI opcode in diExecScsiDiagOp.

DI attempted to set an illegal baud rate.

Set Config attempted to set a read-only configuration.

Indicates DI needs to send response in the Port buffer before completing the command.

Power-on self-test failed the external SRAM Data Bus test.

Power-on self-test failed the external SRAM Address Bus test.

Internal status indicating that a Log command specifies an FLM log.

Returned by some log extraction functions to indicate there is more data to extract.

Comms error (such as framing or overrun) detected on the Serial Test port.

The Serial Test port has timed-out while receiving data.

A device server has requested an operation not supported by diPortIF.

Unable to get a new task object.

SCSI Command cannot be executed in Limited Operation Mode

Internal status instructing DI to send status before starting the protocol test.

Memory access denied to a READ/WRITE BUFFER command.

Memory access denied to a READ/WRITE MEMORY command.

Power-on self-test failed; unrecoverable ECC error detected.

A field is invalid in a diagnostic CDB command.

POST failed. The image checksum is invalid.

POST failed. The checksum is incomplete.

Invalid length/address in READ/WRITE MEMORY command.

The Drive Configuration Table returned permission denied in response to a Write CM/EEPROM operation.

Verify root key failed as no root key found in OTP.

Root key is incorrect.

Drive unexpectedly in unsecured state.

RSA public key not found.

RSA private key not found.

RSA key pair not found.

Data following encryption/decryption with RSA key is incorrect.

Root key generated when one already exists.

Drive in unexpected security state.

Diagnostic control (from 1800h) 67

Code

1870h

1871h

1879h

187Ah

187Bh

187Ch

187Dh

187Eh

187Fh

1880h

1872h

1873h

1874h

1875h

1876h

1877h

1878h

1881h

1882h

1883h

1884h

1885h

1886h

1887h

1888h

1889h

188Ah

188Bh

188Ch

Description

RSA key storage was attempted when one already exists.

OTP public key already exists.

OTP public key not found.

Management ARM testid is not supported.

Unable to obtain Humidity value.

Unable to obtain Humidity value.

Unable to perform OTP write.

Unable to perform OTP read.

Unable to perform OTP write, write-protect set.

Unable to perform OTP write; the bank has been previously written to.

OTP write has taken too long.

OTP STATUS_RDY not set when expected.

OTP STATUS_RDY not set for bank re-read following write.

POST failed OTP security state in debug mode.

Checking OTP banks blank, parameters out of bounds.

Supplied parameters out of bounds for this Buffer ID.

POST failed OTP verifying Debug mode.

POST failed OTP setting Debug mode.

POST successfully set Debug mode.

Failed to read binary data from the Serial port.

Attempting to run ERT test whilst ERT test in progress.

SCSI infrastructure requested a read-only test PortIF operation with an invalid or obsolete TaskPtr.

Read-only test operation with an invalid TestState.

Read-only test attempted with an invalid TapeType.

A Read-only test command requested more SCSI data (out) than was available.

SCSI iInfrastructure requested a read-only test PortIF operation with an unexpected opcode.

PHY setting parameter incorrect.

Write-only test attempted with an invalid TapeType.

Internal Write ERT Test operation completed with an invalid TestState.

Drive control (from 1C00h)

Code

1C00h

1C01h

1C02h

1C03h

Description

Bad cartridge type. Attempted to load a cartridge of a type that drive control cannot handle.

Attempted to unload a cartridge when Prevent Medium Removal is on.

There is no firmware image available for upgrade.

Firmware image is incomplete.

68 Drive error codes

Code

1C04h

1C05h

1C0Dh

1C0Eh

1C0Fh

1C10h

1C11h

1C12h

1C13h

1C14h

1C06h

1C07h

1C08h

1C09h

1C0Ah

1C0Bh

1C0Ch

1C1Dh

1C1Eh

1C1Fh

1C20h

1C21h

1C22h

1C23h

1C24h

1C15h

1C16h

1C17h

1C18h

1C19h

1C1Ah

1C1Bh

1C1Ch

1C25h

1C26h

1C27h

Description

Firmware image has checksum or other errors.

Firmware image is not compatible with the drive configuration.

Firmware image is too big to upgrade from.

Internal error in the Drive Control firmware upgrade code.

A firmware upgrade cartridge was in the drive when it powered on.

A load without threading has been requested for a cartridge with unusable Cartridge Memory.

Tried to load a writable cartridge with an unusable Cartridge Memory.

The write-protect tab setting was changed during a load.

A non-HP cleaning cartridge has been inserted in the drive.

Cannot determine the manufacturer of the cleaning cartridge.

No DRAM space reserved to hold the firmware image.

A cleaning cartridge was in the drive when it powered on.

Drive Control did an eject during the power-on sequence.

A firmware upgrade cartridge has been loaded when a data cartridge was expected.

A firmware upgrade cartridge was expected but some other type of cartridge has been inserted.

Failure due to drive temperature being out of acceptable range.

Cleaning cartridge initialized by a non-HP drive.

Trying to convert a non-data cartridge into a firmware upgrade cartridge.

Operation failed because cartridge is not present or not ready.

Cleaning cartridge loaded when a data cartridge was expected.

Expected a cleaning cartridge but got something else on load.

Cartridge Memory is unusable and failed to read the FID.

Firmware upgrade image information is unavailable.

Could not find firmware information in the new image.

A tape load has failed.

The EOD Validity field is not Good.

Firmware image is not compatible with drive sub-personality configuration.

A TMR timer fired but the ID does not match what was expected.

Firmware image has incorrect signature.

The firmware upgrade image is too old.

Firmware upgrade image version is too large.

Unknown tape format encountered during firmware upgrade.

Unknown host error during firmware upgrade.

Unable to change to the specified partition because no two partition tape is loaded, the current position is already in that partition, or there is no such partition.

Cannot perform a multi-partition operation as partitions are not supported on this media.

The media does not support this number of partitions.

Drive control (from 1C00h) 69

Code

1C28h

1C29h

Description

No format is required because the tape is already formatted as required.

Requested sizes of partitions are outside the valid range for this media.

Drive monitor (from 2000h)

Code

2000h

2001h

Description

No error. Synonymous with GOOD status.

Invalid parameter. The value of a parameter received with a Drive Monitor operation falls outside its valid range.

External interfaces (from 2400h)

2411h

2412h

2413h

2414h

2415h

2416h

240Ah

240Bh

240Ch

240Dh

240Eh

240Fh

2410h

2417h

2418h

2419h

Code

2400h

2401h

2402h

2403h

2404h

2405h

2406h

2407h

2408h

2409h

70 Drive error codes

Description

Command holder full.

Bad command handle.

Empty command handle.

No tape loaded.

Already loaded.

In diagnostic mode.

Not in diagnostic mode.

Tried to write to write protected cartridge.

Aborted an active command.

Aborted a command before it became active.

Tried to abort a command that was not queued.

Invalid state requested of the EII State Manager.

The EII tried to process a firmware upgrade type that is not supported.

The EII state manager could not handle an abort request.

Tried to abort a command that was already being aborted.

Tried to get a command for the wrong module.

Command specified in eiNotifyOp would not have been top of queue.

Attempt to delete a queued EII command.

Multiple attempts to delete an executing EII command.

Attempt to queue a queued EII command.

Attempt to queue an executing EII command.

Attempt to remove a command from empty EII command queue.

Attempt to execute a command still on the EII command queue.

Attempt to execute an EII command when another is executing.

Attempt to stop executing an EII command that was not executing.

The module putting a command on the EII command queue is not the module that allocated it.

Front panel interface (from 2800h)

Code

2801h

Description

Failure due to use of forced eject.

Host interface (from 2C01h)

2C16h

2C17h

2C18h

2C19h

2C1Ah

2C1Bh

2C1Ch

2C1Dh

2C0Eh

2C0Fh

2C10h

2C11h

2C12h

2C13h

2C14h

2C15h

2C1Eh

2C1Fh

2C06h

2C07h

2C08h

2C09h

2C0Ah

2C0Bh

2C0Ch

2C0Dh

Code

2C01h

2C02h

2C03h

2C04h

2C05h

Description

Unknown opcode.

Reserved field set.

Unknown mode page.

Firmware bug.

Parameter list length error.

Already prevented.

Not prevented.

Too many hosts.

32-bit overflow.

Invalid space code.

Bad inquiry page.

Not the reserver.

Not reserved.

Third-party bad.

Third-party host.

Reserved.

Read Buffer ID.

Read Buffer mode.

Write Buffer ID.

Write Buffer mode.

Main Buffer mode.

Write Buffer header.

No EVPD.

Drive not ready.

Density medium no tape.

ARM firmware error code 0, used by the embedded ARM firmware.

ARM POST fail.

TX fail.

Inf host interface ARM POST — SDRAM test failed.

Inf host interface ARM POST — SDRAM BIST time-out.

Inf host interface ARM POST — SDRAM memory access.

Front panel interface (from 2800h) 71

Code

2C20h

2C21h

2C29h

2C2Ah

2C2Bh

2C2Ch

2C2Dh

2C2Eh

2C2Fh

2C30h

2C22h

2C23h

2C24h

2C25h

2C26h

2C27h

2C28h

2C39h

2C3Ah

2C3Bh

2C3Ch

2C3Dh

2C3Eh

2C3Fh

2C40h

2C31h

2C32h

2C33h

2C34h

2C35h

2C36h

2C37h

2C38h

2C41h

2C42h

2C50h

2C51h

72 Drive error codes

Description

Inf host interface ARM POST — Atmel memory test.

Inf host interface ARM POST — no Olga connected.

Inf host interface ARM POST — FC diagnostic CC1

Inf host interface ARM POST — FC diagnostic counters.

Inf host interface ARM POST — FC diagnostic FIFO test.

Inf host interface ARM POST — FC diagnostic interface.

Inf host interface ARM POST — FC diagnostic register check.

SPI host interface report parity error status.

SPI host interface ARM POST — register diagnostics failed.

SPI host interface ARM POST — PDC BIST time-out.

SPI host interface ARM POST — PDC RAM BIST error.

SPI host interface ARM POST — BC BIST time-out.

SPI host interface ARM POST — BC RAM BIST error.

SPI buffer channel 1 CRC error.

SPI buffer channel 1 FIFO parity error.

SPI sync offset error.

SPI illegal write error.

SPI illegal command error.

SPI FIFO overflow or underflow error.

SPI IDE message received.

SPI BDR message received.

SPI abort task message received.

SPI parity error message received.

SPI host interface ARM POST record manager diagnostics failed.

SPI host interface ARM POST host port diagnostics failed.

Buffer manager Titov host port control premature DREQ.

Buffer manager Titov host port control parity error.

Buffer manager Titov host port control CRC error.

Buffer manager Titov host port control FIFO overflow.

Buffer manager Titov host port control DMA overrun.

Buffer manager Titov host port control outstanding error.

Buffer manager Titov host port control sync data error.

Buffer manager check buffer CRCs mismatch.

Buffer manager check CRC passed.

SAS active cable error.

Illegal SCSI command. The hardware or firmware does not recognize the CDB.

The SCSI Macro command was aborted because the drive was selected first.

2C6Dh

2C6Eh

2C6Fh

2C70h

2C71h

2C72h

2C73h

2C74h

2C75h

2C63h

2C64h

2C65h

2C66h

2C67h

2C68h

2C69h

2C6Ah

2C6Bh

2C6Ch

Code

2C52h

2C53h

2C5Bh

2C5Ch

2C5Dh

2C5Eh

2C5Fh

2C60h

2C61h

2C62h

2C54h

2C55h

2C56h

2C57h

2C58h

2C59h

2C5Ah

Description

ATN was pulled by the initiator.

Initiator did not respond to reselect within the reselect time-out period.

The internal port interface task queue was empty.

Too many port interface tasks. There is no room left in the internal port interface task queue.

Parity error on the SCSI bus.

Parity error in the mini-buffer.

Attempted to use an invalid value internally.

The SCSI FIFO was not empty when attempting to write to it.

Not connected. Attempted to issue SCSI macro target command while not in target mode.

Wrong host. Attempted to communicate with Host X while connected to Host Y.

Wrong bus state. Attempted SCSI macro command while in the incorrect bus phase.

No information on host. This host has not communicated with us previously.

Invalid speed. The saved SCSI bus speed for this host is corrupt.

Invalid SCSI ID, outside the range 0-15.

The group code in CDB is not supported.

The host attempted to issue an overlapped command.

Not enough buffer space. The internal requestor asked for more space than was available in the mini-buffer.

The mini-buffer is non-functional.

Buffer in use. The internal requestor was denied access to the mini-buffer.

Status interrupted; the SCSI status phase failed.

Received an IDE (Initiator Detected Error) message.

Received an MPE (Message Parity Error) message.

Received a BDR (Bus Device Reset) message.

Received an Abort message.

Failed the Media Information check.

There is no tape in the drive.

Loading a tape.

Media changed. A tape is present in the drive but not loaded.

Cleaning the tape heads.

Received a PON or SCSI reset.

A mode change (LVD/SE) occurred on the SCSI bus.

Gross error detected by the SCSI Macro.

Illegal length record (ILI) — too long.

Illegal length record (ILI) — too short.

CRC error on read.

The requested burst size was larger than the drive supports.

Host interface (from 2C01h) 73

Code

2C76h

2C77h

2C78h

2C79h

2C7Ah

2C7Bh

2C7Ch

2C7Dh

2C7Eh

2C86h

2C87h

2C88h

2C89h

2C8Ah

2C8Eh

2C8Fh

2C90h

2C7Fh

2C80h

2C81h

2C82h

2C83h

2C84h

2C85h

2C91h

2C92h

2C93h

2C94h

2C95h

2C96h

2C97h

2C98h

2C99h

2C9Ah

2C9Bh

Description

There was an invalid field in the mode parameter list for this MODE SELECT command

Unloading the tape.

A parameter supplied by the internal requestor was out of range.

The allocation length exceeded the permitted length.

Invalid (unsupported) page code.

Invalid (unsupported) page code in parameter list.

BOT encountered on space.

EOT encountered on space.

Blank Check, EOD was encountered. Returned by hiPerformPreExeChecks if a space or read is attempted on a virgin tape.

Position lost. A temporary code for returning status after a write-behind error.

PCR error in the Log Select command.

The supplied Page Code is not a resettable page.

The supplied Page Code is not a writable page.

The reserved bit in the Log Page header has been set.

The Log Select Page Length is incorrect.

There is an error with the Log Parameter Header.

Log Select Parameter list length error.

The Log Sense Page Code is invalid.

The Log Sense PC Code is in error.

Log Select: error in the parameter header.

Restart the Logical Pipeline after a format error.

The Buffer Manager has been interrupted with an error.

Check the cables. The Host Interface has exhausted all of the retries for a data phase.

Log Select parameter list length error.

hiPopulateSenseBuffer() could not find any free sense data buffers.

The failure prediction threshold has been exceeded. This error code is sent when a check condition is generated for a CDB as a result of the Test flag being set in the Information Exceptions Mode page.

Reset after GE. Triggers the power-on self-test UA 2900 after LTO 1 SCSI ASIC GE has been detected.

Return GOOD status. Used to force GOOD status to be returned.

There is a firmware bug in the handling of an inquiry page.

There is a firmware bug in the execution of the Prevent/Allow Medium Removal command.

There is a firmware bug in the parsing of a Mode page.

An attempt was made to write data or filemarks inside EW-EOM.

Firmware incorrectly programmed the SCSI macro.

An unsupported LUN was specified in the SCSI Identify message.

Aborting a previous command.

74 Drive error codes

2CA1h

2CA2h

2CA3h

2CA4h

2CA5h

2CA6h

2CA7h

2CA8h

2CA9h

2CAAh

2CABh

2CACh

2CADh

2CAEh

2CAFh

2CB0h

2CB1h

2CB2h

2CB3h

2CB4h

2CB5h

2CB6h

2CB7h

2CB8h

2CB9h

2CBAh

2CBBh

2CBCh

Code

2C9Ch

2C9Dh

2C9Eh

2C9Fh

2CA0h

Description

Aborting and no disconnect. A command was rejected that could not be queued while an abort was in progress.

The host interface has exhausted all of the retries for a command phase.

Parameter not supported. A request for an invalid page code has been sent.

Buffer offset good. This is used internally by the Read Write Buffer code and should never be reported to the host.

Operation in progress. Reported when an Immediate command is executing and a subsequent command is received.

Illegal length record (ILI) — too long, and there is an EOR in FIFO. This occurs when a record is long by less than the FIFO length.

Illegal length record (ILI) — too short with bad CRC.

Illegal length record (ILI) — too long with bad CRC.

LUN not configured. The drive is the process of becoming ready.

ILI long has been detected but a read error was encountered during the residue flush.

An init command is required; a tape has been loaded but not threaded.

ILI long has been detected but flushing the residue timed out.

LTO 1 drives only: The CD-ROM El Torito identifier is corrupt.

The LTO 1 Formatter ASIC is not supported any more.

The LTO 1 SCSI ASIC is an invalid revision.

MAM attribute header truncated. The specified parameter list length has caused an attribute header to be truncated.

Reserved field set in a MAM attribute header.

MAM attribute IDs were not ascending order.

The MAM attribute header specified an unsupported attribute value.

A MAM attribute ID is unsupported.

A MAM attribute ID is in an incorrect format.

The MAM attribute header specifies an incorrect length for this attribute.

The host attribute area in MAM is full.

A Write Attribute command attempted to delete a non-existent attribute.

An invalid MAM service action was requested.

A Read attribute command failed because the Host Attribute area was not valid.

There is an invalid field in the MAM attribute data.

Failure prediction threshold exceeded. A Tape Alert flag has been set and the next SCSI command needs to be check conditioned.

GWIF idle error, cause unknown. This will never be returned to the host.

GWIF idle, read error. This will never be returned to the host.

GWIF idle, write error. This will never be returned to the host.

MAM is accessible but the cartridge is in the load “hold” position. Unit Attention is generated.

MAM is accessible but the cartridge is in the load “hold” position. Not Ready is generated.

Host interface (from 2C01h) 75

2CD3h

2CD4h

2CD5h

2CD6h

2CD7h

2CD8h

2CD9h

2CDAh

2CCBh

2CCCh

2CCDh

2CCEh

2CCFh

2CD0h

2CD1h

2CD2h

2CDBh

2CDCh

2CDDh

2CDEh

2CDFh

2CE0h

2CE1h

Code

2CBDh

2CBEh

2CC5h

2CC6h

2CC7h

2CC8h

2CC9h

2CCAh

2CBFh

2CC0h

2CC1h

2CC2h

2CC3h

2CC4h

76 Drive error codes

Description

Internal port interface task queue error — invalid task.

Unable to write due to bad Cartridge Memory.

Selway ignored ATN on REQUEST SENSE.

Invalid number of wraps requested for LEOT.

Invalid LEOT request compared to current position.

MAM not accessible for some indeterminate reason.

SCSI sequencer was asked to reconnect during invalid nexus.

SCSI sequencer received a hiRetryDataBurst which failed.

INQUIRY data too long.

REQUEST SENSE data too long.

Invalid LUN for storing INQUIRY data in the mini-buffer.

No free slot to store REQUEST SENSE data.

Surrogate SCSI not configurable.

Surrogate SCSI LUN not a valid LUN.

Surrogate SCSI command arrived.

Incompatible tape type.

The supplied exchange is invalid.

Invalid value for Dev Cfg SDCA.

Bad length for WRITE BUFFER command.

Echo buffer has been overwritten by another host.

Never reported to host — used to signify a special entry in the Fault Log.

Never reported to host—port interface gave good status

Port interface detected a bus error.

Port interface detected an unknown internal opcode

Port interface detected a bad context ID.

Port interface detected bad parameters for an internal operation.

Port interface has encountered a FM/EOD. Should not be reported.

Port interface SCSI reselection timeout

Port interface internal operation failed due to a PIF/MIF buffer parity error

Command outstanding. Should not be reported.

No command outstanding. Should not be reported.

Not in automode status. Should not be reported.

ARM POST failure.

Port interface detected Bad Data Length—FC_DPL mismatch to CDB allocation length.

Selected while reselecting. Never reported to the host.

Bad state—firmware defect.

Bad configuration—firmware defect.

2CFFh

2D00h

2D01h

2D04h

2D05h

2D06h

2D07h

2D08h

2CF0h

2CF1h

2CF2h

2CF3h

2CFDh

2CFEh

2D09h

2D0Ah

2D0Bh

2D0Ch

2D0Dh

2D0Eh

2D0Fh

2D10h

2D11h

Code

2CE2h

2CE3h

2CE4h

2CE5h

2CE6h

2CE7h

2CE8h

2CE9h

2CEAh

2CEBh

2CECh

2CEDh

2CEEh

2CEFh

Description

The Host Interface ASIC has not responded to a mail-box operation within 10 ms.

Got an internal firmware reboot.

SCSI Bus Reset signal asserted by host.

Bus Device Reset message sent by host.

Transceivers changed to SE.

Transceivers changed to LVD.

Got a power-on reset.

Checksum failure when copying bootloader code into Lucan dual-port RAM.

Amunsden has been reset before receiving the hiPowerOneEvent from Iona.

LF stall on reads.

Tape is threaded but the drive shows it as unloaded.

The ARM FW has determined that this is not a DR tape.

There has been a change in the support Logical Unit inventory.

An invalid Port ID has been logged in.

An invalid LUN opcode has been passed to hiConfigureSurrogateLun().

Fixed mode request was too large.

Decompression size mismatch while expanding and programming the Lucan FPGA code.

Host interface has more to do.

SCSI command failed because another host has changed the log pages.

SCSI command failed because new firmware has been downloaded.

SCSI command failed because another host has changed the mode pages.

Hebrides is reporting a failure due to a read-ahead error.

Hebrides is reporting a failure due to a write-behind error.

Drive requested single shot read/write while streaming.

Search for a handle for a given context ID failed.

The dispatcher has completed the handling of the extended reset rewind.

Firmware upgrade or unknown cartridge loaded but not threaded.

Cleaning tape loaded but not threaded.

Drive control has set drDriveStatus to DR_FW_UPGRADE.

Immediate LOAD/UNLOAD in progress.

Reported when an Immediate command is executing and a subsequent command is received.

I_T nexus loss occurred.

The maximum number of surrogate logical units have been defined.

The supplied surrogate inquiry page is incorrect.

The surrogate logical unit inquiry area is full.

The surrogate logical unit inquiry area has been corrupted.

The operation has been denied as the SCSI port is currently enabled.

Host interface (from 2C01h) 77

Code

2D12h

2D13h

2D14h

2D15h

2D16h

2D17h

2D18h

2D19h

2D1Ah

2D1Bh

2D1Ch

2D1Dh

2D1Eh

2D1Fh

2D20h

2D21h

2D22h

2D23h

2D24h

2D25h

Description

ACI has attempted a surrogate SCSI status operation without first setting up any sense data.

This is no nexus live for this surrogate logical unit.

An invalid SCSI status value has been supplied.

Can not process this command, for some reason send it to lib.

The hiConfigureSurrogateLunOp has resulted in a LUN being deleted.

Unsupported Sub pagecode

First burst.

ACK NAK timeout.

NAK received.

Initiator response timeout.

Data offset error.

Information Unit too short.

Too much write data.

Chan1 detected a CRC error and a subsequent check of the buffer found the CRC good.

Chan1 detected a CRC error and a subsequent check of the buffer found the CRC bad.

Test function in progress.

Invalid configuration action.

Firmware defect; caller specified an invalid Relative Target Port.

ILI encountered performing ADI Verify.

A read-ahead error was encountered during ADI Verify. The read-ahead error should be reported to host, not this error.

No space on queue for hiCountermandOp.

2D26h

Logical formatter (from 3000h)

Code

3000h

3001h

3002h

3003h

3004h

3010h

3011h

3012h

301Fh

Description

No error. Synonymous with GOOD status.

Operation of the Logical Formatter has been aborted.

Busy. A Logical Formatter process has received a operation request while in a transient state.

The value of a parameter received with a Logical Formatter operation request falls outside its valid range.

Unsupported operation. A Logical Formatter process received an operation request while in a mode that does not support that operation.

An error condition occurred during execution of the Logical Formatter power-on self-test or reset algorithm,.

Unexpected interrupt. A Logical Formatter process received a signal from the hardware at an unexpected time.

A Logical Formatter process has received a DiscardComplete signal from the hardware at an unexpected time.

The Codeword Packer contains data bits that cannot be self-flushed.

78 Drive error codes

3025h

3026h

3033h

3034h

3035h

3036h

3037h

3040h

3301h

3302h

3303h

3027h

3028h

3029h

302Ah

302Bh

302Ch

302Dh

302Eh

302Fh

3030h

3031h

3032h

3304h

3305h

3306h

Code

3020h

3021h

3022h

3023h

3024h

Description

Data path not empty. The Hardware Functional Blocks that form the Logical Formatter data path contain data.

Filemark encountered.

Recoverable format error. The Logical Formatter has encountered a recoverable format error while unformatting the data stream.

Unrecoverable format error. The Logical Formatter has encountered an unrecoverable format error while unformatting the data stream.

End marker not required. The Logical Formatter has not inserted an end marker in the current dataset because the dataset is empty.

One or more Hardware Functional Blocks in the Logical Formatter are paused.

The Logical Formatter has a filemark pending, meaning that it is logically before the filemark but physically after it.

Restart the Logical Formatter hardware.

The Logical Formatter has provided a dataset with an access point beyond the target position.

The Logical Formatter has encountered a CRC error while unformatting the data stream.

The Logical Formatter’s C1LFI Hardware Functional Block has failed to prime.

The Logical Formatter has encountered a zero-length record error.

The Logical Formatter has encountered a reserved codeword error.

The Logical Formatter has encountered a filemark in record error.

The Logical Formatter has encountered a decompression error.

The Logical Formatter has encountered EOD.

The Logical Formatter failed to write a filemark — aborted.

The Logical Formatter failed to write a filemark — data path not empty.

The Logical Formatter failed to write a filemark — unsupported operation.

The Logical Formatter has received a non-user data set.

The Logical Formatter failed to write a filemark — packer paused.

The Logical Formatter received an unexpected Access Point interrupt.

The Logical Formatter was unable to insert an end marker.

The Llogical Formatter was unable to complete the Data Key Process.

Logical Media not able to supply any more datasets.

Operation of the Logical Formatter’s Hardware Abstraction Layer has been aborted.

Invalid parameter passed to a function in the Logical Formatter’s Hardware Abstraction Layer.

A function in the Logical Formatter’s Hardware Abstraction Layer has detected an illegal combination of variable values.

A function in the Logical Formatter’s Hardware Abstraction Layer has received a request while in a mode that does not support that request.

The Logical Formatter’s hardware has failed to signal (issue an interrupt for) an event expected by the firmware.

During a buffer transfer that ended with a final burst of ten bytes or less, the Logical Formatter’s hardware failed to signal the transfer completion.

Logical formatter (from 3000h) 79

Code

3307h

3308h

3309h

330Ah

3335h

3336h

3337h

3338h

3339h

333Ah

333Bh

332Bh

332Ch

332Dh

3330h

3331h

3332h

3333h

3334h

3321h

3322h

3323h

3324h

3325h

3326h

3327h

332Ah

330Bh

330Ch

330Dh

330Eh

3310h

3311h

3312h

3320h

Description

During a buffer transfer of ten bytes or less, the Logical Formatter’s hardware failed to signal the transfer completion.

During a buffer transfer that ended with a final burst of ten bytes or less within the first 1k DRAM page, the Logical Formatter’s hardware failed to signal the transfer completion.

A parity error was detected transferring data between Iona/Lucan and Amundsen.

Wanted to start a timer for a potential missing NextDAEmpty interrupt but the pipeline was not empty.

LF’s C1LFI block detected a parity error while reading a byte out of its FIFO.

Logical Formatter detected a correctable SDRAM corruption during Restore.

Logical Formatter detected an uncorrectable SDRAM corruption during Restore.

Logical Formatter SDRAM corruption.

Logical Formatter pipeline stalled.

Logical Formatter compressor reset.

Logical Formatter stall timer ID confusion.

Logical Formatter packer overrun.

Logical Formatter non-empty packed segment.

Logical Formatter packer missed EOR.

Logical Formatter unpacker overrun.

Logical Formatter packer aligned EOR.

Logical Formatter packer data in packer.

Logical Formatter compressor at record boundary.

Logical Formatter record boundary status.

No end marker found in a partially full dataset while writing.

No end marker found in a partially full dataset while reading.

Bad valid data length detected while writing.

Bad valid data length detected while reading.

Logical Formatter unexpected current register value.

Logical Formatter unexpected next register value.

LF bad access point value detected while writing.

LF bad access point value detected while reading.

LF adjusting bad access point while writing.

LF adjusting bad access point while reading.

LF unable to find a good access point while writing.

LF unable to find a good access point while reading.

LF unable to adjust the access point.

LF unable to release.

Unsafe to insert an end marker.

End marker insertion was unsuccessful.

80 Drive error codes

Code

333Ch

3340h

3350h

3351h

3352h

3353h

3354h

3355h

3356h

3357h

3341h

3342h

3343h

3344h

3345h

3346h

3347h

3362h

3363h

3364h

3365h

3366h

3367h

3368h

3369h

3358h

3359h

335Ah

335Bh

335Ch

335Dh

3360h

3361h

3370h

3371h

3372h

3373h

Description

End marker insertion was bad.

Logical Formatter compressor not hung when expected.

LF TRNG BIST failure.

LF RNG monobit test failure.

LF RNG twobit test failure.

LF RNG failure.

LF ignoring TRNG BIST failure.

LF TRNG BIST failed in an unexpected way.

LF skipping an all-zero sample from the True Random Number Generator.

Bad encryption key index detected.

Encrypt decompression error detected.

Encrypt record CRC error detected.

Encrypt Crypt error detected.

Encrypt UnpackerLite error detected.

Crypt GCM tag error detectd.

Crypt EoR alignment error.

Crypt EoR before tag error detected.

Crypt If_data_valid error detected.

Crypt EoR found error detected.

LF post-key wrap failure.

LF post-key unwrap failure.

LF post-key unwrap IV failure.

LF key unwrap IV failure.

Encryption boundary detected.

Encryption key mismatch detected.

Encryption AAD mismatch detected.

Encryption UAD mismatch detected.

Unencryption boundary detected.

Encryption key signature mismatch detected while in RAW read mode.

RAW read attempted on encrypted data.

Externally encrypted data detected.

Non-externally encrypted data detected.

LF RAW read M-KAD mismatch detected.

Encryption known answer test has failed.

Decryption known answer test has failed.

Random number generator known answer test has failed.

Random number generator continuous test has failed.

Logical formatter (from 3000h) 81

Code

3374h

3380h

3381h

3382h

33FFh

Description

RSA signature known answer test has failed.

LF Buffer Port has not disabled.

LF Buffer Port lfpout FIFO has not emptied.

LF Check of Compressor HW Bug workaround shows the special pattern check has failed.

A non-specific error has occurred in the Logical Formatter.

Logical media (from 3400h)

3411h

3412h

3413h

3414h

3415h

3416h

3417h

3418h

3409h

340Ah

340Bh

340Ch

340Dh

340Eh

340Fh

3410h

3419h

341Ah

341Bh

Code

3400h

3401h

3402h

3403h

3404h

3405h

3406h

3407h

3408h

Description

Cache overflow. A dataset has been received when the cache is already full.

A dataset has been located in the cache where it should not be.

A tag dataset has been located in the cache where it should not be.

Attempted to unlock a dataset which is not locked.

Cache empty. Expected at least one dataset in the cache.

The dataset index appears in the cache more than once.

The dataset index is too large to be valid.

The cache entry does not contain valid datasets.

End-Of-Data has been encountered.

The number of tag datasets in the cache exceeds the limit.

A dataset is positioned in the cache incorrectly.

One or more dataset indices are missing from the cache.

Not a recognized Virtual Mode.

The operation is not supported when more than one dataset locked.

The tape is unformatted or contains no user datasets.

One or more cache pointers are invalid.

No datasets in the cache to fulfil the request.

Operation is not supported while there are operations outstanding.

Operation is not supported while datasets are locked.

The target dataset has not been located.

The target dataset has been located.

The cache has not be initialized.

Received an operation which is not supported in the current mode.

LF has attempted to rewrite a read-only dataset.

A test has taken too long to complete.

Too many pending LP cache operations.

Too many pending PP cache operations.

Received an inappropriate response.

82 Drive error codes

Code

341Ch

341Dh

3425h

3426h

3427h

3428h

3480h

37FFh

341Eh

341Fh

3420h

3421h

3422h

3423h

3424h

Description

Linked-list ‘next’ pointer is invalid.

CRAM transfer started but not finished.

Allocated insufficient CRAM.

Dataset is available in LM but the drive is not positioned to append.

Datasets in LM, Flush WITH_EOD required before the current operation

LM flushed but EOD is required before the current operation.

The specified dataset type is not supported by the operation.

The specified CRAM dataset type is not supported.

LF has attempted an operation away from EOD that can only be performed at EOD.

Search dataset available dataset number does not match the DSIT contents.

LF has requested a dataset while LM is changing to backup mode.

LM has received a PP space dataset with no access point.

LM has received a previous PP space dataset with no access point.

LM is generating an EOD dataset.

Undefined error.

Logical pipeline control (from 3800h)

Error

3800h

3801h

3802h

3803h

3804h

3805h

3806h

3BFFh

Description

No error. Synonymous with GOOD status.

Aborted operation.

Busy. An operation request was received while in a transient state.

The value of a parameter received with a Logical Pipeline Control operation request falls outside its valid range.

Received an operation request while in a mode that does not allow that operation.

Operation aborted because of a write-behind error.

Logical Pipeline Control has detected an unexpected File Mark during a Space operation.

A non-specific error has occurred in Logical Pipeline Control.

Mechanism control (from 3C00h)

Error

3C00h

3C01h

3C02h

3C03h

3D01h

3E01h

3E02h

Description

No error.

Aborted command error.

Unsupported command error.

Bad parameter error.

Undefined data object error.

Wait for signal.

Object create failed.

Logical pipeline control (from 3800h) 83

4008h

4011h

4012h

4013h

4014h

4015h

4016h

4017h

Error

4002h

4003h

4004h

4005h

4006h

4007h

4018h

4019h

4021h

Error

3E03h

3E04h

3E0Ch

3E0Dh

3E0Eh

3E0Fh

3E10h

3FFEh

3FFFh

3E05h

3E06h

3E07h

3E08h

3E09h

3E0Ah

3E0Bh

Description

Object execute failed.

Cartridge memory LPOS values suspect.

Notify client list full.

Position notify list full.

Notify exists parameter different.

Notify event create failed.

Notify key map failed.

Notify index too large.

Too many MC command objects.

Cleaning cartridge expired.

Cannot determine, or do not recognize, the cartridge format.

Cleaning cartridge could not be threaded.

Too many MI command objects.

Listing command objects in queue.

C++ pure virtual function called.

Undefined error.

Non-volatile data manager (from 4000h)

Description

Invalid parameter.

Data length exceeds table length.

Not a valid EEPROM.

Checksum error. A write to EEPROM failed because the EEPROM is invalid.

Checksum read did not match the checksum written.

An unsupported data type was requested from the Non-Volatile Data Manager.

An unsupported data type was requested to be set in Non-Volatile Data Manager.

PCA EEPROM missing.

PCA EEPROM void.

PCA EEPROM corrupt.

PCA table invalid.

A failure occurred while trying to update the Read ERT log in the PCA EEPROM.

A failure occurred while trying to update the Write ERT log in the PCA EEPROM.

A failure occurred while trying to update the Write Fault Counters log in the PCA EEPROM.

A failure occurred while trying to update the Tapes Used logs in the PCA EEPROM.

PCA Manufacturing Parameters Table is invalid.

Head EEPROM absent.

84 Drive error codes

Error

4022h

4023h

4035h

4036h

4037h

4038h

4039h

403Ah

4025h

4026h

4028h

4031h

4032h

4033h

4034h

403Bh

4041h

4042h

4043h

4044h

404Dh

404Eh

4050h

4051h

4052h

4053h

4054h

4055h

4045h

4046h

4047h

4048h

4049h

404Ah

404Bh

404Ch

4056h

Description

Head EEPROM void.

Head EEPROM corrupt.

Head/Flex Manufacturing Parameters table is invalid.

Head Tuning Parameters table is invalid.

Formatter Data Skew Parameters table is invalid.

Mechanism EEPROM absent.

Mechanism EEPROM void.

Mechanism EEPROM corrupt.

Mechanism table invalid.

A failure occurred while trying to update the Drive Fault logs in the PCA EEPROM.

An Algorithm error occurred while trying to update the Drive Fault Logs in the EEPROM.

Mechanism table 3 invalid.

Mechanism table 4 invalid.

The Servo Fault could not be logged because of EEPROM access failure.

nv_MECH_TABLE2 invalid.

nv_MECH_TABLE1 invalid.

CM EEPROM absent.

CM EEPROM void.

The CM could not be written before an unload causing probable corruption in the CM.

An invalid protected page table was found.

A CRC error was discovered over the unprotected page table.

CM initialized. This is not really an error, it indicates a fresh cartridge.

CM invalid CRC.

An invalid CRC over the Cartridge Manufacturers Information page was found.

An invalid CRC over the Media Manufacturers Information page was found.

An invalid CRC over the Initialization Data page was found.

An initialization table was request to be created for a CM with a valid initialization table in it.

A failure occurred while trying to add a page descriptor to the unprotected page table.

An unprotected page table entry was attempted with an invalid page ID.

An invalid CRC over the Drive Manufacturers Support page was found.

An access to the tape directory was requested before it was read from the CM.

A CRC error was detected in the tape directory while being read.

Data for an illegal wrap section was requested from the tape directory.

The Buffer Manager does not have enough CRAM to hold the CM.

The write-protect operation was aborted because of a bogus initialization data address in CRAM.

A consistency error was detected in the Tape Directory while being read.

No more entries can be added to the Suspended Appends page.

Non-volatile data manager (from 4000h) 85

40ABh

40ACh

40ADh

40AEh

40AFh

40B0h

40B1h

40B2h

Error

4060h

4061h

40A1h

40A2h

40A3h

40A4h

40A5h

40A6h

40A7h

40A8h

4062h

4070h

4080h

4090h

4091h

4092h

40A0h

40A9h

40AAh

40B3h

40B4h

40B5h

40B6h

40B7h

40B8h

Description

An access to a non-existent EOD page was attempted.

An invalid CRC over the EOD page was found.

An access to a non-existent Initialization page was attempted.

An access to a non-existent Tape Write Pass page was attempted.

An access to a non-existent Tape Alert page was attempted.

There is no usage data available in the Cartridge Memory.

Usage pages are out of order and cannot be accessed.

The last updated usage page has a CRC error. The data is invalid.

There is no mechanism sub-page data available in the Cartridge Memory.

The last updated mechanism sub-page has a CRC error. The data is invalid.

There has been a failure executing self-test. This failure is logged in the Fault Log.

Cartridge Memory TapeAlert CRC error.

Cartridge Memory EOD page CRC error.

Cartridge Memory suspend append CRC error.

Cartridge Memory Media Manufacturer CRC error.

Cartridge Memory mechanism CRC error.

Cartridge Memory application specific CRC error.

Unknown cartridge type in Cartridge Memory.

A Cartridge Memory flush operation (CRAM to CM) was aborted, probably because of a time-out condition.

PCA persistant reservation table invalid.

A specific request to check the consistency between the FID and CM pages shows that an inconsistency exists.

Unable to read a word from either the head or PCA EEPROM.

A call to nvInvalidateTuningRevNo was made with an incorrect parameter.

General information about NVDS.

An invalid CRC over the Fatal Error page was found.

Not enough information was available to form a correct Unique Cartridge Identity.

nvSetPersonalityByte was asked to change the personality but this variant of code has a fixed personality.

nvSetPersonalityByte was asked to change the personality but the key provided did not allow this.

nvSetPersonalityByte was asked to change the personality but cannot change zero to non-zero or non-zero to zero.

A protected page table entry was attempted with an invalid page ID.

The Cartridge Content data page has a CRC error. The data is invalid.

An access to a non-existent Cartridge Content data page was attempted.

The requested field to be accessed does not exist in his version of the page.

86 Drive error codes

40CAh

40CBh

40CCh

40CDh

40CEh

40CFh

40D0h

40D1h

40D2h

40D3h

40D4h

40D5h

40D6h

40C0h

40C1h

40C2h

40C3h

40C4h

40C5h

40C6h

40C7h

40C8h

40C9h

Error

40B9h

40BAh

40BBh

40BCh

40BDh

40BEh

40BFh

Description

This product’s EEPROM configuration does not support the persistent storage for the Host Access table.

The persistent storage area for the Host Access table has never been written to and is therefore not initialized.

The persistent storage area for the device ID has never been written to and is therefore not initialized.

The persistent storage area for the device ID only supports storage for 2 LUNs—more has been requested.

A request to access an area of CM which is out of bounds has occurred. The access was disallowed.

Not enough information was available to form a correct Alternative Unique Cartridge Identity.

nvCMGetMechRelatedKAD() was asked to retrieve the KAD in the mechanism-related pages but not KAD has been stored.

The KAD length in the mechanism-related page which was asked to be stored or retrieved was too large.

The mechanism-related page has not been created (or the tape not loaded) so storage or retrieval of the KAD data is not allowed.

A request to access na STTF log idex was outside the permitted range.

The EEPROM does not contain previously saved snapshot event configuration data.

An access to a non-existent Suspended Append page was attempted.

An access to a non-existent Fatal Error page was attempted.

An access to a non-existent Mechanism Specific page was attempted.

An access to a non-existent Fatal Error page was attempted.

The Mechanism Specific page has a CRC error. The data is invalid.

nvCMGetMechSpecificKAD() was asked to retrieve the KAD in the Mechanism Specific page but no KAD has been stored.

The Mechanism Specific page has not been created (or tape not loaded,) so storage or retrieval of the KAD data is not allowed now.

The Certificate Storage table does not have an entry for the security parameter requested (in other words, it is not stored in the table).

The Certificate Storage table does not have a free slot to place the security parameter into.

An unknown security parameter was asked for.

The security parameter to be stored is too large to fit in the table.

This security parameter is not allowed to be cleared.

The Initialization check of the security table showed a bad CRC on the directory entries. The whole table must be cleared and rebuilt.

Mechanism table 8 is invalid.

The security parameter was encrypted, but the encrypted record size is too large for storage.

The KMS security parameter to be stored is too large to fit in the table.

The PCA2 EEPROM is not supported on this platform.

An unknown KMS security parameter was asked for.

The KMS security parameter was encrypted, however the encrypted record size ends up being too large for storage

Non-volatile data manager (from 4000h) 87

Error

40D7h

40D8h

40D9h

40DAh

40DBh

40DCh

40DDh

40DEh

40DFh

40E0h

40E1h

40E2h

40E4h

40E5h

40E6h

40E7h

Description

The Initialization check of the KMS security table showed a bad CRC on the directory entries. The whole table must be cleared and rebuilt.

The KMS Security table does not have an entry for the KMS security parameter requested (tha is, it is not stored in the table).

The Secure EEPROM storage will only allow encryption of field sizes divisible by 16, such as 16,

32, 48 and so on.

A Decrypt/encrypt operation has been attempted when the OTP Public key is empty.

The check of the Drives RSA Key Pair failed.

A multi-partition type of operation was requested but the cartridge has only been formatted as a single partition cartridge. The operation is invalid.

The transponder serial number check byte does not agree with the transponder serial number.

The reported LTO CM Mfr Info CM size is not valid.

The transponder type is not valid.

Operation requested a partition number not supported for this cartridge type.

Access to a non-existent application-specific page was attempted.

An attempt to read or write to the CM failed, however the drive status indicates that no tape was loaded, so this may be a spurious issue

Insert into the tape roller usage log came across an unknown licencee. No data has been inserted into the table.

The Encryption parameter to be stored is too large to fit in the allowed space.

The POST test to check the Mech pairing with the PCA has shown that the EEPROM has not been paired or has been tampered with.

The POST test to check the Head/Flex pairing with the PCA has shown that the EEPROM has not been paired or has been tampered with.

Operating system (from 4400h)

Error

4400h

Description

‘vGiveSem’ failed to signal a semaphore.

Physical formatter (from 4C00h)

Error

4C00h

4C01h

4C02h

4C03h

4C04h

4C05h

4C06h

4C07h

4C08h

Description

C1 has finished before C2 is ready for the dataset.

The physical formatter has been sent an invalid configuration name.

The physical formatter has been sent an invalid configuration value

C2 hardware is busy. The physical formatter C2 hardware is currently processing a dataset.

The physical formatter C2 control DS0 register go bit is set.

The physical formatter C2 control DS1 register go bit is set.

The physical formatter C1 control register go bit is set.

The physical formatter CCQ Reader control register go bit is set.

The physical formatter Read Chain Controller control register go bit is set

88 Drive error codes

501Eh

501Fh

5020h

5080h

5081h

5083h

5084h

5086h

5087h

Error

5000h

5001h

5002h

5003h

5004h

5005h

5008h

5009h

Error

4C09h

4C0Ah

4C0Bh

4C0Ch

4C0Dh

4C0Eh

4C0Fh

4C10h

4C11h

4C12h

4C13h

4C14h

4C15h

4C16h

4C17h

4C18h

Description

The physical formatter has been asked for the error rate log for a channel which does not exist

The physical formatter has been asked for the error rate logs for a channel which does not exist.

The physical formatter could not set the callback timer to enable the Hyperion read gate.

The physical formatter Read Chain Controller DS0 is stuck.

The physical formatter Read Chain Controller DS1 is stuck.

Physical formatter WP update.

Format other than LTO1 or LTO2.

SDRAM error has been detected.

The number of CCPs presented has fallen below the warning threshold.

A CCP has been overwritten.

A C2 error has been reported.

General physical formatter information.

Unexpected format complete signal arrived.

Check CCQ Write Rewrite log: param 1 = CCQSetsWritten, param2 = CCQSetRewrites, param

3 = pfStatus.

Number of CCPS have rolled over causing a reset of the Write Error Rate log.

Number of CCPS have rolled over causing a reset of the Read Error Rate log.

Physical pipeline control (from 5000h)

Description

EOD not found.

Black tape.

EOD encountered.

Undefined error.

The start LPOS of the dataset is before the LPOS of the previous dataset.

The start LPOS is more than 1 metre after the previous dataset.

Invalid configuration has been requested.

Abort reject continue not used.

Search in progress.

Mechanism command time-out; the control command never responded.

Command not allowed in this variant.

Invalid tape type.

The Error Rate Test has been aborted.

PF reported a write error (excessive RWWs).

PF reported a read error (C2).

PF reported a streamfail.

The error-rate test reached the C1 threshold.

Physical pipeline control (from 5000h) 89

Error

5088h

5089h

5091h

5092h

5093h

5094h

5095h

5096h

5097h

5098h

508Ah

508Bh

508Ch

508Dh

508Eh

508Fh

5090h

50A1h

50A2h

50A3h

50A4h

50A5h

50A6h

50A7h

50A8h

5099h

509Ah

509Bh

509Ch

509Dh

509Eh

509Fh

50A0h

50A9h

50AAh

50ABh

50ACh

90 Drive error codes

Description

Unknown notification. An unexpected mechanism control.

Data miscompare.

The drive has gone 4 metres since last dataset was reported.

The speed requested for ERT s out of valid range.

The notify for 4m give-up point is missing.

EOT was reached before requested datasets were written.

Start position requested for ERT s out of valid range

Cannot find the expected dataset number

Blank check. Could not read anything off the tape in the last 4 metres.

Too many datasets returned while flushing.

Could not find the target during a space operation.

Could not find the target ACN during a search operation.

Write Pass on write has been corrupted.

ERT read more datasets than expected.

Logical Media has supplied an invalid dataset index.

Dataset written before BOW.

EOT reached during reading.

Warning: Dataset flags non-zero.

EOD has been read, but is not the one in the Cartridge Memory.

The dataset that has been read should not be on this wrap.

The SPACE command is to a logical position that is beyond EOD.

The current cartridge cannot be written to —Write ERT is not allowed.

The dataset that was reported as C2 uncorrectable is considered good.

The DSIT contains an invalid UCI.

The drive has determined that the WORM data may have been tampered with.

The logical media has given a illegal dataset index for an append.

A search operation appears to have found the target too early.

An LTO-5 dataset was encountered whose encryption algorithm ID was not 01h.

The value of TapeWritePassValue CurrentWrap and SDL sheet has been set.

Shows the value that the Max ATS has been set.

An error code of 7501h (Loss of LPOS) has been detected, causing a reduction in the servo MR bias.

A RampToSpeedRsp signal has arrived while trying to abort.

Excessive offtracks have been seen on a Fuji tape.

The drive tried to perform an ERT whilst the tape was not threaded.

The firmware may have followed a path in which the formatter was not aborted before a re-write.

The firmware has managed to write a dataset that finishes past EOW.

An LTO-5 dataset was encountered whose Encryption Algorithm ID was not 02h.

Error

50ADh

50AEh

50AFh

Description

A call to an NVDS function returned with an unexpected error.

An LTO6 dataset was encountered whose Encryption Algorithm Id was not 0x03.

A dataset was started over 4M away from EOW but reached 4M giveup within 450 mm of EOW.

Physical side error recovery (from 5400h)

Error

5400h

5401h

Description

Not an error—just requests a trace log bank switch.

Shows the LPOS and MM position for the start of tuning.

Read/write control (from 5800h)

5807h

5808h

5809h

5810h

5820h

5821h

5822h

5823h

Error

5800h

5801h

5802h

5803h

5804h

5805h

5806h

5824h

5825h

5826h

5827h

5828h

5829h

5830h

5831h

5840h

5841h

Description

Success.

Null point.

Invalid parameter.

No hardware.

SPI transfer error.

Prometheus set error.

Hyperion set error.

Daughter set error.

Calibration did not complete.

Servo bias status false.

Wrong number of parameters.

Could not set Prometheus 0 to default values.

Could not set Prometheus 1 to default values.

Could not set Prometheus 2 to default values.

Could not set Prometheus 3 to default values.

A valid Mod level was not received from the PCA EEPROM.

Could not set Prometheus 4 to default values.

A failure was detected during a Write Element Resistance test for Artemis.

A failure was detected during a Read Element Resistance test for Apollo.

Artemis did not achieve PLL lock. Parameter 1 is Artemis (0=BumpA, 1=BumpB, FFh=No Artemis was specified). Parameter 2 is value of the Artemis PLL register.

Did not achieve PLL lock.

Could not set Hyperion 0 to default values.

Could not set Hyperion 1 to default values.

Could not initialize the Diagnostic Data rwInitDiagnosticData.

Did not get either INTODRIVE or INTOCARTRIDGE.

Physical side error recovery (from 5400h) 91

Error

5850h

5851h

5852h

5890h

5891h

5892h

5893h

5894h

5895h

58A0h

58A1h

58A2h

58AAh

58ABh

92 Drive error codes

585Dh

5860h

5861h

5870h

5871h

5880h

5881h

5882h

5853h

5854h

5855h

5856h

5857h

5858h

5859h

585Ah

585Bh

585Ch

Description

Delilah failed to autocalibrate.

Gideon failed to autocalibrate: param1 = GideonRegisters, param2 = RegisterValue, param3 = nothing.

Gideon HyperTransport PLL failed to come out of reset: param1 = GideonRegisters, param2 =

RegisterValue, param3 = nothing.

HyperTransport sync failure: param1 = bus, param2 = count, param3 = type.

HyperTransport parity failure: param1 = bus, param2 = count, param3 = type.

HyperTransport unexpected parity state at power-on: param1 = HT Parity Error, param2 = HT Parity

Error count 0, param3 = HT Parity Error count 1.

A valid Blo Dac Gideon Register setting could not be determined in the manual calibration mode.

The Mech Interface firmware returned a failure to RWC firmware when requested to set an ATS clock frequency for Gideon calibration.

The Random Bit Sequence generator failed to collect the required samples in the allowed time.

A valid Blo Dac Gideon register setting could not be determined in the manual calibration mode, retrying the Gideon offset calibration.

HT_ALIGN_FAILED HT_CONTROL bits 30:28 not set to 1.

HT_IN_UNEXPECTED_STATE HT reg is not as expected should be enabled.

T_TURNING_OFF_PARITY_CHECKING Stop checking HT parity otherwise the FW will eventually lock up.

HT_PARITY_ERROR_THRESHOLD_EXCEEDED Have had too many HT parity errors.

Expected a compatible data tape but got something else.

An invalid control word was found while parsing the Cal table to program a ASIC. Param 1 = control word, Param 2 = an integer value unique to each ASIC.

Could not write to Amundsen’s WEQ Control register.

Illegal WEQ setup requested.

The EEPROM calibration table area contains at least one invalid entry.

The Per Drive Cal table in the EEPROM contains one invalid entry.

The Per Drive Cal table in the EEPROM contains a revision number that is less than the revision number found in the base Cal table.

rwc_estimate_boost.

rwc_adjust_boost.

rwc_boost_datasets.

A request to reset the Afirs on the channel, Parameter1, was made to the RWC.

The drive will read using the alternate, or secondary, or writing, bump.

The drive will return to using the primary bump for reading.

The Write ERT operation executed as part of the FFIR calibration during load failed to complete enough datasets.

A channel ERT result has indicated that an FFIR tuning pass is required.

An FFIR calibration attempt at Load has failed. Bad status was returned from the ERT operation.

rwc_VIWP_TEMP_FAULT_ENTRY_A rwc_VIWP_TEMP_FAULT_ENTRY_B

Error

58ACh

58BAh

58BBh

58BCh

58CAh

58DAh

58F0h

58F1h

58F2h

58FFh

Description rwc_VIWP_TEMP_FAULT_ENTRY_C rwc_VIWP_VALUES rwc_VIWP_TEMP_CALCULATED_A rwc_VIWP_TEMP_CALCULATED_B rwc_RMATCH_VALUES rwc_MC_ADAPTION_CHANNEL_RESULT

Setup Servo.

SMUX.

BEN.

Undefined error.

System architecture (from 6400h)

Error

6401h

6402h

Description

Formatter ASIC revision check failed. The ASIC is not a LTO 1 Formatter ASIC.

The processor idle time is less than 30%.

Tight integ (from 6800h)

Error

6801h

6802h

6803h

Description

The Cmicro error handler function has been called (cm_ErrorHandler).

An implicit signal consumption has occurred.

No free SDL timer storage (in SDLTimerFreeList) to set new timer — increase MAX_SDL_TIMERS in TightInteg/cmTmr.c.

Trace logger (from 6C00h)

Error

6C00h

6C01h

6C02h

6C03h

6C04h

6C05h

6C06h

Description

TraceLogger initialization failed. BMM returned no good.

The last Live Trace entry has been reached. Not an error.

The drive has insufficient resources to set more Live Traces.

A flush has started and the initiator must wait to receive the SDL signal diTraceLogFlushed.

An operation has started but the caller must wait for the callback function to be executed.

The TraceLogging SysARM HW Flush All blocking function timed out.

The TraceLogging ServoARM HW Flush Trace channel blocking function timed out.

System architecture (from 6400h) 93

Mechanical interface (from 7400h)

7410h

7411h

7412h

7413h

7414h

7415h

7416h

7417h

7418h

7419h

741Ah

741Bh

741Ch

741Dh

741Eh

741Fh

7420h

Error

7400h

7401h

7402h

7403h

7404h

7405h

7406h

7407h

7408h

7409h

740Ah

740Bh

740Ch

740Dh

740Eh

740Fh

Description

No error.

Aborted command.

Unsupported command.

Wrong number of parameters.

Invalid parameter.

This command is already in progress.

This command is not allowed now.

Command processing error.

A DSP event has occurred (most likely an off-track event unless the default was changed).

The command is obsolete.

Incomplete initialization of the mechanism

There was a timing fault in the servo interrupt.

The mechanism type (SensorRev) specified in the mechanism EEPROM is either obsolete or unsupported.

Obsolete command 300C.

Obsolete command 300D.

Invalid task. The current task for the servo system is of an unknown type. This is most likely caused by a firmware bug.

A Load command is not allowed at this time.

An Unload command is not allowed at this time.

A shuttle tape command cannot be executed at this time.

A Set Cartridge Type command cannot be executed at this time.

A Set Mechanism Type command cannot be executed at this time.

A Set Tension command cannot be executed at this time.

A Set Speed command cannot be executed at this time.

An Adjust Speed command cannot be executed at this time.

A Set Position command cannot be executed at this time.

The Cancel Set Position command cannot be executed at this time. Most likely because there is no previous set position command active.

A Set Position and Speed command cannot be executed at this time.

A Servo Calibration command cannot be executed at this time.

An End of Tape Servo Calibration command cannot be executed at this time.

A Servo Initialization command cannot be executed at this time.

A Load Cartridge command cannot be executed at this time.

A Grab Leader Pin command cannot be executed at this time.

A Load and Grab leader pin command cannot be executed at this time.

94 Drive error codes

Error

7421h

7422h

7423h

7424h

7425h

7426h

7427h

7428h

7429h

742Ah

742Bh

742Ch

742Dh

742Eh

742Fh

7430h

7431h

7432h

7433h

7434h

7435h

7436h

7437h

7438h

7439h

743Ah

743Bh

743Ch

743Dh

743Eh

7441h

7442h

Description

An Ungrab Leader Pin command cannot be executed at this time.

An Unload cartridge command cannot be executed at this time.

A Thread command cannot be executed at this time.

An Unthread command cannot be executed at this time.

A Recover Tape command cannot be executed at this time.

A Head Clean command cannot be executed at this time.

A Power-on Calibration command cannot be executed at this time.

A Set Notify command cannot be executed at this time.

A Wait Until Event command cannot be executed at this time, probably because the tape is not moving.

A Set Head Position command cannot be executed at this time, probably because a servo calibration is in progress.

A Set Tracking Offset command cannot be executed at this time, probably because a servo calibration is in progress.

A DSP command to learn the VI offset is not allowed now because the tape is moving or another task is in progress.

The Set Gen command is not allowed now. The format cannot be changed at this time.

A Forced Eject command is not allowed at this time. Most likely another operation is in progress.

The command to try to unstick the tape from the head cannot be executed at this time.

Sensors are in a state that indicate that the sensors or Callisto is not working correctly.

Sensors are in a state that indicate that the sensors or Callisto is not working correctly on a load.

Sensors are in a state that indicate that the sensors or Callisto is not working correctly on a grab.

Sensors are in a state that indicate that the sensors or Callisto is not working correctly on an ungrab.

Sensors are in a state that indicate that the sensors or Callisto is not working correctly on an unload.

The RD sensor has stopped toggling, probably because the loader mechanism is blocked or the motor is not working.

It is unsafe to load the cartridge. A runaway condition of the FRM has been detected, probably because the tape is broken.

Unexpected LP on a grab. One (and only one) of the LP sensors has been asserted at the beginning of the grab.

Unexpected LP at the start of a grab. One (and only one) of the LP sensors has been asserted at the beginning of the grab. This is logged but not a failure.

The write protect sensor does not match the expected state.

The Cartridge Present sensor does not match the expected state.

Rotate reel command can not be executed at this time.

Measure Kt command can not be executed at this time.

The fault line on the FRM driver asserted while the reel was rotating.

The fault line on the BRM driver asserted while the reel was rotating.

Set Speed command cannot be executed because the tape is snapped.

Set Speed command cannot be executed because the tape is unthreaded.

Mechanical interface (from 7400h) 95

Error

7443h

7444h

744Fh

7450h

7451h

7452h

7453h

7454h

7455h

7456h

7445h

7446h

7447h

7448h

7449h

744Ah

7440h

7460h

7461h

7462h

7463h

7464h

7465h

7466h

7467h

7457h

7458h

7459h

745Ah

745Bh

745Ch

745Dh

745Fh

7468h

7469h

746Ah

746Bh

96 Drive error codes

Description

Set Position command cannot be executed because the tape is snapped.

Set Position command cannot be executed because the tape is unthreaded.

Set Position and Speed command cannot be executed because the tape is snapped.

Set Position and Speed command cannot be executed because the tape is unthreaded.

Adjust Speed command cannot be executed because the tape is snapped.

Adjust Speed command cannot be executed because the tape is unthreaded.

Servo Cal command cannot be executed because the tape is snapped.

Servo Cal command cannot be executed because the tape is unthreaded.

Callisto Bus test error.

In transit after initialization—no cartridge present.

In transit after initialization.

Ungrab after initialization.

Unknown after initialization.

Timed out waiting to send a command to get DSP head-cleaning information.

Timed out waiting for DSP response with head-cleaning information.

Timed out waiting to set up DSP for a head-cleaning command.

Timed out waiting for DSP response to head-cleaning setup.

Timed out waiting for DSP to complete the head-cleaning command.

Head-cleaning engagement time-out.

Head-cleaning parking time-out.

Head-cleaning cycling time-out.

The state of the sensor read at initialization are illegal. The results make no sense.

Timed out waiting to restore DSP after a head-cleaning command.

Timed out waiting for DSP during post-head-cleaning restoration.

Unable to send DSP compensator coefficients.

DSP download error.

Invalid DSP opcode error.

Unable to send a DSP command.

Unable to send a DSP seek command.

DSP failed to complete a seek command.

Send long-term DSP command time-out.

Send short-term DSP command time-out.

DSP long-term command protocol error.

DSP short-term command protocol error.

Too many parameters on DSP Long-term command.

Too many parameters on DSP Short-term command.

Too many results on DSP Long-term command.

Error

746Ch

746Dh

7475h

7476h

7477h

7478h

7479h

747Ah

747Bh

747Ch

746Eh

746Fh

7470h

7471h

7472h

7473h

7474h

7485h

7486h

7487h

7488h

7489h

748Ah

748Bh

748Ch

747Dh

747Eh

747Fh

7480h

7481h

7482h

7483h

7484h

748Dh

748Eh

748Fh

7490h

Description

Too many results on DSP Short-term command.

Long-term DSP command already in progress.

Short-term DSP command already in progress.

Long-term DSP command completed but not in progress.

Short-term DSP command completed but not in progress.

Unable to send a DSP Learn VI offset command.

DSP failed to complete a Learn VI offset.

Unable to send a DSP Calibrate VI command.

DSP failed to complete a Calibrate VI command.

Too many data points requested.

No scope data available from DSP

DSP failed to complete the command during the initialization process.

Unable to send DSP tuning parameters.

DSP failed to boot properly.

Time-out on sending the Clear DSP Fault log.

Time-out on completing the Clear DSP Fault log.

Unable to send DSP Head Clean command.

An abort command was requested while one is already in progress.

An abort command has timed-out while waiting for the tape to stop.

An Adjust Speed command was requested while one is already in progress.

General load failure.

EP sensor did not transition on a load, probably because no cartridge was present.

CD sensor did not transition on a load.

CG sensor did not transition on a grab.

LP sensor did not transition on a grab.

Too many retries to recover on a load or unload.

Cartridge not free to rotate when Cartridge Down.

The RD sensor stopped toggling while EP during a load.

The RD sensor stopped toggling while IT during a load.

The RD sensor stopped toggling while CD during a load.

The RD sensor stopped toggling while CD during a grab.

The RD sensor stopped toggling while LP during a grab.

Invoked tension ramp retry.

FRM runaway. Too much rotation was detected in the cartridge before it was threaded.

A grab was requested but the cartridge was not loaded.

Sensors indicate that the grabber unexpectedly moved into a grab position during a load operation.

While parking the LP, the LM voltage was increased from 0.25V to 0.5V.

Mechanical interface (from 7400h) 97

Error

7491h

7492h

74A3h

74A4h

74A6h

74A7h

74A8h

74A9h

74AAh

74ACh

7493h

7494h

7495h

749Ah

74A0h

74A1h

74A2h

74C7h

74C8h

74C9h

74CAh

74CBh

74CCh

74CDh

74CEh

74ADh

74C0h

74C1h

74C2h

74C3h

74C4h

74C5h

74C6h

74CFh

74D0h

74D1h

74D2h

98 Drive error codes

Description

While parking the LP, the LM voltage was increased from 0.5V to 0.75V.

While parking the LP, the LM voltage was increased from 0.75V to 1.0V.

While threading, the LM voltage was increased from 0.25V to 0.5V.

While threading, the LM voltage was increased from 0.5V to 0.75V.

While threading, the LM voltage was increased from 0.75V to 1.0V.

Load command failed and no CM was detected, therefore it is likely there is no cartridge present.

General unload failure.

EP sensor did not transition while unloading.

CD sensor did not transition while unloading.

CG sensor did not transition while ungrabbing

LP sensor did not transition while ungrabbing

RD sensor stopped toggling while CG during ungrab.

RD sensor stopped toggling while LP during ungrab.

RD sensor stopped toggling while CD during ungrab.

RD sensor stopped toggling while CD during unload.

RD sensor stopped toggling while IT during unload.

Too much rotation of the cartridge was detected while the tape was not threaded.

The load, unload, grab or ungrab operation timed out.

Time-out while deslacking the cartridge.

Emergency stop error.

Already past target position.

Set speed time-out error.

Time-out waiting for an LPOS.

Reels not synchronized.

Safety limit stop reached.

LPOS calculation with invalid LP0.

Missed target position.

Previous tape motion command in progress.

Set Speed timeout error.

Unthreading time-out error.

Remove slack process timed-out.

Leader may have disconnected.

Time-out waiting for radii estimate.

Radii estimation process failed.

Recover tape time-out error.

Invalid cartridge type.

Cal reel driver offset time-out.

Error

74D3h

74D4h

74D5h

74D6h

74DDh

74DEh

74DFh

74E0h

74E1h

74E2h

74E3h

74E4h

74E5h

74E6h

74E7h

74D7h

74D8h

74D9h

74DAh

74DBh

74DCh

7500h

7501h

7502h

7503h

7504h

7505h

7508h

7509h

750Ah

750Bh

750Ch

750Dh

750Eh

750Fh

Description

Time-out waiting for the specified event.

Front-reel motor hall sensor fault.

Back-reel motor hall sensor fault.

The deslacking process timed out and did not complete, probably because the back reel motor failed to rotate.

Threading time out while waiting for half moon to pass the first roller.

Timed out waiting for tape to reach position for speed-up during a thread.

Time out while waiting for tape to reach the position to stop threading.

An unthread command was issued and aborted a tape motion operation that was already in progress.

The cartridge type has not been specified either from LTO-CM or through a serial port command.

The tape speed reported by the DSP is significantly different from the tape speed indicated by the hall sensors.

Specified value of tension is either too high or too low.

The panic stop process timed out and did not complete properly.

Timed-out waiting for the proper tape tension to be established.

Head selection time-out.

Unable to position the head.

Speed too low for enabling the heads.

Speed too low for the head servo.

Speed too low for sensor calibration.

A DSP seek command was attempted while the tape speed was zero.

DSP sensor calibration command was attempted while the tape speed was zero.

The speed is too low to attempt a VI offset command in recover tape. Most likely the tape is stuck to the head.

First write fault.

Write fault: it has been too long since a valid LPOS was read, so writing is not allowed.

Write fault: DSP tracking recovery operations are in progress so writing is not allowed.

Write fault: tape motion start-up operations are incomplete so writing is not allowed.

Write fault: DSP is not tracking properly on the tape, writing is not allowed.

Write fault: the current tape speed is too low so writing is not allowed.

Write fault: ATS clock frequency clipped, or DSP in idle mode.

Write fault: DSP calibrating.

Write fault: DSP VI track follow.

Write fault: DSP tape off-track.

Write fault: DSP demod channel out.

Write fault: DSP seek.

Write fault: DSP uPVI.

Write fault: write unsafe.

Mechanical interface (from 7400h) 99

Error

7510h

7511h

7600h

7601h

7602h

7603h

7604h

7605h

7606h

7607h

7512h

7513h

7514h

7515h

7516h

7517h

75BBh

7610h

7611h

7612h

7613h

7614h

7615h

7616h

7620h

7608h

7609h

760Ah

760Bh

760Ch

760Dh

760Eh

760Fh

7621h

7622h

7623h

7624h

100 Drive error codes

Description

Unknown write fault.

Multiple write faults.

Last write fault.

Write is not allowed; a power-on or reset occurred.

Write is not allowed; a micro-jog is being applied.

Write fault last.

Write is not allowed; 12V power has been lost.

Write fault last.

Write cannot recommence while still offtrack.

Set Speed command invalid parameter.

Adjust Speed command invalid parameter.

Set Position command invalid parameter.

Set Head Position command invalid parameter.

Set Head Table command invalid parameter.

DSP Statistics command invalid parameter.

Get Servo Fault command invalid parameter.

Set Tracking Offset command invalid parameter.

Set Notify command invalid parameter.

Clear Notify command null handle.

ATS Diagnostics command invalid parameter.

Hall Calibrate command invalid parameter.

Radius Calibrate command invalid parameter.

Wait Until Event command invalid parameter.

Convert LPOS command invalid parameter.

Shuttle command invalid parameter.

Get DSP fault log invalid parameter.

Set General Command Invalid parameter.

Set TestMode command parameter is out of range or is invalid.

EEPROM servo table command parameter is out of range or is invalid.

Rotate command — invalid parameter.

Measure Kt command — invalid parameter.

Sleep Recursion fault in MechInterface.

Set speed operation timed out during a recover tape command.

Timed out waiting for the pin sensors to indicate almost parked.

Timed out waiting for the pin sensors to indicate fully parked.

An unthread timed out waiting for the full leader pin seating tension to be established.

Cycling the pull-in tension did not achieve pin-park.

7640h

7641h

7642h

7643h

7644h

7645h

7646h

7647h

7638h

7639h

763Ah

763Bh

763Ch

763Dh

763Eh

763Fh

7648h

762Dh

762Eh

762Fh

7630h

7631h

7632h

7633h

7634h

7635h

7636h

7637h

Error

7625h

7626h

7627h

7628h

7629h

762Ah

762Bh

762Ch

Description

Rethreading and then unthreading again did not get the leader pin parked.

Timed out during the rethread/re-unthread recovery while waiting for almost parked.

All recovery algorithms have been exhausted and still unable to park leader pin.

Rethread recovery operation timed out waiting for the tape to come to a stop.

Rethreading timed out while waiting for the tape to reach the required position.

Deslacking process did not complete., probably because the back reel motor failed to rotate.

The leader pin was parked as indicated by both LP sensors but then came unparked.

The tape has been recovered and leader pin parked but the original operation failed and was abandoned.

Rethreading timed out while waiting for the tape to reach the required position.

Rethread recovery operation timed out waiting for the tape to come to a stop.

A special unthreading recovery operation was needed to un-jam the leader block.

An iteration of the special unthreading recovery operation did not succeed.

The stop tape operation took longer than expected.

An attempt was made to stop the tape while still too far away from the specified position.

An abort command was issued and stopped the tape motion operation that was already in progress.

The tape thickness is too great to be handled properly by the servo system.

An ATS speed change operation (AdjustSpeed) timed out waiting for tape to reach target speed.

An ATS speed change operation (AdjustSpeed) was attempted while the tape was not moving.

While trying to park the pin, LP2 was seen, but LP1 was not seen after rotating the grabber CCW.

Threading timed out while waiting for the half moon to seat onto the back reel.

Tape motion apparently stopped while waiting for head positioning to complete.

Unthread timed out during the initial rewind of tape back into the cartridge.

Timed out during an operation to set tape position and speed.

Timed out during an operation to set the tape position.

Timed out during a RecoverTape operation.

The front reel did not rotate during the tape slack removal process.

Timed out waiting for back reel to reach position where leader block is fully seated.

Timed out waiting for back reel to rotate to the threading reversal point.

Timed out waiting for back reel to rotate to the reverse threaded position.

Timed out waiting for tension to be established during the reverse threading process.

Timed out waiting for the reverse threading target position.

Timed out waiting for leader block to detach during an unthread.

Timed out waiting for tension to be established during the reverse unthreading process.

Timed out waiting for speed to be established during the reverse unthreading process.

A fatal reel fault occurred during the time when the tape was being stopped.

Back reel stalled and was not rotating when determining thread direction.

Mechanical interface (from 7400h) 101

7656h

7657h

7658h

7659h

765Ah

765Bh

765Ch

765Dh

7650h

7651h

7652h

7653h

7654h

7655h

765Eh

765Fh

7660h

7661h

7662h

7663h

7664h

7665h

7666h

7667h

Error

7649h

764Ah

764Bh

764Ch

764Dh

764Eh

764Fh

7668h

7669h

Description

An operation that determines thread direction timed out.

Warning: Tape speed error integrator value is very large.

Timed out waiting for back reel to rotate to the unthreading reversal point.

Timed out waiting for tape to reach unthreading reversal slow down point.

Timed out waiting for tape to reach unthreading turn around point.

Front reel turning CCW but should be CW after going through critical point during recover tape process.

Tape motion unexpectedly stopped during recover tape process of rewinding based on radius estimate.

Unable to detach leader block during recover tape operation when reverse threaded.

Unable to detach leader block during recover tape operation when forward threaded.

Unable to identify cartridge type during recover-tape operation.

The tape thickness reported by the Cartridge Memory is too large or too small.

The tape thickness reported by the CM is invalid and cannot be used.

The full pack radius reported by the CM appears to be invalid and will not be used.

The tape length reported by the CM appears to be invalid and will not be used.

The empty reel inertia reported by the CM appears to be invalid and will not be used.

The empty reel radius reported by the CM appears to be invalid and will not be used.

The front reel is not rotating properly. It is possible that some tape was spilled out from the back reel.

Recovery process was unable to determine the best direction in which to move the tape.

Front reel did not reverse direction after passing through the critical region for threading reversal.

Back reel did not stop as expected during a tape recovery process.

Warning: Leader block demate process resorted to pushing the back reel clockwise.

Rethreading position time-out during the leader block demate retry process.

Leader block demate retry process was unsuccessful.

It was necessary to tug the tape to detach the leader block.

Timed out waiting for the required number of layers to overwrap the leader block.

Timed out waiting for the tape to unwrap from the leader block during a reverse thread.

Timed out waiting for a return to the original lock-in position during a reverse thread.

DSP tuning parameters were reloaded into the DSP before a VI-sensor calibration command. This is a recovery algorithm.

A special test mode has been enabled that will generate specific faults.

The special test mode has now been disabled. Normal operation will resume.

The front reel is not running in the reverse direction after the tension ramp after passing through the critical region during a thread.

The front reel did not reverse direction after passing through the critical region during an unthread, step 1.

The front reel did not reverse direction after passing through the critical region during an unthread, step 2.

102 Drive error codes

7675h

7676h

7677h

7678h

7679h

767Ah

767Bh

767Ch

767Dh

767Eh

Error

766Ah

766Bh

766Ch

766Dh

766Eh

766Fh

7670h

7671h

7672h

7673h

7674h

7687h

7688h

7689h

768Ah

768Bh

767Fh

7680h

7681h

7682h

7683h

7684h

7685h

7686h

Description

Timed out waiting for speed to reduce while approaching the critical region during a thread.

Recovery process is using a secondary head set to perform a sensor calibration operation.

Recovery process is using a secondary head set to perform an azimuth calibration operation.

Servo calibration cannot be done now because it is too close to BOT.

Timed out waiting for half moon to approach head during a thread.

Timed out waiting for half moon to approach head during an unthread.

Timed out waiting for half moon to pass head during a thread.

Timed out waiting for half moon to pass head during an unthread.

Timed out waiting for half moon to enter guide during an unthread.

Servo timing reference mismatch during timing reference calibration

Set position and speed operation missed the target objectives by too much, probably due to DSP retries.

Timed out waiting for the grabber to rotate enough to deactivate the tape lifter and lower the tape onto the head

Cartridge Memory read after threading; mechanism parameters cannot be updated at this time.

Mechanism sensors not in the expected state after a load command.

Mechanism sensors not in the expected state after an unload command.

Mechanism sensors not in the expected state after a grab command.

Mechanism sensors not in the expected state after an ungrab command.

Deslacking process did not complete, probably due to the back reel motor failing to rotate.

FRM tension ramp process did not complete, probably due to excessive tape slippage in the cartridge.

FRM rotation was unexpectedly detected while ungrabbing the cartridge leader pin.

The calculated LPOS media manufacturers string checksum does not match what was read from the tape.

The LP sensor was asserted before loading, possibly because of a stuck or faulty sensor

The DSP was commanded to re-lock onto servo code. (This is a recovery algorithm.)

A retry was necessary on a DSP seek command. (This is a recovery algorithm.)

A retry was necessary on a DSP VI-sensor cal command. (This is a recovery algorithm.)

A retry was necessary on a DSP azimuth cal command. (This is a recovery algorithm.)

A retry was necessary on a DSP command to learn the VI-offset. (This is a recovery algorithm.)

Unable to thread. An ungrab/regrab/rethread recovery process will now be attempted.

The thread operation is being retried because the pin detect sensor indicates parked when not parked.

The threading recovery could not get the tape stopped in a reasonable time period.

Timed out waiting for a regrab to complete before threading.

Timed out trying to read the media manufacturer’s information.

A faulty LP sensor has made it necessary to detect pin parking via FRM stall.

Attempt to park failed. An LP sensor was most likely asserted when it should not have been.

Mechanical interface (from 7400h) 103

Error

768Ch

768Dh

7695h

7696h

7697h

7698h

7699h

769Ah

769Bh

769Ch

768Eh

768Fh

7690h

7691h

7692h

7693h

7694h

769Dh

769Eh

769Fh

76A0h

76A1h

76A2h

76A3h

76A4h

76A5h

76A6h

76A7h

76A8h

76A9h

76AAh

76ABh

76ACh

76ADh

76AEh

76AFh

76B0h

104 Drive error codes

Description

A VI cal was necessary to recover a DSP seek command failure. (This is a recovery algorithm.)

The FRM driver required a reset and was restarted. This is not a fault.

The BRM Driver required a reset and was restarted. This is not a fault.

The reel motor flex continuity check failed, the line is stuck high.

The reel motor flex continuity check failed, the line is stuck low.

Unable to read the media manufacturers information from the LPOS bit stream.

A full eject was invoked as part of a load fault recovery.

Gently nudged grabber in order to help park leader pin. Information only, not a fault.

Leader pin may have come ungrabbed. Regrabbing pin.

A cartridge load as part of init failed.

A special recovery to try to free a stuck LP sensor is in progress.

The recovery effort to try to free a stuck LP sensor failed.

The BRM over rotated during leader block demate in recover tape. Info only.

The front reel motor DAC offset is too large or too small.

The back reel motor DAC offset is too large or too small.

A forced eject command was invoked. This is not a fault.

The LPOS lock-up process 1 produced a value that does not pass the basic sanity check.

The LPOS lock-up process 2 produced a value that does not pass the basic sanity check.

The removing slack operation timed out while trying to determine the best direction for recovery.

The radii estimation process in recover tape yielded a negative result.

Unable to send a DspSetGen command.

Failed to complete a SetGen command.

Empty Dsp interrupt.

Time-out during ReadDspFaultLog.

Time-out during ClearDspFaultLog.

Unable to send a DspWriteDataMem command.

Dsp failed to complete a WriteDataMem command.

Unable to send DSP sample rate parameters.

A threading fault has occurred.

An unthreading fault has occurred.

Unable to send CSP PCA diagnostic command.

DSP failed to complete PCA diagnostic command.

Unable to initiate tape motion. The tape is stuck.

Unable to initiate tape motion even after using the tape lifter. The tape is stuck.

Unable to initiate tape motion even after relaxing hard pull. The tape is stuck.

The tape speed error integrator value is very large. The tape is stuck and not moving.

Unable to initiate tape motion even after pulling in the opposite direction. The tape is stuck.

76C2h

76C3h

76C4h

76C5h

76C6h

76C7h

76C8h

76C9h

76CAh

76CBh

76CCh

76CDh

76CEh

76CFh

76D0h

76D1h

76D2h

76D3h

76BCh

76BDh

76BEh

76BFh

76C0h

76C1h

76B6h

76B7h

76B8h

76B9h

76BAh

76BBh

Error

76B1h

76B2h

76B3h

76B4h

76B5h

Description

The tape finally came free after pulling in the opposite direction.

Unable to read enough valid LPOS words from any servo head to determine LP0S.

Switching to a different speed or different head as part of a Servo Cal retry and recovery process.

This fault code is for firmware debug only. It simulates a DSP fault code.

Relaxed grabber during thread to help pull leader pin out of cartridge. This is for information only; it is not a fault.

An Orion command returned more results than the maximum allowed.

The servo ASIC interrupted the system processor for no good reason.

The LPOS lock-up process produced a value that does not pass the basic sanity check.

The LPOS lock-up process produced a value that does not pass the basic sanity check.

RecoverTape completed successfully. This is for information only; it is not a fault.

An Orion command was sent with more than the maximum number of parameters allowed.

Hardware detected offtrack. This is for information only.

The servo ARM reported an unexpected reset.

No Orion command mailboxes were available

The write-protect sensor does not match the specified high state.

The write-protect sensor does not match the specified low state.

EEPROM values unavailable. Invalid table revision. Default servo tuning values are being used instead.

EEPROM values unavailable. Invalid table revision. Default values are being used instead.

The drive is not in the correct state to allow the power mode to be changed.

The power mode requested is invalid.

The cooling fan is stalled or running significantly below normal operating speed.

The cooling fan was stalled but is now operating normally.

A servo ARM memory parity error was detected. The drive must be reset.

A servo ARM memory parity error was detected. The drive must be reset.

A servo ARM memory parity error was detected. This is for information only.

A servo ARM memory parity error was detected. The drive must be reset.

Mechanism Inetrface resetting the drive. A fatal servo ARM memory parity error was detected.

The servo ARM did not respond within the allotted timeout, shutting down the actuator motor.

The drive is LOAD inhibited. The reel driver offset is out of range. Loading a tape would put it at risk.

Deceleration to the head turn-off speed took longer than expected.

An AdjustSpeed command was terminated early because ATS mode was enabled.

Change to reel tuning parameters not allowed at this time.

Tape Position indicated via LPOS does not agree with Tape Position via Halls.

The speeds indicated by the reels do not agree with each other.

Speed fault when reels are being controlled in special reel servo mode.

Mechanical interface (from 7400h) 105

Error

76D4h

76D5h

76DDh

76DEh

76DFh

76E0h

76E1h

76E2h

76E3h

76E4h

76D6h

76D7h

76D8h

76D9h

76DAh

76DBh

76DCh

76E5h

76E6h

76E7h

76E8h

76EFh

76F0h

76F1h

76F2h

76F3h

76F4h

76E9h

76EAh

76EBh

76ECh

76EDh

76EEh

76F5h

76F6h

76F7h

106 Drive error codes

Description

An ATS command cannot be executed at this time.

Unable to pull in all the slack tape after the front reel stalled during a RecoverTape operation.

Front reel stalled and all retries have been exhausted.

Timed out while rotating back reel to confirm slack tape was removed.

Back reel stalled during process to confirm slack tape was removed.

Successfully recovered from when the front reel stalled.

A new tape lifter operation was attempted before the previous tape lifter operation completed.

A tape lift operation was attempted while a previous tape drop operation was still in progress.

A tape drop operation was attempted while a previous tape lift operation was still in progress.

Tape lifter target state is not valid. The operation cannot be completed.

Tape lifter did not drop the tape onto the head within the allotted time.

Tape lifter did not lift the tape off the head within the allotted time.

A tape lifter operation was requested prior to the mech mode being grabbed.

The tape lifter diag command timed out waiting for motion to complete.

Timed out waiting for the tape lifter to lift the tape off the head.

Timed out waiting for the tape lifter to drop the tape onto the head.

CG sensor not seen during pin parking grabber sweep.

Initial attempt to park the pin failed. Retrying with a larger grabber motion.

The fault line on the reel motor driver asserted during driver offset nulling.

The tape lifter did not drop the tape onto the head quickly enough.

The reel motor flex connection is suspect; the dataset field in the fault log indicates which lines are in error.

Tape tilt calibration failed. Drive write inhibited.

EEPROM values unavailable. Default DSP servo compensator values are being used.

The drive has cooled and the cooling fan has been turned off.

The drive is getting too hot and the cooling fan has been turned on.

The drive has cooled; resuming normal tape speeds.

The drive is getting too hot; tape speed is now being reduced to a minimum.

ASIC temperatures are too high. Operations must stop and the cartridge must be ejected.

The address into the main DRAM buffer must be on an even byte boundary.

The address into the main DRAM buffer is outside the range allowed for the servo system to use.

The specified mode is not valid.

The specified scope channel bit width is not supported.

The specified scope trigger position is too large compared to the specified number of data packets in the trace.

The length of the buffer must be larger than zero and an even number.

The specified source number is not valid.

The specified scope buffer format parameter is not valid.

7707h

770Fh

7710h

7711h

7712h

7720h

7730h

7740h

7741h

7708h

7709h

770Ah

770Bh

770Ch

770Dh

770Eh

7743h

7746h

7747h

774Bh

Error

76F8h

76F9h

76FAh

76FBh

76FCh

76FDh

76FEh

76FFh

7700h

7701h

7702h

7703h

7704h

7705h

7706h

Description

A reel driver calibration factor is out of range.

A reel driver calibration factor for static torque loss is out of range.

A reel driver calibration factor for dynamic torque loss is out of range.

The temperature is above the maximum limit.

The temperature is below the minimum limit.

EEPROM values are unavailable. The default servo tuning values are being used instead.

Previous fault conditions have made it unsafe to thread this cartridge.

The tape temperature is too high. Operations must stop and the cartridge must be ejected.

The base number for constructing DSP error codes. This is not an actual error.

DSP fault: TMS320 was just reset due either to hardware pin assertion or receipt of the Reset command.

DSP fault: the DSP checksum failed after a hardware/software reset.

DSP fault: unsupported command opcode

DSP fault: illegal command sequence.

DSP fault: the Alert bit was set during a seek or CalibrateVI command.

DSP fault: the DSP was asked to do a tape seek when the microprocessor said this was not a safe operation to do.

DSP fault: a seek or VI calibration command was issued but the mechanism has not learned the VI offset yet.

DSP fault: the stroke measured by the VI sensor hardware was not large enough.

DSP fault: excessive actuator power amp offset.

DSP fault: main memory microprocessor time-out.

DSP fault: the tracking PLL in the servo front end did not lock up at power up. Info only.

DSP fault: the servo firmware was sent a command it could not interpret .

DSP fault: no timers were available for use in the servo firmware.

DSP fault: spare

DSP fault: spare

DSP fault: unable to find a top servo band.

DSP fault: unable to lock to track 0 on a top servo band.

DSP fault: unable to verify band ID on a top servo band.

DSP fault: the track-following loop could not stay at the desired set point.

DSP fault: could not stay locked to the tape servo code.

DSP fault: no tape servo data during seek acceleration phase.

DSP fault: acceleration time-out fault.

DSP fault: no tape servo data during the seek deceleration phase.

DSP fault: seek failure during VI gross settle.

DSP fault: seek failure during tape gross settle.

DSP fault: no tape servo data during seek fine settle phase.

Mechanical interface (from 7400h) 107

Error

774Ch

774Dh

7750h

7751h

7752h

7753h

7754h

7755h

7756h

Description

DSP fault: too few samples to generate an azimuth correction.

DSP fault: too few samples to generate a valid timing reference.

MI task was awakened for no apparent good reason.

Orion trace port FIFO not empty when preparing to hibernate.

The RD sensor stopped toggling while IT during a head clean.

The FRM Driver could not be enabled because the DACs are disabled.

The BRM Driver could not be enabled because the DACs are disabled.

12V power has been lost.

A catastrophic servo fault occurred.

Exception handler (from 7800h)

Error

7800h

7801h

7802h

Description

Unrecognized exception.

A Fatal assert has been seen. Parameter 1 shows the PC, parameter 2 the error code for the assert.

A Logged assert has been called. Parameter 1 shows the PC, parameter 2 shows the File ID, parameter

3 the line number.

An assert has been called. Parameter 1 shows the PC.

7803h

SPI interface (from 7C00h)

Error

7C01h

7C02h

7C10h

7C11h

7C12h

Description

Buffer overflow.

Time-out error.

EEPROM write did not complete. It is still in progress.

Flash write did not complete.

Flash read did not complete.

Cartridge Memory (from 8000h)

Error

8000h

8001h

8002h

8003h

8004h

8005h

8006h

8007h

Description

Address out of limits.

SPI writing problems.

Wrong number of bits returned.

Nack error.

Unrecognized data received.

SPI reading problems.

Parity error.

Collision error.

108 Drive error codes

Error

8008h

8009h

800Ah

800Bh

800Ch

800Dh

800Eh

800Fh

8010h

8011h

8012h

8013h

8014h

8015h

Description

Overflow error.

Underflow error.

Overflow error on sending.

Number of bits on data receive error.

Impossible address situation.

Invalid configuration name.

Invalid configuration value.

CRC error.

The serial number check failed.

Error bit set.

Type of transponder not recognized.

RF channel already opened.

RF channel already closed.

EOT polled to.

Fault log manager section (from 8400h)

8406h

8407h

8480h

8481h

8482h

8483h

8484h

8485h

8486h

8487h

8488h

8489h

848Ah

Error

8400h

8401h

8402h

8403h

8404h

8405h

Description

Log not yet implemented.

No more entries to extract.

Uninitialized NV logs.

An SPIXferRequest failed.

Some fault entries were not placed in the log due to flushing occurring.

The size of operation of an entry is different to what the logging system expects.

A tape has been loaded and the fault log entry shows the load count and cartridge serial number.

The requested operation cannot be performed at this time as a flush to NV is currently in progress.

A snapshot change is not allowed because a snapshot is currently in progress.

A request to read a snapshot log failed because the requested log number does not exist.

Snapshotting is not allowed now as one or more preconditions have not been passed.

A request to stop reading a log found the log was not being read in the first place.

An attempt was made to insert too many CDBs for snapshotting.

The end of the snapshot command set has been reached.

An attempt was made to access the log snapshot command set while it is being updated.

A snapshot command requested more SCSI data (out) than was available.

The SCSI infrastructure requested a snapshot PortIF operation with an invalid/obsolete TaskPtr.

The specified snapshot log is unavailable because it is being filled or created.

The specified snapshot log is unavailable because it is being read.

Fault log manager section (from 8400h) 109

Error

848Bh

848Ch

848Dh

848Eh

848Fh

8490h

8491h

Description

The specified snapshot log is unavailable because its status is unexpected.

The command set cannot be changed while it is being read.

The data structure that contains status has an illegal value.

The specified snapshot LogSize is too small.

No task objects are available in the SCSI Task Manager.

The Snapshot log sub-system is unable to save a snapshot log to flash because it is full.

An operation was attempted that cannot be performed because there are protected STTF logs in flash.

Infrastructure section (from 8800h)

8809h

880Ah

880Bh

880Ch

880Dh

880Eh

880Fh

8810h

8811h

8812h

8813h

Error

8800h

8801h

8802h

8803h

8804h

8805h

8806h

8807h

8808h

8814h

8815h

8816h

8817h

8818h

Description

Inf OnEvent: EventSet – the event list is full, so the event has not been set.

Inf OnEvent: the event has not been found in the list.

Inf OnEvent: EventGetIdx – the index is out of bounds.

Inf ARM exception vector taken: undefined instruction.

Inf ARM exception vector taken: software interrupt.

Inf ARM exception vector taken: prefetch abort.

Inf ARM exception vector taken: data abort.

Inf ECC event: recoverable ECC error detected.

Inf ECC event: unrecoverable ECC error detected.

Inf Boot failure: firmware image failed to boot.

The ACI_RST_L input on the ACI connector has been activated.

Inf ECC event: Recoverable ITCM ECC error detected.

Inf ECC event: Recoverable DTCM ECC error detected.

Inf the System ARM is about to enter DiagLite.

Inf the True Random Number Generator's init routine failed at the start.

Inf the True Random Number Generator's BIST never completed.

Inf the True Random Number Generator's BIST SIG never became non-zero.

Inf the True Random Number Generator has failed to re-seed.

Inf the True Random Number Generator has failed to fill its cache.

RTKCritIntSectBeg() has detected that we are in a nested critical section but interrupts are enabled when they should not be.

FUG flash write and reads succeeded, but a subsequent compare failed.

The True Random Number Generator's init routine failed to reset.

The True Random Number Generator's logic self-test failed.

The True Random Number Generator's entropy source logic test failed.

The True Random Number Generator has timed out waiting for initialization.

110 Drive error codes

Error

8819h

881Ah

881Bh

Description

The True Random Number Generator's continuous test has failed.

The True Random Number Generator has no data available to read.

The SysARM Watchdog Timer has fired. This indicates that the SysARM FW has locked up.

Critical section (from 8C00h)

Error

8C00h

8C01h

Description

End section not begun. CRSEndCritIntSect was ended without CRSBegIntSect.

Begin section ints off. CRSBegCritIntSect found ints already off.

SCSI module (from 9400h)

9414h

9415h

9416h

9417h

9418h

9419h

941Ah

940Bh

940Ch

940Dh

940Eh

940Fh

9410h

9412h

9413h

Error

9401h

9402h

9403h

9404h

9405h

9406h

9407h

9408h

9409h

940Ah

Description

Power-on reset Unit Attention.

Firmware reboot after upgrade Unit Attention.

SCSI bus reset Unit Attention.

BDR reset Unit Attention.

Soft reset Unit Attention.

Transceivers changed to SE Unit Attention.

Transceivers changed to LVD Unit Attention.

Nexus lost Unit Attention.

Media changed Unit Attention.

Mode parameters changed Unit Attention.

Log values changed Unit Attention.

Unsupported task management function.

LUN has too many task objects.

Unsupported LUN.

Invalid field in CDB.

Unsupported opcode.

Unsupported command handler request.

Unavailable opcode.

Not a fast ACI command.

Response pending.

Aborted.

Reserved.

Invalid group code.

Truncated mode page.

Invalid field mode data.

Critical section (from 8C00h) 111

Error

941Bh

941Ch

9424h

9425h

9426h

9427h

9428h

9429h

942Ah

942Bh

941Dh

941Eh

941Fh

9420h

9421h

9422h

9423h

9434h

9435h

9436h

9437h

9438h

9439h

943Ah

943Bh

942Ch

942Dh

942Eh

942Fh

9430h

9431h

9432h

9433h

943Ch

943Dh

943Eh

943Fh

112 Drive error codes

Description

BOT encountered on space to record.

BOT encountered on to space to filemark.

Firmware bug.

Echo buffer overwritten.

REPORT DENSITY media not present.

Overlapped command.

Erase operation in progress.

Locate operation in progress.

Rewind operation in progress.

Write inhibit tape drive.

Device ID changed Unit Attention.

Truncated Log data.

Non-clearable Log page.

Invalid field Log data.

Forward task to library. Not a reportable error code.

Invalid surrogate SCSI LUN.

Invalid surrogate SCSI inquiry pages.

Too many surrogate SCSI LUNs.

Inquiry cache corrupted.

Inquiry cache full.

Invalid Exchange ID.

No sense data provided.

Invalid SCSI status.

Reported LUNs data has changed Unit Attention.

Parameter not supported in CDB.

Load operation in progress.

Unload operation in progress.

Early Warning EOM encountered.

Invalid field in Write buffer descriptor.

Prediction threshold exceeded false failure.

Prediction threshold exceeded failure.

Echo buffer invalid.

LUN not configured.

Invalid field in PR Out data.

PR Out parameter list length error in CDB.

PR Out truncated data.

Reservations released Unit Attention.

945Ah

945Bh

945Ch

945Dh

945Eh

945Fh

9460h

9461h

9462h

9463h

9464h

Error

9440h

9441h

944Ah

944Bh

944Ch

944Dh

944Eh

944Fh

9450h

9451h

9442h

9443h

9444h

9445h

9446h

9448h

9449h

9452h

9453h

9454h

9455h

9456h

9457h

9458h

9459h

Description

Registrations preempted Unit Attention.

Reservations preempted Unit Attention.

Invalid release persistent reservation.

WORM overwrite attempted.

WORM cannot erase.

Drive cleaning in progress.

Loading media.

Unloading media.

Firmware upgrade in progress.

Cartridge is write-protected.

Writing inhibited, caused by bad Cartridge Memory.

Unknown cartridge loaded but not threaded.

Tape is loaded but not threaded, initialize command is required.

MAM is accessible but the cartridge is in load ‘hold’ position — not ready.

The tape is threaded but the drive shows it as unloaded.

No media loaded.

An invalid Port ID has been logged in.

The RMC logical unit has been taken offline by the ADC RMC Logical Unit Mode page.

Write inhibit—the media is the wrong generation.

Tape position is past BOM.

No default WWN. Used by the WWN module.

No current WWN. Used by the WWN module.

WWN not changed.

No default value for the WWN. Used by the WWN module.

Insufficient registration resources. Used in Fibre Channel when the maximum number of WWN has been reached.

Library check condition surrogate SCSI command. Used in surrogate SCSI to cause the siSetScsiStatus to set task SCSI status to 2.

Write inhibit caused by suspect integrity.

Busy command during LU Reset. This command should receive BUSY during the resetting of the LU.

Operation complete.

The maximum number of bridge LUNs has been reached.

Unit Attention condition has been detected for this initiation to the SMC LUN.

The remote SMC device server is in the Not Ready state.

The Bridging Mode Sense cache has become corrupt due to a firmware defect.

The Bridging Mode Sense cache is full, caching operation failed.

Unable to forward command to the automation device because the ADT port is logged out.

Used to instruct the Bridge Device server to resend a SCSI command to the remote SMC LUN.

SCSI module (from 9400h) 113

9479h

947Ah

947Bh

947Ch

947Dh

947Eh

947Fh

9480h

9481h

9482h

9483h

9484h

114 Drive error codes

9474h

9475h

9476h

9477h

9478h

946Eh

946Fh

9470h

9471h

9472h

9473h

Error

9465h

9466h

9467h

9468h

9469h

946Ah

946Bh

946Ch

946Dh

Description

Cleaning cartridge is seated but not threaded.

Firmware upgrade cartridge is seated but not threaded.

Invalid value in supplied drive serial number.

siCheckWWN has detected that the supplied WWN is already assigned.

Tagged overlapped command.

Returned GOOD status.

Lock SMC cache failed. Internal return status indicating the SMC cache was not locked.

SMC cache locked. Reported is siSmcLockCache() is called when the cache is not unlocked.

Bridge ready but operation in progress. The Bridging Manager is busy. It already has an open exchange with the remote SMC device server.

Bridge not ready and operation in progress. The Bridging Manager is busy. It already has an open exchange with the remote SMC device server.

Invalid Vendor ID.

Invalid Product ID.

Medium removal prevented.

Forward task to drive. Not a reportable error code.

Logout in bad state. The Bridging Manager received notification of an ADT port Logout while waiting for TMF response to abort synchronizing PAMR command.

Not reserved. If the OIR bit is set in Device Config mode page, commands will return this if there is no persistent reservation.

Initialization in progress. The Automation Controller is initializing the drive.

Invalid field in medium attribute. An invalid field is the SCSI Set Medium Attribute command parameter list.

Truncated medium attribute. A medium attribute in a SCSI Set Medium Attribute parameter list is truncated.

Invalid field in Log Data cache. An invalid field in the SCSI Set Log Data Cache command parameter list.

Truncated log page descriptor. A log page descriptor in a SCSI Set Log Date Cache command is truncated.

Invalid field in parameter list.

Invalid field in SP Out data.

SP Out parameter list length error in CDB.

Data encryption parameters changed by another initiator Unit Attention.

Data encryption parameters changed by vendor specific event Unit Attention.

SP Key instance CTR changed.

Unsupported encryption cartridge.

Firmware upgrade already in progress. Another initiator has already started a FW download sequence.

Firmware upgrade image not MOD4.

Firmware upgrade image has bad CS on first chunk.

Firmware upgrade reboot in progress.

Error

9485h

9486h

9487h

9488h

9489h

948Ah

948Bh

948Ch

948Dh

948Eh

948Fh

9490h

9491h

9492h

9493h

9494h

9495h

9496h

9497h

9498h

9499h

949Ah

949Bh

949Dh

949Eh

949Fh

94A0h

94A1h

94A2h

94A3h

94A4h

94A5h

94A6h

94A7h

Description

The boot info area of the serial flash is corrupt. EnFUG command set will not work.

No key is available when asked to encrypt or decrypt.

SetManagementURI command is only allowed when the drive is not ready.

Parameter list length specified has too many URI descriptors. Only used with the SetManagementURI command.

Logical EOT has been detected.

Decrypt key fail limit reached. Exhaustive search attack prevention.

Stored HAT count in NV is greater than Max HAT Retries.

Stored default Map ID for this port is invalid.

Write command allocation length error. If encryption mode is set to encrypt, only 8 MB record size is allowed.

Too many stalled auto mode commands already exist in the slow device server queue.

The drive has detected invalid sense data from the remote SMC device server.

KMS did not provide a key.

Parameter list length error in the CDB.

A command descriptor in the Set Snapshot Command Set parameter list was truncated.

The configuration descriptor in the Set Snapshot Config parameter list was truncated.

Failed to start the Service Buffer snapshot because one is already in progress.

SI RSA Signature Known Answer Test has failed.

Cannot set security parameters, the drive has been (externally) configured not to accept security parameters.

KMS reported it failed to obtain security parameters, without which the command cannot be executed.

KMS reported it failed to obtain security parameters, unrecoverable error.

KMS reported it failed to obtain security parameters; error when trying to access the key.

KMS reported it failed to obtain security parameters, key not found.

KMS reported it failed to obtain security parameters, incorrect key.

Timer expired when waiting for security parameters from KMS.

Encryption UA.

KMS reported it failed to obtain security parameters, request not authorized (for example, the loaded tape is not encryption capable).

The drive is in a special maintenance or self-test mode.

The parameter list of a SET LIVE TRACE POINTS/VARIABLES command was truncated.

The parameter data of a SET TIMESTAMP command was truncated.

Timestamp changed UA.

Failed to initiate an SPI transfer to read an STTF log from flash memory.

The parameter data of a SET SERVICE LOCATION command was truncated.

Cannot enable an NPIV port when the physical port is in Loop mode.

The parameter data of a SET PREVENT MEDIUM REMOVAL command was truncated.

SCSI module (from 9400h) 115

94BFh

94C0h

94C1h

94C2h

94C3h

94C4h

94C5h

94C6h

94C7h

94C8h

116 Drive error codes

94B7h

94Bh8

94B9h

94BAh

94BBh

94BCh

94BDh

94B1h

94B2h

94B3h

94B4h

94B5h

94B6h

94BEh

Error

94A8h

94A9h

94AAh

94ABh

94ACh

94ADh

94AEh

94AFh

94B0h

Description

The device server does not have sufficient recourses to process all the initiators in the parameter list.

SET PREVENT MEDIUM REMOVAL command not allowed when SMC LUN enabled.

SET PREVENT MEDIUM REMOVAL command not allowed when an NPIV is not associated with the

SMC logical unit.

SET LEGACY RESERVATION command not allowed when SMC LUN enabled.

SET LEGACY RESERVATION command not allowed when an NPIV is not associated with the SMC logical unit.

The parameter data of a SET LEGACY RESERVATIONS command was truncated.

The parameter data of a SET PERSISTENT RESERVATIONS command was truncated.

The device server does not have sufficient recourses to process all the reservation keys in the parameter list.

Error detected in an SP OUT command or its data, either when attempting to establish a CCS, or after decrypting when the integrity is checked.

Error detected in an SP OUT command Authentication step; SAI_AC or SAI_DS is wrong.

Error detected in an SP OUT command Authentication step; authentication failed.

A host tried to initiate a new SA while another is in progress.

The creation of a SA is in progress, the command is not allowed.

FUGImage too large for flash.

The bridging manager has attempted to send a SCSI command to the remote SMC LUN before the bridging port has been registered or configured.

A Cryptographic Algorithm function returned an unexpected length.

The Set Beacon LED Config parameter list is truncated.

No task objects available in the SCSI Task Manager. This is a fatal error.

The Set IP Config parameter list is truncated.

A Certificate Manager function returned an unexpected length.

A Certificate Manager function returned an unexpected length on a Security Configuration command.

A Cryptographic Algorithm function returned an unexpected length on a Security Configuration command.

The SPOUT signature could not be authenticated because the Management Host Certificate public key is not present.

A Set Symbolic Name descriptor is truncated.

A cartridge is not loaded but it has been detected in the drive.

An Automation Device Attribute Descriptor header was truncated.

The Automation Device Attribute value was truncated.

The AER Control deescriptor was truncated.

The status indicates that the specified symbolic name is the same as the current symbolic name.

The SET ADVANCED PORT SETTINGS parameter list was truncated.

The specified symbolic name exceeds the maximum permitted length.

The specified symbolic name is not null-terminated.

The specified Live Trace point has been specified multiple times in the parameter list.

94D8h

94D9h

94DAh

94DBh

94DCh

94DDh

94DEh

94DFh

94E0h

94E1h

94E2h

94E3h

94E4h

94E5h

94E6h

94E7h

94E8h

94E9h

94EAh

Error

94C9h

94CAh

94D2h

94D3h

94D4h

94D5h

94D6h

94D7h

94CBh

94CCh

94CDh

94CEh

94CFh

94D0h

94D1h

Description

The specified Live Trace point ID is invalid. It must be 0000h.

The firmware file sent is too big.

Firmware upgrade tape contains data.

Cannot read flash for the firmware upgrade tape.

Incompatible tape format encountered while creating the firmware upgrade tape.

Format medium operation is in progress.

The cartridge does not support formatting (partitioning).

The SPOUT signature could not be authenticated because the Root CA Certificate is not present.

In Data Path Failover, the symbolic names of Port A and B must be the same. They are not.

Attempt to clear RSA Key pair not allowed; SECURE MODE disabled.

A failover session was released by an initiator that did not own it.

The certificate is not a Root CA certificate with valid dates.

Security configuration changed UA.

Attempt to erase root CA certificate when drive certificate is present.

The WP bit in the RMC Logical Unit mode page 0Eh/03h is set to 1, indicating that the library has write-protected the media.

The logical position supplied in the ALLOW OVERWRITE CDB does not match the current logical position.

The ALLOW OVERWRITE CDB is not allowed when Append-Only mode is not enabled.

Append-Only mode is enabled but the Allow Overwrite variable is not set to 'Format'.

When the drive is in idle (hibernate mode), the REQUEST SENSE data will reflect this state.

The drive received a failover restricted command from an I_T_L nexus not associated with a failover session.

The drive received a command that did not have the expect Failover Sequence Count in the CDB

Control byte.

A failover session has already been established using the specified failover session key.

No failover session has been established with the specified failover session key.

The SET PATH FAILOVER LICENCE KEY parameter list was truncated.

All failover sessions have been allocated.

One or more OpenSSL FIPS selftests failed when SME set to 1 by SPOut command.

Invalid internal LUN.

Role-based authentication of the primary port I_T nexus failed.

The failover session I_T_L nexus settings have changed.

The media changer control path has moved to a different drive.

Security Configuration Protocol Authentication Request failed.

The device certificate does not contain this drive's public key.

The name of the client CA certificate is the same as the root CA name.

The public key is already in the whitelist and must be deleted before being replaced.

SCSI module (from 9400h) 117

Error

94EBh

94ECh

94EDh

94EEh

94EFh

94F0h

94F1h

94F2h

94F3h

94F4h

94F5h

Description

An initiator's Prevent Medium Removal has been preempted by another initiator.

Failover: NCN command tried to reposition to a partition that does not exist.

An RSA key is corrupted.

Whitelist does not contain the required public key.

An error occurred while decrypting data.

An error occurred while performing a signature verification.

The command cannot return the information requested because the logical position cannot be represented.

The Set STTF Config parameter list is truncated.

The SET DRIVE HEALTH RULES parameter list is truncated.

The device server has insufficient buffer space to process the number of rules specified in the parameter list.

Reported to Drive Monitor when the Drive Health Algorithm changes Tape Alert flags and front panel

LEDs.

Automation/Drive Interface (from 9800h)

980Ah

980Bh

980Ch

980Dh

980Eh

980Fh

9810h

9811h

9812h

9813h

9814h

9815h

Error

9801h

9802h

9803h

9804h

9805h

9806h

9807h

9808h

9809h

Description

Resource issue: The ADI failed to queue an object because the queue is full.

The ADI failed to get a queue item because the queue was empty.

Resource issue: The ADI was unable to allocate a new Frame Control Block.

Resource issue: The ADI does not have sufficient memory to complete the current operation.

Firmware defect: An invalid queue was referenced.

Resource issue: Unable to allocate a new exchange ID; all Exchange IDs are in use.

Firmware defect: The firmware generated an invalid state-machine event.

Firmware defect: The firmware referenced an invalid firmware state-machine.

Firmware defect: The firmware referenced an invalid FCB handle.

Unable to get a new task object.

The SCSI Exchange ID table is full.

A new exchange has been started with an ID of an existing exchange.

The ADT Port interface received a SCSI Command IU containing an invalid field.

The ADT Port interface received a SCSI Data IU containing an invalid field.

The ADT Port interface received a SCSI Response IU containing an invalid field.

The ADT Port interface received a SCSI operation from a device server with an invalid Context ID.

Unable to generate a frame because it exceeds the maximum payload size.

The ADT Port interface received more SCSI data than is permitted within a burst.

The ADI Port interface has received a Data IU with an offset outside the current burst.

The ADT Port interface received a command from a device server that it cannot support.

The ADT Port did not receive an ACK for a frame it transmitted.

118 Drive error codes

982Ch

982Dh

982Eh

982Fh

9830h

9831h

9832h

9833h

9824h

9825h

9826h

9827h

9828h

9829h

982Ah

982Bh

9834h

9835h

9836h

9837h

9838h

9839h

983Ah

Error

9816h

9817h

9818h

9819h

981Ah

981Bh

981Ch

981Dh

981Eh

981Fh

9820h

9821h

9822h

9823h

Description

Temp need to replace with SI_ERR_TASK_QUEUE_FULL when available.

Self-test failed: Unexpected FCBs allocated.

Self-test failed: Unexpected exchange open.

Self-test failed: Queue not empty.

Self-test failed: SCSI Exchange not in the state IDLE.

The ADT port has detected an excessive number of framing errors.

Self-test failed: Non-zero library ACK offset.

Received Transfer Ready IU contained an invalid Buffer Offset field.

Received an ACK frame but not for frame it was expecting.

Received an NAK frame but not for frame it was expecting.

Giving up initiating a Port Login after a number of failed attempts.

Discarding an ACK frame it received after the acknowledgement timeout.

Did not receive acknowledgement within the Acknowledgement Period.

Received a frame with a checksum error.

Received a frame when the port was disabled.

Received Transfer Ready IU was shorter than expected.

Received Transfer Ready IU was longer than expected.

Received Transfer Ready IU contained a Burst Length value of zero.

Failed to execute a SCSI operation because it is logged-out.

Failed to execute a SCSI operation because it is busy doing something else.

Aborted bridged SCSI command due to a communication failure.

Unsupported task management function.

Invalid SCSI response code.

Invalid field in SCSI IU.

More data transferred than requested.

Task management function failed.

Service delivery failed.

Invalid LUN in task management IU.

Failed to transmit SCSI command or Task Management Function IU.

Received zero length SCSI data IU.

Received a data IU unexpectedly.

Unexpected null frame pointer.

The drive has detected a library firmware defect.

Specified port is not a recognized ADT port.

Instructs Bridging Manager not to resend a command with a UNIT ATTENTION sense key.

A function will send a response when it has finished.

The library NAKed a frame from the drive. Reported in the ADI/AMI command history log.

Automation/Drive Interface (from 9800h) 119

Error

983Bh

983Ch

983Dh

983Eh

983Fh

9840h

F801h

F802h

Description

Reported in the ADI/AMI Command History log to indicate a PORT RESET event occurred due to a diagnostic command.

Not reported to a host but indicates a firmware defect sequencing a firmware reboot related to an

ADT RESET IU.

Used for test purposes only.

The frame received was saved while the ADI port was being reset.

The previously saved frame was overwritten by another while the ADI port was being reset.

In the ADI Command History log: Indicates an Implicit Logout event.

GWIF pending.

GWIF no change.

Management API (from 9C00h)

9C11h

9C12h

9C13h

9C14h

9C15h

9C16h

9C17h

9C18h

9C09h

9C0Ah

9C0Bh

9C0Ch

9C0Dh

9C0Eh

9C0Fh

9C10h

Error

9C01h

9C02h

9C03h

9C04h

9C05h

9C06h

9C07h

9C08h

Description

The Ethernet RESET line has been activated.

The System ARM maHandleEvent() function has received an illegal event.

An invalid iADT port was specified for connection.

The iADT SENSEa input is asserted by the library controller.

The iADT SENSEa input is not asserted by the library controller.

The iADT SENSEa input has not been read yet.

Failure during socket read.

Failure during socket write.

MgmtArm rejected the maConfigNetworkIF options.

Requested self-test passed.

Requested self-test failed.

Fatal condition caused the Management ARM to fail.

Could not queue the message, the Mailbox is full.

Could not allocate memory to copy an ADT frame.

The awaited event has occurred.

The Mailbox is empty.

The command failed because the requested port does not exist.

Failed to connect to the remote host.

POST status not available.

Unable to get a new task object.

Cannot execute the SCSI command because another is in progress.

The KMS Agent Port interface received more SCSI data than permited within a burst.

PKI type invalid.

PKI format invalid.

120 Drive error codes

Error

9C19h

9C1Ah

9C22h

9C23h

9C24h

9C25h

9C26h

9C27h

9C28h

9C29h

9C1Bh

9C1Ch

9C1Dh

9C1Eh

9C1Fh

9C20h

9C21h

9C2Ah

9C2Bh

9C2Ch

9C2Dh

9C2Eh

9C2Fh

9C30h

9C31h

Description

PKI conversion error.

PKI processing error.

Frame Buffer unrecoverable error.

Buffer Bridge unrecoverable error.

DTCM unrecoverable error.

ITCM unrecoverable error.

Undefined Instruction error.

Prefetch Abort error.

Data Abort error.

Fatal condition caused the Management ARM to iInvoke Dtrap().

Invalid field in CDB.

Invalid field in parameter list.

MA LED test passed.

MA LED test failed.

TCM POST failed.

Frame Buffer POST failed.

MAC Register POST failed.

PHY Register POST failed.

VIC POST failed.

Timer POST failed.

System Controller POST failed.

Tracepoint POST failed.

OpenSSL known answer test failed.

The System ARM received data on the iSerial port unexpectedly.

The KMS Agent Message Queue is full so the message cannot be queued.

Servo (from A000h)

Error

A000h

A001h

A002h

A003h

A005h

A006h

A007h

A008h

Description

No error.

The servo system has shutdown due to panic conditions.

The Servo Task fault buffer has overflowed. Some entries have been lost.

The Servo Interrupt fault buffer has overflowed. Some entries have been lost.

The servo firmware requested a timer when none was available.

Timeout occurred while waiting to report servo statistics.

The current servo firmware task is not a valid task.

The acceleration phase of the seek did not complete within the allotted time.

Servo (from A000h) 121

Error

A009h

A00Ah

A012h

A013h

A014h

A015h

A016h

A017h

A018h

A019h

A00Bh

A00Ch

A00Dh

A00Eh

A00Fh

A010h

A011h

A01Ah

A01Bh

A01Ch

A01Dh

A01Eh

A01Fh

A020h

A021h

A022h

A023h

A024h

A025h

A026h

A027h

A028h

A029h

A02Ah

A02Bh

A02Ch

Description

The deceleration phase of the seek did not complete within the allotted time.

Settle window criterion was not met at the end of the deceleration phase of the seek.

Hand-off to the tracking phase of the seek did not complete within the allotted time.

Servo mode was not recognized during a seek.

A timer fault occurred during a negative stiction pulse.

A timer fault occurred during a positive stiction pulse.

A timer fault occurred during the bottom crash stop calibration.

A timer fault occurred during the top crash stop calibration.

The measured actuator stroke size is too small.

A timer fault occurred during TSB calibration.

TSB0 calibration did not complete within the allotted time.

TSB1 calibration did not complete within the allotted time.

TSB2 calibration did not complete within the allotted time.

TSB3 calibration did not complete within the allotted time.

An invalid servo track number was specified for a seek.

The calculated final target for a VI seek was out of range.

The calculated final target for a Tape seek was out of range.

Unable to find the requested TSB.

Unable to find Servo code on the tape; bad head.

Unable to identify the current Top Servo band.

Unable to identify the requested Seek type.

Unable to lock to tape when not tracking on VI.

Unable to lock to tape servo code within the allotted time.

Primary servo bump went out while writing.

System ARM is not allowing tape servo operations.

VI offset calibration has not been done.

The specified servo scope mode is not valid.

The specified servo scope channel bit width is not supported.

The specified servo source number is not valid.

The specified servo scope trigger position is too large compared with the specified number of data packets in the trace.

The specified servo scope source address was not found in the address array.

The specified servo scope source bit size was not found in the size array.

A Measure Servo Heads command did not complete within the allotted time.

The main system ARM flagged the need to revert to VI.

Band ID had good skew values from both bumps but was unable to identify the band.

Band ID had good skew values from both bumps but identified different valid bands for each bump.

122 Drive error codes

Error

A02Dh

A02Eh

A02Fh

A044h

A045h

A046h

A047h

A048h

A049h

A04Ah

A04Bh

A03Ch

A03Dh

A03Eh

A03Fh

A040h

A041h

A042h

A043h

A04Ch

A04Dh

A04Eh

A04Fh

A030h

A031h

A032h

A033h

A034h

A035h

A036h

A037h

A038h

A039h

A03Ah

A03Bh

Description

Tape servo code available from at least one channel but unable to achieve tape lock. The head is suspect.

Not enough good demod channels to attempt band ID whilst searching for tape servo during TSB calibration.

Tape servo code available from at least one channel but unable to achieve tape lock. The head is suspect.

The servo command is incorrectly formatted.

The servo command cannot be executed now.

Servo fault.

Servo fault.

Servo fault.

Servo fault.

Servo fault.

One or more of the command parameters are invalid.

The servo command sent is not supported.

The servo command sent is out of sequence.

The mechanism interface did not respond within the allotted timeout, shutting down the reel motors.

Init servo command already in progress.

Write memory servo command already in progress.

Read memory servo command already in progress.

Set generation servo command already in progress.

Set scope mode servo command already in progress.

PCA diagnostic servo command already in progress.

Live statistics servo command already in progress.

Seek command already in progress.

Report TSBs servo command already in progress.

Define Scope Sources servo command already in progress.

Configure Oscillator servo command already in progress.

Define Signal Nodes servo command already in progress.

Calibrate VI Stroke servo command already in progress.

Calibrate TSBs servo command already in progress.

Report Servo Status servo command already in progress.

Configure Test DACs servo command already in progress.

Report Servo Configuration servo command already in progress.

Measure Servo Heads servo command already in progress.

Copy Memory Block servo command already in progress.

Report Enum Address servo command already in progress.

Set Compensator Coefficients servo command already in progress.

Servo (from A000h) 123

Error

A050h

A051h

A052h

A053h

A054h

A055h

A056h

A057h

A058h

A060h

A061h

A062h

A063h

A064h

A065h

A066h

A067h

A068h

A069h

A06Ah

A06Bh

A06Ch

A06Dh

A06Eh

A06Fh

A070h

A071h

A072h

A073h

A074h

A080h

A081h

A082h

A083h

A084h

A085h

124 Drive error codes

Description

Set Head Position Tuning Parameters servo command already in progress.

Clean Head servo command already in progress.

Accelerometer Self-Test servo command already in progress.

TSB calibration routine did not complete within the alloted time.

The servo interrupt flagged the need to revert to VI. Most likely cause is that the tape position data went away while tracking.

The servo system attempted to recover the actuator to a known state.

The servo Interrupt execution was longer than the interrupt rate.

The calculated VI gain at destination of a seek is invalid.

The adaptive servo algorithm entered fail safe.

The mechanism revision was not recognized while trying to configure the compensator.

Timer unavailable for motion to the top crash stop as part of a head-clean routine.

Timer unavailable for motion to the bottom crash stop as part of a head-clean routine.

Timer unavailable for motion to the bottom crash stop as part of a head-clean routine.

Seek at the top crash stop during a head-clean.

Seek at the bottom crash stop during a head-clean.

Compensator configuration already set from the EEPROM content or a mechanism revision parameter missing.

The specified head mode is not recognized.

Target VI gain for use at seek destination could not be determined.

A defect scan is already in progress.

Unable to detect motion has ceased at the top stop during a sensor stroke cal.

Unable to detect motion has ceased at the bottom stop during a sensor stroke cal.

Target TSB does not match the TSB returned from BandID.

SR countdown has begun.

VI oscillator is not functioning correctly.

VI oscillator is not oscillating.

The traceport FIFO between system and servo ARMs overflowed.

Unable to reset traceport hardware; the event mailbox was busy.

VI seek landed too close to the edge of servo code to attempt tape tracking.

The measured actuator stroke size is too big.

The index into the VI table is out of range.

Demod data unavailable from elements: TopA.

Demod data unavailable from elements: BottomA.

Demod data unavailable from elements: TopA, BottomA.

Demod data unavailable from elements: TopB.

Demod data unavailable from elements: TopA, TopB.

Demod data unavailable from elements: BottomA, TopB.

Error

A086h

A087h

A088h

A089h

A08Ah

A08Bh

A08Ch

A08Dh

A08Eh

A08Fh

Description

Demod data unavailable from elements: TopA, BottomA, TopB.

Demod data unavailable from elements: BottomB.

Demod data unavailable from elements: TopA, BottomB.

Demod data unavailable from elements: BottomA, BottomB.

Demod data unavailable from elements: TopA, BottomA, BottomB.

Demod data unavailable from elements: TopB, BottomB.

Demod data unavailable from elements: TopA, TopB, BottomB.

Demod data unavailable from elements: BottomA, TopB, BottomB.

Demod data unavailable from elements: TopA, BottomA, TopB, BottomB.

Reserved Servo fault.

Certificate manager (from A400h)

Error

A401h

A402h

A403h

A404h

A405h

A406h

A407h

A408h

A409h

Description

A Root CA certificate already exists and authentication is not possible without a Management Host certificate.

The Management Host certificate was rejected because the Root CA does not exist.

Unknown or unexpected Certificate Manager state.

The Management Host certificate failed verification.

The Public Key length returned does not match the length in the Public Key descriptor.

The certificate usage and index do not specify a valid certificate storage slot.

The certificate usage and index do not specify a valid whitelist public key storage slot.

The device certificate failed verification.

The device certificate was rejected because the Root CA does not exist.

Cryptographic algorithms (from A800h)

Error

A801h

A802h

A803h

A804h

A805h

A806h

A807h

A808h

A809h

A80Ah

A80Bh

Description

Algorithm ID indicated an unsupported algorithm.

Invalid key length specified.

Algorithm index not found.

One or more pointer arguments were null.

Invalid algorithm database.

Initiator message signature is invalid.

Message digest buffer is too small.

Insufficient entropy.

Decryption authentication failure.

Certification authority hash mismatch.

Random number generation failed.

Certificate manager (from A400h) 125

Error

A80Ch

A80Dh

A80Eh

A80Fh

A810h

A811h

A812h

A813h

A814h

A815h

A816h

A817h

A818h

Description

Diffie-Hellman public value creation failed.

Bignum conversion failed.

Message digest failure.

Signature failure.

Encryption argument error.

Encryption failure.

OpenSSL initialization failure.

OpenSSL d2i conversion failure.

Buffer is too small.

One or more CAVP tests failed.

One or more OpenSSL FIPS self-tests failed at poweron with SME set to 1.

Generation of new RSA key pair failed.

OpenSSL memory allocation failure.

Master channel (from 3C00h)

Error

AC01h

AC02h

AC03h

AC04h

Description

Revi() failed, AFIR2 RS counter is zero.

Sandstrom read timeout.

PP adaptation failed to read. Possible No Data Detected.

AFIR2 adaptation failed to read. Possible No Data Detected.

Hyper-drive (from F400h)

Error

F401h

F402h

F403h

F404h

F405h

F406h

F407h

F408h

F409h

F40Ah

F40Bh

Description

Sandstrom read failed waiting for status bit.

Sandstrom read failed waiting for data.

Hyper_init: failed to read READ_SSTROM_RDSP_CONTROL.

Hyper_init: failed to read READ_DSP_TESPORT_ADDRESS.

Hyper_init: failed to read DSP_TESPORT_DATA_BAD.

Hyper_init: failed to read SSTROM_RDSP_PARITY_ERROR.

Hyper_init: failed to read SSTROM_RDSP_SYNC_ERROR.

Hyper_init: Orion page in use.

Hyper_init: HT CONTROL check failed.

Hyper_init: HT PARITY NOT ZERO.

Hyper_init: HT SYNC NOT ZERO.

126 Drive error codes

12 Support and other resources

Related documents

The following documents provide additional information:

Documents specific to HP LTO Ultrium drives

Software Integration Guide, volume 2 of the HP LTO Ultrium Technical Reference Manual

Host Interface Guide, volume 3 of the HP LTO Ultrium Technical Reference Manual

Specifications, volume 4 of the HP LTO Ultrium Technical Reference Manual

UNIX, Linux and OpenVMS Configuration Guide, volume 5 of the HP LTO Ultrium Technical

Reference Manual

Please contact your HP supplier for copies.

The features and benefits of HP LTO Ultrium drives are discussed in the HP LTO Ultrium

Technology White Paper.

For a general background to LTO technology and licensing, go to nl http://www.lto-technology.com

.

Documentation map

The following will help you locate information in the Technical Reference Manual. A reference like

“1 HW Integration: ch. 7” means Volume 1, Hardware Integration Guide, of the HP LTO Ultrium

Technical Reference Manual, chapter 7.

Drives—general

1 HW Integration: ch. 4

1 HW Integration: ch. 3

4 Specifications

Connectors

Front panel LEDs

Specifications

Installation and configuration

Connectors

Determining the configuration

Installation

Linux configuration

Modes of usage

OpenVMS configuration

Optimizing performance

1 HW Integration: ch. 4

2 SW Integration: ch. 2

1 HW Integration: ch. 7

5 UNIX, Linux, OpenVMS Configuration n/a

5 UNIX, Linux, OpenVMS Configuration

1 HW Integration: ch. 6

2 SW Integration: ch. 4

5 UNIX, Linux, OpenVMS Configuration UNIX configuration

Operation

Operation 1 HW Integration: ch. 8

Related documents 127

Cartridges

Cartridge Memory (LTO-CM)

Cartridges

Managing the use of cartridges

Use of cartridges

Interface

FC and SAS host interface guide

Commands

Error codes

Implementation

Interpreting sense data

Messages

Mode pages —see the MODE SENSE command

Pre-execution checks

Responding to sense keys and ASC/Q

Response frames

Sense keys and ASC/Q —see REQUEST SENSE command

Task management functions

Maintenance and troubleshooting

Cleaning

Troubleshooting

Monitoring drive and tape condition

Software troubleshooting techniques

Dealing with errors

Error codes

Exception handling

Logs—see the LOG SENSE command

TapeAlert log

LTO Ultrium features

Autoload

Automation Control Interface (ACI)

Cartridge Memory (LTO-CM)

128 Support and other resources

2 SW Integration: ch. 5

1 HW Integration: ch. 5

2 SW Integration: ch. 1

2 SW Integration: ch. 3

3 Host Interface

3 Host Interface: ch. 5

1 HW Integration: ch. 11

3 Host Interface: ch. 1

2 SW Integration: ch. 6

3 Host Interface: ch. 2

3 Host Interface: ch. 5

3 Host Interface: ch. 4

2 SW Integration: ch. 6

3 Host Interface: ch. 3

3 Host Interface: ch. 5

3 Host Interface: ch. 3

2 SW Integration: ch. 1 nl

2 SW Integration: ch. 5

1 HW Integration: ch. 9

2 SW Integration: ch. 7

2 SW Integration: ch. 1

1 HW Integration: ch. 11

2 SW Integration: ch. 7

3 Host Interface: ch. 5

2 SW Integration: ch. 7

1 HW Integration: ch. 10

1 HW Integration: ch. 10

1 HW Integration: ch. 5 nl

Data compression, managing

OBDR and CD-ROM emulation

Performance optimization

Performance, factors affecting

Software design

Supporting LTO Ultrium features

2 SW Integration: ch. 5

2 SW Integration: ch. 5

2 SW Integration: ch. 7

1 HW Integration: ch. 6

2 SW Integration: ch. 1

2 SW Integration: ch. 4

2 SW Integration: ch. 1

2 SW Integration: ch. 5

Related documents 129

General documents and standardization

See http://www.t10.org/t10_main.htm

for INCITS SCSI Primary Commands—3 (SPC-3), SCSI

Streaming Commands (SSC-3) and other specifications

Copies of documents of other standards bodies can be obtained from:

INCITS 11 West 42nd Street New York, NY

10036-8002 USA

ISO nl

CP 56

CH-1211 Geneva 20 nl

Switzerland

ECMA 114 Rue du Rhône nl

CH-1204 Geneva nl

Switzerland

Global Engineering 2805 McGaw nl

Documents Irvine, CA 92714 nl

USA

Tel: +41 22 849 6000 nl

Web URL: http://www.ecma.ch

Tel: 800 854 7179 or 714 261 1455

130 Support and other resources

Glossary

AL_PA

ANSI arbitrated loop

Arbitrated Loop Physical Address. A 1-byte value used in the arbitrated loop topology used to identify L_ports. This value will then also become the last byte of the address identifier for each public L_port on the loop. The AL_PA can be set through an ACI Set Drive Configuration command.

American National Standards Institute, which sets standards for, amongst other things, Fibre

Channel, SCSI and the safety of electrical devices.

One of the three Fibre Channel topologies. Up to 126 NL_ports and 1 FL_port, or 127 NL_ports, are configured in a unidirectional loop. Ports arbitrate for access to the loop based on their

AL_PA. Ports with lower AL_PAs have higher priority than those with higher AL_PAs.

autoload

BOM buffered mode

When a tape cartridge is inserted, a tape drive with autoload will automatically load it without the host having to send a load command. If a drive does not have autoload, the drive will take no action until it receives a load command.

Beginning Of Media. The first point on the tape that can be accessed by the drive.

A mode of data transfer in write operations that facilitates tape streaming. It is selected by setting the Buffered Mode Field to 1 or 2 in the SCSI MODE SELECT Parameter List header.

channel A means of data communication between processors and between processors and peripherals.

A channel provides a direct or switched point-to-point connection between the communicating devices. A channel is typically hardware-intensive and transports data at the high speed with low overhead. Contrast this with Networks.

compression ratio A measure of how much compression has occurred, defined as the ratio of the amount of uncompressed data to the amount of compressed data into which it is transformed. The LTO-DC algorithm can typically achieve a compression ratio of between 2:1 and 4:1 depending on the nature of the data.

compression A procedure in which data is transformed by the removal of redundant information in order to reduce the number of bits required to represent the data.

decompression

DFA

ECMA

EOD

EOM

A procedure in which the original data is generated from compressed data.

Direct Fabric Attach. The connection between an N_port and an F_port.

European Computer Manufacturers Association. The European equivalent of ANSI.

End Of Data. An area that signifies the end of the valid data. If new data is written over a larger quantity of old data, it is possible for data to exist after EOD, but because it is after EOD, this old data is no longer valid.

End Of Media format. The last usable point on the tape.

131

FC_FLA

FC_GS

FC_SW

FCP fibre channel filemark

FL_port forced eject

FRU hard error host

L_port load

LUN

LVD

N_port

EW-EOM

F_port fabric fabric zoning

FC

FC-AL

Early Warning End Of Media. A physical mark or a device-computed position on the tape that tells the drive that it is approaching EOM.

Fabric port. A port on a fabric switch operating according to point-to-point topology, to which

N_ports may be directly connected. An F_port uses the address identifier FFFFFEh.

See switched fabric.

Isolation of two separate switched fabric (FC_SW) zones by the switch.

See fibre channel.

Fibre Channel Arbitrated Loop. An ANSI standard that describes how several Fibre Channel ports can share a single communication ring. Using optical fiber to connect devices, FC-AL is compatible with SCSI for high-performance storage systems.

See also arbitrated loop[.

Fibre Channel Fabric Loop Attach. An ANSI standard that describes the rules by which NL_ports and FL_ports communicate with each other.

Fibre Channel Generic Service. An ANSI standard that describes services such as Directory

Service that allow a host to identify which storage devices are available and what their addresses are.

Fibre Channel Switch Fabric. An ANSI standard that describes how fibre channel switches are required to behave.

See also switched fabric.

Fibre Channel Protocol. There are three: arbitrated loop, point-to-point and switched fabric.

Fibre Channel provides an inexpensive yet expendable means of quickly transferring data between workstations, mainframes, supercomputers, desktop computers, storage devices, displays and other peripherals. Although it is called Fibre Channel, its architecture represents neither a channel nor a real network topology. It allows for an active intelligent interconnection scheme, called a fabric, to connect devices. All a Fibre Channel port has to do is to manage a simple point-to-point connection between itself and the fabric.

Several common ULPs (Upper Level Protocols) including IP and SCSI can be used with Fibre

Channel, merging high-speed I/O and network functionality in a single connectivity technology.

A mark written by the host. It does not necessarily separate files; it is up to the host to assign a meaning to the mark.

Fabric-Loop port. An F_port which is capable of supporting an attached arbitrated loop. An

FL_port on a loop will have the AL_PA 00h, giving the fabric highest priority access to the loop.

An FL_port is the gateway to the fabric for NL_ports on a loop.

Functionality in the drive that should unload the cartridge in an emergency of if the cartridge fails to eject normally. To force ejection, press and hold the Eject button for 20 seconds. Wait for the cartridge to be ejected. This may take up to 15 minutes (the maximum rewind time).

On full height drives, there is also an emergency reset button—see

“Automation interface”

(page 54) .

Field Replaceable Unit, an assembly or group of components that is replaced in its entirety by

Service Engineers when it contains a fault.

An uncorrectable data error.

The host computer system acting as controller for the drive.

Loop port. A generic term for an NL_port or FL_port, in other words, any Fibre Channel port that supports the arbitrated loop topology.

The process in which the drive takes in an inserted cartridge and goes online.

Logical Unit Number, by which different devices at a particular SCSI ID can be addressed individually. The drive has a fixed LUN of 0.

Low-Voltage Differential

Node port. A port on a a device such as a computer system host bus adapter, disk drive or tape drive, through which the device connects to a point-to-point or fabric Fibre Channel topology.

132 Glossary

network

NL_port node offline online point-to-point

A collection of connected nodes (like workstations, file servers or peripherals) with its own protocol that supports interaction among these nodes. A network has relatively high overhead since it is software-intensive, and consequently slower than a channel. Networks can handle a more extensive range of tasks than channels as they operate in an environment of unanticipated connections, while channels operate among only a few devices with predefined addresses.

Node-Loop port. An N_port which can operate on the arbitrated loop topology.

A device that has at least one N_port or NL_port.

The drive is offline if the tape is currently unloaded or not in the drive. The host has limited access, and cannot perform any commands that would cause tape motion. The host can, however, load a tape, if one is inserted, and can execute any diagnostic tests that do not require tape motion.

The drive is online when a tape is loaded. The host has access to all command operations, including those that access the tape, set configurations and run diagnostic tests.

A Fibre Channel topology in which two points communicate directly.

port private loop private NL_port public loop public NL_port

RAW read-after-write ready-to-eject position

SAN

SFP switched fabric

An access point in a device to which a link attaches.

An arbitrated loop that has no attached switch port (NL-port to NL_port). In theory, private loop devices can only communicate with other devices on the same loop.

An NL_port that only communicates with other ports on the loop, not with the fabric. A private

NL_port may exist on either a private loop or a public loop.

An arbitrated loop where one of the ports on the loop is a switch port (an FL_port), thus allowing ports or devices on the loop to communicate with hosts or devices attached to other switch ports.

An NL_port that can communicate with other ports on the loop as well as through an FL_port to other N_ports connected to the fabric.

See read-after-write.

RAW improves data integrity by reading data immediately after it is written and writing the data again if an error is found.

A point at which a cartridge is held after an unload command is received by the drive (when

Auto-Eject is not set) and the tape has be rewound and unthreaded. The drive will then wait at this point until it is commanded to eject the cartridge by the ACI Unload command

Storage Area Network. A dedicated, high-speed network that establishes a direct connection between storage elements and servers. The hardware that connects workstations and servers to storage devices in a SAN is referred to as a fabric. The SAN fabric enables any-server-to-any-storage device connectivity through the use of Fibre Channel switching technology.

Small Form Pluggable transceiver. See transceiver.

One of the three Fibre Channel topologies. An interconnected network of Fibre Channel host ports, device ports and switch ports. In the fabric topology, N_ports are connected to F_ports on a switch. The link is the two unidirectional fibres transmitting in opposite directions. Each fibre is attached to a transmitter of a port at one end and a receiver of another port at the other end. It is possible for fabric switches to be connected to support up to 16 million+ N_ports on a single network.

133

TapeAlert transceiver

ULP

VHD zoning

A set of 64 flags is held in the TapeAlert log that indicate faults or predicted faults with the drive or the media. By reading this log, host software can inform the user of existing or impending conditions, and can, for example, advise the user to change the tape.

A device used to convert electrical signals in the drive to optical signals for transmission in a fibre optic cable. Used in Fibre Channel drives only.

Upper Level Protocol. The protocol which runs on top of Fibre Channel. Typical ULPs running over

Fibre Channel are SCSI (Small Computer System Interface), IP (Internet Protocol), HIPPI (High

Performance Parallel Interface, and IPI (Intelligent Peripheral Interface).

Very High Density

A logical grouping of fabric-attached devices that is isolated from other devices and other zones by the switch.

134 Glossary

Index

A

ACI,

51

, 53

, 54

connector,

20 ,

26

connector pins,

26

controlling loads,

58

error codes,

62

reset,

46

addresses, fibre channel,

25

ADI,

54

pin layout,

27

ADT,

54

airflow,

10

tape arrays,

40

airflow requirements,

10

AL_PAs,

25

,

131

ANSI,

127

, 130

,

131

arbitrated loop,

131

arbitrated loop physical address,

131

autochangers,

51

autoload, configuring,

58

autoloader front panel,

53

autoloaders,

51

autoloading,

131

automation control interface,

51 ,

53 ,

54

automation device interface,

54

automation front panel,

52

automation/drive interface,

54

error codes,

118

B

backup software,

39

,

51

BOM,

131

buffer manager error codes,

65

buffered mode,

131

bus types, supported,

38

bus, dedicated,

35

C

cartridge memory,

33 ,

51 ,

61

access via ACI,

55

error codes,

108

problems with,

33

cartridges,

31

jammed,

47

life,

32

loading,

44

not ejected,

49

positions during load and unload,

59

problems with,

48

unloading,

45

certificate manager, error codes,

125

channel,

131

cleaning heads,

45

problems with,

50

CM see cartridge memory,

51

compression ratio,

131

condensation, avoiding,

32

connecting to server,

38

connectors,

20 ,

41

automation,

26

FC,

26

internal SAS,

39

remote LED,

26

SAS,

20

,

26

contactless memory,

51

cooling,

10

critical section error codes,

111

cryptographic algorithms, error codes,

125

current requirements,

9

D

data compression,

131

data rate matching,

35

DC_GS,

132

decompression,

131

DFA,

131

diagnostic control error codes,

66

diagnostic port,

52

,

53

dimensions,

7

direct fabric attach,

131

DLT cartridges,

31

documents, related,

127

drive

ID,

39

not recognized,

48

Drive Error LED,

13

drive monitor error codes,

70

drives control error codes,

68

error codes,

62

ID,

51

moving,

42

operating,

43

problems with,

48

resetting,

46

resetting in libraries,

46

DRM,

35

duplex-LC connectors,

20

E

ECMA,

130

, 131

eject button,

52 ,

53

eject point,

59

eject, forced,

47

electrical fit,

9

emergency reset switch,

12

emergency unload,

47

Encryption LED,

13

EOD,

131

EOM,

131

135

error codes,

62

errors, hard,

132

Ethernet port see iADT

EW-EOM,

132

exception handler error codes,

108

external drives indentifying the drive,

42

loading a cartridge,

44

unloading a cartridge,

45

external fan,

58

external interfaces error codes,

70

F

F_port,

132

fabric,

133

fabric zoning,

132

fan interface,

58

FC connection,

40

FC-AL,

132

FC/SCSI router,

40

FC_FLA,

132

FC_SW,

132

FCP,

132

fibre channel,

132

addressing,

25

arbitrated loop,

132

fabric loop attach,

132

generic service,

132

ports,

24

switched fabric,

132

fibre channel connector,

26

filemarks,

132

filtering,

10

firmware upgrade, LED patterns,

18

fixing dimensions,

7

FL_port,

132

forced airflow,

10

forced eject,

47 ,

132

formatter ASIC,

10

front panel autoloader,

53

automation,

52

interface error codes,

71

LEDs,

13

replacing,

18

FRU,

132

fusing,

37

G

generic module error codes,

62

grounding integrity,

37

H

hard error,

132

HBA,

38

head cleaning,

45

host,

132

interface error codes,

71

problems with,

48

136 Index hyper-drive, error codes,

126

I

iADT,

54 ,

56

ID drive,

39 ,

51

loop,

25

identifying the drive external,

42

internal,

37

removable,

40

INCITS,

130

infrastructure, memory codes,

110

installing drives in libraries,

41

internal,

37

internal drives indentifying the drive,

37

reset switch,

12

ISO,

130

L

L_port,

132

labeling cartridges,

31

LEDs,

24

front panel,

13

rear panel,

24

libraries,

51

installation in,

41

resetting drives in,

46

life of cartridges,

32

load points,

60

loading,

132

loading cartridges configuring,

58

external drives,

44

positions,

59

positions of importance,

58

logical formatter error codes,

78

logical media error codes,

82

logical pipeline control error codes,

83

logs, TapeAlert,

134

loop IDs,

25

loop topology,

131

LTO-CM,

33 ,

51 ,

61

LUNs,

132

M

Management API, error codes,

120

master channel, error codes,

126

mechanical interface error codes,

94

mechanism control error codes,

83

modes of usage,

35

mounting requirements,

38

moving drives,

42

N

N_port,

132

NL_port,

133

node,

133

non-volatile data manager error codes,

84

O

offline,

133

online,

133

operating drives,

43

operating system error codes,

88

optimizing performance,

35

P

physical formatter error codes,

88

physical pipeline control error codes,

89

pins

ACI connector,

26

ADI connector,

27

point-to-point,

133

port LEDs,

24

ports,

24

,

133

power requirements,

9

power-on self-test,

43

primary temperature sensor,

10

private loop,

133

private NL_port,

133

PSU requirements,

9

public loop,

133

public NL_port,

133

R

rack-mount systems,

40

RAW,

133

read/write control error codes,

91

Ready LED,

13

ready-to-eject position,

60 ,

133

rear panel,

20

,

41

LEDs,

24

removable drives identifying the drive,

40

installing,

40

replacing drives in tape array,

41

replacing front panel,

18

reset switch,

12

resetting drives in libraries,

46

resetting drives via ACI,

46

S

safety,

37

SAN,

133

attaching a tape array,

40

SAS connector,

20

,

26

, 39

SCSI module, error codes,

111

self-test,

43

failure,

24

serial numbers external drives,

42

internal drives,

37

server, installing drive in,

37

Servo, error codes,

121

software, backup,

39

SPI interface error codes,

108

storage area network,

133

storing cartridges,

32

switched fabric,

133

system architecture error codes,

93

system configurations,

35

system performance,

35

T

tape arrays airflow,

40

installing drives,

40

replacing a drive,

41

Tape Error LED,

13

tape libraries see libraries,

51

tape life, maximizing,

32

TapeAlert log,

134

temperature, measuring,

10

tight integ error codes,

93

trace logger error codes,

93

U

ULP,

134

UNIX configuration,

7

unloading cartridges external drives,

45

in emergency,

47

positions of importance,

58

Use Cleaning Tape LED,

13

V

voltage requirements,

9

voltage supply requirements,

9

W

write-protecting cartridges,

31

Z

zoning,

134

137

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents