Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek SL8500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
 

What to do when you see a  "Error from device Code: 604 - Drive is not functional", event in the library log snapshot.

In this Document

Symptoms

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Adding new knowledge

Applies to:

Symptoms

Error from device Code: 604 - Drive is not functional.

During the log snapshot analysis process you encounter the following messages.

2014-02-06T15:51:50.256, 1.4.2.1.4, root, default, internal, 0, error, 1320, "Drive communication time-out 1,4,2,1,4"

2014-02-06T16:20:38.328, 1.4.2.1.4, root, default, internal, 0, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="8936807" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6450</resultCode><resultText><!|CDATA|drive 1,4,2,1,4: Power up FAILED, resultCode = 6450 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>

2014-02-06T21:50:53.165, 1.4.2.1.4, root, default, internal, 0, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="8941360" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6450</resultCode><resultText><!|CDATA|drive 1,4,2,1,4: Power up FAILED, resultCode = 6450 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>

2014-02-07T18:31:47.792, 1.4.2.1.4, root, default, internal, 0, error, 1320, "Drive communication time-out 1,4,2,1,4"

Cause

Possible cause of a 1320 Drive communication timeout.

ADDITIONAL POSSIBLE CAUSE FOR 1320, "Drive communication time-out is on T10K and 9x40 tape drives that they have taken a dump and have disappeared for some minutes from the libraries/tape drives communication path.
This can be verified by checking the drives status in SLConsole.

Log on to SLC:
At "System Detail" screen, open the drive folder and select affected tape drive.
On the right hand side of the SLC screen, called "Drive", select the tab called "Display"

Look for the line called "Trace available"
If "off" than tape drive has currently no dump available.
If "on" than a dump is available in the tape drive and could be the cause for the 1320, "Drive communication time-out.

Solution

Assist with identifying a possibly defective drive in a SL8500 or SL3000 tape library.

Verify the drive type, attempt to collect a drive dump via SDP2 if possible.. If the drive is not connected have the customer initiate a drive dump via MDVOP and open a HW task to have the drive dump/event logs analyzed and/or replace the drive if necessary.

This solution has no attachment