I have noticed that ever since Bookworm, Rev 1.3 3B+ quite often doesn't clear the boot. This came with Bookworm, I never saw it happening with Bullseye. This also doesn't happen with any other Pi model. All my Pis (2x 3B+, 2x 4B, 400, 5B) have official power supplies and quality cards. In the case of 3B+, this happens to both of them and the card model doesn't seem to affect the behavior.
This has grown to be a nuisance, so I did a test arrangement with my spare 3B+, as follows:
1) 3B+ default Bookworm install (2024-09-26) + full-upgrade, Ethernet connection, static IP. Scheduled reboot every 5 minutes (crontab: */5 * * * * sudo reboot).
2) Another Pi (400, not relevant) pings the 3B+ once a minute. If missed three consecutive pings, it considers the thing stuck and power cycles it via a smart plug.
I have run the test 6 days now and the stats are: 1728 reboots, 24 times stuck. So although maybe not so bad percentage-wise, the problem does exist. Additionally it seems to manifest more frequently when operating outside artificial test environment.
I particularly see the problem with this one drone 3B+ of mine running with overlay file system. Every power outage, every software update, there's no guarantee that the thing comes back up. I had to devise a watchdog system for it to be able to trust it measuring anything.
Again, this never was a problem with Bullseye. This doesn't happen with the other Pi models.
To replicate the problem, simply install default Bookworm to 3B+ Rev 1.3 and put */5 * * * * sudo reboot to crontab. You'll get it stuck in a day.
This has grown to be a nuisance, so I did a test arrangement with my spare 3B+, as follows:
1) 3B+ default Bookworm install (2024-09-26) + full-upgrade, Ethernet connection, static IP. Scheduled reboot every 5 minutes (crontab: */5 * * * * sudo reboot).
2) Another Pi (400, not relevant) pings the 3B+ once a minute. If missed three consecutive pings, it considers the thing stuck and power cycles it via a smart plug.
I have run the test 6 days now and the stats are: 1728 reboots, 24 times stuck. So although maybe not so bad percentage-wise, the problem does exist. Additionally it seems to manifest more frequently when operating outside artificial test environment.
I particularly see the problem with this one drone 3B+ of mine running with overlay file system. Every power outage, every software update, there's no guarantee that the thing comes back up. I had to devise a watchdog system for it to be able to trust it measuring anything.
Again, this never was a problem with Bullseye. This doesn't happen with the other Pi models.
To replicate the problem, simply install default Bookworm to 3B+ Rev 1.3 and put */5 * * * * sudo reboot to crontab. You'll get it stuck in a day.
Statistics: Posted by dpeltola — Wed Oct 02, 2024 9:04 am — Replies 0 — Views 22