Sun StorageTek SL8500 Modular Library System
 

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

In this Document

Symptoms

Cause

Solution

References

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

Applies to:

Symptoms

SL8500 with two CAPs. CAP B doesn't unlock causing the gear to strip when CAP button is pressed to open CAP.

hbzb/log/stk/log_error

2015-08-24T11:08:00.909, 0.0.0.0.0, 701, vader, /usr/local/bin/capb, error, 0000, 7001, "CapVader ifMain, command=2; checkForIsrFailure saw status=3, error=7001, mech=capb; Motor Failure"
command=3; checkForIsrFailure saw status=1, error=7004, mech=capb; Move failed, excessive current required"
2015-08-26T12:49:16.609, 0.0.0.0.0, 701, vader, /usr/local/bin/capb, error, 0000, 7002, "CapVader ifMain, command=3; checkForIsrFailure saw status=2, error=7002, mech=capb; Stall: Position Error, known range(-8388606 - 8388605) position = -52606"
2015-09-09T10:56:14.627, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7009, "CapVader ifMain, command=2; checkForIsrFailure saw status=14, error=7009, mech=capb; Failed to close CAP cylinder, check for obstruction"
2015-09-09T11:00:30.103, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7004, "CapVader ifMain, command=3; checkForIsrFailure saw status=1, error=7004, mech=capb; Move failed, excessive current required"
2015-09-09T11:00:48.477, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7004, "CapVader ifMain, command=3; checkForIsrFailure saw status=1, error=7004, mech=capb; Move failed, excessive current required"
2015-09-09T12:58:22.103, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7004, "CapVader ifMain, command=3; checkForIsrFailure saw status=1, error=7004, mech=capb; Move failed, excessive current required"
2015-09-09T12:58:46.099, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7004, "CapVader ifMain, command=3; checkForIsrFailure saw status=1, error=7004, mech=capb; Move failed, excessive current required"
2015-10-22T12:01:34.290, 0.0.0.0.0, 702, vader, /usr/local/bin/capb, error, 0000, 7009, "CapVader ifMain, command=2; checkForIsrFailure saw status=8, error=7009, mech=caplockb; Failed to confirm locked"


Part replaced so far:
CAP
CAP motor
CAP lock pin motor
CAP to HBN cable CBL ASSY,HBZ-CAP P/N 314810702
HBN Card.
Both HBZ modules

Cause

Wrong hardware revision (revision 1) is set on new style CAP B
HBZB trace shows CAP B has a wrong H/W revision set. Must be revision = 2 for newer style CAP.

HBZA trace shows a correct H/W revision set for CAP A.

Revision 1 (old style) is set right after the "test_motor_present" gets the "hall_error_received=1"  This test is like checking a lock motor is connected or not to determine the CAP style.
Because we don't detect a lock motor, old style is asserted.

> hbza/log/stk/log_trace
> 2015-09-01T13:06:23.827122, servo, test_motor_present, hall_error_received=0
> 2015-09-01T13:06:23.947220, servo, test_motor_present, hall_error_received=0
> 2015-09-01T13:06:23.948278, cap, cap_hdw_rev_set: cap_hdw_revision = 2, revision
from db, CAP hardware revision = 2, mech = 4
>
> hbzb/log/stk/log_trace
> 2015-09-01T13:21:56.050047, servo, test_motor_present, hall_error_received=1
> 2015-09-01T13:21:56.170047, servo, test_motor_present, hall_error_received=1
> 2015-09-01T13:21:56.171090, cap, cap_hdw_rev_set: cap_hdw_revision = 1, revision
from db, CAP hardware revision = 1, mech = 4

Solution

Replaced the knuckle cable P/N 313928206 CBL ASSY,PNL-PNL,HBZ
Reboot CAP B, collect a log snapshot  and check in HBZB log_trace hardware revision 2 is set for CAP B

References

This solution has no attachment