Results 1 to 9 of 9
  1. #1
    Join Date
    Jun 2004
    Posts
    282

    yum install kernel grubby error

    tried to upgrade kernel to lataest


    [email protected] [~]# yum install kernel
    Gathering header information file(s) from server(s)
    Server: CentOS-3 - Addons
    Server: CentOS-3 - Base
    Server: CentOS-3 - Extras
    Server: CentOS-3 - Updates
    Finding updated packages
    Downloading needed headers
    Resolving dependencies
    Dependencies resolved
    I will do the following:
    [install: kernel 2.4.21-27.0.4.EL.i686]
    Is this ok [y/N]: y
    Downloading Packages
    Running test transaction:
    Test transaction complete, Success!
    kernel 100 % done 1/1
    stdin: is not a tty
    stdin: is not a tty
    stdin: is not a tty
    grubby fatal error: unable to find a suitable template
    Kernel Updated/Installed, checking for bootloader
    Lilo found - adding kernel to lilo and making it the default
    Installed: kernel 2.4.21-27.0.4.EL.i686
    Transaction(s) Complete
    here is /etc/lilo.conf


    prompt
    timeout=50
    default=linux
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear

    image=/boot/vmlinuz-2.4.21-27.0.4.EL
    label=2.4.21-27.0.4.E
    initrd=/boot/initrd-2.4.21-27.0.4.EL.img
    read-only
    root=/dev/hda2

    image=/boot/vmlinuz-2.4.21-27.0.1.ELsmp
    label=linux
    initrd=/boot/initrd-2.4.21-27.0.1.ELsmp.img
    read-only
    root=/dev/hda2

    image=/boot/vmlinuz-2.4.21-27.0.1.EL
    label=linux-up.bak
    initrd=/boot/initrd-2.4.21-27.0.1.EL.img
    read-only
    root=/dev/hda2

    image=/boot/vmlinuz-2.4.21-27.0.4.EL
    label=linux-up
    root=/dev/hda2
    read-only
    initrd=/boot/initrd-2.4.21-27.0.4.EL.img


    why did i got :
    grubby fatal error: unable to find a suitable template

    and why kernel 2.4.21-27.0.4.EL.img was not set to default

  2. #2
    Join Date
    May 2005
    Location
    Scranton, PA
    Posts
    18
    This was a Red Hat bug that I believe should've been fixed by now, but there is a patch available for grubby. Since I can't link to other sites due to lack of posts, the url is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83512, sorry for not being able to url it, but the Text of the patch is as follows:

    Comment #7 From Bob Nelson on 2003-06-03 23:12 EST [reply]

    Here's a patch to correct the problem as referenced by David Winter on
    2003-03-03 00:24. The problem is readily replicated by using a LABEL for the
    root device instead of an explicit "root=/dev/..." key/value pair in lilo.conf.



    *** grubby.c-old 2003-06-03 22:05:17.000000000 -0500
    --- grubby.c 2003-06-03 22:10:09.000000000 -0500
    ***************
    *** 659,665 ****
    --- 659,671 ----
    line = entry->lines;
    while (line && line->type != LT_ROOT) line = line->next;

    + + #ifdef WANT_GRUBBY_FAILURE_BEFORE_TRYING_LT_KERNELARGS
    + /*
    + * 3 JUN 2003: [[email protected]] - ifdef corrects premature
    + * return before evaluation and possible ``else'' decision.
    + */
    if (!line) return 0;
    + + #endif

    if (line && line->numElements >= 2)
    dev = line->elements[1].item;

    Hope this helps!
    BurstNET® - The Speed the Internet Travels™
    BurstNET® - an INC500™ Company
    BurstNET - 1-877-BURSTNET - [email protected]
    http://www.burst.net-http://www.nocster.net

  3. #3
    Join Date
    Jun 2004
    Posts
    282
    wich part of lilo.conf exactly i should change

  4. #4
    Join Date
    May 2005
    Location
    Scranton, PA
    Posts
    18
    Actually, you should ignore my last messages, which, if I'd read further, I would've seen the message stating that bug had been fixed by a newer version of mkinitrd. Also, I should've read your message. It appears you are booting into the kernel, although it is not the default. What is booting as the default kernel?
    BurstNET® - The Speed the Internet Travels™
    BurstNET® - an INC500™ Company
    BurstNET - 1-877-BURSTNET - [email protected]
    http://www.burst.net-http://www.nocster.net

  5. #5
    Join Date
    Jun 2004
    Posts
    282
    [email protected] [~]# uname -r
    2.4.21-27.0.1.ELsmp

    server Specifications:

    Intel Celeron 2.4GHz
    512MB DDRAM Memory
    80GB EIDE Hard Drive
    1,000GB Data Transfer

    centos3.4 with WHM 10.1.0 cPanel 10.2.0-S83

  6. #6
    Join Date
    May 2005
    Location
    Scranton, PA
    Posts
    18
    ok, it's not booting because right here:
    prompt
    timeout=50
    default=linux
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear
    the default is "linux", which is
    image=/boot/vmlinuz-2.4.21-27.0.1.ELsmp
    label=linux
    initrd=/boot/initrd-2.4.21-27.0.1.ELsmp.img
    read-only
    root=/dev/hda2
    the label for the older kernel. The new kernel is:
    image=/boot/vmlinuz-2.4.21-27.0.4.EL
    label=2.4.21-27.0.4.E
    initrd=/boot/initrd-2.4.21-27.0.4.EL.img
    read-only
    root=/dev/hda2
    If the default= line was correct, it would boot into the correct kernel. The correct line would be default=2.4.21-27.0.4.E
    BurstNET® - The Speed the Internet Travels™
    BurstNET® - an INC500™ Company
    BurstNET - 1-877-BURSTNET - [email protected]
    http://www.burst.net-http://www.nocster.net

  7. #7
    Join Date
    Jun 2004
    Posts
    282
    i tried to make default=2.4.21-27.0.4.E then reboot

    but still

    [email protected] [~]# uname -r
    2.4.21-27.0.1.ELsmp


    if my system kernel is smp why did ( yum kernel install ) brought for me a non smp kernel?

    would that be the cuz of the problem?

  8. #8
    Join Date
    Apr 2001
    Posts
    2,588
    run lilo -v -v after making the changes to your lilo.conf

  9. #9
    Join Date
    Jun 2004
    Posts
    282
    Originally posted by Haze
    run lilo -v -v after making the changes to your lilo.conf
    i did run lilo -v -v but still get

    [email protected] [~]# uname -r
    2.4.21-27.0.1.ELsmp



    any way i installed kernel-2.4.21-27.0.4.ELsmp manually and every thing is ok now

    [email protected] [~]# uname -r
    2.4.21-27.0.4.ELsmp


    but why i still get grubby fatal error and why ( yum kernel install ) brought for me a non smp kernel?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •