From owner-freebsd-questions@FreeBSD.ORG Tue Aug 25 07:41:23 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 736351065690 for ; Tue, 25 Aug 2009 07:41:23 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7468FC18 for ; Tue, 25 Aug 2009 07:41:23 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n7P7fMCf062703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Aug 2009 00:41:22 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n7P7fM6H062702; Tue, 25 Aug 2009 00:41:22 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA14532; Tue, 25 Aug 09 00:35:23 PDT Date: Tue, 25 Aug 2009 00:38:59 -0700 From: perryh@pluto.rain.com To: kellymartin@gmail.com Message-Id: <4a939513.NMAP0NNWLEg7ayVF%perryh@pluto.rain.com> References: <1338880b0908241129p75b6845cg26d21804e118364@mail.gmail.com> <44y6p9q7rd.fsf@be-well.ilk.org> In-Reply-To: <44y6p9q7rd.fsf@be-well.ilk.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: hard disk failure - now what? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 07:41:23 -0000 Lowell Gilbert wrote: > Kelly Martin writes: > > I just experienced a hard drive failure on one of my > > FreeBSD 7.2 production servers with no backup! ... > First, try copying the entire disk, *without* mounting it. Yep. > Use dd(1) to get a copy of the whole disk. I believe that > "conv=noerror" may be necessary. Much better: use sysutils/ddrescue, which was written specifically to deal with this sort of situation.