Bug 928339 - systemd[1]: Failed to mount /run: No such file or directory
Summary: systemd[1]: Failed to mount /run: No such file or directory
Keywords:
Status: CLOSED DUPLICATE of bug 922988
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
: 928338 928994 (view as bug list)
Depends On:
Blocks: F19Alpha, F19AlphaBlocker
TreeView+ depends on / blocked
 
Reported: 2013-03-27 13:23 UTC by Kamil Páral
Modified: 2013-04-04 01:58 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-02 16:07:28 UTC
Type: Bug


Attachments (Terms of Use)
boot messages (9.04 KB, image/png)
2013-03-27 13:23 UTC, Kamil Páral
no flags Details
verbose boot messages (20.17 KB, image/png)
2013-03-27 13:25 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2013-03-27 13:23:47 UTC
Created attachment 717074 [details]
boot messages

Description of problem:
I installed F19 from F19 Alpha TC2 Live x86_64. After reboot, I see this error message:

> systemd[1]: 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

Comment 1 Kamil Páral 2013-03-27 13:25:46 UTC
Created attachment 717076 [details]
verbose boot messages

Comment 2 Kamil Páral 2013-03-27 13:30:49 UTC
Proposing as an Alpha blocker:
All release-blocking images must boot in their supported configurations.
http://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria

Comment 3 Harald Hoyer 2013-03-27 14:00:40 UTC
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.

Comment 4 Kamil Páral 2013-03-27 16:07:15 UTC
/sysroot is present, /sysroot/run is not. Reassigning to anaconda.

Comment 5 Adam Williamson 2013-03-27 18:02:43 UTC
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.

Comment 6 Michal Schmidt 2013-03-27 20:43:00 UTC
*** Bug 928338 has been marked as a duplicate of this bug. ***

Comment 7 Chris Lumens 2013-03-28 14:12:31 UTC
Why was this reassigned to anaconda?  We don't construct the initrd.  We only call other programs to do that for us.

Comment 8 Kamil Páral 2013-03-28 14:24:47 UTC
Changing needinfo to Harald for a closer explanation.

Comment 9 Stef Walter 2013-03-28 14:58:43 UTC
Can reproduce this here as well.

Comment 10 Adam Williamson 2013-03-28 20:03:31 UTC
clumens: I think on the basis that it's similar to / the same as:

https://bugzilla.redhat.com/show_bug.cgi?id=922988

particularly:

https://bugzilla.redhat.com/show_bug.cgi?id=922988#c16

i.e. there's no sysroot/run during install. But I don't know if we're missing something there.

Comment 11 Jens Petersen 2013-03-29 09:30:49 UTC
Is it only happening for Live installs?

Comment 12 Kamil Páral 2013-03-29 10:23:00 UTC
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.

Comment 13 Harald Hoyer 2013-04-02 07:34:35 UTC
I think this is a duplicate of bug 922988

Comment 14 Jens Petersen 2013-04-02 08:05:52 UTC
Changing to MODIFIED then based on comment 12,
but feel free to mark it a duplicate or close as appropriate.

Comment 15 Adam Williamson 2013-04-02 16:07:28 UTC
harald: good enough for me.

*** This bug has been marked as a duplicate of bug 922988 ***

Comment 16 Jens Petersen 2013-04-04 01:58:13 UTC
*** Bug 928994 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.