[Bug 888052] New: dracut and LUKS-encrypted partitions
https://bugzilla.novell.com/show_bug.cgi?id=888052 https://bugzilla.novell.com/show_bug.cgi?id=888052#c0 Summary: dracut and LUKS-encrypted partitions Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 I upgraded from a long-working openSUSE 13.1 install to Factory. My first boot was not a happy one, as the new dracut system could not find my encrypted disk. I was able to (thanks to the emergency shell which mysteriously appeared after some time) cryptsetup the partition and continue the boot. I posited that /etc/crypttab needed to be explicitly set up, which I did and rebuilt the dracut initrd, and things have worked fine ever since. So, there are really two issues: 1. openSUSE 13.1 did not require /etc/crypttab (although I used it for swap, I did not use it for root) and - apparently - Factory does. 2. There is no indication as to /if/ or /when/ the emergency shell might appear - I could have saved myself a half-dozen failed boots if I had been more patient, but with an SSD even 30-60 seconds is a long time to wait. *Some* indication that "eventually, you might get an emergency shell" would be nice. Better yet, some way to get into the emergency shell right away would be /awesome/. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888052 https://bugzilla.novell.com/show_bug.cgi?id=888052#c Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |systemd-maintainers@suse.de AssignedTo|bnc-team-screening@forge.pr |lnussel@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888052 https://bugzilla.novell.com/show_bug.cgi?id=888052#c1 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfalken@opensuse.org AssignedTo|lnussel@suse.com |trenn@suse.com --- Comment #1 from Ludwig Nussel <lnussel@suse.com> 2014-08-11 17:24:17 CEST --- $ osc bugowner dracut Defined in package: Base:System/dracut bugowner of dracut : sfalken, trenn -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=888052 https://bugzilla.novell.com/show_bug.cgi?id=888052#c2 Thomas Renninger <trenn@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Thomas Renninger <trenn@suse.com> 2014-09-02 12:58:37 UTC ---
I posited that /etc/crypttab needed to be explicitly set up, which I did and rebuilt the dracut initrd, and things have worked fine ever since. According to Julian: He did a SLE11 to SLE12 upgrade and /etc/crypttab was there and things work. Could it be that you somehow manually set up the crypto fs and therefore did not had a /etc/fstab?
There is no indication as to /if/ or /when/ the emergency shell might appear Yep, but it is rather hard to access the console at this point of time. We had a quick look, but could not come up with a solution.
Sorry, I have to close this one won't fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com