From owner-freebsd-questions Thu Jul 10 15:31:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA02413 for questions-outgoing; Thu, 10 Jul 1997 15:31:37 -0700 (PDT) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA02408 for ; Thu, 10 Jul 1997 15:31:34 -0700 (PDT) Received: from terra.aros.net (terra.aros.net [207.173.16.10]) by mars.aros.net (8.8.5/8.8.4) with ESMTP id QAA25076 for ; Thu, 10 Jul 1997 16:30:49 -0600 (MDT) Received: (from angio@localhost) by terra.aros.net (8.8.5/8.6.12) id QAA13001 for questions@freebsd.org; Thu, 10 Jul 1997 16:31:32 -0600 From: Dave Andersen Message-Id: <199707102231.QAA13001@terra.aros.net> Subject: Damaged disk in CCD - kernel panics To: questions@freebsd.org Date: Thu, 10 Jul 1997 16:31:31 -0600 (MDT) X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We have a drive that's relatively damaged that was a part of a 4-stripe CCD. A kind soul shut off our air conditioning in our old facility and caused a great deal of equipment to fail (growl). The drive has been somewhat recovered, but causes a kernel panic when some files on the CCD are accessed. We've sent in a send-pr for it, but I was curious if anyone had any suggestions? The server is running 2.2.2. I need as much data off of the drives as possible; the CCD won't fsck. However, anything that caused it to stop kernel panicing and instead cause the access operation to fail would be quite groovy. -Dave