Failed to load module [veeamsnap] (For pre 5.8 kernels)
| KB ID: | 2260 |
| Product: | Veeam Agent for Linux 5.0, Veeam Agent for Linux 4.0, Veeam Agent for Linux 3.0 |
| Published: | 2017-03-13 |
| Last Modified: | 2021-08-26 |
Challenge
Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]Cause
This error occurs when the veeamsnap module cannot be loaded. The most common reasons are:
- The module is not installed
- The installed module is not compatible
- DKMS was unable to compile the module
- The kernel headers package is missing.
- The kernel headers version and the running kernel version mismatch.
- Loading 3rd party kernel modules are not allowed
Solution
About the veeamsnap kernel module
The veeamsnap module is available to be compiled using DKMS or as a pre-compiled module for select distros (kmod for RHEL/CentOS* or kmp for SLES/openSUSE).
For more information about installation requirements please see: Veeam Agent for Linux - System Requirements.
*Precompiled veeamsnap kmod not compatible with Oracle Linux.
Check if veeamsnap prerequisites for RHEL/CentOS 7.0+ are present
For RHEL/CentOS 7.0+ using Veeam Agent for Linux version 4+, ensure that the python3 package is installed and working correctly. If it is not, install/fix it before proceeding with troubleshooting. Python3 is used to automatically load the correct pre-compiled veeamsnap version into the kernel.
Run the following command to query which python3 version is installed:
python3 --version# python3 --version
Python 3.6.8Check if veeamsnap kernel module is installed
Use the following command to determine if the veeamsnap module is installed:
Check if veeamsnap kernel module is loaded
Use the following command to query the state of the veeamsnap module:
lsmod | grep veeamsnapmodprobe -r veeamsnapChecking veeamsnap precompiled module compatibility
Each precompiled veeamsnap module is built for a specific version of RHEL/CentOS/SLES/openSUSE.
Use the examples below to check if the correct precompiled veeamsnap module is installed.
Troubleshooting DKMS failing to compile veeamsnap module
When using DKMS to compile the kernel module, ensure that the installed kernel-headers package matches the kernel in use. If the kernel-headers package is not installed, or the installed kernel-headers package does not match the kernel in use, you will need to install the matching kernel-headers package.
After installing/updating the kernel-headers package, reinstall Veeam Agent for Linux.
Examples of Matching kernel-headers and kernel:
Using veeamsnap module with Secure Boot
If secure boot is enabled, the kernel module may not be loaded due to system restrictions. In such a situation review the following:
- For the pre-compiled veeamsnap module (kmod/kmp) the veeamsnap-ueficert package containing the module key must be enrolled using mokutil to allow the module to load.
Please refer to the User Guide for instructions.
- For DKMS compiled modules there is no such package as it is not possible to automatically sign non-precompiled modules. In this case, you must either sign the module yourself and enroll the key to your system, or disable Secure Boot.
More information
If the information in this article does not resolve the issue, please open a support case and include the following information.
Run each line individually as root, and save the output.
Note: Some commands may return an empty response, be sure to include these results.
(hostnamectl||uname -a)
cat /etc/*release
(rpm -qa||dpkg-query -l) | egrep -i '(veeam|dkms|kernel-headers|kernel.*devel|linux-image|linux-headers)' | sort
dkms status
mokutil --sb-state
mokutil --list-new
find /lib/modules -name '*veeam*' -exec ls -ld {} +
lsmod | grep -i veeam
modinfo veeamsnap
modprobe -vvv veeamsnap| KB ID: | 2260 |
| Product: | Veeam Agent for Linux 5.0, Veeam Agent for Linux 4.0, Veeam Agent for Linux 3.0 |
| Published: | 2017-03-13 |
| Last Modified: | 2021-08-26 |
Couldn't find what you were looking for?
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
