Date: Fri, 21 Apr 2000 10:00:24 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Grigoriy Strokin <grg@philol.msu.ru> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: bad144 missing? Message-ID: <20000421100024.A20588@orion.ac.hmc.edu> In-Reply-To: <20000421204946.A29420@isabase.philol.msu.ru>; from grg@philol.msu.ru on Fri, Apr 21, 2000 at 08:49:46PM %2B0400 References: <20000421204946.A29420@isabase.philol.msu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 21, 2000 at 08:49:46PM +0400, Grigoriy Strokin wrote: > 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? Yes it has been removed. Modern drives do it for you. By the time you actually see bad blocks your disk is about to die. IIRC, the code was suffering from bitrot and the drives that really needed it will (ESDI and MFM mostly) aren't supported in 5.0. > 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? Most likely the disk is dead. If it is even remotly modern it has lost so many blocks that it has run out of spares and thus is ready to toss. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. 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?20000421100024.A20588>