From owner-freebsd-questions Wed Oct 11 13:56:04 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA17765 for questions-outgoing; Wed, 11 Oct 1995 13:56:04 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA17759 for ; Wed, 11 Oct 1995 13:55:59 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id NAA03154; Wed, 11 Oct 1995 13:55:47 -0700 From: Julian Elischer Message-Id: <199510112055.NAA03154@ref.tfs.com> Subject: Re: bad144 on a 1gig IDE drive To: rnw+@andrew.cmu.edu (Robert N Watson) Date: Wed, 11 Oct 1995 13:55:47 -0700 (PDT) Cc: freebsd-questions@freefall.freebsd.org In-Reply-To: from "Robert N Watson" at Oct 10, 95 04:05:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1842 Sender: owner-questions@FreeBSD.org Precedence: bulk > > Yes, it's me, the one with numerous NIS, wd1, etc, problems. Well, > those are all fixed ;). However, now I have to deal with a set of bad > blocks that inopportunely turned up in my /var partition. It's going to > be one of those days, I think (so far in the last two days: failed to > install a 540 meg IDE drive for about 18+ housr). I have set several > bad144 sessions going over the past 8 hours, trying to get some > combination and setup that is happy, and have had a variety of problems, > but so far been unable to mark any bad blocks with it. It scans fine, > and finds them, they just don't get marked because bad144 aborts each > time. This time it got.. > > ... > Block: 271516 will be marked BAD. > Block: 271517 will be marked BAD. > Block: 271518 will be marked BAD. > Too many bad sectors, can only handle 126 per slice. ^^^^^^^^^^ > fledge> divide your disk into two slices.. :) > > Which seems logical, only leaving the question what to do about it. It > also failed with a variety of sn# errors earlier, but that seems to have > stopped for now. As far as I know, badsect is the other bad sector > handling program -- does anyopne have any particular advice as to how to > pull all the information together and block off the sectors from general > use? I assume some script combining bad144 to get the bad block > numbers, and then badsect to create a file over them, but I honestly > don't know, as I haven't dealt with this problem before. Is there any > way to turn up the number of sectors handled by bad144, or a premade > script someone has lying around to block out such sectors? > > Thanks.. > > Robert > ---- > Robert Watson (rnw+@andrew.cmu.edu) * Double major: IDS/CS * H&SS > http://www.watson.org/ robert@fledge.watson.org >