Results 1 to 18 of 18
  1. #1
    Join Date
    Mar 2006
    Posts
    36

    can't upgrade kernel on a centos box, please help

    hi guys, i have a centos 5.4 machine with 2.6.18-164.11.1.el5PAE kernel on it.
    i have run yum update, kernel was updated to 2.6.18-164.15.1.el5PAE

    i double checked /etc/grub.conf so it shows default=0

    rebooted the machine but when i run "uname -r" it still shows the old kernel: 2.6.18-164.11.1.el5PAE


    here's the output of "cat /etc/grub.conf"
    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/md0
    #          initrd /initrd-version.img
    #boot=/dev/md1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-164.15.1.el5PAE)
           root (hd0,0)
           kernel /vmlinuz-2.6.18-164.15.1.el5PAE ro root=/dev/md0
           initrd /initrd-2.6.18-164.15.1.el5PAE.img
    title CentOS (2.6.18-164.11.1.el5PAE)
           root (hd0,0)
           kernel /vmlinuz-2.6.18-164.11.1.el5PAE ro root=/dev/md0
           initrd /initrd-2.6.18-164.11.1.el5PAE.img
    title CentOS (2.6.18-164.el5PAE)
           root (hd0,0)
           kernel /vmlinuz-2.6.18-164.el5PAE ro root=/dev/md0
           initrd /initrd-2.6.18-164.el5PAE.img
    can someone please help me ? thanks.

  2. #2
    Join Date
    Nov 2003
    Location
    Kherson, Ukraine
    Posts
    267
    In centos by default /etc/grub.conf is symlink to /boot/grub/grub.conf
    Is it so?
    What is in your /boot/grub/grub.conf?
    Private remote administrator of Linux servers - www.petrov.ks.ua
    Quality hosting - Host-Web-Site.com

  3. #3
    Join Date
    Mar 2006
    Posts
    36
    yes, it is symlinked, it has the same content:

    Code:
    root@milo [~]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/md0
    #          initrd /initrd-version.img
    #boot=/dev/md1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-164.15.1.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.15.1.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.15.1.el5PAE.img
    title CentOS (2.6.18-164.11.1.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.11.1.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.11.1.el5PAE.img
    title CentOS (2.6.18-164.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.el5PAE.img

  4. #4
    Join Date
    Mar 2004
    Location
    Odessa, Ukraine
    Posts
    610
    You have real server or virtual?

  5. #5
    Join Date
    Nov 2004
    Location
    India
    Posts
    1,104
    What is the result of,

    rpm -q kernel

    it should show both the kernels if not the installation was not successful.
    AssistanZ - Beyond Boundaries...
    Cloudstack Consultancy / 24x7 Web Hosting Support / 24x7 Server Management / Infrastructure Management Services
    Web & Mobile Apps Development / Web Designing Services / Php, Grails, Java Development

  6. #6
    Join Date
    Mar 2006
    Posts
    36
    it was showing nothing, then i ran yum install kernel
    then rebooted and now it shows:

    root@milo [~]# uname -r
    2.6.18-164.11.1.el5PAE
    root@milo [~]# rpm -q kernel
    kernel-2.6.18-164.15.1.el5
    root@milo [~]# rpm -q kernel-PAE
    kernel-PAE-2.6.18-164.el5
    kernel-PAE-2.6.18-164.11.1.el5
    kernel-PAE-2.6.18-164.15.1.el5
    root@milo [~]# rpm -q kernel-headers
    kernel-headers-2.6.18-164.15.1.el5

    and grub.conf looks like:
    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/md0
    #          initrd /initrd-version.img
    #boot=/dev/md1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-164.15.1.el5)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.15.1.el5 ro root=/dev/md0
            initrd /initrd-2.6.18-164.15.1.el5.img
    title CentOS (2.6.18-164.15.1.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.15.1.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.15.1.el5PAE.img
    title CentOS (2.6.18-164.11.1.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.11.1.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.11.1.el5PAE.img
    title CentOS (2.6.18-164.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.el5PAE.img

  7. #7
    Join Date
    Nov 2004
    Location
    India
    Posts
    1,104
    It appears to be a kernel panic in the newly installed kernel, after the 5 seconds timeout it boots the old kernel again. The 5 seconds timeout has been set in your grub.conf,

    timeout=5

    Maybe you can try removing the following lines from grub.conf after backing up the grub.conf,

    title CentOS (2.6.18-164.11.1.el5PAE)
    root (hd0,0)
    kernel /vmlinuz-2.6.18-164.11.1.el5PAE ro root=/dev/md0
    initrd /initrd-2.6.18-164.11.1.el5PAE.img

    Please note this is at your own risk. If it fails to boot then you may need to contact the DC.
    AssistanZ - Beyond Boundaries...
    Cloudstack Consultancy / 24x7 Web Hosting Support / 24x7 Server Management / Infrastructure Management Services
    Web & Mobile Apps Development / Web Designing Services / Php, Grails, Java Development

  8. #8
    Join Date
    Apr 2003
    Location
    San Jose, CA.
    Posts
    1,624
    You're doing this on a metadevice...

    So you might want to redo the bootloader manually to make sure the right stuff got written to both? drives.

    grub
    root (hd0,0)
    setup (hd0)
    root (hd1,0)
    setup (hd1)
    quit

    reboot

    Afaik timeout has nothing to do with it's failback support. It just declares how much time to wait a the bootloader in case you want to make changes.
    Last edited by Lightwave; 03-20-2010 at 09:43 AM.
    Daved @ Lightwave Networking, LLC.
    AS1426 https:/www.lightwave.net
    Primary Bandwidth: EGIHosting (NLayer, NTT, HE, Cogent)
    Xen PV VPS Hosting

  9. #9
    Join Date
    Mar 2006
    Posts
    36
    i don't know what's wrong, grub.conf now looks like this:
    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/md0
    #          initrd /initrd-version.img
    #boot=/dev/md1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-164.15.1.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.15.1.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.15.1.el5PAE.img
    title CentOS (2.6.18-164.el5PAE)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-164.el5PAE ro root=/dev/md0
            initrd /initrd-2.6.18-164.el5PAE.img
    but after the reboot, "uname -r" shows an old kernel which is not even mentioned in the grub.conf:
    uname -r
    2.6.18-164.11.1.el5PAE

    any other ideeas?

  10. #10
    Join Date
    Mar 2006
    Posts
    36
    @Lightwave: that didn't work either, after the reboot i have the same 2.6.18-164.11.1.el5PAE kernel

  11. #11
    Join Date
    Mar 2006
    Posts
    36
    anybody knows what should i do?
    thanks.
    Last edited by minadreapta; 03-22-2010 at 05:43 AM.

  12. #12
    Can you get console access to the server?
    http://erectvps.com - We care about our customers | OpenVZ US | Level 3 support | Give us try
    Twitter: http://twitter.com/erectvps
    *New This Week: New SolusVM master VPS*

  13. #13
    Join Date
    Mar 2009
    Location
    InfoPark, Cochin, India
    Posts
    986
    What does the command dmesg show? Reboot the server, login as root and execute the command dmesg .

  14. #14
    Join Date
    Mar 2006
    Posts
    36
    @erectvps: the server is online, it's working fine. i have full root acces to the server. the problem is that the new kernel is not on place.
    I can get console acces if i want to, but why, i have SSH access already?


    @VIPoint: i ran "dmesg |grep 'kernel'", i can't reboot the server now, there are about 50 live accounts on it in this moment.

    Code:
    root@milo [/boot]# dmesg |grep 'kernel'
    Memory for crash kernel (0x0 to 0x0) notwithin permissible range
    Memory: 8237156k/10223616k available (2158k kernel code, 87604k reserved, 892k data, 228k init, 7408532k highmem)
    Freeing unused kernel memory: 228k freed
    Write protecting the kernel read-only data: 404k
    backupdriver: module license 'Proprietary' taints kernel.

    the backupdriver thing is from the r1soft CDP agent i think

  15. #15
    Join Date
    Mar 2006
    Posts
    36
    any other ideeas?

  16. #16
    Join Date
    Mar 2006
    Posts
    36
    here is something from dmesg, i took out all the initialization texts...
    Code:
    ------------initialization (cpu, mem, acpi, etc)---------------
    device-mapper: uevent: version 1.0.3
    device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com
    device-mapper: dm-raid45: initialized v0.2594l
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: considering sdb3 ...
    md:  adding sdb3 ...
    md: sdb1 has different UUID to sdb3
    md:  adding sda3 ...
    md: sda1 has different UUID to sdb3
    md: created md0
    md: bind<sda3>
    md: bind<sdb3>
    md: running: <sdb3><sda3>
    md: kicking non-fresh sda3 from array!
    md: unbind<sda3>
    md: export_rdev(sda3)
    raid1: raid set md0 active with 1 out of 2 mirrors
    md: considering sdb1 ...
    md:  adding sdb1 ...
    md:  adding sda1 ...
    md: created md1
    md: bind<sda1>
    md: bind<sdb1>
    md: running: <sdb1><sda1>
    md: kicking non-fresh sda1 from array!
    md: unbind<sda1>
    md: export_rdev(sda1)
    raid1: raid set md1 active with 1 out of 2 mirrors
    md: ... autorun DONE.
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    -------------------ACPI bla bla's---------------------
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: considering sda1 ...
    md:  adding sda1 ...
    md: sda3 has different UUID to sda1
    md: md1 already running, cannot run sda1
    md: export_rdev(sda1)
    md: considering sda3 ...
    md:  adding sda3 ...
    md: md0 already running, cannot run sda3
    md: export_rdev(sda3)
    md: ... autorun DONE.
    device-mapper: multipath: version 1.0.5 loaded
    loop: loaded (max 8 devices)
    EXT3 FS on md0, internal journal
    kjournald starting.  Commit interval 5 seconds
    EXT3 FS on md1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    Adding 3068404k swap on /dev/sdb2.  Priority:-1 extents:1 across:3068404k
    Adding 3068404k swap on /dev/sda2.  Priority:-2 extents:1 across:3068404k
    kjournald starting.  Commit interval 5 seconds
    EXT3 FS on loop0, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    igb: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
    ip_tables: (C) 2000-2006 Netfilter Core Team
    Netfilter messages via NETLINK v0.30.
    ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
    backupdriver: module license 'Proprietary' taints kernel.
    budInit: backupdriver version 3.1.0 build 8761 loaded

  17. #17
    Join Date
    Mar 2006
    Posts
    36
    nobody can help me with this one?

    thanks.

  18. #18
    Join Date
    Apr 2003
    Location
    San Jose, CA.
    Posts
    1,624
    You should consider fixing your RAID 1 mirrors first.

Similar Threads

  1. [How To] Kernel Upgrade via Yum for CentOs boxes
    By layer0 in forum Hosting Security and Technology Tutorials
    Replies: 54
    Last Post: 08-23-2012, 04:14 AM
  2. Centos + kernel 2.6.9-34.0.2 issues - how to upgrade kernel?
    By vbnz88 in forum Hosting Security and Technology
    Replies: 5
    Last Post: 04-30-2007, 02:32 PM
  3. is that really? can't upgrade kernel in centos
    By Slackerman in forum Hosting Security and Technology
    Replies: 13
    Last Post: 10-02-2006, 06:45 AM
  4. CentOS 3.3 : Do I have to upgrade kernel past 2.4.21-EL3
    By EuroVPS/Director in forum Hosting Security and Technology
    Replies: 14
    Last Post: 03-31-2005, 08:05 PM
  5. the way to upgrade rackshack's dual box kernel?
    By Bashar in forum Hosting Security and Technology
    Replies: 13
    Last Post: 01-08-2004, 11:07 AM

Posting Permissions

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