Package Details: mkinitcpio-sd-zfs 1.0.2-1

Git Clone URL: https://aur.archlinux.org/mkinitcpio-sd-zfs.git (read-only)
Package Base: mkinitcpio-sd-zfs
Description: Compatibility between systemd and ZFS roots
Upstream URL: https://github.com/dasJ/sd-zfs
Keywords: zfs
Licenses: MIT
Conflicts: mkinitcpio-sd-zfs-git
Submitter: das_j
Maintainer: das_j
Last Packager: das_j
Votes: 3
Popularity: 0.117121
First Submitted: 2016-08-04 21:09
Last Updated: 2017-11-10 13:13

Latest Comments

jrudess commented on 2017-11-11 03:23

@das_j Can confirm that 1.0.2 fixed the importing issues for my pool

das_j commented on 2017-11-10 13:12

@robree @nibjob Please test the current version

roobre commented on 2017-11-04 14:42

It seems that this issue just hit me too. Since there's no response upstream, can anyone link to the previous compiled version? /cc @nibjib

nibjib commented on 2017-10-10 22:08

I also had this issue: running 'dmesg' in the rescue console allowed me to see that the unit generator 'initrd-zfs-generator' was failing with a segfault, causing a fallback to the standard systemd-fstab-generator that creates the sysroot.mount unit from the 'root' kernel parameter (which, when prefixed by 'zfs:' doesn't work for the standard 'mount' command, as you might expect).

Luckily I had the previous version of this package in my aurutils-managed local repository to downgrade to.

If it's useful, I can upload both packages for comparison and to aid in tracking down the error?

fclad commented on 2017-10-04 23:45

Same problem here. I had to rollback my root partition and create a new ramdisk, the pool was not imported on boot.

das_j commented on 2017-09-30 19:45

@jcstryker I have the same problem, but only on some machines.
I don't have a lot of time to investigate, so it might take a while.
If you have any hints, I'd be very grateful.

jcstryker commented on 2017-09-22 03:32

Current upstream version is 1.0.1.

I am also am getting an issue where pool doesn't get imported on boot, causing sysroot.mount to fail.

Need to use "zpool import -N <zpool>" and restart sysroot.mount to continue.

This happened out of the blue, not sure which update may have caused this. Any idea why?