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

Page 81

	Flag	Type	Set	Recommended Host Message	Cause
10	No removal	I		You cannot eject the cartridge	A manual or software
				because the tape drive is in use.	unload was attempted when
				Wait until the operation is complete	Prevent Medium Removal
				Wait until the operation is complete	was in force.
				before ejecting the cartridge.
11	Cleaning media	I		The tape in the drive is a cleaning	A cleaning cartridge is
				cartridge.	loaded in the drive.

12	Unsupported	I		You have tried to load a cartridge of	Attempted load of an
	format			a type that is not supported by this	unsupported tape format.
				drive.

13	Recoverable	C		The operation has failed because the	The tape has snapped or
	mechanical			tape in the drive has experienced a	suffered some other
	cartridge failure			mechanical failure:	mechanical failure in the
				1. Discard the old tape.	drive, but the tape can still
				1. Discard the old tape.	be ejected.
				2. Restart the operation with a	be ejected.
				2. Restart the operation with a
				different tape.

14	Unrecoverable	C		The operation has failed because the	The tape has snapped or
	mechanical			tape in the drive has experienced a	suffered some other
	cartridge failure			mechanical failure:	mechanical failure in the
				1. Do not attempt to extract the tape	drive and the tape cannot
				1. Do not attempt to extract the tape	be ejected.
				cartridge.
				2. Call the tape drive supplier’s
				helpline.

15	Memory chip in	W		The memory in the tape cartridge has	The LTO-CM chip has failed
	cartridge failure			failed, which reduces performance.	in cartridge.
				Do not use the cartridge for further
				write operations.

16	Forced eject	C		The operation has failed because the	A manual or forced eject
				tape cartridge was manually	occurred while the drive was
				de-mounted while the tape drive was	writing or reading.
				actively writing or reading.

17	Read-only	C		You have loaded a cartridge of a	A write command has been
	format			type that is read-only in this drive.	attempted to a tape whose
				The cartridge will appear as	format is read-only in this
				write-protected.	drive.

18	Tape directory	W		The tape directory on the cartridge	The drive was powered
	corrupted on			has been corrupted. File search	down with a tape loaded, or
	load			performance will be degraded. The	a permanent error prevented
				tape directory can be rebuilt by	the tape directory being
				reading all the data on the cartridge.	updated.

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

Image 81

Contents LTO 4 FC, SCSI and SAS drives volume 2 software integrationHP LTO Ultrium tape drives technical reference manual HP restrictedLegal and notice information 1 Designing backup applications Contents2 Configuration and initialization 3 Use of tapes4 Factors affecting performance 5 Supporting Ultrium features7 Exception handling 6 Sense keys and codesHP restricted Documentation map Related documentsDocuments specific to HP Ultrium drives Drives-generalOperation Installation and configurationCartridges InterfaceDealing with errors Maintenance and troubleshootingGeneral documents and standardization LTO Ultrium featuresNon-immediate commands 1 Designing backup applicationsOptimizing performance Large data transfer sizeManaging the use of tapes Cleaning tape headsInformation in Cartridge Memory Monitoring tape useDiagnostic logs Design goals for LTO backup applicationsTapeAlert 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 MODE SENSE Using Cartridge Memory attributes3 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 WORM media Changes to SCSI commandsHow WORM media works New additional sense codes and TapeAlert flagsERASE commands rejected Error Usage pageSET 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 Corrective action RWW retry countsWays of optimizing performance 4 Factors affecting performanceDetecting the drive’s speed Ensuring the recommended minimum transfer sizesUsing the Performance Log page for diagnosing problems Using Cartridge Memory instead of tape headersTime-out values Media type identificationRecommended support of log pages Factors affecting performanceHost-related factors Recommendation Examplewhere possible or a reasonably sized RAID system. More disks means makes sense to split heavily used FC cards across separate PCI bussesDo not interleave write commands with other commands, such as READ Drive-related factorsFormat-related factors Page 34 Factors affecting performance Cartridge Memory LTO-CM 5 Supporting Ultrium featuresAutomation 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 Backward compatibility New features in ACISCSI command Encryption support Supporting the ACI protocol Further detailsRecommended ACI time-out values 42 Supporting Ultrium featuresTreatment of reserved fields Recommended power-up sequenceRecommended load-unload configuration Recommended Get Drive Status polling frequency Firmware upgrade via tapeACI protocol communications retry Upgrading the drive firmwareFirmware upgrade via ACI Firmware upgrade via the primary host interfaceLibrary firmware upgrade via tape Handling irregular cartridgesExpired cleaning cartridge HP-configured or Universal Cleaning cartridge HP-configured or UniversalNon-HP Ultrium 1 cleaning cartridge Unreadable data cartridgeData cartridge with unreadable CM Valid firmware upgrade cartridgeCartridge fails to seat or load Cartridge cannot be loadedCleaning Frequently asked questionsInvalid firmware upgrade cartridge Is there separate firmware for drives intended to go into libraries?Resetting drives Backup softwareResetting via the ACI Reset command Resetting using the ACIRSTL lineControlling data compression Accessing Cartridge Memory without threading the tapeOther mode page information Buffer size at EW-EOMWrite delay time Rewind on resetPartition size 52 Supporting Ultrium featuresSense keys-actions to take 6 Sense keys and codesAction Console MessageFor additional sense codes, see “3h-MEDIUM ERROR” on “3h-MEDIUM ERROR” on page 62 . Also see the Media Accesslog the error, terminate I/O to the drive, and pass the appropriate error to the calling applicationConsole Message ActionAction Console MessageAction Physical Additional sense codes-actions to takeEnd-of-Tape reached, unable to fit0h-NO SENSE 2h-NOT READY 1h-RECOVERED ERRORLUN not accessible, port in The software must issue a LOAD before media accessThe 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 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 5h-ILLEGAL REQUEST A MODE SELECT parameter list sent to the drive contains68 Sense keys and codes persistent reservation using the PERSISTENT RESERVE OUT 6h-UNIT ATTENTIONallowed to execute. In other words, some commands can 32 initiators to register, using PERSISTENT RESERVE OUTAction A PERSISTENT RESERVE OUT command was executed service action removed all reservations and the persistentWRITE BUFFER or MAINTENANCE OUT command A SET DEVICE IDENTIFIER command has been successful7h-DATA PROTECTION Action 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 1. Retrieve fault information Typical escalation procedure3. Allow the user to try recovery 4. Allow the user to reset devicesSupporting TapeAlert Monitoring the condition of the drive and mediaType FlagsPage Page Page Page Page Page Page TapeAlert models Designing software to use the TapeAlert logReading the TapeAlert log TapeAlert polling usage modelTapeAlert informational exception usage model One-Button Disaster Recovery OBDR Responding to the ‘Clean’ LEDSupporting OBDR Requirements for drivers and logical device managers Providing pass-through modeGlossary see ”read-while-write” Index Page Page HP restricted