From owner-freebsd-current Wed Nov 18 10:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18377 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:49:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18359 for ; Wed, 18 Nov 1998 10:49:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA07314; Wed, 18 Nov 1998 10:48:41 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:48:40 -0800 (PST) From: Doug White To: Jason George cc: "'freebsd-current@freebsd.org'" Subject: Re: Issue with Bad Block scan on fresh disk In-Reply-To: <01BE128F.CD600D40@infomat> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Jason George wrote: > I was building two new 3.0 boxes when I stumbled upon a little nuance > with the bad block scan within the initial sysinstall. I was > wondering if anyone else had noticed this or had any suggestions. The bad block scan is useless for IDE and SCSI drives. If it finds anything return the drive and get a replacement... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message