Hello,
when booting my custom image built with Yocto 2.8b1, I noticed the following message during boot (at 5.28, related to the system journal):
[ OK ] Started Remount Root and Kernel File Systems.
Starting Flush Journal to Persistent Storage...
Starting Rebuild Hardware Database...
Starting Create System Users...
[ OK ] Started Create System Users.
Starting Create Static Device Nodes in /dev...
[ OK ] Started Create Static Device Nodes in /dev.
[ 5.254438] systemd-journald[211]: Received request to flush runtime journal from PID 1
Starting udev Kernel Device Manager...
[ 5.280481] systemd-journald[211]: File /var/log/journal/8a01e534f12643c389d44ce8af014d71/system.journal corrupted or uncleanly shut down, re.
[ OK ] Reached target Local File Systems (Pre).
Mounting /var/volatile...
[ OK ] Started udev Kernel Device Manager.
[ OK ] Mounted /var/volatile.
Starting Load/Save Random Seed...
[ OK ] Reached target Local File Systems.
Starting Rebuild Dynamic Linker Cache...
Starting Rebuild Journal Catalog...
[ OK ] Started Flush Journal to Persistent Storage.
I don’t think it depends on my custom image, as the same happens with the standard Toradex console image built with:
bitbake console-tdx-image
I don’t have this problem on the same hardware using my previous Image built with Yocto 2.7b3.
I would not have noticed about the problem if it wasn’t for the message when logging in with my user:
apalis-imx6-misa login: misa
Password:
Last login: Sun Mar 18 14:09:04 UTC 2018 on ttymxc0
[ 23.571221] systemd-journald[211]: File /var/log/journal/f050724bfde44a9aaf4458806b168d4c/user-1000.journal corrupted or uncleanly shut down,.
apalis-imx6-misa:~$
apalis-imx6-misa:~$
My question is, is it a real problem ? Anything I can do to fix it ? It does not happen on the same hardware with 2.7b3, so I don’t think it could be the flash.
Thank you for any help.
Nicola