Just want to confirm that, after updating to 6.1.1 and having a spook this morning, tweaking PKGBUILD to zfs 2.1.7 did the trick on my end as well. (you will need to do the same for zfs-utils and install both at the same time)
Search Criteria
Package Details: zfs-dkms 2.3.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
---|---|
Package Base: | zfs-dkms |
Description: | Kernel modules for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Provides: | SPL-MODULE, zfs, ZFS-MODULE |
Submitter: | isiachi |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 188 |
Popularity: | 2.27 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-05-03 09:40 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 66 Next › Last »
VileLasagna commented on 2022-12-22 18:57 (UTC)
gromit commented on 2022-12-22 16:09 (UTC)
PSA: This package does not build the latest kernel (6.1.1-arch1-1)!
==> dkms install --no-depmod zfs/2.1.6 -k 6.1.1-arch1-1
fgrep: warning: fgrep is obsolescent; using grep -F
Error! Bad return status for module build on kernel: 6.1.1-arch1-1 (x86_64)
Consult /var/lib/dkms/zfs/2.1.6/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.6 -k 6.1.1-arch1-1' exited 10
Manually upgrading the PKGBUILD
to use the latest version (at the time its 2.1.7) solved the problem for me :)
etrigan63 commented on 2022-12-22 16:00 (UTC)
Kernel 6.1.1 is out. Will 2.1.7 support it? My system updated to the new kernel and the zfs-dkms modules failed to install properly. I have not rebooted in order to keep my backup array (the only ZFS I have) online.
HMich commented on 2022-11-14 19:58 (UTC) (edited on 2022-11-14 19:58 (UTC) by HMich)
thanks yurikoles
I see, I tried them too, I will try again soon I find some time
meanwhile I compiled openzfs git 2.1.99 and it installed and works just fine with kernel 6.0.8
yurikoles commented on 2022-11-14 14:35 (UTC) (edited on 2022-11-14 14:37 (UTC) by yurikoles)
Dear Michael,
This AUR page is for zfs-dkms
, please report issue with archzfs' zfs-dkms-git
to them. I fixed this issue in AUR's zfs-dkms-git
, but according to package versions, you are using archzfs' one.
HMich commented on 2022-11-14 12:20 (UTC)
there seems something wrong wit zfs for kernel 6.0.8
it doesn't matter if I install zfs-dkms zfs-utils or any of the respective git packages
this moment I am with zfs-dkms-git 2022.11.10.r8214.g9f4ede63d2-1 zfs-utils-git 2022.11.10.r8214.g9f4ede63d2-2
no compile error, no mkinit build error zfs.ko loads with no error, but any operation with zfs or zpool returns the sme error
zfs: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory zpool: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
any lib sym link magic doesn't work either
lucky me, I'm not on zfs root, I just mount remote pools on this machine if somebody has an idea, that would be nice, thanks
fryfrog commented on 2022-11-06 22:07 (UTC)
iio7: In a completely unsurprising, non-twist... building both aur/zfs-utils and aur/zfs-dkms on an updated system results in a zfs
module that loads fine and zfs
and zpool
commands that also work. This host does not use zfs, so it was not installed at all to start with.
iio7 commented on 2022-11-06 20:41 (UTC)
Not any more people posting is a really bad measurements for when a problem exists or not. Test it out yourself, don't use archzfs, they are not on the same version.
zfs-dkms 2.1.6-1 require libcrypto.so.1.1 which clearly is no longer present on the system.
fryfrog commented on 2022-11-06 20:28 (UTC)
They why aren't more people posting here w/ broken zfs? I use archzfs, but mine is fine. I had a few packages that gave the error you're referencing (eternal terminal and paru), but a re-compile fixed both of them. Clearly archzfs repo itself re-build zfs-utils, but my zfs-dkms builds after the openssl upgrade because I mask kernel upgrades.
I really think you're not re-compiling zfs-utils and/or the zfs dkms kernel module.
iio7 commented on 2022-11-06 20:21 (UTC)
I am compiling by hand, no helper. But it seems like systemd-cryptsetup are having problems too since the upgrade of openssl. https://bugs.archlinux.org/task/76440
Looks like the upgrade to openssl3 breaks anything that depends on libcrypto.so.1.1 or libssl.so.1.1
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, as declared in the META file.
Options if your Linux kernel's version is not within that range:
1) Switch to another Linux kernel, such as
linux-lts
.2) Prevent your kernel package from upgrading to an unsupported version until OpenZFS increases the maximum supported kernel version.
3) Modify this package to support your kernel by patching it on your local machine.
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)