From owner-freebsd-hardware Fri Dec 14 17:37:19 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id EA57B37B419 for ; Fri, 14 Dec 2001 17:37:15 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBF1hLb05808; Fri, 14 Dec 2001 17:43:21 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112150143.fBF1hLb05808@mass.dis.org> To: John Polstra Cc: hardware@freebsd.org, msmith@mass.dis.org Subject: Re: Question about a strange hardware problem In-Reply-To: Message from John Polstra of "Fri, 14 Dec 2001 16:43:19 PST." Date: Fri, 14 Dec 2001 17:43:21 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > The system has been up for 317 days. It seems like if the problem > were in the RAM (the obvious place), it would have crashed by now. That's not a given at all. > Given all that, it seems to me that the problem must be in the drive > electronics of da0. What do you think? As a test, I've moved the > files that always show the errors over to da1 for a while, to see if > that fixes it. That's a good test, and I'd want to see the results of it before making any more judgements, although you might just be masking the problem. 8( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message