[BlueOnyx:15237] Re: Kernel Question

[Ken Marcus]

On 4/20/2014 11:53 PM, Chuck Tetlow wrote:
> 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.
>
> 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.
>
> I tried Jason's fix down below.  No luck.
>
> 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.
>
> So the machine won't reboot on its own.  I've got to manually select 
> the oldest kernel to get it to boot.
>
> 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.
>
>
> Chuck
>
>
> *---------- Original Message -----------*
> From: "James" <james at slor.net>
> To: "'BlueOnyx General Mailing List'" <blueonyx at mail.blueonyx.it>
> Sent: Sun, 17 Mar 2013 12:23:25 -0400
> Subject: [BlueOnyx:12559] Re: Kernel Question
>
> > After doing what you did, if you should still end up with any missing
> > entries in future you can do this (courtesy of Michael in older 
> thread):
> >
> > #!/bin/sh
> > # Setup newest Kernel as default:
> > KERNEL=`ls -k1 /boot/vmlinuz-*| sed s#/boot/vmlinuz-##|sort -V 
> -r|head -1`
> > /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install \
> > --make-default $KERNEL
> > cat /etc/grub.conf | grep -v ^serial |grep -v ^terminal >
> > /boot/grub/grub.conf
> >
> > I actually ran into you issue with a recently-deployed 5108R - 
> sounds like I
> > should have been surprised since it should have been cleared up in that
> > release.  At any rate, I made the symlink you did and ran this 
> script to
> > peruse my boot folder and build a proper grub.conf.
> >
> > > -----Original Message-----
> > > From: blueonyx-bounces at mail.blueonyx.it [mailto:blueonyx-
> > > bounces at mail.blueonyx.it] On Behalf Of bluequartz at ozin.com
> > > Sent: Sunday, March 17, 2013 11:26 AM
> > > To: 'BlueOnyx General Mailing List'
> > > Subject: [BlueOnyx:12558] Re: Kernel Question
> > >
> > > > Can you document the fix so we can choose to do it?
> > >
> > > I did this myself in the end. Rebooted and it works so I think I 
> have it
> > right.
> > >
> > > First copy /etc/grub.conf to /boot/grub/grub.conf:
> > >
> > >    rm /boot/grub/grub.conf
> > >    cp /etc/grub.conf /boot/grub/grub.conf
> > >    chmod 644 /boot/grub/grub.conf
> > >
> > > Then create a Symlink where /etc/grub.conf points to 
> /boot/grub/grub.conf
> > >
> > >    rm /etc/grub.conf
> > >    ln -s /boot/grub/grub.conf /etc/grub.conf
> > >
> > > Jason
> > >




What about a lower case      -v



Ken Marcus




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20140421/73bcd6da/attachment.html>