StoreEver Tape Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

MSL6000 - Drive issues

Colin Mackay
Frequent Advisor

MSL6000 - Drive issues

Greetings,

I have been put in charge of our backups and have recently added two Ultrium tape drives to our MSL6000, for a total of four.

The issue I am having is when I load HP L&TT and view the devices. It lists three drives under the MSL6000 and the third is listed under Drives.

Now, it seems to work (when I can get DP 5.5 to behave)... Is there any idea's out there as to why?

The SCSI connections are according to page 170 from this document:

http://h200001.www2.hp.com/bc/docs/support/SupportManual/c00296712/c00296712.pdf

Thanks.
18 REPLIES
Marino Meloni_1
Honored Contributor

Re: MSL6000 - Drive issues

be sure to use last LTT version,

try to disable and enable the drives form the Operator Control panel in the library

marino
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

The drives work, and yes I can enable and disable them from the front panel.

I raelly don't know if this problem is actually causing any real issues... But shouldn't the tape show up under the Library?
Marino Meloni_1
Honored Contributor

Re: MSL6000 - Drive issues

Yes it should,
I had myself this problem after changing the library configuration, I perfomed several actions, but not sure which has fixed.
I upgraded LTT, I played a bit in the OCP, and resetted some parameter from the web interface of the library, and then sudenly after a reboot the drives where all under the robotic controller in LTT.
Anyway there where no problems with my backup software.

marino
David Ruska
Honored Contributor

Re: MSL6000 - Drive issues


> The issue I am having is when I load HP L&TT and view the devices. It lists three drives under the MSL6000 and the third is listed under Drives.

I think you meant to say the 4th is listed under drives.

LTT attempts to find all the drives reported by the library (via read element status) and associate them to the library (listed indented under the library in the "by product" tab).

It typically finds the drives by looking for them on the system by serial number.

If the library reported 4 drives, but LTT could only match 3 of them, it will give a warning that it was unable to find all the drives. If the library only reported 3 drives (and it found 3), then LTT will not complain at all.

Can you clarify if LTT thinks the library was looking for 3 or 4 drives? You may have to look at "details" under the scan tab.
The journey IS the reward.
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

We have 4 drives...

Sorry, it's seeing drive 1, 2 and 4 but drive 3 is sitting outside the tape library according to L&TT.

I have downloaded a new version of L&TT and placed the MSL and the Cell manager onto their own Zone on the SAN. Still no change.
Scott McIntosh_2
Honored Contributor

Re: MSL6000 - Drive issues

If Data Protector is your backup product, then let's see what devbra -dev reports. It'll list the serial numbers the library reports as well as the serial numbers of the drives, so maybe that'll give a view of something being off.

devbra -dev

either in /opt/omni/lbin or OmniBack\bin, depending on the OS of the system which can see the robotics and all drives.

Thanks,
Scott
HP Support
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

The output was:

Tape HP:Ultrium 2-SCSI Path: "Tape3:1:1:1C" SN: "HUL5D10742"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape2:1:1:0" SN: "N/A"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape1:1:0:2C" SN: "HUL4E06624"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape0:1:0:1C" SN: "HUL4A01647"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Exch HP:MSL6000 Series Path: "Changer0:1:0:0" SN: "3G41LRT5TDAX"
Description: CLAIMED:HP StorageWorks MSL 6000 Series
Revision: 0507 Flags: 0x0016 Slots: 58 Drives: 4
Drive(s) SN:
"HUL4A01647"
"HUL4E06624"
"HUL5E01877"
"HUL5D10742"

So as you can see, the second tape drive in this list has no S/N, yet there is a serial number listed under the Changer...

I also noticed that the Reload button in DP for the Tape Drive serial number is greyed out.
David Ruska
Honored Contributor

Re: MSL6000 - Drive issues

If the serial number is not being reported back, that explains why LTT would not associate it with the library.

The serial numbers reported by the library are obtained from the drive by a separate (serial) interface port.

In LTT, can you pull a support ticket for the drive? It should contain the SN the drive is reporting across SCSI.

I wonder if you have an intermittent SCSI connection to that drive.
The journey IS the reward.
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

I don't think so, while we've had some issues with backups, they've been mostly attributed to our SAN switch. We had no zones configured and other devices were sending SCSI reset commands during restores and backups...

I just went over all the connections, but I've tried doing some backups on these drives and they all succeeded.

David Ruska
Honored Contributor

Re: MSL6000 - Drive issues

Colin,

If you're fairly confident the drive is behaving properly from an backup perspective, then the issue appears limited to detection/reporting of the serial number by LTT and devbra.

Can you collect an LTT support ticket for the drive in question (to see if the SN is reported correctly there)?
The journey IS the reward.
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

Well, I know it backs up. I performed a number of them with that drive...

All the Serial Numbers show up in L&TT correctly, all the firmware is the most recent and backups work...
David Ruska
Honored Contributor

Re: MSL6000 - Drive issues

Just for clarification, is devbra still reporting this for the drive in question:

Tape HP:Ultrium 2-SCSI Path: "Tape2:1:1:0" SN: "N/A"
Description: CLAIMED:HP LTO drive

With no serial number?
The journey IS the reward.
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

Oddly, no:

Tape HP:Ultrium 2-SCSI Path: "Tape3:1:1:1C" SN: "HUL5D10742"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape2:1:1:0C" SN: "HUL5E01877"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape1:1:0:2C" SN: "HUL4E06624"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Tape HP:Ultrium 2-SCSI Path: "Tape0:1:0:1C" SN: "HUL4A01647"
Description: CLAIMED:HP LTO drive
Revision: F59W Device type: lto [13] Flags: 0x0011

Exch HP:MSL6000 Series Path: "Changer0:1:0:0" SN: "3G41LRT5TDAX"
Description: CLAIMED:HP StorageWorks MSL 6000 Series
Revision: 0507 Flags: 0x0016 Slots: 58 Drives: 4
Drive(s) SN:
"HUL4A01647"
"HUL4E06624"
"HUL5E01877"
"HUL5D10742"

But L&TT still shows the drive with S/N: HUL4A01647 as not under the MSL6000

David Ruska
Honored Contributor

Re: MSL6000 - Drive issues

Thanks, sounds like it is only an LTT problem at the moment.

You're not using the "saved" scan feature in LTT are you? Make sure you do an actual hardware scan.

If the issue persists, can you collect the "eventlog.ltt" file from the logs folder after doing the LTT scan and exiting? You can mail it to ltt_team@hp.com, and reference this post?

They can see if there's any indication of why the drive is not getting associated. It would be good to also include the library support ticket and the separate drive support ticket (you can zip them to make them much smaller).
The journey IS the reward.
Scott McIntosh_2
Honored Contributor

Re: MSL6000 - Drive issues

Unrelated, but you have the Windows driver enabled for the medium changer device. Not supported.

Thanks,
Scott
HP Support
Colin Mackay
Frequent Advisor

Re: MSL6000 - Drive issues

The Windows driver is not supported by L&TT?
David Ruska
Honored Contributor

Re: MSL6000 - Drive issues

LTT doesn't use the windows driver, but shouldn't fail because it's there. LTT goes directly through the "NT miniport" (or aspi if configured) driver to talk to the device.

You just need to make sure any services that might be accessing the device through that driver are disabled (such as Windows Removable Storage).

I think Scott means that DP does not want a windows driver installed (and I suspect goes directly throuth NT miniport).
The journey IS the reward.
Scott McIntosh_2
Honored Contributor

Re: MSL6000 - Drive issues

Well, not sure what miniport, starport, all that stuff means. Never been able to figure out that Windows stuff.

But yes, talking about Data Protector. While we prefer the driver for the tape drives not loaded, we require the driver for the robotics not loaded. Then again, if this system isn't the one controlling the robotics for DP operations, then it shouldn't matter I guess. Still, the less hands in the pot, the better.

We create the CDBs ourselves and send them to the HBA to be forwarded to the robotics.

Thanks,
Scott
HP Support