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
Have rebooted yet?
Repeatedly
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-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Sun 2020-11-15 18:51:16 GMT; 8s ago
TriggeredBy: ● systemd-journald-dev-log.socket
● systemd-journald.socket
● systemd-journald-audit.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 34057 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 19096)
Memory: 1.3M
CGroup: /system.slice/systemd-journald.service
└─34057 /usr/lib/systemd/systemd-journald
Nov 15 18:51:16 xircon-w6567sz systemd-journald[34057]: Journal started
Nov 15 18:51:16 xircon-w6567sz systemd-journald[34057]: Runtime Journal (/run/log/journal/df42ab4307ea45ce862845b75f777>
Nov 15 18:51:16 xircon-w6567sz systemd-journald[34057]: Runtime Journal (/run/log/journal/df42ab4307ea45ce862845b75f777>
Everything goes to /run - I am completely baffled.
systemd-machine-id-setup --print > mcid
dbus-uuidgen --get >> mcid
\cat /etc/machine-id >> mcid
\cat /var/lib/dbus/machine-id >> mcid
df42ab4307ea45ce862845b75f7777ce
df42ab4307ea45ce862845b75f7777ce
df42ab4307ea45ce862845b75f7777ce
df42ab4307ea45ce862845b75f7777ce
So no problem there. Remains the same after a reboot.
ran:
mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal
systemctl restart systemd-journald
As su - no joy.
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 
Maybe that should help somehow
Yes, saw that (at least twice). Not sure if it applies. Have cross posted on reddit (btrfs & linux questions) just in case 
And it is pay walled 
1 Like
Jeez…Haven’t even noticed, what a crap 
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 /
Sure thing:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=4EAC-B056 /boot/efi vfat umask=0077 0 2
UUID=3ff8ff8b-71b4-402a-82c6-24ddd0b82628 / btrfs subvol=@,defaults,noatime,space_cache,autodefrag,compress=lzo 0 1
UUID=3ff8ff8b-71b4-402a-82c6-24ddd0b82628 /home btrfs subvol=@home,defaults,noatime,space_cache,autodefrag,compress=lzo 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
UUID=a1a5ca63-d695-45bb-8854-e3c7c978380e /data ext4 rw,relatime 0 2
/dev/sdb1: UUID="a1a5ca63-d695-45bb-8854-e3c7c978380e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="7c6c4bc4-01"
/dev/sda1: UUID="4EAC-B056" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b4e2446c-700d-ba4c-a7d5-2f25fbfaaf46"
/dev/sda2: UUID="3ff8ff8b-71b4-402a-82c6-24ddd0b82628" UUID_SUB="4c29735f-febf-491a-b6fb-09afc2ad9988" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="7d3fb8d8-45e1-d043-9437-af6fb1a22739"
/dev/sda3: UUID="a90993bf-4906-4ba6-bb71-f908278c9b70" TYPE="swap" PARTUUID="92d0aadb-f626-fa4c-9783-71f88a1defb8"
/dev/sdc1: LABEL="ventoy" UUID="AA39-7193" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTUUID="5da6b0ea-01"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="5DBF-2B5F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="5da6b0ea-02"
ID 256 gen 5165 top level 5 path timeshift-btrfs/snapshots/2020-11-15_17-54-26/@
ID 257 gen 5636 top level 5 path @home
ID 271 gen 5089 top level 5 path timeshift-btrfs/snapshots/2020-11-13_20-54-49/@
ID 297 gen 5165 top level 5 path timeshift-btrfs/snapshots/2020-11-14_22-00-01/@
ID 303 gen 5165 top level 5 path timeshift-btrfs/snapshots/2020-11-15_17-55-57/@
ID 304 gen 5636 top level 5 path @
ID 310 gen 5166 top level 5 path timeshift-btrfs/snapshots/2020-11-15_22-00-01/@
Added blkid. Thanks for the help, I need to see some logs for another problem, slow close down, this is driving me nuts!
Ok, so only the standard subvols @ and @home. No problem i could spot.
ah thats what is also suggested on
https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html
How does your /var/log/journal look now (is there a subfolder reflecting the machine-id (a long alpha-numeric string)? What about the access rights? a simple ls -la again please 
Your first ls -lah only showd the “remote” subfolder (plus . & . . of course), but no “machine-id” subfolder…
ls -la /var/log/journal
total 0
drwxr-sr-x+ 1 root systemd-journal 0 Nov 16 16:28 .
drwxr-xr-x 1 root root 308 Nov 16 16:56 ..
Everything still points to /run :
status systemd-journald
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Mon 2020-11-16 17:31:01 GMT; 2h 12min ago
TriggeredBy: ● systemd-journald-dev-log.socket
● systemd-journald.socket
● systemd-journald-audit.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 35914 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 19101)
Memory: 9.7M
CGroup: /system.slice/systemd-journald.service
└─35914 /usr/lib/systemd/systemd-journald
Nov 16 17:31:01 xircon-w6567sz systemd-journald[35914]: Journal started
Nov 16 17:31:01 xircon-w6567sz systemd-journald[35914]: Runtime Journal (/run/log/journal/df42ab4307ea45ce862845b75f777>
Warning: journal has been rotated since unit was started, output may be incomplete.
status, enable, start & restart are all aliases (lazy)
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.
2 Likes
Typo, sorry
haha that would have been too easy 
so, its very insistent…
but no errors were thrown!?
1 Like
@freggel.doe you are a genius!
cat volatile-storage.conf
#
# SPDX-License-Identifier: GPL-3.0-or-later
[Journal]
Storage=volatile
Where the hell did that come from! Commented out and now working. Thank you for pointing me in the correct direction.
It was in /etc/journald.conf.d
2 Likes