http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c1 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |snwint@suse.com Flags| |needinfo?(jreidinger@suse.c | |om) --- Comment #1 from Steffen Winterfeldt --- Hm, it says: bootloader/mbr_update.rb:20 Stage1: I wonder if this 'activate: false' is the correct thing. Josef? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c3 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@lwfinger.net Flags|needinfo?(jreidinger@suse.c |needinfo?(Larry.Finger@lwfi |om) |nger.net) --- Comment #3 from Josef Reidinger --- OK, I check logs and this is logs only from running system. I will need logs from that installation. Can you upload complete logs? You can get it with command `save_y2logs` that creates tarball for you and it should include also installation logs ( unless it is already rotated away ). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c5 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Larry.Finger@lwfi | |nger.net) | --- Comment #5 from Larry Finger --- Created attachment 763161 --> http://bugzilla.suse.com/attachment.cgi?id=763161&action=edit Saved YaST2 logs from installation I reinstalled from scratch using Build 151.1. As before, I had partition 7 with the legacy_boot flag set. After finishing the installation, that partition still had the flag set. If I selected the new Leap 15 installation for booting, I was then able to use the YaST2 => System => Boot Loader page to manipulate that flag. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c7 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Flags|needinfo?(jreidinger@suse.c |needinfo?(jsrain@suse.com) |om) | --- Comment #7 from Josef Reidinger --- Thanks for logs. Now it is clear for me what happened. Original proposal is boot from MBR and do not activate, because disk already have legacy_boot flag ( grub2 does not use it and for firmware any partition already marked is fine ). Then customer switched to boot from boot and we just change device for stage1,, but not setting for generic_mbr neither activate. That is reason why bootloader write warning: 2018-03-08 14:27:16 <1> install(3612) [Ruby] installation/proposal_runner.rb:514 proposal returns warning with level error and msg The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk. So question is if we should modify behavior and when boot from partition is pressed, if we should automatic mark generic_mbr to true and also activate? Jiri - what is your opinion on it? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c9 --- Comment #9 from Josef Reidinger --- Well, disadvantage is that when we ask user in popup it basically kills idea of one click change of proposal. In such case I think that even changing it automatically is better and if user want more control he can always use full bootloader. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1084017 http://bugzilla.suse.com/show_bug.cgi?id=1084017#c11 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED URL| |https://trello.com/c/K3qhjB | |6l Assignee|yast2-maintainers@suse.de |yast-internal@suse.de --- Comment #11 from Steffen Winterfeldt --- Tracking in YaST scrum board. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1084017 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jreidinger@suse.c | |om) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1084017 https://bugzilla.suse.com/show_bug.cgi?id=1084017#c14 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jreidinger@suse.c | |om) | --- Comment #14 from Josef Reidinger --- well, info was set to me. And to answer question if it is still relevant, answer is yes, as code is not changed at https://github.com/yast/yast-bootloader/blob/master/src/lib/bootloader/propo... where it will need probably distinguish if mbr or partition is set and adapt generic boot code and boot flag accordingly. -- You are receiving this mail because: You are on the CC list for the bug.