| 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: | 179 |
| Popularity: | 6.41 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2024-09-05 04:42 (UTC) |
I'm getting a build error on the latest system update:
==> dkms install zfs/0.8.3 -k 5.6.8-arch1-1
Error! Bad return status for module build on kernel: 5.6.8-arch1-1 (x86_64)
Consult /var/lib/dkms/zfs/0.8.3/build/make.log for more information.
Any suggestions on how to proceed?
The log file does not seem to exist, BTW.
Cheers and good to know about LTS. On a test rig, I released gcc and gcc-libs, did a full update but no newer versions were installed. I took the plunge and upgraded the kernel, rebuilt zfs-dkms with that 5.6 kernel running, rebooted, did a modprobe zfs and all was well. Many thanks to all for the assist.
I think you want to be running the same gcc/glibc that your kernel was built with. Normally, that just means keeping current. I would release gcc and gcc-libs and update. Then update your kernel. Then if zfs-dkms isn't latest, update and let it build for your newly updated kernel.
FWIW, I have both linux and linux-lts installed and my archzfs/zfs-dkms builds just fine.
I get adding the key, really I do :-) It's just that during my testing, on a 5.5 kernel I'm using, I cannot build this with the 'horrible but quick test hack' makepkg --skippgpcheck. On a 5.6 kernel, it builds just fine. This of course might all be me, so I wanted to highlight that when we had the zfs issues with moving to kernel 5.5 from 5.4, I know we had to keep the gcc versions in line with the kernel. Since the 5.6 issue was raised, I've had the follow in my pacman.conf
IgnorePkg=linux linux-headers gcc gcc-libs
As a workaround, I was considering removing zfs-dkms from my 5.5 main desktop as I can just about manage with it in the short term. Then upgrading to 5.6 and finally popping zfs-dkms back in again. I'd prefer to be able to upgrade other, older 5.5 kernel machines without doing those steps, but if that's the best way forward to upgrade, I'm happy to do that. Any thoughts appreciated.
Thanks for the help, in my case I get:
==> Verifying source file signatures with gpg...
zfs-0.8.3.tar.gz ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!
If I use --skippgpcheck, the resulting build gives:
libtoolize: copying file 'config/lt~obsolete.m4'
configure:24227: error: possibly undefined macro:
ZFS_AC_KERNEL_SRC_BLKG_TRYGET
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure:41387: error: possibly undefined macro: ZFS_AC_KERNEL_BLKG_TRYGET
autoreconf: /usr/bin/autoconf failed with exit status: 1
==> ERROR: A failure occurred in prepare().
Aborting...
This is with 5.5.13-arch2-1 that is up to date.
@ck2katAUR - zfs working fine for me in 5.6.3.a-1-hardened
@eschwartz; Thank you for your comment. Based on this I've just done a; git pull and a; makepkg with linux-hardened 5.6.3.a-1. No errors were reported and now my server is back in action again. @itoffshore and @fryfrog; Thank you also for your comments. Recognising and respecting eschwartz as the maintainer of this package, I waited for his words before trying anything. Kernel version 5.6.4 and its varieties are evidently coming through the repo system as I write. I will check for comments here (hopefully indicating OK) before upgrading again.
@dmshimself: The package builds fine. Are you encountering this error? https://aur.archlinux.org/packages/zfs-dkms/?O=10&PP=10#comment-735021
I'm getting a PGP check failure when trying to apply a makepkg
Pinned Comments
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
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)