I tried over the weekend to add four new IBM LTO5 drives (SAS) to a working NEO 8000e jukebox equipped with four HP LTO5 (SAS) drives. The operating system and jukebox can see and work with the drives, but not TSM. TSM just doesn't see them.
TSM Extended Edition 6.3.3.0 running on RHEL 6.3 with kernel 2.6.32-358.11.1.el6.x86_64
The drives were sold to us by the same Overland reseller who sold us the NEO 8000e equipped with the four original HP drives. The drive firmware version is D2A0. That is the second-most-recent version available when I check the Overland support web site. Because the OS can work with the drives, I think this is a very TSM-specific issue. The NEO 8000e is running the lastest firmware.
My dsmserv startup script uses /opt/tivoli/tsm/devices/bin/autoconf -a to populate /dev/tsmscsi. Only the four HP drives are identified and provisioned (meaning included in the /dev/tsmsci/mtinfo file and symbolic links made from /dev/tsmscsi/mt0 to /dev/sg5 etc).
I have tried all of the workarounds I could think of, including making links by hand for the new drives in /dev/tsmscsi (and modifying mtinfo and making the /dev/sg* files for the new drives world readable and writable like autoconf did for the HP drives). But when I got to define a drive and a path in dsmadmc I get an I/O error when TSM tries to contact the drive to determine it's capabilities and serial number (ANR8420E DEFINE PATH: An I/O error occurred while accessing drive DRIVE5.)
I tried using the /opt/tivoli/tsm/devices/bin/tsmscsi program instead of autoconf (first creating /opt/tivoli/tsm/devices/bin/{mt,lb,op}.conf files with the right info from /proc/scsi/scsi). That didn't recognize ANY drives.
If I /usr/bin/strings the autoconf binary, I see the same device model names as are printed during boot
(see dmesg output below) for the HP drives listed but NOT that of the IBM drives. But googling for "tsm ULTRIUM-TD5" yielded only hits that looked like TSM supported the IBM drives. I even downloaded the rpm containing the latest autoconf (6.3.4.000-TIV-TSMALL-Linuxx86_64.bin) and extracted its autoconf, hoping that it would behave differently. Nope. Looks identical to the 6.3.3 autoconf. (The (only) copyright date printed is 2009, which seems hard to believe.) Oh, and autoconf contains "Ultrium 6-SCSI" so it's LTO-6 ready...
string for HP: Ultrium 5-SCSI
string for IBM: ULTRIUM-TD5
scsi 0:0:0:0: Sequential-Access HP Ultrium 5-SCSI X51H PQ: 0 ANSI: 6
scsi 0:0:4:0: Sequential-Access IBM ULTRIUM-TD5 D2A0 PQ: 0 ANSI: 6
Thanks!
Jeffrey
TSM Extended Edition 6.3.3.0 running on RHEL 6.3 with kernel 2.6.32-358.11.1.el6.x86_64
The drives were sold to us by the same Overland reseller who sold us the NEO 8000e equipped with the four original HP drives. The drive firmware version is D2A0. That is the second-most-recent version available when I check the Overland support web site. Because the OS can work with the drives, I think this is a very TSM-specific issue. The NEO 8000e is running the lastest firmware.
My dsmserv startup script uses /opt/tivoli/tsm/devices/bin/autoconf -a to populate /dev/tsmscsi. Only the four HP drives are identified and provisioned (meaning included in the /dev/tsmsci/mtinfo file and symbolic links made from /dev/tsmscsi/mt0 to /dev/sg5 etc).
I have tried all of the workarounds I could think of, including making links by hand for the new drives in /dev/tsmscsi (and modifying mtinfo and making the /dev/sg* files for the new drives world readable and writable like autoconf did for the HP drives). But when I got to define a drive and a path in dsmadmc I get an I/O error when TSM tries to contact the drive to determine it's capabilities and serial number (ANR8420E DEFINE PATH: An I/O error occurred while accessing drive DRIVE5.)
I tried using the /opt/tivoli/tsm/devices/bin/tsmscsi program instead of autoconf (first creating /opt/tivoli/tsm/devices/bin/{mt,lb,op}.conf files with the right info from /proc/scsi/scsi). That didn't recognize ANY drives.
If I /usr/bin/strings the autoconf binary, I see the same device model names as are printed during boot
(see dmesg output below) for the HP drives listed but NOT that of the IBM drives. But googling for "tsm ULTRIUM-TD5" yielded only hits that looked like TSM supported the IBM drives. I even downloaded the rpm containing the latest autoconf (6.3.4.000-TIV-TSMALL-Linuxx86_64.bin) and extracted its autoconf, hoping that it would behave differently. Nope. Looks identical to the 6.3.3 autoconf. (The (only) copyright date printed is 2009, which seems hard to believe.) Oh, and autoconf contains "Ultrium 6-SCSI" so it's LTO-6 ready...
string for HP: Ultrium 5-SCSI
string for IBM: ULTRIUM-TD5
scsi 0:0:0:0: Sequential-Access HP Ultrium 5-SCSI X51H PQ: 0 ANSI: 6
scsi 0:0:4:0: Sequential-Access IBM ULTRIUM-TD5 D2A0 PQ: 0 ANSI: 6
Thanks!
Jeffrey