I've seen similar messages on 32bit RPiOS running on zero and A+ models too.
My guess? It's because only the Pi5 has an onboard RTC. The other models fake it which means until that occurs the clock is reset at boot to the start of the epoc. It's corrected once fakehwclock is processed (and can still be earlier than the journal timestamp) and again once an ntp server can be reached.
You should probably open an issue on the Raspberry Pi OS github repo.
My guess? It's because only the Pi5 has an onboard RTC. The other models fake it which means until that occurs the clock is reset at boot to the start of the epoc. It's corrected once fakehwclock is processed (and can still be earlier than the journal timestamp) and again once an ntp server can be reached.
You should probably open an issue on the Raspberry Pi OS github repo.
Statistics: Posted by thagrol — Thu Feb 29, 2024 12:51 pm