On Mon, 21 Mar 2005 at 10:38am, Brian Cuttler wrote

> The system we have attached it to is running kernel 2.4.20-24 on
> Red Hat Linux release 9 (Shrike).

As an aside, I highly recommend CentOS as an option for RH shops moving 
forward.  RH9 is far from supported, while CentOS (being an RHEL rebuild) 
will be supported for years.

> And the attempts to access the device via mt fail:
> # mt -f /dev/st0 status
> /dev/st0: No such device or address

What does /sbin/lsmod say at this point?  Based on what's below, it 
should be working...

> Do we need to update a driver, run a config command or are we just
> using the wrong name for the tape device ?
> 
> Off hand, how do I find the name for the robot ?

Everything is below:

> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
>         <Adaptec 29160 Ultra160 SCSI adapter>
>         aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> 
> blk: queue db93ae14, I/O limit 4095Mb (mask 0xffffffff)
>   Vendor: M4 DATA   Model: MagFile           Rev: 6.0 
>   Type:   Medium Changer                     ANSI SCSI revision: 02
> blk: queue db93aa14, I/O limit 4095Mb (mask 0xffffffff)
>   Vendor: HP        Model: Ultrium 2-SCSI    Rev: F45Z
>   Type:   Sequential-Access                  ANSI SCSI revision: 03
> blk: queue d4fa7014, I/O limit 4095Mb (mask 0xffffffff)
> st: Version 20030406, bufsize 32768, max init. bufs 4, s/g segs 16
> Attached scsi generic sg1 at scsi1, channel 0, id 0, lun 0,  type 8
> Attached scsi tape st0 at scsi1, channel 0, id 1, lun 0
> scsi : 2 hosts left.

So, your changer is /dev/sg1 and your tape drive should be /dev/{n}st0.  
Make sure -- what's the output of 'cat /proc/scsi/scsi'?  What does
'mtx -f /dev/sg1 status' say?

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University