Posted May 29th, 2009 by mateen

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.
Ravi's picture

Grub Error:13

On June 29th, 2009 Ravi (not verified) says:

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

Ravi Phulsundar's picture

grub: Error 13

On June 29th, 2009 Ravi Phulsundar (not verified) says:

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

Mitch Frazier's picture

Check /boot

On May 29th, 2009 Mitch Frazier says:

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 and the Web Editor for linuxjournal.com.

mateen's picture

My problem has been solved

On May 31st, 2009 mateen says:

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.

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

See more Linux Journal Videos

From the Magazine

December 2009, #188

If last month's Infrastrucuture issue was too "big" for you then try on this month's Embedded issue. Find out how to use Player for programming mobile robots, build a humidity controller for your root cellar, find out how to reduce the boot time of your embedded system, and if you're new to embedded systems find out the basics that go into one. You can also read about the Beagle Board, the Mesh Potato and a spate of other interestingly named items. And along with our regular columns don't miss our new monthly column: Economy Size Geek.


Read this issue