Why do ZFS pools not mount after boot?

Why do ZFS pools not mount after boot?

After a restart, no pools were present ( zpool status showed no pools), but a zpool import would restore my pool. Turned out to be fixed by the answers to ZFS Pools not mounted 16.04. Reproducing the working answer here:

When to replace a device in a ZFS root pool?

If you need to replace a device that is UNAVAIL because it has failed, see Replacing a Device in a ZFS Storage Pool. If a device is UNAVAIL in a root pool or a mirrored root pool, see the following references: Mirrored root pool disk failed – Booting From an Alternate Disk in a Mirrored ZFS Root Pool

What happens if a ZFS storage device is unavailable?

If the device causes a top-level virtual device to be unavailable, then nothing in the pool can be accessed. Otherwise, the fault tolerance of the pool might be compromised. In either case, the device just needs to be reattached to the system to restore normal operations.

Why does ZFS automatically mount after reboot in Ubuntu?

Running ubuntu 13.10 server. Installed and setup zfs from the ubuntu ppa. All appears to work fine after a reboot if I manaully do a ‘sudo zfs mount -a’, but reading the FAQ on zfsonlinux.org it appears I should expect it to automatically mount.

How do I Reset my ZFS mount point?

Reset the mount points for the ZFS BE and its datasets. For example: Reboot the system. When the option to boot a specific boot environment is presented, either in the GRUB menu or at the OpenBoot PROM prompt, select the boot environment whose mount points were just corrected.

What should I do if my ZFS boot is failing?

If the boot is failing because of /var mounting problems, look for a similar incorrect temporary mount point for the /var dataset. Reset the mount points for the ZFS BE and its datasets.

How to automatically import ZFS-zpools in Ubuntu?

The first option is preferable and faster. To automatically import the zpools, change the value from 1 to 0: File: /etc/init/zpool-import.conf