HP LTO 4 FC manuals
Computer Equipment > Computer Drive
When we buy new device such as HP LTO 4 FC we often through away most of the documentation but the warranty.
Very often issues with HP LTO 4 FC begin only after the warranty period ends and you may want to find how to repair it or just do some service work.
Even oftener it is hard to remember what does each function in Computer Drive HP LTO 4 FC is responsible for and what options to choose for expected result.
Fortunately you can find all manuals for Computer Drive on our side using links below.
96 pages 920.92 Kb
3 Contents7 Related documentsDocumentation map8 Installation and configurationDetermining the configuration External drives In libraries In servers In tape arrays Linux configuration Modes of usage OpenVMS configuration Optimizing performance UNIX configuration Operation Cartridges Cartridge Memory (LTO-CM) Cartridges Managing the use of cartridges Use of cartridges Interface Commands Error codes 9 ImplementationInterpreting sense data Messages Mode pages —seethe MODE SENSE command Pre-executionchecks Responding to sense keys and ASC/Q Sense keys and ASC/Q —seeREQUEST SENSE command Task management functions Maintenance and troubleshooting Cleaning In tape arrays) Monitoring drive and tape condition Software troubleshooting techniques Dealing with errors Handling errors Logs—seethe LOG SENSE command Recovering from write and read errors Software response to error correction Software response to logs TapeAlert log 10 General documents and standardization11 1 Designing backup applications15 2 Configuration and initialization19 3 Use of tapes27 4 Factors affecting performanceWays of optimizing performanceDetecting the drive’s speed Ensuring the recommended minimum transfer sizes Media type identification Using Cartridge Memory instead of tape headers Using the Performance Log page for diagnosing problems 28 Time-outvalues29 Recommended support of log pagesFactors affecting performance 35 5 Supporting Ultrium features53 6 Sense keys and codesSense keys—actionsto take55 This indicates that the current I/O operation has failed due to ahardware failure.The FRU code in the sense data should indicate which part of the hardware is bad. The drive should not be used again until corrective action has been taken. Specific recovery depends on the operating system and application For additional sense codes, see “4h—HWERROR” on page Console Message: Tape drive hardware failure “5h—ILLEGAL REQUEST” on page Console Message: Illegal SCSI command requested “6h—UNIT ATTENTION” on page Console Message: Tape drive operating conditions may have changed 57 Additional sense codes—actionsto take58 0h—NOSENSE59 1h—RECOVEREDERROR2h—NOTREADY61 A medium-accesscommand has been sent to the driveinstalled while a cleaning cartridge was loaded Terminate the current I/O, and return the appropriate error Send a message to the console indicating that a cleaning cartridge is in the drive and a cleaning cycle is being performed Prompt the user to wait for the cartridge to be ejected. In a library, the cartridge will be ejected when requested by the library or host. In an internal or external single drive, the cartridge will be ejected automatically Prompt the user to proceed with the next application-specificactivity Log the cleaning cycle in the system log Medium not present A medium-accesscommand has been received when no cartridge is in the drive As a minimum, issue a message to the console indicating that a drive is present but no tape is loaded Medium not present A media access command has been received when the Media Auxiliary Memory tape has been loaded but not threaded. This will be accessible reported if the hold bit of the LOAD CDB was set or the Autoload field in the Control mode page is non zero Logical unit has not This is set during power-upwhen it is not possible to self-configuredyet send medium-accesscommands to the drive because complete, the additional sense changes to 3A 00h 04 01h or 04 02h depending on whether a cartridge was present at power-on Issue a message to the console indicating that the drive is powering up Effectively poll the drive until the drive transitions to another state, at which point either execute the command or terminate the I/O 62 3h—MEDIUMERROR63 Unrecovered read errorA read from tape has failed. This is probably due to bad media, but may be hardware-related write has occurred Determine whether the error is deferred, and report the last successful operation and the failed operation to the calling application Log the error and all recovery actions in the system log Recovery action is as follows: Use Log Sense to find the age and state of the tape drive or replace the tape If the fault is drive-related,ask the user to retry the operation after the drive has been cleaned If the fault is with the media, prompt the user to back up the data to a new tape, restart the application and discard the current tape An error has occurred while attempting to write to MAM read error The cartridge should not be used for further backups but should be able to be used for restoring data Recorded entity not found A SPACE or LOCATE command failed because of the drive could not find the target of the operation because of a format violation Terminate the I/O and return the appropriate error Send a message to the console indicating that EOD could not be found because the tape has a corrupt format Prompt the user to back up the data to another tape and discard the current one 65 Cleaning failureA cleaning operation was attempted but could not be completed for some reason Use another cleaning cartridge because the current one has expired 30 0D WORM medium—integrity The drive has detected an inconsistency when performing check failed an integrity check on a WORM cartridge. The cartridge may have been tampered with. Data can be read from the cartridge by setting the WTRE bit in the Device Configuration mode page. The event should be logged for audit purposes drive has detected an inconsistency in the WORM cartridge that indicates it may have been tampered with Alert the user that the cartridge may have been tampered with Log the incident in the system log for audit purposes Initiate WTRE-controlledEOD with clear warnings to the end-userthat the data may have been tampered Medium format corrupted READ or SPACE has tried to read data that is in a format that is recognized but which is not valid a problem with the format of the tape in the drive Prompt the user to eject the media and insert a valid Ultrium tape 67 4h—HWERROR68 5h—ILLEGALREQUEST69 6h—UNITATTENTION71 When operating the drive in this type of environment, thefollowing actions should occur: 1. The calling application receiving this code should issue a MODE SENSE command requesting the drive to return all parameters 2. The application should check those parameters over which it has configuration control, to ensure that the current configuration of the drive does not conflict with what the application expects 3. If it finds discrepancies, the application can either reconfigure the drive to the original values, or halt and report an error 4. If an error is reported, a console message must be displayed, and information logged to the system log Log parameters changed The Log parameters for the drive have been changed by an initiator other than the one issuing the command Reservations pre-empted A PERSISTENT RESERVE OUT command with the Clear reservation Reservations released A PERSISTENT RESERVE OUT command executed. The original persistent reservation has been replaced with another of a different type or removed completely Registrations pre-empted command was executed which removed all registrations Data encryption parameters The encryption parameters that this initiator was using changed by another have been modified by another initiator initiator changed by vendor specific have been modified because of a vendor specific event event (such as tape unload or reservation released) Firmware upgraded The firmware in the drive has just been changed by a command Firmware Update Cartridge, ADI or ACI Device identifier changed Reported LUNs data has changed 72 7h—DATAPROTECTION73 30 0CWORM—overwriteattempted A write operation could not be executed because an overwrite has been attempted on a WORM cartridge. This may be because an overwrite backup was specified instead of an appended backup Send a message to the console indicating that an attempt has been made to overwrite on a WORM cartridge the operation to an appended backup WORM—integritycheck An attempt has been made to write to a WORM cartridge failed its integrity has detected an inconsistency with the WORM cartridge that indicates that it may have been tampered Advise the user that the tape may have been tampered with and they should use a different cartridge Security error Generic security (encryption/decryption) error. For example, the Decryption mode is set to RAW and the drive has been asked to read, but the hardware does not allow this Decryption mode on the current block Unable to decrypt data The drive encountered encrypted data while reading, but decryption mode is not enabled Send a command with Decryption Mode set to Decrypt or Mixed, and the Key field specifying the correct decryption key Unencrypted data The decryption mode is enabled but the drive encountered encountered while decrypting non-encrypteddata while reading Decryption Mode set to Disable; alternatively with Decryption Mode set to Mixed and the Key field specifying the correct decryption key 74 8h—BLANKCHECK75 Bh—ABORTEDCOMMAND76 Dh—VOLUMEOVERFLOW77 7 Exception handlingTypical escalation procedure 78 Monitoring the condition of the drive and mediaSupporting TapeAlert79 FlagsThe 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 Information A suggestion to the user Warning The user is advised to take action. Performance or data may be at risk otherwise Critical Take action immediately Flag Recommended Host Message Cause Flags for Tape Drive Write/Read Management Read warning 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 Write warning writing data. No data has been lost trouble writing Hard error 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 81 No removalYou 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 was in force before ejecting the cartridge Cleaning media The tape in the drive is a cleaning A cleaning cartridge is loaded in the drive Unsupported 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 Recoverable 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 be ejected 2. Restart the operation with a Unrecoverable 1. Do not attempt to extract the tape drive and the tape cannot 2. Call the tape drive supplier’s Memory chip in The memory in the tape cartridge has The LTO-CMchip has failed failed, which reduces performance in cartridge Do not use the cartridge for further write operations Forced eject A manual or forced eject tape cartridge was manually occurred while the drive was de-mountedwhile the tape drive was writing or reading actively writing or reading Read-only You have loaded a cartridge of a A write command has been type that is read-onlyin this drive attempted to a tape whose The cartridge will appear as format is read-onlyin this write-protected Tape directory 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 83 RetensionThe tape drive has requested a The drive is having trouble requested retension operation reading or writing that will be resolved by a retension cycle Dual-port A redundant interface port on the One of the interface ports in interface error tape drive has failed a dual-portconfiguration (in other words, Fibre Channel) has failed Flags for Tape Drive Hardware Errors Cooling fan A tape drive cooling fan has failed A fan inside the drive mechanism or enclosure has failed Power supply A redundant power supply has failed A redundant PSU has failed inside the tape drive enclosure inside the tape drive Check the enclosure user’s manual for instructions on replacing the failed power supply Power The tape drive power consumption is The tape drive power consumption outside the specified range consumption is outside the specified range Preventive maintenance of the tape The drive requires preventive maintenance drive is required maintenance (not cleaning) Check the tape drive user’s manual for preventive maintenance tasks or call the tape drive supplier’s helpline Hardware A The tape drive has a hardware fault: The drive has a hardware 1. Eject the tape or magazine fault from which it can recover through a reset Reset the drive Restart the operation Hardware B 1. Turn the tape drive off and then fault that is not read/write related or that it can recover on again from through a power cycle 3. If the problem persists, call the drive fails its internal power-on self-tests.It is not cleared internally until the drive is powered off 85 The tape directory on the tapeAn error has occurred invalid at cartridge just unloaded has been preventing the tape directory unload corrupted. File search performance being updated on unload will be degraded. The tape directory can be rebuilt by reading all the data Tape system The tape just unloaded could not Write errors occurred while area write write its system area successfully: writing the system area on Copy the data to another tape unload Discard the old cartridge The tape system area could not be Read errors occurred while area read read successfully at load time reading the system area on load No start of data The start of data could not be found The tape has been on the tape: damaged, bulk erased, or is Check that you are using the of an incorrect format correct format tape Discard the tape or return the tape to your supplier Loading failure The drive is unable to load media cannot be loaded and the cassette and thread the threaded tape Remove the cartridge, inspect it as specified in the product manual, and retry the operation If the problem persists, call the tape drive supplier’s help line The drive is unable to load failure tape cannot be unloaded: unload the tape Do not attempt to extract the tape Call the tape driver supplier’s help line 87 Designing software to use the TapeAlert log89 One-ButtonDisaster Recovery (OBDR)Responding to the ‘Clean’ LED 90 Providing pass-throughmodeRequirements for drivers and logical device managers 91 Glossary92 offlinethat do not require tape motion online The drive is online when a tape is loaded. The host has access to all command tests RWW see ”read-while-write” read-while-write RWW improves data integrity by reading data immediately after it is written and writing the data again if an error is found TapeAlert Write Once, Read Many 93 Index95 parity error 75 partition size 52 pass-throughmode 38, 90 performance factorsdrive-related 31 format-related 32 host-related 29 performance log polling frequency, Get Drive Status 45 power-upsequence problems, predicting 13, 78 product ID product revision level 15 read errors reading the TapeAlert log 88 remaining capacity 20 reserved fields reset revision level 15, 16 RWW retries 89 retry counts SCSI pass-throughmode 38 sense keys ABORTED COMMAND 56, 75 BLANK CHECK 56, 74 DATA PROTECTION 56, 72 HW ERROR 55 ILLEGAL REQUEST 55 SET CAPACITY command 21 slave to a library controller 37 speed, detecting status of tape support for additional LUNs Tape Capacity log 20 tape heads, cleaning 12 tape integrity 24 TapeAlert informational exception usage model 88 polling usage model TapeAlert log 13, 25, 78, 92 reading using 87 tapemarks, use of 32 tapes use of 12 using 19 WORM tests, read/write 13 time-outvalues 28 transfer size 11 effect on performance 32 troubleshooting Ultrium finding the format generation 16 supporting features UNIX drivers 15 upgrading firmware 45 Use Cleaning Tape LED variable-lengthblock mode 11 vendor ID Windows drivers 15 WORM 92 WORM media 22 write errors 62, 66 write-protect
Also you can find more HP manuals or manuals for other Computer Equipment.