В Sat, 01 Feb 2014 08:16:26 -0500
Anton Aylward
I'm not hoping that there's some way I can correct this,
Correct *what*? I still do not understand what the problem is. Did you install booltoader onto the "wrong" drive?
That's how it looks The bootloader for the 13.1 is on the drive that has the 12.3 and I can't boot the 12.3.
Can you boot 13.1? There are unfortunately mostly emotions and very little factual information in your message.
Yes, I've tried YAST/bootloader to put it on the drive with the 13.1 but that still leaves me with an inaccessble 12.3.
You tried it when? When you installed 13.1? After installation when you tried to repair?
And I'm not entirely sure about the drive with the 13.1......
Nor do I understand what you want to say here.
have the mbr of sda boot from the /boot on /sda and the mbr on sdb boot from the /boot on sdb.
To literally do what you describe you need to install generic MBR on both /dev/sda and /dev/sdb,
Yes I understand that.
mark partitions with /boot as active,
Yes I understand that
install bootloaders into /boot partitions boot block and somehow select your boot drive in BIOS every time you want to boot from another drive.
That's what I thought the install process on the new drive was doing. It appears it didn't.
It does what it is told. If you go to bootloader installation details, you will see various checkmarks (MBR, /boot, root etc). Yast will install bootloader boot code in every checked location. The one thing that may be confusing - MBR means "MBR of the very first drive" and you need to double check drive order and which drive is considered the first. I always prefer to uncheck everything and explicitly select disk where I want bootloader to be installed (on the same screen). Oh, and of course instead of using generic MBR + bootloader in partition you may just as well install bootloader into MBR directly. As long as no Windows is involved it is simpler and more robust.
I thought grub2 was supposed to scan for these things?
Which things? It is hard to guess what you expect here.
I thought that grub2 used something like os-prober to find all the available operating system images ...
it does but it is disabled by default in 13.1, you need to go into yast bootloader settings and enable it explicitly. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org