Red Hat Bugzilla – Bug 928339
systemd: Failed to mount /run: No such file or directory
Last modified: 2013-04-03 21:58:13 EDT
Created attachment 717074 [details]
Description of problem:
I installed F19 from F19 Alpha TC2 Live x86_64. After reboot, I see this error message:
> systemd: Failed to mount /run: No such file or directory
And I have to hard-reboot the computer, nothing else works. selinux=0 doesn't help.
Version-Release number of selected component (if applicable):
F19 Alpha TC2
Created attachment 717076 [details]
verbose boot messages
Proposing as an Alpha blocker:
All release-blocking images must boot in their supported configurations.
Can you boot with "rd.break" on the kernel command line and check, that /sysroot/run is present?
If no, please reassign the bug to anaconda.
/sysroot is present, /sysroot/run is not. Reassigning to anaconda.
Discussed at 2013-03-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Accepted as a blocker per criterion "A system installed with a graphical package set must boot to the 'firstboot' utility on the first boot after installation. The firstboot utility must be able to create a working user account." (the criterion cited in comment #2 does not apply). This appears to be different from #922988, as it didn't affect TC1.
*** Bug 928338 has been marked as a duplicate of this bug. ***
Why was this reassigned to anaconda? We don't construct the initrd. We only call other programs to do that for us.
Changing needinfo to Harald for a closer explanation.
Can reproduce this here as well.
clumens: I think on the basis that it's similar to / the same as:
i.e. there's no sysroot/run during install. But I don't know if we're missing something there.
Is it only happening for Live installs?
Yes, I see this particular problem just on Live install.
However, I just tried F19 Alpha TC3 Live x86_64 and the installed system booted correctly. I didn't even disable selinux. The problem seems to be fixed.
I think this is a duplicate of bug 922988
Changing to MODIFIED then based on comment 12,
but feel free to mark it a duplicate or close as appropriate.
harald: good enough for me.
*** This bug has been marked as a duplicate of bug 922988 ***
*** Bug 928994 has been marked as a duplicate of this bug. ***