Adrian Lawrence wrote:
> Jens Pall writes:
> > Hi
> >
> > I've been trying to get my tape to work with my 2940UW controller, but
> > with no luck. The tape is a Seagate STT28000N-RF and is supposed to
> > work. The tape is detected at boot but when I try to use it (i.e. tar
> > cf /dev/st0 tape.test) the tape whirrs for a short while and the stops,
> > but with the activity light on. tar is also stuck and not even kill -9
> > can stop it. I've tried to fiddle around with the SCSISelect utility but
> > I haven't stumbled on a setting that works for me. The SCSI HOWTO says
> > that the BIOS on the controller has to be enabled for it to work but as
> > I only have the tape on the bus, it is disabled automatically (as far as
> > I have been able to find out, the BIOS is only used to boot from a disk
> > on the controller). Is it fundamentally necessary to have the BIOS
> > enabled to be able to use the tape or might it be that something else is
> > interfering? Is there a way to track this problem down? Perhaps using
> > gdb? As for now, I don't have a clue as to what might be happening.
> >
> > I'm pretty sure that there are no hardware conflicts in the system, and
> > /dev/st0 is a character device with major 9 and minor 0.
> >
> > My system is a slightly modified Debian 2.0, running kernel 2.2.5 with
> > the crypt extension.
> > The hardware I have is: Soundblaster AWE64, 3c509 ethernet, 3D Artist
> > and Voodo2.
>
> Have a look in /var/log/messages (or wherever you syslog messages go).
> Here is an extract on a box with a 2940 and a scsi drive:
>
> (scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 8/0
> (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
> (scsi0) Downloading sequencer code... 419 instructions downloaded
> scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
> kernel: <Adaptec AHA-294X Ultra SCSI host adapter>
> kernel: scsi : 1 host.
> kernel: Vendor: AIWA Model: TD-20001 Rev: 0159
> kernel: Type: Sequential-Access ANSI SCSI revision: 02
> kernel: Vendor: IBM Model: DDRS-34560W Rev: S97B
> kernel: Type: Direct-Access ANSI SCSI revision: 02
>
> Check also cat /proc/scsi/scsi.
>
> Since your drive is reacting to /dev/st0, it sounds as if these entries will
> be ok. What does mt status give? That might have to be
> mt -f /dev/st0 status .
> Check that you have at least mt-st v. 0.05b. The earlier
> version had a bug which stopped things working if the -f flag was used.
/var/log/syslog says:
May 14 20:05:27 phoenix kernel: st: bufsize 32768, wrt 30720, max buffers 4,
s/g segs 16.
May 14 20:05:27 phoenix kernel: Detected scsi tape st0 at scsi0, channel 0, id
4, lun 0
dmesg produces:
(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 10/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
<Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
Vendor: Seagate Model: STT8000N Rev: 3.22
Type: Sequential-Access ANSI SCSI revision: 02
(scsi0:0:4:0) Synchronous at 10.0 Mbyte/sec, offset 15.
cat /proc/scsi/scsi produces:
Attached devices:
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: Seagate Model: STT8000N Rev: 3.22
Type: Sequential-Access ANSI SCSI revision: 02
I would say that all this looks pretty promising. The hostadapter is detected
correctly and the tape is found.
mt --version produces:
GNU mt version 2.4.2
(is mt-st something else or is that a package you are referring to?)
With no tape in the drive, mt -f /dev/st0 status, produces:
mt: /dev/st0: No medium found
No lockup.
If I try, mt -f /dev/st0 status, with a tape in the drive, I get:
drive type = Generic SCSI-2 tape
drive status = 1157628416
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 512 bytes. Density code 0x45 (unknown).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
and mt locks up with status D (uninterruptible sleeping process if I recall
correctly)
Nothing but reboot kills this process.
The same thing happens to tar cf /dev/st0 file, that is, it gets the D status.
After this nothing relevant appears in the syslog.
One thing I noticed though was that after a reboot and I hadn't used the tape
at all the following appeared in the log:
May 14 06:42:42 phoenix syslogd 1.3-3#26: restart.
May 14 06:42:59 phoenix /USR/SBIN/CRON[464]: (mail) CMD (runq)
May 14 07:03:00 phoenix /USR/SBIN/CRON[468]: (mail) CMD (runq)
May 14 07:23:00 phoenix /USR/SBIN/CRON[472]: (mail) CMD (runq)
May 14 07:43:00 phoenix /USR/SBIN/CRON[476]: (mail) CMD (runq)
May 14 08:03:00 phoenix /USR/SBIN/CRON[480]: (mail) CMD (runq)
May 14 08:09:59 phoenix kernel: SCSI host 0 abort (pid 28) timed out -
resetting
May 14 08:09:59 phoenix kernel: SCSI bus is being reset for host 0 channel 0.
May 14 08:10:01 phoenix kernel: (scsi0:0:4:-1) Unexpected busfree, LASTPHASE =
0xa0, SEQADDR = 0x9e
May 14 08:23:00 phoenix /USR/SBIN/CRON[484]: (mail) CMD (runq)
(The runq messages appear because of a permission problem I haven't gotten
around to fix yet)
I don't remember if there was a tape in the drive.
I hope you or someone can see something out of all this.
Jens
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
