

Yes, it does interfere.ronin78 wrote:The wiki tutorial explains how to install GRUB on each drive of the RAID 1, so I thought I could do that for both of the RAID 1s below the RAID 0 and it would work out fine (GRUB can't see RAID arrays, only physical drives, so I did not think the RAID 0 would interfere).
Okay, thanks for clearing that up. I should have known better than to try to be creative this early in my gentoo career. Any advice on how to change the /boot partition to one of the RAID1 arrays without redoing the installation?cyrillic wrote:Yes, it does interfere.
During the boot process, GRUB expects to find its files all on 1 physical device. Since RAID0 splits the filesystem across multiple devices, this configuration doesn't work. RAID1 is ok because 100% of the data is on each physical device.


Thanks to Jorge and NS for your help on this. I have not decided whether to use all four drives or only two as boot sectors (it depends on if I could find any use for the other RAID1). Originally, my installation had been running non-stop, but due to a power failure last night, I will have to boot from the LiveCD again. If I understand you both correctly, I should restart all of the RAIDs as they were (including md1), copy the /boot to another space on the hard drive, unmount /boot and take md1 offline, delete md1, reinitialize the RAIDs, mount md5 (as two or four drives) as /boot and move the copy back onto it. I can then follow the wiki instructions for getting grub running on each of the drives.jmbsvicetto wrote:Hi.
You just need to boot with the live-cd, mount your partitions, chroot and install GRUB again. I would suggest you use md5 or md6 and delete md1. Although you install GRUB into /dev/md5 or /dev/md6, on the grub.conf file and when running grub you use hd(X,Y) to refer to one of the partitions that is part of the array. In other words, you can't tell GRUB to use the /dev/mdX devices.


I double-checked and they are all bootable, but still no luck. The boot partitions are ext3 filesystems of the "fd", or Linux RAID auto-detect type, as per the RAID wiki instructions. I have sent an e-mail to Intel tech support to see if they are any help; good community support for the motherboard would be much nicer.NeddySeagoon wrote:ronin78,
Some BIOS's are very picky about having a partitkon flagged bootable. Others don't care.
Use fdisk to check that your /boots (each part of the mirror) has the bootable flag set.
Set it if required and try again.
appears at boot up at attempting to boot the new system.Error 15 file not found
(hd0,5)/kernel-genkernel-x86_64-2.6.16-gentoo-r9 does not exist because you probably did not copy your kernel to Gentoo's root. Genkernel copied it to Gentoo's /boot directory, fix your grub entry as decribed in the handbook. Please also notesnakeo2 wrote:error 15 file not found
...
title= Gentoo Server
root (hd0,5)
kernel /kernel-genkernel-x86_64-2.6.16-gentoo-r9 root=/dev/ram0 init=linuxrc ramdisk=8192 real_root=/dev/sda6
initrd /initramfs-genkernel-x86_64-2.6.16-gentoo-r9
Hthhandbook wrote:Besides, if you chose to use a different partitioning scheme and did not put /boot in a separate partition, the /boot prefix used in the above code samples is really required. If you followed our suggested partitioning plan, the /boot prefix it not required, but a boot symlink makes it work. In short, the above examples should work whether you defined a separate /boot partition or not.


Code: Select all
title= Gentoo Server
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-2.6.16-gentoo-r9 root=/dev/ram0 init=linuxrc ramdisk=8192 real_root=/dev/sda6
initrd /boot/initramfs-genkernel-x86_64-2.6.16-gentoo-r9Code: Select all
default 0
timeout 4
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=Gentoo Linux 2.6.16-r9
root (hd0,0)
kernel /boot/kernel-genkernel-x86-2.6.16-gentoo-r9 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev vga=0x317
initrd /boot/initramfs-genkernel-x86-2.6.16-gentoo-r9