From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 6 Jan 2017 16:58:06 +0100 (CET) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cPWty-0001v5-O9 for dm-crypt@saout.de; Fri, 06 Jan 2017 16:57:58 +0100 From: Robert Nichols Date: Fri, 6 Jan 2017 09:57:49 -0600 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Subject: Re: [dm-crypt] Decrypting a drive; says a correct password is "incorrect" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 01/04/2017 08:34 PM, K Mmmm wrote: > Using a platter switch, I was able to copy most of the data to a new > hard disk. Fortunately, *there _does_ appear to be a valid version > of /_a_ /LUKS header still intact.* However, the password I was > using isn't working. Did "most of the data" include the entire ~2MB LUKS header? You need at least the first 256KB to get all the stripes of the first keyslot. If that data is not all bit-for-bit perfect, the master key cannot be recovered and your data cannot be decrypted. You can look at section 4.2 of the cryptsetup FAQ at for information on how to build and run a keyslot checker that can test for obvious damage to the keyslots ("obvious" meaning "data with low entropy appearing in places that should appear random"). > I think the partition layout might be relevant, as there is only a 2 > space between the EXT and Linux partitions. Your partition layout is fine. Logical partitions (numbers 5 and higher) exist within the extended partition. All that is needed is space for the 1-sector extended partition header before the start of partition 5. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.