Comment # 3 on bug 1017778 from Jiri Srain

Well, YaST assumes that the disk you install to is the boot disk (and the order
in which the Linux kernel gets the disks and gives them names may depend on the
order of loading kernel modules if they are connected to different
controllers). Therefore the behavior may be correct as - based on BIOS settings
- /dev/sdb may really be the boot disk.

However, for your scenario when /dev/sda is in the order of disks listed as
first, I cannot really see whether/where it makes sense to write the generic
code. As long as GRUB is installed into /dev/sdbx, I cannot see any way how
generic code in MBR of /dev/sda could be of any use. Putting it to /dev/sdb
would make sense if any other loader chainloaded it, but then it could
chainload the boot sector with GRUB directly. Additionally, with c.a. 400 bytes
I doubt that the code is ready to run on anything else than 1st disk (in the
BIOS POV), which does not match the disk order in the screenshot.

Perhaps we should prevent installing generic code to MBR if GRUB is not
installed on the first (according to the order) disk?