[SOLVED] Boot messages are nor journaled when /var on other

[nbd]

Greetings!

I have the /var partition mounted on an external USB hard disk with btrfs file system (in order to reduce SD card wearing). The problem is that 'journalctl -b' right after boot returns no messages at all. I don't know if the former is the cause of the latter. Later messages in the course of the session are journaled and stored OK. During boot, the messages on the screen run fast and are impossible to read, but no red colored "[FAILED]" marks are observed, only green "[OK]" ones.

In /etc/systemd/journald.conf I have a single (non-commented) line:

$this->bbcode_second_pass_code('', 'Storage=persistent')

In /etc/system.com the only entry is:

$this->bbcode_second_pass_code('', '[Manager]
LogLevel=notice')

/etc/fstab is as follows:

$this->bbcode_second_pass_code('', '/dev/mmcblk0p1 /boot vfat rw,async,noatime,auto,nouser,dev,suid,exec 0 0
LABEL="stor" /home btrfs rw,subvol=rpi/home,acl,auto,nouser,nodev,suid,exec,async 0 0
LABEL="stor" /var btrfs rw,subvol=rpi/var,acl,auto,nouser,nodev,suid,exec,async 0 0')

Both /home and /var are mounted and accessible when checked just after boot.

How to get boot messages to be journaled?

Thanks.
Albert.

EDIT:
Marked as solved.

[WarheadsSE]

Are you using an initrd?

[nbd]

$this->bbcode_second_pass_quote('WarheadsSE', 'A')re you using an initrd?

[WarheadsSE]

What devices is this on? Because the vanilla configuration is different for some boards.

[nbd]

The device is Raspberry Pi 2.

I tried to return /var back to the root partition and boot messages in this case are logged OK. Don't know how this can be explained, since the journald.conf manual reads about the "Storage=persistent" option (my case):

$this->bbcode_second_pass_quote('', 'I')f "persistent", data will be stored preferably on disk, i.e. below the /var/log/journal hierarchy (which is created if needed), with a fallback to /run/log/journal (which is created if needed), during early boot and if the disk is not writable.

[WarheadsSE]

Yes, stored anyways, in /var, possibly prior to /var being a mount point.

[nbd]

This makes sense. Thanks! (I thought that since the SyncIntervalSec is 5 minutes, messages should be cached. But maybe they are flushed before mounting /var.)