http://bugzilla.suse.com/show_bug.cgi?id=1142229
http://bugzilla.suse.com/show_bug.cgi?id=1142229#c20
Michael Chang
OK, so the last piece of information for making the best possible proposal.
Michal - when grub2 does not fit into extended partition? only for btrfs?
The btrfs booting requires bootloader to know how to reading for it, which means the boot code can't be realized by the size less than 512byte.
can we somehow detect it in advance that logical is only option when mbr gap is too small and also extended does not fit?
We came up with the patch for bsc#841247, the mbr has to be used as bootloader location and once the mbr gap too small is encountered, it will fallback to btrfs partition for core.img.
https://build.opensuse.org/package/view_file/Base:System/grub2/grub2-setup-t...
The mbr boot code in this case is not syslinux, but grub's own stage1, thus activation of ebr/pbr should be irrelevant. It looks like the report was YaST suggested to use EBR for grub2, which doesn't work for btrfs (it failed in a way like mbr gap, but "ebr too small"). IMHO YaST could go straight to use MBR for btrfs because above patch should workaround the occasion of mbr gap being too small. -- You are receiving this mail because: You are on the CC list for the bug.