All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Farina <sidhayn@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] unable to mount my encrypted drive
Date: Mon, 02 Dec 2013 11:22:52 -0500	[thread overview]
Message-ID: <529CB3DC.1040304@gmail.com> (raw)

All of a sudden, I'm unable to mount my encrypted drive anymore.  I
don't really reboot a lot, so I'm sure a lot has changed since my last
luksOpen including kmod version and cryptsetup being updated from 1.4.3
to 1.6.2.

I typically decrypt with something like this:

zero@ozzie ~ % gpg --batch --decrypt /run/usbstick/slicehdd.gpg 2>
/dev/null | sudo cryptsetup luksOpen /dev/sdb1 slice -d -

But now all I'm getting is this:

No key available with this passphrase.


here is some additional information:

zero@ozzie ~ % sudo cryptsetup luksDump /dev/sdb1
LUKS header information for /dev/sdb1

Version:       	1
Cipher name:   	aes
Cipher mode:   	xts-essiv:wp256
Hash spec:     	sha1
Payload offset:	4096
MK bits:       	512
MK digest:     	removed
MK salt:       	removed
MK iterations: 	removed
UUID:          	removed

Key Slot 0: ENABLED
	Iterations:         	removed
	Salt:               	removed
	Key material offset:	removed
	AF stripes:            	removed
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED


Please let me know what else is needed for troubleshooting.

Thanks for the support, and the great software.  Been using cryptsetup
for years and loving it.

-Zero

             reply	other threads:[~2013-12-02 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 16:22 Rick Farina [this message]
2013-12-02 16:47 ` [dm-crypt] unable to mount my encrypted drive Ralf Ramsauer
2013-12-02 16:53   ` Ralf Ramsauer
2013-12-02 20:14     ` Claudio Moretti
2013-12-03 12:21       ` Claudio Moretti

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=529CB3DC.1040304@gmail.com \
    --to=sidhayn@gmail.com \
    --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.