MSL6000 - ioscan shows state unclaimed and type unknown

[Tariq Hasan_1]

ioscan doesn't show the library as claimed:

unknown -1 0/8/0/0.1.3.255.0.0.0 UNCLAIMED UNKNOWN HP MSL6000 Series

whereas there are 2 drives on the same path that are showing as claimed, as below:

tape 0 0/8/0/0.1.3.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/0m /dev/rmt/0mn /dev/rmt/c12t0d1BEST /dev/rmt/c12t0d1BESTn
/dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c12t0d1BESTb /dev/rmt/c12t0d1BESTnb
tape 1 0/8/0/0.1.3.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/1m /dev/rmt/1mn /dev/rmt/c12t0d2BEST /dev/rmt/c12t0d2BESTn
/dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c12t0d2BESTb /dev/rmt/c12t0d2BESTnb

How is this possible? I am trying to run a backup to ultrium in one of the 2 drives, and attempting to mt -t /dev/rmt/0m (or 1m) fails.

Thanks

Tariq

[Luk Vandenbussche]

Hi,

Have you added the driver schgr to your kernel.
This is the driver for the robot arm

[Don Mallory]

Agreed, looks like your schgr driver is missing.

Devices I show on an ioscan -f:

fc 1 0/10/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
fcp 2 0/10/0/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 8 0/10/0/0.1.0.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 9 0/10/0/0.1.0.255.0.0 tgt CLAIMED DEVICE
autoch 3 0/10/0/0.1.0.255.0.0.0 schgr CLAIMED DEVICE HP MSL6000 Series
tape 12 0/10/0/0.1.0.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
tape 13 0/10/0/0.1.0.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 2-SCSI
ctl 71 0/10/0/0.1.0.255.0.0.3 sctl CLAIMED DEVICE HP NS E1200-160

ext_bus 47 0/10/0/0.1.15.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 28 0/10/0/0.1.15.255.0.0 tgt CLAIMED DEVICE
tape 14 0/10/0/0.1.15.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI
tape 15 0/10/0/0.1.15.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
ctl 83 0/10/0/0.1.15.255.0.0.2 sctl CLAIMED DEVICE HP NS E1200-160

Just another item of note though, HP has a recommendation of 2 drives per SCSI-Fiber bridge (NS1200), however it's actually a requirement. You cannot run 4 drives due to the throughput volume that can peak on 4 drives.

What happens is, when you have all 4 drives going all out, the NSR1200 crashes. You can't even telnet to it. All the drives hand and you're stuck. The only thing that gets you out is a reboot of the node and the jukebox.

I also needed a firmware update. (5.6.69 is the current one I'm running.)