I also think it is not storage device related. I think it is IP/internet/router issue. I had to change ISP several times, seen various issues over the years. I have still alternatives for my 'fiber ISP' working, so in this case I would simply connect a Linux box via a 'different pipe' to the internet and use https://wiki.debian.org/Debootstrap to get an container/VM running. Run apt to install some extra packages, then see if problem still the sarme.The outside issue is obviously a possible; as I mentioned sometihng like this happened a while back and then didn't. It was only a day or two though whereas this time it has been failing for at least a couple of weeks.My quick judgement is you have some 'changing IP networking conditions' during running those commands. That is most likely somewhere outside your control (on the internet, repo servers or whatever), hence a few days or week later it might work again. Or as mentioned something in the Pi itself, slow/bad SD-card ,network hiccup, wrong time as mentioned maybe.
Given the range of Pi involved, it seems very unlikely to be SD card stuff (after all, two of the Pi 5 have NVME HATs, one has SD card, a Pi 4 has a usb SSD, likewise a Pi 3, the PiHole Pi 2 has SD card).
I guess I can sacrifice a machine to some deeper testing, load up an untouched .img that is old enough to need updating, try that, etc.
A different pipe can also be a VPN, but make sure the whole setup is different enough from your usual home network and ISP. And don't forget you have PiHole. I know Windows10 simply failed updating for me if its DNS was/is? PiHole. And check IPv4 v.s. IPv6 maybe.
Statistics: Posted by redvli — Tue Oct 01, 2024 6:41 am