Date: Tue, 9 Apr 1996 15:20:00 -0700 (PDT) From: Richard Chang <richardc@CSUA.Berkeley.EDU> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: joerg_wunsch@uriah.heep.sax.de, questions@freebsd.org Subject: Re: hard reading error Message-ID: <Pine.PTX.3.91.960409151919.24231q-100000@soda.CSUA.Berkeley.EDU> In-Reply-To: <199604091403.XAA16140@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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<uncorr> > > wd0s2e: hard error reading fsbn 1006499 of 1006496-1006511 (wd0s2 bn 1112995; cn > > 1104 tn 2 sn 37)wd0: status 59<seekdone,drq,err> error 40<uncorr> > > wd0s2e: hard error reading fsbn 1006499 of 1006496-1006511 (wd0s2 bn 1112995; cn > > 1104 tn 2 sn 37)wd0: status 59<seekdone,drq,err> error 40<uncorr> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.PTX.3.91.960409151919.24231q-100000>