[oe] Systemd and read-only-rootfs

Sven Ebenfeld sven.ebenfeld at gmail.com
Tue Nov 4 12:39:40 UTC 2014


Hi,

I have some issues with systemd since I've switched to dizzy release.
I've created my own machine configuration based on wandboard-solo and
my own Image based on console-systemd-Image.

After building everything, I get following error Messages during boot:
[...]
[    2.521774] systemd-sysv-generator[70]: Could not find init script
for umountnfs.service
[    2.530219] systemd-sysv-generator[70]: Could not find init script
for mountnfs.service
[    2.538489] systemd-sysv-generator[70]: Could not find init script
for rmnologin.service
[    2.546865] systemd-sysv-generator[70]: Could not find init script
for mountnfs.service
[    2.555089] systemd-sysv-generator[70]: Could not find init script
for rmnologin.service
[    2.563444] systemd-sysv-generator[70]: Could not find init script
for mountnfs.service
[    2.571643] systemd-sysv-generator[70]: Could not find init script
for rmnologin.service
[    2.580011] systemd-sysv-generator[70]: Could not find init script
for mountnfs.service
[    2.588217] systemd-sysv-generator[70]: Could not find init script
for rmnologin.service
[    2.596577] systemd-sysv-generator[70]: Could not find init script
for banner.service
[    2.604595] systemd-sysv-generator[70]: Could not find init script
for sysfs.service
[    2.612512] systemd-sysv-generator[70]: Could not find init script
for mountall.service
[    2.620721] systemd-sysv-generator[70]: Could not find init script
for checkroot.service
[    2.629087] systemd-sysv-generator[70]: Could not find init script
for urandom.service
[    2.637235] systemd-sysv-generator[70]: Could not find init script
for populate-volatile.service
[    2.646214] systemd-sysv-generator[70]: Could not find init script
for devpts.service
[    2.654231] systemd-sysv-generator[70]: Could not find init script
for hostname.service
[    2.664782] systemd-sysv-generator[70]: Could not find init script
for bootmisc.service
[    2.673093] systemd-sysv-generator[70]: Could not find init script
for sendsigs.service
[    2.681567] systemd-sysv-generator[70]: Could not find init script
for save-rtc.service
[    2.689753] systemd-sysv-generator[70]: Could not find init script
for urandom.service
[    2.697799] systemd-sysv-generator[70]: Could not find init script
for umountnfs.service
[    2.706939] systemd-sysv-generator[70]: Could not find init script
for umountfs.service
[    2.715201] systemd-sysv-generator[70]: Could not find init script
for halt.service
[    2.723411] systemd-sysv-generator[70]: Could not find init script
for sendsigs.service
[    2.731671] systemd-sysv-generator[70]: Could not find init script
for save-rtc.service
[    2.739895] systemd-sysv-generator[70]: Could not find init script
for urandom.service
[    2.748019] systemd-sysv-generator[70]: Could not find init script
for umountnfs.service
[    2.756292] systemd-sysv-generator[70]: Could not find init script
for umountfs.Service
[...]
         Starting Create Volatile Files and Directories...
         Starting Load/Save Random Seed...
[  OK  [    9.292509] systemd-journald[87]: Received request to flush
runtime journal from PID 1
] Started Trigger Flushing of Journal to Persistent Storage.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[...]

The Output of the mentioned command Shows the following:

â systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static)
   Active: failed (Result: exit-code) since Thu 1970-01-01 00:00:09
UTC; 44 years 10 months ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
 Main PID: 309 (code=exited, status=1/FAILURE)
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
[/usr/lib/tmpfiles.d/systemd-remote.conf:10] Unknown group
'systemd-journal-remote'.
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
[/usr/lib/tmpfiles.d/systemd-remote.conf:11] Unknown group
'systemd-journal-remote'.
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
[/usr/lib/tmpfiles.d/systemd.conf:19] Unknown user 'systemd-network'.
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
[/usr/lib/tmpfiles.d/systemd.conf:20] Unknown user 'systemd-network'.
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
[/usr/lib/tmpfiles.d/systemd.conf:21] Unknown user 'systemd-network'.
Jan 01 00:00:09 wandboard-cd2 systemd-tmpfiles[309]:
symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file system
Jan 01 00:00:09 wandboard-cd2 systemd[1]:
systemd-tmpfiles-setup.service: main process exited, code=exited,
status=1/FAILURE
Jan 01 00:00:09 wandboard-cd2 systemd[1]: Failed to start Create
Volatile Files and Directories.
Jan 01 00:00:09 wandboard-cd2 systemd[1]: Unit
systemd-tmpfiles-setup.service entered failed state.

Can anybody help me where I should look or what I should Change in my
Image recipe to get read-only rootfs working?

Mit freundlichen Grüßen,
Sven Ebenfeld



More information about the Openembedded-devel mailing list