From owner-freebsd-hardware  Wed Jun 11 10:52:46 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA06944
          for hardware-outgoing; Wed, 11 Jun 1997 10:52:46 -0700 (PDT)
Received: from argus.acpub.duke.edu (argus.acpub.duke.edu [152.3.233.31])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06939
          for <hardware@FreeBSD.ORG>; Wed, 11 Jun 1997 10:52:43 -0700 (PDT)
Received: from louis.ourway.com (async249-97.async.duke.edu [152.3.249.97]) 
	by argus.acpub.duke.edu (8.8.5/Duke-4.4.1) with SMTP id NAA20556;
	Wed, 11 Jun 1997 13:49:55 -0400 (EDT)
Message-Id: <1.5.4.32.19970611174957.00695aa8@chem.duke.edu>
X-Sender: reese@chem.duke.edu
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 11 Jun 1997 13:49:57 -0400
To: hardware@FreeBSD.ORG
From: Charles Reese <reese@chem.duke.edu>
Subject: Re: Boot up failure
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

At 09:00 AM 6/11/97 +0000, you wrote:
>Tony Kimball wrote:
>> 
>> Quoth Michael Smith on Wed, 11 June:
>> 
>
>A bit deleted for brevity...
>
>> 
>> I have a large IDE disk with one block that will not read.
>> Am I to understand that FBSD provides no mechanism to deal
>> with a single bad block on a disk?
>
>I just recently installed 2.2.2 on my 3.2GB Western Digital EIDE drive
>that until recently had a large amount of bad blocks which prevented
>FreeBSD from being installed at all.  FreeBSD DOES have means for
>detecting and marking bad spots (called 'bad144') which the install can
>optionally use before the filesystem is placed on the drives (or
>after??). However, either bad144 or the way the filesystem is designed
>cannot handle a large amount of bad spots, and thus my drive was useless
>for a long time.  I finally recently got ahold of some utilities from WD
>which thoroughly tests the drive (and destroys all data, i might add)
>and remaps all bad-spots.  In essence once it has done its job you have
>a "defect free" drive.
>
>
>Chris Dillon
>
>
>

Thanks to everyone who replied to my original post.  I ran fsck with the -y
option from single user mode and it seems to have fixed things at least
temporairily.  I have about 60 files in lost+found.  

Cheers
Charlie Reese


-------------------------------------------------------------
Charles E. Reese        *                                   *
Durham, NC 27710        *   Buy      Sell     Trade    CDs  *
919-660-1585            *            NO MIDDLEMAN           *
919-544-7217            *            TOTALLY FREE           *
                        *       http://trader.ourway.com    *
reese@chem.duke.edu     *                                   *
-------------------------------------------------------------