From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 25 Feb 2016 17:24:01 +0100 (CET) References: <20160225160849.21765320@othir.localdomain> From: Ondrej Kozina Message-ID: <56CF2938.2010102@redhat.com> Date: Thu, 25 Feb 2016 17:18:00 +0100 MIME-Version: 1.0 In-Reply-To: <20160225160849.21765320@othir.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] help List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Felix Wagner , dm-crypt@saout.de Hi Felix, don't loose all hope yet! On 02/25/2016 04:08 PM, Felix Wagner wrote: > So i thought well It didn't work so lets try again: > > cryptsetup-reencrypt -v -c > aes-xts-plain64 /dev/disk/by-uuid/2ea1bb9e-a4a0-48c8-bc67-a694fa6c8cf7 > Reencryption will change: volume key, set cipher to aes-xts-plain64. > Enter passphrase for key slot 0: > Key slot 0 unlocked. > LUKS header > backup of device /dev/disk/by-uuid/2ea1bb9e-a4a0-48c8-bc67-a694fa6c8cf7 > created. ^^^^^^^^ First of all, you actually may have the LUKS header backup! The cryptsetup-reencrypt created one for you automatically. Look for LUKS-foobar.org file in the directory where you initiated the cryptsetup-reencrypt. If... (well rather big fat _IF_ because this is really important) the reencryption didn't write any data yet you may restore your LUKS header using the .org backup created by cryptsetup-reencrypt. But again _don't_ do the header recovery unless you're 100% sure that reencryption didn't write (aka already reencrypted) any ciphertext sectors! So, what's in your reencrypt log file (look for LUKS-foobar.log in same directory where is also the header backup)? Regards Ondra