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 1324026
Summary: | Failed to start Cryptography Setup for luks | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Kaspar // Dee'Kej <deekej> | ||||
Component: | systemd | Assignee: | systemd-maint | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 23 | CC: | johannbg, jsynacek, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-12-20 19:48:48 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: |
|
Might be related to #1318045. See 'systemctl status "systemd-cryptsetup@luks\\x2d88f9...72.service"' for details. In addition it seems we are doing double escaping here. I'm not sure I will be able to run that command after the fail, but I will try it (next time it occurs). Unfortunately, I was not able to open any terminal/shell where I could see the details of 'systemctl status "systemd-cryptsetup@luks\\x2d88f9...72.service"'. (Pressing ALT+F1..F12, F1..F12, ESC, etc. did not work.) Once this happens, I am forced to do a hard-restart. Pressing CTRL+ALT+DELETE shows that the reboot should occur, but nothing happens as well. Is there any way I could see the details of previously failed boot after I make a successful boot (post-mortem)? (In reply to David Kaspar [Dee'Kej] from comment #3) > Is there any way I could see the details of previously failed boot after I > make a successful boot (post-mortem)? "journalctl -b-1" This might or might not yield anything useful depending on what exactly was started in the boot before it gets stuck. Hello Zbigniew, so it finally happened again. I tried to lookup what was the problem by using 'journalctl -b -1'. Unfortunately, there were no logs regarding the failed boot. What was going on: ------------------ 1) I reboot my system - logs are existing in journactl 2) Decryption failed - no logs are available in journalctl for this 3) Hard shutdown, started again sucessfully - logs continue from this point I really don't know what other info I can provide you... :-/ If you think of anything, I will try it next time this happens again. Dee'Kej Okay, so during the time, I have observed that the cryptography will FAIL when I type wrong encryption password 3 times in a row. (At least for current F24.) I guess this can be closed now, but here's a small idea: It would nice to inform the user that the machine has been "locked" and he has to do hard reset in order to try again... Best regards, Dee'Kej (In reply to David Kaspar [Dee'Kej] from comment #6) > Okay, so during the time, I have observed that the cryptography will FAIL > when I type wrong encryption password 3 times in a row. (At least for > current F24.) See bz#1381136. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |
Created attachment 1143780 [details] photo of bug Description of problem: systemd-cryptsetup fails to unlock encrypted partion on SSD Version-Release number of selected component (if applicable): systemd-222-14.fc23.x86_64 How reproducible: It happens occasionally. Approximately in 2/10 occurences. But once it happens, it usually repeats 2-3 times. Steps to Reproduce: 1. Create an encrypted BTRFS partition during Fedora installation. 2. Reboot your PC. 3. Write the correct password to unlock the encrypted partition. Actual results: Disk is not decrypted, booting fails, hard-reset is necessary. Expected results: Disk is descrypted and booting continues. Additional info: Whenever this happens, I am asked 3 times for the password entry. I'm pretty sure I write the password correctly. The keyboard layout used during password typing is Czech. My password contains special ASCII characters, but it does not contain any special Czech language characters.