From owner-freebsd-hardware Thu Jul 10 12:29:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18438 for hardware-outgoing; Thu, 10 Jul 1997 12:29:17 -0700 (PDT) Received: from cruz.isle.net (root@cruz.isle.net [204.140.227.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18432 for ; Thu, 10 Jul 1997 12:29:11 -0700 (PDT) Received: from john (router1port05.isle.net [204.140.227.228]) by cruz.isle.net (8.6.12/8.6.11) with SMTP id MAA11410 for ; Thu, 10 Jul 1997 12:53:01 -0700 Message-Id: <3.0.1.32.19970710122500.0085c730@mail.isle.net> X-Sender: johns@mail.isle.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 10 Jul 1997 12:25:00 -0700 To: freebsd-hardware@FreeBSD.ORG From: John Scharles Subject: disk Hard Error Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On powering up our FreeBSD 2.1.6 this morning we were greeted with a "hard error reading block such&such" message. This is a Dell machine with a built in IDE controller. After looking through the handbook and archives I haven't found much information about trying to recover files off a dying drive (it has the /usr directory, which of course has some files that are nowhere else!). Is there way I can look at or force a mount? Also I saw some reference to a full drive causing this type of error...could this be the cause of a hard error? Thanks John