Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What is the latest version of firmware for IBM LTO GEN DRIVE
- Thread starter tuka
- Start date
- Thread starter
- #2
tapedrivedoctor
Technical User
hi,
the latest firmware is 4561, and yes there is a list of problems fixed by this firmware, it is in pdf format.
the latest firmware is 4561, and yes there is a list of problems fixed by this firmware, it is in pdf format.
- Thread starter
- #4
tapedrivedoctor
Technical User
hope this helps
IBM has just released an LTO Gen1 firmware update, 4561, that is intended to,
among other things, increase overall reliability, improve tape handling, further
reduce any possibility of error, and provide continued enhancements to diagnostic
capabilities. Firmware fixes since 3CKE follow:
14303 Periodic cleaning regimen required: A new function is added allowing
customer to enable a periodic clean cycle of every 40 full file passes. This is
controlled by the Behavior Configuration Mode Page 2Fh.
14357 Buffer Overflow because the Pause is ignored: A particular write
command sequence can cause write error due to a flag being reset unexpectedly.
14408 Permanent Read error on 1st read attempt: On a cartridge with
invalid EOD, 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.
14414 CM read error recovery enhancement: Perform alternate gain
adjustments and retry to CM read when initial read fails.
14481 Unexpected write error corrected counter decrement: The write
errors corrected counter is incorrectly decremented when a write permanent error
occurs.
14508 Flush after perm error reports good status: When write command
completes with an error, the flag indicating data to be flushed from buffer is cleared
and incorrect good status returned.
14509 CM Access failure causes incorrect wrap number to be used in
write ERP: If a write temp occurs that requires a drive ERP, a variable in the CM
is updated. If the ERP completes successfully, the write will continue. If the drive
moves to another wrap, and another write ERP occurs, and a CM access failure
occurs, the ERP uses the old wrap number for subsequent writes.
14592 Incorrect status translation results in Unload hang: The firmware
incorrectly translates status from a write permanent error which may result in the
drive ignoring subsequent commands which in-turn results in a stuck cartridge.
14622 Cartridges encountered with undetected incorrect format :
Implement additional tack following servo format check.
14627 Read Position command reports incorrect data: The Read Position
command will intermittently report incorrect values after a buffer flush.
IBM Removable Media Storage Solutions
Storage Systems Division 06/10/04
9000 South Rita Road, Tucson, AZ 85744
14676 Unexpected error on WFM0 in early warning area: When in Early
Warning area and an error is encountered and recovered, a Write FileMark of zero
will return an error.
14771 Queue hang for Read abort on EXT: If an internal abort is issued in a
READ operation while Error Recovery is in progress, a hang will result.
14795 Sense reporting to TUR when hardware error: Add flag to indicate
that HW error has been reported during POST/Diagnostics. If this flag is set, Sense
Key 4 (H/W error) is reported instead of reporting Ready/Not Ready for TUR
command and Medium Access commands.
14826 Library serial number not remaining over set config: If the library
port write buffer command for changing the library serial number (buffer 0x13)
occurs before a set config command on the library port which causes a reboot, the
information from the write buffer command is lost.
14848 Misreporting Locate Failure with SCD 4 instead of 6: The mode
flag will be set properly and the error will be reported as a “6”.
14904 Drive posts a SCD ‘4’ during write with an FSC=219D: Drive is
receiving write commands from the host. The host unexpectedly aborts a write
command. While the drive is still in write mode aborting this write command, the
host sends another write command, initiating a second write mode which leaves the
code in an invalid state.
14992 Check Condition with Report Density, Media=1 w/corrupted
medium: 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.
14779 LUN1 error mishandling: Upon a failed LDI packet transmission to the
library (i.e. never received a ACK, NAK, or SNAK), the library code always
entered into the LUN 1 packet sending error handler regardless of whether or not
the failed packet was a LUN 1 command or not (i.e. LDI Maint. command).
15177 Invalid LUN1 command causes LUN1 queue hang: LUN1 Invalid
SCSI CDB causes queue hang condition for LUN1 SCSI command handler.
IBM has just released an LTO Gen1 firmware update, 4561, that is intended to,
among other things, increase overall reliability, improve tape handling, further
reduce any possibility of error, and provide continued enhancements to diagnostic
capabilities. Firmware fixes since 3CKE follow:
14303 Periodic cleaning regimen required: A new function is added allowing
customer to enable a periodic clean cycle of every 40 full file passes. This is
controlled by the Behavior Configuration Mode Page 2Fh.
14357 Buffer Overflow because the Pause is ignored: A particular write
command sequence can cause write error due to a flag being reset unexpectedly.
14408 Permanent Read error on 1st read attempt: On a cartridge with
invalid EOD, 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.
14414 CM read error recovery enhancement: Perform alternate gain
adjustments and retry to CM read when initial read fails.
14481 Unexpected write error corrected counter decrement: The write
errors corrected counter is incorrectly decremented when a write permanent error
occurs.
14508 Flush after perm error reports good status: When write command
completes with an error, the flag indicating data to be flushed from buffer is cleared
and incorrect good status returned.
14509 CM Access failure causes incorrect wrap number to be used in
write ERP: If a write temp occurs that requires a drive ERP, a variable in the CM
is updated. If the ERP completes successfully, the write will continue. If the drive
moves to another wrap, and another write ERP occurs, and a CM access failure
occurs, the ERP uses the old wrap number for subsequent writes.
14592 Incorrect status translation results in Unload hang: The firmware
incorrectly translates status from a write permanent error which may result in the
drive ignoring subsequent commands which in-turn results in a stuck cartridge.
14622 Cartridges encountered with undetected incorrect format :
Implement additional tack following servo format check.
14627 Read Position command reports incorrect data: The Read Position
command will intermittently report incorrect values after a buffer flush.
IBM Removable Media Storage Solutions
Storage Systems Division 06/10/04
9000 South Rita Road, Tucson, AZ 85744
14676 Unexpected error on WFM0 in early warning area: When in Early
Warning area and an error is encountered and recovered, a Write FileMark of zero
will return an error.
14771 Queue hang for Read abort on EXT: If an internal abort is issued in a
READ operation while Error Recovery is in progress, a hang will result.
14795 Sense reporting to TUR when hardware error: Add flag to indicate
that HW error has been reported during POST/Diagnostics. If this flag is set, Sense
Key 4 (H/W error) is reported instead of reporting Ready/Not Ready for TUR
command and Medium Access commands.
14826 Library serial number not remaining over set config: If the library
port write buffer command for changing the library serial number (buffer 0x13)
occurs before a set config command on the library port which causes a reboot, the
information from the write buffer command is lost.
14848 Misreporting Locate Failure with SCD 4 instead of 6: The mode
flag will be set properly and the error will be reported as a “6”.
14904 Drive posts a SCD ‘4’ during write with an FSC=219D: Drive is
receiving write commands from the host. The host unexpectedly aborts a write
command. While the drive is still in write mode aborting this write command, the
host sends another write command, initiating a second write mode which leaves the
code in an invalid state.
14992 Check Condition with Report Density, Media=1 w/corrupted
medium: 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.
14779 LUN1 error mishandling: Upon a failed LDI packet transmission to the
library (i.e. never received a ACK, NAK, or SNAK), the library code always
entered into the LUN 1 packet sending error handler regardless of whether or not
the failed packet was a LUN 1 command or not (i.e. LDI Maint. command).
15177 Invalid LUN1 command causes LUN1 queue hang: LUN1 Invalid
SCSI CDB causes queue hang condition for LUN1 SCSI command handler.
- Thread starter
- #6
A quick reminder however on drive code for STK library installed drives. You must get the STK version of the code to run correctly on STK libraries.
Also, if you are wanting to set up autocleaning with IBM Gen1 drives and the STK library, a bit has to be enabled in the STK version of 4561 code. This requires a special tool that STK has.
Also, if you are wanting to set up autocleaning with IBM Gen1 drives and the STK library, a bit has to be enabled in the STK version of 4561 code. This requires a special tool that STK has.
HI..
The are many fixed problems with LTO drives IBM, the main of all are that IBM LTO tape drive cannot save the index information correctly in the memory of the tape cartridge, this made your backup and recovery more slowly, because in this part of the cartridge have the index information of all tape, then the positioning of the tape its more slowly, and the another big problem its with the block size, the tape drive cannot found the write marks into the tape, and sense an error in the software. The latest firmware for a LTO IBM its the 4561 version, and it can only be provided by a STK engineer, because this microcodes are specialy made for the interactivity between IBM LTO and L-series STK libraries.
The are many fixed problems with LTO drives IBM, the main of all are that IBM LTO tape drive cannot save the index information correctly in the memory of the tape cartridge, this made your backup and recovery more slowly, because in this part of the cartridge have the index information of all tape, then the positioning of the tape its more slowly, and the another big problem its with the block size, the tape drive cannot found the write marks into the tape, and sense an error in the software. The latest firmware for a LTO IBM its the 4561 version, and it can only be provided by a STK engineer, because this microcodes are specialy made for the interactivity between IBM LTO and L-series STK libraries.
- Status
