Kernel Update; Grub menu.lst updated incorrectly

[xboxboy]

When I performed my original install I was provided the server kernel. I am running a raid array and 4gb ram so I guess the installer assumes it's a server. So, one of my first tasks was to install the desktop kernel.

 

I have hard drives sda and sdb as the raid array, and I boot from drive sdc.

 

I use grub as the bootloader, the mbr points to sdc11 to the grub installed there (thats my 2009 install, which I wanted to keep) and from there I added a section to boot to sdc6, where my 2010 install is. I installed the bootloader for 2010 to the same partition, So I go through two bootloaders to get to 2010.

 

Upon the kernel change to desktop, as well as the kernel update through urpmi the other day, it boots to the first bootloader, where I choose 2010 to go to the second bootloader, but it says partition doesn't exist etc.

 

Here is how part of the menu.lst should look:

 

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title linux
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e resume=UUID=5a8732f5-8fd6-45eb-a7a3-0a68de5883e8 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title linux-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e resume=UUID=5a8732f5-8fd6-45eb-a7a3-0a68de5883e8
initrd (hd0,5)/boot/initrd.img

title failsafe
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e failsafe
initrd (hd0,5)/boot/initrd.img

 

But after updating the kernel this is what I have in menu.lst

 

Timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,5)/boot/gfxmenu
default 0

title linux
kernel (hd1,5)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e resume=UUID=5a8732f5-8fd6-45eb-a7a3-0a68de5883e8 splash=silent vga=788
initrd (hd1,5)/boot/initrd.img

ttle linux-nonfb
kernel (hd1,5)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e resume=UUID=5a8732f5-8fd6-45eb-a7a3-0a68de5883e8
initrd (hd1,5)/boot/initrd.img

title failsafe
kernel (hd1,5)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=8d98e80f-5ff9-4d31-8f99-22eacfead24e failsafe
initrd (hd1,5)/boot/initrd.img

 

I have no idea how to ensure that the next kernel update runs smoothly. I'm not sure if this is a configuration problem at my end, or a bug due to my unusual install.

 

If possible I would like the mbr to point straight to my 2010 install on sdc6 as I am happy enough to use it as my main system, and add a link to the 2009 bootloader.

[David Batson]

I've seen a couple of recent reports of a kernel update messing up GRUB. Likely a bug somewhere.

[xboxboy]

I've seen a couple of recent reports of a kernel update messing up GRUB. Likely a bug somewhere.

 

Ok, thanks David. Seems strange that it tries to change the hard disk it boots off ie. hd(0,5) versus hd(1,5)

 

Makes sense that it's likely a bug.

[xboxboy]

Yes it is a bug. Here is the link: Kernel update cause grub change disk device in menu.lst

 

By the looks no real intention of correcting it any time soon.

 

Simple answer is to ensure that the boot device is /dev/sda.

 

Mine isn't /dev/sda, mine is /dev/sdc, as sda and sdb are a raid data storage array. This is run through the intel onboard raid, and I'm not risking swapping drives to correct this. I will have to manually edit menu/lst by the looks. Strange as I didn't have this issue with 2009, but the bug is from back then.