Date: Fri, 17 Oct 1997 11:10:46 -0400 From: Andrew T Heybey <ath@bellcore.com> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), Greg Lehey <grog@lemis.com> Cc: scsi@freebsd.org Subject: Re: NCR 53c810 & DAT tape Message-ID: <199710171510.LAA04572@grapenuts.bellcore.com> In-Reply-To: Your message of Fri, 17 Oct 1997 08:44:18 %2B0200. <19971017084418.JR57181@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>>On Fri, 17 Oct 1997 08:44:18 +0200, j@uriah.heep.sax.de (J Wunsch) said: j> If this happens randomly, at different spots, and not on each j> dump, this awfully smells like the similar problems people j> (including me) have been reporting for these drives on the ahc j> driver. Symptoms there: ``timed out in command phase'', j> resetting SCSI bus, etc. You should be able to find the traces j> in the -scsi list archives, by searching for "ARCHIVE Python j> 25501-XXX". It does happen randomly. Last night I managed to dump all of /usr (~300 MB) without complaint. This morning I tried to dump / and it died after 1670 blocks. Then I tried again and got through / and the first 206 MB of /usr before it crapped out. This is trying to use different tapes, so I don't think it is a tape problem. (Though they are all the same brand of tape (Digital 60m DDS)--maybe I should get a different brand?) A search for "ARCHIVE Python" and then "DAT wunsch" failed to reveal any -scsi messages that looked like my problem. Was there any kind of resolution in the earlier messages? I also tried the Windoze NT backup program on it last night. It claimed to write the tape fine (two backup sets of about 200 & 300 MB) but complained of read errors when trying to verify the backup. Greg Lehey wrote: > Is this repeatable? Do you have your termination set up correctly? It is definitely repeatable (see above). There are passive terminators on the controller and active termination in the DAT drive. All the terminators have been installed/turned on since the beginning. The DAT drive has the ability to supply terminator power; at first that was turned off but I have since turned it on. The drive can enable or disable parity, so I tried that both ways as well (not that I really thought it would make a difference). andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710171510.LAA04572>