All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: David Christensen <dpchrist@holgerdanske.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device.
Date: Wed, 6 Apr 2016 07:38:15 +0200	[thread overview]
Message-ID: <5704A0C7.2040707@gmail.com> (raw)
In-Reply-To: <57048FA2.7090008@holgerdanske.com>

On 04/06/2016 06:25 AM, David Christensen wrote:
> 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?

LUKS device cannot be used with random volume key, so I guess you use
just plain device without header. (So obviously header backup fails because
there is no header.)

You can verify it by checking entry in /etc/crypttab - no luks keyword:

> # grep sda2 /etc/fstab
> /dev/mapper/sda2_crypt                    none                    swap 

or running "cryptsetup status sda2_crypt" over unlocked device
(type is LUKS1 for LUKS devices)

Milan

  reply	other threads:[~2016-04-06  5:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  4:25 [dm-crypt] Debian 7.10 random key swap Device /dev/sda2 is not a valid LUKS device David Christensen
2016-04-06  5:38 ` Milan Broz [this message]
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=5704A0C7.2040707@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=dpchrist@holgerdanske.com \
    /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.