[SOLVED] Powervault TL2000 tape library configuration

F

funnyance

New Member
Mar 9, 2024
6
1
3
Recently got a deal on a TL2000 Tape Library and i've run into an issue configuring it. Never had opportunity to play with any tape systems so that's adding possible user error to broken hardware and hardware comparability/support as cause.

Issue is i can't connect/add/find the changer to proxmox backup both web gui and proxmox-tape changer scan come up blank. Drive shows up just fine. Library web management interface shows everything ready, i can't find any errors for the library, drive or server. I've updated firmware to the latest for drive and library.

Next steps:
Upgrade from ancient IBM ServRaid 8k to supported Dell HBA (already ordered)
Utilize IBM Tape Diagnostics Tool (having hard time finding linux cli version, anyone have link?)
Upgrade from LTO-4 SAS drive to supported LTO-5/6 drive

Any suggestions?

Thanks
 
  • Like
Reactions: hunterkiller2011
I am in the exact same boat as you are. I got myself a TL3100 and proxmox sees the tape drive but not the library/changer even with the proxmox-tape changer scan. I currently have a SAS LTO6 drive connected through a Dell H200 updated to the latest firmware and I installed ITDT, so I am sorry to say that I am all those steps ahead of you and I am still having issues.

What is the output of these commands for you?
Code: 
lspci
lsscsi
ls -lR /dev/tape/*
 
Awesome, but also not Awesome....

Code: 
root@pbs:~# lspci
00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev b1)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev b1)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1c.1 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 (rev 09)
00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c2)
03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
04:00.0 RAID bus controller: Adaptec AAC-RAID (Rocket) (rev 02)
05:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c2)
06:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
10:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430]
10:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series]
1a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
1a:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
1b:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
1b:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
root@pbs:~# lsscsi
[2:0:0:0]    disk    ServeRA  boot             V1.0  /dev/sda
[2:1:0:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:1:1:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:1:2:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:1:3:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:1:4:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:1:5:0]    disk    IBM-ESXS ST3300555SS      BA33  -       
[2:3:0:0]    enclosu IBM-ESXS VSC7160          1.06  -       
[2:3:1:0]    tape    IBM      ULT3580-HH4      D8D5  /dev/st0
root@pbs:~# ls -laR /dev/tape
/dev/tape:
total 0
drwxr-xr-x  4 root root   80 Sep 20 03:15 .
drwxr-xr-x 20 root root 4600 Sep 20 03:15 ..
drwxr-xr-x  2 root root  160 Sep 20 03:15 by-id
drwxr-xr-x  2 root root   80 Sep 20 03:15 by-path

/dev/tape/by-id:
total 0
drwxr-xr-x 2 root root 160 Sep 20 03:15 .
drwxr-xr-x 4 root root  80 Sep 20 03:15 ..
lrwxrwxrwx 1 root root   9 Sep 20 03:15 scsi-10WT009547 -> ../../st0
lrwxrwxrwx 1 root root  10 Sep 20 03:15 scsi-10WT009547-nst -> ../../nst0
lrwxrwxrwx 1 root root   9 Sep 20 03:15 scsi-10WT009547-sg -> ../../sg8
lrwxrwxrwx 1 root root   9 Sep 20 03:15 scsi-35000e111601d6001 -> ../../st0
lrwxrwxrwx 1 root root  10 Sep 20 03:15 scsi-35000e111601d6001-nst -> ../../nst0
lrwxrwxrwx 1 root root   9 Sep 20 03:15 scsi-35000e111601d6001-sg -> ../../sg8

/dev/tape/by-path:
total 0
drwxr-xr-x 2 root root 80 Sep 20 03:15 .
drwxr-xr-x 4 root root 80 Sep 20 03:15 ..
lrwxrwxrwx 1 root root  9 Sep 20 03:15 pci-0000:04:00.0-scsi-0:3:1:0 -> ../../st0
lrwxrwxrwx 1 root root 10 Sep 20 03:15 pci-0000:04:00.0-scsi-0:3:1:0-nst -> ../../nst0
root@pbs:~#

Found a thread on SHT: https://forums.servethehome.com/ind...ell-tl4000-sas-tape-library-lto-drives.35557/ that gave me a few ideas, namely changing the drive slot, which didn't change anything.
 
Small update:

Pulled drive from sled to look for the DIP switches... none to be found.
poked mtx a bit, and then found loaderinfo which gave conflicting info if using /dev/sg8 or /dev/tape/by-id/scsi-10WT009547-sg

found errors in dmesg
Code: 
[    2.019552] aacraid 0000:04:00.0: 64 Bit DAC enabled
[    2.028833] scsi host2: ServeRAID
[    2.029201] scsi 2:0:0:0: Direct-Access     ServeRA  boot             V1.0 PQ: 0 ANSI: 2
[    2.040451] scsi 2:1:0:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.047597] scsi 2:1:1:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.054737] scsi 2:1:2:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.061880] scsi 2:1:3:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.069497] scsi 2:1:4:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.076618] scsi 2:1:5:0: Direct-Access     IBM-ESXS ST3300555SS      BA33 PQ: 0 ANSI: 5
[    2.090678] usb 2-6: new high-speed USB device number 2 using ehci-pci
[    2.133434] scsi 2:3:0:0: Enclosure         IBM-ESXS VSC7160          1.06 PQ: 0 ANSI: 3
[    2.253428] usb 2-6: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.26
[    2.253432] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.253434] usb 2-6: Product: USB2.0 Hub
[    2.253436] usb 2-6: Manufacturer: GenesysLogic
[    2.253856] hub 2-6:1.0: USB hub found
[    2.254170] hub 2-6:1.0: 4 ports detected
[    2.283936] scsi 2:3:1:0: Sequential-Access IBM      ULT3580-HH4      D8D5 PQ: 0 ANSI: 6
[    2.295104] scsi 2:3:1:0: Unexpected response from lun 1 while scanning, scan aborted
[    2.313202] sd 2:0:0:0: [sda] 1755316224 512-byte logical blocks: (899 GB/837 GiB)
[    2.313222] sd 2:0:0:0: [sda] Write Protect is off
[    2.313226] sd 2:0:0:0: [sda] Mode Sense: 12 00 10 08
[    2.313255] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA
[    2.313290] sd 2:0:0:0: Attached scsi generic sg0 type 0
[    2.313458] scsi 2:1:0:0: Attached scsi generic sg1 type 0
[    2.313612] scsi 2:1:1:0: Attached scsi generic sg2 type 0
[    2.313769] scsi 2:1:2:0: Attached scsi generic sg3 type 0
[    2.313924] scsi 2:1:3:0: Attached scsi generic sg4 type 0
[    2.314127] scsi 2:1:4:0: Attached scsi generic sg5 type 0
[    2.315113] scsi 2:1:5:0: Attached scsi generic sg6 type 0
[    2.315304] scsi 2:3:0:0: Attached scsi generic sg7 type 13
[    2.315474] scsi 2:3:1:0: Attached scsi generic sg8 type 1
[    2.357177]  sda: sda1 sda2 sda3
[    2.357448] sd 2:0:0:0: [sda] Attached SCSI removable disk
[    2.366655] st: Version 20160209, fixed bufsize 32768, s/g segs 256
[    2.369676] st 2:3:1:0: Attached scsi tape st0
[    2.369684] st 2:3:1:0: st0: try direct i/o: yes (alignment 4 B)
[    2.435013] bnx2 0000:03:00.0 eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X 64-bit 133MHz found at mem dc000000, IRQ 16, node addr 00:1a:64:07:9d:e0
[    2.435097] bnx2 0000:06:00.0: enabling device (0000 -> 0002)
[    2.495529] ses 2:3:0:0: Attached Enclosure device

i think the most useful information is actually:
Code: 
[    2.315304] scsi 2:3:0:0: Attached scsi generic sg7 type 13
[    2.315474] scsi 2:3:1:0: Attached scsi generic sg8 type 1

per: https://en.wikipedia.org/wiki/SCSI_Peripheral_Device_Type
Type 1 is a Sequential-access device (e.g., magnetic tape)
Type 13 is a Enclosure services device
But i have no type 8 Medium changer (e.g. jukeboxes)

I think i need to test different hardware configs.... no management card, no drive, power but no communications to library, both drive slots, reboot/power on order.

Perhaps i'll start with some IPA cleaning of contacts and a offering to Murphy and the electronics gods.
 
does it work when using 'mtx' ? e.g.`mtx -f <device> status` ?

what we noticed were that some raid controllers/hbas simply don't support passing through changer information, and changing to a proper hba fixed this (no guarantees in your case though)
 
Code: 
root@pbs:~# ls -laR /dev/tape/by-id/
/dev/tape/by-id/:
total 0
drwxr-xr-x 2 root root 160 Mar 11 06:17 .
drwxr-xr-x 4 root root  80 Mar 11 06:17 ..
lrwxrwxrwx 1 root root   9 Mar 11 06:17 scsi-10WT009547 -> ../../st0
lrwxrwxrwx 1 root root  10 Mar 11 06:17 scsi-10WT009547-nst -> ../../nst0
lrwxrwxrwx 1 root root   9 Mar 11 06:17 scsi-10WT009547-sg -> ../../sg8
lrwxrwxrwx 1 root root   9 Mar 11 06:17 scsi-35000e111601d6001 -> ../../st0
lrwxrwxrwx 1 root root  10 Mar 11 06:17 scsi-35000e111601d6001-nst -> ../../nst0
lrwxrwxrwx 1 root root   9 Mar 11 06:17 scsi-35000e111601d6001-sg -> ../../sg8
root@pbs:~# mtx -f /dev/st0 status
cannot open SCSI device '/dev/st0' - No medium found
root@pbs:~# mtx -f /dev/nst0 status
cannot open SCSI device '/dev/nst0' - No medium found
root@pbs:~# mtx -f /dev/sg8 status
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 20
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: Field in Error = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=yes
mtx: Request Sense: SKSV=yes
mtx: Request Sense: Field Pointer = 00 00
READ ELEMENT STATUS Command Failed
root@pbs:~#

Command took couple minutes on st0 and nst0 devices, but fast response on sg8.

Once i saw the scsi dmesg entries, the SAS controller compatibility was my prime suspect, and reading a couple posts has only re-enforced that. Unfortunately it seems support for non disk features not only uncommon in use, but also in documentation of support.

As for testing, all i got was the should have been expected error messages, no power and no communication states. Although the unexpected response in dmesg only showed up if the tape library was powered on before the server.

I'm not 100% sure Dell H200 i ordered is on the supported list, but I've seen a few posts stating it works. If it does work not sure what that means for hunterkiller2011 setup.

So for now i'm waiting on snail mail.
 
TLDR: Who knew RTFM was so important...

Good News! I spent quite a bit messing with my library this weekend and it suddenly started registering for me in PBS. Spent the last day trying to figure out exactly what I changed to make it appear. I have a TS3100 and idk how similar the TL2000 is, but check if the library mode is set to sequential or random.

I looked up a manual for both our systems and discovered("Choosing general library settings") that changing the setting to random "allows the server's (host's) application software to select any data cartridge in any order"

I have attached some screenshots for what to potentially expect to see:

1710206534720.png

1710206437188.png
 
dcsapak said:
does it work when using 'mtx' ? e.g.`mtx -f <device> status` ?

what we noticed were that some raid controllers/hbas simply don't support passing through changer information, and changing to a proper hba fixed this (no guarantees in your case though)
Click to expand...
For my case, I had to do an extensive amount of research to determine if my H200 could handle multiple LUNs, even going as far as attempting to determine if I needed a different type of firmware(IT mode or HBA mode), update the firmware, and determine if Debian natively supported multiple LUNs. I never got a firm answer from any manuals, only that I stumbled upon other threads where the H200 was being used by others for tape drives and libraries. This ruled out my specific HBA and I was back to square one. Thank fully, you did already say that you had purchased a Dell HBA so even if you're current HBA doesn't support multiple LUNs your new one should(depending on what you got).
 
YEY! So the Dell H200 SAS card fixed everything right up. That lack of a firm clear answer was aggravating, but guess it is unusual hardware without support contract.

That's a very interesting catch on the random/sequential configuration, I think i would have expected errors during operation, not invisible hardware.

As far as i can tell the difference between Dell and IBM tape libraries is limited to swapping logos on firmware and the case.

Thanks for help!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back