From owner-freebsd-hackers Tue May 16 16:39:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 78BD637B59F for ; Tue, 16 May 2000 16:39:22 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id QAA09360; Tue, 16 May 2000 16:39:15 -0700 (PDT) Date: Tue, 16 May 2000 16:39:14 -0700 From: Brooks Davis To: Nick Rogness Cc: hackers@FreeBSD.ORG Subject: Re: Bad Block scan Message-ID: <20000516163914.A8494@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from nick@rapidnet.com on Tue, May 16, 2000 at 04:59:11PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 16, 2000 at 04:59:11PM -0600, Nick Rogness wrote: > > I thought FreeBSD had an option on install to run a bad block scan on a > drive? Just installed (4.0-RELEASE) and noticed it wasn't there. Any > specific reason...or maybe a reference page that explains. Thanks in > advance. Bad block management was removed in 4.0. All modern drives (ATA and SCSI) do hardware bad block management and no one wanted to maintain the old code so it was killed. The general feeling is that if your disk generates errors it has run out of replacement sectors and thus is dying and should be replaced. -- 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-hackers" in the body of the message