#1 Global Leader in Data Protection & Ransomware Recovery

Failed to load module [veeamsnap] on Oracle Linux 8 with UEK R7 kernel

KB ID: 4394
Product: Veeam Backup & Replication | 11 | 12 | 12.1
Veeam Agent for Linux | 5.0 | 6.0 | 6.1
Published: 2022-12-21
Last Modified: 2023-12-12
mailbox
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.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Article Applicability

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

For all other situations involving the error "Failed to load module [veeamsnap]", please refer to KB2260.

Challenge

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

 

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

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.

Click to Expand for Veeam Agent for Linux 5.0.2 Pre-Compile Steps
If Veeam Agent for Linux 5.0.2 is installed, and there are no immediate plans to update to Veeam Agent for Linux 6, a hotfix is available for Veeam Agent for Linux 5.0.2. Perform the following steps before proceeding to the rebuild steps.
 
  1. Contact Veeam Technical Support for Veeam Agent for Linux build 5.0.2.4639.

    Note: Veeam Agent for Linux build 5.0.2.4639 is covered under Experimental Support.
  2. Remove current Veeam Agent for Linux 5.0.2.x install.
  3. Install veeam-5.0.2.4639-1.el8.x86_64.rpm and veeamsnap-5.0.2.4639-1.noarch.rpm packages
     

After acquiring and installing Veeam Agent for Linux 5.0.2.4639, proceed with the rebuild steps below.

Rebuilding the VeeamSnap Module

  1. 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.
veeamconfig -v
  1. Make sure the kernel-uek-devel package matching your running kernel is installed:
rpm -qa | grep kernel-uek-devel-$(uname -r)

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
  1. Check dkms status output. veeamsnap/v.x.y.zzzz must have added status:
dkms status

Example output:

[root@localhost ~]# dkms status
veeamsnap/6.1.0.1498: added
  1. 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.
scl enable gcc-toolset-11 -- dkms install -m veeamsnap/v.x.y.zzzz --force
  1. Verify that veeamsnap/v.x.y.zzzz has installed status for the kernel you are running:
uname -r
dkms status

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
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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.