From owner-freebsd-questions Thu Oct 2 22:09:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17600 for questions-outgoing; Thu, 2 Oct 1997 22:09:07 -0700 (PDT) Received: from joshua.sns.org (dan@joshua.sns.org [207.219.216.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17592 for ; Thu, 2 Oct 1997 22:09:04 -0700 (PDT) Received: from localhost (dan@localhost) by joshua.sns.org (8.8.5/8.8.5) with SMTP id BAA04202 for ; Fri, 3 Oct 1997 01:08:35 -0400 (EDT) Date: Fri, 3 Oct 1997 01:08:35 -0400 (EDT) From: dan To: freebsd-questions@freebsd.org Subject: Bad Blocks on IDE Drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I am continuing my battle to install -CURRENT on a 1.6Gb IDE Western Digital Drive. I have tried installing via FTP a number of times and ran into wd0: soft error and wd0: hard error's. The recommendations from my first post indicated that I had some bad blocks on the drive. I tried to do a bad block/low level format of the drive but my bios did not support this. I downloaded a util from WD to lowlevel the drive and gave it a shot. Again installation failed. I switched to a brand new, ultra modern motherboard and ran the bios lowlevel/bad block marking routine. Both the WD and BIOS utils find no bad blocks. Again installation fails. So I gave it one last shot and selected bad block scan from the FreeBSD FDISK screen. The scan found roughly 9 bad sectors and then started picking out bad blocks. This became rather tedious so I left the room and came back to find that bad144 had found too many bad blocks and was exiting. The strange thing is that both dos and windows installs and operates on the drive without any problems. Is there anything anyone can suggest? I am really stumped with this one! I suppose returning the drive would be a good idea, but the shop has gone under. Thanks! dan dan@sns.org