Scalar i500 Maintenance Guide

(1)

ADVANCED DIGITAL INFORMATION CORPORATION

Maintenance Guide

(2)

The information contained in this document is subject to change without notice.

This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of ADIC.

ADIC shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory.

All trademarks within this document are the property of their respective owners.

All rights reserved. No part of this document may be copied or reproduced in any form or by any means, without prior written permission of ADIC Europe, ZAC des Basses Auges, 1 rue Alfred de Vigny, 78112 Fourqueux, France.

ADIC Europe assumes no responsibility for any errors that may appear in this document, and retains the right to make changes to these specifications and descriptions at any time, without notice.

This publication may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC Europe conveys no license under any patent or any other right.

ADIC Europe makes no representation or warranty with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, ADIC Europe reserves the right to revise or change this publication without obligation on the part of ADIC Europe to notify any person or organization of such revision of change.

Every effort has been made to acknowledge trademarks and their owners. Trademarked names are used solely for identification or exemplary purposes: any omissions are unintentional.

ADIC is a registered trademark and ADIC Europe is a trademark of Advanced Digital Information Corporation.

Published: Preliminary Document Number: 62-2301-01 Rev A

ADIC USA 11431 Willows Road NE Redmond, Washington 98052-4952 Tel.: 1-800-336-1233 Fax: 1-425-881-2296 ADIC Europe

ZAC des Basses Auges 1, rue Alfred de Vigny 78112 Fourqueux, France Tel.: 33-0-1-30-87-53-00 Fax: 33-0-1-30-87-53-01 ADIC-Germany GmbH&Co.KG Eschenstraße 3 89558 Böhmenkirch Germany Tel: 49-0-7332-83-0 Fax: 49-0-7332-83-135

(3)

1 About This Guide and Your Product

1

Product Safety Statements . . . 1

Product Model Number . . . 1

Explanation of Symbols and Notes . . . 1

2 Troubleshooting the Scalar i500 Library

3

How the Library Reports Problems . . . 3

Working with RAS Tickets . . . 4

RAS Ticket Error Codes . . . 4

T002 . . . 4 T003 . . . 5 T004 . . . 6 T005 . . . 7 T006 . . . 7 T007 . . . 8 T008 . . . 9 T009 . . . 9 T010 . . . 10 T011 . . . 11 T013 . . . 11 T017 . . . 12 T018 . . . 13 T019 . . . 13 T020 . . . 14 T021 . . . 14 T022 . . . 15 T023 . . . 15 T024 . . . 16 T025 . . . 16 T031 . . . 17 T032 . . . 18 T033 . . . 18 T034 . . . 19 T035 . . . 19 T036 . . . 20 T037 . . . 21

(4)

T038 . . . 21 T039 . . . 22 T040 . . . 22 T041 . . . 23 T045 . . . 23 T046 . . . 24 T047 . . . 24 T048 . . . 25 T049 . . . 26 T050 . . . 26 T051 . . . 26 T052 . . . 27 T060 . . . 27 T062 . . . 28 T063 . . . 29 T064 . . . 30 T065 . . . 30 T066 . . . 31 T067 . . . 31 T068 . . . 32 T069 . . . 33 T070 . . . 33 T071 . . . 34 T072 . . . 34

Closing RAS Tickets . . . 35

Using the Service Menu . . . 35

Interpreting LEDs. . . 35

LCB LEDs . . . 35

Amber LED on Blades. . . 36

Servicing a Blade Based on LED Status. . . 36

Tape Drive LEDs . . . 37

Fibre Port Link LED . . . 37

Fibre Port Link LED on Tape Drives . . . 38

Power Supply LEDs. . . 38

3 Adding, Removing, and Replacing

41

Before You Start . . . 41

Important Topics in the Scalar i500 User’s Guide . . . 41

Required Library State. . . 42

Required Tools . . . 42

General Service Guidelines. . . 42

CRU and FRU Listings . . . 43

Cable Spool . . . 44

Replacing the Cable Spool . . . 44

Control Module . . . 48

Replacing the Control Module . . . 49

Expansion Module . . . 51

Adding an Expansion Module . . . 51

Removing an Expansion Module. . . 52

Replacing an Expansion Module . . . 54

Front Bezels . . . 57

Replacing the Front Bezels . . . 57

I/E Station Lock Assembly. . . 58

(5)

I/E Station Slide Assembly . . . 59

Replacing the I/E Station Slide Assembly . . . 59

Library Control Blade (LCB) . . . 60

Replacing the LCB. . . 60

LCB Compact Flash Card . . . 61

Replacing the LCB Compact Flash Card. . . 61

Operator Panel (LCD) . . . 62

Replacing the Operator Panel . . . 62

Picker Assembly . . . 63

Replacing the Picker Assembly . . . 63

Power Supply . . . 65

Adding a Redundant Power Supply. . . 65

Removing a Redundant Power Supply . . . 65

Replacing a Power Supply . . . 66

Rackmount Kit . . . 66

Installing the Rackmount Kit . . . 66

Installing additional modules into the rack. . . 71

Tape Column . . . 75

Replacing a Tape Column . . . 75

Tape Drive . . . 76

Adding a Tape Drive . . . 76

Removing a Tape Drive. . . 77

Replacing a Tape Drive . . . 77

Y Motor . . . 78

Replacing the Y Motor . . . 78

4 Common Service Procedures

81

Using the Service Port. . . 81

Logging in with Service Privileges . . . 81

Capturing a Snapshot . . . 81

Saving the Library Configuration . . . 82

Restoring the Library Configuration. . . 82

Taking the Library Online/Offline . . . 83

Powering the Library On . . . 84

Powering the Library Off . . . 84

Restarting the Library . . . 85

Manually Unlocking the I/E Station door . . . 85

Testing Your Fix . . . 85

5 Library Drawings

87

Component Diagrams . . . 87

Library, Front View . . . 87

Library, Front View Showing Front Bezels . . . 88

Library Rear View . . . 89

Control Module . . . 90

Library, Front View, I/E station Door Open . . . 90

Library, Front View, Access Door and I/E station Door Open . . . 91

I/E station Lock Assembly . . . 91

I/E station Slide Assembly . . . 92

Access Door, Inside, With Operator Panel . . . 92

(6)

Picker. . . 94

Cable Spool . . . 95

Library Control Blade (LCB) . . . 96

Power Supplies . . . 97

Tape Drive, Front. . . 98

Tape Drive, Rear . . . 99

Rackmount Kit Accessories for Racks with Square Holes . . . 100

Rackmount Kit Accessories for Racks with Rounded Holes . . . 100

Rackmount Kit Accessories: Rackmount Rails . . . 101

Rackmount Rails in Rack . . . 101

Rackmounted Library . . . 103

System Diagrams . . . 104

Major Component Connections . . . 104

(7)

Tables

1 About This Guide and Your Product

2 Troubleshooting the Scalar i500 Library

Table 1 Blade LEDs . . . 36

Table 2 Amber LED on Blades . . . 36

Table 3 Tape Drive Activity . . . 37

Table 4 Fibre Port Link LED on Tape Drive . . . 38

Table 5 Power Supply LEDs . . . 38

3 Adding, Removing, and Replacing

Table 6 Important topics in the Scalar i500 User’s Guide . . . 41

Table 7 Servicing library components: Library state required . . . 42

Table 8 CRUs and FRUs . . . . 44

4 Common Service Procedures

(8)

(9)

Figures

1 About This Guide and Your Product

2 Troubleshooting the Scalar i500 Library

Figure 1 Location of Tape Drive LEDs . . . 37

3 Adding, Removing, and Replacing

4 Common Service Procedures

5 Library Drawings

Figure 2 Library, Front View (14U library) . . . 87

Figure 3 Library, Front View Showing Front Bezels . . . 88

Figure 4 Library, Rear View (14U library) . . . 89

Figure 5 Control Module Front . . . 90

Figure 6 Library, Front View, I/E Station Door Open . . . 90

Figure 7 Library Front View, Access Door and I/E Station Door Open . . . 91

Figure 8 I/E Station Lock Assembly . . . 91

Figure 9 I/E Station Slide Assembly (removed from module) . . . 92

Figure 10 Access Door, Inside (showing back of Operator Panel) . . . 92

Figure 11 Operator Panel . . . 93

Figure 12 Picker with Cable Spool, Y motor, and Z motor . . . 94

Figure 13 Picker . . . 94

Figure 14 Cable Spool . . . 95

Figure 15 Library Control Blade . . . 96

Figure 16 Power Supplies . . . 97

(10)

Figure 19 Tape Drive, Rear View . . . 99

Figure 20 Rackmount Kit accessories for racks with 9.5mm square holes . . . 100

Figure 21 Rackmount Kit accessories for racks with 7.2mm round holes . . . 100

Figure 22 Rackmount Rails (separate from rack) . . . 101

Figure 23 Rackmount Rails in Rack (as viewed from the front, showing studs installed in rack) . 101 Figure 24 Rackmount Rails in Rack (as viewed from the back, showing studs installed in rack) . 102 Figure 25 Rackmounted Library, Front . . . 103

Figure 26 Rackmounted Library, Back . . . 104

Figure 27 Cabling Diagram . . . 104

(11)

About This Guide and Your Product

This guide is intended for service personnel who perform maintenance on the Scalar i500®. Be aware that you must be logged in to the Scalar i500 with service level privileges to perform many of the instructions provided in this guide.

Product Safety Statements

The Scalar i500 is designed for storing and sharing electronic data via a magnetic tape library system. Any other application of the library is not considered the intended use. ADIC will not be held liable for damage arising from unauthorized use of the product. The user assumes all risk in this aspect.

This unit is engineered and manufactured to meet all safety and regulatory requirements. Be aware that improper use may result in bodily injury, damage to the equipment, or interference with other equipment.

Product Model Number

The Scalar i500 model number is:

Explanation of Symbols and Notes

The following symbols appear throughout this document to highlight important information.

Note

Be sure to read all operating instructions in this manual and in the System, Safety, and

Regulatory Information Guide before servicing and operating the Scalar i500.

WARNING BEFORE POWERING ON OR USING THIS EQUIPMENT, READ THE SYSTEM, _{SAFETY, AND REGULATORY INFORMATION GUIDE. KEEP THE GUIDE FOR} FUTURE REFERENCE.

(12)

Getting More Information or Help

More information about this product is available on the Customer Service Center website at

www.adic.com/csc. The Customer Service Center contains a collection of information, including answers to frequently asked questions (FAQs). You can also access software, firmware, and drivers through this site. For further assistance, or if training is desired, contact ADIC:

CAUTION Indicates a situation that may cause possible damage to equipment, loss of _{data, or interference with other equipment.}

Note

Indicates important information that helps you make better use of your system.

Note

Release Notes are also available for this product. The Release Notes describe changes

to your system or firmware since the last release, provide compatibility information, and discuss any known issues and workarounds. The Release Notes can be found in the product box or at www.adic.com/manuals.

ADIC Technical Assistance Center (ATAC) in the USA:

800-827-3822

ATAC in Europe or Japan: 00-800-9999-3822 For additional contact information: www.adic.com/contact

(13)

Troubleshooting the Scalar i500 Library

The Scalar i500 tape library is a member of the growing intelligent library family. Like all intelligent libraries, the Scalar i500 can automatically detect host servers in the storage area network (SAN) and perform periodic self-tests to ensure that the library is fully operational. If it detects a problem, the Scalar i500

isolates where the problem exists and provides helpful instructions for resolving it. The Scalar i500 also supports geographic addressing, which means that you can install tape drives in any open drive slot, and the library will automatically update its configuration model without requiring you to assign the address of the drive yourself.

All Scalar i500 libraries consist of one control module and can include up to three 5U expansion modules or four 9U expansion modules, to a maximum height of 41U. All libraries taller than 14U must be

rackmounted.

The control module houses the central intelligence of the library; without it, the library cannot function. The control module contains several essential components, including the library control blade and the robotic picker assembly. The library control blade controls the library’s functions, while the robotic picker assembly is responsible for physically retrieving data cartridges from the library’s modules, inserting the cartridges into the appropriate tape drive, and returning them to their appropriate storage slot. The control module also provides a configurable I/E Station for importing and exporting data cartridges, and several columns of fixed storage space. You can control the library using its LCD Operator Panel, or by using the remoteWeb client. Expansion modules are available in two sizes: 5U and 9U. Each expansion module provides a configurable

I/E Station and additional space for fixed tape storage.

How the Library Reports Problems

The Scalar i500 uses advanced problem detection, reporting, and notification technology to alert customers of problems as soon as they occur. The library performs numerous self-tests to monitor the library’s temperature, voltage and currents, and standard library operations. It performs these self-tests each time the library is powered on, and during normal operation when the library is idle.

If the self-test detects a problem, the library generates a service report, or RAS ticket, that identifies which component is likely causing the problem. The library’s LEDs may also turn on or off and flash to indicate an abnormal state. If the problem is not severe, the library continues to provide full functionality to all unaffected

partitions.

Note

When adding expansion modules to the library, you must add modules of the

same size. The library cannot contain a combination of 5U and 9U expansion modules.

(14)

When possible, the library provides instructions for resolving problems. These instructions appear on the library’s operator panel, and are also available via the remote Web client. Access the library’s online Help system if you have questions about the instructions provided.

Customers can frequently resolve a simple problem themselves, but if the problem is complex or involves a field replaceable unit (FRU), the customer must contact service. Only qualified service technicians can service FRUs.

Working with

RAS Tickets

RAS tickets are special service reports that describe the current reliability, availability, and serviceability

(RAS) of the library. RAS tickets provide detailed information about system problems.

RAS Ticket

Error Codes

When the library detects a problem, it generates an error code and displays it in the RAS Ticket report, along with a full description of the problem and suggestions for resolving it.

The following tables provide details on each RAS Ticket error code.

T002

T002 - Put Operation Failed, Tape Final Position Unknown, Motion OK

Description The library cannot successfully put a tape into a drive, storage or IE location and the final “resting place” of the tape is unknown. There are no additional recovery logic paths to be exercised. Fundamental servo control seems OK. If the operation was initiated by a host move media, the move media

command has failed with a SK/ASC/ASCQ 4h/15h/01h (hardware mechanical positioning error).

Detection Scenarios Put is not successful and put recovery is not successful and tape is not known to be properly seated in picker or storage slot.

Root Causes • Magazine is damaged.

• Magazine is wrong type for tape cartridge.

• Cell is blocked by foreign material, not clipped in and seated correctly. • Calibration problem results in improper robot position.

• Picker offset problem. • Cartridge is damaged.

• Unlabeled cartridge or intermittently readable cartridge label in destination. • Drive load mechanism not working.

• A variety of picker problems such as slipping gears, encoder issues, etc.

Possible CRUs/FRUs • Cable spool • Chassis • Robot assembly • LCB • Tape Cartridge Components/Agents Involved

(15)

T003

Triggering Element and Fault Code Combinations

m_MoveFailedPut

Resolution DR001 - Manually Recover Tape 1 Take all partitions offline

2 Open the library bulk load doors

3 Use the thumbwheel on the picker to drive the cartridge out 4 Close the library bulk load doors

5 Import the tape via host application to the appropriate partition.

T003 - Get Operation Failed, Tape Final Position Unknown, Motion OK

Description The library cannot successfully get a tape from a drive, storage or IE location. The final “resting place” of the tape is unknown. There are no additional recovery logic paths. Fundamental servo control appears to be OK. If the operation was initiated by a host move media, the move media command has failed with an ASC/ASCQ of 4h/15h/01h (hardware mechanical positioning error).

Detection Scenarios Get is not successful and put recovery is not successful and tape is not known to be properly seated in picker or storage slot.

Root Causes • Magazine is damaged.

• Magazine is wrong type for tape cartridge.

• Cell is blocked by foreign material, not clipped in and seated correctly. • Calibration problem results in improper robot position.

• Picker offset problem. • Cartridge is damaged.

• Unlabeled cartridge or intermittently readable cartridge label in destination. • Drive load mechanism not working.

Motion Control Subsystem

m_MoveFailedGet

(16)

T004

Resolution DR001 - Manually Recover Tape 1 Take all partitions offline

2 Open the library bulk load doors

3 Use the thumbwheel on the picker to drive the cartridge out 4 Close the library bulk load doors

5 Import the tape via host application to the partition.

T004 - Put Operation Failed, Tape Back In Source Location, Motion OK

Description The library cannot successfully put a tape into the intended target drive, storage or IE location. The library has successfully returned the tape to the source location. Fundamental servo control appears to be OK.

Detection Scenarios Put is not successful and put recovery is not successful at the destination element. Recovery logic has allowed the tape to be returned to the initial source location. If the operation was initiated by a host move media, the move media command has failed with a SK/ASC/ASCQ 4h/15h/01h.

Root Causes • Magazine is damaged, wrong type, cell is blocked by foreign material, not clipped in and seated correctly.

• Calibration problem. • Picker offset problem.

• Destination cell full with labeled cartridge (invalid inventory).

• Destination cell is full with cartridge that has damaged label or is unlabeled or has an intermittently readable label.

• Motion Control Subsystem • Logical Medium Changer

• SCSI Medium Changer Device Server

m_MoveFailedPutSourceRestored

Resolution DR004 - Manually Inspect Destination Element

1 Identify the coordinate provided in the Details of the ticket. 2 Open the library bulk load doors and locate the problem location. 3 Inspect it for the presence of unlabeled media, or other contamination or

damage that prevented the library robot from placing the tape cartridge.

(17)

T005

T006

T005 - X, Y, T Motion Profile Failure, Tape in Picker, Motion NOT OK

Description Any X, Y, T motion failure that cannot be considered a complete obstruction. This problem only occurs during a move and NOT a get or put. Because the tape is in the picker, tape recovery must be a part of the resolution strategy. This ticket cause specifically excludes any Z axis motion failures that are typically associated with get or put actions. Specifically included are motion failures that occur while pivoting, moving on the x axis or moving on the y-axis.

Detection Scenarios • A specified move in the x-axis cannot complete. • A specified move in the y-axis cannot complete. • A specified movement in the T-axis cannot complete.

Root Causes • A large number of electrical hardware failures. Code or hardware detects that motion control is not occurring properly (encoder issues, motor driving circuit issues, motor winding issues, cable connections issues, etc.). • A relatively small number of mechanical hardware errors that do not result

in the detection of a complete obstruction but where motion control does not appear to be normal (contamination or damage to encoder wheel, high friction, etc).

Possible CRUs/FRUs • Cable spool • Chassis • Tape Drive • Robot assembly • LCB • Tape Cartridge • Y-carriage assembly Components/Agents Involved

m_XYThetaMotionProfileErrorTapeInPicker

Resolution DR005 - Motion Failure Diagnostic

T006 - X, Y, T Motion Profile Failure, No Tape In Picker, Motion NOT OK

Description An unrecoverable motion failure occurs at an operational point where a tape is not in the picker. Because the tape is not in the picker, tape recovery is not necessary as part of the resolution to this issue. This cause specifically excludes any Z axis motion failures. Specifically included are motion failures that occur while pivoting, moving on the x axis or moving on the y-axis.

Detection Scenarios • A specified move in the x-axis cannot complete. • A specified move in the y-axis cannot complete. • A specified movement in the T-axis cannot complete.

(18)

T007

Root Causes • Human intervention that results in foreign material or an obstructing object in a library motion path.

• Certain damaged hardware conditions that obstruct motion at a particular point along an axis.

Possible CRUs/FRUs • Cable spool • Chassis • Tape Drive • Robot assembly • Tape Cartridge • Y-carriage assembly Components/Agents Involved

m_XYThetaMotionProfileError

T007 - X, Y, T Motion Obstruction, Motion OK

Description A complete physical obstruction exists in a motion path that precludes repeated attempts to move beyond a certain point in the range of motion. Servo control appears normal but a move profile cannot be completed. Cartridge may have been returned to a home slot.

Detection Scenarios • A specified move in the x-axis cannot complete but motion control appears normal.

• A specified move in the y-axis cannot complete but motion control appears normal.

• A specified move in the T-axis cannot complete but motion control appears normal.

Root Causes • A large number of electrical hardware failures. Code or hardware detects that motion control is not occurring properly (encoder issues, motor driving circuit issues, motor winding issues, cable connections issues, etc.). • A relatively small number of hardware errors that do not result in complete

obstruction but where servo control does not appear to be normal.

Possible CRUs/FRUs • Cable spool • Chassis • Tape Drive • Robot assembly • Tape Cartridge • Y-carriage assembly Components/Agents Involved

(19)

T008

T009

m_XYThetaObstruction

T008 - Cannot Home, Motion OK

Description Robot motion and servo control appear normal but home sensors do not transition when the robot is moved through prescribed search distances and times.

Detection Scenarios • X home sensor does not transition while homing • Y home sensor does not transition while homing • T home sensor does not transition while homing • Z home sensor does not transition while homing

Root Causes • Malfunctioning home sensors

• Missing or damaged mechanical flags that trigger home sensors • Hardware failures that result in apparent normal motion according to

encoders but no actual motion (ex. slipping gears)

Possible CRUs/FRUs • Chassis

• Robot assembly • LCB

Components/Agents Involved

m_HomeFailure

T009 - Drive Load Unsuccessful, Motion OK

Description The robot has successfully completed all motion profiles associated with putting to a drive but the drive reports that the tape cartridge did not load.

Detection Scenarios • While checking the status of a drive after a put motion profile to the drive is completed, the drive does not report back a loaded state.

Root Causes • Defective drive

• Defective tape cartridge

• Motion profile was successful as detected at motor encoders but tape did not get placed far enough

• Picker dragged cartridge back out of drive but not far enough to trigger picker cartridge present sensor

(20)

T010

Possible CRUs/FRUs • Cable Spool • Chassis • Tape Drive • Robot assembly • LCB • Tape Cartridge Components/Agents Involved • UDS Subsystem

• Motion Control Subsystem

m_DriveLoadUnsuccessful

Resolution DR006 - General Drive Diagnostic

T010- Drive Unload Failed

Description The library is expecting the drive to achieve an unloaded state but the drive does not.

Detection Scenarios • After being issued a move media from a host that requires a get from a drive, the drive never achieves the unloaded state.

• When GUI commands are issued that require a drive unload (manual drive unload, move media, etc.) and the drive never achieves the unloaded state.

Note

This ticket cause will interact with the “explicit unload” behavior as called out in the 0-11318 functional spec. Since the library will always issue an unload command, it will not be possible to determine if a host unload command failed first followed by a subsequent failure of a library issued unload command.

Root Causes • Drive fails to unload after the library issues an unload command.

Possible CRUs/FRUs • Tape Drive • Tape Cartridge

• UDS Subsystem

• Logical Medium Changer

m_DriveUnloadUnsuccessful

Resolution DR003 - Drive Unload Diagnostic

1 Retry drive unload from host backup application. 2 Open the library bulk load doors

3 Push the blue unload button on the front of the drive. Remove the tape if it is ejected by the drive.

Contact Service if the tape remains stuck in the drive.

(21)

T011

T013

T011- Drive Over Eject Condition

Description The library is about to perform a get from a drive and checks the drive status to determine if the tape cartridge is ejected. LTO drives have demonstrated a specific failure mode where they eject a tape in a non-normal manner. Normally upon eject, the tape is in a particular position where it is clear of the robot motion path and it cannot be re-loaded due to mechanical interlock within the drive load mechanism. The historical failure mode is that the tape slips an additional amount out of the drive throat which re-arms the load mechanism of the drive. Two subsequent problems can occur. The over ejected tape can become an obstruction hazard for robot moves. In addition, the robot get operations can then re-trigger the drive load mechanism by bumping the tape during a get. There can be a “tug of war” between robot and drive OR the drive can win the tug of war resulting in the loading of a phantom tape. When the drive loads a phantom tape, there are resulting drive errors. The goal of reporting this problem is to identify tape drives that over eject tapes to avoid the two types of problems.

Detection Scenarios Library checks drive status prior to moving to perform a get. It is trying to determine if the drive is in an unloaded state and if a cartridge is present. If a cartridge is not reported as present, the library can assume it was “over ejected”.

Root Causes • The drive eject process did not result in the proper position of the ejected tape.

Possible CRUs/FRUs • Tape Drive

• UDS Subsystem

m_DriveOverejectCondition

Resolution RR001 - Remove and Replace Drive Sled • Contact service for drive replacement.

T013- Cannot Read or Invalid Library Serial Number Label

Description The library logic learns the SN of the system by reading an internal SN label. This is done at first boot up from a “cleared to ship” condition in order to establish the SN. It is also done on subsequent boot ups to confirm that the LCB is in the proper library. The library will report a problem when it cannot read a SN or detects an invalid SN. A different motion related problem will be reported if motion is preventing the proper reading of the SN.

Detection Scenarios • At first boot up from clear to ship, the library must establish the SN for the first time. There may be no SN in system memory at this point.

• Any power up. System memory already has a SN established for the LCB. • An LCB is improperly swapped into a different physical chassis and the

(22)

T017

Root Causes • LCB’s swapped between libraries • Label is damaged

• Bar code scanner not working properly

• Entire communication path to bar code scanner is not working properly.

Possible CRUs/FRUs • Cable spool • Chassis • LCB • Robot assembly • Y-carriage assembly Components/Agents Involved • (none) Triggering Element and Fault Code Combinations

m_InvalidSerialNumber

Resolution DR007 - Bar Code Scanner Diagnostic

T017- Invalid Storage or IE Position

Description Calibration completes and the coordinates of each storage and IE element are calculated. The calculated values are determined to be outside travel limits that have been established for the robot.

Detection Scenarios • Calculated element positions fail validity check against travel limits.

Root Causes • Calibration targets not in position

• Calibration sensor detects edges but is not correctly finding calibration target edges

Possible CRUs/FRUs • Cable spool • Chassis • Fiducial Targets • Robot assembly • Y-carriage assembly Components/Agents Involved

m_InvalidStorageIEPosition

Resolution DR008 - Calibration Diagnostic

(23)

T018

T019

T018- Invalid Drive Position

Description Calibration completes and the coordinates of each drive are calculated. The calculated values are determined to be outside travel limits that have been established for the robot.

Detection Scenarios • Calculated element positions fail validity check against travel limits

Root Causes • Drive calibration target is not in position

• Calibration sensor detects edges but is not correctly finding calibration target edges.

Possible CRUs/FRUs • Cable spool • Chassis • Tape Drive • Robot assembly • Y-carriage assembly Components/Agents Involved

m_InvalidDrivePosition

T019 - Cannot Calibrate Drive, Motion OK

Description System electrically detects a drive and is able to scan the bar code label but cannot successfully calibrate the position of the drive. The calibration search pattern completes successfully.

Detection Scenarios • Calibration motion completes but edge finding of one or more edges does not occur

Root Causes • Calibration sensor not functioning properly • Calibration target not functioning properly

• Drive or robot position is so far off nominal that search pattern cannot locate target.

Possible CRUs/FRUs • Cable spool • Chassis • Tape Drive • Robot assembly • Y-carriage assembly Components/Agents Involved

(24)

T020

T021

T020 - Cannot Calibrate Storage, Motion OK

Description System cannot successfully calibrate the position of a storage magazine but the calibration search pattern completes successfully.

Detection Scenarios • Calibration motion completes but edge finding of one or more edges does not occur

Root Causes • Calibration sensor not functioning properly • Calibration target not functioning properly

• Drive or robot position is so far off nominal that search pattern cannot locate target.

Possible CRUs/FRUs • Cable spool • Chassis • Fiducial Targets • Robot assembly • Y-carriage assembly Components/Agents Involved

m_StorageCalibrationFailure

T021 - Lost Electrical Connection/Communication With Drive Sled

Description The library had been communicating with a drive sled and had considered it to be assigned to a logical library. Two way communications no longer occur. This ticket is specifically NOT caused by physical removal of a drive if the drive is not assigned to a partition.

Detection Scenarios • Routine polling of the sled can no longer occur. Polling interval is TBD. • Specific library to drive sled commands are not responded to

Root Causes • Drive is physically removed/unplugged (intentional or never screwed in correctly)

• Various hardware failures on the drive sled • Various hardware failures in the library

• Tape Drive • LCB

(25)

T022

T023

TBD

T022 - Lost Electrical Connection/Communication with Drive Brick

Description Internal to the drive, the sled control board can no longer communicate with the drive brick.

Detection Scenarios • Routine polling between sled control board and drive brick can no longer occur. Polling interval is TBD.

• Specific commands such as unload, reset, etc. are not responded to

Root Causes • Cable broken, unlplugged, damaged, etc. • Drive brick failure

• UDS Subsystem

TBD

T023 - Drive Sled Fan Spinning Too Slow or Not At All

Description A drive sled fan is detected to be spinning too slow or not at all.

Detection Scenarios • Regular polling/monitoring of the fan indicates a problem. Polling interval TBD.

Root Causes • Hardware failure of fan • Wiring or PCBA failure • Blocked air paths • Physical obstruction

• UDS Subsystem

(26)

T024

T025

TBD

T024 - AC Power Loss

Description A power supply has detected loss of AC power. AC power loss to a single power supply CM is unlikely to be able to post this ticket due to the speed at which system shut down occurs after an AC loss. This Ticket is most likely to occur when there is AC loss to a redundant power supply in a CM or any supply in any EM.

Detection Scenarios • AC power status from the supply creates an interrupt that is managed by software.

Root Causes • AC supply is gone (cord removed, customer side AC failure, etc.) • Individual on/off switch for the supply has been set to off

• Hardware failure inside supply

Possible CRUs/FRUs • Power supply

• Hardware

PowerSupply_ACFail

Resolution DR009 - AC Failure Diagnostic

1 Check the facility AC power and the power supply power switch. 2 Correct them if necessary and Close the ticket.

• If the facility AC power and the power supply power switch are OK, contact service for possible power supply replacement.

T025 - Power Supply Hardware Failure

Description Power supplies report 4 failure conditions that are considered to be a hardware failure within the supply: Fan Fail, Over Temp, DC Fail and Over Current. These failures can occur in both single and redundant power supply CM’s and any EM with a power supply.

Detection Scenarios • Regular monitoring of power supply status results in one of 4 detected failures.

(27)

T031

Root Causes • Detected fan failure in the supply

• Detected over temp condition in the supply • Detected DC failure in the supply

• Detected over current failure in the supply.

• LCB • Power supply Components/Agents Involved • Hardware Triggering Element and Fault Code Combinations

• PowerSupply_DCFail • PowerSupply_FanFail • PowerSupply_OverCurrent • PowerSupply_OverTemperature

Resolution RR003 - Remove and Replace Power Supply

• Contact service for possible power supply hardware replacement.

T031 - Can’t Unlock IE Station

Description System logic or external command is requiring IE station lock to unlock but it will not.

Detection Scenarios • When unlock action is attempted, lock/unlock position sensor does not detect the proper state

Root Causes • Lock mechanism not working properly • Lock position sensor not working properly

• Mechanical binding or obstruction prevents proper motion and detection • Mechanical failure of sensor flag

• I/E lock assembly • I/E mechanism • LCB

• Display assembly

• Physical Medium Changer

m_IEUnlockFail

(28)

T032

T033

Resolution DR011 - IE Lock Diagnostic 1 Shut down the library.

2 Open all IE station doors. Select Self Test to trigger the library to verify all doors are open. If the test fails, replace the IE assembly.

3 Close all IE station doors. Select Self Test to trigger the library to verify all IE doors are closed. If the test fails, replace the IE assembly.

4 Select Self Test to trigger the library to verify that all IE locks can be locked and opened. If the test fails, replace the IE lock assembly.

5 Attempt to open all IE doors to confirm that doors are locked. If any of the doors open, replace the IE lock assembly.

6

T032 - Can’t Lock IE Station

Description System logic or external command is requiring IE station lock to lock but it will not.

Detection Scenarios • When lock action is attempted, lock/unlock position sensor does not detect the proper state

Root Causes • Lock mechanism not working properly • Lock position sensor not working properly

• Mechanical binding or obstruction prevents proper motion and detection • Mechanical failure of sensor flag

• I/E lock assembly • I/E mechanism • LCB

• Display assembly

m_IELockFail

Resolution DR011 - IE Lock Diagnostic

T033 - Drive Tape Alert 3 – Hard Read or Write Error

Description System determines that the drive has issued a Tape Alert 3 indicating an unrecoverable read, write or positioning error.

Detection Scenarios • Tape drive issues a Tape Alert 3 which is recognized by the library during the continuous 4 second polling cycle of drive status.

Root Causes • Drive has determined that there is a problem per its internal algorithms.

(29)

T034

T035

UDS Subsystem

m_TapeAlert3faultCode

Resolution RR008 - Remove and Replace Tape Cartridge

• If the cartridge is a FUP tape or cleaning tape managed by the library; export the tape via the library Operations>Media>Export function. Retire the tape from service.

• If the tape is a cleaning tape or data tape managed by a host application, export the tape via the host application. Retire the tape from service.

T034 - Drive Tape Alert 4 – Media

Description System determines that the drive has issued a Tape Alert 4 indicating an unrecoverable read, write or positioning error that the drive specifically isolates to a the media.

Possible CRUs/FRUs • Tape Cartridge

UDS Subsystem

T035 - Drive Tape Alert 5 – Read Failure

Description System determines that the drive has issued a Tape Alert 5 indicating an unrecoverable read error where isolation is uncertain between drive and media.

(30)

T036

UDS Subsystem

T036 - Drive Tape Alert 6 – Write Failure

Description System determines that the drive has issued a Tape Alert 6 indicating an unrecoverable write error where isolation is uncertain between drive and media.

UDS Subsystem

(31)

T037

T038

T037 - Drive Tape Alert 8 – Not Data Grade

Description System determines that the drive has issued a Tape Alert 8 indicating that the tape cartridge in the drive is not a data grade tape.

UDS Subsystem

T038 - Drive Tape Alert 9 – Write Protected

Description System determines that a write was attempted on a write protected tape.

Detection Scenarios • Tape drive issues a Tape Alert 9

Root Causes • Write protect feature on tape is protecting the tape but the user is trying to write to it.

UDS Subsystem

Resolution DR014 - Write Protect or Worm Diagnostic

1 Determine whether the tape should be write protected or not.

If not, export the tape via your back up application and correct the problem be manually changing the write protect switch on the tape cartridge.

If the tape is correctly set as a “read only” tape, investigate your host application to determine why a write was attempted.

(32)

T039

T040

T039 - Drive Tape Alert 12 – Unsupported Format

Description System determines that the drive has issued a Tape Alert 12 indicating that the media loaded is an unsupported format. In the case of the IBM LTO family of drives, full backward read and write compatibility stopped when LTO 3 was introduced. LTO 3 cannot write in LTO 1 format. Therefore an LTO 1 tape is an unsupported format when trying to write to it with an LTO 3 drive.

UDS Subsystem

Resolution DR015 - Unsupported Format Diagnostic

• If the cartridge was loaded to the drive via the Library GUI, export the tape via the library Operations>Media>Export function. Import the proper type of tape for the desired operation and continue.

• If the tape was loaded to the drive via a host application, export the tape via the host application. Import the proper type of tape for the desired operation and continue.

T040 - Drive Tape Alert 15 – MIC Chip Failure

Description System determines that the drive has issued a Tape Alert 15 indicating that MIC (memory in cassette) of the media loaded is not working properly.

UDS Subsystem

(33)

T041

T045

T041 - Drive Tape Alert 16 - Forced Eject

Description System determines that the drive has issued a Tape Alert 16 indicating that an unload of a drive was triggered while the drive was actively reading or writing. The source of the unload can be either an operator initiated manual push button on the drive itself or a GUI initiated command.

UDS Subsystem

T045 - Drive Tape Alert 20 – Clean Now

Description System determines that the drive has issued a Tape Alert 20 indicating that the drive requires cleaning. This should be coincident with a Bang C on the drive seven segment display.

(34)

T046

T047

Components/Agents Involved UDS Subsystem Triggering Element and Fault Code Combinations

Resolution DR018 - Manually Clean Drive

1 Enable the library cleaning function, import cleaning tapes and clean the drive.

OR

1 Use host application cleaning tools to clean the drive.

T046 - Drive Tape Alert 21 – Clean Periodic

Description System determines that the drive has issued a Tape Alert 21 indicating that the drive requires cleaning. This should be coincident with a Bang C on the drive seven segment display.

UDS Subsystem

Resolution DR018 - Manually Clean Drive

1 Enable the library cleaning function, import cleaning tapes and clean the drive.

OR

1 Use host application cleaning tools to clean the drive.

T047 - Expired Cleaning Media

Description System determines that a cleaning media is expired.

Detection Scenarios • Tape drive issues a Tape Alert 22

• Code that manages library based cleaning determines that a cartridge is consumed based on actively managing the use count.

Root Causes • Cleaning tape is used up.

(35)

T048

UDS Subsystem

m_ExpiredCleaningMedia

T048 - Drive Tape Alert 23 – Invalid Cleaning Tape

Description System determines that the drive has issued a Tape Alert 23 indicating that the drive was expecting a cleaning tape but the loaded cartridge is not a cleaning tape.

Root Causes • User or library attempts to mount a cleaning tape but the tape is not actually a cleaning tape.

• User mistakenly loads a data tape as a cleaning tape

• Inventory or application issue results in data tape being loaded when drive expects cleaning tape

UDS Subsystem

(36)

T049

T050

T051

T049 - Drive Tape Alert 30 – Hardware A

Description System determines that the drive has issued a Tape Alert 30 indicating a hardware error that requires a drive power cycle before the drive might recover to a usable state.

UDS Subsystem

T050 - Drive Tape Alert 31 – Hardware B

Description System determines that the drive has issued a Tape Alert 31 indicating a hardware error that requires a drive power cycle before the drive might recover to a usable state.

UDS Subsystem

T051 - Drive Tape Alert 32 – Interface

Description System determines that the drive has issued a Tape Alert 32 indicating a tape drive has detected a problem with the application client interface.

(37)

T052

T060

UDS Subsystem

Resolution DR012 - Host Cabling Diagnostic

1 Check the external drive cabling and connections for completeness or possible damage.

T052 - Drive Tape Alert 33 – Eject Media Error Recovery

Description System determines that the drive has issued a Tape Alert 33 indicating that the drive requires a tape to be ejected in order to resolve a problem.

UDS Subsystem

T060 - Door Open

Description At boot time or run time the library detects that any door is open when the library is correctly terminated and is in 9 of 15 valid frame configurations.

Detection Scenarios • Code detects 9 specific frame configurations (out of 15 total) and the door is open. (note: The door open bit is only valid in a properly terminated library stack. An unterminated library stack will appear to be equivalent to a 3 EM stack. Therefore the door open bit cannot be Detection of 3 EM’s cannot be distinguished as a real configuration or a mis be caused by aresults in an indeterminate case where a door open cannot be distinguished from a missing terminator)

(38)

T062

Root Causes • Door is open A stack of frames is not terminated properly at run time or boot time. This includes missing or removed cables or terminators and various electrical hardware failures.

• Any door is actually open and the system is in one of the 6 possible configurations with 3 EM’s.

• A number of electrical hardware failures in the door switch circuit (this includes intermittent issues)

• Mechanical issues where door switch is not being made even though door is closed (this includes intermittent issues)

• LCB

• Module-to-module cable • Module terminator

• Environmental Management Subsystem

TBD

Resolution DR019 – Door Open Diagnostic

T062 - Frame Configuration Problem

Description At boot time or run time the library physical frame configuration is not valid.

Detection Scenarios • Code determines that there is greater than 1 CM module based on geographic address bits

• Code detects 5 frames or greater above the CM per the geographic address bits

• Code detects 5 frames or greater below the CM per the geographic address bits

• Code detects that one or more geographic address bit patterns do not match a valid configuration

• The code detects/communicates with a device (IE stations, power supplies, drives, blades, fan blades) that should not exist per the detected frame count and frame configuration.

• Code determined frame configuration based on frame count and geographic address bit pattern does not match hard stops found by y motion tests. • Code has compared the current detected configuration to a persisted

configuration and it does not match.

(39)

T063

Root Causes • Greater than 1 CM module exists in a stack of frames wired together • 5 frames or greater are actually above the CM

• 5 frames or greater are actually below the CM

• Hardware failure results in one or more invalid geo bit patterns.

• Hardware failure results in one or more valid but incorrect geo bit patterns when compared to frame count (more frames detected than actual or less frames detected than actual)

• LCB • Module-to-module cable • Module terminator Components/Agents Involved • Hardware Triggering Element and Fault Code Combinations • ChassisConfiguration_FifthModuleAbove • ChassisConfiguration_FifthModuleBelow • ChassisConfiguration_FrameIDStateChange • ChassisConfiguration_InvalidLowerFrameBits • ChassisConfiguration_InvalidUpperFrameBits • ChassisConfiguration_MissingLowerBoxToBoxTerminatorOrCable • ChassisConfiguration_MissingUpperBoxToBoxTerminatorOrCable • ChassisConfiguration_MultipleCMDetected

Resolution DR010 - EM Connectivity Diagnostic

1 Verify that the terminators and all module to module cables plugged in properly. If they are not, power down the library, plug the cables in and power the library back on. When the library powers up, it should detect the presence of the cables and terminators and properly configure itself.

T063 - Cannot Read or Mismatch WWN Label

Description The library logic learns the library WWN of the system by reading an internal WWN bar code label. This is done at first boot up from a “cleared to ship” condition in order to establish the WWN. It is also done on subsequent boot ups to TBD. The library will report a problem when it cannot read a the WWN. A different motion related problem will be reported if motion is preventing the proper reading of the WWN.

Detection Scenarios • At first boot up from clear to ship, the library must establish the WWN for the first time. There may be no WWN in system memory at this point.

• Any power up. System memory already has a WWN established for the LCB.

• An LCB is improperly swapped into a different physical chassis and the system reads the physical chassis WWN label.

(40)

T064

T065

Root Causes • LCB’s swapped between libraries • Label is damaged

• Bar code scanner not working properly

• Entire communication path to bar code scanner is not working properly.

Possible CRUs/FRUs • Cable spool • Chassis • Robot assembly • Y-carriage assembly • LCB Components/Agents Involved

• Physical Medium Changer

• m_InvalidWWN

Resolution DR007 - Bar Code Scanner Diagnostic

T064 - LCB Hardware Failure

Description The library encounters an error which appears to be isolated to hardware on the LCB itself.

Detection Scenarios • Code detects a board level voltage problem.

Root Causes • Board level voltage problems

Possible CRUs/FRUs • LCB

• Hardware

• LCB 48 V Fuse / is blown

Resolution TBD

T065 - LCB Robot Power Fuse (F3) Blown (42volt bus)

Description The library detects that the 42V, F3 picker power fuse located on the LCB has blown.

Detection Scenarios • Monitoring of voltage divider indicates partial or complete voltage drop (monitoring frequency?)

Root Causes • Board level hardware failures

• Permanent or temporary short in cables, connectors, picker

• Various hardware failures in picker that cause too much current to be drawn

(41)

T066

T067

Possible CRUs/FRUs • LCB • LCB Picker Fuse Components/Agents Involved • Hardware Triggering Element and Fault Code Combinations

• LCB 48 V Fuse / is blown

Resolution TBD

T066 - Drive Power Fuse (F1) Blown

Description The library detects that an F1 drive fuse located on a DSIB board has failed. Each module has a DSIB card to provide an electrical connection point for the drive sleds. Each DSIB has a replaceable fuse for the overall drive power bus. This protects the core library hardware components from some type of short or over current problem in one or more drives.

Detection Scenarios • Monitoring of voltage divider indicates partial or complete voltage drop (monitoring frequency?)

Root Causes • Board level hardware failures

• Permanent or temporary short circuit conditions in drives, drive sleds, docking connectors, etc.

Possible CRUs/FRUs • DSIB Fuse

• Hardware

• TBD

Resolution TBD

T067 - Display Assembly Hardware Failure

Description The library encounters an error which appears to be isolated to display assembly hardware. This includes the DIEB board.

Detection Scenarios • No i2C communication with board • No GPIO with board

• No CAN with board • DIEB fuse is blown

Root Causes • Board level hardware failures • Display not plugged in

• Cable failure or not plugged in

Scalar i500 Maintenance Guide

Maintenance Guide

Contents

1 About This Guide and Your Product

1

2 Troubleshooting the Scalar i500 Library

3

3 Adding, Removing, and Replacing

41

4 Common Service Procedures

81

5 Library Drawings

87

Tables

1 About This Guide and Your Product

2 Troubleshooting the Scalar i500 Library

3 Adding, Removing, and Replacing

4 Common Service Procedures

Figures

1 About This Guide and Your Product

2 Troubleshooting the Scalar i500 Library

3 Adding, Removing, and Replacing

4 Common Service Procedures

5 Library Drawings

About This Guide and Your Product

Product Safety Statements

Product Model Number

Explanation of Symbols and Notes

Note

Other Documents you Might Need

Getting More Information or Help

Note

Note

Troubleshooting the Scalar i500 Library

How the Library Reports Problems

Note

Working with

RAS Tickets

RAS Ticket

Error Codes

T002

T003

T004

T005

T006

T007

T008

T009

T010

Note

T011

T013

T017

T018

T019

T020

T021

T022

T023

T024

T025

T031

T032

T033

T034

T035

T036

T037

T038

T039

T040

T041

T045

T046

T047

T048

T049

T050

T051

T052