HP LTO 4 FC, LTO 4 SCSI manual Data cartridge with unreadable CM, Cartridge fails to seat or load

Page 48

Data cartridge with unreadable CM

If the Cartridge Memory cannot be read, the drive assumes that the cartridge is not supported. If the cartridge is loaded into the drive, it will be placed at the ready-to-eject point with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Cartridge Type = ‘Unknown’, and Tape Activity = ‘Idle’. TapeAlert flag 0Fh will be set.

Cartridge fails to seat or load

If a cartridge fails to seat or load, it will be placed at the ready-to-eject position with the Cartridge Present, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Tape Activity = ‘Idle’. TapeAlert flag 04h will be set. If the cartridge type is recognized, this will be indicated in the Cartridge Type field, otherwise the field will indicate Cartridge Type = ‘Unknown’.

Cartridge cannot be loaded

HP recommends that GOOD status is not returned to the host for the MOVE MEDIUM command until the library controller has seen the Cartridge Load bit in the Get Drive Status RDATA set to 1. If the library controller does not see this bit set, HP recommends invoking an appropriate load re-try algorithm. After re-trying the load, if this bit is still not set to 1, assume that there is a problem with the cartridge. HP recommends that the library controller responds to the MOVE MEDIUM command with CHECK CONDITION, a sense key of Not Ready and additional sense of 5300 (media load or eject failure), and then moves the cartridge back to the source element. If the Drive Error bit is set to 1 in the Get Drive Status RDATA, appropriate actions should be taken.

Valid firmware upgrade cartridge

If a firmware upgrade cartridge with a valid firmware image is loaded, and neither the library controller nor the host knows that the cartridge is a firmware upgrade cartridge, what occurs depends on the Upgrade Protect bit in the Set Drive Configuration command.

Upgrade Protect = 1 If the Upgrade Protect bit in the Set Drive Configuration command is set to 1, it is assumed that the Upgrade bit in the Load command will be zero and no firmware upgrade will be performed. The cartridge will be placed at the ready-to-eject position with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Cartridge Type = ‘Firmware Upgrade’, and Tape Activity = ‘Idle’. TapeAlert flag 10h will be set.

Upgrade Protect = 0 If the Upgrade Protect bit in the Set Drive Configuration command is 0, a firmware upgrade will be performed on the drive. While the drive is preparing to upgrade the firmware, it will report Tape Activity = “Code Update in Progress”. When actually upgrading the firmware the drive will not respond to ACI commands. After the firmware upgrade has completed the drive will reset and send out an ENQ byte over ACI.

It is recommended that the library controller follows the normal power-up ACI command sequence after receiving the ENQ byte to ensure that the drive is configured correctly and to verify the firmware version and ACI version.

48 Supporting Ultrium features

HP restricted

Page 47 Page 49
Image 48
Page 47 Page 49
Contents volume 2 software integration LTO 4 FC, SCSI and SAS drivesHP LTO Ultrium tape drives technical reference manual HP restrictedLegal and notice information Contents 1 Designing backup applications2 Configuration and initialization 3 Use of tapes5 Supporting Ultrium features 4 Factors affecting performance6 Sense keys and codes 7 Exception handlingHP restricted Related documents Documentation mapDocuments specific to HP Ultrium drives Drives-generalInstallation and configuration OperationCartridges InterfaceMaintenance and troubleshooting Dealing with errorsLTO Ultrium features General documents and standardization1 Designing backup applications Non-immediate commandsOptimizing performance Large data transfer sizeCleaning tape heads Managing the use of tapesInformation in Cartridge Memory Monitoring tape useDesign goals for LTO backup applications Diagnostic logsTapeAlert Displaying drive informationInclude the capability to download firmware 2 Configuration and initialization Inquiry string recoveryOperating system drivers Example 16 Configuration and initializationSCSI protocol, regardless of transport or interface type Support for additional LUN Enabling additional LUN supportSupporting additional LUNs 18 Configuration and initialization Using Cartridge Memory attributes Using MODE SENSE3 Use of tapes LTO cartridge memoryTape status and capacity Finding the remaining capacityInterpreting Log Sense data Using the SET CAPACITY command Command descriptor blockCDB fields Changes to SCSI commands WORM mediaHow WORM media works New additional sense codes and TapeAlert flagsError Usage page ERASE commands rejectedSET CAPACITY command Re-writing media labelsUsing CM to check tape integrity Behavior with a missing or inconsistent EOD valueUnique media identifier Responding to Cartridge Memory data Load countBarcode support RWW retry counts Corrective action4 Factors affecting performance Ways of optimizing performanceDetecting the drive’s speed Ensuring the recommended minimum transfer sizesUsing Cartridge Memory instead of tape headers Using the Performance Log page for diagnosing problemsTime-out values Media type identificationRecommended support of log pages Factors affecting performanceHost-related factors Example Recommendationwhere possible or a reasonably sized RAID system. More disks means 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 5 Supporting Ultrium features Cartridge Memory LTO-CMAutomation interface Further informationAutomation/Device Interface ADI Automation Control Interface ACI Modes of usage through ACISlave to a library controller ACI command set ACI commands that affect drive streaming performanceSCSI pass-through mode New features in ACI Backward compatibilitySCSI command Encryption support Further details Supporting the ACI protocolRecommended ACI time-out values 42 Supporting Ultrium featuresRecommended power-up sequence Treatment of reserved fieldsRecommended load-unload configuration Firmware upgrade via tape Recommended Get Drive Status polling frequencyACI protocol communications retry Upgrading the drive firmwareFirmware upgrade via the primary host interface Firmware upgrade via ACILibrary firmware upgrade via tape Handling irregular cartridgesCleaning cartridge HP-configured or Universal Expired cleaning cartridge HP-configured or UniversalNon-HP Ultrium 1 cleaning cartridge Unreadable data cartridgeValid firmware upgrade cartridge Data cartridge with unreadable CMCartridge fails to seat or load Cartridge cannot be loadedFrequently asked questions CleaningInvalid firmware upgrade cartridge Is there separate firmware for drives intended to go into libraries?Backup software Resetting drivesResetting via the ACI Reset command Resetting using the ACIRSTL lineAccessing Cartridge Memory without threading the tape Controlling data compressionOther mode page information Buffer size at EW-EOMRewind on reset Write delay timePartition size 52 Supporting Ultrium features6 Sense keys and codes Sense keys-actions to takeAction Console Message“3h-MEDIUM ERROR” on page 62 . Also see the Media Access For additional sense codes, see “3h-MEDIUM ERROR” onlog the error, terminate I/O to the drive, and pass the appropriate error to the calling applicationAction Console MessageAction Console Messagepage Additional sense codes-actions to take PhysicalEnd-of-Tape reached, unable to fit0h-NO SENSE 1h-RECOVERED ERROR 2h-NOT READYThe software must issue a LOAD before media access LUN not accessible, port inThe command cannot be executed because the specified 60 Sense keys and codesmechanism tests are being executed. When the tests are 3h-MEDIUM ERROR A READ , SPACE , WRITE or WRITE FILEMARKS command62 Sense keys and codes 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 5h-ILLEGAL REQUEST A MODE SELECT parameter list sent to the drive contains68 Sense keys and codes 6h-UNIT ATTENTION persistent reservation using the PERSISTENT RESERVE OUTallowed to execute. In other words, some commands can 32 initiators to register, using PERSISTENT RESERVE OUTAction service action removed all reservations and the persistent A PERSISTENT RESERVE OUT command was executedWRITE BUFFER or MAINTENANCE OUT command A SET DEVICE IDENTIFIER command has been successful7h-DATA PROTECTION Code 8h-BLANK CHECK Bh-ABORTED COMMAND READ BUFFER commandrelated to a missing EOD data set. The most likely cause Dh-VOLUME OVERFLOW A WRITE or WRITE FILEMARKS command has encountered76 Sense keys and codes Typical escalation procedure 1. Retrieve fault information3. Allow the user to try recovery 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 modelsReading the TapeAlert log TapeAlert polling usage modelTapeAlert informational exception usage model One-Button Disaster Recovery OBDR Responding to the ‘Clean’ LEDSupporting OBDR Providing pass-through mode Requirements for drivers and logical device managersGlossary see ”read-while-write” Index Page Page HP restricted
Top Page Image Contents