https://bugzilla.novell.com/show_bug.cgi?id=309040#c17 --- Comment #17 from Richard Creighton <rccj@ricreig.com> 2007-10-04 07:14:26 MST --- (In reply to comment #16 from Thomas Fehr)
I assume the problem only happens if /boot is also on a MD raid (necessarily a raid1).
Yes, I supplied a partitioning info but basically the IDE drive was self contained and had 10.2 on it and was supposed to be exempt. I set up the raid(s) plural IAW the HOWTO on the openSuSE website except for the one for the /home where I used a raid 5 and the example was a raid 1. Swap was a raid 0, Boot was a raid 1, Root was a raid 1 and home was raid 5 (raid 1 in the howto). Under 10.2, this worked perfectly and I could boot either installation, The one from the IDE drive OR the one contained on the RAID 1 MD installation /boot which had its own MBR which I could test by going to bios and selecting which device to boot from. It would boot properly even if I electrically removed the IDE drive and left only the MD Raid installations. There was NO stub drive anywhere. This is the way it is now with 10.3 once I got it to work by removing the IDE and manually fudging around with GRUB and eventually getting it to write a MBR in the /boot raid and by editing boot.lst manually I coulld boot properly (and still do). The problem only shows its head when the IDE drive is legacy equipment originaly HDxx and you are updating an installation on the SATA contained RAID. A gentleman who also posted to this bug had a different configuration that I could not help him solve completely but he added his logs but it is obvious it is based upon a very similar scenerio and his is also a pure MD Raid installation whereas mine had the complication of the other install. I also had a query from someone that had Windows that refused to boot after the install due to rewriting the MBR on the Windows drive destroying the Windows boot, but that I wasn't sure was related to MD Raid so I didn't mention it here before but it did relate to the renaming in the middle of an install problem that still seems to exist. The RC2 install went much nicer once I took out the IDE drive and even recognized there was a MD raid install to upgrade, it just didn't want to write back to the MD raid to update the grub/mbr even though the IDE drive wasn't there so it had nothing to do with the rename bug, Strictly the install to MD Raid. When I debugged it, It had swapped the MD0 and MD1 array (swap and boot) which I had put in a different order. I had to reinstall from scratch because there was too much damage when it wrote swap stuff in the boot partition before I could stop it. Like I said, close but no cigar. But the match stayed lit :) -- 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.