Why updating (5.10.120-1~bpo10+1) over (5.10.103-1~bpo10+1) wrecked my 2.5Gb Realtek R8125B NIC

  • Don't know why my machine has been offered 5.10.120-1~bpo10+1 (103 and 106 at least is in between) along with a bunch of Nvidia 470 driver/Cuda updates. Tried again installing alone after first attempt with 50+ updates wrecking it so restored a Clonezilla backup image.


    Output was:


    Reading package lists...

    Building dependency tree...

    Reading state information...

    The following additional packages will be installed:

    linux-image-5.10.0-0.bpo.15-amd64

    Suggested packages:

    linux-doc-5.10 debian-kernel-handbook

    Recommended packages:

    apparmor

    The following NEW packages will be installed:

    linux-image-5.10.0-0.bpo.15-amd64

    The following packages will be upgraded:

    linux-image-amd64

    1 upgraded, 1 newly installed, 0 to remove and 57 not upgraded.

    Need to get 0 B/53.6 MB of archives.

    After this operation, 299 MB of additional disk space will be used.

    Selecting previously unselected package linux-image-5.10.0-0.bpo.15-amd64.

    (Reading database ...

    (Reading database ... 5%

    (Reading database ... 10%

    (Reading database ... 15%

    (Reading database ... 20%

    (Reading database ... 25%

    (Reading database ... 30%

    (Reading database ... 35%

    (Reading database ... 40%

    (Reading database ... 45%

    (Reading database ... 50%

    (Reading database ... 55%

    (Reading database ... 60%

    (Reading database ... 65%

    (Reading database ... 70%

    (Reading database ... 75%

    (Reading database ... 80%

    (Reading database ... 85%

    (Reading database ... 90%

    (Reading database ... 95%

    (Reading database ... 100%

    (Reading database ... 154225 files and directories currently installed.)

    Preparing to unpack .../linux-image-5.10.0-0.bpo.15-amd64_5.10.120-1~bpo10+1_amd64.deb ...

    Unpacking linux-image-5.10.0-0.bpo.15-amd64 (5.10.120-1~bpo10+1) ...

    Preparing to unpack .../linux-image-amd64_5.10.120-1~bpo10+1_amd64.deb ...

    Unpacking linux-image-amd64 (5.10.120-1~bpo10+1) over (5.10.103-1~bpo10+1) ...

    Setting up linux-image-5.10.0-0.bpo.15-amd64 (5.10.120-1~bpo10+1) ...

    I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-0.bpo.12-amd64

    I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-0.bpo.12-amd64

    I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-0.bpo.15-amd64

    I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-0.bpo.15-amd64

    /etc/kernel/postinst.d/dkms:

    Error! Your kernel headers for kernel 5.10.0-0.bpo.15-amd64 cannot be found.

    Please install the linux-headers-5.10.0-0.bpo.15-amd64 package,

    or use the --kernelsourcedir option to tell DKMS where it's located

    Error! Your kernel headers for kernel 5.10.0-0.bpo.15-amd64 cannot be found.

    Please install the linux-headers-5.10.0-0.bpo.15-amd64 package,

    or use the --kernelsourcedir option to tell DKMS where it's located

    Error! Your kernel headers for kernel 5.10.0-0.bpo.15-amd64 cannot be found.

    Please install the linux-headers-5.10.0-0.bpo.15-amd64 package,

    or use the --kernelsourcedir option to tell DKMS where it's located

    /etc/kernel/postinst.d/initramfs-tools:

    update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.15-amd64

    /etc/kernel/postinst.d/zz-update-grub:

    Generating grub configuration file ...

    Found linux image: /boot/vmlinuz-5.10.0-0.bpo.15-amd64

    Found initrd image: /boot/initrd.img-5.10.0-0.bpo.15-amd64

    Found linux image: /boot/vmlinuz-5.10.0-0.bpo.12-amd64

    Found initrd image: /boot/initrd.img-5.10.0-0.bpo.12-amd64

    Found linux image: /boot/vmlinuz-5.10.0-0.bpo.9-amd64

    Found initrd image: /boot/initrd.img-5.10.0-0.bpo.9-amd64

    done

    Setting up linux-image-amd64 (5.10.120-1~bpo10+1) ...


    Rebooted and bam, no Eth0. Didn't look any logs etc. on console before restoring and now researching.


    Not updating to OMV 6.x at this stage. Still running current latest OMV 5.x on Debian 10.

    Wanted it back online for Plex in Docker, kids school holidays etc. Won't be so pressed at least next week.


  • Rebooted and bam, no Eth0. Didn't look any logs etc. on console before restoring and now researching.

    Recommendation is to use a USB stick for OS, this way in case of errors, plugging the old one back gets you up and running in no time and allows for debugging reasons of error during upgrade.

    Your issue might be related to a bug in apt package manager discussed here

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

  • chente

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!