StorageTek T10000C Tape Drive
 
StorageTek T10000D Tape Drive
 

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

In this Document

Symptoms

Cause

Solution

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

Applies to:

Symptoms

FSC 3F21

Cause

 FSC 3F21 is caused by servo issues on the drive.

Solution

FSC3F21 was introduced in T10000C 3.62.108 and higher code.  It is in the T10000D microcode beginning with the 4.09.107 release.

Note:

FSC 3F21 detection was removed from T10KC code in released 3.65.103 microcode. It will be removed from T10KD microcode in future version 4.14.10x.

The reason that 3F21 detection was removed is that current microcode has an improved check for stuck/seized rollers that will result in a 3F2E error. This check is more reliable vs. the 3F21 check that was based on servo offtrack numbers. We have seen where a certain drive tray can take 3F21 errors on multiple drives. This situation is addressed by installing T10KC code 3.65.103 or for T10KD drives we have a special build that can be used until 4.14.10x code releases.

The 3F21 FSC is generated when the drive detects that it is having servo problems as found in the internal servo stats.  It is too broken to mount any further tapes.

For any 3F21 that is encountered the tape drive must be replaced.  The drive will no longer mount tapes after the error is detected. If another tape is loaded the same fsc will be posted to the display.

Do not ask the customer to reboot the drive just replace it.

Once the drive detects the failing condition, it will allow the current tape to be dismounted if the drive is running on RC362109 code or higher.

Note - Code version 3.62.109 was superseded by code version RC362.109 as 3.62.109 code did not allow the last tape to be unloaded by the library.

Troubleshooting Process:

If you suspect that a T10000C/D drive failed with a 3F21 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 3F21.

- Any future mount attempts will receive 3F21 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 3F21 in the Drive Display field.

This solution has no attachment