Description of problem: ---rc.log--- rc sysinit logging started at Mon Apr 9 05:01:31 2012 OpenRC 0.9.9.3 is starting up Gentoo Linux (i686) * /proc is already mounted, skipping * /run is already mounted, skipping * /run/lock: creating directory * checkpath: mkdir: Read-only file system * Mounting security filesystem ... [ ok ] * Mounting debug filesystem ... [ ok ] * Mounting config filesystem ... [ ok ] * Mounting cgroup filesystem ... [ ok ] * Using /dev mounted from kernel ... [ ok ] * checkpath: mkdir: Read-only file system * Starting udev ... error binding udev control socket * start-stop-daemon: failed to start `/lib/udev/udevd' * Failed to start udev [ !! ] * ERROR: udev failed to start rc sysinit logging stopped at Mon Apr 9 05:01:31 2012 rc boot logging started at Mon Apr 9 05:01:31 2012 * Setting system clock using the hardware clock [UTC] ... ---cut--- Version-Release number of selected component (if applicable): 018 How reproducible: every time Steps to Reproduce: 1. build initramfs with dracut-018 2. 3. Actual results: above Expected results: boot with no errors Additional info: downgrading dracut to 017 or earlier makes initramfs that boots with no errors
I get similar problem with dracut-018-33.git20120424.fc18.noarch on Fedora. Initramfs could not start udevd: init: line 113: /lib/systemd/systemd-udevd: No such file or directory The Fedora issue has been fixed in dracut-018-37.git20120425.fc18.1.noarch.
> The Fedora issue has been fixed in dracut-018-37.git20120425.fc18.1.noarch. No. I don't think it has been fixed yet. I'm using dracut-018-74.git20120522.fc18.noarch with a vanilla kernel. The only thing I can read as boot output is messages about missing udev storage devices. The system was upgraded from F16 to F17. Attempts to use the F17 dracut in F16 to upgrade the system resulted in this udev issue and an unbootable system. Upgrade was finally done using the F16 dracut and fstab.sys. Once the usrmove was completed a yum upgrade of the stock Fedora kernel was successful. The system boots using the stock kernel. But now that the upgrade to F17 is completed, and the F17 dracut was reinstalled, I still have the udev issue when attempting to use a vanilla kernel. I tried "rdshell rdinitdebug" in the kernel command line. But dracut cannot drop to a shell so I can get more information. Udev is saying it cannot access any of the storage devices. Dracut command is host-only mode with no other options except verbose and -f. I am going to try to manually create a new initfs using the stock Fedora kernel and see if that works. If it does then maybe there is an issue with my vanilla kernel.
> I am going to try to manually create a new initfs using the stock Fedora kernel > and see if that works. If it does then maybe there is an issue with my vanilla > kernel. Well, it is not a kernel issue. I tried it with the Fedora kernel and got the same output: udevd inotify_add_watch [all the udev storage devices] no such file or directory dracut then tries to drop to a shell with no success. It keeps repeating the attempts to drop to the shell. The output scrolls by too fast to read. But most of the lines start with /lib/udev or something like that.
I have verified there is a udev issue for me in F17 dracut. I had tried using various F17 dracut builds, including dracut-019 from rawhide. Most of them fail to even mount the dracut root so I can get to a dracut shell. Eventually I tried dracut-013-100.git20111021.fc17.noarch.rpm. I was finally able to get to a dracut shell using that version. Using dracut-013-100.git20111021.fc17 I was able to verify that udev is running, but it is not setting up the block devices. The block devices appear in the sysfs. Since udev is running it is a separate issue from this bug. I will create a new bug for my dracut issue. The bug is https://bugzilla.redhat.com/show_bug.cgi?id=830881.
original issue is fixed.