• zfs dkms error during linux kernel (4.11.6-1) update


    Here’s the error from terminal output:
    /*
    Running pre-transaction hooks…
    Remove DKMS modules
    ==> dkms remove spl/0.7.0rc4 -k 4.11.5-1-ARCH
    ==> dkms remove zfs/0.7.0rc4 -k 4.11.5-1-ARCH
    Upgrading boost-libs (1.64.0-1 -> 1.64.0-2)…
    Upgrading linux (4.11.5-1 -> 4.11.6-1)…

    Updating module dependencies. Please wait …
    Upgrading linux-headers (4.11.5-1 -> 4.11.6-1)…
    Upgrading perl-http-message (6.11-3 -> 6.13-1)…
    Running post-transaction hooks…
    Install DKMS modules
    ==> dkms install zfs/0.7.0rc4 -k 4.11.6-1-ARCH
    configure: error:
    *** Please make sure the kmod spl devel <kernel> package for your
    *** distribution is installed then try again. If that fails you
    *** can specify the location of the spl objects with the
    *** ‘–with-spl-obj=PATH’ option. Failed to find spl_config.h in
    *** any of the following:
    /usr/src/spl-0.7.0rc4/4.11.6-1-ARCH
    /usr/src/spl-0.7.0rc4
    */

    I restored from last night’s midnight cron backup /boot, /, and /home and am booted up to the Desktop fine.

    Will wait for your review and reply until I try again.
    Dietrich

  • So, I gave this 4 hours to see if anyone would reply. Nope.
    I am going back to ext4 for now. ZFS is not ready for prime time, it would appear, and, after more than a year still issues.

    Closing the issue. --Dietrich

  • Reopening this issue to give an update.
    I did a clean install of Antergos with ZFS again, this time not creating a separate partition for /home and not opting (as previously) to install Linux Kernel-LTS.

    This time around, I have proactively installed zfs-auto-snapshot which is in the Arch repo.
    The backup routines are not controlled by a crond, but enabled, started, stopped using systemctl; ex:
    #systemctl enable zfs-auto-snapshot-hourly.timer
    #systemctl start --now zfs-auto-snapshot-hourly-timer
    "#systemctl list-timers" produces this output confirming the services are running one about to fire in 4 minutes:
    http://i.imgur.com/mTAwtkY.png
    That’s it. If I get another update error of the kind above, I can now restore from a snapshot, presumably.
    Thanks

  • Update: It is 6:30 am now. 1st cup of coffee and checked to see if the auto snapshot is working:

    [[email protected] dts]# zfs list -t snap
    NAME                                             USED  AVAIL  REFER  MOUNTPOINT
    [email protected]                      13.5M      -  6.88G  -
    [email protected]_2017-06-21-0000_hourly       11.0M      -  6.88G  -
    [email protected]_2017-06-21-0100_hourly       19.0M      -  6.91G  -
    [email protected]_2017-06-21-0200_hourly       26.0M      -  6.92G  -
    [email protected]_2017-06-21-0300_hourly       36.6M      -  6.93G  -
    [email protected]_2017-06-21-0400_daily         248K      -  6.94G  -
    [email protected]_2017-06-21-0400_hourly        376K      -  6.94G  -
    [email protected]_2017-06-21-0500_hourly       50.7M      -  6.98G  -
    [email protected]_2017-06-21-0600_hourly       56.7M      -  6.98G  -
    [email protected]_2017-06-21-0700_hourly       72.6M      -  7.02G  -
    [email protected]_2017-06-21-0800_hourly       76.8M      -  7.03G  -
    [email protected]_2017-06-21-0900_hourly       84.6M      -  7.04G  -
    [email protected]_2017-06-21-1000_hourly       92.2M      -  7.05G  -
    [email protected]_2017-06-21-0000_hourly  10.1M      -   412M  -
    [email protected]_2017-06-21-0100_hourly  5.04M      -   457M  -
    [email protected]_2017-06-21-0200_hourly  5.71M      -   460M  -
    [email protected]_2017-06-21-0300_hourly  4.89M      -   461M  -
    [email protected]_2017-06-21-0400_daily      0B      -   463M  -
    [email protected]_2017-06-21-0400_hourly     0B      -   463M  -
    [email protected]_2017-06-21-0500_hourly  4.93M      -   465M  -
    [email protected]_2017-06-21-0600_hourly  5.97M      -   468M  -
    [email protected]_2017-06-21-0700_hourly  5.01M      -   469M  -
    [email protected]_2017-06-21-0800_hourly  5.16M      -   471M  -
    [email protected]_2017-06-21-0900_hourly  5.27M      -   473M  -
    [email protected]_2017-06-21-1000_hourly  5.20M      -   475M  -
    [[email protected] dts]# 
    
    

    So it is. I am pleased. And I must apologize for my remarks (not ready for prime time). I was wrong. It is ready.

    Now, I feel that even if a package update fails such as the above error with dkms, I can roll back instantaneously and wait for help from the Antergos Team.

    I’ll mark this solved and again thank you to the developers for their hard work. – Sincerely Dietrich

  • Well, I just reopened this issue (marked unsolved) b/c this am I found updates ready to apply that included linux:
    /*
    [[email protected] ~]$ sudo pacman -Syyu
    [sudo] password for dts:
    :: Synchronizing package databases…
    antergos 153.2 KiB 1344K/s 00:00 [######################] 100%
    core 125.6 KiB 1047K/s 00:00 [######################] 100%
    extra 1665.3 KiB 2.01M/s 00:01 [######################] 100%
    community 3.9 MiB 2.05M/s 00:02 [######################] 100%
    multilib 176.6 KiB 2.08M/s 00:00 [######################] 100%
    :: Starting full system upgrade…
    resolving dependencies…
    looking for conflicting packages…

    Packages (5) lib32-icu-59.1-1 lib32-libxml2-2.9.4+16+g07418011-1
    linux-4.11.6-3 linux-headers-4.11.6-3 lua-5.3.4-2

    Total Download Size: 77.49 MiB
    Total Installed Size: 168.56 MiB
    Net Upgrade Size: 47.50 MiB

    :: Proceed with installation? [Y/n] y
    */
    It seems that every time an Antergos system using ZFS attempts to apply a Linux update, it is scripted to run dkms to remove the old ZFS drivers and then it commences to add the new ones, … and chokes, errors out as below:
    :: Proceed with installation? [Y/n] y
    :: Retrieving packages…
    linux-4.11.6-3-x86_64 61.4 MiB 2.02M/s 00:30 [####################################################] 100%
    linux-headers-4.11.6-3-x86_64 7.7 MiB 2.05M/s 00:04 [####################################################] 100%
    lua-5.3.4-2-x86_64 227.0 KiB 2.07M/s 00:00 [####################################################] 100%
    lib32-icu-59.1-1-x86_64 7.6 MiB 2016K/s 00:04 [####################################################] 100%
    lib32-libxml2-2.9.4+16+g07418011-1-x86_64 556.6 KiB 1899K/s 00:00 [####################################################] 100%
    (5/5) checking keys in keyring [####################################################] 100%
    (5/5) checking package integrity [####################################################] 100%
    (5/5) loading package files [####################################################] 100%
    (5/5) checking for file conflicts [####################################################] 100%
    (5/5) checking available disk space [####################################################] 100%
    :: Running pre-transaction hooks…
    (1/1) Remove DKMS modules
    ==> dkms remove zfs/0.7.0rc4 -k 4.11.6-1-ARCH
    ==> dkms remove spl/0.7.0rc4 -k 4.11.6-1-ARCH
    :: Processing package changes…
    (1/5) installing lib32-icu [####################################################] 100%
    (2/5) upgrading lib32-libxml2 [####################################################] 100%
    (3/5) upgrading linux [####################################################] 100%

    Updating module dependencies. Please wait …
    (4/5) upgrading linux-headers [####################################################] 100%
    (5/5) upgrading lua [####################################################] 100%
    :: Running post-transaction hooks…
    (1/3) Install DKMS modules
    ==> dkms install spl/0.7.0rc4 -k 4.11.6-3-ARCH
    Job for systemd-modules-load.service failed because the control process exited with error code.
    See “systemctl status systemd-modules-load.service” and “journalctl -xe” for details.
    ==> dkms install zfs/0.7.0rc4 -k 4.11.6-3-ARCH
    Job for systemd-modules-load.service failed because the control process exited with error code.
    See “systemctl status systemd-modules-load.service” and “journalctl -xe” for details.
    (2/3) Updating linux initcpios
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: ‘default’
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 4.11.6-3-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [autodetect]
    -> Running build hook: [modconf]
    -> Running build hook: [block]
    -> Running build hook: [keyboard]
    -> Running build hook: [keymap]
    -> Running build hook: [resume]
    -> Running build hook: [zfs]
    ==> ERROR: module not found: zlib_deflate' -> Running build hook: [filesystems] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect ==> Starting build: 4.11.6-3-ARCH -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: wd719x ==> WARNING: Possibly missing firmware for module: aic94xx -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [resume] -> Running build hook: [zfs] ==> ERROR: module not found:zlib_deflate’
    -> Running build hook: [filesystems]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    error: command failed to execute correctly
    (3/3) Arming ConditionNeedsUpdate…
    [[email protected] ~]$

    ================================

    It’s the same situation as happen when I opened this ticket last week but on a different day. ;) Additionally journalctl shows this:

    Jun 24 07:41:50 dts systemd[1]: Starting Load Kernel Modules…
    – Subject: Unit systemd-modules-load.service has begun start-up
    – Defined-By: systemd
    – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    – Unit systemd-modules-load.service has begun starting up.
    Jun 24 07:41:50 dts systemd-modules-load[22865]: Failed to lookup alias ‘sg’: Function not implemented
    Jun 24 07:41:50 dts systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
    Jun 24 07:41:50 dts systemd[1]: Failed to start Load Kernel Modules.
    – Subject: Unit systemd-modules-load.service has failed
    – Defined-By: systemd
    – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    – Unit systemd-modules-load.service has failed.

    – The result is failed.
    Jun 24 07:41:50 dts systemd[1]: systemd-modules-load.service: Unit entered failed state.
    Jun 24 07:41:50 dts systemd[1]: systemd-modules-load.service: Failed with result ‘exit-code’.

    /*

    */

    Unless I rollback ZFS, which I can do, I am dead in the water when I reboot.

    Please review and advise. Thanks all – Dietrich

kernel64 during14 dkms5 error166 Posts 5Views 170
Log in to reply