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-2304560.1
Update Date:2017-11-13
Keywords:

Solution Type  Problem Resolution Sure

Solution  2304560.1 :   SL3000/HP LTO4 - Result Code 6406, Error 3933, Not Communicating, Not Powered, Not initializing  


Related Items
  • Sun StorageTek SL3000 Modular Library System
  •  
  • HP LTO4 Tape Drive
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
  •  


error codes 3955, 6406, 1303, 3204,  1301, 6450, 1311

In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-15661258401>

Applies to:

HP LTO4 Tape Drive - Version All Versions to Not Applicable [Release All Releases to N/A]
Sun StorageTek SL3000 Modular Library System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

Result Code 6406, Error 3933, Not Communicating, Not Powered, Not initializing.

Error codes 3955, 6406, 1303, 3204, 1301, 6450, 1311

2017-09-01T12:17:14.073, 1.1.4.1.1, root, default, queryTable, 6618801, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="972334" final="true"><command>getDriveConfig</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6406</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: getDriveConfig FAILED, resultCode = 6406||></resultText><operationalState>604</operationalState></resultStatus><driveWwn>N/A</driveWwn><portAWwn>N/A</portAWwn><portBWwn>N/A</portBWwn><portALoopId>auto</portALoopId><portBLoopId>auto</portBLoopId><portASpeed>N/A</portASpeed><portBSpeed>N/A</portBSpeed><portALinkStatus>N/A</portALinkStatus><portBLinkStatus>N/A</portBLinkStatus><dualPort>true</dualPort><portAEnabled>true</portAEnabled><portBEnabled>true</portBEnabled></result></response>
2017-09-01T12:17:14.105, 1.1.4.1.1, root, default, queryTable, 6618801, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="972334" final="true"><command>getDriveConfig</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6406</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: getDriveConfig FAILED, resultCode = 6406||></resultText><operationalState>604</operationalState></resultStatus><driveWwn>N/A</driveWwn><portAWwn>N/A</portAWwn><portBWwn>N/A</portBWwn><portALoopId>auto</portALoopId><portBLoopId>auto</portBLoopId><portASpeed>N/A</portASpeed><portBSpeed>N/A</portBSpeed><portALinkStatus>N/A</portALinkStatus><portBLinkStatus>N/A</portBLinkStatus><dualPort>true</dualPort><portAEnabled>true</portAEnabled><portBEnabled>true</portBEnabled></result></response>
2017-09-01T19:13:54.571, 1.1.4.1.1, root, default, queryTable, 6642901, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="973606" final="true"><command>getDriveConfig</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6406</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: getDriveConfig FAILED, resultCode = 6406||></resultText><operationalState>604</operationalState></resultStatus><driveWwn>N/A</driveWwn><portAWwn>N/A</portAWwn><portBWwn>N/A</portBWwn><portALoopId>auto</portALoopId><portBLoopId>auto</portBLoopId><portASpeed>N/A</portASpeed><portBSpeed>N/A</portBSpeed><portALinkStatus>N/A</portALinkStatus><portBLinkStatus>N/A</portBLinkStatus><dualPort>true</dualPort><portAEnabled>true</portAEnabled><portBEnabled>true</portBEnabled></result></response>
2017-09-01T19:13:54.604, 1.1.4.1.1, root, default, queryTable, 6642901, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="973606" final="true"><command>getDriveConfig</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6406</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: getDriveConfig FAILED, resultCode = 6406||></resultText><operationalState>604</operationalState></resultStatus><driveWwn>N/A</driveWwn><portAWwn>N/A</portAWwn><portBWwn>N/A</portBWwn><portALoopId>auto</portALoopId><portBLoopId>auto</portBLoopId><portASpeed>N/A</portASpeed><portBSpeed>N/A</portBSpeed><portALinkStatus>N/A</portALinkStatus><portBLinkStatus>N/A</portBLinkStatus><dualPort>true</dualPort><portAEnabled>true</portAEnabled><portBEnabled>true</portBEnabled></result></response>
2017-09-01T19:14:56.452, 1.1.4.1.1, root, default, queryDrive, 6643001, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="973608" final="true"><command>getState</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6406</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: getState FAILED, resultCode = 6406||></resultText><operationalState>604</operationalState></resultStatus><driveState>notCommunicating</driveState><needsCleaning>false</needsCleaning><hostActivity>true</hostActivity><overTemp>false</overTemp><validationInProg>false</validationInProg></result></response>
2017-09-01T19:15:06.548, 1.1.4.1.1, root, default, reboot, 6643201, error, 3204, "System error - Invalid state transition", state=Error transtion=Vary offline
2017-09-01T19:17:02.755, 1.1.4.1.1, root, default, queryTable, 6643401, error, 1301, "Device response time-out", request=<request sequence="973619"><command>getDriveConfig</command><requestId>Internal</requestId><parms><address>1,1,4,1,1</address></parms></request>
2017-09-01T19:17:02.765, 1.1.4.1.1, root, default, queryTable, 6643401, error, 1320, "Drive communication time-out - drive - get wwname"
2017-09-01T19:19:09.549, 1.0.0.1.0, root, default, internal, 0, error, 3333, "Dropped unexpected device response", Data=<response sequence="973619" final="true"><command>getDriveConfig</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6202</resultCode><resultText><!|CDATA|End of Text||></resultText><operationalState>000</operationalState></resultStatus><driveWwn>N/A</driveWwn><portAWwn>N/A</portAWwn><portBWwn>N/A</portBWwn><portALoopId>auto</portALoopId><portBLoopId>auto</portBLoopId><portASpeed>N/A</portASpeed><portBSpeed>N/A</portBSpeed><portALinkStatus>N/A</portALinkStatus><portBLinkStatus>N/A</portBLinkStatus><dualPort>true</dualPort><portAEnabled>false</portAEnabled><portBEnabled>false</portBEnabled></result></response>
2017-09-01T19:20:09.505, 1.1.4.1.1, root, default, queryTable, 6644001, error, 1301, "Device response time-out", request=<request sequence="973626"><command>getDriveConfig</command><requestId>Internal</requestId><parms><address>1,1,4,1,1</address></parms></request>
2017-09-01T19:20:09.514, 1.1.4.1.1, root, default, queryTable, 6644001, error, 1320, "Drive communication time-out - drive - get wwname"
2017-09-01T19:22:54.085, 1.1.4.1.1, root, default, reboot, 6643201, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="973617" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6450</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: Power up FAILED, resultCode = 6450 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>
2017-09-01T19:22:54.118, 1.1.4.1.1, root, default, reboot, 6643201, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="973617" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6450</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: Power up FAILED, resultCode = 6450 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>
2017-09-01T19:39:13.348, 1.1.4.1.1, root, default, internal, 0, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="973642" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6411</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: Power up FAILED, resultCode = 6411 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>
2017-09-01T19:39:13.378, 1.1.4.1.1, root, default, internal, 0, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="973642" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6411</resultCode><resultText><!|CDATA|drive 1,1,4,1,1: Power up FAILED, resultCode = 6411 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>

Cause

Drive tray power supply
No power on drive. The drive power LED was said to be on. The tray showed degraded and not in a good status on the SLC.

Solution

Replaced the drive power supply in the LTO4 drive tray. (SL3000)

References

<NOTE:1528033.1> - SL3000 - Drive Not Powered On, Result Code 3992, 3955, 6027
<NOTE:2281427.1> - SL3000/IBM LTO6 - 3955 "Error from device Code: 604 - Drive is not functional", Data=|CDATA|drive 1,1,4,1,1: getState FAILED, resultCode = 6402| notCommunicating

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