You can assume that filesystem blocks are corrupted on their way to -and from USB device. Maybe look ate the syslogfile in detail as binary, then you will see.
What I see from dmesg is that an old kernel is used, it is not Bookworm. Typical case of in-place upgrade from old pre-bookworm to bookworm.
In Rasberry Pi OS Bookworm and later, kernel and firmware package names are changed and they are not automatically installed when doing Debian compliant in-place upgrade. You have to do it manually, including changes in fstab and config.txt
If you can handle Linux issues with packages etc yourself and have an other Linux computer as extra in case those manual changes would fail somehow, you can fix it. I just need a final reboot to activate newly installed kernel and firmware.
You can look into a Raspbian Bookworm image how things should be. In short
- mount bootpartition in rootfs /boot/firmware, so unmount and create dir and remount
- install raspi-firmware and linux-image-rpi-v7
- change statements in config.txt, minimum is:- reboot
- remove old firmware and kernel packages, that might wipe files in boot partition, so check and re-install raspi-firmware package to fix it.
For an RPi3, I would not use 32-bit, but 64-bit and even just standard Debian Trixie, this is what I use. That should rewrite config.txt and cmdline.txt for you, so less manual fixes.
What I see from dmesg is that an old kernel is used, it is not Bookworm. Typical case of in-place upgrade from old pre-bookworm to bookworm.
In Rasberry Pi OS Bookworm and later, kernel and firmware package names are changed and they are not automatically installed when doing Debian compliant in-place upgrade. You have to do it manually, including changes in fstab and config.txt
If you can handle Linux issues with packages etc yourself and have an other Linux computer as extra in case those manual changes would fail somehow, you can fix it. I just need a final reboot to activate newly installed kernel and firmware.
You can look into a Raspbian Bookworm image how things should be. In short
- mount bootpartition in rootfs /boot/firmware, so unmount and create dir and remount
- install raspi-firmware and linux-image-rpi-v7
- change statements in config.txt, minimum is:
Code:
root@raspi1:~# cat /boot/firmware/config.txt # For more options and information see# http://rptl.io/configtxt redirects to https://www.raspberrypi.com/documentation/computers/config_txt.html# kernel and initrdarm_64bit=0auto_initramfs=1- remove old firmware and kernel packages, that might wipe files in boot partition, so check and re-install raspi-firmware package to fix it.
For an RPi3, I would not use 32-bit, but 64-bit and even just standard Debian Trixie, this is what I use. That should rewrite config.txt and cmdline.txt for you, so less manual fixes.
Statistics: Posted by redvli — Wed Dec 31, 2025 1:31 pm