mounting scsi tape drive
Kenneth D. Merry
ken at kdm.org
Mon Apr 5 14:19:15 PDT 2004
On Mon, Apr 05, 2004 at 16:03:54 -0500, junk wrote:
> On Mon, 2004-04-05 at 15:57, Kenneth D. Merry wrote:
> > On Mon, Apr 05, 2004 at 15:53:48 -0500, junk wrote:
> > > I am having a problem mounting a scsi tape drive.
> > > The kernel sees it , but it wont mount.
> > >
> > > >From dmesg:
> > >
> > > sa0 at ahc0 bus 0 target 5 lun 0
> > > sa0: <CONNER CTT8000-S 1.17> Removable Sequential Access SCSI-2 device
> > > sa0: 5.000MB/s transfers (5.000MHz, offset 15)
> > >
> > > When i try to mount it:
> > >
> > > [root at cpr]/dev(184): mount /dev/sa0 /mnt/tape/
> > > mount: /dev/sa0: Block device required
> > >
> > > even tried:
> > > [root at cpr]/dev(185): mount /dev/nsa0 /mnt/tape/
> > > mount: /dev/nsa0: Block device required
> >
> > You can't mount a tape drive like that. mount only works for disk devices
> > with filesystems.
> >
> > > [root at cpr]/dev(186): mt rewind
> > > mt: /dev/nsa0: Invalid argument
> >
> > Do you have a tape in the drive? What happens when you type 'mt status'?
> >
> > Try this:
> >
> > camcontrol tur sa0 -v
> >
> > Ken
> Yes, I have a tape in it.
>
> [root at cpr]/etc(195): mt status
> mt: /dev/nsa0: Invalid argument
You might be getting something in the dmesg when you type mt status.
> [root at cpr]/etc(196): camcontrol tur sa0 -v
> Unit is not ready
> (pass2:ahc0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (pass2:ahc0:0:5:0): ILLEGAL REQUEST asc:80,81
> (pass2:ahc0:0:5:0): Vendor Specific ASC
[ reply moved to the bottom, please don't top post ]
That's a vendor-specific ASC/ASCQ. There's something wrong with the tape
or drive, but there's not much we can tell from that response.
I'd see if you can find a SCSI manual or interface spec for the drive.
That might help you figure out what's wrong. Or, look to see if there are
any error LEDs on the drive, and then try to decode the meaning from the
manual.
It's kinda weird to return illegal request for a test unit ready, but then
again I'm not really sure what's wrong with the drive.
Ken
--
Kenneth Merry
ken at kdm.org
More information about the freebsd-scsi
mailing list