From owner-freebsd-hardware Tue Jun 10 17:03:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14071 for hardware-outgoing; Tue, 10 Jun 1997 17:03:17 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14051 for ; Tue, 10 Jun 1997 17:03:09 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA12555; Wed, 11 Jun 1997 09:32:28 +0930 (CST) From: Michael Smith Message-Id: <199706110002.JAA12555@genesis.atrad.adelaide.edu.au> Subject: Re: Boot up failure In-Reply-To: <199706101742.MAA00935@compound.east.sun.com> from Tony Kimball at "Jun 10, 97 12:42:31 pm" To: Anthony.Kimball@East.Sun.COM Date: Wed, 11 Jun 1997 09:32:27 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, reese@chem.duke.edu, hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Kimball stands accused of saying: > > 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? No, FreeBSD provides several mehanisms for dealing with bad blocks. In your case, I would try the 'badsect' manpage, and possibly also 'bad144'. The previous correspondent had a disk showing the signs of catastrophic failure, which no bad-sector-remapping program is going to help. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[