Failed to load module [veeamsnap] on Oracle Linux 8 with UEK R7 kernel
This article is specifically regarding Oracle Linux 8 with UEK R7 kernel (5.15+):
[root@localhost ~]# cat /etc/os-release PRETTY_NAME="Oracle Linux Server 8.9"
[root@localhost ~]# uname -r 5.15.0-200.131.27.1.el8uek.x86_64
A similar issue may occur for Oracle Linux 9 with UEK R8 Kernel, reference KB4732.
For all other situations involving the error "Failed to load module [veeamsnap]", please refer to KB2260.
Challenge
A Veeam Agent for Linux 6.x backup job fails with:
[error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/lo... [error] Processing finished with errors
A Veeam Agent for Linux 13.x backup job fails with:
[error] Veeam snapshot kernel module not found [error] Is Secure Boot enabled? Check that Veeam UEFI certificate is installed [error] Was DKMS used? Check that the linux-headers or kernel-devel packages for the current kernel are installed
Deployment of Veeam Agent for Linux from the Veeam Backup & Replication console fails with the error:
Failed to install Veeam Agent for Linux: Failed to install agent: non-matching package versions
Cause
UEK R7 is built with GCC 11, while Oracle Linux 8 ships GCC 8.5. This causes veeamsnap kernel module build failure because DKMS uses GCC 8.5:
[root@localhost ~]# cat /var/lib/dkms/veeamsnap/6.1.0.1498/build/make.log DKMS make.log for veeamsnap-6.1.0.1498 for kernel 5.15.0-200.131.27.1.el8uek.x86_64 (x86_64) Wed Dec 6 12:03:39 EST 2023 make: Entering directory '/usr/src/kernels/5.15.0-200.131.27.1.el8uek.x86_64' warning: the compiler differs from the one used to build the kernel The kernel was built by: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9.2.0.1) You are using: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-20.0.1) CC [M] /var/lib/dkms/veeamsnap/6.1.0.1498/build/log.o CC [M] /var/lib/dkms/veeamsnap/6.1.0.1498/build/mem_alloc.o gcc: error: unrecognized command line option '-ftrivial-auto-var-init=zero' gcc: error: unrecognized command line option '-ftrivial-auto-var-init=zero' gcc: error: unrecognized command line option '-fzero-call-used-regs=used-gpr' make[1]: *** [scripts/Makefile.build:288: /var/lib/dkms/veeamsnap/6.1.0.1498/build/log.o] Error 1 make[1]: *** Waiting for unfinished jobs.... gcc: error: unrecognized command line option '-fzero-call-used-regs=used-gpr' make[1]: *** [scripts/Makefile.build:288: /var/lib/dkms/veeamsnap/6.1.0.1498/build/mem_alloc.o] Error 1 make: *** [Makefile:1986: /var/lib/dkms/veeamsnap/6.1.0.1498/build] Error 2 make: Leaving directory '/usr/src/kernels/5.15.0-200.131.27.1.el8uek.x86_64
Solution
Summary
This article will guide you through rebuilding the veeamsnap module using Software Collection (SCL) for GCC 11. SCL for GCC 11, which is shipped with UEK R7 kernel.
Rebuilding the VeeamSnap Module
- Check the version of Veeam Agent for Linux that is installed using the following command:
Take note of the build number that is installed, it will be referred to in later steps as v.x.y.zzzz.
- Make sure the kernel-uek-devel package matching your running kernel is installed:
Example output:
[root@localhost ~]# rpm -qa | grep kernel-uek-devel-$(uname -r) kernel-uek-devel-5.15.0-200.131.27.1.el8uek.x86_6
- Check dkms status output. veeamsnap/v.x.y.zzzz must have added status:
Example output:
[root@localhost ~]# dkms status veeamsnap/6.1.0.1498: added
- Build veeamsnap/v.x.y.zzzz with dkms using GCC 11 SCL:
Replace v.x.y.zzzz with the installed build number from Step 1.
- Verify that veeamsnap/v.x.y.zzzz has installed status for the kernel you are running:
Example output:
[root@localhost ~]# uname -r 5.15.0-200.131.27.1.el8uek.x86_64
[root@localhost ~]# dkms status veeamsnap/6.1.0.1498, 5.15.0-200.131.27.1.el8uek.x86_64, x86_64: installed
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.