Then you have some corrupted hardware.
Also, syslog wasn’t capable of logging during the initial stages of boot, which is pretty important.
Re:Systemd.timer, an Alternative to Cron
by egberts1 on Friday December 09, 2022 @12:16PM
(#33923856)
Then there aught to be some kind of fsck (file checking) for journal files.
To forever complain until user intervention is downright silly.
Five separate but disparate hardware does not make for a probable hardware error.
I'm still experiencing file corruption regularly with journald on various distros.
Cannot recall corruption nor unreadability with syslog.