Installing headers after kernel update?

  • Hi. I am having OpenMediaVault setup with zfs plugin. Every time there is a kernel update, I run into this annoying problem. Maybe it is just how it must be, but it would be nice if it could be looked at and if it is even possible to do.


    My problem is that when I update the kernel it wants to rebuild it to be able to use zfs. But it is not able to do that because it does not have the headers to the new kernel. Would it be possible to when you update the kernel and having the zfs plugin installed, to tell it to install the new kernel update and the headers to the new kernel. I have to figured out how to do this without a reboot.


    When I install the new kernel it does net install the headers for it.


    I can then reboot after the kernel install but when it boots the zfs won't work because of the missing headers.


    Then I simply have to install the new headers to the new kernel and then reboot again. Now the zfs works again but it have messed up the mounting point for the zfs because it was booted up without zfs working.


    I then just have to remove the old mount point for the zfs and just remount for it to work again.


    All of this could probably be avoided if it install the headers at the same time as the new kernel installs.


    I hope that I am not the only one with this issue and please let me know if you want some more info to maybe fix this.


    It is something that I can live with but if you was totally unaware of this you would probably as a "normal" user be scared of losing your data when this happens.

  • This issue isn't common since the plugin depends on linux-headers-amd64 which is a meta package for the latest kernel headers. So, unless you are using a weird kernel, this should be working.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • This works for me as you would like to have it. I did not change anything to make it work that way.


    Regards Hoppel

    ---------------------------------------------------------------------------------------------------------------
    frontend software - tvos | android tv | libreelec | win10 | kodi krypton
    frontend hardware - appletv 4k | nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2
    -------------------------------------------
    backend software - debian | openmediavault | latest backport kernel | zfs raid-z2 | docker | emby | unifi | vdr | tvheadend | fhem
    backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • i try to install headers in order to make to work veem agent for linux but i gost this error:





  • Did you disable backports after installing a backports kernel? What is the output of: dpkg -l | grep linux-

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Did you disable backports after installing a backports kernel? What is the output of: dpkg -l | grep linux-

    here is the output, i haven't disabled nor enabled backports

  • got this error on jobs:



    i checked and it seems that the module veeamsnap is not correctly compiled :|

  • Now it makes more sense. The veeam module that it is trying to compile won't build on the 4.18 kernel (probably too new). You will have to find something on a veeam forum about this or disable backports, install the standard 4.9 kernel, and remove the 4.18 kernels.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Now it makes more sense. The veeam module that it is trying to compile won't build on the 4.18 kernel (probably too new). You will have to find something on a veeam forum about this or disable backports, install the standard 4.9 kernel, and remove the 4.18 kernels.

    i found that:


    https://github.com/veeam/veeamsnap




    Compatibility
    This module supports Linux kernels from 2.6.32 to 4.18.





    so it should work. hva you ever tried it?

  • so it should work. hva you ever tried it?

    The readme was updated 6 days ago. Are you using git code? If not, the readme before that said it only supports kernels up to 4.14. And no, I haven't tried veeam since I have no reason to use it. fsarchiver works for what I need.

    omv 5.5.9 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!