From: Olaf Hering <olaf@aepfle.de>
To: initramfs@vger.kernel.org
Subject: built-in configuration file prevents booting with command line options
Date: Mon, 8 Jul 2024 13:40:06 +0200 [thread overview]
Message-ID: <20240708134006.05da2f2d.olaf@aepfle.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
dracut in Leap 15.5 puts /etc/cmdline.d/90crypt.conf into initrd.
This file contains "rd.luks.uuid=luks-${old_uuid}".
If the disk dies, and the backup is populated on the replacement disk,
the UUID of the LUKS container does obviously change.
I was able to boot the existing old initrd with "rd.luks.crypttab=0
rd.luks.key=/some_path rd.luks.uuid=${new_uuid}", but this was not enough.
Booting with "rd.debug" revealed that "${old_uuid}" was still expected
to be present. A search in the extracted initrd revealed that
"rd.hostonly=0" removes "/etc/cmdline.d/*.conf". But using that option
disables also all knobs specified on the kernel command line.
Is booting an "arbitrary" existing initrd with "rd.hostonly=0",
and specifying every required detail of the root filesystem on
the kernel command line, supposed to work?
Did I maybe miss yet another required knob?
This is the full list of used kernel cmdline options:
log_buf_len=16M
mitigations=off
net.ifnames=0
nosgx
panic=9
plymouth.enable=0
rd.fstab=0
rd.luks.allow-discards
rd.luks.crypttab=0
rd.luks.key=/.root.key
rd.luks.uuid=${new_uuid}
rd.lvm.conf=0
rd.lvm.lv=${vg}/${lv}
rd.lvm.vg=${vg}
rd.timeout=11
resume=/dev/disk/by-label/${label_swap}
root=/dev/disk/by-label/${label_btrfs}
rootflags=subvol=/${subvolume},noatime
Thanks,
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-07-08 11:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240708134006.05da2f2d.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=initramfs@vger.kernel.org \
/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