From owner-freebsd-questions Sat Dec 7 06:30:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA27487 for questions-outgoing; Sat, 7 Dec 1996 06:30:47 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA27480 for ; Sat, 7 Dec 1996 06:30:42 -0800 (PST) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.7.6/8.7.3) with SMTP id GAA10313; Sat, 7 Dec 1996 06:30:28 -0800 (PST) Date: Sat, 7 Dec 1996 06:30:27 -0800 (PST) From: Jaye Mathisen To: Cliff Addy cc: Network Coordinator , questions@freebsd.org Subject: Re: Marking Bad Blocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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 > To: Network Coordinator > 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. >