From: Arno Wagner <wagner@arnowagner.info>
To: Darek Hisc <darek.hisc@aleeas.com>
Cc: cryptsetup@lists.linux.dev
Subject: Re: Problem after detaching the header
Date: Fri, 30 Jun 2023 12:54:19 +0200 [thread overview]
Message-ID: <20230630105419.GB3092@tansi.org> (raw)
In-Reply-To: <168811588839.6.11593174509180454664.147320636@aleeas.com>
That would be a question for your distribution.
On Fri, Jun 30, 2023 at 11:04:34 CEST, Darek Hisc wrote:
>
> > Looks like the initrd cannot deal with detached headers.
> Please note that until the luksErase operation everything is fine and the header is read from the detached location (since the original slots no longer exist)
>
> > Can you manually map the LUKS container from the
> > initrd console? If not, waht errot do you get?
> I'm sorry but I don't know how to do it :(
> Can you provide the command to type in the console initramfs?
>
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2023-06-30 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 19:17 Problem after detaching the header Darek Hisc
2023-06-30 2:50 ` Arno Wagner
2023-06-30 9:04 ` Darek Hisc
2023-06-30 10:54 ` Arno Wagner [this message]
2023-07-01 7:50 ` Milan Broz
2023-07-01 17:06 ` Darek Hisc
2023-07-01 21:00 ` Milan Broz
2023-07-04 16:58 ` Darek Hisc
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=20230630105419.GB3092@tansi.org \
--to=wagner@arnowagner.info \
--cc=arno@wagner.name \
--cc=cryptsetup@lists.linux.dev \
--cc=darek.hisc@aleeas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox