Description of problem: I can't boot kernel 3.6.9 on my machine because /dev/mapper/VolGroup-lv_root isn't found. Kernel 3.6.7 boots without problems Version-Release number of selected component (if applicable): kernel-3.6.9-4.fc18.x86_64 How reproducible: allways Steps to Reproduce: 1. Install kernel-3.6.9-4.fc18.x86_64 2. Reboot the system 3. Actual results: Boot progress aborts because /dev/mapper/VolGroup-lv_root is not found Expected results: System should boot without problems like kernel 3.6.7 does Additional info:
Is the initramfs present in /boot for this kernel? Does the grub2 config file specify it as well? Can you post dmesg output of the boot somehow? Without any data other than "can't find root", we aren't going to be able to tackle this one.
Created attachment 659586 [details] My grub.conf This is my current grub.conf. Do I have a chance to save the dmesg output for the failing kernel 3.6.9 boot if dracult says it can't boot because /dev/mapper/VolGroup-lv_root doesn't exist?
Created attachment 659593 [details] Content of /boot
Created attachment 662558 [details] Screenshot when boot process is aborted I've made a screenshot after booting kernel 3.6.9 and 3.6.10 stopped
(In reply to comment #4) > Created attachment 662558 [details] > Screenshot when boot process is aborted > > I've made a screenshot after booting kernel 3.6.9 and 3.6.10 stopped That isn't particularly helpful unfortunately. Can you boot an existing kernel that did work and attach the output of "dmesg" after a fresh boot? If you have some way of getting the full boot output from a failing boot via serial console, that would also be very helpful. Can you also put the initramfs for both a working and non-working kernel somewhere that they can be downloaded and inspected?
Created attachment 663910 [details] dmesg output This is the dmesg output from booting the working 3.6.7 kernel.
initramfs from kernel 3.6.7: http://www.fileswap.com/dl/W6mQtG7BN/initramfs-3.6.7-5.fc18.x86_64.img.html initramfs from kernel 3.6.10:
initramfs from kernel 3.6.10: http://www.fileswap.com/dl/BAOxo419Te/initramfs-3.6.10-4.fc18.x86_64.img.html
Any progress on this problem? BTW: rebuilding the initramfs doesn't solve this problem.
(In reply to comment #9) > Any progress on this problem? > > BTW: rebuilding the initramfs doesn't solve this problem. Not as of yet. I'm curious if rebuilding the initramfs for 3.6.7 will make your system not boot. Could you copy the existing initramfs somewhere safe, rebuild it, and reboot? At the moment, there are no other reports of lvm suddenly not working for people so if something is broken in the kernel just on your system that would be rather odd. Stranger things have happened though.
Sorryy, my fault. Rebuilding the initramfs for the kernels >= 3.6.9 doesn't solve the problem. So kernel 3.6.7 is the last bootable kernel for me.
(In reply to comment #11) > Sorryy, my fault. Rebuilding the initramfs for the kernels >= 3.6.9 doesn't > solve the problem. So kernel 3.6.7 is the last bootable kernel for me. Right, I understood that. I was asking you to try rebuilding the initramfs for 3.6.7 as well.
Kernel 3.6.7 doesn't boot too after rebuilding the initramfs.
(In reply to comment #13) > Kernel 3.6.7 doesn't boot too after rebuilding the initramfs. Ok, then this isn't something in the kernel. This is something in the initramfs that was updated around the same time as the 3.6.9 kernel. You might want to review your yum.log file and see what else was brought in.
$ sudo cat /var/log/yum.log|grep "Dec 06"|grep Updated Dec 06 22:04:13 Updated: systemd-libs-195-10.fc18.x86_64 Dec 06 22:04:17 Updated: systemd-195-10.fc18.x86_64 Dec 06 22:04:18 Updated: systemd-sysv-195-10.fc18.x86_64 Dec 06 22:04:19 Updated: libgudev1-195-10.fc18.x86_64 Dec 06 22:04:19 Updated: 32:bind-license-9.9.2-5.P1.fc18.noarch Dec 06 22:04:20 Updated: 32:bind-libs-9.9.2-5.P1.fc18.x86_64 Dec 06 22:04:21 Updated: 1:NetworkManager-glib-0.9.7.0-9.git20121004.fc18.x86_64 Dec 06 22:04:21 Updated: dnsmasq-2.64-1.fc18.x86_64 Dec 06 22:04:22 Updated: kernel-tools-libs-3.6.9-4.fc18.x86_64 Dec 06 22:04:23 Updated: ffmpeg-libs-1.0.1-1.fc18.x86_64 Dec 06 22:04:24 Updated: ffmpeg-1.0.1-1.fc18.x86_64 Dec 06 22:04:25 Updated: kernel-tools-3.6.9-4.fc18.x86_64 Dec 06 22:04:26 Updated: 1:NetworkManager-0.9.7.0-9.git20121004.fc18.x86_64 Dec 06 22:04:27 Updated: 32:bind-utils-9.9.2-5.P1.fc18.x86_64 Dec 06 22:04:27 Updated: 32:bind-libs-lite-9.9.2-5.P1.fc18.x86_64 Dec 06 22:04:28 Updated: systemd-analyze-195-10.fc18.x86_64 Dec 06 22:04:32 Updated: cjkuni-uming-fonts-0.2.20080216.1-51.fc18.noarch Dec 06 22:04:34 Updated: python-meh-0.19-1.fc18.noarch Dec 06 22:07:13 Updated: wqy-zenhei-fonts-0.9.46-9.fc18.noarch Dec 06 22:07:15 Updated: kernel-headers-3.6.9-4.fc18.x86_64
Or could dracut-024-10.git20121121.fc18.x86_64, which came with kernel 3.6.7, be the source of the problem?
(In reply to comment #16) > Or could dracut-024-10.git20121121.fc18.x86_64, which came with kernel > 3.6.7, be the source of the problem? It could well be, yes. The only other package that looks at all related in your list is the systemd updates, though those are current as far as I know. The latest dracut in f18 is dracut-024-15.git20121218.fc18. You might try updating to that and rebuilding the initramfs to see.
My dracut is already up2date: $ rpm -qa dracut dracut-024-16.git20121220.fc18.x86_64
(In reply to comment #18) > My dracut is already up2date: > > $ rpm -qa dracut > dracut-024-16.git20121220.fc18.x86_64 OK, that either means dracut itself isn't the problem, or it's still broken in that version if you're rebuilding initramfses with it. The fact that 3.6.7 worked originally and now doesn't when you rebuild the initramfs seems to show something is off. Were there other yum updates between 3.6.7 and 3.6.9?
Created attachment 667811 [details] yum.log between kernels 3.6.7 and 3.6.9 This is the part of the yum.log with the timeframe between kernel 3.6.7 and 3.6.9
Created attachment 667812 [details] yum.log between kernels 3.6.7 and 3.6.9
Okay, I got it. I've compared the contents of the working and non-working initramf-files and noticed that the non-working was missing the lvm module. After some further investigations I found out the lvm2 was missing on my system. After installing lvm2 and rebuilding the non-working initramf file everything works fine.
Very odd. Thanks for working through this one, it is much appreciated.