From owner-freebsd-stable Fri Oct 6 12:14:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.eastlink.ca (syd.eastlink.ca [24.222.47.133]) by hub.freebsd.org (Postfix) with ESMTP id 04E1937B502 for ; Fri, 6 Oct 2000 12:14:15 -0700 (PDT) Received: from Craig (u56n134.hfx.eastlink.ca [24.222.56.134]) by mail.eastlink.ca (8.9.3/8.9.3) with ESMTP id QAA07642 for ; Fri, 6 Oct 2000 16:14:08 -0300 Message-Id: <5.0.0.25.0.20001006160901.009eb5d0@pop.syd.eastlink.ca> X-Sender: dest@pop.syd.eastlink.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 06 Oct 2000 16:14:38 -0300 To: freebsd-stable@FreeBSD.org From: Craig Hawco Subject: Bad IDE Drive Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have recently fled from FreeBSD back into (ugh) windows because of a minor drive problem. It seems that my drive has a few bad blocks, and I know what they are. FreeBSD seems to try to write to the same bad sectors every time, and keeps printing errors that it can't write to the block, etc etc. The thing is it's the same few (about a dozen) sectors, about 8/10ths the way through the drive. I could use only up to that amount, but that doesn't seem like an elegant solution leaving a few hundred megs of empty space. Is there a way to have FreeBSD map the sectors and try to neither read nor write to them? It wouldn't be a problem (I can turn off syslog and get rid of the nasty messages ;) if it didn't cause the filesystem to become corrupted (fsck tries to read/fix the data on the bad spots and dies). Hope someone out there can help. --Craig P.S. - I know this might not be the BEST place to ask, but I've been on this list and only this list for a couple months, so I'd prefer to ask here. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message