Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1991043.1
Update Date:2018-05-02
Keywords:

Solution Type  Problem Resolution Sure

Solution  1991043.1 :   T10000A and T10000B - Stiction Issues  


Related Items
  • Sun StorageTek T10000B Tape Drive
  •  
  • Sun StorageTek T10000A Tape Drive
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK T-Series Drive
  •  




In this Document
Symptoms
Cause
Solution


Applies to:

Sun StorageTek T10000A Tape Drive - Version All Versions to All Versions [Release All Releases]
Sun StorageTek T10000B Tape Drive - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Stiction related perm errors on T10000A and T10000B  tape drives.

FSC: 5809    SRV_FSC_UNWIND_RECOVERY_STALLED_EARLY
FSC: 5904    REEL_CTL_FSC_FILE_AMP_SATURATED
FSC: 5905    REEL_CTL_FSC_MACHINE_AMP_SATURATED
FSC: 591D    REEL_FSC_TAPE_STUCK_IN_TAPE_PATH
FSC: 5920    REEL_FSC_SOFT_STICTION_DETECTED
FSC: 5921    REEL_FSC_HARD_STICTION_DETECTED
FSC: 5922    REEL_FSC_VELO_DIFF_STICTION_DETECTED
FSC: 5923    REEL_FSC_MACH_AMP_SAT_STICTION_DETECTED
FSC: 5924    REEL_FSC_FILE_AMP_SAT_STICTION_DETECTED
FSC: 5925    REEL_FSC_MACH_UNDER_VELO_STICTION_DETECTED
FSC: 5926    REEL_FSC_FILE_UNDER_VELO_STICTION_DETECTED
FSC: 5928    REEL_FSC_MACHINE_REEL_STUCK_DURING_UNSLACK
FSC: 5929    REEL_FSC_FILE_REEL_STUCK_DURING_UNSLACK
FSC: 592F    REEL_FSC_EXCESS_REEL_MOTION_IN_STICTION_RECOVERY
FSC: 5931    REEL_FSC_EXCESS_SLACK_STICTION_DETECTED
FSC: 5932    REEL_FSC_BRAKING_SETTLE_TIMEOUT
FSC: 5933    REEL_FSC_STICTION_AVOIDANCE_WARNING
FSC: 5941    REEL_FSC_PULLING_REEL_STICTION_DETECTED

Cause

 Tape stiction problem. This is caused by the tape getting stuck to the drive heads.

Solution

For any of the above stiction related FSCs (as a permanent error) do the following:

1. Ensure that the drives are running at 1.48.x05 code. (or higher)

2. Determine which tapes are involved. Check the history of the failing tapes to see if they are failing on other drives as well. If the tape is failing on other drives then this is a media problem. This can be accomplished using host logs or by using STA.

3. If the drive experiences 4 or more perm errors on unique tapes then this SR needs to be sent to an L2 Domain rep for drive replacement verification.





Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback