All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available for this passphrase
Date: Sat, 8 Sep 2012 15:35:25 +0200	[thread overview]
Message-ID: <20120908133525.GC23589@tansi.org> (raw)
In-Reply-To: <0970e8b6f714123c66b14c5bb1b79810@tenak.net>

Hi,

seems you have damaged the keyslot are in some way. 
(See FAQ Item 6.12) This is where a header-backup 
(See FAQ item 6.1ff) comes in, typically as the only way 
to recover. Other things you can try: If you have multiple 
passphrases, try them all.

From what you describe, I do not see how you could have
done damage. Have you maybe used the "encrypted partition"
feature of Ubuntu? It has a known bug (see FAQ item 1.3) 
that makes it look like it maps LUKS partitions, but it 
really re-creates them, destroyuing the old data permanently.

While the update is suspicuous, you being able to boot it
once (I assume from war or cold reset) and the test with the
other system should rule it out as root cause.

Arno

On Sat, Sep 08, 2012 at 10:03:42AM +0100, Marcos wrote:
> Hi,
> 
> I have a encrypted fs on my Archlinux laptop that I cannot unlock
> anymore:
> 
> # cryptsetup luksOpen /dev/sda2 vgroup
> No key available for this passphrase
> 
> I updated yesterday my system and booted once successfully into it.
> After that I used the machine and created a live Ubuntu USB for a
> friend and tested it booting into it, live mode. I shutted it down
> and after that I'm unable to unlock the key of my encrypted
> partition.
> 
> I've done the following so far:
> 
>  * tested to write the passphrase using a US-layout keyboard to
> discard keymap problems
>  * booted from a liveUSB and try to luksOpen it from there, with no
> success (using the right keymap, es_ES in my case)
>  * plugged my harddisk via USB to another computer running Debian
> and tried to unlock it from there, no success neither.
> 
> AFAICT the luksHeader is OK:
> 
> # cryptsetup -v isLuks /dev/sda2
> Command successful.
> 
> I installed the system few years ago following this guide:
> http://www.pindarsign.de/webblog/?p=767 in case you want no know how
> luks was setup.
> 
> Can any one give some hints on what to do now? Do you need more
> information about it?
> 
> My last backup is from some time ago and I'm really worried about my
> data now.
> 
> Thanks in advance,
> -- 
> Marcos
> http://tenak.net/
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
> 

-- 
Arno Wagner,    Dr. sc. techn., Dipl. Inform.,   Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty 
are stupid, and those with any imagination and understanding are filled 
with doubt and indecision. -- Bertrand Russell 

  reply	other threads:[~2012-09-08 13:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  9:03 [dm-crypt] No key available for this passphrase Marcos
2012-09-08 13:35 ` Arno Wagner [this message]
2012-09-08 18:47   ` Marcos
2012-09-08 20:02     ` Arno Wagner
2012-09-08 20:51       ` Marcos
2012-09-08 22:47         ` Arno Wagner
2012-09-09 12:53           ` Marcos
2012-09-09 13:49             ` Arno Wagner
2012-09-09 14:06               ` Marcos
2012-09-08 23:16         ` [dm-crypt] Re2: " Arno Wagner
2012-09-09 12:58           ` Marcos
2012-09-08 22:45       ` [dm-crypt] " Matthias Schniedermeyer
2012-09-09  8:45         ` Milan Broz
2012-09-09 13:42           ` Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2013-01-25 17:53 Sebastian
2013-01-25 19:40 ` Arno Wagner
2013-01-25 19:57   ` Sebastian
2013-01-25 21:50     ` Arno Wagner
2013-01-26 10:15       ` Sebastian
2013-01-26 17:41         ` Arno Wagner
2013-01-27  8:42           ` Sebastian
2013-01-28 23:46             ` .. ink ..
2013-01-29  2:39               ` Arno Wagner
2013-01-31 13:43                 ` Sebastian
2013-01-31 17:48                   ` .. ink ..

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=20120908133525.GC23589@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.