From owner-freebsd-questions Tue Apr 9 15:20:24 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA21879 for questions-outgoing; Tue, 9 Apr 1996 15:20:24 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA21826 for ; Tue, 9 Apr 1996 15:20:16 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id PAA23912; Tue, 9 Apr 1996 15:20:02 -0700 Date: Tue, 9 Apr 1996 15:20:00 -0700 (PDT) From: Richard Chang To: Michael Smith cc: joerg_wunsch@uriah.heep.sax.de, questions@freebsd.org Subject: Re: hard reading error In-Reply-To: <199604091403.XAA16140@genesis.atrad.adelaide.edu.au> 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, Michael Smith wrote: > Richard Chang stands accused of saying: > > > >>> 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? > >> > >> Error messages? > > > > Here they are: > > > > 1006499 of 1006496-1006511 (wd0s2 bn 1112995; cn 1104 tn 2 sn 37)wd0: status 59< > > seekdone,drq,err> error 40 > > wd0s2e: hard error reading fsbn 1006499 of 1006496-1006511 (wd0s2 bn 1112995; cn > > 1104 tn 2 sn 37)wd0: status 59 error 40 > > wd0s2e: hard error reading fsbn 1006499 of 1006496-1006511 (wd0s2 bn 1112995; cn > > 1104 tn 2 sn 37)wd0: status 59 error 40 > > The 'badsect' command is the easiset way of dealing with this. Read > the 'badsect' manpage for intimate details on the process. The "bad > sector number" you want is the 'fsbn' (filesystem block number) value, > ie 1006499. > > If we assume that /dev/wd0s2e is mounted as /foo, you would say : > > # cd /foo > # mkdir BAD > # badsect BAD 1006499 Tried this but it said cannot attach 1006499 so any ideas? > # cd / > # umount /foo > # fsck /dev/rwd0s2e > (respond as detailed in the badsect manpage) Richard