From owner-freebsd-questions  Sat Dec  7 05:04:11 1996
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id FAA25183
          for questions-outgoing; Sat, 7 Dec 1996 05:04:11 -0800 (PST)
Received: from revelstone.jvm.com (revelstone.jvm.com [207.98.213.2])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA25175
          for <questions@freebsd.org>; Sat, 7 Dec 1996 05:04:08 -0800 (PST)
Received: (from fbsdlist@localhost) by revelstone.jvm.com (8.7.5/8.6.12) id IAA01952; Sat, 7 Dec 1996 08:04:01 -0500 (EST)
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
In-Reply-To: <Pine.BSF.3.91.961206200415.15041A-100000@alyssa.ai.net>
Message-ID: <Pine.BSF.3.91.961207080123.1909A-100000@revelstone.jvm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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.