Date: Tue, 9 Jan 2001 17:46:24 +0000 From: Jonathan Perkin <sketchy@netcraft.com> To: Matthew Jacob <mjacob@feral.com> Cc: freebsd-scsi@freebsd.org Subject: Re: Aborted commands and parity errors Message-ID: <20010109174624.G2152@netcraft.com> In-Reply-To: <Pine.LNX.4.21.0101090931490.27687-100000@zeppo.feral.com>; from mjacob@feral.com on Tue, Jan 09, 2001 at 09:35:18am -0800 References: <20010109113131.B1688@netcraft.com> <Pine.LNX.4.21.0101090931490.27687-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 09, 2001 at 09:35:18am -0800, Matthew Jacob wrote: > It's either a bad cable or something that is corrupting data. Be thankful > parity caught it. > > When was the last time you power cycled things? Sometimes a resetting > termpwr fuse gets frotzed and termpwr stops being supplied by the drive > that's supplying it, thus nullifying termination. 5:42PM up 53 days, 1:39, 3 users, load averages: 0.18, 0.48, 0.93 > It's also true, tho rare, that traces just sometimes go on drive or PC > motherboards. Does your system and/or drives run hot? Justin's earlier suggestions fit quite close - the room has been quite hot recently, so I put a fan in there, which is balanced on top of this very SCSI enclosure :) It does vibrate quite a bit, so I guess it could have shaken the cable slightly loose or something. > Try a powercycle. Let it cool down. Then boot up again and see. It always > could be s/w but in this case I doubt it. Yes, I intend to. Many thanks. -- Jonathan Perkin <sketchy@netcraft.com> +44 (0)1225 867914 Netcraft Ltd, Bradford on Avon, UK - http://www.netcraft.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010109174624.G2152>