IBM LTO1 Tape Drive Firmware Update - IBM Servers

Download Description

• New IBM xSeries firmware and device driver file naming convention

Note: You now have two ways of downloading files with the *.sh extension. You can use either the IBM Download Director, or the HTTP protocol to download these files. Do NOT use FTP as this will only cause the file to open your browser.

Change history

Number Description

1. A new function is added allowing customer to enable a periodic clean cycle of
   every 40 full file passes.
2. A particular write command sequence can cause write error due to a flag being reset unexpectedly.
3. On a cartridge with invalid End of Data, less than 4 datasets recorded, SILI bit
   on in variable length mode and an over length condition, the first attempt to
   read will result in a permanent error.
4. Perform alternate gain adjustments and retry to CM read when initial read fails.
5. The write errors corrected counter is incorrectly decremented when a write
   permanent error occurs.
6. When write command completes with an error, the flag indicating data to be
   flushed from buffer is cleared and incorrect good status returned.
7. The firmware incorrectly translates status from a write permanent error which
   may result in a stuck cartridge.
8. The Read Position command will intermittently report incorrect values after a
   buffer flush.
9. When in Early Warning area and an error is encountered and recovered, a Write FileMark of zero will return an error.
10. If an internal abort is issued in a READ operation while Error Recovery is in
    progress, a hang will result.
11. Add flag to indicate that Hardware error has been reported during Diagnostics.
12. Misreporting Locate Failure with error code 4 instead of 6.
13. A check condition will incorrectly be reported if a Report Density
    command is issued with media field set to 1 and a corrupted cartridge is loaded.
14. Certain servo errors can cause the drive to randomly skip sections of tape
    during writing. If there were numerous “old” datasets in this area during a read
    operation, the drive could not find the next Valid dataset. A permanent read
    error would occur, even though the next valid dataset was written correctly.
15. Unexpectedly large lateral movement of tape during drive start/stop motion
    would cause the drive to be unable to find servo signals. This would cause
    various write errors, including permanent write errors.
16. Drive diagnostic ‘F’ was changed help diagnose drive issues which affect
    cartridge capacity.
17. A cartridge with a corrupt Cartridge Memory would cause the drive to hang and
    FSC 2025, 2076, 2095 might be reported by the drive.
18. TapeAlert flag 22 is not cleared when Cleaner Cartridge is removed.