public inbox for dm-crypt@saout.de
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Suddenly unable to access encrypted LUKS partition
Date: Mon, 9 Dec 2019 09:55:55 +0100	[thread overview]
Message-ID: <20191209085554.GA21308@tansi.org> (raw)
In-Reply-To: <VaK8y2BZZIWQoYiWEFfc7lS88rS5LTwnRaSNMdb7sO-4oYqSIzavaSaWwLUOC_jxw3oFbnbksZPNVr_vBeqyiYQb5w4Su_bhRhNuciyGRjY=@protonmail.com>

Hi Andrea,

Do you have a header backup from before this happened?

Regards,
Arno

On Sun, Dec 08, 2019 at 00:41:27 CET, ampica@protonmail.com wrote:
>    Hello,
> 
>    I'm sorry to be the latest user which had a problem with the LUKS
>    header but I'm really desperate to recover my data and contacting this
>    mailing list is my last hope at this point.
> 
>    I use a dual-boot setup on a Lenovo T480 with Windows 10 and Arch Linux
>    on the same SSD drive, Arch is encrypted with LVM on LUKS as described
>    in the Arch Wiki
>    ([1]https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_
>    system#LVM_on_LUKS).
> 
>    To make the story short and simple, since yesterday I've been suddenly
>    unable to decrypt my LVM on LUKS partition and started having "No key
>    available with this passphrase" despite the correctness of the
>    passphrase. Needless to say I made several attempts and checks and made
>    sure the password is correct. If you want to have a look at logs and
>    see all details I simply redirect you to the posts I made on Reddit
>    [2]https://www.reddit.com/r/archlinux/comments/e76se0/unable_to_access_
>    encrypted_luks_partition_wrong/ and on the Arch Linux forum
>    [3]https://bbs.archlinux.org/viewtopic.php?id=251218.
> 
>    As suggested in the FAQ and forums, I tried several things, like using
>    the keyslot check tool and analyzing the hexdump command output (no
>    evident damage from both), tried decrypting the header on another
>    system with the same result and filtered out all other possible
>    problems like keyboard layout, user error and system specific
>    configuration. The only relevant thing to say is that last time I shut
>    down my laptop before facing the issue I updated the linux kernel to
>    5.4.2 and run "mkinitcpio -p linux" but I didn't notice anything
>    unusual respect to other times in the output from command line.
> 
>    I've really no clue on what happened since I didn't do anything
>    accidentally. I'm already on the "Acceptance" phase but I still have
>    that 0.01% hope left to recover my system, so any help or suggestion is
>    really much appreciated. If you need more information, please let me
>    know (I've no problem sharing my LUKS header and passphrase for a
>    further analysis). Thank you very much in advance for everything.
> 
>    Best Regards,
> 
>    Andrea Piccione
> 
> References
> 
>    1. https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#LVM_on_LUKS
>    2. https://www.reddit.com/r/archlinux/comments/e76se0/unable_to_access_encrypted_luks_partition_wrong/
>    3. https://bbs.archlinux.org/viewtopic.php?id=251218

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt


-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

      parent reply	other threads:[~2019-12-09  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 23:41 [dm-crypt] Suddenly unable to access encrypted LUKS partition ampica
2019-12-08 19:54 ` Chris Murphy
2019-12-10 16:09   ` Carl-Daniel Hailfinger
2019-12-09  8:55 ` Arno Wagner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191209085554.GA21308@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox