[BlueOnyx:14621] Re: Apparent grub problems after last update round

[Larry Smith]

Michael,

  Thanks, tried that but no luck.  Finally got the server back online
by booting 2.6.32-358.23.2.el6.i686 kernel (oldest I have on this box).
Only difference in the previous grub and the new is the addition
of the string "biosdevname=0" to the end of each kernel lineb
but even tried removing that with no luck either.

Every other kernel acts like it is booting but stops activity (disk)
right after you press enter (or b to boot from grub menu).

-- 
Larry Smith
lesmith at ecsis.net

On Wed February 12 2014 18:29, Michael Stauber wrote:
> Hi Larry,
>
> > That one gets to the grub, but regardless
> > of what you select it just sits at a blinking cursor...
> >
> > Suggestions before I start taking it apart ??
>
> Boot off the BlueOnyx CD and select "Rescue" at the boot prompt. When
> prompted, select language and keyboard. When asked to configure the
> network, you can skip that. When asked if you want to mount the disks of
> the installed system, say yes. Once you get the prompt, do ...
>
> chroot /mnt/sysimage
>
> ... to mount the disks as /
>
> Then run this command:
>
> ls -k1 /boot/vmlinuz-*| sed s#/boot/vmlinuz-##|sort -V -r|head -1
>
> It should tell you which kernel is the latest one. Then run this command:
>
> /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install
> --make-default XXX
>
> Replace XXX with the exact info from the previous command. That will
> ready this kernel and will update grub.conf as well.