Problem with new OMV7 kernel update

Mic2024 · Feb 19th 2025

Quote from Krisbee

Pinning kernel to backports installs 6.12.9+bpo-amd64 resulting in zfs modules failing to build against zfs-dkms version2.1.11-1+deb12u1.

This can be solved be installing updated version of zfs-dkms ( and dependencies) from backports without need of pve kernel then the update can complete.

I expected something like this. Could the developers of the OMV-Extras Plugin please provide an update containing this change? Thank you.

I have now installed:

Code

# zfs -V
zfs-2.2.7-pve1
zfs-kmod-2.2.7-pve1

# dpkg -l | grep zfs
ii  libzfs4linux                         2.2.7-pve1                          amd64        OpenZFS filesystem library for Linux - general support
ii  openmediavault-zfs                   7.1.1                               amd64        OpenMediaVault plugin for ZFS
ii  zfs-zed                              2.2.7-pve1                          amd64        OpenZFS Event Daemon
ii  zfsutils-linux                       2.2.7-pve1                          amd64        command-line tools to manage OpenZFS filesystems

ryecoaaron · Feb 20th 2025

Quote from Krisbee

Pinning kernel to backports installs 6.12.9+bpo-amd64 resulting in zfs modules failing to build against zfs-dkms version2.1.11-1+deb12u1.

If you enable backports from omv-extras or just click apt clean repos if you know backports is enabled, then zfs* is pinned and you will get zfs-dkms 2.2.7 from backports

Krisbee · Feb 20th 2025

Quote from ryecoaaron

If you enable backports from omv-extras or just click apt clean repos if you know backports is enabled, then zfs* is pinned and you will get zfs-dkms 2.2.7 from backports

True, but on systems using the stable kernel and openzfs 2.1.11 the OMV update installed the backport kernel without changing zfs-dkms.

Code

Start-Date: 2025-02-19  17:53:52
Commandline: apt-get --yes --allow-downgrades --allow-change-held-packages --fix-broken --fix-missing --auto-remove --allow-unauthenticated --show-upgraded --option DPkg::Options::=--force-confold dist-upgrade
Install: linux-image-6.12.9+bpo-amd64:amd64 (6.12.9-1~bpo12+1, automatic), linux-headers-6.12.9+bpo-amd64:amd64 (6.12.9-1~bpo12+1, automatic), linux-kbuild-6.12.9+bpo:amd64 (6.12.9-1~bpo12+1, automatic), linux-headers-6.12.9+bpo-common:amd64 (6.12.9-1~bpo12+1, automatic)
Upgrade: firmware-bnx2x:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-iwlwifi:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-brcm80211:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-atheros:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-myricom:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-ipw2x00:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-netxen:amd64 (20230210-5, 20240709-2~bpo12+1), linux-headers-amd64:amd64 (6.1.128-1, 6.12.9-1~bpo12+1), firmware-linux:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-intel-sound:amd64 (20230210-5, 20240709-2~bpo12+1), linux-image-amd64:amd64 (6.1.128-1, 6.12.9-1~bpo12+1), firmware-siano:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-realtek:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-libertas:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-amd-graphics:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-bnx2:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-misc-nonfree:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-qlogic:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-linux-nonfree:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-netronome:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-ivtv:amd64 (20230210-5, 20240709-2~bpo12+1), firmware-cavium:amd64 (20230210-5, 20240709-2~bpo12+1)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2025-02-19  17:56:36

Mic2024 · Feb 20th 2025

I think the solution to change the Standard-Kernel to the Proxmox-Kernel which natively includes ZFS support is the best and reliable solution. I hope and expect if there is an update of this Kernel this update includes ZFS support again. So, no “patching/updating” the Kernel with ZFS drivers is needed.

If there is a chance it would be great if the development team of OMV7 also includes ZFS support natively in the OMV standard Kernel. I think this may not be an issue for users who don’t install the OMV-extras ZFS plugin but make the life easier for users who install it.

For the moment, I am very happy that my system is running properly again. Also, If I would not use the word disaster, re-installing and setting-up OMV7 from scratch again would be a huge amount of work because I made a big bunch of settings in the WebGUI and there is no export and import solution for these hand-made configurations in OMV. (I miss something like the Teleporter feature from Pi-hole WebGUI.)

Thank you for your support and the great hint regarding the Proxmox-Kernel. 😊

Krisbee · Feb 20th 2025

Quote from Mic2024

I think the solution to change the Standard-Kernel to the Proxmox-Kernel which natively includes ZFS support is the best and reliable solution. I hope and expect if there is an update of this Kernel this update includes ZFS support again. So, no “patching/updating” the Kernel with ZFS drivers is needed....

Your post shows a misunderstanding of how ZFS works in Linux. Because of licensing issues OpenZFS is not in kernel and the associated kernel modules are not distributed pre-compiled in Debian and other distros. Hence the need to use debian's DKMS system and the zfs-dkms package and associated dependencies. Everytime time a new debian kernel is installed the associated new kernel headers are also installed and the DKMS system dynamically builds the necessary kernel modules. That takes time and the occasional problem can occur. There is never any "patching" with ZFS drivers and there is no such thing as "native" ZFS support.

Using the Proxmox kernel which is based on an upstream Ubuntu kernel avoids the need to rely on DKMS as the ZFS kenrel modules have been pre-built. In general you'd expect using the PVE kernel would give you a more recent version of OpenZFS than if you used the stable debian kernel. Although, right now, the pve kernel and debian backport kernel both give you OpenZFS 2.2.7

Mic2024 · Feb 20th 2025

Hi. Thank you for your explanations and details about the kernel and the handling of ZFS. This is really appreciated. Also, if you say ZFS is not natively implemented but it is pre-compiled in the Proxmox kernel this seems to be an advantage compared to the Debian backport kernel which is used by OMV7.

I just still wonder why this issue was not handled by the OMV update tool. I had the opinion I should not need to do any changes or adaptations outside the WebGUI of OMV. (Mostly when I did this, I run into troubles… e.g. with my beloved Error 500.) Due to that, I would expect, if I click on “download updates” in the OMV7 WebGUI, all tasks are done properly to install all updates and all dependencies.

I am also happy not to have the latest and greatest kernel or ZFS version. It just should run stabile in any case. 😊

I don’t see any downsides by using the mentioned Proxmox kernel (also for other OMV features like Docker…). So, I think I will continue with it.

Regards, Mic.

Krisbee · Feb 20th 2025

Quote from Mic2024

Hi. Thank you for your explanations and details about the kernel and the handling of ZFS. This is really appreciated. Also, if you say ZFS is not natively implemented but it is pre-compiled in the Proxmox kernel this seems to be an advantage compared to the Debian backport kernel which is used by OMV7.

Just to clarify. There is a difference between something being in the kernel as in the kernel code already supports a feature or needs a module to support a feature. Proxmox provides a kernel with the required modules for zfs pre-complied, they are not pre-complied in the kernel as they are not part of the kernel config.

ryecoaaron · Feb 20th 2025

Quote from Krisbee

True, but on systems using the stable kernel and openzfs 2.1.11 the OMV update installed the backport kernel without changing zfs-dkms.

That is probably because the OMV update fixed the backports pinning but nothing fixed the omv-extras zfs pinning until apt clean repos step is run.

Krisbee · Feb 20th 2025

Quote from ryecoaaron

That is probably because the OMV update fixed the backports pinning but nothing fixed the omv-extras zfs pinning until apt clean repos step is run.

Fine, but how would users know to do that?

ryecoaaron · Feb 20th 2025

Quote from Krisbee

how would users know to do that?

I didn't know it until this thread. So, I'm not saying they would. I was just reporting why the situation was happening and that going back to 6.1 is not required. The changelogs for OMV and omv-extras do report backports pinning fixes. A user would get the fixes eventually as well. Unfortunately, they get the 6.12 kernel first. This has been a problem with Debian backports for a long time (new kernel before new zfs package) and why I added the proxmox kernel in the beginning.

Mic2024 · Feb 20th 2025

Quote from ryecoaaron

That is probably because the OMV update fixed the backports pinning but nothing fixed the omv-extras zfs pinning until apt clean repos step is run.

By the way... "apr clean" in OMV-Extras did not solve my problem. In my opinion an update for the ZFS plugin rolled-out at the same time the kernel update is rolled out would be a solution.

ryecoaaron · Feb 20th 2025

Quote from Mic2024

"apr clean" in OMV-Extras did not solve my problem

apt clean repos (repos is important here) just fixes the zfs pinning so that the backports zfs-dkms package can be installed which is required for the 6.12 kernel. It may not have solved you problem with just that button click but it did fix what was necessary.

Quote from Mic2024

In my opinion an update for the ZFS plugin rolled-out at the same time the kernel update is rolled out would be a solution.

The zfs plugin can't fix this. It can't make apt changes while it is being installed. If people are going to use zfs, they should either install the proxmox kernel or disable backports if they don't ever want to run into this issue. I can't control what Debian does in backports.

Mic2024 · Feb 20th 2025

Quote from ryecoaaron

apt clean repos (repos is important here) just fixes the zfs pinning so that the backports zfs-dkms package can be installed which is required for the 6.12 kernel. It may not have solved you problem with just that button click but it did fix what was necessary.

I clicked it and tried to install the ZFS plugin again... and it failed.

Quote from ryecoaaron

The zfs plugin can't fix this. It can't make apt changes while it is being installed. If people are going to use zfs, they should either install the proxmox kernel or disable backports if they don't ever want to run into this issue. I can't control what Debian does in backports.

Proxmox is now my solution for the issue. Because: Where and how in the WebGUI do I enable or disable backports? I cannot remember that I have changed this option. 🤔

Soma · Feb 20th 2025

Quote from Mic2024

Where and how in the WebGUI do I enable or disable backports?

arleq · Feb 20th 2025

I dont use the ZFS plugin, but my OMV was very unstable since 6.12.9+bpo-amd64 update.

Changing kernel to 6.11 proxmox seems to fix the unstability. Thanks guys!

Quazgar · Feb 25th 2025

It would be useful to provide some documentation on ZFS + proxmox kernel outside of the forums.

For example, the official documentation at https://docs.openmediavault.or…esystems.html#filesystems talks about ZFS plugin but does not mention Proxmox kernel

Quote

Support for zfs is available through ZoL an uses a third party plugin provided by omv-extras. The development of the plugin was done in conjunction with core of openmediavault, so new code was added in the filesystem backend to improve support for zfs. The plugin registers datasets and pools in the internal database so you can create shared folders for zfs volumes. The creation of zvols is automatically recognized by openmediavault so you can format them and mount them in the web interface. The iscsiplugin can also use these zvols block devices to export LUN’s.

It would also be useful to mention common confusion (myself included) thinking that the PVE kernel is only needed if running OMV on top of Proxmox

markc · Feb 25th 2025

I just installed the OpenMediaVault 7.7.0 LXC container from helper-scripts.com and was looking for a ZFS plugin so I could perhaps mount a dataset from one of my ZFS pools. I don't need the "proxmox kernel" because I'm already on a Proxmox host but I'm getting the feeling that even trying to locate the extra packages for OMV 7.7 with a ZFS toolset so I can use the web gui (or cli) is going to be a waste of time, in my case.

Would anyone care to comment if using OMV 7.7 in a LXC container on a ZFS host node is possible, or not?

Krisbee · Feb 25th 2025

Quote from markc

I just installed the OpenMediaVault 7.7.0 LXC container from helper-scripts.com and was looking for a ZFS plugin so I could perhaps mount a dataset from one of my ZFS pools. I don't need the "proxmox kernel" because I'm already on a Proxmox host but I'm getting the feeling that even trying to locate the extra packages for OMV 7.7 with a ZFS toolset so I can use the web gui (or cli) is going to be a waste of time, in my case.

Would anyone care to comment if using OMV 7.7 in a LXC container on a ZFS host node is possible, or not?

OMV was never designed to run in LXC and it requires a nasty hack to get anything to work ( see: https://github.com/community-s…ProxmoxVE/discussions/175). I don't know what services apart from file serving you want from OMV, but there other and better was to do this by bind mounting zfs datasets to individual LXC containers running in Proxmox.

votdev · Feb 25th 2025

Quote from markc

I just installed the OpenMediaVault 7.7.0 LXC container from helper-scripts.com and was looking for a ZFS plugin so I could perhaps mount a dataset from one of my ZFS pools. I don't need the "proxmox kernel" because I'm already on a Proxmox host but I'm getting the feeling that even trying to locate the extra packages for OMV 7.7 with a ZFS toolset so I can use the web gui (or cli) is going to be a waste of time, in my case.

Would anyone care to comment if using OMV 7.7 in a LXC container on a ZFS host node is possible, or not?

There is a prominent warning that OMV does not work in LXC in the documentation.

ryecoaaron · Feb 25th 2025

Quote from Quazgar

It would be useful to provide some documentation on ZFS + proxmox kernel outside of the forums.

For example, the official documentation at https://docs.openmediavault.or…esystems.html#filesystems talks about ZFS plugin but does not mention Proxmox kernel

Feel free to contribute docs. From my point of view, it would just say try the proxmox kernel on amd64 to avoid compiling the zfs module and using debian backports for the latest zfs version.

The official docs don't usually mention anything about third party plugins. zfs and the proxmox kernel are omv-extras plugins.

Problem with new OMV7 kernel update

Participate now!

Similar Threads

Problems with Proxmox Kernel after update to OpenMediaVault 7

RTL8126 not working with OMV7

Successful Migration from OMV 6 to OMV7

System disk does not boot

kernel plugin: OMV6 to OMV7 upgrade followed by pve kernel install creates incorrect zfs config

Tags