Troubleshooting; Finding Event Information; Identifying A Failed Component; Running Library Tests - Dell EMC ML3 User Manual

Troubleshooting

Attention: This library is designed to operate when installed in a rack with the rack rail kit or on a
tabletop. Operating the library without installing it correctly in the rails might cause errors. Placing any
weight on top of the library might also cause errors. Expanded library configurations on tabletops are not
supported.

Finding event information

You can find event information by viewing log files from the Library > Events screen or downloading
support tickets from the Drives > Actions > Export Drive Logs screen.
See "Locating Management functions" on page 63.

Identifying a failed component

1. Management GUI: Activate the UID LEDs from the Library > Actions > Turn Identifier Light On or
Off screen. This action illuminates the blue LED on the front and rear of the Base Module to identify
the library that contains the failed module or component.
2. Identify the module within the library that contains the failed component.
a. In the upper left of the Home screen, locate the module that indicates an error.
b. Click or tap the module for information on the failed component.

Running library tests

The library provides tests to verify library operations.
v On the Management GUI, go to Library > Actions > Tests and choose the library test that you want to
run.
– Library Verify
– Demo Mode
– Drive Test
– Slot to Slot Exerciser
v On the Operator Panel, go to Maintenance > Library Tests to run tests from the Operator Panel.
– Demo Mode
– Drive Diagnostics

Troubleshooting Guide

Refer to this table of symptoms or errors that might occur with the tape library and the installed tape
drives. The table provides actions to correct the problems. See www.Dell.com/support.
Table 34. Resolving errors
Problem
Event code/Attention information on Management GUI or Library
Event code that is shown on
Event Ticket on the
Management GUI. See "Finding
event information."
Solution
v Look up the error code. See Event Codes.
v Try to resolve the failure.
v If necessary, power cycle the library.
73