Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 May 2001 11:05:56 -0400
From:      "Eric Sproul" <esproul@cstone.net>
To:        freebsd-hardware@freebsd.org
Subject:   problem with tape drive?
Message-ID:  <3B0E74D4.2C293F35@cstone.net>

next in thread | raw e-mail | index | archive | help
Hi,
I'm using an Exabyte EXB-210 tape changer with one Mammoth drive under
4.3-RELEASE with Amanda.  The past two nights, Amanda has reported
failures while writing backups to tape.  I noticed the following
messages in dmesg:

(sa0:ahc1:0:6:0): SCB 0x4 - timed out while idle, SEQADDR == 0x8
STACK == 0x3, 0x17c, 0x166, 0x0
SXFRCTL0 == 0x80
ahc1: Dumping Card State at SEQADDR 0x8
SCSISEQ = 0x12, SBLKCTL = 0x6, SSTAT0 0x0
SCB count = 20
Kernel NEXTQSCB = 3
Card NEXTQSCB = 3
QINFIFO entries: 
Waiting Queue entries: 
Disconnected Queue entries: 0:4 
QOUTFIFO entries: 
Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28 29 30 31 
Pending list: 4 
Kernel Free SCB list: 14 15 16 17 18 19 0 1 2 5 6 7 8 9 13 12 11 10 
Untagged Q(6): 4 
(sa0:ahc1:0:6:0): Queuing a BDR SCB
(sa0:ahc1:0:6:0): Bus Device Reset Message Sent
(sa0:ahc1:0:6:0): no longer in timeout, status = 34b
ahc1: Bus Device Reset on A:6. 1 SCBs aborted
(sa0:ahc1:0:6:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 
(sa0:ahc1:0:6:0): UNIT ATTENTION csi:0,0,0,44 asc:29,0
(sa0:ahc1:0:6:0): Power on, reset, or bus device reset occurred
(sa0:ahc1:0:6:0): failed to write terminating filemark(s)
(sa0:ahc1:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
command to
 clear this state.


Here's the probe for ahc1 and sa0: 

ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0xe800-0xe8ff mem
0xfebef000-0xfebeffff irq 10 at device 11.1 on pci0
aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs

sa0 at ahc1 bus 0 target 6 lun 0
sa0: <EXABYTE EXB-89008E000204 V38b> Removable Sequential Access SCSI-2
device 
sa0: 10.000MB/s transfers (10.000MHz, offset 15)

The SCSI controller is integrated on the Tyan S1837 motherboard.  Can
anyone tell me what happened here?  It is not a persistent problem
because after I noticed the failures, I flushed the remaining dumps
without incident.  

Thanks in advance!
Eric

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B0E74D4.2C293F35>