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-1437961.1
Update Date:2018-03-02
Keywords:

Solution Type  Problem Resolution Sure

Solution  1437961.1 :   T10000 - FSC4032 Invalid MIR  


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




In this Document
Symptoms
Cause
Solution
References


Applies to:

StorageTek T10000C Tape Drive - Version Not Applicable and later
Sun StorageTek T10000B Tape Drive - Version Not Applicable and later
StorageTek T10000D Tape Drive - Version All Versions to All Versions [Release All Releases]
Sun StorageTek T10000A Tape Drive - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

4032 FSC
MIR_NOT_WRITABLE_AT_UNLOAD tape alert flag being set in the event log unload records.
FSC 367C
FSC367C

Invalid MIR

Cause

An Invalid MIR on a T10000 tape will not cause any significant performance problems as the RFID has enough information to do high speed searches without a performance hit. It is not worth the time and effort required to rebuild the MIR on T10000 tapes. Invalid MIRs are typically caused by a drive that is writing poorly.

Solution

T10000 drives use the MIR to "look up" the physical location of a block on tape then will use high speed to go out to that block. A portion of this index table that contains the physical location of blocks on tape is also recorded in the RFID.

When the tape drive receives a Space or Locate command, the drive code will go to the MIR first. If the MIR is Invalid, it will go to the RFID and find the block closest to the target and high speed out to that block.

Current T10000C/D drive code will also track the location of files in the RFID to use for Space File commands in case the MIR is invalid. T10000A/B drive code does not have this capability.

The best way to identify a drive that is not writing the MIR on tapes during the upload operation is to run a health check on all drives in the account and submit it to SPLAT. Search for the MIR_NOT_WRITABLE_AT_UNLOAD tape alert flag being set in the event log unload records. (FSC 367C)

Any drive that is writing poorly is suspect for this condition.  If a drive is found to be failing to write MIRs to multiple tapes, it should be taken offline and replaced.

How to Remove / Replace a Tape Drive in 9310/L5500/9741 Library Drive Cabinet:ATR:1353648.1:2 (Doc ID 1353648.1)
How to Remove and Replace a Tape Drive in SL8500:ATR:1353584.1:2 (Doc ID 1353584.1)

How to Remove / Replace a Tape Drive in SL3000 Library:ATR:1364700.1:2 (Doc ID 1364700.1)


References

<NOTE:1353648.1> - How to Remove / Replace a Tape Drive in 9310/L5500/9741 Library Drive Cabinet:ATR:1353648.1:2
<NOTE:1353584.1> - How to Remove and Replace a Tape Drive in SL8500:ATR:1353584.1:2

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