Closed Zsub closed 7 years ago
From looking at other issues I gather the move to systemd shouldn't be a problem, but I can't see my pool unless I manually import it.
Several tickets are open regarding systemd glitches and integration issues. Running Ubuntu 15.04 in upstart mode is a quick solution per:
The PPA will likely get two non-trivial updates during the Vivid series. The first to bundle systemd unit files, and the second to preserve mount ordering behavior. (eg: interleave support)
Another quick and dirty workaround is to add the following to rc.local:
# Workaround because mountall doesnt seem to work....
# Ensure all ROOT Pool mount points are mounted
zfs mount -a
# Import Extra Pools
zpool import extra-pool
# Ensure all Extra Pools mount points are mounted - possibly redundant
zfs mount -a
# Ensure all Shares are exported
zfs share -a
Is there a way to manually fix this issue until a package update comes out? The rc.local hack does work, but I'd prefer a solution which resolves the systemd problem.
Any ETA on the PPA update to fix systemd problems?
Same problem; I can't use the rc.local hack easily because I also have other stuff starting up which depends on ZFS filesystems being available. My best option at this point seems to be to switch back to upstart, unless this problem will be resolved soon?
@g-a-c, systemd was pushed out after the release freeze for Vivid (less than four weeks of lead time), and there wasn't enough time to do good work for both systems, so using upstart mode is currently the best choice. The update is planned between now and the W series.
I'm closing this as Vivid has been EOL for a while now.
I upgraded my ubuntu 14.10 to 15.04 and reinstalled the kernel modules for ZoL, but now my pool is not mounted on boot anymore. From looking at other issues I gather the move to systemd shouldn't be a problem, but I can't see my pool unless I manually import it. Once I import it manually it is immediately available (it does get mounted as soon as I import). But I'd rather eliminate the need for manual intervention each reboot :-)
The FAQ states to attach a unmodified kern.log, but that is huge, maybe the last boot will suffice as well?
However, zpool import has no trouble finding it:
Dmesg output: