From owner-freebsd-scsi  Fri Feb  2 23:30:29 2001
Delivered-To: freebsd-scsi@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id A279637B4EC
	for <freebsd-scsi@freebsd.org>; Fri,  2 Feb 2001 23:30:11 -0800 (PST)
Received: from beppo (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id XAA28677;
	Fri, 2 Feb 2001 23:29:49 -0800
Date: Fri, 2 Feb 2001 23:29:47 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: thomas@hentschel.net
Cc: wash@iconnect.co.ke, freebsd-scsi@freebsd.org
Subject: Re: CANNOT ACCESS T20 TAPE
In-Reply-To: <200102030336.f133a1H25367@falcon.home.hentschel.net>
Message-ID: <Pine.BSF.4.21.0102022328001.1868-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I have my doubts. The errors he was seeing indicated complete breakage (i.e,,
never could have worked at all). I have a T20 that works for me 3.01.

W/O more details about how it fails for you (please build a CAMDEBUG kernel
and use the -Ic option to turn on debugging when doing an initial 'mt status'
if this is where it's failing for you) I can't say whether "same" is a
meaningful statement.

> dmesg snipped :
> sa0 at ahc0 bus 0 target 3 lun 0
> sa0: <HP T20 3.01> Removable Sequential Access SCSI-2 device 
> sa0: 3.300MB/s transfers
> 
> otherwise same symptons as for Wash.
> If there is anything else needed, please let me know.
> 
> -Th [just subscribing to -scsi, so please cc: me]
> 



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