DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# dpkg --configure -a
Setting up linux-headers-4.19.0-0.bpo.9-amd64 (4.19.118-2+deb10u1~bpo9+1) ...
/etc/kernel/header_postinst.d/dkms:
configure: error: unknown
Error! Bad return status for module build on kernel: 4.19.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information.
^CFailed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-4.19.0-0.bpo.9-amd64.postinst line 11.
dpkg: error processing package linux-headers-4.19.0-0.bpo.9-amd64 (--configure):
subprocess installed post-installation script returned error exit status 255
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.19.0-0.bpo.9-amd64-unsigned (4.19.118-2+deb10u1~bpo9+1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-0.bpo.9-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-0.bpo.9-amd64
/etc/kernel/postinst.d/dkms:
configure: error: unknown
Error! Bad return status for module build on kernel: 4.19.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information.
^Cdpkg: error processing package linux-image-4.19.0-0.bpo.9-amd64-unsigned (--configure):
subprocess installed post-installation script was interrupted
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-3-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda1
cryptsetup: WARNING: could not determine root device from /etc/fstab
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?)
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-headers-4.19.0-0.bpo.9-amd64
linux-image-4.19.0-0.bpo.9-amd64-unsigned
initramfs-tools
I am particularly concerned with these two lines:
Code:
I: /vmlinuz is now a symlink to boot/vmlinuz-4.19.0-0.bpo.9-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.19.0-0.bpo.9-amd64
Distribution: Ubuntu based stuff for the most part
Posts: 1,177
Rep:
A quick search of the first error
Quote:
Error! Bad return status for module build on kernel: 4.19.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information.
Support for Debian 9 Stretch ended last year and the kernel you are trying to install is for Debian 10.
If the system will not boot with the new kenrnel, then select the old kenrnel in teh grub menu and boot into that and remove the new kernel and headers.
What? No, I am not using ZFS. But I think I have some ZFS related package installed...
Just checked, yes, I have a zfs module running. I tested it in a loopback file system a few days ago, but I don't have that anymore. I'm not really using it.
But the module is loaded and I can't unload it, rmmod says 'rmmod: ERROR: Module zfs is in use'
OK, I think I unloaded it with rmmod -f but the error with 'dpkg --configure -a' still happens.
And now I can't even run synaptic and manage my packages because something is broken. Synaptic tells me I have to run 'dpkg --configure -a' but that command never completes, it prints out the error and hangs indefinitely.
Quote:
Originally Posted by uteck
Support for Debian 9 Stretch ended last year and the kernel you are trying to install is for Debian 10.
If the system will not boot with the new kenrnel, then select the old kenrnel in teh grub menu and boot into that and remove the new kernel and headers.
This time the command returned after a long time. But it seems to be very upset.
Code:
# dpkg --configure -a
Setting up initramfs-tools (0.130) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.19.0-0.bpo.9-amd64-unsigned (4.19.118-2+deb10u1~bpo9+1) ...
/etc/kernel/postinst.d/dkms:
configure: error: unknown
Error! Bad return status for module build on kernel: 4.19.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information.
configure: error:
*** Please make sure the kmod spl devel <kernel> package for your
*** distribution is installed then try again. If that fails you
*** can specify the location of the spl objects with the
*** '--with-spl-obj=PATH' option.
Error! Bad return status for module build on kernel: 4.19.0-0.bpo.9-amd64 (x86_64)
Consult /var/lib/dkms/zfs/0.6.5.9/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.9-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda1
cryptsetup: WARNING: could not determine root device from /etc/fstab
/etc/kernel/postinst.d/zz-runlilo:
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
dpkg: error processing package linux-image-4.19.0-0.bpo.9-amd64-unsigned (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.9-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda1
cryptsetup: WARNING: could not determine root device from /etc/fstab
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?)
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-4.19.0-0.bpo.9-amd64-unsigned
initramfs-tools
I still don't know what to do. This is all Greek to me.
Please note that those lines regarding "missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169" have been around for many months, possibly more than one year.
Well, the log says,
Code:
DKMS make.log for spl-0.6.5.9 for kernel 4.19.0-0.bpo.9-amd64 (x86_64)
Tue Jul 25 00:20:30 -03 2023
make: *** No targets specified and no makefile found. Stop.
So I checked this spl thing and found it's also related to ZFS. Sheesh, what a nuisance. But I managed to purge it.
Running dpkg --configure -a again:
Code:
dpkg --configure -a
Setting up linux-image-4.19.0-0.bpo.9-amd64-unsigned (4.19.118-2+deb10u1~bpo9+1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.9-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda1
cryptsetup: WARNING: could not determine root device from /etc/fstab
/etc/kernel/postinst.d/zz-runlilo:
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
dpkg: error processing package linux-image-4.19.0-0.bpo.9-amd64-unsigned (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-0.bpo.9-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda1
cryptsetup: WARNING: could not determine root device from /etc/fstab
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?)
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-4.19.0-0.bpo.9-amd64-unsigned
initramfs-tools
Distribution: Ubuntu based stuff for the most part
Posts: 1,177
Rep:
Code:
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?
Do you have NFS or RAID mounted?
I looked at the link you posted for the download, and linux-image-4.19.0-0.bpo.9-amd64-unsigned_4.19.118-2+deb10u1~bpo9+1_amd64.deb was released in 2020-06-15 11:12. So it is still 3 years out of date as that is when they stopped supplying backports to that version of Debian. Nothing in that directory is past 2020.
Fatal: Trying to map files from unnamed device 0x0014 (NFS/RAID mirror down ?
Do you have NFS or RAID mounted?
No, I don't.
Quote:
Originally Posted by uteck
I looked at the link you posted for the download, and linux-image-4.19.0-0.bpo.9-amd64-unsigned_4.19.118-2+deb10u1~bpo9+1_amd64.deb was released in 2020-06-15 11:12. So it is still 3 years out of date as that is when they stopped supplying backports to that version of Debian. Nothing in that directory is past 2020.
It's still in the Stretch repository. It was always there, but one or two of the packages became unavailable from Synaptic (image or header, can't remember) not too long ago so now I get things from there.
I have both vmlinuz-4.19.0-0.bpo.9-amd64 and initrd.img-4.19.0-0.bpo.9-amd64 in my /boot directory so I guess it's installed to some extent. Not sure how much or how well.
I have two concerns now:
1. apt-get still has dirty output and some problem with initramfs.
2. I'm afraid booting with the new kernel will render the Btrfs file system unmountable by the old kernel. I've been told a newer Btrfs kernel implementation may "taint" a Btrfs and make it incompatible with an older kernel. I certainly know I cannot mount a Btrfs created with a 5.18 kernel from the current 4.9 kernel installation.
BTRFS support is really solid in kernel version 6. IT was not bad at the back half of version 5. It was there in versions 3 (late) and 4 since 2009, but at an early and unstable level. Why would you want to go back to an unsupported kernel while using a rapidly developing filesystem?
What is it you are not telling us?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.