T015: Drive Sled Fiducial Read Failure; T016: Unexpected Drive Type - IBM TS3310 Maintenance Information

Root Causes
Resolution

T015: Drive Sled Fiducial Read Failure

Description
Detection Scenarios
Root Causes
Possible CRU Replacements
Resolution

T016: Unexpected Drive Type

Description
Detection Scenarios
Root Causes
Possible CRU Replacements
6-10
TS3310 Tape Library Maintenance Information
1. Missing I/O Station magazine
2. A cartridge in an I/O Station just happens to have a label that decodes as
"%XXX".
Note: The inability to communicate between the Library Control Blade and
the bar code scanner should result in a different ticket cause.
Perform "DR023: Resolve Missing I/O Station Magazine" on page 6-69.
GUI Description: The robot is unable to scan the drive sled's
identification/fiducial label.
Explanation: When the library is attempting to determine the type of a drive
and verify its physical presence in the library, it cannot do so because it
cannot read a label where it expects to find one.
1. Installation of a drive into a library drive slot triggers the library to
discover it.
2. Boot up causes the library to physically discover any drive that is
electrically connected in the system.
1. Damaged label or marginal label that cannot be read
2. Drive with invalid label is present (earlier generation of plug compatible
drive sled)
Note: The inability to communicate between the Library Control Blade and
the bar code scanner should result in a different ticket cause.
Drive sled
Perform "DR007: Resolve Barcode Scanner Issue" on page 6-63.
GUI Description: A configured drive sled has been replaced with a drive sled
of different type. .
Explanation: When the library is attempting to determine the type of a drive
and verify its physical presence in the library, it detects a drive type that is
not compatible with the logical library assignment of the drive slot (for
example, an LTO-1 drive in an LTO-3 drive position).
1. Installation of a tape drive into a library drive slot triggers the library to
discover it.
2. Bootup causes the library to physically discover any tape drive that is
electrically connected in the system.
1. End user or CE mistakenly uses the actual wrong type of CRU (for
example, LTO-1 drive sled in a slot defined as LTO-3).
2. Manufacturing defect has wrong label type for actual physical drive type
(for example, LTO-1 label on an LTO-3 drive).
Note: Inability to communicate between the LCB and the scanner should
result in a different ticket cause.
Drive sled