From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sat, 5 Nov 2016 11:16:47 +0100 (CET) Received: from localhost ([88.90.242.143]) by mrelayeu.kundenserver.de (mreue004) with ESMTPSA (Nemesis) id 0M5tBF-1cmoJr2zjF-00xvoo for ; Sat, 05 Nov 2016 11:16:46 +0100 Date: Sat, 5 Nov 2016 11:16:45 +0100 From: Heinz Diehl Message-ID: <20161105101645.GA2907@fritha.org> References: <20161103190406.GA12951@yeono.kjorling.se> <20161104113255.GA7254@tansi.org> <20161104200841.GG12951@yeono.kjorling.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20161104200841.GG12951@yeono.kjorling.se> Subject: Re: [dm-crypt] Missing keyslot or broken header or still some hope? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 04.11.2016, Michael Kj=F6rling wrote:=20 > I _strongly_ recommend ddrescue over dd; ddrescue is far better suited > for this use case. It also gives you a nice progress indication while > it is working. FWIW: You can also get dd to show transfer statistics by using the "status=3Dprogress" flag.