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-1999766.1
Update Date:2017-08-16
Keywords:

Solution Type  Problem Resolution Sure

Solution  1999766.1 :   T10000 - FSC 377A Troubleshooting  


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


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for Service Personnel

Applies to:

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

Symptoms

 Error 377A will occur if you try to read a block that was involved with a previous write perm.

Cause

T1000A/B/C/D This will occur if you try to read a block that was involved with a previous write perm.

Solution

Error 377A will occur if you try to read a block that was involved with a previous write perm.

As an aid to troubleshoot this type of problem, additional information was added to the drive event logs for the following code versions:

T10000C version RC362109 and higher.

T10000D version 4.10.10x and higher.

If you have event logs from a drive that has the additional fields and a FSC 377A error is seen:

- Pull the all_evl.csv file into a spreadsheet. (You won't find these fields in the viewer)

- Check column AZ to see if it contains "TAPE_ENDS_WITH_WRITE_PERM". If it does, failing write blockid and failing write FSC are available in the next 2 columns.

- Also look at the last writing drive in the 367C demount record in the event log for the serial number of the failing drive.

 

Troubleshooting with the above information:

If column AZ contains "TAPE_ENDS_WITH_WRITE_PERM" then you know the problem is most likely caused by a job that is trying to read a block that was never written properly.

Check the next column for the failing write blockid to see if it matches (or is close to) the blockid where the 377A is occurring.

If you have a match then inform the customer that they have a job that is trying to read a block that was never written properly. Have them check their process that they follow when a drive takes a write perm and ensure that: 1) the job marks the tape so that no further writes occur on the tape and 2) the tape is copied to another tape, 3) the tape is certified to ensure there is no physical damage to the media before re-using the tape.

Check to see if the drive that failed to write on this tape is still in the shop. If it is then it should be checked to ensure the write system is healthy.


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