I had a crash yesterday evening at about 7.46 UCT (the time when my monitor messaged me) I was in middle of nowhere and took me 3 hours to be able to boot from Zen, at about 10.40 UCT /var/log/messages shows this Jul 26 19:34:12 elm systemd[93989]: Reached target Exit the Session. Jul 26 19:34:12 elm systemd[1]: user(a)0.service: Succeeded. Jul 26 19:34:12 elm systemd[1]: Stopped User Manager for UID 0. Jul 26 19:34:12 elm systemd[1]: Stopping User runtime directory /run/user/0... Jul 26 19:34:12 elm systemd[1]: run-user-0.mount: Succeeded. Jul 26 19:34:12 elm systemd[1]: user-runtime-dir(a)0.service: Succeeded. Jul 26 19:34:12 elm systemd[1]: Stopped User runtime directory /run/user/0. Jul 26 19:34:12 elm systemd[1]: Removed slice User Slice of UID 0. Jul 30 22:02:48 elm systemd[282311]: Starting D-Bus User Message Bus Socket. Jul 30 22:02:48 elm systemd[282311]: Started Mark boot as successful after the user session has run 2 minutes. Jul 30 22:02:48 elm systemd[282311]: Reached target Timers. Jul 30 22:02:48 elm systemd[282311]: Reached target Paths. Jul 30 22:02:48 elm systemd[282311]: Listening on D-Bus User Message Bus Socket. Jul 30 22:02:48 elm systemd[282311]: Reached target Sockets. Note the future date! Further down the log I see Aug 3 ... Then Jul 24... and then Jul 26 again So I assume the file has got corrupted. The first messages I can find after reboot time: Jul 26 22:49:49 elm rsyslogd[1502]: imjournal: 414535 messages lost due to rate-limiting (20000 allowed within 600 secon ds) Jul 26 22:50:01 elm systemd[1]: Starting system activity accounting tool... Jul 26 22:50:01 elm systemd[1]: Started Session 46 of user root. Jul 26 22:50:01 elm systemd[1]: sysstat-collect.service: Succeeded. Jul 26 22:50:01 elm systemd[1]: Started system activity accounting tool. Jul 26 22:50:03 elm systemd[1]: session-46.scope: Succeeded. And the rest of the log looks normal date and time order Well out of my depth. Any suggestions welcome a) to explain the above and b) where to look for cause of crash Hugh