https://bugzilla.novell.com/show_bug.cgi?id=227377#c30
--- Comment #30 from Richard Creighton 2007-08-14 11:12:40 MST ---
This problem definitely still exists in Beta1 of 10.3. In fact, it destroyed
the grub config information in the IDE drive which I intentionally did not
include in the installation. I configured the MD raid IAW the instructions on
the openoffice.org HOWTO except I used 4 drives and chose raid 5 for the /home
partition (/dev/md3) in the attachment just submitted. Not only did it not
put the info in the correct area, but it ATE the info in the IDE drive which
was not part of the installation (which contained a valid 10.2 install) and
that install ceased to function on reboot AND the 10.3 install failed as well.
It took a day to figure out what happened and physical removal of the IDE
device to get the system to use the SATA drive for grub and then it used the
wrong partitions no matter what I tried. Finaly, it ended up putting the boot
on /dev/sdb which I still don't understand, but the system does boot now.
/dev/sdb is part of a 4 drive set, and is the 2nd of a 2 drive subset that
makes up /dev/md1 in the attachment which would not be where I would normally
have put the mbr or the grub files as that would be the 2nd drive of a raid 1
image partition. I manually fixed the grub files and got 10.3 to boot, but I
left them where the install system tried to put them. I was able to boot beta
1 10.3. I then put 10.2 back on and the 10.3beta grub config files had
overwritten the 10.2 files even though they were not suppposed to even be in
the loop at all. Grub has a problem when there are both IDE and SATA drives
and apparantly when there are MD drives involved as well. It took a day to
straighten out the 10.2 install files to get it to boot again. Now, I can
boot either install, 10.2 from the IDE or 10.3 from the MDraid on 10.3 by using
the BIOS boot selector. I am working to get grub on the 10.2 install to allow
me to select it without having to go through bios but that is not proving to be
easy for some reason, but that is another story.
--
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.