From: Guilhem Moulin <guilhem@fripost.org>
To: procmem <procmem@riseup.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
Date: Thu, 13 Sep 2018 18:02:42 +0200 [thread overview]
Message-ID: <20180913160241.GA30786@localhost.localdomain> (raw)
In-Reply-To: <1f4ca0d5-0166-dbbb-e8d8-dbdb302ccc27@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Thu, 13 Sep 2018 at 14:22:00 +0000, procmem wrote:
> Ondrej Kozina:
>> Well, this sounds like a bug. Could you please provide us with debug
>> output for failing command trying to luksConvertKey that particular
>> keyslot?
>
> Sure thing but I don't know how to access initramfs command history.
> Unlike a booted-up environment there is no opportunity to scroll and
> select entire output for saving.
You can redirect the output to a file under /run/initramfs. /run is
moved to the rootfs at init-bottom stage, shortly before the execution
is turned over to the `init` binary, so content added at early boot
stage will also be available later during the boot process.
(Again, assuming your initramfs is comes from initramfs-tools, which is
the default in Debian — and I guess its derivatives.)
--
Guilhem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-13 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:09 [dm-crypt] Troubleshooting: Header Conversion to argon2id procmem
2018-09-11 17:20 ` Ondrej Kozina
2018-09-11 17:53 ` procmem
2018-09-12 4:16 ` procmem
2018-09-12 4:44 ` Milan Broz
2018-09-12 15:21 ` procmem
2018-09-12 15:52 ` Guilhem Moulin
2018-09-13 0:47 ` procmem
2018-09-13 1:53 ` Arno Wagner
2018-09-13 1:58 ` Guilhem Moulin
2018-09-13 14:13 ` procmem
2018-09-13 15:00 ` Ondrej Kozina
2018-09-13 14:22 ` procmem
2018-09-13 16:02 ` Guilhem Moulin [this message]
2018-09-14 0:21 ` procmem
2018-09-14 7:10 ` Ondrej Kozina
2018-09-14 8:20 ` Ondrej Kozina
2018-09-15 1:33 ` procmem
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=20180913160241.GA30786@localhost.localdomain \
--to=guilhem@fripost.org \
--cc=dm-crypt@saout.de \
--cc=procmem@riseup.net \
/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