Date: Tue, 12 Aug 1997 18:38:17 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Joachim Wunder <Joachim.Wunder@lrz.tu-muenchen.de> Cc: questions@FreeBSD.ORG Subject: Re: bad block 808464440, ino 23166 (HELP!) Message-ID: <Pine.BSF.3.96.970812183706.252E-100000@localhost> In-Reply-To: <9708121826.AA12225@sun1.lrz-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Aug 1997, Joachim Wunder wrote: > I have an old WD AP4200 (200 MByte) IDE-drive for /usr/obj > > After a tar to /usr/obj the dmesg output look like the following: > > [...] > pid 1442 (tar), uid 100 on /usr/obj: bad block > bad block 808464432, ino 23166 > > Of course I already formatted /dev/wd2 new (where my /usr/obj lies). > And I did a bad144 -s -v. > > A bad144 /dev/wd2 shows: > bad block information at sector 414505 in /dev/wd2: > cartridge serial number: 10211994(10) > > > > So do I really have a bad harddisk?! Unfortunately the bad blocks are going to show, so you're over your buffer. bad144 will block them out, but more will probably pop up. A new disk is in order, although a few passes with bad144 will lock out anything it finds. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970812183706.252E-100000>