Date: Fri, 6 Oct 2000 14:19:21 -0500 (CDT) From: David Kelly <dkelly@mail.hiwaay.net> To: dest@syd.eastlink.ca, freebsd-stable@FreeBSD.ORG Subject: Re: Bad IDE Drive Message-ID: <200010061919.e96JJLR20684@mail.hiwaay.net>
next in thread | raw e-mail | index | archive | help
Craig Hawco <dest@syd.eastlink.ca> writes:
>
> 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.
man badsect:
BADSECT(8) FreeBSD System Manager's Manual BADSECT(8)
NAME
badsect - create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector....
[...]
A better solution would be to contact the manufacturer of the IDE drive
for a utility to internally remap the bad blocks. This kind of thing
is standardized on SCSI disks but apparently not on IDE.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010061919.e96JJLR20684>