Date: Sun, 5 Dec 1999 22:50:26 +0100 (CET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: kbyanc@posi.net (Kelly Yancey) Cc: jkh@zippy.cdrom.com, dseg@texar.com, billf@chc-chimes.com, rfg@monkeys.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Strange SCSI sickness Message-ID: <199912052150.WAA74217@yedi.iaf.nl> In-Reply-To: <Pine.BSF.4.05.9912051604550.35433-100000@kronos.alcnet.com> from Kelly Yancey at "Dec 5, 1999 4:15:51 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Kelly Yancey wrote ... > > > > 3b) Examination of the drive(s) in question for any cooling or > > mounting deficiencies. Depending on the SCSI errors in question, > > I might even investigate firmware updates for the drive(s). > > > > I actually used to get these *exact* errors a couple of years ago on > various 2.x systems. At first, I had assumed a bug in the driver (the ahc > driver was noted as still having some bugs at the time, if I recall > correctly). The errors would rare (every month or so, but they would come > in batches). I kept upgrading, from 2.1.5, through 2.2.5 hoping that the > errors would go away. Now, my ignorance being point out, it turned out > that the errors were actually heat-induced. Another interesting cause for problems is duff powersupplies. As the proverb goes "every machine is as good as it's PSU". E.g. I just struggeled with a DLT tape unit that inexplicable reset itself. After examining the 5Volts rail with a scope I found glitches on it whenever the drive did a bit of rewinding (dropping out of streaming mode). Had me stumped for a while. W/ -- | / o / / _ Arnhem, The Netherlands - The FreeBSD Project |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912052150.WAA74217>