| Summary: | Disk encryption fails - Entering emergency mode & dracut shell | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | anaconda-maint-list, bugproxy, g.kaviyarasu, jkachuck, jonathan, vanmeeuwen+fedora, vpodzime, wgomerin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ppc64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-14 06:00:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Attachments: | |||
Created attachment 821797 [details]
encrypted root manual partitioning screen
Created attachment 821798 [details]
Serial console logs from affected machine
Created attachment 821799 [details]
Some last lines from Journalctl command output
Created attachment 821800 [details] rdsosreport.txt as mentioned in IBM comment # 6 Could you please provide the storage.log file? (either under /tmp/ during the installation process, or /var/log/anaconda on the installed system) Created attachment 823434 [details]
anaconda.storage.log file from installed system
------- Comment on attachment From shubgoya.com 2013-11-13 08:07 EDT-------
Am attaching "anaconda.storage.log" file from installed system. Although this bug is bit inconsistent. I can confirm one scenario where its happening for me in release TC6.0. After providing incorrect password twice for the encrypted root, my system is dropping to dracut shell. Am sure that it was dropping to dracut shell even after providing a correct password earlier in Alpha drop.
Could you please retest this with F20-Beta? There has been some issues with console keymap loading before disk unencryption that may cause issues you describe. Thanks! ------- Comment From shubgoya.com 2013-11-13 20:07 EDT------- I tried with F20-Beta & now am able to reproduce this issue only when am entering wrong LUKS password 3 times. Below are the error logs: [ 130.615075] bio: create slab <bio-0> at 0 [FAILED] Failed to start Cryptography Setup for luks-37cb82f3...6-dad1dbc71397. See 'systemctl status systemd-cryptsetup@luks\x2d37cb82f3\x...ice' for details. [DEPEND] Dependency failed for Encrypted Volumes. [DEPEND] Dependency failed for Initrd Default Target. [ 130.862211] systemd[1]: Starting Emergency Shell... [ 130.864943] systemd[1]: Stopped dracut initqueue hook. [ 130.865236] systemd[1]: Stopped Forward Password Requests to Plymouth. [ 130.865357] systemd[1]: Stopping Forward Password Requests to Plymouth Directory Watch. [ 130.865460] systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch. [ 130.865490] systemd[1]: Stopping Show Plymouth Boot Screen... [ 130.865580] systemd[1]: Stopped Show Plymouth Boot Screen. [ 130.865632] systemd[1]: Stopping udev Coldplug all Devices... [ 130.865658] systemd[1]: Stopped udev Coldplug all Devices. [ 130.865868] systemd[1]: Starting Journal Service... [ 130.867798] systemd[1]: Stopped udev Kernel Device Manager. [ 130.867874] systemd[1]: Stopping Create static device nodes in /dev... [ 130.867901] systemd[1]: Stopped Create static device nodes in /dev. [ 130.867968] systemd[1]: Stopping Create list of required static device nodes for the current kernel... [ 130.867996] systemd[1]: Stopped Create list of required static device nodes for the current kernel. [ 130.868056] systemd[1]: Stopping udev Kernel Socket. [ 130.868083] systemd[1]: Closed udev Kernel Socket. [ 130.868113] systemd[1]: Stopping udev Control Socket. [ 130.868146] systemd[1]: Closed udev Control Socket. [ 130.871400] systemd-journald[444]: Received SIGTERM [ 130.872792] systemd[1]: Starting Journal Service... [ 130.873466] systemd[1]: Started Journal Service. [ 130.879654] systemd-journald[2421]: Vacuuming done, freed 0 bytes Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. (In reply to IBM Bug Proxy from comment #8) > ------- Comment From shubgoya.com 2013-11-13 20:07 EDT------- > I tried with F20-Beta & now am able to reproduce this issue only when am > entering wrong LUKS password 3 times. Below are the error logs: > > [ 130.615075] bio: create slab <bio-0> at 0 > [FAILED] Failed to start Cryptography Setup for > luks-37cb82f3...6-dad1dbc71397. > See 'systemctl status systemd-cryptsetup@luks\x2d37cb82f3\x...ice' for > details. > [DEPEND] Dependency failed for Encrypted Volumes. > [DEPEND] Dependency failed for Initrd Default Target. > [ 130.862211] systemd[1]: Starting Emergency Shell... > [ 130.864943] systemd[1]: Stopped dracut initqueue hook. > [ 130.865236] systemd[1]: Stopped Forward Password Requests to Plymouth. > [ 130.865357] systemd[1]: Stopping Forward Password Requests to Plymouth > Directory Watch. > [ 130.865460] systemd[1]: Stopped Forward Password Requests to Plymouth > Directory Watch. > [ 130.865490] systemd[1]: Stopping Show Plymouth Boot Screen... > [ 130.865580] systemd[1]: Stopped Show Plymouth Boot Screen. > [ 130.865632] systemd[1]: Stopping udev Coldplug all Devices... > [ 130.865658] systemd[1]: Stopped udev Coldplug all Devices. > [ 130.865868] systemd[1]: Starting Journal Service... > [ 130.867798] systemd[1]: Stopped udev Kernel Device Manager. > [ 130.867874] systemd[1]: Stopping Create static device nodes in /dev... > [ 130.867901] systemd[1]: Stopped Create static device nodes in /dev. > [ 130.867968] systemd[1]: Stopping Create list of required static device > nodes for the current kernel... > [ 130.867996] systemd[1]: Stopped Create list of required static device > nodes for the current kernel. > [ 130.868056] systemd[1]: Stopping udev Kernel Socket. > [ 130.868083] systemd[1]: Closed udev Kernel Socket. > [ 130.868113] systemd[1]: Stopping udev Control Socket. > [ 130.868146] systemd[1]: Closed udev Control Socket. > [ 130.871400] systemd-journald[444]: Received SIGTERM > [ 130.872792] systemd[1]: Starting Journal Service... > [ 130.873466] systemd[1]: Started Journal Service. > [ 130.879654] systemd-journald[2421]: Vacuuming done, freed 0 bytes > Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist > Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist > Warning: /dev/mapper/luks-37cb82f3-95f6-4a7c-8406-dad1dbc71397 does not exist > > Generating "/run/initramfs/rdsosreport.txt" > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or > /boot > after mounting them and attach it to a bug report. That's an expected behaviour. No additional info needed, I'm closing this bug. If you think such behaviour is wrong, please reopen this bug and reassing it to the 'dracut' component. |
== Comment: #0 - Shubham Goyal <shubgoya.com> - 2013-10-31 14:15:28 == Description of problem: I did a fresh installation with /root as encrypted. To check my disk layout please check attachment #1 [details] from manual partitioning screen. After providing all details & encryption password I continued with installation. Post installation my system went to emergency mode & dracut shell. It seems that disk encryption is not working. How reproducible: Always Version-Release number of selected component (if applicable): 3.11.0-300.fc20.ppc64p7 : junoiocplus2-lp4 Steps to Reproduce: 1) Perform a fresh install with / as encrypted partition. 2) Post install you will get this error. Actual results: System went to emergency mode & dracut shell Expected results: System should be installed properly & after providing encrypted password system should boot Additional info: Attaching snapshot of error & all relevant logs == Comment: #10 - Kamalesh Babulal <kamaleshb.com> - 2013-11-08 04:03:39 == The installation is successfully, if the LVM is not encrypted.