LinuxQuestions.org - Problems with /boot/grub/grub.conf not being read properly on reboots

Using CentOS 5.2 - current with updates

I have modified several parameters in my /boot/grub/grub.conf file and these modifications are not being applied on reboot. Although I don't consider myself an expert, I am not a total newb and am sure this is deeper than a misconfiguration in the file.

Some of the modifications I have made include commenting out the following lines with #:
default=0
timeout=5
hiddenmenu

I have also deleted an entire option for an older CentOS 5 kernel (2.6.18-92.el5xen) as I am now using 2.6.18-92.1.13.el5xen.

When I reboot, I still default to the first option, I still timeout in 5 seconds and it still hides the boot menu until I press a key. If I press a key I still have 3 options (the 2 xen kernels and windows which is on a separate drive) even though I only have 2 options in my /boot/grub/grub.conf file. I have checked and both /etc/grub and /boot/grub/menu.lst are linked to /boot/grub/grub.conf and as such are identical.

I am not running a separate boot partition like I normally do. Instead I have 3 drives running software raid. The root partition is a raid 1 array (md0) which is spread across /dev/sdb and /dev/sdc and uses 30GB of my 500 GB drives. The /boot is a directory on that array. There is also a RAID 5 array (md1) spread across /dev/sdb /dev/sdc and /dev/sdd used for storage (400+GB per drive) and my swap and /var/log are located in the remaining space on /dev/sdd.

I think the reason boot isn't being read is somehow related to the fact that is a directory on my root partition which is a RAID 1 array. Any ideas? BTW - I have searched the drive (find / -name grub.conf) for another grub.conf file and can't find any other than /boot/grub/grub.conf and the symlink in /etc/ I mentioned before.

Thanks in advance!!

-Craig