or something, the pools don't seem to be ready for import?

maalis 11 12:31:59 bryant systemd[1]: Starting Import ZFS pools by cache file...
-- Subject: A start job for unit zfs-import-cache.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit zfs-import-cache.service has begun execution.
-- 
-- The job identifier is 15.
maalis 11 12:31:59 bryant zpool[2141]: no pools available to import
maalis 11 12:31:59 bryant systemd[1]: Started Import ZFS pools by cache file.
-- Subject: A start job for unit zfs-import-cache.service has finished 
successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit zfs-import-cache.service has finished successfully.
-- 
-- The job identifier is 15.
maalis 11 12:31:59 bryant systemd[1]: Reached target ZFS pool import target.
-- Subject: A start job for unit zfs-import.target has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit zfs-import.target has finished successfully.
-- 
-- The job identifier is 14.
maalis 11 12:31:59 bryant systemd[1]: Mounting /home/tjaalton...
-- Subject: A start job for unit home-tjaalton.mount has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit home-tjaalton.mount has begun execution.
-- 
-- The job identifier is 61.
maalis 11 12:31:59 bryant systemd[1]: Mounting /root...
-- Subject: A start job for unit root.mount has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit root.mount has begun execution.
.
.
.

and so on, it mounts everything else during zfs-import but not my /data
pool..

-- 
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
Status in zfs-linux source package in Focal:
  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

Reply via email to