built-in configuration file prevents booting with command line options

Olaf Hering <[email protected]> Mon, 8 Jul 2024 13:40:06 +0200

Newsgroups	org.kernel.vger.initramfs
Message-ID	<[email protected]>

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

signature.asc (application/pgp-signature, 833 B)