From owner-freebsd-current Wed Nov 18 00:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00163 for freebsd-current-outgoing; Wed, 18 Nov 1998 00:08:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skunkworks.specialty.ab.ca (skunkworks.specialty.ab.ca [207.167.8.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00158 for ; Wed, 18 Nov 1998 00:08:39 -0800 (PST) (envelope-from j.b.george@ieee.org) Received: (from uucp@localhost) by skunkworks.specialty.ab.ca (8.8.8/8.8.8) with UUCP id BAA19608 for freebsd-current@freebsd.org; Wed, 18 Nov 1998 01:08:14 -0700 (MST) (envelope-from j.b.george@ieee.org) Received: from infomat (infomat [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id BAA19619 for ; Wed, 18 Nov 1998 01:07:08 -0700 (MST) (envelope-from j.b.george@ieee.org) Received: by infomat with Microsoft Mail id <01BE128F.CD600D40@infomat>; Wed, 18 Nov 1998 01:07:24 -0700 Message-ID: <01BE128F.CD600D40@infomat> From: Jason George To: "'freebsd-current@freebsd.org'" Subject: Issue with Bad Block scan on fresh disk Date: Wed, 18 Nov 1998 01:07:23 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA00159 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Here's the scenario: I took a new 5.2G Quantum IDE drive out of the sealed static bag, configured the BIOS to detect it, and booted the 3.0-RELEASE boot floppy. I chose a Custom Install, and Dangerously Dedicated the entire disk, set it bootable, and flagged a Bad Block Scan. I then sliced the disk. When it finally came time to do the bad block scan and subsequent filesystem generation, the bad block scan DID NOT proceed, yet the filesystem generation and system install did continue to completion. A little perplexed, I rebooted and followed my normal installation procedure (Custom Install, Dangerously Dedicated, etc, as above). This time, the bad block scan ran before the filesystem generation. The system install continued to completion. I thought this was a freak occurence, but when I built a second box with another farm-fresh virgin drive using the same procedure, the bad block scan was ignored again. I reinstalled a second time on the second box. The bad block scan ran fine. I'd dig more into this, but the cost of iteration makes the work a little difficult. ;-) --Jason j.b.georgeieee.org jbgmasterplan.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message