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-2283815.1
Update Date:2018-04-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  2283815.1 :   IBM LTO6 - Status is Inoperative, Drive and Tray Health is Okay  


Related Items
  • IBM LTO6 Tape Drive
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-15174838271>

Applies to:

IBM LTO6 Tape Drive - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Health of drive tray is ok, but the LTO6 is inoperate status.

Drive Address Bay DMOD # Tray Serial # Type Vendor Drive Status Firmware Tray Health IP
1.1.1.1.2 8 10WT012609 unknown IbmUltrium6 IBM inoperative G350 ok N/A

Following messages occurred when add the drive tray to the SL3000:

2017-07-03T16:43:40.502, 1.1.1.1.2, root, default, internal, 0, warn, 3994, "Device removed", device=drive
2017-07-03T16:43:40.882, 1.1.1.1.2, root, default, queryTable, 250201, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="46600" final="true"><command>getState</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6021</resultCode><resultText><!|CDATA|drive 1,1,1,1,2: getState requested for drive not installed||></resultText><operationalState>604</operationalState></resultStatus><driveState></driveState><needsCleaning>false</needsCleaning><hostActivity>false</hostActivity><overTemp>false</overTemp><validationInProg>false</validationInProg></result></response>
2017-07-03T17:16:56.783, 1.1.1.1.2, root, default, internal, 0, error, 3955, "Error from device Code: 604 - Drive is not functional", Data=<response sequence="46668" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6411</resultCode><resultText><!|CDATA|drive 1,1,1,1,2: Power up FAILED, resultCode = 6411 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>
2017-07-03T17:16:56.816, 1.1.1.1.2, root, default, internal, 0, error, 1303, "Failure from drive Code: 604 - Drive is not functional", Data:=<response sequence="46668" final="true"><command>controlPower</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6411</resultCode><resultText><!|CDATA|drive 1,1,1,1,2: Power up FAILED, resultCode = 6411 (state = inoperative)||></resultText><operationalState>604</operationalState></resultStatus></result></response>

 

From SLC, Drive tray status is good, but "Refresh data for specified device failed" occurred when try to bring online or take offline.

 

Changes

Drive replacement can not resolve this problem.

Customer found the broken belisarius card, so replaced the bel card and cables, but can not fix this issue.

swapped HBD and power supply with another good drive tray, but problem was still with this drive.

Cause

Communication Issue via Belisarius card.

Solution

Another document fixed this issue by cable reconnection, but it's not work at this time.

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 (Doc ID 2281427.1)

 

After bypass the Belisarius card, drive was back to online and working good!

IBM LTO - Belisarius Card Bypass Procedure (Doc ID 2037654.1)


 


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