MSL6000 - Drive issues

[David Ruska]

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)?

[Colin Mackay]

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]

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?

[Colin Mackay]

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]

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).

[Scott McIntosh_2]

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

Thanks,
Scott
HP Support

[Colin Mackay]

The Windows driver is not supported by L&TT?

[David Ruska]

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).

[Scott McIntosh_2]

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