zfs not correctly imported at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zfs-linux (Ubuntu) |
New
|
Undecided
|
Andrea Righi |
Bug Description
On a fresh and up-to-date Ubuntu 20.04 amd64 installation I configured two encrypted partitions on the same hdd. On these I created a stripped zpool. After login I can import and mount the pool without problems, but the at-boot import fails after the first partitions is available and never tried again.
zpool version:
zfs-0.8.
zfs-kmod-
uname -a:
Linux hostname 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
systemd --version
systemd 245 (245.4-4ubuntu3.2)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-
Relevant logs:
Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write Protect is off
Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 17 07:12:25 hostname kernel: sdb: sdb1 sdb2
Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: zfs-import-
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.
Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-
Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for sdb1_crypt...
Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for sdb2_crypt...
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.
Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-
Aug 17 07:12:32 hostname systemd[1]: Finished Cryptography Setup for sdb2_crypt.
Aug 17 07:12:32 hostname systemd[1]: Reached target Block Device Preparation for /dev/mapper/
Aug 17 07:12:32 hostname zpool[1887]: cannot import 'sdb': no such pool or dataset
Aug 17 07:12:32 hostname zpool[1887]: Destroy and re-create the pool from
Aug 17 07:12:32 hostname zpool[1887]: a backup source.
Aug 17 07:12:32 hostname systemd[1]: zfs-import-
Aug 17 07:12:32 hostname systemd[1]: zfs-import-
Aug 17 07:12:34 hostname systemd[1]: Finished Cryptography Setup for sdb1_crypt.
Aug 17 07:12:34 hostname systemd[1]: Reached target Block Device Preparation for /dev/mapper/
affects: | systemd (Ubuntu) → zsys (Ubuntu) |
Please run apport-collect to attach logs so that we can debug your setting.
@baling: why subscribing zsys to this bu? There is no mention of zsys being used here, it seems directly a manual zfs setup.