Gary Thomas <gary@...> writes: > > All of the recent images I've built (for beaglebone at least) > fail on boot with these messages: > > Starting Journal Service... > Failed to start Journal Service >
I'll add an extra data point. I find that boot succeeds if the file /etc/machine-id exists, even if it is an empty file. So far as I can tell from a brief look, systemd tries to create the file /etc/machine-id, if it does not exist, but this appears to be attempted when the root file system is readonly. (And, yes, if you force the root filesystem to be read-write when /sbin/init starts, again the boot will be successful.) Not sure yet why that cascades into the observed failure yet. An annoying complication I found was that the rescue and emergency modes were not working, leaving the system with no access at all. This turned out to be because the systemd-image.tar.bz2 did not include a /root directory. Creating /root resulted in the emergency maintenance prompt being presented. -- ---- Space Science Instrumentation Group (SRI) The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Rd Laurel MD 20723-6099 Phone: 240-228-3552 Fax: 240-228-7636 Internet: graham.a.mur...@jhuapl.edu "Space isn't remote at all. It's only an hour's drive away if your car could go straight upwards." - Fred Hoyle. _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
