[Bug 969047] New: After upgrade on encrypted LVM system cannot decrypt volumes (initrd)
http://bugzilla.opensuse.org/show_bug.cgi?id=969047 Bug ID: 969047 Summary: After upgrade on encrypted LVM system cannot decrypt volumes (initrd) Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: beckjake+suse@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Overview: Something about the upgrade from 4.4.1-1 to 4.4.2-1 or dracut 044-3.1 -> 044-4.1 or another recent (last ~week) package change broke initrd for all installed kernels, even ones that existed before the upgrade. I'm currently on tumbleweed, version_id=20160229 Steps to Reproduce: * Install OpenSuse Tumbleweed a week ago * During setup, choose to have an encrypted LVM install with separate /home and / partitions + encrypted swap (not sure this is important) and an unencrypted /boot. * remove "quiet" and "splash" from kernel boot cmdline. In my case it was via /etc/default/grub and grub2-mkconfig * Perform kernel upgrade * reboot Actual behavior: After asking for my password to decrypt sda1 (swap), boot fails and dumps me into the dracut recovery prompt with a message that "/dev/mapper/system-root" couldn't be found. Expected behavior: Ask for my password once, boot to my login manager, etc. Additional information/tedious long-winded explanation: I have a Tumbleweed install that I set up a week ago Monday. During installation I opted for an LVM managed full-disk encryption that could suspend to disk. This ended up creating what looks like an encrypted swap partition on /dev/sda1 and a encrypted / and /home on /dev/sda3. /boot is at /dev/sda2, unencrypted. Yesterday I did an update with zypper, which included a kernel update from 4.4.1-1 to 4.4.2-1, (though there were a little over 300 updates total). Upon booting I get dropped into the dracut recovery shell with a message that "/dev/mapper/system-root" doesn't exist. It definitely doesn't, though system-swap does. One thing I noticed was that /dev/sda1 is the only entry in my /etc/crypttab under dracut, I'm not sure if that's normal or what. I was able to boot by doing:
cryptsetup -v luksOpen /dev/sda3 cr_sda3 # this gave me /dev/mapper/cr_sda3 lvm vgchange -a y system # this gave me /dev/mapper/system-root and /dev/mapper/system-home, plus /dev/system/root and /dev/system/home ^D // ctrl+d
Then it asked me for my password again for cr_ata-...-sda3. Finally it booted and I rebuilt initrd with
mkinitrd -f -v /boot/initrd-$(uname -r).img $(uname -r)
Now everything is fine (I can reboot, etc). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969047 http://bugzilla.opensuse.org/show_bug.cgi?id=969047#c1 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain@suse.com |trenn@suse.com --- Comment #1 from Jiri Srain <jsrain@suse.com> --- I could guess that this may have been a weird order of package updates, since (IIUC) after everything was upgraded, new re-created initrd serves well. Anyway, Thomas, do you want to have a look? Maybe there is a specific reason why this situation happened? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=969047 http://bugzilla.opensuse.org/show_bug.cgi?id=969047#c2 --- Comment #2 from Jacob Beck <beckjake+suse@gmail.com> --- In my /var/log/zypper/history, it looks like the very last thing to run as part of the update was in fact an mkinitrd, so I don't think it's just mkinitrd failing to run. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com