IBM System Storage TS3310, Maintenance Information

Page: 174 / 531

Troubleshooting Steps:
1. If the drive was intentionally removed, close this ticket.
2. Check for T021 tickets posted against other drives in the same module, if present. If other tickets exist, skip to
step #7.
3.
Close this ticket and remove and reseat the drive. Check the thumb screws on the drive to make sure they are
tight and the drive is mounted flush to the library chassis.
4. If this ticket reappears, close it again and move the drive to an empty slot in the same module. If no ticket
appears after this, contact Service to replace the chassis.
5. Otherwise, close the ticket and move the drive to an empty slot in an adjacent module, if applicable. Check for
ticket recurrence.
6. If the ticket is posted yet again, contact Service for drive replacement If the ticket is posted yet again, contact
Service for drive replacement.
7. Check the power supply in the back of the module to verify that it is turned on and plugged in properly. If
not, correct the problem, close all the T021 tickets for the module, and verify that they do not get posted again.
8. If the tickets do reappear, check further for T021 tickets posted against drives in other modules, if applicable. If
there are none, contact Service for chassis replacement.
9. If T021 tickets do exist for drives in other modules, close them, turn off the library, remove and reseat the LCB,
and turn the library back on. Check to see if any T021 tickets reappear.
10.
If so, then check for other causes. There are other problems such as T066- Drive Power Fuse Blown or a
module terminator or module-to-module cable with bent or broken pins that can cause communication loss.
Resolve these problems, if found.
11. If not, contact service for further assistance.
DR030: Resolve Drive Load Failure
Problem:
The robot was unable to load a tape drive. The robot motion completed normally but the drive did not report that it
successfully loaded the tape. The problem may be caused by defective drive hardware or a defective picker
mechanism.
There are two possible scenarios that can lead to this problem:
1. The drive hardware is not functioning properly.
2. The robot hardware is not functioning properly.
Troubleshooting:
1. The problem is most likely isolated to the specific drive referenced under the Details button. However, check for
the same problem being reported for other drives in the system.
2. If this same problem is reported on multiple drives, replace the Picker. Refer to “M2 Picker Assembly” on page
8-72.
3.
If this problem is isolated to an individual drive, replace the drive. Refer to “Drive Sled” on page 8-43.
DR031: Resolve Robot Initialization Failure
Problem:
During a power ON or after closing library main access doors, the robot did not initialize properly.
A common cause for this problem is an unplugged cable that leads to the robot. Other permanent hardware failures
that result in loss of connection to the robot can also be a root cause.
6-72
TS3310 Tape Library Maintenance Information