HP LTO 4 SAS, LTO 4 FC, LTO 4 SCSI manual

Page 86

 

Flag

Type

Set

Recommended Host Message

Cause

57

Automation

C

 

The tape drive has a problem with

The drive has identified a

 

interface failure

 

 

the automation interface:

fault in the automation

 

 

 

 

1.

Check the power to the

interface.

 

 

 

 

 

 

 

 

 

 

automation system.

 

 

 

 

 

2.

Check the cables and cable

 

 

 

 

 

 

connections.

 

 

 

 

 

3.

Call the supplier’s helpline if the

 

 

 

 

 

 

problem persists.

 

 

 

 

 

 

 

58

Firmware failure

W



The tape drive has reset itself due to

There is a firmware bug.

 

 

 

 

a detected firmware fault. If the

 

 

 

 

 

problem persists, call the supplier’s

 

 

 

 

 

helpline.

 

 

 

 

 

 

 

59

WORM

W



The tape drive has detected an

Someone has tampered with

 

medium—integr

 

 

inconsistency while checking the

the WORM tape.

 

ity check failed

 

 

WORM tape for integrity. Someone

 

 

 

 

 

may have tampered with the

 

 

 

 

 

cartridge.

 

 

 

 

 

 

 

60

WORM

W



An attempt has been made to

The application software

 

medium—

 

 

overwrite user data on a WORM

does not recognize the tape

 

overwrite

 

 

tape:

as WORM.

 

attempted

 

 

1.

If you used a WORM tape

 

 

 

 

 

 

 

 

 

 

 

inadvertently, replace it with a

 

 

 

 

 

 

normal data tape.

 

 

 

 

 

2.

If you used a WORM tape

 

 

 

 

 

 

intentionally, check that:

 

 

 

 

 

the software application is

 

 

 

 

 

 

compatible with the WORM tape

 

 

 

 

 

 

format you are using.

 

 

 

 

 

the cartridge is bar-coded

 

 

 

 

 

 

correctly for WORM.

 

 

 

 

 

 

 

 

 

 

 

Flags 61–64 are not currently used

 

Note that often messages will not appear in isolation. For example, message 01h (“The tape drive is having problems reading data.”) is likely to appear with a message suggesting remedial action, such as message 04h (“You are advised to copy any data...”) or message 14h (Clean Now).

Each flag is cleared to zero in the following circumstances:

At power-on.

When specified corrective action has been taken, such as using a cleaning cartridge.

When the TapeAlert Log page is read.

86 Exception handling

HP restricted

Image 86
Contents HP LTO Ultrium tape drives technical reference manual volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP restrictedLegal and notice information 2 Configuration and initialization Contents1 Designing backup applications 3 Use of tapes5 Supporting Ultrium features 4 Factors affecting performance6 Sense keys and codes 7 Exception handlingHP restricted Documents specific to HP Ultrium drives Related documentsDocumentation map Drives-generalCartridges Installation and configurationOperation InterfaceMaintenance and troubleshooting Dealing with errorsLTO Ultrium features General documents and standardizationOptimizing performance 1 Designing backup applicationsNon-immediate commands Large data transfer sizeInformation in Cartridge Memory Cleaning tape headsManaging the use of tapes Monitoring tape useTapeAlert Design goals for LTO backup applicationsDiagnostic logs Displaying drive informationInclude the capability to download firmware Operating system drivers 2 Configuration and initializationInquiry string recovery SCSI protocol, regardless of transport or interface type Example16 Configuration and initialization Supporting additional LUNs Support for additional LUNEnabling additional LUN support 18 Configuration and initialization 3 Use of tapes Using Cartridge Memory attributesUsing MODE SENSE LTO cartridge memoryInterpreting Log Sense data Tape status and capacityFinding the remaining capacity CDB fields Using the SET CAPACITY commandCommand descriptor block How WORM media works Changes to SCSI commandsWORM media New additional sense codes and TapeAlert flagsSET CAPACITY command Error Usage pageERASE commands rejected Re-writing media labelsUnique media identifier Using CM to check tape integrityBehavior with a missing or inconsistent EOD value Barcode support Responding to Cartridge Memory dataLoad count RWW retry counts Corrective actionDetecting the drive’s speed 4 Factors affecting performanceWays of optimizing performance Ensuring the recommended minimum transfer sizesTime-out values Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Media type identificationHost-related factors Recommended support of log pagesFactors affecting performance where possible or a reasonably sized RAID system. More disks means ExampleRecommendation makes sense to split heavily used FC cards across separate PCI bussesDrive-related factors Do not interleave write commands with other commands, such as READFormat-related factors Page 34 Factors affecting performance Automation interface 5 Supporting Ultrium featuresCartridge Memory LTO-CM Further informationAutomation/Device Interface ADI Slave to a library controller Automation Control Interface ACIModes of usage through ACI SCSI pass-through mode ACI command setACI commands that affect drive streaming performance New features in ACI Backward compatibilitySCSI command Encryption support Recommended ACI time-out values Further detailsSupporting the ACI protocol 42 Supporting Ultrium featuresRecommended power-up sequence Treatment of reserved fieldsRecommended load-unload configuration ACI protocol communications retry Firmware upgrade via tapeRecommended Get Drive Status polling frequency Upgrading the drive firmwareLibrary firmware upgrade via tape Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Handling irregular cartridgesNon-HP Ultrium 1 cleaning cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Unreadable data cartridgeCartridge fails to seat or load Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge cannot be loadedInvalid firmware upgrade cartridge Frequently asked questionsCleaning Is there separate firmware for drives intended to go into libraries?Resetting via the ACI Reset command Backup softwareResetting drives Resetting using the ACIRSTL lineOther mode page information Accessing Cartridge Memory without threading the tapeControlling data compression Buffer size at EW-EOMPartition size Rewind on resetWrite delay time 52 Supporting Ultrium featuresAction 6 Sense keys and codesSense keys-actions to take Console Messagelog the error, terminate I/O to the drive, and pass the appropriate “3h-MEDIUM ERROR” on page 62 . Also see the Media AccessFor additional sense codes, see “3h-MEDIUM ERROR” on error to the calling applicationAction ActionConsole Message Console MessageConsole Message End-of-Tape Additional sense codes-actions to takePhysical reached, unable to fit0h-NO SENSE 1h-RECOVERED ERROR 2h-NOT READYThe command cannot be executed because the specified The software must issue a LOAD before media accessLUN not accessible, port in 60 Sense keys and codesmechanism tests are being executed. When the tests are 62 Sense keys and codes 3h-MEDIUM ERRORA READ , SPACE , WRITE or WRITE FILEMARKS command Send a console message that an unrecovered error on and the drive. Based on this, ask the user to clean the64 Sense keys and codes Send a message to the console indicating that there is The current command such as READ, SPACE, REWIND 66 Sense keys and codes4h-HW ERROR 68 Sense keys and codes 5h-ILLEGAL REQUESTA MODE SELECT parameter list sent to the drive contains allowed to execute. In other words, some commands can 6h-UNIT ATTENTIONpersistent reservation using the PERSISTENT RESERVE OUT 32 initiators to register, using PERSISTENT RESERVE OUTAction WRITE BUFFER or MAINTENANCE OUT command service action removed all reservations and the persistentA PERSISTENT RESERVE OUT command was executed A SET DEVICE IDENTIFIER command has been successful7h-DATA PROTECTION Action 8h-BLANK CHECK related to a missing EOD data set. The most likely cause Bh-ABORTED COMMANDREAD BUFFER command 76 Sense keys and codes Dh-VOLUME OVERFLOWA WRITE or WRITE FILEMARKS command has encountered 3. Allow the user to try recovery Typical escalation procedure1. Retrieve fault information 4. Allow the user to reset devicesMonitoring the condition of the drive and media Supporting TapeAlertFlags TypePage Page Page Page Page Page Page Designing software to use the TapeAlert log TapeAlert modelsTapeAlert informational exception usage model Reading the TapeAlert logTapeAlert polling usage model Supporting OBDR One-Button Disaster Recovery OBDRResponding to the ‘Clean’ LED Providing pass-through mode Requirements for drivers and logical device managersGlossary see ”read-while-write” Index Page Page HP restricted