Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing Active Backup for Business Agent 100% * current installing folder is /tmp/selfgz2612 Hit:1 https://mirrors.tuna.tsinghua.edu.cn/debian bookworm InRelease Get:2 https://mirrors.tuna.tsinghua.edu.cn/debian bookworm-updates InRelease [55.4 kB] Hit:3 https://mirrors.tuna.tsinghua.edu.cn/debian-security bookworm-security InRelease Hit:4 https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/debian bookworm InRelease Hit:5 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64 InRelease Fetched 55.4 kB in 2s (36.7 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 47 packages can be upgraded. Run 'apt list --upgradable' to see them. * start checking dependency of (3) * checking linux-headers-6.1.0-38-amd64 * linux-headers-6.1.0-38-amd64 has already installed * checking dkms * dkms has already installed * checking make * make has already installed * start installing snapshot driver and agent service * snapshot driver has not installed, installing snapshot driver * installing synosnap-0.11.6.deb Selecting previously unselected package synosnap. (Reading database ... 98146 files and directories currently installed.) Preparing to unpack synosnap-0.11.6.deb ... Unpacking synosnap (0.11.6) ... Setting up synosnap (0.11.6) ... Loading new synosnap/0.11.6 DKMS files... Deprecated feature: CLEAN (/usr/src/synosnap-0.11.6/dkms.conf) Building for 6.1.0-37-amd64 and 6.1.0-38-amd64
Building initial module synosnap/0.11.6 for 6.1.0-37-amd64 Deprecated feature: CLEAN (/var/lib/dkms/synosnap/0.11.6/source/dkms.conf) Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub
Running the pre_build script...(bad exit status: 1) Failed command: cd /var/lib/dkms/synosnap/0.11.6/build/ && /var/lib/dkms/synosnap/0.11.6/build/genconfig.sh 6.1.0-37-amd64 Consult /var/lib/dkms/synosnap/0.11.6/build/make.log for more information. dpkg: error processing package synosnap (--install): installed synosnap package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: synosnap * failed to install snapshot driver * Please review the highlighted information above. ********************************************************************** * Please check if your distro / kernel version is supported in detail at * https://sy.to/abb_requireandlimit * or the "System requirement" part in README.md **********************************************************************
# Use standard location at the /boot [ ! -f "$SYSTEM_MAP_FILE" ] && SYSTEM_MAP_FILE="/boot/System.map-${KERNEL_VERSION}" if [ ! -f "$SYSTEM_MAP_FILE" ] || [ $(cat"$SYSTEM_MAP_FILE" | wc -l) -lt 10 ]; then # The build is running on Debian 11+. File /boot/System.map-${KERNEL_VERSION} exists, but it # contains just a single line. # Maybe package linux-image-$(uname -r)-dbg is installed... SYSTEM_MAP_FILE="/usr/lib/debug/boot/System.map-${KERNEL_VERSION}"
if [ ! -f "$SYSTEM_MAP_FILE" ] then # Detect if runing kernel version and `uname -r` are different, which meaning an upgrade is on-going RUNNING_KERNEL_VERSEION="$(cat /proc/version | sed 's|^Linux\ version\ \([^ ]\+\)\ .*|\1|g')" if [ "${RUNNING_KERNEL_VERSEION}" != "${KERNEL_VERSION}" ] then # No valid SystemMap found and /proc/kallsyms not usable becuase it's upgrade, so we make build fail echo_highlight "* System map at /boot/System.map-${KERNEL_VERSION} does not contain valid symbol table, and " echo_highlight "* we are trying to install synosnap driver for a differnt kernel than the one currently running." echo_highlight "* Synosnap driver will encounter error during installation." echo_highlight "* We will try to install/build driver when next booting into new kernel." echo_highlight "* After rebooting into the new kernel, if the backup process still fails," echo_highlight "* please uninstall and reinstall Active Backup for Business Linux Agent."
exit 1 fi fi
# For non-upgrading case, we can use /proc/kallsyms for target kernel systemmap because it's the same as current one # Use fallback option [ ! -f "$SYSTEM_MAP_FILE" ] && SYSTEM_MAP_FILE="/proc/kallsyms" fi
结合上文中详细的构建日志：
/var/lib/dkms/synosnap/0.11.6/build/make.log
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
DKMS (dkms-3.2.1) make.log for synosnap/0.11.6 for kernel 6.1.0-37-amd64 (x86_64) Tue Aug 19 05:04:34 PM CST 2025
Running the pre_build script # command: cd /var/lib/dkms/synosnap/0.11.6/build/ && /var/lib/dkms/synosnap/0.11.6/build/genconfig.sh 6.1.0-37-amd64 [0;31m[43m* System map at /boot/System.map-6.1.0-37-amd64 does not contain valid symbol table, and [0m [0;31m[43m* we are trying to install synosnap driver for a differnt kernel than the one currently running.[0m [0;31m[43m* Synosnap driver will encounter error during installation.[0m [0;31m[43m* We will try to install/build driver when next booting into new kernel.[0m [0;31m[43m* After rebooting into the new kernel, if the backup process still fails,[0m [0;31m[43m* please uninstall and reinstall Active Backup for Business Linux Agent.[0m
