http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c1 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asarai@suse.de Flags| |needinfo?(asarai@suse.de) --- Comment #1 from Jiri Srain --- This looks to me like a comment to another bug unfortunately submitted as a new one? Can you, please, copy it where it belongs and close this one? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c3 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(asarai@suse.de) --- Comment #3 from Jiri Srain --- The very first sentence "Yes you read it right" sounds like an answer to someone else's comment. Anyway, as it is a new bug: Any chance to provide logs from the failed attempt to install? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c5 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin@suse.com, | |jsrain@suse.com Assignee|jsrain@suse.com |mchang@suse.com --- Comment #5 from Jiri Srain --- What I would hope in is some output of GRUB or shim installation, that might be helpful. Michael, any chance to guess what the reason of this behavior is? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c7 --- Comment #7 from Aleksa Sarai --- Sorry for not responding in so long. Currently I'm a bit cautious to do this with my laptop (my current install works). However, someone I know has found that this issue happens on their machine too (and is currently trying to reproduce it in a VM). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c8 --- Comment #8 from James Ye --- There appears to be multiple issues at play here: 1. YaST creates a different partition set-up with the same selected options when there are already partitions on the disk. This causes the different outcomes of install. 2. YaST attempts to create a too small btrfs partition in some circumstances. This causes the install failure. 3. GRUB is unable to boot with cryptodisk (maybe to do with UEFI Secure Boot?). This causes "error: Couldn't load sha256 hash." and "error: no such cryptodisk foud." I tested this in a KVM virtual machine using a 20GB virtual disk, using OVMF with Secure Boot. The partition setup I used each time in "Edit proposal settings" was to use encryption, do not create a separate /home and use btrfs for root. On the first install (with a blank disk), the partitioner automatically created an EFI System Partition, a 400MB /boot, and a LVM+LUKS container with / and swap. This installed and was booted successfully. On the second install, the partitioner automatically created an EFI System Partition, NO /boot partition, and the LVM+LUKS container. This installed successfully but does NOT boot, resulting in the GRUB sha256 hash error. On the third install, the same partitions are created as the first install. However, I manually overrided to partitioner to create the second partition setup, and also disabled Secure Boot in the firmware and in bootloader settings. This also failed to boot after install. Additionally, I noticed that after the third install the stub grub.cfg in the ESP had different UUIDs for the disk... Also I was able to boot my executing grubx64.efi from the EFI shell. So I think there are issues installing when overwriting an existing system. To sum up, the following scenarios can occur: A normal >= 400MB /boot partition is created and everything works. (VM, first install) A small (illegal) ~156MB /boot partition is created and the install fails. (My laptop) No /boot partition is created. The system cannot boot. (VM second and third installs) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c10 --- Comment #10 from James Ye --- Created attachment 689767 --> http://bugzilla.opensuse.org/attachment.cgi?id=689767&action=edit YaST log from install that fails to boot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c12 --- Comment #12 from Michael Chang --- (In reply to James Ye from comment #8)

There appears to be multiple issues at play here:

3. GRUB is unable to boot with cryptodisk (maybe to do with UEFI Secure Boot?). This causes "error: Couldn't load sha256 hash." and "error: no such cryptodisk foud."

It's fixed in Tumbleweed snapshot 20160826. And yes, it's UEFI Secure Boot related, as the sha256 module is missing from the signed grub.efi image. The new cryptsetup has changed it's default to sha256 for luks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=985346 http://bugzilla.opensuse.org/show_bug.cgi?id=985346#c14 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com Flags| |needinfo?(mchang@suse.com) --- Comment #14 from Jiri Srain --- Michael, regarding the 2nd case in comment#8: I'd expect the system to boot, just GRUB2 asking for LUKS password and then kernel asking again. IIRC this is the case in case of Power (where we got complaints about double entering password). Why is it not the case? Regarding different proposals: This is not necessarily a bug; the proposal code uses several algorithms to create the proposal and the contents of the disk changes the proposal. After all, it is only a proposal, not final decision. But it should boot. -- You are receiving this mail because: You are on the CC list for the bug.