From owner-freebsd-current Sat Feb 26 9:23:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1CE1537BE5B for ; Sat, 26 Feb 2000 09:23:03 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA12342; Sat, 26 Feb 2000 18:22:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: kibbet Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad blocks In-reply-to: Your message of "Sun, 27 Feb 2000 02:39:03 +1030." Date: Sat, 26 Feb 2000 18:22:45 +0100 Message-ID: <12340.951585765@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , kibbet writes: >This message is in MIME format >--_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_ >Content-Type: text/plain; charset=us-ascii > >Hi all, > >Quick question, how does the new ata driver handle bad blocks? >I've been tracking -current since around Nov 99 but haven't >seen this come up. It doesn't. The drives have to handle bad blocks now. If you have a drive where bad144 remapping is enabled, try to find out if any sectors have been remapped, if not you can simply turn off bad144. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message