Created attachment 939622 [details] a targ gz of severla files ( old-kernel-no-passphrase.txt Problem-Description: rdsosreport-newkernel.txt old-kernel-with-passphrase.txt saved-files ) Description of problem: Version-Release number of selected component (if applicable): Fedora20: 3.16.2-200.fc20.x86_64 How reproducible: Every reboot Steps to Reproduce: 1. Create system as described (LUKS etc) 2. reboot 3. Actual results: Attached files show failing boot (new kernel) and two boots of 3.15.10-201.fc20.x86_6 Expected results: Prompt for LUKS password, and normal boot. Additional info: This has some things in common with BUG1142125
Created attachment 939623 [details] Just the problem description (to save doawloding tar (gz) file 20Sep2014: G Vetterlein graeme.fedora On Fedora20. Got a message "reboot to install updates" accepted this, it rebooted install updates, then failed to reboot: New ===> menuentry 'Fedora (3.16.2-200.fc20.x86_64) Old ===> menuentry 'Fedora (3.15.10-201.fc20.x86_64) If I reboot and select Old(see above) from grub menu the boot proceeds normally. My reading of this the "recent upgrade has broken boot" The system is as follows: 64 bit Intel processor. 16Gb RAM Disk#1 SSD 32GB. Two fdisk partitions (2nd is unused) Partition#1 is LVM (root & swap) Disk#2 HDD 2TB. Single partition (LUKS encrypted) entire encrypted partition is LVM (pgroup = WD2TB) To help debug this, I captured output of the failing boot. I then rebooted with the OLD kernel but deliberately failed to provide a passphrase, so boot failed (seems similar) then rebooted with old kernel and DID PROVIDE THE PASSPHRASE. Hint: search for SIGRTMIN+20 to see where logs diverge. [ there is no prompt of passphrase with the new kernel ] I have attached: 83078 Sep 20 16:56 rdsosreport-newkernel.txt 110031 Sep 20 17:14 old-kernel-no-passphrase.txt 212393 Sep 20 17:14 old-kernel-with-passphrase.txt 178 Sep 20 17:31 Problem-Description: rdsosreport-newkernel.txt: Was copied to /boot from the failing boot shell old-kernel-no-passphrase.txt: Is a boot of the OLD kernel, I DID NOT provide a passphrase, so boot failed this is the (last bit of) the output of journalctl from the emergency shell old-kernel-with-passphrase.txt: Is a boot of the OLD kernel, I PROVIDED THE PASSPHRASE , so the boot succeeded this is the output of journalctl from normal shell (so is much bigger)
Does it work, if you add rd.luks.uuid=luks-2cca3cd6-7807-4239-a6a7-218e3aca43e0 to the kernel command line?
(In reply to Harald Hoyer from comment #2) > Does it work, if you add > rd.luks.uuid=luks-2cca3cd6-7807-4239-a6a7-218e3aca43e0 > to the kernel command line? Yes that boots. Please find attached: grub.cfg dmesg.log Additionally, recent update using: vmlinuz-3.16.3-200.fc20.x86_64 also boots (it appear in grub.cfg)
Created attachment 945760 [details] modified grub.cfg to include to option you gave + later kernel with boots Boots with mod as provided. Also later entry boots
Created attachment 945761 [details] dmesg of working boot, with the mod given This is just dmesg ... I can provide bigger logs if required.
Suggest you look @ https://bugzilla.redhat.com/show_bug.cgi?id=1142125 As possible dupe?
Should we not marked this closed?
*** This bug has been marked as a duplicate of bug 1142125 ***