Installing headers after kernel update?

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • 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.

      The post was edited 1 time, last by henkall: typoes, commas and gramatics ().

    • 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 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Installing headers after kernel update?

      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:




      Source Code

      1. root@omvtest:~# apt-get install linux-headers-amd64
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. linux-headers-amd64 : Depends: linux-headers-4.18.0-0.bpo.3-amd64 but it is not going to be installed
      12. E: Unable to correct problems, you have held broken packages.
      13. root@omvtest:~# apt-get install linux-headers-4.18.0-0.bpo.3-amd64
      14. Reading package lists... Done
      15. Building dependency tree
      16. Reading state information... Done
      17. Some packages could not be installed. This may mean that you have
      18. requested an impossible situation or if you are using the unstable
      19. distribution that some required packages have not yet been created
      20. or been moved out of Incoming.
      21. The following information may help to resolve the situation:
      22. The following packages have unmet dependencies:
      23. linux-headers-4.18.0-0.bpo.3-amd64 : Depends: linux-compiler-gcc-6-x86 (>= 4.14.17-1~) but 4.9.130-2 is to be installed
      24. E: Unable to correct problems, you have held broken packages.
      Display All
    • Did you disable backports after installing a backports kernel? What is the output of: dpkg -l | grep linux-
      omv 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      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

      Source Code

      1. root@omvtest:~# dpkg -l | grep linux
      2. ii console-setup-linux 1.164 all Linux specific part of console-setup
      3. ii firmware-linux 20180825+dfsg-1~bpo9+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
      4. ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel
      5. ii firmware-linux-nonfree 20180825+dfsg-1~bpo9+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
      6. ii libselinux1:amd64 2.6-3+b3 amd64 SELinux runtime shared libraries
      7. ii linux-base 4.5 all Linux image base package
      8. ii linux-compiler-gcc-6-x86 4.18.20-2~bpo9+1 amd64 Compiler for Linux on x86 (meta-package)
      9. ii linux-headers-4.18.0-0.bpo.1-amd64 4.18.6-1~bpo9+1 amd64 Header files for Linux 4.18.0-0.bpo.1-amd64
      10. ii linux-headers-4.18.0-0.bpo.1-common 4.18.6-1~bpo9+1 all Common header files for Linux 4.18.0-0.bpo.1
      11. ii linux-headers-4.18.0-0.bpo.3-amd64 4.18.20-2~bpo9+1 amd64 Header files for Linux 4.18.0-0.bpo.3-amd64
      12. ii linux-headers-4.18.0-0.bpo.3-common 4.18.20-2~bpo9+1 all Common header files for Linux 4.18.0-0.bpo.3
      13. ii linux-image-4.14.0-0.bpo.3-amd64 4.14.13-1~bpo9+1 amd64 Linux 4.14 for 64-bit PCs
      14. ii linux-image-4.18.0-0.bpo.3-amd64 4.18.20-2~bpo9+1 amd64 Linux 4.18 for 64-bit PCs
      15. ii linux-image-amd64 4.18+100~bpo9+1 amd64 Linux for 64-bit PCs (meta-package)
      16. ii linux-kbuild-4.18 4.18.20-2~bpo9+1 amd64 Kbuild infrastructure for Linux 4.18
      17. ii util-linux 2.29.2-1+deb9u1 amd64 miscellaneous system utilities
      18. root@omvtest:~#
      Display All
    • got this error on jobs:


      Source Code

      1. 09:30:35 Job BackupJob started at 2019-01-02 09:30:35 CET
      2. 09:30:35 Preparing to backup
      3. 09:30:35 [error] Failed to create volume snapshot 00:00:01
      4. 09:30:36 [error] Failed to perform backup
      5. 09:30:36 [error] Child execution has failed. Exit code: [1]
      6. 09:30:36 [error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]
      7. 09:30:36 [error] Processing finished with errors at 2019-01-02 09:30:36 CET
      Display All
      i checked and it seems that the module veeamsnap is not correctly compiled :|
    • Source Code

      1. Setting up veeamsnap (2.0.1.665) ...
      2. Loading new veeamsnap-2.0.1.665 DKMS files...
      3. Building for 4.18.0-0.bpo.3-amd64
      4. Building initial module for 4.18.0-0.bpo.3-amd64
      5. Error! Bad return status for module build on kernel: 4.18.0-0.bpo.3-amd64 (x86_64)
      6. Consult /var/lib/dkms/veeamsnap/2.0.1.665/build/make.log for more information.
      7. Setting up veeam (2.0.1.665) ...
      8. root@omvtest:~# cat /var/lib/dkms/veeamsnap/2.0.1.665/build/make.log
      9. DKMS make.log for veeamsnap-2.0.1.665 for kernel 4.18.0-0.bpo.3-amd64 (x86_64)
      10. Wed Jan 2 09:34:18 CET 2019
      11. make: Entering directory '/usr/src/linux-headers-4.18.0-0.bpo.3-amd64'
      12. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/log.o
      13. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/mem_alloc.o
      14. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/sparse_array_1lv.o
      15. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/sparse_bitmap.o
      16. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/container.o
      17. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/container_spinlocking.o
      18. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/queue_spinlocking.o
      19. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/bitmap_sync.o
      20. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/page_array.o
      21. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/rangelist.o
      22. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/rangevector.o
      23. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.o
      24. In file included from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.c:4:0:
      25. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h: In function ‘blk_bioset_create’:
      26. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: error: implicit declaration of function ‘bioset_create’ [-Werror=implicit-function-declaration]
      27. return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
      28. ^~~~~~~~~~~~~
      29. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: warning: return makes pointer from integer without a cast [-Wint-conversion]
      30. return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
      31. ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      32. CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.o
      33. cc1: some warnings being treated as errors
      34. /usr/src/linux-headers-4.18.0-0.bpo.3-common/scripts/Makefile.build:322: recipe for target '/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.o' failed
      35. make[3]: *** [/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.o] Error 1
      36. make[3]: *** Waiting for unfinished jobs....
      37. In file included from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.h:2:0,
      38. from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c:2:
      39. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h: In function ‘blk_bioset_create’:
      40. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: error: implicit declaration of function ‘bioset_create’ [-Werror=implicit-function-declaration]
      41. return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
      42. ^~~~~~~~~~~~~
      43. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: warning: return makes pointer from integer without a cast [-Wint-conversion]
      44. return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
      45. ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      46. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c: In function ‘blk_direct_bioset_free’:
      47. /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c:26:3: error: implicit declaration of function ‘bioset_free’ [-Werror=implicit-function-declaration]
      48. bioset_free( BlkDirectBioset );
      49. ^~~~~~~~~~~
      50. cc1: some warnings being treated as errors
      51. /usr/src/linux-headers-4.18.0-0.bpo.3-common/scripts/Makefile.build:322: recipe for target '/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.o' failed
      52. make[3]: *** [/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.o] Error 1
      53. make[3]: *** wait: No child processes. Stop.
      54. /usr/src/linux-headers-4.18.0-0.bpo.3-common/Makefile:1519: recipe for target '_module_/var/lib/dkms/veeamsnap/2.0.1.665/build' failed
      55. make[2]: *** [_module_/var/lib/dkms/veeamsnap/2.0.1.665/build] Error 2
      56. Makefile:146: recipe for target 'sub-make' failed
      57. make[1]: *** [sub-make] Error 2
      58. Makefile:8: recipe for target 'all' failed
      59. make: *** [all] Error 2
      60. make: Leaving directory '/usr/src/linux-headers-4.18.0-0.bpo.3-amd64'
      61. root@omvtest:~#
      Display All
    • 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 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      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:

      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?
    • spupuz wrote:

      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 4.1.17 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Users Online 1

      1 Guest