StorageTek T10000D Tape Drive
 
StorageTek T10000C Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK T-Series Drive
 

In this Document

Symptoms

Changes

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for service personnel

Applies to:

Symptoms

3F2E error on T10000C or T10000D tape drives. Tapes will not load after this error is posted on the drive. The drive may show as inoperative in the library logsnap and have 3F2E in the display.. This may occur on the unload of the first tape mounted after the code is upgraded. If another tape load is attempted the load will fail. At this time the 3F2E FSC will not show up in the library log snap. Future library code will allow SNO FSCs (like 3F2E) to be displayed in the log snap.

Changes

Microcode was upgraded to the versions list below on the tape drives:
T10000C - 3.63.101 (or higher)
T10000D - 4.12.106 (or higher)

Cause

 One or more stuck rollers were detected during the unload sequence for the last tape loaded.

Solution

Background:

A new check for seized rollers cut in with 3.63.101 T10000C and 4.12.106 T10000D microcode. This check is done for every tape during the unload cycle.

It is HIGHLY RECOMMENDED to immediately load and unload a tape in each drive that is upgraded to these code versions before they are put into production to see if the drive has a stuck roller.

For large accounts it is highly recommended to get the ID files from all drives and identify the drives with 100 Million meters or more on the roller sub assembly. These drives are at a much higher risk of having a stuck roller. For these higher meter count drives it is recommended to upgrade the code on no more than 5 drives at a time and then load and unload a tape to see if they take a 3F2E error on the first mount. If these 5 drives are ok then load the code on 5 more drives and repeat the load/unload process on these drives. If you run into 5 or more drives that fail you may want to stop the process on these high meter count drives until these 5 are replaced.

If any drives fail with a 3F2E error on the first mount after 3.63.101(T10KC) or 4.12.106(T10KD) code is loaded then the drive may have had a stuck (seized) roller for some time. Some customers might want to read down tapes tapes that were on the drive recently to verify readability.

Troubleshooting Process:

If you suspect that a T10000C/D drive failed with a 3F2E error follow these steps:

1. Confirm that the drive is running on microcode that checks for seized rollers.

2. Some possible symptoms for this problem are:

    - The code was recently upgraded to a version that can detect seized rollers.

    - 1320 errors in the library - any drive SNO will cause a 1320 error in the library. The 3F2E error is a SNO. Not all 1320 errors can be attributed to a 3F2E error but it is a symptom. At this time the 3F2E FSC will not show up in the library log snap. Future library code will allow SNO FSCs (like 3F2E) to be displayed in the log snap.

    - 3F2E is shown in the drive display. Once the drive takes a 3F2E SNO the drive will SNO and then IPL and display 3F2E.

   -  Any future mount attempts will receive 3F2E errors although the mount should not complete as the drive returns "Maintenance Mode" status to the library at this point.

   - The drive will show as inoperative in the Configuration tab in the library log snap.

3. If the above symptoms are seen, have the customer bring up SL Console and select the drive. Have them click on the Display tab. Check for 3F2E in the Drive Display field.

Once the 3F2E error is confirmed:

Replace the drive for any 3F2E errors. CPAS is no longer required for these failures.

This solution has no attachment