Description of problem: After selecting kernel 3.2.3-2.fc16 from Grub menu system drops to dracut shell with warning, that it can't find root FS. I have encrypted root system setup with LVM and console says: --- Loading initial ramdisk No root device "block:/dev/mapper/vg_XXX-root" found LVM vg_XXX/swap not found LVM vg_XXX/root not found Dropping to debug shell sh: can't access tty: job control turned off --- Typing exit doesn't reboot the system, I have to reboot using CtrlAltDel, just displays the error above. During boot there is no prompt for the password for encrypted partition. I have to select kernel 3.1.9 to boot. Version-Release number of selected component (if applicable): 3.2.3-2 3.2.5-3 Fedora release 16 How reproducible: Steps to Reproduce: 1. Install system using encrypted root with LVM. 2. Upgrade to kernel 3.2.X. 3. Reboot system, choose kernel 3.2.X and observe system not booting.
Can you provide the output of: 1) dmesg from a good kernel boot 2) dmesg from a bad kernel boot 3) lspci -nn -vv
Created attachment 563935 [details] dmesg of failed boot
Created attachment 563936 [details] dmesg of successful boot
Created attachment 563937 [details] lspci -nn -vv
Can you boot the bad kernel with 'rd.debug' added to and 'rhgb' removed from the kernel command line and provide the output of that? For some reason the dracut luks module isnt' even running and getting that information might help us figure out why. Also, if you run: 'cryptsetup isLuks /dev/sda5' and 'cryptsetup luksUUID /dev/sda5' at the dracut shell what is the output?
Created attachment 567721 [details] failed dmesg with rd.debug without rhgb Sorry for the delay. cryptsetup fails with not found. There is no find in the environment, but I didn't find (manually) this executable in /bin, /sbin, /usr/bin, /usr/sbin.
Well... LUKs isn't going to work without cryptsetup in the initramfs. Harald, any ideas on this one?
(In reply to comment #7) > Well... LUKs isn't going to work without cryptsetup in the initramfs. > > Harald, any ideas on this one? The only idea, is that the initramfs was created without cryptsetup in the installation.
Is this still a problem? If yes, please attach the debug.txt of: # dracut -f --debug test.img "<kernel version of failing kernel>" 2>debug.txt # rm test.img
I can't test this easily, I've prevented upgrade of kernel on the machine and left it on 3.1.9, which just works. I'll test this in two weeks and let you know.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.