latest update fails compiling zfs module (kernel 5.18)

Tupsi · Jul 1st 2022

I just did a omv-upgrade on the console and the update process tried to upgrade from 5.16 to 5.18. While compiling the kernel there was an error compiling the zfs module which resulted in no zfs available when booting the new kernel. I could temp fix this by rebooting and selecting the old 5.16, but I am not wondering how I can fix this by getting back into a sane state, either removing that latest update with the 5.18 from my system or retrying the build.

Any help appreciated.

below some errors of the logs. Seems like problems in the build script, so I cam really clueless how to fix this:

Code

/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c: In function 'vdev_bio_set_dev':
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:540:22: error: implicit declaration of function 'vdev_blkg_tryget' [-Werror=implicit-function-declaration]
  540 |  if (q->root_blkg && vdev_blkg_tryget(q->root_blkg))
      |                      ^~~~~~~~~~~~~~~~
In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/umh.h:4,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/kmod.h:9,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/module.h:17,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/atomic.h:27,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:46,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c: In function '__vdev_disk_physio':
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/gfp.h:344:18: warning: passing argument 1 of 'bio_alloc' makes pointer from integer without a cast [-Wint-conversion]
  344 | #define GFP_NOIO (__GFP_RECLAIM)
      |                  ^~~~~~~~~~~~~~~
      |                  |
      |                  unsigned int
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:628:29: note: in expansion of macro 'GFP_NOIO'
  628 |   dr->dr_bio[i] = bio_alloc(GFP_NOIO, bio_max_segs(
      |                             ^~~~~~~~
In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/writeback.h:209,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/memcontrol.h:22,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/swap.h:9,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/vmsystm.h:29,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:48,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/bio.h:423:58: note: expected 'struct block_device *' but argument is of type 'unsigned int'
  423 | static inline struct bio *bio_alloc(struct block_device *bdev,
      |                                     ~~~~~~~~~~~~~~~~~~~~~^~~~
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:628:19: error: too few arguments to function 'bio_alloc'
  628 |   dr->dr_bio[i] = bio_alloc(GFP_NOIO, bio_max_segs(
      |                   ^~~~~~~~~
In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/writeback.h:209,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/memcontrol.h:22,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/swap.h:9,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/vmsystm.h:29,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:48,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/bio.h:423:27: note: declared here
  423 | static inline struct bio *bio_alloc(struct block_device *bdev,
      |                           ^~~~~~~~~


In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/umh.h:4,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/kmod.h:9,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/module.h:17,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/atomic.h:27,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:46,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c: In function 'vdev_disk_io_flush':
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/gfp.h:344:18: warning: passing argument 1 of 'bio_alloc' makes pointer from integer without a cast [-Wint-conversion]
  344 | #define GFP_NOIO (__GFP_RECLAIM)
      |                  ^~~~~~~~~~~~~~~
      |                  |
      |                  unsigned int
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:707:18: note: in expansion of macro 'GFP_NOIO'
  707 |  bio = bio_alloc(GFP_NOIO, 0);
      |                  ^~~~~~~~
In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/writeback.h:209,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/memcontrol.h:22,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/swap.h:9,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/vmsystm.h:29,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:48,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/bio.h:423:58: note: expected 'struct block_device *' but argument is of type 'unsigned int'
  423 | static inline struct bio *bio_alloc(struct block_device *bdev,
      |                                     ~~~~~~~~~~~~~~~~~~~~~^~~~
/var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:707:8: error: too few arguments to function 'bio_alloc'
  707 |  bio = bio_alloc(GFP_NOIO, 0);
      |        ^~~~~~~~~
In file included from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/writeback.h:209,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/memcontrol.h:22,
                 from /usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/swap.h:9,
                 from /var/lib/dkms/zfs/2.1.4/build/include/os/linux/spl/sys/vmsystm.h:29,
                 from /var/lib/dkms/zfs/2.1.4/build/include/sys/zfs_context.h:48,
                 from /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.c:29:
/usr/src/linux-headers-5.18.0-0.bpo.1-common/include/linux/bio.h:423:27: note: declared here
  423 | static inline struct bio *bio_alloc(struct block_device *bdev,
      |                           ^~~~~~~~~
cc1: some warnings being treated as errors
make[5]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:293: /var/lib/dkms/zfs/2.1.4/build/module/zfs/../os/linux/zfs/vdev_disk.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:555: /var/lib/dkms/zfs/2.1.4/build/module/zfs] Error 2
make[3]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/Makefile:1858: /var/lib/dkms/zfs/2.1.4/build/module] Error 2
make[3]: Leaving directory '/usr/src/linux-headers-5.18.0-0.bpo.1-amd64'
make[2]: *** [Makefile:55: modules-Linux] Error 2
make[2]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build/module'
make[1]: *** [Makefile:880: all-recursive] Error 1
make[1]: Leaving directory '/var/lib/dkms/zfs/2.1.4/build'
make: *** [Makefile:741: all] Error 2

Display More

raulfg3 · Jul 1st 2022

please install kernel pluging and install promox kernel , then try again

ryecoaaron · Jul 1st 2022

zfs 2.1.4 doesn't compile on the 5.18 kernel. You will have to wait until zfs 2.1.5 is in the repo. We can't control Debian from doing this. So, as raulfg3 says, use the proxmox kernel.

Tupsi · Jul 2nd 2022

thanks for the explanation guys! Will do the change once I find it again in the new gui! Still trying to figure out where everything is after the change from 5 to 6.

macom · Jul 2nd 2022

That is actually something that has changed. There is now a new "kernel"plugin to install

Quote

The plugin allows the user to select which grub entry to boot from and
installation of the Proxmox kernel. It also allows for the download
and grub entry to boot from the following rescue Linux distros:
- Clonezilla
- GParted Live
- SystemRescue

Display More

Tupsi · Jul 2nd 2022

Quote from macom

That is actually something that has changed. There is now a new "kernel"plugin to install

explains why I did not find it after the upgrade to v6 nicely. It is all done and working again. Only thing left for me is find a way to get rid of that 5.18 kernel. It is still sitting in my grub list. Should I go to the command line for that and uninstall it in the normal debian style with apt or is there a gui option to remove a certain kernel?

macom · Jul 2nd 2022

Quote from Tupsi

Only thing left for me is find a way to get rid of that 5.18 kernel.

Mhm

Tupsi · Jul 2nd 2022

well, thats only for the proxmox stuff right? I just got that installed to get rid of my problem. I was talking about the "normal" kernel which got installed during one of the latest updates before I even had the kernel plugin (and proxmox) installed. But maybe I am looking at this the wrong way. As OMV is ment to make everything easier for the normal home user, it is not ment to be to fizzle around with kernels in the first place, so there is no option to mess with the normal flow of kernel updates. I can respect that. Makes sense in a way. It is more of "nice to have" thing anyway. I have set the proxmox as default kernel now and can just patiently wait until the normal update process kicks the 5.18 kernel out of the system because at some point in the future it will be "the old" which gets automatically deleted anyway.

All good!

macom · Jul 2nd 2022

"Remove non-Proxmox kernels" will remove "normal" kernels.

Tupsi · Jul 2nd 2022

Quote from macom

"Remove non-Proxmox kernels" will remove "normal" kernels.

ohh!!! Reading helps (as usual).

Sorry for me being so dumb, I will try this. Thanks again!!!

Mandroid · Sep 2nd 2022

Hello,

since some weeks ago I also got Errors while installing updates. The problem is to remove the old zfs DKMS files and building the new one. The system is running using Proxmox Kernel, so it seems that building this module is not necessary.

I don't know when and why this started happen, but I know that this erreors has not shown while I am starting using OMV6 with proxmox kernel and ZFS. Any Idea how to remove this error?

Thanks and Regards

Code

Setting up zfs-dkms (2.1.5-1~bpo11+1) ...
Removing old zfs-2.1.5 DKMS files...

------------------------------
Deleting module version: 2.1.5
completely from the DKMS tree.
------------------------------
Done.
Loading new zfs-2.1.5 DKMS files...
Building for 5.15.39-4-pve
Building initial module for 5.15.39-4-pve
configure: error: in `/var/lib/dkms/zfs/2.1.5/build':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
Error! Bad return status for module build on kernel: 5.15.39-4-pve (x86_64)
Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
dpkg: error processing package zfs-dkms (--configure):
 installed zfs-dkms package post-installation script subprocess returned error exit status 10

Display More

latest update fails compiling zfs module (kernel 5.18)

Participate now!

Tags