[yocto] read-only-rootfs causes systemd-tmpfiles-setup.service failure ( symlink(../run/lock, /var/lock) failed: Read-only file system)

[richard_allen at keysight.com]

This is what I have,


$ cat etc/fstab 
# stock fstab - you probably want to override this with a machine specific one

/dev/root            /                    auto       ro              1  0
proc                 /proc                proc       defaults              0  0
devpts               /dev/pts             devpts     mode=0620,gid=5       0  0
tmpfs                /run                 tmpfs      mode=0755,nodev,nosuid,strictatime 0  0
tmpfs                /var/volatile        tmpfs      defaults              0  0

# uncomment this if your device has a SD/MMC/Transflash slot
#/dev/mmcblk0p1       /media/card          auto       defaults,sync,noauto  0  0



-----Original Message-----
From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Ayoub Zaki
Sent: Friday, October 06, 2017 9:19 AM
To: yocto at yoctoproject.org
Subject: Re: [yocto] read-only-rootfs causes systemd-tmpfiles-setup.service failure ( symlink(../run/lock, /var/lock) failed: Read-only file system)


Hi,

On 06.10.2017 15:40, richard_allen at keysight.com wrote:
> I am build an image with read-only-rootfs When enabled, during startup 
> I get a
>
> [FAILED] Failed to start Create Volatile Files and Directories.
> See 'systemctl status systemd-tmpfiles-setup.service' for details.
>
>
>
> ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
>     Loaded: loaded 
> (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor 
> pre
> set: enabled)
>     Active: failed (Result: exit-code) since Fri 2017-09-01 19:16:27 UTC; 3min 52s ago
>       Docs: man:tmpfiles.d(5)
>             man:systemd-tmpfiles(8)
>    Process: 945 ExecStart=/bin/systemd-tmpfiles --create --remove 
> --boot --exclude-prefix= /dev (code=exited, status=1/FAILURE)
>   Main PID: 945 (code=exited, status=1/FAILURE)
>
> Sep 01 19:16:27 dso systemd[1]: Starting Create Volatile Files and Directories...
> Sep 01 19:16:27 dso systemd-tmpfiles[945]: symlink(../run/lock, 
> /var/lock) failed: Read-only file system Sep 01 19:16:27 dso systemd-tmpfiles[945]: "/var/tmp" already exists and is not a directory.
> Sep 01 19:16:27 dso systemd-tmpfiles[945]: "/var/log" already exists and is not a directory.
> Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Main 
> process exited, code=exited, status=1/FAILURE Sep 01 19:16:27 dso systemd[1]: Failed to start Create Volatile Files and Directories.
> Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
> Sep 01 19:16:27 dso systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
>
>
> Not clear if I should be worried about this.
> If so, what should be done?
> Thanks
>
>
> Richard C. Allen
> Keysight Technologies
> richard_allen at Keysight.com
>
can you show your /etc/fstab ?

--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel.     : +4971415074546
Mobile   : +4917662901545
Email    : ayoub.zaki at embexus.com
Homepage : https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fembexus.com&data=02%7C01%7C%7C449c3fc3937e4dcd89a908d50cd604cd%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636429035696758010&sdata=C%2BWEfzYBKOcwCSSmsZjxsyNJjRQCTM8aQhnm0re%2BYds%3D&reserved=0

--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7C449c3fc3937e4dcd89a908d50cd604cd%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636429035696758010&sdata=5jvH4ZIsWtvbxSWOIjLIrazIkmyD9jOeEy%2Flp%2BN%2FBkU%3D&reserved=0