Bugzilla – Bug 1049359
System does not boot after upgrade to the latest version
Last modified: 2017-07-27 07:17:56 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Build Identifier: After applying upgrade system stops booting. My configuration is encrypted LVM volume. Packages: ucode-intel-20170511-7.3.1 grub2-2.02~beta2-94.3.1 latest kernel in opensuse 42.2 Reproducible: Always Steps to Reproduce: 1. Install OpenSuse 42.2 and create encrypted LVM volume 2. Restart 3. sudo zypper up 3. Restart Actual Results: See attached screenshot Expected Results: System boots up
Created attachment 732911 [details] Log file from upgrading
Created attachment 732912 [details] Console errors after upgrade boot
As you have reported this against a maintenance update, can I please ask you to roll back updates until you find the minimal set that triggers this, out of the 696 in the log. You mentioned ucode-intel, grub2 and kernel-source, please start with these.
Also please don't touch the priority field. It's the field adjusted by developer side.
As this is my main machine I don't want to reboot it since bringing it back to normal state is a little bit problematic at least. I would bet on ucode-intel package upgrade or grub since I locked kernel version and I bet that if I restart it now it won't be able to boot. All other packages are just boilerplate, just wanted you to have full update log. If you want any log files or configuration files I can provide them since it is running now.
Created attachment 732949 [details] Output from lsinitrd command
Please let us know when you can isolate the package.
It seems that this is the same issue as in https://bugzilla.opensuse.org/show_bug.cgi?id=904987 but in Leap
Also did a fresh install of leap 42.2 but with online repositories enabled and hit the same issue.
Same issue here after latest updates. Rolling back updates isn't possible for me unfortunately.
This is a duplicate of issue: https://bugzilla.suse.com/show_bug.cgi?id=1048679 *** This bug has been marked as a duplicate of bug 1048679 ***