Date: Fri, 17 Oct 1997 08:44:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: ath@bellcore.com (Andrew Heybey) Subject: Re: NCR 53c810 & DAT tape Message-ID: <19971017084418.JR57181@uriah.heep.sax.de> In-Reply-To: <199710162020.QAA01841@grapenuts.bellcore.com>; from Andrew Heybey on Oct 16, 1997 16:20:22 -0400 References: <199710162020.QAA01841@grapenuts.bellcore.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Andrew Heybey wrote: > I try to do a large dump on the drive (about 300 MB), and it dies > after 26340 tape blocks with a write error, and the drive wedges with > both LEDs on. > ncr0:6: ERROR (a0:0) (a-2a-0) (48/13) @ script (1bc:7c094800). > ncr0: script cmd = 900b0000 > ncr0: regdump: da 10 80 13 47 48 06 1f 01 0a 86 2a 80 00 0a 00. > ncr0: restart (fatal error). > st0: COMMAND FAILED (9 ff) @f064ea00. > ncr0: timeout ccb=f064ea00 (skip) If this happens randomly, at different spots, and not on each dump, this awfully smells like the similar problems people (including me) have been reporting for these drives on the ahc driver. Symptoms there: ``timed out in command phase'', resetting SCSI bus, etc. You should be able to find the traces in the -scsi list archives, by searching for "ARCHIVE Python 25501-XXX". -- 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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971017084418.JR57181>