From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <guilhem@fripost.org>
Received: from outgoing.fripost.org (giraff.fripost.org
 [IPv6:2a00:1c20:4089:126c:300f:e2a1:9840:5351])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 13 Sep 2018 18:02:46 +0200 (CEST)
Date: Thu, 13 Sep 2018 18:02:42 +0200
From: Guilhem Moulin <guilhem@fripost.org>
Message-ID: <20180913160241.GA30786@localhost.localdomain>
References: <0a634f10-a4fe-54e3-b6ad-edd3f7682ec3@redhat.com>
 <05d42a4b-7439-0f5a-21b0-d79d1195b07f@riseup.net>
 <cdad2fc3-5013-0412-2634-3a11fe04a3bc@gmail.com>
 <48f41120-27ae-cef3-8bb0-482eb164d468@riseup.net>
 <20180912155201.GA31331@localhost.localdomain>
 <8c5025a3-efdd-02a7-d6b8-4d14dcd0beb6@riseup.net>
 <20180913015846.GA20220@localhost.localdomain>
 <4d010d4e-de8c-e16e-8728-cb227f563c66@riseup.net>
 <324ac016-507c-714f-5a45-894b0a87e8f7@redhat.com>
 <1f4ca0d5-0166-dbbb-e8d8-dbdb302ccc27@riseup.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi"
Content-Disposition: inline
In-Reply-To: <1f4ca0d5-0166-dbbb-e8d8-dbdb302ccc27@riseup.net>
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: procmem <procmem@riseup.net>
Cc: dm-crypt@saout.de


--6c2NcOVqGQ03X4Wi
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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?
>=20
> 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 =E2=80=94 and I guess its derivatives.)

--=20
Guilhem.

--6c2NcOVqGQ03X4Wi
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAluaiiAACgkQ05pJnDwh
pVJbCQ//bldkfQLlhFRF48hpRIjW554hj9LCpYJwyflfDBlAvTifEE2aVvdS6Rlh
GEfIWP7O2TqbJoXCzFpttI79aJrRpOpytabWq/gojRzmad18stRoHD1PcMRwZ8Dy
t3Q95Q0VXJ4W2kMyS46Lh0mKxyzD1L9Uxv6rwkoq+kbpcja9ORNvbdgQGCyIfVqj
pTgTKnKh/l46C4wpH3rDJ+G4BFFxwebBZki4tUgDj0kGJmiYVls9YF5s7kDYW2WL
eQgdSyDw3WGOaLDV4T5v3Cc1zMkKtdaOYPBb5Apm9K0dCoTGzngUhv9Ngl1HmQuS
Fxvkq2PZZOAEVHSe6hMnYQm0UNaIjqCV+VH2V1Og5xX5hj2LULRogqBhimS61jaz
N8cT9QneFeGcx1GZm0lC+Ivp43oRlIXW+yzIO9sQU7QXg3kvhwlo9+Wn1kKBr6RG
shWOxyozUvjO3a9V2qr6pHYpPLo02jua8T35iYPkr/iTfqWr0hklKzXZwiPi4Miu
oOsE9613BeMVHeDZvTGZu/oQZnmFDo6KVF0A6P/j4zYDfGT1ZUkf75A1X51fGgMi
WB9YbnfTY3fYYRyJGeZswqvr0blaeQt7GBIYhUq5WNDL337wZY2o3jTW7Twx1HfL
KjNdJ1bRHbUjlUDZYePdnLTSpGPuzDbFUGvlxf08Ec6ltkcbS88=
=3OjH
-----END PGP SIGNATURE-----

--6c2NcOVqGQ03X4Wi--