Username/Email:  Password: 
TwitterFacebookFlickrRSS
Home › Forums › Linux Support › Linux Kernel ›

Kernel not booting from grub.conf

May 29, 2009  By mateen
 in

HI All,

I have a New 64bit fedora 10 remote dedicated box from Hosting Company. I have updated its kernel from 2.6.27.21-170.2.56.fc10.x86_64 to 2.6.27.24-170.2.68.fc10.x86_64.

After rebooting Server its always boot from kernel-2.6.27.21-170.2.56.fc10.x86_64. It totally ignore the sequence of kernel booting defined in grub.conf. i have commented all older kernel entries in grub.conf except New one-2.6.27.24-170.2.68.fc10.x86_64. Even then it boot from older kernel 2.6.27.21-170.2.56.fc10.x86_64.

For information i have not installed lilo. Can anyone tell why and how server is booting from a specific kernel and not entertaining grub.conf.

I have checked the booting logs, server simply boot from kernel-2.6.27.21-170.2.56.fc10.x86_64 and not errors in logs. can someone tell me whats going on with my box.

Regards, mateen

‹ 2.6.13 char driver not working on 2.6.22 dual boot with suse n rehhat ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Grub Error:13

Ravi's picture
Submitted by Ravi (not verified) on Mon, 06/29/2009 - 10:05.

Dear All,
I've generated rootfs using buildroot and copied (rsync -av /opt/* /media/CF) on compact flash
copied kernel vmlinuz image to /boot and edited menu.lst and
then I have install grub using grub-install successfully
But now I'm getting following error.
Error 13: Invalid or unsupported executable format.

Can anyone help me

regards
Ravi

grub: Error 13

Ravi Phulsundar's picture
Submitted by Ravi Phulsundar (not verified) on Mon, 06/29/2009 - 10:02.

Dear All,
I've generated rootfs using buildroot and copied (rsync -av /opt/* /media/CF) on compact flash
copied kernel vmlinuz image to /boot and edited menu.lst and
then I have install grub using grub-install successfully
But now I'm getting following error.

Can anyone hepl me

regards
Ravi

Check /boot

Mitch Frazier's picture
Submitted by Mitch Frazier on Fri, 05/29/2009 - 16:17.

Make sure the kernel(s) you think you're booting exists in /boot.

It also might help to post your grub.conf in the forum.

Mitch Frazier is an Associate Editor for Linux Journal.

My problem has been solved

mateen's picture
Submitted by mateen on Sun, 05/31/2009 - 13:52.

Thanks Mitch Frazier:-

I have removed the /boot partition separately added for booting. MBR had
the boot entry on /, instead of /boot, which was causing the problem.