from what I can see is that its trying to do importing before the disks have been mapped because /etc/multipath.conf is being read just after zfs failed
Dec 11 23:04:57 aio systemd[1]: Started Mount ZFS filesystems. Dec 11 23:04:57 aio systemd[1]: Starting Mount ZFS filesystems... Dec 11 23:04:57 aio systemd[1]: Reached target ZFS pool import target. Dec 11 23:04:57 aio systemd[1]: Failed to start Import ZFS pools by cache file. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Failed with result 'exit-code'. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Main process exited, code=exited, status=1/FAILURE Dec 11 23:04:57 aio zpool[3622]: a backup source. Dec 11 23:04:57 aio zpool[3622]: Destroy and re-create the pool from Dec 11 23:04:57 aio zpool[3622]: cannot import 'ZFS3WAY': no such pool or dataset Dec 11 23:04:57 aio multipathd[3627]: path checkers start up Dec 11 23:04:57 aio multipathd[3627]: read /etc/multipath.conf Dec 11 23:04:57 aio multipathd[3627]: --------start up-------- Dec 11 23:04:57 aio kernel: rdac: device handler registered Dec 11 23:04:57 aio kernel: emc: device handler registered Dec 11 23:04:57 aio kernel: alua: device handler registered Dec 11 23:04:57 aio systemd[1]: Starting Import ZFS pools by cache file... Dec 11 23:04:57 aio systemd[1]: Started Install ZFS kernel module. Dec 11 23:04:57 aio systemd[1]: Starting Device-Mapper Multipath Device Controller... Dec 11 23:04:57 aio systemd[1]: Starting Install ZFS kernel module... Dec 11 23:04:57 aio systemd[1]: Started udev Wait for Complete Device Initialization. Dec 11 23:04:57 aio kernel: ZFS: Loaded module v0.8.2-1, ZFS pool version 5000, ZFS filesystem version 5 Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Dec 11 23:04:57 aio systemd[1]: Starting LVM event activation on device 9:0... Dec 11 23:04:57 aio systemd[1]: Created slice system-lvm2\x2dpvscan.slice. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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
