From owner-freebsd-hardware  Tue Jun 16 23:15:08 1998
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA15936
          for freebsd-hardware-outgoing; Tue, 16 Jun 1998 23:15:08 -0700 (PDT)
          (envelope-from owner-freebsd-hardware@FreeBSD.ORG)
Received: from feral.com (mjacob@gw100.feral.com [192.67.166.129])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15929;
          Tue, 16 Jun 1998 23:15:05 -0700 (PDT)
          (envelope-from mjacob@feral.com)
Received: (from mjacob@localhost)
	by feral.com (8.8.6/8.8.6) id XAA06056;
	Tue, 16 Jun 1998 23:14:59 -0700
Date: Tue, 16 Jun 1998 23:14:59 -0700
From: Matthew Jacob <mjacob@feral.com>
Message-Id: <199806170614.XAA06056@feral.com>
To: asami@FreeBSD.ORG, richard@pegasus.com, sef@kithrup.com
Subject: Re: scsi disk question
Cc: hardware@FreeBSD.ORG
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>se@freebsd.org (not to be confused with sef@freebsd.org ;)) first made the
>suggestion about writing the block fixing it, and I am, at this point,
>thinking that is what did it.  I hope so, anyway. :)

Rewriting sectors often fixes spurious and transient ECC errors.
If this happens a lot for you, check your power supply && drive
grounding - sometimes static buildup can cause this. Or at least
used to. I haven't seen this kind of stuff for quite some time.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message