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 1142125 - Newly created initramfs won't boot
Summary: Newly created initramfs won't boot
Keywords:
Status: CLOSED DUPLICATE of bug 1146749
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1144781 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-16 08:16 UTC by Nelson Chan
Modified: 2014-11-02 21:23 UTC (History)
4 users (show)

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

Attachments (Terms of Use)
Boot screenshot (424.58 KB, application/octet-stream)
2014-09-16 08:16 UTC, Nelson Chan 		no flags Details
View All

Description Nelson Chan 2014-09-16 08:16:14 UTC 
Created attachment 937902 [details]
Boot screenshot

Description of problem:

since recent kernel update kernel-3.16.2-200.fc20.x86_64
my system no longer able to boot after entering luks passphrase
 
the last messages on screen is  (see attached boot screenshot)
Reached target Encrypted Volume
Reached target System Initialization
Reached target Basic System
Found device /dev/mapper/bulldozer-root

last working kernel is
kernel-3.15.10-201.fc20.x86_64
kernel-3.11.10-301.fc20.x86_64

However if i try to rebuild initramfs for 3.11.10-301
 dracut  -f /boot/initramfs-3.11.10-301.fc20.x86_64.img 3.11.10-301.fc20.x86_64
it wont boot as well.


however if i rebuild initramfs without host specific for 3.16.2-200
 dracut -fN /boot/initramfs-3.16.2-200.fc20.x86_64.img 3.16.2-200.fc20.x86_64
Then it works.


This is a recent installation (fresh install 2 weeks ago)






Version-Release number of selected component (if applicable):

dracut-037-11.git20140402.fc20.x86_64





Additional info:


About my setup

2 drive - 1 SSD (System + home)  +  1 HDD (storage)

System is on LUKS/LVM - volumegroup1  (/ and /home;  /boot /boot/efi on physical partition)
HDD has LUKS/LVM - volumegroup2  (swap + storage)

LUKS on HDD has the same passphrase as System (setup during installation). HDD luks was added later.
and HDD luks added to /etc/crypttab
So on boot, it should as for my password and unlock BOTH luks.

i've also added intel_iommu=on to /etc/sysconfig/grub GRUB_CMDLINE_LINUX


Besides the above i cant think of anything that can be related.



Please let me know if more data is needed from my setup.
Comment 1 Graeme Vetterlein 2014-09-27 14:43:50 UTC 
I just did an update to: vmlinuz-3.16.3-200.fc20.x86_64
and it now prompts of luks and password (see defect https://bugzilla.redhat.com/show_bug.cgi?id=1144781 ) does it fix this also?
Comment 2 Zbigniew Jędrzejewski-Szmek 2014-09-27 23:21:46 UTC 
Is this on a Haswell processor? If yes, then most likely the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1146749.
Comment 3 Zbigniew Jędrzejewski-Szmek 2014-11-02 21:21:00 UTC 
*** Bug 1144781 has been marked as a duplicate of this bug. ***
Comment 4 Zbigniew Jędrzejewski-Szmek 2014-11-02 21:23:10 UTC 
With no response, I'll assume that my guess was correct.

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