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-71-2126475.1
Update Date:2017-07-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  2126475.1 :   T10000/9x40: Stuck Tape Process - External  


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




In this Document
Goal
Solution
References


Applies to:

Sun StorageTek T10000 Tape Drive - Version All Versions and later
Sun StorageTek 9840 Tape Drive - Version Not Applicable and later
Information in this document applies to any platform.

Goal

 Stuck Tape Process

Solution

 WHAT ACTION DOES THE CUSTOMER NEED TO TAKE:

Prior to requesting an onsite FE to physically remove a jammed /stuck cartridge, make sure the following actions have been taken to avoid any unnecessary steps. These instructions cover a situation when a tape cartridge is not unloading from the drive.

  • In environments that utilize ACSLS, HSC/ELS, (and other applications that can be used to dismount tapes from a tape drive), verify that a forced dismount command has been issued to the drive in question.
  • Check the drive status using either VOP or SL Console to see if the tape is in an unloaded state.
  • If the drive is still loaded, force a drive dump. Upload the dump to the SR, then notify tape support via MOS that a dump exists for the stuck tape problem.
  • Forcing a drive dump effectively does a reset to the drive which should cause it to unload any tape that was loaded. The tape should then be able to be dismounted and put back in it's home cell in the library.
  • Check status again to ensure that the tape did unload successfully. The time to complete this unload may vary depending on how much tape was on the machine reel. Certain error conditions can take 1 hour or more due to the drive going into a slow speed rewind state.

Note:

Reference this Knowledge Base Entry for the process used to force a drive dump:

T10000 - How To Force A Drive Dump (DocID 2099953.1)


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