David C. Rankin wrote:
James Knott wrote:
I did all that, as per the directions. I tried it a couple of times and the result was the same. I couldn't even boot in rescue mode and mount /boot, as it complained it was part of a RAID array. How is a booting computer supposed to deal with RAID, when it can't even load the necessary software to do that? Creating RAID arrays is not the problem. Booting one is, even though I used RAID 1 for /boot..
James,
That is kind of weird. Currently I have 4 different each spinning a software RAID 1 array and I have done it the same way each time and I have never had any complaint from grub or any other package that /boot was inside a raid array. In fact all 4 of my RAID installs have /boot inside the array, 3 with separate /boot partitions and one with /boot as part of /.
Several months ago, maybe 6 months or so, the same discussion about /boot inside of RAID went across the list and I can't remember what resolution was reached. It could be a controller issue. I have 2 of the arrays on nVidia controllers and 2 on Promise controller (all fake raid controllers)
One thing that is worth checking is the BIOS. As with my previous posts on 3 out of 4 of my machines you must specifically set the raid array as bootable in the BIOS. It is usually as sub-screen on the 3rd or 4th main screen of the BIOS. I have had trouble finding the setting before, but if I keep digging, I always run into it. This is definitively work checking into, especially if the MB is advertised as having any type of RAID capabilities under windows.
Hope this helps, keep plugging away at it.
I've got it going now. The trick was to put Grub on the MBR. I don't see that mentioned anywhere in those directions. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org