LTO Tape Drive
 
Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek T10000 Tape Drive
 

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

In this Document

Symptoms

Changes

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for service personnel

Applies to:

Symptoms

SL3000 newly added drives not showing partition or HLI/SCSI address

Problem description:

Added a new drive bay and 6 x drives to a SL3000, running 4.31 code.

Note: This occurs with 4.40 also. (26-Oct, 2016)

4 of the drives that went into the existing drive bay array(number 2) are all green in SLC and have been assigned a HLI/SCSI address after a 2nd reboot / power cycle of the library as per previous installs of drives into this library.

2 of the drives in the new drive bay array(number 3) show all green in SLC also but these drives do not have a partition or HLI/SCSI address assigned to them (Partition=Unassigned, HLI/SCSI addr=Not Applicable).

Previously when this has occurred a reboot of the library resolved the issue but not in this case. CLI command: ’config check’ / ’reboot’ has been issued with no change either. Drives have been swapped between drive bays in inside the array 3 and between array 2 and 3. No drive in bottom drive array(3) receives an address.

All cabling from the bay back to the motherboard has been checked and re-seated.

Changes

Actions take to try to solve the issue without success:

- Swapped TTI cables at the PUM end, from connectors J224 and J225. The issue moved to drive bay array number 2. So this ruled out this being a drive bay/cable issue in drive bay array 3.

- This lead to a conclusion that the issue would be the PUM. However PUM replacement didn't solve the issue.
- Next the HBT was replaced, and again no positive affect to the problem.
- Downgraded the library firmware to 4.00. No help.
- Upgraded the code back to 4.31. No help.

Cause

Log snapshot analyze:

This shows the new drives are not in the partition configuration file. This is the reason they are not getting the HLI/SCSI address assigned to them.

Why aren’t the new drives in the partition configuration file?

Speculation: Library code was changed regarding the partitioning section of the code with 4.3x code due introducing the media validation feature. Media validation(if used) will enable partitioning in the background, and create a separate partition for the validation drives. This causes the drives to be listed differently in the partition configuration file than we normally see with non-partitioned libraries.

Here is a sample how the file looks with this problematic customer(see the attachment)

Note that the drives are listed individually rather than grouped to entries, where we list a range of rows or columns in one entry. See a sample from the CAP how we should expect the drives to be added typically. So this is a way to identify we have the file in a mode, where media validation is used.

Solution

To get past this problem, follow the instructions in the attached document: Just reset defaults via cell activation menu!  No reboot is needed at the end.  See the exact steps in the attached document!

Note: 17-Nov, 2015

With SLC 6.25 "reset default button" not found.
Upgraded to version SLC 6.51 it works fine.

Note: 18-Mar, 2016

Replaced two existing faulty drives T10000A - partition=0, HLI/SCSI addr=Not Applicable - occurred after upgrade to 4.31; fixed with the same steps, so it could happen to newly replaced drive too.

This solution has no attachment