https://bugzilla.novell.com/show_bug.cgi?id=398356
User mail@steffen-moser.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=398356#c4
--- Comment #4 from Steffen Moser 2008-06-08 17:19:56 MDT ---
I hope that I can clarify it a bit:
- LILO has definitive the problem that it still cannot boot from MD devices
that have the superblock version 1.0 (at least the version of LILO that comes
with 11.0-RC1). MD devices created during the installation do have version 1.0,
so they lead to an unbootable system. I think that in this case, we can warn
the user and/or use superblock version 0.90 in this case for the boot device.
- Despite to my initial posting, GRUB in general is able to boot from MD
devices, no matter which superblock version they consist of.
When installing openSUSE-11.0-RC1 on a system partitioned as follows:
/dev/sda1 \
---- /dev/md0 -> SWAP
/dev/sdb1 /
/dev/sda2 \
---- /dev/md1 -> /boot
/dev/sdb2 /
/dev/sda3 \
---- /dev/md2 -> /
/dev/sdb3 /
the system may be unbootable.
The problem is that in this case, GRUB gets only installed to the MBR of
"/dev/sdb", but not to the MBR of "/dev/sda". Now it depends on the system
BIOS, which disk is selected for booting. In my test environment, the BIOS only
tried to boot from "/dev/sda" which had an empty MBR, as it was a completely
fresh install. After telling the BIOS to boot from "/dev/sdb", the system came
up cleanly. Installing GRUB also to "/dev/sda" manually made the system
bootable from both disks.
So I think, that when using GRUB, YaST2 (or "grub-install") should take care of
installing the boot code to the MBRs of all disks which are part of the MD
device that is used for booting.
I have only tested RAID level 1.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.