Selecting a Diagnostic or Maintenance Function
The Ultrium 2 Tape Drive can run diagnostics, test write and read functions, test a suspect tape cartridge, update its own firmware, and perform other diagnostic and maintenance functions. The drive must be in maintenance mode to perform these functions. To place the drive in maintenance mode and select a diagnostic or maintenance function, see Table 9.
Attention: Maintenance functions cannot be performed concurrently with read or write operations. While in maintenance mode, the tape drive does not accept SCSI or Fibre Channel commands from the server. The tape drive does accept LDI or
Table 9. Diagnostic and maintenance functions
Function Code 1 - Run SCSI or Fibre Channel Tape Drive Diagnostics
Causes the tape drive to run self tests.
Attention: Insert only a scratch data cartridge for this test. Data on the cartridge will be overwritten.
1.Make sure that no cartridge is in the drive.
2.Within a
3.Press the unload button once per 1.5 seconds until 1 appears in the
4.To select the function, press and hold the unload button for 3 seconds. After you select the function, 1 flashes, the drive runs diagnostics for approximately 90 seconds, then C flashes. When C flashes, the drive is waiting for a cartridge.
5.Within 60 seconds, insert a scratch data cartridge (or the tape drive exits maintenance mode). After you insert the cartridge, 1 flashes:
v If the diagnostic completes successfully, it begins again and runs for a maximum of 10 times. Each loop takes approximately 20 minutes to run. After the tenth loop, the diagnostic stops and automatically exits maintenance mode. To halt the diagnostic, press the unload button within the first 20 minutes of the test (or the diagnostic will run another 20 minutes). The drive acknowledges the request by slowing the length of time that the currently displayed character flashes on the
vIf the diagnostics fail, the status light flashes amber and an error code displays. The tape drive unloads the tape cartridge and exits maintenance mode. To resolve the error, locate the code in Table 15 on page 67.