*BSD News Article 67670


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!EU.net!Germany.EU.net!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Does Archive Viper 150 SCSI tape work reliably?
Date: 4 May 1996 11:29:06 GMT
Organization: Private BSD site, Dresden
Lines: 32
Message-ID: <4mff22$lob@uriah.heep.sax.de>
References: <4m5tjq$gq3@yama.mcc.ac.uk> <4m8mie$jgm@gw.dgii.com>
  <4m9e9f$3cs@yama.mcc.ac.uk>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E

bill@winu.fa.umist.ac.uk (Bill Nutt) wrote:

> sd1(ahc0:1:0):timed out in command phase, SCSISIGI==0x84
> st0(ahc0:6:0):asserted ATN - device reset in message buffer
> st0(ahc0:6:0):timed out in command phase, SCSISIGI==0x94
> ahc0: Issued Channel A Bus Reset #1, 3SCBs aborted
> sd1(ahc0:1:0):UNIT ATTENTION asc:29,0
> sd1(ahc0:1:0):Power on reset, or bus device reset occurred field replaceable
> unit: 29
> ,retries:3
> 
> after that, the machine seems to recover (thankfully!) - the SCSI bus doesnt
> lock up like it did before.
> 
> so - looks like the slow tape doesn't relinquish the bus quick enough, and
> clobbers a command intended for the disk..??????
> 
> ideas anyone?  the tar TO the tape was so close... it must be something
> pretty small - as I said, 2.1-stable is a radical improvement.

Since both the Adaptec 274X and the Archive Viper are known to work
rather well under FreeBSD (i've been using a Viper 150 for almost two
years on my BusLogic 742A [also EISA] controller before i upgraded the
drive to a Tandberg 2.5 Gig one), this smells like some SCSI bus
problem (cabling, termination, ambigous term power, etc.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)