Specifying boot ID or boot offset has no effect, no persistent journal was found. Tried changing auto to persistent in journalctl.conf but it hasn’t helped. New install on btrfs

[image] xircon: journalctl.conf Maybe just a typo but the relevant file would be /etc/systemd/journald.conf and any config file in the /etc/systemd/journald.conf.d/ directory.

does the folder /var/log/journal exist?

It does, I just deleted and recreated to make sure and to see if it helps.

and was there any content inside / is there now after recreating (and rebooting)? thats inside my /var/log/journal: drwxr-sr-x+ 1 root systemd-journal 4036 8. Nov 10:33 2b55b673ff8c4e258c53b57ac7ac5d59 drwxr-sr-x+ 1 root systemd-journal-remote 0 30. Aug 17:48 remote

ls -lah Alias tip: lh total 0 drwxr-sr-x+ 1 root systemd-journal 12 Sep 20 21:10 . drwxr-xr-x 1 root root 290 Nov 15 18:22 .. drwxr-sr-x 1 root systemd-journal-remote 0 Sep 20 21:10 remote But still got the problem, tried a timeshift restore, has not helped. ● systemd…

Well have read the internet, tried everything I can find - same issue, I give up for the night.

Getting nowhere with this, round and round in circles.

Wish i could help somehow, but that’s beyond voodoo magic, no idea and haven’t seen anything like it before too :frowning: Maybe that should help somehow [image] Journal persistent logging fails after reboot - Red Hat Customer Portal This issue happens only if Persistent logging for the…

Yes, saw that (at least twice). Not sure if it applies. Have cross posted on reddit (btrfs & linux questions) just in case :smiley: And it is pay walled :frowning:

[image] xircon: And it is pay walled :frowning: Jeez…Haven’t even noticed, what a crap :laughing:

could it be related to any kind of btrfs “issue”? Like have you created additional subvolumes and something is wrong? Could you post your /etc/fstab? and maybe additionally run sudo btrfs subvolume list /