datto / dattobd

kernel module for taking block-level snapshots and incremental backups of Linux block devices
GNU General Public License v2.0
575 stars 122 forks source link

dattobd on debian10 (n proxmox vm ) - Failed to find module 'dattobd' #384

Open nonvwvnon opened 2 months ago

nonvwvnon commented 2 months ago

install from repos and get the following error Failed to find module 'dattobd'

$ modprobe dattobd modprobe: FATAL: Module dattobd not found in directory /lib/modules/5.3.13-1-pve


$ apt-get install dattobd-dkms dattobd-utils

Preparing to unpack .../13-linux-headers-amd64_4.19+105+deb10u22_amd64.deb ... Unpacking linux-headers-amd64 (4.19+105+deb10u22) ... Setting up linux-compiler-gcc-8-x86 (4.19.316-1) ... Setting up linux-kbuild-4.19 (4.19.316-1) ... Setting up libfile-fcntllock-perl (0.22-3+b5) ... Setting up libalgorithm-diff-perl (1.19.03-2) ... Setting up dattobd-dkms (0.11.8-32.1debian10) ... Loading new dattobd-0.11.8 DKMS files... Building for 5.3.13-1-pve Module build for kernel 5.3.13-1-pve was skipped since the kernel headers for this kernel does not seem to be installed. Setting up libfakeroot:amd64 (1.23-1) ... Setting up fakeroot (1.23-1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode Setting up libdattobd1 (0.11.8-32.1debian10) ... Setting up dattobd-utils (0.11.8-32.1debian10) ... Configuring initramfs, please wait... update-initramfs: deferring update (trigger activated) Setting up linux-headers-4.19.0-27-common (4.19.316-1) ... Setting up libalgorithm-diff-xs-perl (0.04-5+b1) ... Setting up libalgorithm-merge-perl (0.08-3) ... Setting up libstdc++-8-dev:amd64 (8.3.0-6) ...

Setting up linux-headers-4.19.0-27-amd64 (4.19.316-1) ... /etc/kernel/header_postinst.d/dkms: grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory grep: /usr/lib/debug/boot/System.map-4.19.0-27-amd64: No such file or directory Job for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details. Setting up linux-headers-amd64 (4.19+105+deb10u22) ... Setting up g++-8 (8.3.0-6) ... Setting up g++ (4:8.3.0-1) ... update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode Setting up build-essential (12.6) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10) ... Processing triggers for initramfs-tools (0.133+deb10u1) ... update-initramfs: Generating /boot/initrd.img-5.3.13-1-pve cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. Running hook script 'zz-pve-efiboot'.. Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace.. No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.

$ systemctl status systemd-modules-load.service ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2024-09-11 13:11:25 CEST; 1min 42s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 6504 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 6504 (code=exited, status=1/FAILURE)

Sep 11 13:11:25 host systemd[1]: Starting Load Kernel Modules... Sep 11 13:11:25 host systemd-modules-load[6504]: Failed to find module 'dattobd' Sep 11 13:11:25 host systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Sep 11 13:11:25 host systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Sep 11 13:11:25 host systemd[1]: Failed to start Load Kernel Modules.

iamandrii commented 2 months ago

Hi @nonvwvnon! Thanks for your feedback.

As I see, you have two kernels installed on your system: 5.3.13-1-pve and 4.19.0-27-amd64. And from logs, you are using 5.3.13-1-pve.

This kernel is distributed by Proxmox and as I see, the problem is related to lack of kernel development headers. According to Proxmox Forums, you can install headers using command:

sudo apt install pve-headers-$(uname -r)

After that, you'd have to install dattobd, as right now it is not installed due to the problem, the easiest way is to use dkms, so just run the following command:

sudo dkms install dattobd/0.11.8 -k $(uname -r)

After that just insert the module:

modprobe dattobd

Please, keep me in touch in case of any troubles.. and have a nice day 🙂