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-2349355.1
Update Date:2018-02-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2349355.1 :   T10000C/D - 602F Error Troubleshooting  


Related Items
  • StorageTek T10000D Tape Drive
  •  
  • StorageTek T10000C 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:

StorageTek T10000C Tape Drive - Version All Versions and later
StorageTek T10000D Tape Drive - Version All Versions and later
Information in this document applies to any platform.

Symptoms

 602F errors on tapes that are loaded.

Cause

 RFID is corrupted.

Solution

602F errors may or may not allow loading of the tape without issue. If it does load successfully then the tape should be readable without issue. Once the tape comes ready, the data should be copied to a new tape.

The drive will not allow writing to a tape with a corrupted RFID. If the tape is a scratch tape, the customer or FE should be able to utilize the Make Data Tape utility to update the RFID to correct its content.

Big Caution – If you run Make Data Tape to the tape all customer data currently written on the tape will be lost. Do not run Make Data Tape to any tape with live data on it.

It is possible for a tape to take a 602F error where the tape fails to load if the RFID chip is corrupted by a bad RFID writer in some drive in the shop. This has been the most recent cause for 602F RFID issues. If you see this problem then you will need to check the history of the tape to see when it was last loaded successfully in a drive. The drive that last loaded the tape successfully is probably the culprit drive as it probably corrupted the RFID when the tape was unloaded. Research this using their application logs, etc. If the tape has live data on it then contact Oracle Tape Support for further instructions. A forced dump will be required for this tape.

 

We have seen instances where the drive that is corrupting RFID chip information on tapes does not detect that it is doing so. Because of this possibility, a new check will be put in to both T10000C and T10000D microcode that will read back and verify the data in the RFID after it is written when the tape is unloaded. T10000C microcode will have this test in it starting with the future 3.65.103 code version. The T10000D drive will have this new check in it starting with the future 4.14.1xx code version.

 

 


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