+++ This bug was initially created as a clone of Bug #808907 +++ Description of problem: /var/lib/random-seed file is not functional under readonly root enabled. This file cannot be removed due to "Read-only file system" error and the system will show the error message when booting: "systemd-random-seed[517]: Failed to write new random seed file: Bad file descriptor". Version-Release number of selected component (if applicable): initscripts-9.34.2-1.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1. Just install base and core groups 2. Enable readonly root function in /etc/sysconfig/readonly-root file, set READONLY=yes and TEMPORARY_STATE=yes. 3. Add mount option ro in /etc/fstab for / directory. 4. Reboot Actual results: "systemd-random-seed[517]: Failed to write new random seed file: Bad file descriptor" and the file cannot be removed/modified. Expected results: No error for /var/lib/random-seed. Seeing the same error in Fedora 18 alpha still.
*** Bug 888618 has been marked as a duplicate of this bug. ***
Hi, this is not bug in readonly-root, but in systemd-random-seed.service. Adding fedora-readonly.service to systemd-randomd-seed's After solves this issue - /var/lib/random-seed is bind mounted as rw before it is used. -After=systemd-readahead-collect.service systemd-readahead-replay.service systemd-remount-fs.service +After=systemd-readahead-collect.service systemd-readahead-replay.service systemd-remount-fs.service fedora-readonly.service There is another issue with selinux involved bz #921456.
Proper solution is to add random-seed to Before= in fedora-readonly.service - switching back to initscipts
Patch commited to git -> http://git.fedorahosted.org/cgit/initscripts.git/commit/?id=d43d856ff2c8fd144a0d2030cb4655e7acea6084 -> post