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

Page 79

Flags

The following table lists the flags that could potentially be supported in tape drives. Of these, flags 3,4,5,6,20,22 and 31 are mandatory for drives such as Ultrium drives that support cleaning cartridges.

The flags are grouped into the following sections:

Flags 1 to 19: For tape drive write/read management

Flags 20 to 25: For cleaning management

Flags 26 to 39: For tape drive hardware errors

Flags 50 to 60: For additional tape drive errors

For each flag, the message that the host software should display to the user is given, together with the cause of the flag being set. The Type column classifies the flags by seriousness into the following three groups:

I

Information

A suggestion to the user.

W

Warning

The user is advised to take action. Performance or data

 

 

may be at risk otherwise.

 

 

 

C

Critical!

Take action immediately.

The Set column indicates if the flag can be set by LTO 4 drives. The other flags are supported but never set.

 

Flag

Type

Set

Recommended Host Message

Cause

Flags for Tape Drive Write/Read Management

 

1

Read warning

W



The tape drive is having problems

The drive is having severe

 

 

 

 

reading data. No data has been lost,

trouble reading.

 

 

 

 

but there has been a reduction in the

 

 

 

 

 

capacity of the tape.

 

 

 

 

 

 

 

2

Write warning

W

 

The tape drive is having problems

The drive is having severe

 

 

 

 

writing data. No data has been lost,

trouble writing.

 

 

 

 

but there has been a reduction in the

 

 

 

 

 

capacity of the tape.

 

 

 

 

 

 

 

3

Hard error

W



The operation has stopped because

This flag is set for any

 

 

 

 

an error has occurred while reading

unrecoverable

 

 

 

 

or writing data which the drive

read/write/positioning

 

 

 

 

cannot correct.

error, and is cleared

 

 

 

 

 

internally when the tape is

 

 

 

 

 

ejected. The flag is set as an

 

 

 

 

 

explanation of the error in

 

 

 

 

 

conjunction with one of the

 

 

 

 

 

recovery action flags 4, 5,

 

 

 

 

 

or 6.

 

 

 

 

 

 

HP LTO Ultrium 4 drives technical reference manual, volume 2: software integration 79 HP restricted

Image 79
Contents HP restricted volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP LTO Ultrium tape drives technical reference manualLegal and notice information 3 Use of tapes Contents1 Designing backup applications 2 Configuration and initialization4 Factors affecting performance 5 Supporting Ultrium features7 Exception handling 6 Sense keys and codesHP restricted Drives-general Related documentsDocumentation map Documents specific to HP Ultrium drivesInterface Installation and configurationOperation CartridgesDealing with errors Maintenance and troubleshootingGeneral documents and standardization LTO Ultrium featuresLarge data transfer size 1 Designing backup applicationsNon-immediate commands Optimizing performanceMonitoring tape use Cleaning tape headsManaging the use of tapes Information in Cartridge MemoryDisplaying drive information Design goals for LTO backup applicationsDiagnostic logs TapeAlertInclude the capability to download firmware Inquiry string recovery 2 Configuration and initializationOperating system drivers 16 Configuration and initialization ExampleSCSI protocol, regardless of transport or interface type Enabling additional LUN support Support for additional LUNSupporting additional LUNs 18 Configuration and initialization LTO cartridge memory Using Cartridge Memory attributesUsing MODE SENSE 3 Use of tapesFinding the remaining capacity Tape status and capacityInterpreting Log Sense data Command descriptor block Using the SET CAPACITY commandCDB fields New additional sense codes and TapeAlert flags Changes to SCSI commandsWORM media How WORM media worksRe-writing media labels Error Usage pageERASE commands rejected SET CAPACITY commandBehavior with a missing or inconsistent EOD value Using CM to check tape integrityUnique media identifier Load count Responding to Cartridge Memory dataBarcode support Corrective action RWW retry countsEnsuring the recommended minimum transfer sizes 4 Factors affecting performanceWays of optimizing performance Detecting the drive’s speedMedia type identification Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Time-out valuesFactors affecting performance Recommended support of log pagesHost-related factors makes sense to split heavily used FC cards across separate PCI busses ExampleRecommendation where possible or a reasonably sized RAID system. More disks meansDo not interleave write commands with other commands, such as READ Drive-related factorsFormat-related factors Page 34 Factors affecting performance Further information 5 Supporting Ultrium featuresCartridge Memory LTO-CM Automation interfaceAutomation/Device Interface ADI Modes of usage through ACI Automation Control Interface ACISlave to a library controller ACI commands that affect drive streaming performance ACI command setSCSI pass-through mode Backward compatibility New features in ACISCSI command Encryption support 42 Supporting Ultrium features Further detailsSupporting the ACI protocol Recommended ACI time-out valuesTreatment of reserved fields Recommended power-up sequenceRecommended load-unload configuration Upgrading the drive firmware Firmware upgrade via tapeRecommended Get Drive Status polling frequency ACI protocol communications retryHandling irregular cartridges Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Library firmware upgrade via tapeUnreadable data cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Non-HP Ultrium 1 cleaning cartridgeCartridge cannot be loaded Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge fails to seat or loadIs there separate firmware for drives intended to go into libraries? Frequently asked questionsCleaning Invalid firmware upgrade cartridgeResetting using the ACIRSTL line Backup softwareResetting drives Resetting via the ACI Reset commandBuffer size at EW-EOM Accessing Cartridge Memory without threading the tapeControlling data compression Other mode page information52 Supporting Ultrium features Rewind on resetWrite delay time Partition sizeConsole Message 6 Sense keys and codesSense keys-actions to take Actionerror to the calling application “3h-MEDIUM ERROR” on page 62 . Also see the Media AccessFor additional sense codes, see “3h-MEDIUM ERROR” on log the error, terminate I/O to the drive, and pass the appropriateConsole Message ActionConsole Message Actionpage reached, unable to fit Additional sense codes-actions to takePhysical End-of-Tape0h-NO SENSE 2h-NOT READY 1h-RECOVERED ERROR60 Sense keys and codes The software must issue a LOAD before media accessLUN not accessible, port in The command cannot be executed because the specifiedmechanism tests are being executed. When the tests are A READ , SPACE , WRITE or WRITE FILEMARKS command 3h-MEDIUM ERROR62 Sense keys and codes and the drive. Based on this, ask the user to clean the Send a console message that an unrecovered error on64 Sense keys and codes Send a message to the console indicating that there is 66 Sense keys and codes The current command such as READ, SPACE, REWIND4h-HW ERROR A MODE SELECT parameter list sent to the drive contains 5h-ILLEGAL REQUEST68 Sense keys and codes 32 initiators to register, using PERSISTENT RESERVE OUT 6h-UNIT ATTENTIONpersistent reservation using the PERSISTENT RESERVE OUT allowed to execute. In other words, some commands canAction A SET DEVICE IDENTIFIER command has been successful service action removed all reservations and the persistentA PERSISTENT RESERVE OUT command was executed WRITE BUFFER or MAINTENANCE OUT command7h-DATA PROTECTION Action 8h-BLANK CHECK READ BUFFER command Bh-ABORTED COMMANDrelated to a missing EOD data set. The most likely cause A WRITE or WRITE FILEMARKS command has encountered Dh-VOLUME OVERFLOW76 Sense keys and codes 4. Allow the user to reset devices Typical escalation procedure1. Retrieve fault information 3. Allow the user to try recoverySupporting TapeAlert Monitoring the condition of the drive and mediaType FlagsPage Page Page Page Page Page Page TapeAlert models Designing software to use the TapeAlert logTapeAlert polling usage model Reading the TapeAlert logTapeAlert informational exception usage model Responding to the ‘Clean’ LED One-Button Disaster Recovery OBDRSupporting OBDR Requirements for drivers and logical device managers Providing pass-through modeGlossary see ”read-while-write” Index Page Page HP restricted