From owner-freebsd-hardware  Tue Jun 10 10:45:26 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA19520
          for hardware-outgoing; Tue, 10 Jun 1997 10:45:26 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA19512
          for <hardware@FreeBSD.ORG>; Tue, 10 Jun 1997 10:45:22 -0700 (PDT)
Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA06377; Tue, 10 Jun 1997 11:02:33 -0700
Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3)
	id NAA29946; Tue, 10 Jun 1997 13:41:33 -0400
Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4)
	id NAA06504; Tue, 10 Jun 1997 13:42:35 -0400
Received: (from alk@localhost) by compound.east.sun.com (8.8.5/8.7.3) id MAA00935; Tue, 10 Jun 1997 12:42:31 -0500 (CDT)
Date: Tue, 10 Jun 1997 12:42:31 -0500 (CDT)
Reply-To: Anthony.Kimball@East.Sun.COM
Message-Id: <199706101742.MAA00935@compound.east.sun.com>
From: Tony Kimball <Anthony.Kimball@East.Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: msmith@atrad.adelaide.edu.au
Cc: reese@chem.duke.edu, hardware@FreeBSD.ORG
Subject: Re: Boot up failure
References: <1.5.4.32.19970610134414.006eec70@chem.duke.edu>
	<199706101455.AAA09464@genesis.atrad.adelaide.edu.au>
X-Face: O9M"E%K;(f-Go/XDxL+pCxI5<W_e*r7B8ojMD.5+qDgOp4/\gTQEgbOoBqf:Vtl*aW:<;9/
	UIVk'U^XhYg+v#r~*X<$Q=_ik@5:%E}pl]9|9|:]WLW8n:fLgg0~cfwWRBQxK/HSG0b1D/gljJC$qp
	b=HDF@+"H<|fXy`w#$8#6A"!F:>*gr[=FN@Y`cl1.Tn
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Quoth Michael Smith on Wed, 11 June:

: > Failure: cannont read blk 19904
: 
: You appear to have suffered a disk failure.
: 
: > So the question is: What can be done?  Is there a FreeBSD program to scan
: > and fix the bad blocks?  Can we run tar and/or transfer files to the floppy
: > disk in single user mode?  Can we ftp over the local ethernet?
: 
: The correct procedure in this situation is :
: 
:  - check cabling in case vibration has dislodged the power or data 
:    connectors
:  - replace the disk
:  - restore from backup
:  - optional : attempt to recover the disk using vendor-supplied disk recovery
:    tools, or return to the supplier for warranty replacement
: 
: Even the most expensive IDE disk is not worth more than a few hours of
: downtime and operator time, and it sounds as though yours has thrown 
: in the towel good and proper.
: 

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?