Date: Mon, 21 Oct 1996 22:43:58 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Dan Janowski <danj@netcom.com> Cc: questions@FreeBSD.org Subject: Re: IDE hard error Message-ID: <Pine.BSI.3.94.961021224259.4986G-100000@gdi.uoregon.edu> In-Reply-To: <199610191556.IAA20720@netcom.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Oct 1996, Dan Janowski wrote: > > I have a Seagate 1.2GB IDE (a Conner drive, a la acquisition), > the kernel is generating the following message: > > wd0s1e: hard error reading fsbn 34192 of 34176-34303 (wd0s1 bn 611728; cn 606 tn 13 sn 61)wd0: status 59<seekdone,drq,err> error 40<uncorr> > > This is a bad block, I assume. Are not IDE drives suppoed to > handle badblocks internally? If so, is this driver bad? > If not, what am I supposed to do to mark the badblock? > BTW, This is a brand new drive, the first Conner/Seagate had > a bad controller, yikes! They're SUPPOSED to (or the controller is at least) but the feature can be disabled by external jumpers on some models. You might check cabling and internal temperature. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.961021224259.4986G-100000>