From owner-freebsd-questions Tue Apr 9 06:41:32 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA11565 for questions-outgoing; Tue, 9 Apr 1996 06:41:32 -0700 (PDT) Received: from lenzi ([200.247.248.103]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA11559 for ; Tue, 9 Apr 1996 06:41:21 -0700 (PDT) Received: (from lenzi@localhost) by lenzi (8.6.12/8.6.12) id KAA00433; Tue, 9 Apr 1996 10:42:31 -0300 Date: Tue, 9 Apr 1996 10:42:25 -0300 (EST) From: "Lenzi, Sergio" X-Sender: lenzi@lenzi To: questions@freebsd.org cc: Richard Chang Subject: Re: hard reading error In-Reply-To: <199604090752.JAA08450@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 9 Apr 1996, J Wunsch wrote: > As Richard Chang wrote: > > > I am experiencing a problem with my FreeBSD partition with a hard > > reading error on my hard drive since someone accidentally kicked the > > machine while it was running. I had fixed the problem in DOS by > > repairing it with Norton Disk Doctor, is there a way to do it under FreeBSD? Hello Richard, I correct this problem in my FreeBSD using the badsect program When the error occurs the system display on the console: FSB NNNNNNNNN where NNN is the sector number in error. 1) make a /BAD directory in the file system in error say: /usr/BAD 2) run badsect /usr/BAD NNNN NNNNN NNNN... 3) boot the machine with -s option. 4) run fsck /dev/rwdxx (xx) as indicated in the badsect output 5) answer to the fsck (y or n) according. (preserve BAD..., no remove BAD, remove file...) 6) quit shell and let the system reboot. 7) recover deleted files listed by fsck. (from the cdrom for example). That's it . Sergio lenzi Unix consult.