From owner-freebsd-questions Tue Aug 12 18:38:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA07609 for questions-outgoing; Tue, 12 Aug 1997 18:38:33 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts7-line11.uoregon.edu [128.223.150.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07604 for ; Tue, 12 Aug 1997 18:38:30 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id SAA00279; Tue, 12 Aug 1997 18:38:17 -0700 (PDT) Date: Tue, 12 Aug 1997 18:38:17 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Joachim Wunder cc: questions@FreeBSD.ORG Subject: Re: bad block 808464440, ino 23166 (HELP!) In-Reply-To: <9708121826.AA12225@sun1.lrz-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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