Bug 694958
| Summary: | Error message about failing to create /var/run/mdadm | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | cam <camilo> |
| Component: | mdadm | Assignee: | Doug Ledford <dledford> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | awilliam, dledford, groknok |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-14 23:57:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
cam
2011-04-09 06:51:46 UTC
I just tested F15 Beta RC2 livecd i686 and the message is different, longer. There is still a non-graphical stage at the end of boot before login. Possible related issue, though different. I downloaded nightly build Fedora-15-Nightly-20110407.23-i686-Live-xfce.iso, put it on a USB stick with Fedora liveusb-creator. Booted off it, things seemed to go well, Plymouth showed the Fedora logo over the light blue background, and the logo slowly filling. After the logo was full nothing happened. Half an hour after boot started I decided to call it quits. I pressed the right arrow key on the keyboard and got this message: "In: failed to create symbolic link '/var/run/mdadm': No such file or directory." I had to press the power switch to reboot. The message about /var/run/mdadm is not very significant; it occurs on all boots, successful or otherwise. If you are seeing some more significant issue and that's what you're worried about - on the mailing list you mentioned not being able to install - please adjust the bug with details on that problem, or file a new bug. OK, I don't mind filing a new bug, but if it is not about mdadm I have no clue what it is about. I still have the image in the USB stick so I can try to install it again. As I described previously, Anaconda just seems to hang somewhere. Is there a way I could get some debugging information from Anaconda in order to file a proper bug report? Or is there a way to disable Plymouth during Anaconda install so that I can see where it stops? I don't know why you're talking about anaconda when you're booting a live CD, it is not involved at all. to see what's happening during boot on a live image, edit the boot parameters and take out 'rhgb quiet'. Yes, you are right about Anaconda, my mistake.
So I booted with 'rhgb quiet' removed as you suggested.
The very last line before it hang was:
"Adding live user"
But before that there were a number of failures seemingly due to SELinux blocking different actions.
For example, just before it stopped there were 6 lines like this:
type=1400 audit(....):avc:denied {read} for pid=.... comm="mount" name="run" dev=dm-0 ino=1073 scontext=system_u:system_r:mount_t:s0 tcontext:system_u:object_r:var_t:s0 tclass=linkFile
However the very *first* thing that failed due to SELinux blocking was:
Start Recreate Volatile Files and Directories failed, see 'systemctl status systemd-tmpfiles-setup.services' for details.
There were more actions blocked by SELinux in between those that I am not listing here.
Which module do you think this bug should be filed against?
I just noted you're on a nightly. Don't file a bug, this is known. The nightlies don't have all the latest fixes that are in Beta RC2. Use that instead. Good to know this has been fixed. So my issue is no more (there is still the issue of the original reporter). Thanks. (In reply to comment #8) Yes... I think the ugly non graphical screen gives a poor impression at startup. It would not put a reviewer in a good frame of mind. The original problem should have been fixed already. If not, then please reopen this bug. |