The problem is further complicated by the notion of questing -> resolute
upgrades of a ZFS encrypted system. Such a system will fail on first
boot (post upgrade).
I've been able to address this for new installs by creating a dracut
drop-in file like so
add_device+=" /dev/zvol/rpool/keystore "
I see two options ahead:
1. patch curtin + u-r-u
Curtin can add a drop-in file like the above to the target system, which I have
tested and confirmed works.
However, this doesn't fix devices upgrading from questing, so a similar fix
will be needed in the release upgrader. It should be a straightforward code
change in u-r-r as the expected path to check for this problem on the questing
system is very fixed - /dev/zvol/rpool/keystore.
2. patch dracut to consider devices under /dev/zvol
`find /dev/zvol -type l` should do it for enumerating the additionial devices
to consider.
** Changed in: dracut (Ubuntu Resolute)
Status: Invalid => New
** Description changed:
With debian/patches/ubuntu/4001-dracut-Open-and-mount-luks-
keystore.patch applied, systemd-cryptsetup is a requirement.
Proceeding without goes poorly.
+
+ Further, dracut needs to know about the /dev/zvol/... devices, which it
+ does not today. This could be resolved with dracut drop-in files, or
+ maybe we patch dracut to also consider /dev/zvol devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2140415
Title:
dracut needs to see crypto_LUKS devices in order to consider including
systemd-cryptsetup in the initrd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/2140415/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
