On Fri, 27 Apr 2001, Juergen Knott wrote:
> But the /dev/nst0 device don't work, and i don't know why.
> I can put in a tape from hand in the tapedrive and can start ./amcheck Daily,
> and it's all ok.
> The second start of ./amcheck Daily is running....and running...and running.
> No messages on the screen, sot hat i send a break after 10 minutes with
> CTRL-C to the System and look into the *debug files from amanda and the
> chg-scsi script can't read from de/nst0 btw. /dev/nst0 have a io-error and
> can't be open.
>
I'm not sure where the problem is, so I suggest a few steps to find what's
working and what's not.
First see if the Tapedrive is found at all. Cat /proc/scsi/scsi and see if
you find a device of type Sequential-Access like this:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: HP Model: C1533A Rev: 9503
Type: Sequential-Access ANSI SCSI revision: 02
Then check if the st driver is loaded and has found the tapedrive. Make
sure that the module is loaded (if st is a module, do a 'modprobe st') and
check the kernel logs for something like:
Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0
st: bufsize 32768, wrt 30720, max init. buffers 4, s/g segs 16.
Check if /dev/st0 and /dev/nst0 are correct:
crw-rw---- 1 root tape 9, 128 Jul 21 1998 /dev/nst0
crw-rw---- 1 root tape 9, 0 Jul 21 1998 /dev/st0
Run 'mt -f /dev/st0 status'. If this works all right (i.e. you don't get
error messages like mt: /dev/st0: No such file or directory or
/dev/st0: No such device or address) then the OS and the tapedrive are
working fine and your problem is an Amanda problem :)
PS. The st SCSI module does not depend on the sg SCSI module, so the st
driver does not talk to the sg module or is a layer above sg. St is
strickly for tapedrives, sg is for everything except disks, cdroms and
tapes (so you also need sg for a scanner).
--
Tot ziens,
Bart-Jan
