IBM LTO6 Tape Drive
 
IBM LTO4 Tape Drive
 
Sun StorageTek SL3000 Modular Library System
 
IBM LTO3 Tape Drive
 
IBM LTO5 Tape Drive
 
Sun StorageTek SL8500 Modular Library System
 
IBM LTO7 Tape Drive
 

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

In this Document

Symptoms

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Detailed Oracle Product Information is Included

Applies to:

Symptoms

SL3000/SL8500 - Unexpected Unload Occurring during load on IBM LTO Tape Drives.

Cause

While loading an IBM LTO tape drive if the drive is doing a locate or position on tape then the library would fail the load and issue an unload to the drive.

We have seen this on IBM LTO4 and IBM LTO7 on the SL3000 and on IBM LTO4 and IBM LTO5 drives in the SL8500 but it could occur on other generations of IBM LTO drives in both the SL3000 and SL8500 libraries.

We have seen this issue on SL3000 codes 4.30, 4.31, and 4.32.

We have seen this issue on SL8500 code 8.35.

The library trace in the drive dump will show the unexpected unload command come from the library and with TTI debug tracing turned on for a drive the HBT log_trace, log_trace.0, etc file will show the unexpected unload being sent from the library in the library logs.

Here are examples of the issue in the HBT trace logs:

You will see the LoadDrive command from the library to the drive: 

2016-06-20T09:48:13.004306, tti-dbg-08, IBMPackets: LoadDrive

...and then a short time later you will see the RewindDrive command being sent from the library to the drive: 

2016-06-20T09:48:21.826726, tti-dbg-08, IBMPackets: RewindDrive

Note: You will not see any entries in the HBT log_error or log_warning logs for this issue.

You can also verify this was the issue by looking at the ACSLS command history or a monitor trace from the library as it will not show the rewind/unload command coming from the host or ACSLS.

Solution

Library engineering has provided fixes for this issue in both the SL3000 code 4.40 and the SL8500 code 8.36.

This solution has no attachment