I have been chasing my tail on this all day.
I had a working install on a RPI5 a PI OS lite 64 bit that supported a Radxa 5 port SATA hat, a USB 3 OS BOOT, OpenMediaVault, samba shares, yada yada yada. OMV had been nagging me to install updates so I finally did it and the system would not reboot. I couldn't even see the headless text on a connected HDMI monitor. Without a OMV backup I could salvage, yeah I know, I started from scratch and got the system back up and running. This was about 2 months ago. Then the nagging updates again, although THIS TIME I have been holding off, then today I backed up my OMV to a safe place and went after the update. Guess what? System hosed again.
So now I am taking my time slowly, writing in a blog each step I take, making sure I do not miss anything, and I was at the point where my OS was booting from the USB drive but the partition was taking all 500gb of the NVME space. But before I went after resizing the file system and then resizing the partition, and then installing OMV, I decided to go after apt-get update && apt-get upgrade and sure enough, it is hose yet again. I didn't lose anything this time. I haven't even installed OMV 7 yet. And I KNOW that there are two different header and firmware packages usually kept back (not held back this time though)...They just went right ahead and tried to install instead of being held back. Not sure why. And sure enough, the OS is hosed again.
At least this time, I was able to capture the apt upgrade results. Can anyone help me figure out what the heck I am doing wrong? The 1st of these 3 installs went like clock work until apt-get showed those four packages. Then the wheels came off big time.
Strange thing, before this last failed attempt, I decided to stay with an SD card to see what would happen with installing those held packages, both individually and then both. As expected, after apt-get update and apt-get upgrade I also encountered those four packages which at that time were actually held back. I decided to install the 2712 version (headers and image) and it worked fine. And the other two packages disappeared. So why did it behave that way using an SD CARD and differently with an OS installed on a USB? The image I used for the SD CARD and the USB NVME SSD are exactly the same.
I'm no linux pro at all. I know a little about a lot of things, but this issue breached that understanding. If there is anything I omitted that would be needed, please let me know and I will go get it and post it. THANKS!!!
I had a working install on a RPI5 a PI OS lite 64 bit that supported a Radxa 5 port SATA hat, a USB 3 OS BOOT, OpenMediaVault, samba shares, yada yada yada. OMV had been nagging me to install updates so I finally did it and the system would not reboot. I couldn't even see the headless text on a connected HDMI monitor. Without a OMV backup I could salvage, yeah I know, I started from scratch and got the system back up and running. This was about 2 months ago. Then the nagging updates again, although THIS TIME I have been holding off, then today I backed up my OMV to a safe place and went after the update. Guess what? System hosed again.
So now I am taking my time slowly, writing in a blog each step I take, making sure I do not miss anything, and I was at the point where my OS was booting from the USB drive but the partition was taking all 500gb of the NVME space. But before I went after resizing the file system and then resizing the partition, and then installing OMV, I decided to go after apt-get update && apt-get upgrade and sure enough, it is hose yet again. I didn't lose anything this time. I haven't even installed OMV 7 yet. And I KNOW that there are two different header and firmware packages usually kept back (not held back this time though)...
Code:
linux-headers-rpi-2712 linux-headers-rpi-v8 linux-image-rpi-2712 linux-image-rpi-v8At least this time, I was able to capture the apt upgrade results. Can anyone help me figure out what the heck I am doing wrong? The 1st of these 3 installs went like clock work until apt-get showed those four packages. Then the wheels came off big time.
Strange thing, before this last failed attempt, I decided to stay with an SD card to see what would happen with installing those held packages, both individually and then both. As expected, after apt-get update and apt-get upgrade I also encountered those four packages which at that time were actually held back. I decided to install the 2712 version (headers and image) and it worked fine. And the other two packages disappeared. So why did it behave that way using an SD CARD and differently with an OS installed on a USB? The image I used for the SD CARD and the USB NVME SSD are exactly the same.
I'm no linux pro at all. I know a little about a lot of things, but this issue breached that understanding. If there is anything I omitted that would be needed, please let me know and I will go get it and post it. THANKS!!!
Code:
root@RPI5-NAS-01:/# apt-get update && apt-get upgradeHit:1 http://deb.debian.org/debian bookworm InReleaseGet:2 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]Get:4 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages [235 kB]Get:5 http://archive.raspberrypi.com/debian bookworm InRelease [39.3 kB]Get:6 http://archive.raspberrypi.com/debian bookworm/main arm64 Packages [520 kB]Get:7 http://deb.debian.org/debian-security bookworm-security/main armhf Packages [220 kB]Get:8 http://deb.debian.org/debian-security bookworm-security/main Translation-en [141 kB]Get:9 http://deb.debian.org/debian bookworm-updates/main arm64 Packages [8,844 B]Get:10 http://deb.debian.org/debian bookworm-updates/main armhf Packages [8,292 B]Get:11 http://deb.debian.org/debian bookworm-updates/main Translation-en [8,248 B]Get:12 http://archive.raspberrypi.com/debian bookworm/main armhf Packages [549 kB]Fetched 1,833 kB in 2s (883 kB/s)Reading package lists... DoneReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneCalculating upgrade... DoneThe following packages have been kept back: linux-headers-rpi-2712 linux-headers-rpi-v8 linux-image-rpi-2712 linux-image-rpi-v8The following packages will be upgraded: initramfs-tools initramfs-tools-core libcamera-ipa libcamera0.3 linux-libc-dev raspberrypi-net-mods raspberrypi-sys-mods raspi-config raspi-firmware rpi-eeprom rpicam-apps-lite tzdata12 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.Need to get 26.2 MB of archives.After this operation, 1,398 kB disk space will be freed.Do you want to continue? [Y/n] yGet:1 http://deb.debian.org/debian bookworm-updates/main arm64 tzdata all 2024b-0+deb12u1 [298 kB]Get:2 http://archive.raspberrypi.com/debian bookworm/main arm64 raspi-firmware all 1:1.20241126-1 [12.8 MB]Get:3 http://archive.raspberrypi.com/debian bookworm/main arm64 initramfs-tools all 0.142+rpt2+deb12u1 [17.1 kB]Get:4 http://archive.raspberrypi.com/debian bookworm/main arm64 initramfs-tools-core all 0.142+rpt2+deb12u1 [53.1 kB]Get:5 http://archive.raspberrypi.com/debian bookworm/main arm64 libcamera0.3 arm64 0.3.2+rpt20241119-1 [815 kB]Get:6 http://archive.raspberrypi.com/debian bookworm/main arm64 libcamera-ipa arm64 0.3.2+rpt20241119-1 [1,071 kB]Get:7 http://archive.raspberrypi.com/debian bookworm/main arm64 linux-libc-dev all 1:6.6.62-1+rpt1 [2,057 kB]Get:8 http://archive.raspberrypi.com/debian bookworm/main arm64 raspi-config all 20241210 [35.6 kB]Get:9 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-net-mods all 1.4.3 [2,272 B]Get:10 http://archive.raspberrypi.com/debian bookworm/main arm64 raspberrypi-sys-mods arm64 20241202 [22.0 kB]Get:11 http://archive.raspberrypi.com/debian bookworm/main arm64 rpi-eeprom all 26.7-1 [8,496 kB]Get:12 http://archive.raspberrypi.com/debian bookworm/main arm64 rpicam-apps-lite arm64 1.5.3-1 [490 kB]Fetched 26.2 MB in 1min 1s (430 kB/s)Reading changelogs... DonePreconfiguring packages ...(Reading database ... 56292 files and directories currently installed.)Preparing to unpack .../00-raspi-firmware_1%3a1.20241126-1_all.deb ...Unpacking raspi-firmware (1:1.20241126-1) over (1:1.20240924-2) ...Preparing to unpack .../01-tzdata_2024b-0+deb12u1_all.deb ...Unpacking tzdata (2024b-0+deb12u1) over (2024a-0+deb12u1) ...Preparing to unpack .../02-initramfs-tools_0.142+rpt2+deb12u1_all.deb ...Unpacking initramfs-tools (0.142+rpt2+deb12u1) over (0.142+rpt1+deb12u1) ...Preparing to unpack .../03-initramfs-tools-core_0.142+rpt2+deb12u1_all.deb ...Unpacking initramfs-tools-core (0.142+rpt2+deb12u1) over (0.142+rpt1+deb12u1) ...Preparing to unpack .../04-libcamera0.3_0.3.2+rpt20241119-1_arm64.deb ...Unpacking libcamera0.3:arm64 (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ...Preparing to unpack .../05-libcamera-ipa_0.3.2+rpt20241119-1_arm64.deb ...Unpacking libcamera-ipa:arm64 (0.3.2+rpt20241119-1) over (0.3.2+rpt20240927-1) ...Preparing to unpack .../06-linux-libc-dev_1%3a6.6.62-1+rpt1_all.deb ...Unpacking linux-libc-dev (1:6.6.62-1+rpt1) over (1:6.6.51-1+rpt3) ...Preparing to unpack .../07-raspi-config_20241210_all.deb ...Unpacking raspi-config (20241210) over (20241119) ...Removing obsolete conffile /etc/init.d/raspi-config ...Removing obsolete conffile /etc/default/cpu_governor ...Preparing to unpack .../08-raspberrypi-net-mods_1.4.3_all.deb ...Unpacking raspberrypi-net-mods (1.4.3) over (1.4.2) ...Preparing to unpack .../09-raspberrypi-sys-mods_20241202_arm64.deb ...Unpacking raspberrypi-sys-mods (20241202) over (20241111) ...Preparing to unpack .../10-rpi-eeprom_26.7-1_all.deb ...Unpacking rpi-eeprom (26.7-1) over (26.4-1) ...Preparing to unpack .../11-rpicam-apps-lite_1.5.3-1_arm64.deb ...Unpacking rpicam-apps-lite (1.5.3-1) over (1.5.2-2) ...Setting up linux-libc-dev (1:6.6.62-1+rpt1) ...Setting up tzdata (2024b-0+deb12u1) ...Current default time zone: 'America/Phoenix'Local time is now: Fri Jan 3 17:48:53 MST 2025.Universal Time is now: Sat Jan 4 00:48:53 UTC 2025.Run 'dpkg-reconfigure tzdata' if you wish to change it.Setting up raspi-firmware (1:1.20241126-1) ...'/boot/vmlinuz-6.6.51+rpt-rpi-2712' -> '/boot/firmware/kernel_2712.img''/boot/vmlinuz-6.6.51+rpt-rpi-v8' -> '/boot/firmware/kernel8.img'Setting up rpi-eeprom (26.7-1) ...Setting up initramfs-tools-core (0.142+rpt2+deb12u1) ...Setting up raspi-config (20241210) ...Setting up initramfs-tools (0.142+rpt2+deb12u1) ...update-initramfs: deferring update (trigger activated)Setting up raspberrypi-sys-mods (20241202) ...Setting up raspberrypi-net-mods (1.4.3) ...Installing new version of config file /etc/profile.d/wifi-check.sh ...Setting up libcamera0.3:arm64 (0.3.2+rpt20241119-1) ...Setting up libcamera-ipa:arm64 (0.3.2+rpt20241119-1) ...Setting up rpicam-apps-lite (1.5.3-1) ...Processing triggers for libc-bin (2.36-9+rpt2+deb12u9) ...Processing triggers for man-db (2.11.2-2) ...Processing triggers for initramfs-tools (0.142+rpt2+deb12u1) ...update-initramfs: Generating /boot/initrd.img-6.6.51+rpt-rpi-v8sync: error syncing '/boot/initrd.img-6.6.51+rpt-rpi-v8': Input/output errordpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1dpkg: unrecoverable fatal error, aborting: failed to open diversions file: Input/output errorE: Sub-process /usr/bin/dpkg returned an error code (2)W: Problem unlinking the file /var/cache/apt/pkgcache.bin - pkgDPkgPM::Go (30: Read-only file system)root@RPI5-NAS-01:/# apt-get update && apt-get upgradebash: /usr/bin/apt-get: Input/output errorroot@RPI5-NAS-01:/#Statistics: Posted by HopWorks — Sat Jan 04, 2025 1:23 am
