Mailinglist Archive: opensuse-bugs (4243 mails)

< Previous Next >
[Bug 1017778] bootloader is written to disk sdb, while this is not configured. System does not show the bootloader when sdb is selected.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 04 Jan 2017 19:13:42 +0000
  • Message-id: <bug-1017778-21960-zL0oEOwHhB@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1017778
http://bugzilla.opensuse.org/show_bug.cgi?id=1017778#c6

--- Comment #6 from Richard Bos <richard.bos@xxxxxxxxx> ---
From #c3:
Perhaps we should prevent installing generic code to MBR if GRUB is not
installed
on the first (according to the order) disk?

If installing the MBR does not make sense, it shouldn't be done.

I want to provide this system (the one I'm working with at the moment) with a
RAID-1 for the various partitions, so there will be a
/dev/md0 [sda1,sdb1]
/dev/md1 [sda2,sdb2]
etc

Now, when disk sda gets defect it should be possible to start from the second
disk, just by selecting the 2nd disk manually during system startup.
In this case the bootloader config can/must be the same (similar) for sda and
sdb.

See article that I referenced in 1017761#c0

With this in mind I find the YaST bootloader confusing. In the disk boot order
is set
sda and then sdb. But the bootloader is written to sdb... What is the reason
for the
disk order popup window? It's for this reason I opened #1017731#c0.

Let's see if this can be improved...

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References