Red Hat Bugzilla – Bug 842426
Dracut didn't create a working initramfs
Last modified: 2012-09-27 05:31:50 EDT
Created attachment 599856 [details]
kernel 3.4.4.-4 initramfs
Description of problem:
New kernel won't boot. Drops to dracut shell. No encrypted partitions are accessible. Could be udev in dracut process not waiting for cryptsetup.
Version-Release number of selected component (if applicable):
System won't boot with kernel-126.96.36.199-4 at any time. No encrypted partitions are listed in /dev/mapper/ when dropped to shell.
Steps to Reproduce:
1. yum update to latest.
2. Try to reboot with latests kernel and dracut.
3. Try to follow dracut troubleshooting procedures.
Get dropped to dracut shell with error message.
"dracut warning: Unable to process initqueue"
System to boot as normal.
I tried some testing late last night/early this morning and got to the point that udev isn't finding the partitions. udev sender uid=-1, message ignored.
Tried to follow the various troubleshooting documents but they refer to grub.conf and not grub2. Tried to enable dracut debugging but couldn't get it to work.
This is similar to bug https://bugzilla.redhat.com/show_bug.cgi?id=839362.
Created attachment 599857 [details]
This is the working initramfs
Created attachment 599859 [details]
dracut log for 3.4.2-1 kernel
This is the dracut log file for the working kernel.
Created attachment 599860 [details]
dracut log for 3.4.4-4 kernel
This is the dracut log for the non-working kernel.
Looking through the working and non-working initramfs, I see that in the working one it points to modules with
whereas the broken one points to the modules like this.
On another computer, I didn't update the dracut and it is till running dracut-013-22.fc16.noarch but works with 3.4.4-4.fc16.i686.PAE.
I personally don't know enough to go further and the troubleshooting pages don't work with grub2.
Jul 01 02:41:32 Installed: kernel-3.4.2-1.fc16.x86_64
Jul 09 01:51:32 Installed: kernel-3.4.4-4.fc16.x86_64
Apr 07 10:18:54 Updated: dracut-013-22.fc16.noarch
Jul 05 16:12:36 Updated: dracut-018-55.git20120606.fc16.noarch
Sorry for the inconvenience.
Can you boot with "rd.debug" on the kernel command line, and after you are dropped to the dracut debug shell, save "/run/initramfs/init.log" and the output of "dmesg" to a USB stick or the /boot partition.
Then boot the old kernel and attach these files here.
I applied the latest kernel upgrade and still get dropped to the same error messages. I can only boot into the 4.2-1 kernel.
I am not sure about the "kernel command line" but I will see what I can find and report for both kernels.
Created attachment 601112 [details]
dmesg for kernel 3.4.4-4
This is the dmesg for kernel 3.4.4-4
Created attachment 601113 [details]
init.log for kernel 3.4.4-4
/run/initramfs/init.log for kernel 3.4.4-4
Created attachment 601114 [details]
dmesg for kernel 3.4.6-1
dmesg for kernel 3.4.6-1, just updated.
Created attachment 601115 [details]
init.log for kernel 3.4.6-1
/run/initramfs/init.log for kernel 3.4.6-1
Created attachment 601118 [details]
init.log for kernel 3.4.2-1
/run/initramfs/init.log for kernel 3.4.2-1. This is a working boot.
Created attachment 601120 [details]
dmesg for kernel 3.4.2-1
dmesg for working boot. Kernel 3.4.2-1
Okay, I finally figured out how to configure grub2. This needs to be in a simple instruction someplace.
edit "/etc/default/grub" to remove quite and rghb as well as add rd.debug
run grub2-mkconfig -o /boot/grub2/grub.cfg
I have uploaded both non-working init.log and dmesg for the failed boots as well as the working files.
Is your /etc/crypttab setup correctly? What is your kernel command line?
Please attach /etc/crypttab
Dracut does not seem to find "rd.luks.uuid=luks-5bc868a4-39fb-4fe6-97cb-4979217fa9f9".
Created attachment 601354 [details]
I have uploaded the cryptab file. This file format has worked with kernels upto the current ones.
luks-5bc868a4-39fb-4fe6-97cb-4979217fa9f9 UUID=5bc868a4-39fb-4fe6-97cb-4979217fa9f9 /dev/urandom swap
You can remove that safely from the kernel command line for now. The real root should set it up for you later.
I am not sure what you mean. Do you mean to remove
from the command line in /etc/default/grub or remove
"luks-5bc868a4-39fb-4fe6-97cb-4979217fa9f9 UUID=5bc868a4-39fb-4fe6-97cb-4979217fa9f9 /dev/urandom swap"
from the crypttab?
And what do you mean by the "real root" should set it up later? Is this the actual "/" partition on the disk and when it is mounted?
Can I run "dracut initramfs-3.4.6-1.fc16.x86_64.img 3.4.6-1.fc16.x86_64" to create a new initramfs after making the changes to test the changes?
(In reply to comment #17)
> I am not sure what you mean. Do you mean to remove
> from the command line in /etc/default/grub
yes, and of course in /etc/grub2.cfg or /etc/grub.conf.
No need to recreate the initramfs and no need to run "grub2-mkconfig -o /boot/grub2/grub.cfg"
This worked. I wonder how this came about and when in the process it started as I never edited these files before.
I guess this means the bug can be closed unless this is an issue for others.
Thank you very much.