From owner-freebsd-questions@FreeBSD.ORG Mon Jul 5 14:10:09 2010 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 295601065673 for ; Mon, 5 Jul 2010 14:10:09 +0000 (UTC) (envelope-from kuku@kukulies.org) Received: from werkwelt.de (post.werkwelt.de [91.194.85.74]) by mx1.freebsd.org (Postfix) with ESMTP id BC9188FC0A for ; Mon, 5 Jul 2010 14:10:08 +0000 (UTC) Received: from [87.79.34.228] (account kuku@kukulies.org HELO [172.27.4.215]) by werkwelt.de (CommuniGate Pro SMTP 5.0.13) with ESMTPSA id 6976413; Mon, 05 Jul 2010 16:09:41 +0200 Message-ID: <4C31E793.3040000@kukulies.org> Date: Mon, 05 Jul 2010 16:09:23 +0200 From: Christoph Kukulies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Polytropon , "freebsd-questions@freebsd.org" References: <4B434D52.3030301@kukulies.org> <20100106023007.b3a19517.freebsd@edvax.de> In-Reply-To: <20100106023007.b3a19517.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: copying a disk with ignoring errors 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: Mon, 05 Jul 2010 14:10:09 -0000 Am 06.01.2010 02:30, schrieb Polytropon: > On Tue, 05 Jan 2010 15:31:46 +0100, Christoph Kukulies wrote: > >> It copies a disk sector by sector to a file (kind of dd), but ignores >> errors, it just skips sectors it couldn't read (after a couple >> of retries). The result was, that one had a - albeit - worm-eaten - >> image of the disk allowing to access the filesystem >> and getting to the important files with a little luck these not being >> amongst the corrupted data. >> >> Anyone knowing what this little tool was named? Something like diskcopy, >> devcopy, I forgot. >> > > From my "list" of recovery-related tools: > dd_rescue > ddrescue > fetch -rR > recoverdisk > > I'm quite sure it was one of them. > > Allow me to followup on this a bit vintaged thread but it's an all over again happening issue. Some student lost some important data due to disk failure. I tried PHKs' recoverdisk with recoverdisk -b 1024000 /dev/ad2 ad2.dmp and it went off quite promising just few dma read timeouts and when I was at 7% of recovery it suddenly says: ad2: FAILURE - device detached. 1558528000 1024000 failed (device not configured) # Hmm. How can I avoid that the device gets detached? -- Christoph