Failed to load module [veeamsnap] on Oracle Linux 8 with UEK R7 kernel
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Challenge
When running Oracle Linux 8 with UEK R7 kernel (5.15+):
[root@localhost ~]# cat /etc/oracle-release Oracle Linux Server release 8.7 [root@localhost ~]# uname -r 5.15.0-4.70.5.2.el8uek.x86_64
Veeam Agent for Linux backup job fails with "Failed to load module [veeamsnap] error":
[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
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:
make.log DKMS make.log for veeamsnap-5.0.2.4627 for kernel 5.15.0-4.70.5.2.el8uek.x86_64 (x86_64) make: Entering directory '/usr/src/kernels/5.15.0-4.70.5.2.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.1.0.2) You are using: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-15.0.1) CC [M] /var/lib/dkms/veeamsnap/5.0.2.4627/build/log.o 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/5.0.2.4627/build/log.o] Error 1 make: *** [Makefile:1974: /var/lib/dkms/veeamsnap/5.0.2.4627/build] Error 2 make: Leaving directory '/usr/src/kernels/5.15.0-4.70.5.2.el8uek.x86_64'
Solution
Tip: Hover over the command blocks below to see the copy to clipboard button.
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-4.70.5.2.el8uek.x86_64
- Check dkms status output. veeamsnap/v.x.y.zzzz must have added status:
Example output:
[root@localhost ~]# dkms status veeamsnap/6.0.0.1060: 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-4.70.5.2.el8uek.x86_64 [root@localhost ~]# dkms status veeamsnap/6.0.0.1060, 5.15.0-4.70.5.2.el8uek.x86_64, x86_64: installed
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.
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.