Date: Wed, 11 Jun 1997 13:49:57 -0400 From: Charles Reese <reese@chem.duke.edu> To: hardware@FreeBSD.ORG Subject: Re: Boot up failure Message-ID: <1.5.4.32.19970611174957.00695aa8@chem.duke.edu>
next in thread | raw e-mail | index | archive | help
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 * *
-------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1.5.4.32.19970611174957.00695aa8>