Sun StorageTek T10000A Tape Drive
 
Sun StorageTek T10000B Tape Drive
 
StorageTek T10000D Tape Drive
 
Sun StorageTek SL3000 Modular Library System
 
StorageTek T10000C Tape Drive
 
Sun StorageTek 9840 Tape Drive
 
LTO Tape Drive
 
Sun StorageTek T10000 Tape Drive
 
Sun StorageTek SL8500 Modular Library System
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for service personnel
Created from <SR 3-7333995371>

Applies to:

Symptoms

Result Code 1320 - Drive Communication Timeout Errors

Example:

Drive 1,3,2,1,1 offline.

Drive may or may not be in an operational status. 

Drive_Bay29(1.3.2.1.1)

1301 - (1X)
Device response time-out, request= getState Internal 1,3,2,1,1 address = Drive_Bay29(1,3,2,1,1)
(Errors Started - 2013-06-05 18:47:30 Errors Stopped - 2013-06-05 18:47:30)

1303 - (50X)
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6407
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6406
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6403
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: setDriveConfig FAILED, resultCode = 6407
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: getState FAILED, resultCode = 6407
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: Power up FAILED, resultCode = 6407 (state = inoperative)
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: Power up FAILED, resultCode = 6406 (state = inoperative)
Failure from drive Code: 604 - Drive is not functional, drive 1,3,2,1,1: getDriveConfig FAILED, resultCode = 6417
(Errors Started - 2013-06-05 11:55:01 Errors Stopped - 2013-06-06 18:15:06)

1320 - (87X)
Drive communication time-out 1, 3,2,1,1
(Errors Started - 2013-06-05 11:54:50 Errors Stopped - 2013-06-06 18:16:04)

3955 - (61X)
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6407
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6406
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getInfo FAILED, resultCode = 6403
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: setDriveConfig FAILED, resultCode = 6407
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getState FAILED, resultCode = 6407
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: Power up FAILED, resultCode = 6407 (state = inoperative)
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getState FAILED, resultCode = 6406
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: Power up FAILED, resultCode = 6406 (state = inoperative)
Error from device Code: 604 - Drive is not functional, drive 1,3,2,1,1: getDriveConfig FAILED, resultCode = 6417
Error from device Code: 000 - ok, drive 1,3,2,1,1: getDriveNetData FAILED, resultCode = 6406. Returning command not supported.
Error from device Code: 000 - ok, drive 1,3,2,1,1: driveDisplay FAILED, resultCode = 6406. Returning command not supported.
(Errors Started - 2013-06-05 11:55:01 Errors Stopped - 2013-06-06 18:16:04)

3992 - (7X)
Warning from device, drive 1,3,2,1,1: setDriveConfig Command Not Supported.
(Errors Started - 2013-06-05 08:51:07 Errors Stopped - 2013-06-05 12:04:53)

3994 - (2X)
Device removed, device=drive
(Errors Started - 2013-06-05 18:51:12 Errors Stopped - 2013-06-06 17:24:14)

Changes

Cause

Some possible causes:

• Drive SNO

  - Drive SNO, Starting at SL8500 code level 8.60 the library error log will report the drive SNO FSC in the 5025 event; example FFFA is the drive SNO FSC

    2018-01-26T12:05:49.304,   3.2.1.1.2,   root,   default,   internal,   0,   error,   5025,   "FSC reported with announce drive reset FSC = FFFA" - Drive was IPLed

- Drive was removed from the library.

- Drive tray power problem

Solution

Verify if the drive was power cycled. The drive could have been power cycled by pulling the drive tray and re-inserting it into the library.

If the drive was not power cycled then check SL Console and determine if the drive is shown as operational.

If the drive is shown as operational then the drive could have experienced a SNO and came back up.

1. Check the drive for a recent dump.

    a.  If a dump is present, retrieve the dump and upload it to the SR along with the drive event log.

If the drive is not shown as operational:

1. Check the tray status to see if the tray power status looks good. If the power/ Tray power is not ok there may be a drive/tray power supply problem.

2. Check the display on the drive using SL Console to see if the drive has a FSC shown which would indicate that a T10000C/D SNO occurred.  If the FSC in the display is 3F2E or 3F21 see KBs 2251787.1  and 1991877.1 for details on these errors.

3. If Tray power shows no fault and the drive display has no FSC shown, try to set the drive online using Tools>System Details>Expand the drive folder>Highlight the drive in question> Select Transition>Bring online and apply.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

A service request should be entitled against the Drive Tray and not the library. Obtain a drive dump and Library log snapshot to isolate root cause.

Example:

1,3,2,1,2 25 579004000241 579000200138 T10000d StorageTek notCommunicating 4.09.107-5.50

SL3000/SL8500 - How to Collect Log Snapshot From SL8500 or SL3000 Library [ID 1307534.1]

IBM LTO - How to Collect Statistical and Dump Logs From IBM LTO Drives Using ITDT (IBM Tape Diagnostics Tool):ATR:1016763.1:0(Doc ID 1016763.1)

HP LTO - How to Collect Statistical and Error Logs from HP LTO Tape Drive Using HP LTT:ATR:1185771.1:1(Doc ID 1185771.1)

How to Collect Statistical and Error Logs From 9840, 9940 or t10000 Tape Drive Using VOP:ATR:1014247.1:0(Doc ID 1014247.1)

This solution has no attachment