What | Removed | Added |
---|---|---|
CC | jsrain@suse.com | |
Flags | needinfo?(jreidinger@suse.com) | needinfo?(jsrain@suse.com) |
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?