Where to find log files from previous boot?

My Home Assistant keeps locking up at least once a week. The Screen says ‘Unknow Error / Reload UI’, but that doesn’t work on any page and I can’t access it via SSH. So the only thing I can do it unplug it and plug it back in to reboot.

This is a Pi3B+ running latest release.

After rebooting the log files only show info from the current boot.

Where do I find log files from the previous boot when it locked up?


1 Like

The system log can only be found on the SD card before booting. Take it to a Linux PC or Windows PC running Disk Internals Linux Reader (free).

I think there are CLI commands for the core and supervisor logs that can look at the previous journaled logs but I don’t know what they are.

So they get wiped after a boot?
Argh. Ok, I’ll look at the SD card next time it freezes

Only the system log.

The core and supervisor previous logs are stored. But as I said, I’m not sure how to access them.

Froze again. Found the System log file with Disk Internal Linux Reader. It’s encrypted or something. Nothing human readable. Not surprised.

home-assistant.log should be a plain text file.

sudo journalctl -D /mnt/logs/

Journal file /mnt/logs//ef268a58007742a88e4a2eb4d3e53862/user-1004@9d6ff77296d147199f80e93324b46277-0000000000000f54-0005c5468cabb990.journal corrupted, ignoring file.

Journal file /mnt/logs//ef268a58007742a88e4a2eb4d3e53862/system@334ee78b37b0452dada9ae59870dc045-0000000000053032-0005bcb9b06063d2.journal uses an unsupported feature, ignoring file.

Use SYSTEMD_LOG_LEVEL=debug journalctl --file=/mnt/logs//ef268a58007742a88e4a2eb4d3e53862/system@334ee78b37b0452dada9ae59870dc045-0000000000053032-0005bcb9b06063d2.journal to see the details.

-- No entries --

sudo SYSTEMD_LOG_LEVEL=debug journalctl --file=/mnt/logs//ef268a58007742a88e4a2eb4d3e53862/system@334ee78b37b0452dada9ae59870dc045-0000000000053032-0005bcb9b06063d2.journal
Journal effective settings seal=no compress=no compress_threshold_bytes=8B
Journal file /mnt/logs//ef268a58007742a88e4a2eb4d3e53862/system@334ee78b37b0452dada9ae59870dc045-0000000000053032-0005bcb9b06063d2.journal has unknown incompatible flags 0x4
Failed to open journal file /mnt/logs//ef268a58007742a88e4a2eb4d3e53862/system@334ee78b37b0452dada9ae59870dc045-0000000000053032-0005bcb9b06063d2.journal: Das Protokoll wird nicht unterstützt
mmap cache statistics: 0 hit, 1 miss
Failed to open files: Das Protokoll wird nicht unterstützt

Not easy to debug :frowning: Any Suggestions?