http://bugzilla.opensuse.org/show_bug.cgi?id=1096066 http://bugzilla.opensuse.org/show_bug.cgi?id=1096066#c2 --- Comment #2 from Neil Rickert --- Created attachment 772556 --> http://bugzilla.opensuse.org/attachment.cgi?id=772556&action=edit A screenshot of the summary screen, showing the problem -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1096066 http://bugzilla.opensuse.org/show_bug.cgi?id=1096066#c4 --- Comment #4 from Neil Rickert --- I distinctly remember, from either openSUSE 12.3 or openSUSE 13.1, that changing the boot order did change which MBR was used. I was installing to an external drive at the time. The default was to install boot to "/dev/sda". By changing the disk order, it installed boot to the MBR of the external drive. Back to my test install. I repeated, and went ahead with the install. The newly installed system did boot from the second disk. I'm not sure what would have happened if I had chainloaded to "/dev/sdb" from my 42.3 install on the first drive. I guess I should test that. I went ahead and tried installing boot to "/dev/sda" (custom boot location). I did that with Yast bootloader on the installed system, rather than with a re-install. And that worked. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1096066 http://bugzilla.opensuse.org/show_bug.cgi?id=1096066#c9 --- Comment #9 from Josef Reidinger --- (In reply to richard bragg from comment #8)

As the person who raised the issue on the forum I found this change to be confusing. 42.3 just simply "refused" to install to MBR if boot order of disks is changed, Leap would always install to where /boot is located and this isn't highlighted clearly. It is mentioned but you have to read carefully that it will use MBR on "the wrong disk".

I've always installed Linux by changing boot order in BIOS, then installing O/S to sda (sdb is for data) and it has always installed and booted nicely. If MS need big patches to Windows I can change boot order in BIOS to let Windows do it's multiple reboots without needing to be there.

I am bit lost here. It should work with new way in Leap15, not? It will install it to sda if sda is the one without windows and sdb is only for data + windows, not? or you have sda with windows and linux, but want to boot linux with sdb? Then I worry the later one is really expert one which involves touches BIOS configuration and for that Boot Custom should work as intended. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1096066 http://bugzilla.opensuse.org/show_bug.cgi?id=1096066#c14 --- Comment #14 from Neil Rickert ---

And proposal is to add real devices that is used for install. So it will look like "boot from MBR (/dev/sda, /dev/sdb)" How do you like it?

Yes, that should be good. Anything that increases clarity and reduces ambiguity is good. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1096066 http://bugzilla.opensuse.org/show_bug.cgi?id=1096066#c16 --- Comment #16 from Josef Reidinger --- (In reply to richard bragg from comment #15)

Will there be any guidance on custom location? So if I want to put into MBR of a disk I enter /dev/sd? and it will get it right.

I did have one situation where somehow an extra disk showed up so my disk normally showing and sdb was actually sdc.

But in essence if I want GRUB to go to MBR of my second (data) disk I'd select Custom and enter /dev/sdb?

well, in such case as yast2-bootloader do not modify entry, but understand udev links, I suggest to put there udev link which is stable like /dev/disk/by-id/ ( replace disk_id with real udev name ) -- You are receiving this mail because: You are on the CC list for the bug.