Date: Sat, 7 Dec 1996 06:30:27 -0800 (PST) From: Jaye Mathisen <mrcpu@cdsnet.net> To: Cliff Addy <fbsdlist@revelstone.jvm.com> Cc: Network Coordinator <nc@ai.net>, questions@freebsd.org Subject: Re: Marking Bad Blocks Message-ID: <Pine.NEB.3.95.961207063003.27077Q-100000@mail.cdsnet.net> In-Reply-To: <Pine.BSF.3.91.961207080123.1909A-100000@revelstone.jvm.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Running your adapters disk verify utility should get rid of these blocks. I thought the fs was supposed to do this as well, but it doesn't appear to. On Sat, 7 Dec 1996, Cliff Addy wrote: > Date: Sat, 7 Dec 1996 08:04:01 -0500 (EST) > From: Cliff Addy <fbsdlist@revelstone.jvm.com> > To: Network Coordinator <nc@ai.net> > Cc: questions@freebsd.org > Subject: Re: Marking Bad Blocks > > On Fri, 6 Dec 1996, Network Coordinator wrote: > > > We are seeing errors like this on one of our lab systems: > > > > sd0(ahc0:0:0): MEDIUM ERROR info:396e24 asc:11,0 Unrecovered read error > > We had the same problem, repeatedly, with an Adaptec 2940W and several > Micropolis drives. Never found a solution. The same question you just > asked never got a reply in any forum. Finally just tossed both in favor > of a 2940UW and a Quantum drive (yesterday). Now we'll see if it was the > equipment or if it's an inherent flaw in fbsd. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.961207063003.27077Q-100000>