Sun StorageTek 9840 Tape Drive
 
Sun StorageTek T10000 Tape Drive
 
Sun StorageTek 9940 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK T-Series Drive
 

In this Document

Goal

Solution

Applies to:

Goal

 Describe the process to collect event logs and possibly force a drive dump as part of the stuck tape process.

Solution

Application requirements & restrictions:
- MDVOP 1.2.14 or VOP 1.0.17 (or higher) is required to gather dumps and logs from T9840A/B/C or T9940A/B tape drives.
- MDVOP 1.3 or VOP 1.0.18 (or higher) is required to gather dumps and longs from T10000A/B drives running code version 1.48.x05 (or higher) and T10000C drives running 1.53.311 (or higher).

Files to gather:
- Drive Event Logs
- Drive Perm Error Logs
- Drive ID files
- Forced Drive Dump

*The process of gathering these files (excluding the forced drive dump) is non-disruptive.

T10000A/B/C/D and 9840D Forced Drive Dump

A drive dump is a very useful tool to determine the cause of a stuck tape problem. The information in the drive dump can tell the person working the problem  if a hardware problem occurred in the drive or if the the drive failed to receive an unload command from the host. The act of forcing a dump also resets the drive as the drive will perform the IPL process after the dump information is collected to the internal drive EEPROM. During the IPL process the drive will detect if tape media is present in the tape path and attempt to gracefully unload the tape.

A drive dump should only be forced on a tape drive for a stuck tape scenario if the drive is at the minimum code versions listed below as previous code versions were susceptible to a potential tape breakage problem if the reel motor was defective.

These are the minimum code levels the drive needs to be at in order to force a dump on a drive with a stuck tape:

9840D - no restrictions.

T10000A/B - no restrictions.

T10000C - 1.61.301 (or higher) Note: 3.62.xxx code is higher than 1.61.301 code.

T10000D - 4.08.105 (or higher)

The drive does not need to be offline in order to force a dump.

To force a dump using VOP:
- Make sure all traffic to the drive has been stopped.
- Bring up VOP and connect to the drive.
- Select > Drive Operations > Force Dump
- Watch the display on VOP. It should reconnect to the drive after the drive IPLs. This can take several minutes. If VOP does
not reconnect to the drive after 10 or 15 minutes, open a new VOP session to the drive.

9840A/B/C and 9940 A/B Forced Drive Dump

- Hold in the Menu and Unload buttons on the operator panel for one second to dump current drive status from memory to
EEPROM.
- Dump saving to the EEPROM begins when CHK FFFF displays and the power indicator begins to flash.
- When the dump is saved, the service indicator flashes.
- The drive automatically performs an IPL and returns to Online.
- The display will alternate between * (asterisk) and FFFF:Dmpyy

(yy = total number of all uncollected dump logs) until any normal drive activity is started.

Retrieving The Log Files
To gather the logs (including dumps):

Collect drive support logs using single drive VOP CSE version.
(VOP--File--Collect Support Logs)
This will pull ID, perms, event log, and all dump files.

Zip and upload these files as attachments to the SR. (Note: Please do not use spaces in any of the file names.)

Reference:
StorageTek Virtual Op Panel Customer User's Guide
http://download.oracle.com/docs/cd/E19202-01/en/E20750/E20750_01.pdf

This solution has no attachment