Bug 1418218 - boot after 'reboot' doesn't prompt for LUKS passphrase in grub / plymouth
Summary: boot after 'reboot' doesn't prompt for LUKS passphrase in grub / plymouth
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-01 09:59 UTC by Andrew Hatfield
Modified: 2017-04-19 23:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-19 23:56:59 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Andrew Hatfield 2017-02-01 09:59:56 UTC 
Description of problem:

If you have a root partition protected with LUKS and restart with 'reboot', on next boot you are never prompted to enter your LUKS passphrase and the boot never completes.


Version-Release number of selected component (if applicable):
Fedora 25
4.9.6-200.fc25.x86_64 and 4.9.4-201.fc25.x86_64

How reproducible:
each time

Steps to Reproduce:
1.  log into gnome as a normal user
2.  Open gnome-terminal
3.  sudo su -
4.  reboot

Actual results:
At boot screen the LUKS passphrase prompt is not displayed as it is from a cold poweron.  Boot never completes, waits indefinitely

Expected results:
Same behaviour as cold poweron and grub / plymouth displays LUKS passphrase.

Additional info:
Comment 1 Zbigniew Jędrzejewski-Szmek 2017-02-01 17:26:40 UTC 
I think that's unlikely. There is very little difference between a reboot and a cold boot. Maybe try booting without "quiet rhgb" on the kernel commadn line and enter the password through the text interface.
Comment 2 Andrew Hatfield 2017-04-19 23:56:59 UTC 
I've just tested this again on Fedora 25 4.10.10-200-fc25.x86_64 and it correctly prompts for LUKS passphrase at boot time
Note You need to log in before you can comment on or make changes to this bug.