Red Hat Bugzilla – Bug 789119
dracut-015-1.fc17 generated initramfs makes it impossible to boot
Last modified: 2012-02-13 11:22:27 EST
Description of problem:
After an update to dracut-015-1.fc17 and kernel-3.3.0-0.rc2.git6.1.fc17 all attempts to boot end up with "cannot find init" from dracut and in a dracut "debug shell". 'init' is there sitting as an executable /bin/sh script in the top directory if initrams. Attempts to restart a machine from there fizzle with "Failed to talk to init daemon" errors. If you will try in this debug shell run explicitely './init' then it starts going through motions and runs fsck on /sysroot/usr but eventually chokes with:
mount: can't find /sysroot/usr in /etc/fstab.
Actually /etc/fstab has only two identical lines, like this, in it:
LABEL=/usr1 /sysroot/usr ext3 defaults 1 2
and 'mount LABEL=/usr1 /sysroot/usr' or 'mount -L /usr1 /sysroot/usr' work just fine although 'mount /sysroot/usr' fails with "can't find".
The only things I was able to do in this moment was either power switch or a kernel panic after 'exit'.
Version-Release number of selected component (if applicable):
Is this another instance of binutils bug 788107? An attempt to boot the same kernel with a dracut-014-77.git20120126.fc17.1 generated initramfs got stuck with a claim that 'init' is not executable and I did not get even a debug shell (which does not seem to be that useful anyway).
Still broken in rawhide with dracut-015-7.fc18
Created attachment 560879 [details]
can you try the attached patch on /usr/lib/dracut/modules.d/98usrmount/mount-usr.sh ?
(In reply to comment #2)
> can you try the attached patch on
> /usr/lib/dracut/modules.d/98usrmount/mount-usr.sh ?
With initramfs generated by dracut-015-8.git20120210 + this patch my machine booted 3.3.0-0.rc2.git6.1.fc17.x86_64. Thanks!
Works for me too, please commit fix.
neither applying the patch nor rebuilding the initramfs has fixed the issue with me. I opened a new bugzilla for this ( 789503 ) and will post updates there if I see anything more.
seems to have fixed it. Thanks.