I've tested and validated this on the scenarios mentioned in the bug description. The summary is below: - ZFS only setup ✅ - LUKS only ✅ - ZFS on LUKS ✅
The first two scenarios are easily accessible from the default Ubuntu Desktop Installer for Focal. For ZFS on LUKS, I followed the upstream ZFS documentation [0] and deboostrapped focal on top of the disks from the live installer. I found no regressions, and the warning messages about resolving the ZFS devices are gone. Below are full test logs for verification. [0] https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubuntu/Ubuntu%2020.04%20Root%20on%20ZFS.html -- *** ZFS only halves@ubuntu20:~$ apt policy cryptsetup cryptsetup: Installed: 2:2.2.2-3ubuntu2.5 Candidate: 2:2.2.2-3ubuntu2.5 Version table: *** 2:2.2.2-3ubuntu2.5 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:2.2.2-3ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2:2.2.2-3ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages halves@ubuntu20:~$ zpool status pool: bpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 8cda55e1-06 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 8cda55e1-07 ONLINE 0 0 0 errors: No known data errors halves@ubuntu20:~$ lsblk /dev/vda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 25G 0 disk ├─vda1 252:1 0 512M 0 part /boot/efi ├─vda2 252:2 0 1K 0 part ├─vda5 252:5 0 1.1G 0 part [SWAP] ├─vda6 252:6 0 1.2G 0 part └─vda7 252:7 0 22.1G 0 part *** LUKS ubuntu@ubuntu20:~$ apt policy cryptsetup cryptsetup: Installed: 2:2.2.2-3ubuntu2.5 Candidate: 2:2.2.2-3ubuntu2.5 Version table: *** 2:2.2.2-3ubuntu2.5 500 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:2.2.2-3ubuntu2.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2:2.2.2-3ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@ubuntu20:~$ lsblk /dev/vda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 25G 0 disk ├─vda1 252:1 0 512M 0 part /boot/efi ├─vda2 252:2 0 1K 0 part ├─vda5 252:5 0 1.4G 0 part /boot └─vda6 252:6 0 23.1G 0 part └─vda6_crypt 253:0 0 23.1G 0 crypt ├─vgubuntu-root 253:1 0 22G 0 lvm / └─vgubuntu-swap_1 253:2 0 976M 0 lvm [SWAP] root@ubuntu20:/home/ubuntu# update-initramfs -c -k all update-initramfs: Generating /boot/initrd.img-5.15.0-136-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-138-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-67-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. root@ubuntu20:/home/ubuntu# *** ZFS on LUKS root@ubuntu20:/# lsblk /dev/vda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:0 0 25G 0 disk ├─vda1 252:1 0 512M 0 part /boot/efi ├─vda2 252:2 0 500M 0 part ├─vda3 252:3 0 2G 0 part └─vda4 252:4 0 22G 0 part └─luks1 253:0 0 22G 0 crypt root@ubuntu20:/# zpool status -P rpool pool: rpool state: ONLINE status: Mismatch between pool hostid and system hostid on imported pool. This pool was previously imported into a system with a different hostid, and then was verbatim imported into this system. action: Export this pool on all systems on which it is imported. Then import it to correct the mismatch. see: http://zfsonlinux.org/msg/ZFS-8000-EY scan: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 /dev/mapper/luks1 ONLINE 0 0 0 errors: No known data errors root@ubuntu20:/# update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-214-generic root@ubuntu20:/# apt policy cryptsetup cryptsetup: Installed: 2:2.2.2-3ubuntu2.5 Candidate: 2:2.2.2-3ubuntu2.5 Version table: *** 2:2.2.2-3ubuntu2.5 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:2.2.2-3ubuntu2.4 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2:2.2.2-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu20:/# ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830110 Title: patch for finding zfs, solves: cryptsetup: WARNING: Couldn't determine root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1830110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
