mjon
ADSM.ORG Member
Hi all,
I am in the process of replacing an STK9730 with an STKL40. probe-scsi-all showed the device and drives, and dmesg clearly shows the library available to solaris.
I'm following the steps in the administrators guide for "Configuring Device Drivers for Non-IBM Tape Drives and Libraries."
I edited /usr/kernel/drv/lb.conf, but didn't make any changes because the Target and LUN on the new library are the same. The new library is on a different PCI slot though.
At any rate, I ran /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb which says "Driver (lb) is already installed." The /dev/rmt/*lb corresponding to my library is not created though.
I went through this exact same thing 2 years ago when adding my L20, and as I recall, the solution was pretty simple. I can't remember what it was though. I have a feeling that whatever I'm doing wrong has to do with the TSM device driver for the library creating those links.
Any help would be much appreciated.
jon
I am in the process of replacing an STK9730 with an STKL40. probe-scsi-all showed the device and drives, and dmesg clearly shows the library available to solaris.
I'm following the steps in the administrators guide for "Configuring Device Drivers for Non-IBM Tape Drives and Libraries."
I edited /usr/kernel/drv/lb.conf, but didn't make any changes because the Target and LUN on the new library are the same. The new library is on a different PCI slot though.
At any rate, I ran /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb which says "Driver (lb) is already installed." The /dev/rmt/*lb corresponding to my library is not created though.
I went through this exact same thing 2 years ago when adding my L20, and as I recall, the solution was pretty simple. I can't remember what it was though. I have a feeling that whatever I'm doing wrong has to do with the TSM device driver for the library creating those links.
Any help would be much appreciated.
jon