http://bugzilla.opensuse.org/show_bug.cgi?id=916014
--- Comment #3 from Darren Freeman ---
I believe the reason for the BIOS not booting is that I put the 12.3 install on
a different USB memory stick than the 13.x, and so the BIOS treated it as a new
configuration and messed with what it was doing previously.
Something to think about. It's not always as simple as booting from a different
CD and getting the same outcome.
So finishing off.. have zeroed /dev/sda1, then added it to the RAID for /boot.
Fixed /etc/fstab, mounted it. YaST2 bootloader tool has a new option that I've
never seen before: "Enable redundancy for MD array". If this does what I hope
it does, i.e. write boot code to MBR of each disc, then I'm thoroughly
impressed.
Also a little puzzled as to why I've never seen this before. I've done quite a
few installs on this system. Maybe it's got something to do with the way that
I'm now using /dev/disk/by-id/md-name-xxx in fstab. Or it's because it's only
in the Qt version of YaST2.
Sadly it wouldn't boot. Welcome to Grub. Error: unknown filesystem. Entering
rescue mode. "grub rescue> _"
This can be a problem for later, I actually need this machine now.
Doesn't boot with bootloader install from ncurses mode and only MBR and custom
/dev/sda selected. Afraid there might be a hidden option still for redundant
install across the array.
Revert to a lonely /dev/sda1 boot partition... checked the option for MBR and
entered /dev/sda as custom boot partition. Note that /boot has been zeroed and
had a fresh filesystem put on it, with rsync copy the files over from the RAID.
So this is not due to some residual boot code in the partition. This method
from ncurses actually works. (Partly this is a note to myself in case of
disaster!)
Anyway, COOL. 12.3 seems pretty solid as far as my disc setup is concerned. It
was a reasonable assumption that 13.x should have worked on it. There is a huge
regression.
--
You are receiving this mail because:
You are on the CC list for the bug.