From: David Christensen <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
Date: Tue, 5 Apr 2016 21:25:06 -0700 [thread overview]
Message-ID: <57048FA2.7090008@holgerdanske.com> (raw)
dm-crypt:
I have a Debian 7.10 (Wheezy) computer with a random-key swap device.
The disk and swap are working.
When I try to backup the LUKS header:
# cryptsetup luksHeaderBackup /dev/sda2 --header-backup-file
luksheaderbackup-sda2.bin
Device /dev/sda2 is not a valid LUKS device.
Is this expected/ normal behavior for a dm-crypt/ LUKS random-key swap
partition?
David
# cat /etc/debian_version
7.10
# dpkg-query -l cryptsetup
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii cryptsetup 2:1.4.3-4 amd64 disk encryption support -
startup
# grep sda2 /etc/crypttab
sda2_crypt /dev/sda2 /dev/urandom
cipher=aes-xts-plain64,size=256,swap
# grep sda2 /etc/fstab
/dev/mapper/sda2_crypt none swap
sw 0 0
# swapon -s
Filename Type Size Used Priority
/dev/mapper/sda2_crypt partition 488444 0 -1
# cryptsetup -v isLuks /dev/sda2
Device /dev/sda2 is not a valid LUKS device.
Command failed with code 22: Device /dev/sda2 is not a valid LUKS device.
# cryptsetup -v luksDump /dev/sda2
Device /dev/sda2 is not a valid LUKS device.
Command failed with code 22: Device /dev/sda2 is not a valid LUKS device.
next reply other threads:[~2016-04-06 4:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 4:25 David Christensen [this message]
2016-04-06 5:38 ` [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device Milan Broz
2016-04-06 5:59 ` David Christensen
2016-04-06 6:37 ` Milan Broz
2016-04-06 10:55 ` Michael Kjörling
2016-04-06 19:35 ` David Christensen
2016-04-06 20:26 ` Sven Eschenberg
2016-04-06 23:06 ` David Christensen
2016-04-07 9:39 ` Arno Wagner
2016-04-07 9:46 ` Arno Wagner
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=57048FA2.7090008@holgerdanske.com \
--to=dpchrist@holgerdanske.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.