<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 4/20/2014 11:53 PM, Chuck Tetlow
wrote:<br>
</div>
<blockquote cite="mid:20140421064755.M33790@tetlow.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta content="OPENWEBMAIL" name="GENERATOR">
I hate to bring up old topics - but I'm still experiencing this
problem. I'd held off asking about it - hoping further fixes
would correct it, but no luck.
<br>
<br>
One of our machines is a Centos based 5106R. It won't boot unless
I select the oldest kernel in the boot splash screen ->
2.6.18-308.11.1.el5. If I allow it to try the latest
2.6.18-371.6.1.el5, I get a kernel panic and lock up.
<br>
<br>
I tried Jason's fix down below. No luck.
<br>
<br>
Then I tried Michael's script. At first, I received complaints
about "-V" not a valid option for sort. Thought he might be
trying to do a unique sort, so changed the -V to -u and ran it
again. Still no luck.
<br>
<br>
So the machine won't reboot on its own. I've got to manually
select the oldest kernel to get it to boot.
<br>
<br>
Anyone know a fix for this issue? This isn't the Scientific Linux
most people with this problem was running - this is Centos. So
I'm at a loss, but need to fix it.
<br>
<br>
<br>
Chuck
<br>
<font size="2">
<br>
<br>
<b>---------- Original Message -----------</b>
<br>
From: "James" <a class="moz-txt-link-rfc2396E" href="mailto:james@slor.net"><james@slor.net></a> <br>
To: "'BlueOnyx General Mailing List'"
<a class="moz-txt-link-rfc2396E" href="mailto:blueonyx@mail.blueonyx.it"><blueonyx@mail.blueonyx.it></a> <br>
Sent: Sun, 17 Mar 2013 12:23:25 -0400 <br>
Subject: [BlueOnyx:12559] Re: Kernel Question <br>
<br>
> After doing what you did, if you should still end up with
any missing <br>
> entries in future you can do this (courtesy of Michael in
older thread): <br>
> <br>
> #!/bin/sh <br>
> # Setup newest Kernel as default: <br>
> KERNEL=`ls -k1 /boot/vmlinuz-*| sed s#/boot/vmlinuz-##|sort
-V -r|head -1` <br>
> /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod
--install \ <br>
> --make-default $KERNEL <br>
> cat /etc/grub.conf | grep -v ^serial |grep -v ^terminal
> <br>
> /boot/grub/grub.conf <br>
> <br>
> I actually ran into you issue with a recently-deployed
5108R - sounds like I <br>
> should have been surprised since it should have been
cleared up in that <br>
> release. At any rate, I made the symlink you did and ran
this script to <br>
> peruse my boot folder and build a proper grub.conf. <br>
> <br>
> > -----Original Message----- <br>
> > From: <a class="moz-txt-link-abbreviated" href="mailto:blueonyx-bounces@mail.blueonyx.it">blueonyx-bounces@mail.blueonyx.it</a>
[<a class="moz-txt-link-freetext" href="mailto:blueonyx">mailto:blueonyx</a>- <br>
> > <a class="moz-txt-link-abbreviated" href="mailto:bounces@mail.blueonyx.it">bounces@mail.blueonyx.it</a>] On Behalf Of
<a class="moz-txt-link-abbreviated" href="mailto:bluequartz@ozin.com">bluequartz@ozin.com</a> <br>
> > Sent: Sunday, March 17, 2013 11:26 AM <br>
> > To: 'BlueOnyx General Mailing List' <br>
> > Subject: [BlueOnyx:12558] Re: Kernel Question <br>
> > <br>
> > > Can you document the fix so we can choose to do
it? <br>
> > <br>
> > I did this myself in the end. Rebooted and it works so
I think I have it <br>
> right. <br>
> > <br>
> > First copy /etc/grub.conf to /boot/grub/grub.conf: <br>
> > <br>
> > rm /boot/grub/grub.conf <br>
> > cp /etc/grub.conf /boot/grub/grub.conf <br>
> > chmod 644 /boot/grub/grub.conf <br>
> > <br>
> > Then create a Symlink where /etc/grub.conf points to
/boot/grub/grub.conf <br>
> > <br>
> > rm /etc/grub.conf <br>
> > ln -s /boot/grub/grub.conf /etc/grub.conf <br>
> > <br>
> > Jason <br>
> > </font><br>
</blockquote>
<br>
<br>
<br>
<br>
What about a lower case -v <br>
<br>
<br>
<br>
Ken Marcus<br>
<br>
<br>
<br>
<br>
</body>
</html>