Bug 1282785
Summary: | Encrypted disk doesn't unlock with latest kernel, grub.cfg missing initrd16 configuration | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexander Todorov <atodorov> | ||||||||
Component: | grubby | Assignee: | Peter Jones <pjones> | ||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | high | ||||||||||
Version: | 24 | CC: | atodorov, bcl, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pjones | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2017-08-08 12:25:27 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Alexander Todorov
2015-11-17 12:13:42 UTC
You need to add the equivalent initrd16 line. Otherwise the initramfs is not loaded at all and the tools to help unlock the disks are not present. (In reply to Josh Boyer from comment #1) > You need to add the equivalent initrd16 line. Otherwise the initramfs is > not loaded at all and the tools to help unlock the disks are not present. I know that, the question is why wasn't this line automatically added in grub.cfg at the time I was upgrading my system. Something broke but I'm not quite sure how to reproduce or go hunt for it. It's a problem in grubby. There are many instances of something like this happening. I'll shift the bug over there as it is not a kernel problem. Please attach your /var/log/grubby file, and anything else relevant from the time of the upgrade (eg. check the journal for errors). Created attachment 1096516 [details]
/var/log/grubby
Created attachment 1096517 [details]
dnf.log
Look for events on Nov 16 around 09:00 AM
Created attachment 1096518 [details]
journalctl
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |