From owner-freebsd-stable Fri Apr 21 10:12:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B7FF237BD73 for ; Fri, 21 Apr 2000 10:12:30 -0700 (PDT) (envelope-from dkelly@mail.hiwaay.net) Received: (from dkelly@localhost) by mail.hiwaay.net (8.10.1/8.10.1) id e3LHCTb26100; Fri, 21 Apr 2000 12:12:29 -0500 (CDT) Date: Fri, 21 Apr 2000 12:12:29 -0500 (CDT) From: David Kelly Message-Id: <200004211712.e3LHCTb26100@mail.hiwaay.net> To: freebsd-stable@FreeBSD.ORG, grg@philol.msu.ru Subject: Re: bad144 missing? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Accidentally, I've found out that /usr/sbin/bad144 in my fbsd 4.0 > is dated by December, and there is no bad144 in /usr/src. > So, has it disappeared? > > I have a HDD with bad blocks, how do I find all of them and mark them? > I've done newfs, then fsck, fsck reports > CANNOT READ: BLK 1114288 CONTINUE? [yn] > several times. Apparently, fsck won't mark the blocks it can't read as bad, > and therefore some data will be written there and then lost. > Am I missing something? How could I achieve functionality > that earlier was provided by bad144? Use badsect(8) to create files(s) containing the bad blocks. -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message