Date: Thu, 23 Jul 1998 18:42:33 -0400 From: Nathan Dorfman <nathan@fcc.net> To: freebsd-questions@FreeBSD.ORG Subject: Problems with st0 Message-ID: <19980723184233.A12037@fcc.net>
next in thread | raw e-mail | index | archive | help
I'm running 2.2.7-STABLE. On a SCSI DAT drive, and using the 2940UW
host adapter, I reliably get this problem when trying to dump:
1) Dump will get to pass III and start writing to tape for
a few minutes. The light comes on and I can hear the drive
doing something.
2) After a while, this goes to the console:
st0(ahc0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0
SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa
st0(ahc0:2:0): Queueing an Abort SCB
st0(ahc0:2:0): Abort Message Sent
st0(ahc0:2:0): SCB 0 - Abort Completed.
st0(ahc0:2:0): no longer in timeout
DUMP: write error 6620 blocks into volume 1
DUMP: Do you want to restart?: ("yes" or "no") ahc0:A:2: no active SCB for rec
onnecting target - issuing BUS DEVICE RESET
SAVED_TCL == 0x20 ARG_1 == 0xff SEQADDR == 0x111
ahc0: Bus Device Reset delivered. 0 SCBs aborted
ahc0: Bus Device Reset delivered. 0 SCBs aborted
3) Pressing no here results in the following messages. At
this point the tape light on the DAT drive begins to blink
rapidly and the in-use light comes on. A few minutes later
the tape light returns to the normal "on" status and the
in-use light dies. Only then can I eject the tape.
DUMP: The ENTIRE dump is aborted.
ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers
st0(ahc0:2:0): UNIT ATTENTION asc:29,0
st0(ahc0:2:0): Power on, reset, or bus device reset occurred
Is this a hardware problem or a software problem? Has anyone
experienced it before? I am told that this system worked fine
with NT (I saved it from that beast last week). The first hard
drive in the chain works fine, and is where all the filesystems
are; the second doesn't even get detected by the host adapter
and the third is the DAT drive. This chain is in a huge box
called a DataDock 7000. If it's a termination problem or something
similar, opening it would be quite a pain in the ass, so I'd
like to eliminate the possibility of driver problems or otherwise
first.
Also, running cat /dev/st0 results in a long period of tape-whirring
and no output, then the messages above. It looks like it can move
the tape but can't read or write it. The drive id
dmesg shows a few Target Busy messages for st0 after the "no longer
in timeout" message. The drive is a:
(ahc0:2:0): "ARCHIVE Python 28388-XXX 5.AC" type 1 removable SCSI 2
Any insight would be greatly appreciated.
--
Nathan Dorfman | E-mail (business): nathan@fcc.net
Frontline Communications | E-mail (personal): nathan@rtfm.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980723184233.A12037>