T050: Drive Tapealert 31 - Hardware B; T051: Drive Tapealert 32 - Interface - IBM TS3310 Maintenance Information

Resolution

T050: Drive TapeAlert 31 - Hardware B

Description
Detection Scenario
Root Causes
Possible CRU Replacements
Resolution

T051: Drive TapeAlert 32 - Interface

Description
Detection Scenarios
Root Causes
Possible CRU Replacements
Resolution
6-24
TS3310 Tape Library Maintenance Information
Before performing the following:
v "Removing a Drive Sled" on page 8-43.
v "Replacing a Drive Sled" on page 8-44.
refer to Chapter 1, "Start Service," on page 1-1 for additional diagnostic
procedures.
v Perform "DR049: Resolve Drive TapeAlert 30, 31 - Drive Hardware Error"
on page 6-79.
v From the Operator Panel, select Tools → Service → Drives to run the drive
diagnostic. A blank, scratch cartridge is required for this test.
GUI Description: The tape drive detected an internal hardware problem.
Explanation: System determines that the drive has issued a TapeAlert 31
indicating a hardware error that requires a drive power cycle before the
drive might recover to a usable state.
Tape drive issues a TapeAlert 31 which is recognized by the library during
the continuous four second polling cycle of drive status.
Drive has determined that there is a problem per its internal algorithms.
Drive Sled
v Perform "DR049: Resolve Drive TapeAlert 30, 31 - Drive Hardware Error"
on page 6-79.
v From the Operator Panel, select Tools → Service → Drives to run the drive
diagnostic. A blank, scratch cartridge is required for this test.
GUI Description: The tape drive reported an external data interface problem
Explanation: System determines that the drive has issued a TapeAlert 32
indicating a tape drive has detected a problem with the application client
interface.
Tape drive issues a TapeAlert 32 which is recognized by the library during
the continuous four second polling cycle of drive status.
Drive has determined that there is a problem per its internal algorithms.
Drive Sled(only if all cables are OK and host communication to other drives
works)
1. Perform "DR012: Resolve Drive Tape Alert 32 - Host Interface" on page
6-65.
2. Use the "Details" option in the RAS ticket to identify which tape drive
reported the RAS ticket.
3. Clear the RAS ticket.
4. Check the cabling from the back of the tape drive to the host and reseat
all the cables.
5. If RAS ticket persists, swap cables between drives to isolate a bad cable.
If this works and you can detect the drive, replace the bad cable.
6. If swapping cables did not fix the problem, then upgrade the tape drive
to the latest drive firmware.