You have been subscribed to a public bug:

Having just upgraded Ubuntu 16.04, and seeing systemd updates, I
rebooted the machine, but it failed to start, entering emergency mode.
Relevant piece of info was this:

* Failed to start Import ZFS pools by cache file.
* Started Mount ZFS filesystems
** A start job is running for dev-disk....

and then it enters emergency mode.

Now, the only ZFS pool I have is a backup USB HDD which is constantly
attached, and the pool is on a LUKS provider, meaning you won't see it
until the provider is unlocked.

My guess is that the latest update, having triggered initramfs rebuild,
wrote the zpool.cache file with that state, and it shouldn't have.

This is totally wrong, as zpool cache should not be built like this as
it PREVENTS you from having external pools that might not be available
on boot. I also have no idea why it happened now because I've been
having this setup (external backup zfs pool on a LUKS provider) since
16.04 came out and never had a problem until now.

Removing the /etc/zfs/zpool.cache allowed the system to reboot fine.

# lsb_release -rd
Description:    Ubuntu 16.04.1 LTS
Release:        16.04

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: bot-comment regression-update
Ubuntu 16.04 breaks boot with wrong zpool.cache
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to