Red Hat Bugzilla – Bug 496895
plymouth not hiding in some cases when / isn't getting mounted
Last modified: 2010-01-12 10:32:14 EST
Owen has a raid setup that didn't get upgraded correctly (see bug 496390). Upon rebooting he was left with an unbootable system and plymouth hiding the messages that were saying what was going wrong.
It turns out /sysroot wasn't getting mounted properly because of an error in the md configuration.
We *do* have:
cond -ne 0 plymouth --hide-splash
in the file, so maybe mount is returning a zero exit status even though it's failing? Or maybe plymouth is racing with the system panic? Not sure.
Nevertheless, I think we should add:
after switchroot so we show messages no matter what.
Owen would you mind attaching your /init file?
Created attachment 340551 [details]
/init file that was failing silently
With this and the bad RAID configuration, there was a cascading chain of failures starting at the mdadm call, but I saw no messages (other than kernel messages) subsequent to the start of plymouthd.
Oh thinking about this more, there's no way we can call plymouth quit after switchroot. switchroot does and rm -rf / type thing.
so i guess we need to figure out which of
1) if mount is returning 0 when it shouldn't
2) if cond isn't working
3) if plymouth --hide-splash isn't working (maybe racing with the panic that follows immediately after?)
I think I have the same problem here. I removed rhgb from the kernel options in grub to get a detailed view of the boot progress. Since F11 however the echo's in initrd after the plymouth activation all disappeard.
This was inconvenient as a ran into Bug 503109.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This is a mass edit of all mkinitrd bugs.
Thanks for taking the time to file this bug report (and/or commenting on it).
As you may have heard in Fedora 12 mkinitrd has been replaced by dracut. In Fedora 12 the mkinitrd package is still around as some programs depend on
certain libraries it provides, but mkinitrd itself is no longer used.
In Fedora 13 mkinitrd will be removed completely. This means that all work
on initrd has stopped.
Rather then keeping mkinitrd bugs open and giving false hope they might get fixed we are mass closing them, so as to clearly communicate that no more work will be done on mkinitrd. We apologize for any inconvenience this may cause.
If you are using Fedora 11 and are experiencing a mkinitrd bug you cannot work around, please upgrade to Fedora 12. If you experience problems with the initrd in Fedora 12, please file a bug against dracut.