All of lore.kernel.org
 help / color / mirror / Atom feed
* [dm-crypt] cryptsetup: WARNING: Target has an invalid header
@ 2018-11-29  9:43 Carabus
  2018-11-30  9:49 ` Ondrej Kozina
  2018-11-30 11:13 ` Guilhem Moulin
  0 siblings, 2 replies; 4+ messages in thread
From: Carabus @ 2018-11-29  9:43 UTC (permalink / raw)
  To: dm-crypt

Hello.

i`m trying to mount luks volume with detached header on boot (debian 
testing), exactly the same method, as i do on very old system, which is 
work fine before.

i use external usb flash with two partition, one for /boot 
(TYPE="ext3"), and another one for 10 mb partition for  luks header 
(TYPE="crypto_LUKS")

in my crypttab i set

buster /dev/disk/by-id/xxxx none luks,header=/dev/disk/by-uuid/xxxx

where header have exact uuid of second partition of usb flash (crypto_LUKS)

but cryptsetup say, i`m do it wrong

cryptsetup: WARNING: Target buster has an invalid header
     /dev/disk/by-uuid/xxxx

but this header work fine when open with this command:

cryptsetup open /dev/disk/by-id/xxxx --header /dev/disk/by-uuid/xxxx buster

would you please give me examples of crypttab `header=` option which 
will work?

in case of header detached to external usb flash partition, with own 
uuid, type crypto_LUKS,

and in case of header is image file, which have not uuid, on `ext` file 
system on /boot/

?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] cryptsetup: WARNING: Target has an invalid header
  2018-11-29  9:43 [dm-crypt] cryptsetup: WARNING: Target has an invalid header Carabus
@ 2018-11-30  9:49 ` Ondrej Kozina
  2018-11-30 11:13 ` Guilhem Moulin
  1 sibling, 0 replies; 4+ messages in thread
From: Ondrej Kozina @ 2018-11-30  9:49 UTC (permalink / raw)
  To: Carabus, dm-crypt

On 11/29/18 10:43 AM, Carabus wrote:

Hi,

> 
> buster /dev/disk/by-id/xxxx none luks,header=/dev/disk/by-uuid/xxxx

Is it just simplified example or do you really pass identical string to 
both header= and data device parameters?

> 
> where header have exact uuid of second partition of usb flash (crypto_LUKS)
> 
> but cryptsetup say, i`m do it wrong
> 
> cryptsetup: WARNING: Target buster has an invalid header
>       /dev/disk/by-uuid/xxxx

I can't find this message anywhere in cryptsetup source code. What 
cryptsetup version did you use? (But I guess this error message 
originates in systemd-cryptsetup binary since it's systemd-cryptsetup 
what unlocks devices put in crypttab if you run distro with systemd)

> 
> but this header work fine when open with this command:
> 
> cryptsetup open /dev/disk/by-id/xxxx --header /dev/disk/by-uuid/xxxx buster

In that case it's probably bug in systemd crypttab handling.

> 
> would you please give me examples of crypttab `header=` option which
> will work?

I don't think you did anything wrong. From crypttab documentation you 
should be able to pass same value in header= option of crypttab line as 
you would do with cryptsetup --header option.

Regards
O.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] cryptsetup: WARNING: Target has an invalid header
  2018-11-29  9:43 [dm-crypt] cryptsetup: WARNING: Target has an invalid header Carabus
  2018-11-30  9:49 ` Ondrej Kozina
@ 2018-11-30 11:13 ` Guilhem Moulin
  2018-11-30 11:55   ` Carabus Savvey
  1 sibling, 1 reply; 4+ messages in thread
From: Guilhem Moulin @ 2018-11-30 11:13 UTC (permalink / raw)
  To: Carabus; +Cc: dm-crypt

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

Hi,

On Thu, 29 Nov 2018 at 12:43:04 +0300, Carabus wrote:
> but cryptsetup say, i`m do it wrong
> 
> cryptsetup: WARNING: Target buster has an invalid header
>     /dev/disk/by-uuid/xxxx

That message doesn't come from cryptsetup upstream, but from the
initramfs hook & boot scripts shipped in Debian's ‘cryptsetup-initramfs’
package.  Between 2:2.0.3-2 and 2:2.0.5-1 the script choked when the
‘header’ value wasn't a regular file.  The regression was fixed in
2:2.0.5-2, which transitioned to testing (aka Buster) earlier today :-)

Cheers,
-- 
Guilhem.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] cryptsetup: WARNING: Target has an invalid header
  2018-11-30 11:13 ` Guilhem Moulin
@ 2018-11-30 11:55   ` Carabus Savvey
  0 siblings, 0 replies; 4+ messages in thread
From: Carabus Savvey @ 2018-11-30 11:55 UTC (permalink / raw)
  To: dm-crypt

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

hi, thanks for that info, now i see the incident is settled.
i will try to boot debian testing from luks with detached header next time.
best regards.


пт, 30 нояб. 2018 г., 14:13 Guilhem Moulin guilhem@fripost.org:

> Hi,
>
> On Thu, 29 Nov 2018 at 12:43:04 +0300, Carabus wrote:
> > but cryptsetup say, i`m do it wrong
> >
> > cryptsetup: WARNING: Target buster has an invalid header
> >     /dev/disk/by-uuid/xxxx
>
> That message doesn't come from cryptsetup upstream, but from the
> initramfs hook & boot scripts shipped in Debian's ‘cryptsetup-initramfs’
> package.  Between 2:2.0.3-2 and 2:2.0.5-1 the script choked when the
> ‘header’ value wasn't a regular file.  The regression was fixed in
> 2:2.0.5-2, which transitioned to testing (aka Buster) earlier today :-)
>
> Cheers,
> --
> Guilhem.
>

[-- Attachment #2: Type: text/html, Size: 1212 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-11-30 11:55 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-11-29  9:43 [dm-crypt] cryptsetup: WARNING: Target has an invalid header Carabus
2018-11-30  9:49 ` Ondrej Kozina
2018-11-30 11:13 ` Guilhem Moulin
2018-11-30 11:55   ` Carabus Savvey

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.