RAID:After Kernel Update, grub menu.lst doesn't add new kernel to both HDDs

[leitner]

After successfully getting RAID 1 to be bootable on my Fedora 10 setup, I ran the update and one of the things updated was my kernel. It appears that the new kernel was added to the grub/menu.lst for the first HDD, but not for the second. Does this new kernel have to be added to the second HDD manually? Or was my bootable RAID not as successful as I hoped?

Here's my new menu.lst:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.27.12-170.2.5.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img


It appears that the first stanza following "hiddenmenu" was added after the kernel update.

[falko]

Add this stanza after the first kernel:
title Fedora (2.6.27.12-170.2.5.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.x86_64 ro root=/dev/md2 rhgb quiet
initrd /initrd-2.6.27.12-170.2.5.fc10.x86_64.img

Then run the Grub setup again.

If cat /proc/mdstat doesn't show any problems, then your RAID's working fine.

[leitner]

Thanks again Falko ... this does actually make sense to me.

But a question still remains: Must I do this each time I have a kernel update? Such updates are fairly frequent for Fedora (and, I suppose. other distros too, since they share the same kernel). I must assume the answer is yes, though it would be nice to somehow automate this. But I'm looking for some reassurance ...

Also, if the new kernel works fine, I don't see any need to keep any more than one previous version of the kernel in the grub menu.lst, correct?

By the way, "cat /proc/mdstat" shows exactly as in your HowTo, which is exactly what I expected.

Rich

[falko]

But a question still remains: Must I do this each time I have a kernel update?Yes.

Also, if the new kernel works fine, I don't see any need to keep any more than one previous version of the kernel in the grub menu.lst, correct?Yes. But you can keep the old kernels as a fallback.

[leitner]

Great, that's what I'll do. I usually kept the previous kernel around until I was satisfied that everything worked as expected under the new kernel, and that seems like a good strategy to keep here.

I think I will "test" the RAID setup today by removing one of the disks and rebooting ... I've been reluctant to do this yet, but it really should be done.