btw, there's another bug in plymouth package that breaks root on encrypted zfs in some cases, the patch is there but it's waiting for review: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1810154
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1852406 Title: Double-escape in initramfs DECRYPT_CMD Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Eoan: In Progress Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification, Eoan == initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line 414: DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'" This is OK when the line is executed by shell, such as in line 430 or 436, but when plymouth is used it results in plymouth executing "zfs load-key 'rpool'" - and zfs is unable to find pool called "'rpool'". If I understand https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html correctly zfs pool name is always 'shell-friendly', so removing the quotation marks would be a proper fix for that. == Fix == One line fix as attached in https://bugs.launchpad.net/ubuntu/+source /zfs-linux/+bug/1852406/comments/1 == Test == Boot with encrypted data set with plymouth. Without the fix zfs is unable to find the root encrypted pool. With the fix this works. == Regression Potential == This just affects the encrypted dataset that holds key for root dataset; currently this is causing issues because of the bug, so the risk of the fix outweighs the current situation where this is currently broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
