Is ZFS supported in Kernel 4.13-4.15?

    • OMV 4.x
    • Resolved
    • Upgrade 3.x -> 4.x

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

    • vulcan4d wrote:

      ryecoaaron wrote:

      vulcan4d wrote:

      What Kernel are you guys using with ZFS in OMV 4? My previous kernel of 4.4.67-1-pve does not work. Nor do any of the 4.9.0.0 bpo 1-6, or 4.9.0.6. That's all I have in my list, none work with ZFS. The other version your guys mentioned I don't even have show up.
      All of those kernels work with zfs (especially the proxmox kernel). You probably don't have the kernel headers installed.
      Almost got it working but one more hurdle remains, this is what I did.

      Proxmox would not install and "apt install linux-headers-$(uname -r)" would give error messages the the linux-header package was not available
      I ran "apt-get upgrade" and "apt-get dist-upgrade" which ended up installing the 4.15 kernel
      Then it let me run "apt install linux-headers-$(uname -r)" to install the kernel header on 4.15
      Rebooted, and my ZFS pools imported correctly
      Then I noticed the Shared Folders were still N/A for "device"
      I wanted to re-create, however the ZFS pools don't show up under devices anymore therefore I cannot create a Shared Folder.

      Very odd, any suggestions? They show up on the File System and they are mounted.
      You should always do an apt-get update before you install something otherwise you don’t have the most recent available package list. If you didn’t do this after altering your sources, apt would not have known the headers were available - hence your error.

      Do not use dist-upgrade on your OMV system. You run the risk of moving to a newer version of Debian, when released. At present it’s fine because you’re on the latest available stable version, but it might not have been - if you’d issued that command when Debian 10 was released, you’d be looking at a broken system right now. OMV has its own upgrade path that you should utilise when available.

      The problem you are seeing with the ZFS not showing as available in the shared folder lists is detailed here: ZFS device(s) not listed in devices dropdown and is being worked on. If you compile from git, you can get the fixes now.

      You could try adding a file system to the pool as Henkall suggested and see if it makes a difference, but in my case it didn’t.

      The post was edited 1 time, last by ellnic ().

    • Hi guys,

      today my omv informed me about new kernel header packages. So I did the following:

      Source Code

      1. Last login: Mon May 7 17:39:46 2018 from 10.11.11.100
      2. root@omv4:~# apt-get upgrade
      3. Paketlisten werden gelesen... Fertig
      4. Abhängigkeitsbaum wird aufgebaut.
      5. Statusinformationen werden eingelesen.... Fertig
      6. Paketaktualisierung (Upgrade) wird berechnet... Fertig
      7. Die folgenden Pakete sind zurückgehalten worden:
      8. linux-headers-amd64
      9. Die folgenden Pakete werden aktualisiert (Upgrade):
      10. intel-microcode linux-compiler-gcc-6-x86 linux-kbuild-4.9 linux-libc-dev wget
      11. 5 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
      12. Es müssen noch 0 B von 4.579 kB an Archiven heruntergeladen werden.
      13. Nach dieser Operation werden 15,4 kB Plattenplatz zusätzlich benutzt.
      14. Möchten Sie fortfahren? [J/n] J
      15. (Lese Datenbank ... 138529 Dateien und Verzeichnisse sind derzeit installiert.)
      16. Vorbereitung zum Entpacken von .../wget_1.18-5+deb9u2_amd64.deb ...
      17. Entpacken von wget (1.18-5+deb9u2) über (1.18-5+deb9u1) ...
      18. Vorbereitung zum Entpacken von .../intel-microcode_3.20180425.1~bpo9+1_amd64.deb ...
      19. Entpacken von intel-microcode (3.20180425.1~bpo9+1) über (3.20180312.1~bpo9+1) ...
      20. Vorbereitung zum Entpacken von .../linux-compiler-gcc-6-x86_4.16.5-1~bpo9+1_amd64.deb ...
      21. Entpacken von linux-compiler-gcc-6-x86 (4.16.5-1~bpo9+1) über (4.15.11-1~bpo9+1) ...
      22. Vorbereitung zum Entpacken von .../linux-kbuild-4.9_4.9.88-1+deb9u1_amd64.deb ...
      23. Entpacken von linux-kbuild-4.9 (4.9.88-1+deb9u1) über (4.9.88-1) ...
      24. Vorbereitung zum Entpacken von .../linux-libc-dev_4.9.88-1+deb9u1_amd64.deb ...
      25. Entpacken von linux-libc-dev:amd64 (4.9.88-1+deb9u1) über (4.9.88-1) ...
      26. intel-microcode (3.20180425.1~bpo9+1) wird eingerichtet ...
      27. update-initramfs: deferring update (trigger activated)
      28. intel-microcode: microcode will be updated at next boot
      29. linux-libc-dev:amd64 (4.9.88-1+deb9u1) wird eingerichtet ...
      30. linux-compiler-gcc-6-x86 (4.16.5-1~bpo9+1) wird eingerichtet ...
      31. linux-kbuild-4.9 (4.9.88-1+deb9u1) wird eingerichtet ...
      32. wget (1.18-5+deb9u2) wird eingerichtet ...
      33. Trigger für man-db (2.7.6.1-2) werden verarbeitet ...
      34. Trigger für initramfs-tools (0.130) werden verarbeitet ...
      35. update-initramfs: Generating /boot/initrd.img-4.15.0-0.bpo.2-amd64
      36. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      Display All

      One package was hold back, but I tried to install it and its dependencies:

      Source Code

      1. root@omv4:~# apt-get install linux-headers-amd64
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. The following additional packages will be installed:
      6. linux-headers-4.16.0-0.bpo.1-amd64 linux-headers-4.16.0-0.bpo.1-common linux-kbuild-4.16
      7. Die folgenden NEUEN Pakete werden installiert:
      8. linux-headers-4.16.0-0.bpo.1-amd64 linux-headers-4.16.0-0.bpo.1-common linux-kbuild-4.16
      9. Die folgenden Pakete werden aktualisiert (Upgrade):
      10. linux-headers-amd64
      11. 1 aktualisiert, 3 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      12. Es müssen noch 0 B von 9.522 kB an Archiven heruntergeladen werden.
      13. Nach dieser Operation werden 55,6 MB Plattenplatz zusätzlich benutzt.
      14. Möchten Sie fortfahren? [J/n]
      15. Vormals nicht ausgewähltes Paket linux-headers-4.16.0-0.bpo.1-common wird gewählt.
      16. (Lese Datenbank ... 138529 Dateien und Verzeichnisse sind derzeit installiert.)
      17. Vorbereitung zum Entpacken von .../linux-headers-4.16.0-0.bpo.1-common_4.16.5-1~bpo9+1_all.deb ...
      18. Entpacken von linux-headers-4.16.0-0.bpo.1-common (4.16.5-1~bpo9+1) ...
      19. Vormals nicht ausgewähltes Paket linux-kbuild-4.16 wird gewählt.
      20. Vorbereitung zum Entpacken von .../linux-kbuild-4.16_4.16.5-1~bpo9+1_amd64.deb ...
      21. Entpacken von linux-kbuild-4.16 (4.16.5-1~bpo9+1) ...
      22. Vormals nicht ausgewähltes Paket linux-headers-4.16.0-0.bpo.1-amd64 wird gewählt.
      23. Vorbereitung zum Entpacken von .../linux-headers-4.16.0-0.bpo.1-amd64_4.16.5-1~bpo9+1_amd64.deb ...
      24. Entpacken von linux-headers-4.16.0-0.bpo.1-amd64 (4.16.5-1~bpo9+1) ...
      25. Vorbereitung zum Entpacken von .../linux-headers-amd64_4.16+93~bpo9+1_amd64.deb ...
      26. Entpacken von linux-headers-amd64 (4.16+93~bpo9+1) über (4.15+91~bpo9+1) ...
      27. linux-headers-4.16.0-0.bpo.1-common (4.16.5-1~bpo9+1) wird eingerichtet ...
      28. linux-kbuild-4.16 (4.16.5-1~bpo9+1) wird eingerichtet ...
      29. linux-headers-4.16.0-0.bpo.1-amd64 (4.16.5-1~bpo9+1) wird eingerichtet ...
      30. /etc/kernel/header_postinst.d/dkms:
      31. Error! Bad return status for module build on kernel: 4.16.0-0.bpo.1-amd64 (x86_64)
      32. Consult /var/lib/dkms/zfs/0.7.6/build/make.log for more information.
      33. linux-headers-amd64 (4.16+93~bpo9+1) wird eingerichtet ...
      Display All

      I saw the last lines:

      Source Code

      1. Error! Bad return status for module build on kernel: 4.16.0-0.bpo.1-amd64 (x86_64)
      2. Consult /var/lib/dkms/zfs/0.7.6/build/make.log for more information.
      3. linux-headers-amd64 (4.16+93~bpo9+1) wird eingerichtet ...

      Here is the output of the file "/var/lib/dkms/zfs/0.7.6/build/make.log": pastebin.com/WkqZgBp8


      zfs-0.7.6 is Debian Stretch default at the moment. So I had a look at GitHub and learned that zfs-0.7.6 is compatible with kernels from 2.6.32 to 4.15: github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.6

      To use kernel 4.16 we need to get zfs-0.7.8 first: github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.8

      So, at the moment it's not possible to use kernel 4.16 with zfs under omv4 without compiling zfs-0.7.8 by your own.

      The title of this thread needs to be changed. ;)

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------

      The post was edited 1 time, last by hoppel118 ().

    • The 4.16 kernel was released yesterday. Nothing we can do until 0.7.8 is in the repo. Just don't upgrade to the 4.16 kernel until then.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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!
    • vcp_ai wrote:

      Can anybody point me how to 'downgrade' to 4.14 ?
      You don't need to downgrade. Just the set the 4.14 kernel to be the default kernel in the omv-extras kernel tab. You might run into issue if you upgrade other packages that use a compiled kernel module though.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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!
    • yeah it didn't help changing back to in my case 4.15 kernel still getting zfs errors.

      root@nas:~# uname -a
      Linux nas 4.15.0-0.bpo.2-amd64 #1 SMP Debian 4.15.11-1~bpo9+1 (2018-04-07) x86_64 GNU/Linux

      root@nas:~# zfs status
      The ZFS modules are not loaded.
      Try running '/sbin/modprobe zfs' as root to load them.
      root@nas:~# /sbin/modprobe zfs
      modprobe: FATAL: Module zfs not found in directory /lib/modules/4.15.0-0.bpo.2-amd64
    • Is ZFS supported in Kernel 4.13-4.15?

      That’s the kernel you were on before? Did you purge after you upgraded? The module should still be there.

      Do you have several choices in the drop down? Are you sure it’s the 4.15 kernel?

      You could try installing headers [again?]:

      Source Code

      1. apt install linux-headers-amd64


      What does this result in? You’ll probably have to modprobe ZFS afterwards, or reboot.


      Sent from my iPhone using Tapatalk
    • I went back to 14 still sawe problem

      root@nas:~# uname -a
      Linux nas 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) x86_64 GNU/Linux

      When trying to install the headers it seems to search for 16 dependency while i am on 14 now

      root@nas:~# apt install linux-headers-amd64
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:


      The following packages have unmet dependencies:
      linux-headers-amd64 : Depends: linux-headers-4.16.0-0.bpo.1-amd64 but it is not going to be installed
      E: Unable to correct problems, you have held broken packages.
    • I booted back to 16 as i was curious if i had same header issue there and yes i did trying to install it i get the following problem

      root@nas:~# apt install linux-headers-amd64
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:


      The following packages have unmet dependencies:
      linux-headers-amd64 : Depends: linux-headers-4.16.0-0.bpo.1-amd64 but it is not going to be installed
      E: Unable to correct problems, you have held broken packages.
      root@nas:~# apt install linux-headers-4.16.0-0.bpo.1-amd64
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Some packages could not be installed. This may mean that you have
      requested an impossible situation or if you are using the unstable
      distribution that some required packages have not yet been created
      or been moved out of Incoming.
      The following information may help to resolve the situation:


      The following packages have unmet dependencies:
      linux-headers-4.16.0-0.bpo.1-amd64 : Depends: linux-compiler-gcc-6-x86 (>= 4.14.17-1~) but 4.9.88-1+deb9u1 is to be installed
      E: Unable to correct problems, you have held broken packages.
      root@nas:~# apt install linux-compiler-gcc-6-x86
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      linux-compiler-gcc-6-x86 is already the newest version (4.9.88-1+deb9u1).
      linux-compiler-gcc-6-x86 set to manually installed.
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

      So on 16 i am also not able to install the headers as it wants a compiler newer or equal to 4.14 but 4.9.88 is installed ?

      Now i am stucked as i am also not able to compile zfs manually for the 16 kernel without the header install.

      EDIT: Do i need to go to the stretch backports to get higher version little weird or not?

      The post was edited 1 time, last by ArmandH ().

    • ​I just built the zfs 0.7.9 packages from debian sid and uploaded to omv-extras 4.x testing repos. These are working on my test VM with the 4.16 kernel. I didn't test against the 4.14 or 4.15 kernel though.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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:

      I just built the zfs 0.7.9 packages from debian sid and uploaded to omv-extras 4.x testing repos. These are working on my test VM with the 4.16 kernel. I didn't test against the 4.14 or 4.15 kernel though.
      That's kind of a relief. If 4.16 will work (eventually), great.

      I've built OMV4 a few times on real hardware, installed the kernel headers, didn't install the 4.16 update, pinned the 4.14 kernel in OMV-Extras, and the ZFS plugin insisted on building a module for the 4.16 kernel, regardless. All attempts ended in an error like @hoppel118's above.
      Good backup takes the "drama" out of computing
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
      2nd Data Backup: OMV 3.0.99, R-PI 2B, 16GB boot, 4TB WD USB MyPassport - direct connect (no hub)

      The post was edited 1 time, last by flmaxey: edit ().

    • flmaxey wrote:

      the ZFS plugin insisted on building a module for the 4.16 kernel, regardless
      Because we didn't want to specify specific versions of headers (nightmare to maintain), the zfs plugin depends on linux-headers-amd64 which is a meta package that Debian points to the newest kernel. So, the plugin will always install them which will make it install the linux-image-amd64 meta package as well. The only true way around this is disable backports in /etc/default/openmediavault and use the 4.9 kernel from the standard repo. This will use linux-image-amd64 and linux-headers-amd64 from the standard repo which is the 4.9 kernel and headers.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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:

      The only true way around this is disable backports in /etc/default/openmediavault and use the 4.9 kernel from the standard repo. This will use linux-image-amd64 and linux-headers-amd64 from the standard repo which is the 4.9 kernel and headers.
      Would using kernel 4.9 in stretch have detrimental affects on the rest of OMV4's packages (specifically Samba)? I can't see the Dev's of various packages making immediate use of new kernel abilities.

      I'm not looking for a definitive answer, - just a best guess.
      Good backup takes the "drama" out of computing
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
      2nd Data Backup: OMV 3.0.99, R-PI 2B, 16GB boot, 4TB WD USB MyPassport - direct connect (no hub)
    • flmaxey wrote:

      Would using kernel 4.9 in stretch have detrimental affects on the rest of OMV4's packages (specifically Samba)?
      Packages? I can't think of one that would be affected. Hardware support? Yes. btrfs? yes. The kernel has nothing to do with samba.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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:

      Packages? I can't think of one that would be affected. Hardware support? Yes. btrfs? yes. The kernel has nothing to do with samba.
      You mean Samba will run without the kernel?? 8o Just kidding... :D My test hardware is the humble kind. (Older stuff.)
      BTRFS - nothing to miss there. Prediction - all good by kernel 5.0.
      ____________________________________________________________

      But, I must have something else going on. Even with kernel 4.9.0, the ZFS plugin is still attempting to install 0.7.9 and it stops with an endless Error. It's time to start over and sift through the details.
      Good backup takes the "drama" out of computing
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
      2nd Data Backup: OMV 3.0.99, R-PI 2B, 16GB boot, 4TB WD USB MyPassport - direct connect (no hub)
    • I got my zfs back in 16 kernel but when forcing the mount of my pool my pool is empty :-((((

      Only my folders are there but nothing in it

      root@nas:/onepool# ls *
      docker:


      downloads:
      deluge transmission


      kids:


      movies:


      music:


      photos:


      series:


      timemachine:


      videos:

      Weird thin is it says:

      root@nas:~# zfs list
      NAME USED AVAIL REFER MOUNTPOINT
      onepool 1.22T 2.29T 1.22T /onepool

      so nothing but still 1.22T in use, i most forget something
    • ryecoaaron wrote:

      I just built the zfs 0.7.9 packages from debian sid and uploaded to omv-extras 4.x testing repos. These are working on my test VM with the 4.16 kernel. I didn't test against the 4.14 or 4.15 kernel though.

      Just to be sure... Whats the right way to upgrade to your latest zfs packages?

      Tonight my omv4 informed me about your zfs packages:

      Source Code

      1. CRON-APT RUN [/etc/cron-apt/config]: Sat May 19 00:09:36 CEST 2018
      2. CRON-APT SLEEP: 3264, Sat May 19 01:04:00 CEST 2018
      3. CRON-APT ACTION: 3-download
      4. CRON-APT LINE: /usr/bin/apt-get -o Acquire::http::Dl-Limit=25 dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
      5. Reading package lists...
      6. Building dependency tree...
      7. Reading state information...
      8. Calculating upgrade...
      9. The following packages will be upgraded:
      10. curl libcurl3 libcurl3-gnutls libnvpair1linux libuutil1linux libzfs2linux
      11. libzpool2linux spl-dkms zfs-dkms zfs-zed zfsutils-linux
      12. 11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      13. Need to get 2963 kB/3771 kB of archives.
      14. After this operation, 263 kB of additional disk space will be used.
      15. Get:1 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 spl-dkms all 0.7.9-2 [398 kB]
      16. Get:2 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 zfs-dkms all 0.7.9-2 [1398 kB]
      17. Get:3 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 zfsutils-linux amd64 0.7.9-2 [312 kB]
      18. Get:4 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 libuutil1linux amd64 0.7.9-2 [48.5 kB]
      19. Get:5 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 libnvpair1linux amd64 0.7.9-2 [45.6 kB]
      20. Get:6 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 libzpool2linux amd64 0.7.9-2 [561 kB]
      21. Get:7 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 libzfs2linux amd64 0.7.9-2 [137 kB]
      22. Get:8 https://dl.bintray.com/openmediavault-plugin-developers/arrakis-testing stretch/main amd64 zfs-zed amd64 0.7.9-2 [62.6 kB]
      23. Fetched 2963 kB in 2min 35s (19.1 kB/s)
      24. Download complete and in download only mode
      Display All

      1. I searched for the latest kernels:

      Source Code

      1. root@omv4:~# apt-cache search linux-image*
      2. linux-image-4.9.0-6-amd64 - Linux 4.9 for 64-bit PCs
      3. linux-image-4.9.0-6-amd64-dbg - Debug symbols for linux-image-4.9.0-6-amd64
      4. linux-image-4.9.0-6-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
      5. linux-image-4.9.0-6-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-6-rt-amd64
      6. linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
      7. linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
      8. linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
      9. linux-image-4.9.0-3-amd64 - Linux 4.9 for 64-bit PCs
      10. linux-image-4.9.0-3-amd64-dbg - Debug symbols for linux-image-4.9.0-3-amd64
      11. linux-image-4.9.0-3-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
      12. linux-image-4.9.0-3-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-3-rt-amd64
      13. linux-image-4.9.0-4-amd64 - Linux 4.9 for 64-bit PCs
      14. linux-image-4.9.0-4-amd64-dbg - Debug symbols for linux-image-4.9.0-4-amd64
      15. linux-image-4.9.0-4-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
      16. linux-image-4.9.0-4-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-4-rt-amd64
      17. linux-image-4.9.0-5-amd64 - Linux 4.9 for 64-bit PCs
      18. linux-image-4.9.0-5-amd64-dbg - Debug symbols for linux-image-4.9.0-5-amd64
      19. linux-image-4.9.0-5-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
      20. linux-image-4.9.0-5-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-5-rt-amd64
      21. linux-image-4.15.0-0.bpo.2-amd64 - Linux 4.15 for 64-bit PCs
      22. linux-image-4.15.0-0.bpo.2-amd64-dbg - Debug symbols for linux-image-4.15.0-0.bpo.2-amd64
      23. linux-image-4.15.0-0.bpo.2-cloud-amd64 - Linux 4.15 for x86-64 cloud
      24. linux-image-4.15.0-0.bpo.2-cloud-amd64-dbg - Debug symbols for linux-image-4.15.0-0.bpo.2-cloud-amd64
      25. linux-image-4.16.0-0.bpo.1-amd64 - Linux 4.16 for 64-bit PCs
      26. linux-image-4.16.0-0.bpo.1-amd64-dbg - Debug symbols for linux-image-4.16.0-0.bpo.1-amd64
      27. linux-image-4.16.0-0.bpo.1-cloud-amd64 - Linux 4.16 for x86-64 cloud
      28. linux-image-4.16.0-0.bpo.1-cloud-amd64-dbg - Debug symbols for linux-image-4.16.0-0.bpo.1-cloud-amd64
      29. linux-image-4.9.0-4-grsec-amd64 - Linux 4.9 for 64-bit PCs, Grsecurity protection (unofficial patch)
      30. linux-image-grsec-amd64 - Linux image meta-package, grsec featureset
      31. linux-image-amd64 - Linux for 64-bit PCs (meta-package)
      32. linux-image-cloud-amd64 - Linux for x86-64 cloud (meta-package)
      33. linux-image-cloud-amd64-dbg - Debugging symbols for Linux cloud-amd64 configuration (meta-package)
      34. linux-headers-4.14.0-0.bpo.3-amd64 - Header files for Linux 4.14.0-0.bpo.3-amd64
      35. linux-headers-4.14.0-0.bpo.2-amd64 - Header files for Linux 4.14.0-0.bpo.2-amd64
      36. linux-image-4.14.0-0.bpo.2-amd64 - Linux 4.14 for 64-bit PCs
      37. linux-image-4.13.0-0.bpo.1-amd64 - Linux 4.13 for 64-bit PCs
      Display All


      2. I installed the latest kernel:

      Source Code

      1. root@omv4:~# apt-get install linux-image-4.16.0-0.bpo.1-amd64
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. Vorgeschlagene Pakete:
      6. linux-doc-4.16 debian-kernel-handbook
      7. Empfohlene Pakete:
      8. irqbalance apparmor
      9. Die folgenden NEUEN Pakete werden installiert:
      10. linux-image-4.16.0-0.bpo.1-amd64
      11. 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 8 nicht aktualisiert.
      12. Es müssen 45,6 MB an Archiven heruntergeladen werden.
      13. Nach dieser Operation werden 259 MB Plattenplatz zusätzlich benutzt.
      14. Holen:1 http://cdn-fastly.deb.debian.org/debian stretch-backports/main amd64 linux-image-4.16.0-0.bpo.1-amd64 amd64 4.16.5-1~bpo9+1 [45,6 MB]
      15. Es wurden 45,6 MB in 8 s geholt (5.619 kB/s).
      16. Vormals nicht ausgewähltes Paket linux-image-4.16.0-0.bpo.1-amd64 wird gewählt.
      17. (Lese Datenbank ... 155311 Dateien und Verzeichnisse sind derzeit installiert.)
      18. Vorbereitung zum Entpacken von .../linux-image-4.16.0-0.bpo.1-amd64_4.16.5-1~bpo9+1_amd64.deb ...
      19. Entpacken von linux-image-4.16.0-0.bpo.1-amd64 (4.16.5-1~bpo9+1) ...
      20. linux-image-4.16.0-0.bpo.1-amd64 (4.16.5-1~bpo9+1) wird eingerichtet ...
      21. I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-0.bpo.2-amd64
      22. I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-0.bpo.2-amd64
      23. I: /vmlinuz is now a symlink to boot/vmlinuz-4.16.0-0.bpo.1-amd64
      24. I: /initrd.img is now a symlink to boot/initrd.img-4.16.0-0.bpo.1-amd64
      25. /etc/kernel/postinst.d/dkms:
      26. Error! Bad return status for module build on kernel: 4.16.0-0.bpo.1-amd64 (x86_64)
      27. Consult /var/lib/dkms/zfs/0.7.6/build/make.log for more information.
      28. /etc/kernel/postinst.d/initramfs-tools:
      29. update-initramfs: Generating /boot/initrd.img-4.16.0-0.bpo.1-amd64
      30. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
      31. /etc/kernel/postinst.d/zz-update-grub:
      32. GRUB-Konfigurationsdatei wird erstellt …
      33. Linux-Abbild gefunden: /boot/vmlinuz-4.16.0-0.bpo.1-amd64
      34. initrd-Abbild gefunden: /boot/initrd.img-4.16.0-0.bpo.1-amd64
      35. Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-0.bpo.2-amd64
      36. initrd-Abbild gefunden: /boot/initrd.img-4.15.0-0.bpo.2-amd64
      37. Linux-Abbild gefunden: /boot/vmlinuz-4.14.0-0.bpo.2-amd64
      38. initrd-Abbild gefunden: /boot/initrd.img-4.14.0-0.bpo.2-amd64
      39. Linux-Abbild gefunden: /boot/vmlinuz-4.13.0-0.bpo.1-amd64
      40. initrd-Abbild gefunden: /boot/initrd.img-4.13.0-0.bpo.1-amd64
      41. Linux-Abbild gefunden: /boot/vmlinuz-4.9.0-4-amd64
      42. initrd-Abbild gefunden: /boot/initrd.img-4.9.0-4-amd64
      43. erledigt
      Display All


      Again I see the following message. But this is fine.

      Source Code

      1. /etc/kernel/postinst.d/dkms:
      2. Error! Bad return status for module build on kernel: 4.16.0-0.bpo.1-amd64 (x86_64)
      3. Consult /var/lib/dkms/zfs/0.7.6/build/make.log for more information.


      3. I checked to have the latest kernel headers:

      Source Code

      1. root@omv4:~# apt-get install linux-headers-amd64
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. linux-headers-amd64 ist schon die neueste Version (4.16+93~bpo9+1).
      6. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 8 nicht aktualisiert.
      What do I have to now? Is the following the right way?

      4. Reboot to the latest kernel 4.16
      5. Install the new zfs packages
      6. Maybe another Reboot is needed


      If this steps go wrong, is it still possible to load kernel 4.15 with the at moment installed zfs 0.76 modules? Or isn't it possible, because the 0.7.9-2 zfs packages overwrite the 0.7.6 modules?

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • flmaxey wrote:

      But, I must have something else going on. Even with kernel 4.9.0, the ZFS plugin is still attempting to install 0.7.9 and it stops with an endless Error. It's time to start over and sift through the details.
      If you disable the omv-extras testing repo, it won't install the 0.7.9 packages.
      omv 4.1.9 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      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