Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1144781 - following update to 3.16.2-200.fc20.x86_64, boot now hangs
Summary: following update to 3.16.2-200.fc20.x86_64, boot now hangs
Keywords:
Status: CLOSED DUPLICATE of bug 1142125
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-20 17:27 UTC by Graeme Vetterlein
Modified: 2014-11-02 21:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-02 21:21:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
a targ gz of severla files ( old-kernel-no-passphrase.txt Problem-Description: rdsosreport-newkernel.txt old-kernel-with-passphrase.txt saved-files ) (69.73 KB, application/octet-stream)
2014-09-20 17:27 UTC, Graeme Vetterlein 		no flags Details
Just the problem description (to save doawloding tar (gz) file (2.94 KB, text/plain)
2014-09-20 17:33 UTC, Graeme Vetterlein 		no flags Details
modified grub.cfg to include to option you gave + later kernel with boots (5.44 KB, text/plain)
2014-10-10 17:55 UTC, Graeme Vetterlein 		no flags Details
dmesg of working boot, with the mod given (79.83 KB, text/plain)
2014-10-10 17:56 UTC, Graeme Vetterlein 		no flags Details
View All

Description Graeme Vetterlein 2014-09-20 17:27:32 UTC 
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
Comment 1 Graeme Vetterlein 2014-09-20 17:33:40 UTC 
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)
Comment 2 Harald Hoyer 2014-10-09 09:31:15 UTC 
Does it work, if you add 
rd.luks.uuid=luks-2cca3cd6-7807-4239-a6a7-218e3aca43e0
to the kernel command line?
Comment 3 Graeme Vetterlein 2014-10-10 17:52:26 UTC 
(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)
Comment 4 Graeme Vetterlein 2014-10-10 17:55:14 UTC 
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
Comment 5 Graeme Vetterlein 2014-10-10 17:56:22 UTC 
Created attachment 945761 [details]
dmesg of working boot, with the mod given

This is just dmesg ... I can provide bigger logs if required.
Comment 6 Graeme Vetterlein 2014-10-10 17:59:14 UTC 
Suggest you look @
https://bugzilla.redhat.com/show_bug.cgi?id=1142125

As possible dupe?
Comment 7 Graeme Vetterlein 2014-11-02 16:48:52 UTC 
Should we not marked this closed?
Comment 8 Zbigniew Jędrzejewski-Szmek 2014-11-02 21:21:00 UTC 

*** This bug has been marked as a duplicate of bug 1142125 ***
Note You need to log in before you can comment on or make changes to this bug.