CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't know why the older kernel is loading and I find that odd becuase the output clearly shows you installed a new one.
At one point I had 5 kernels in my Grub Menu so I change the limit to =2 by editing the
/etc/yum.conf file.
If you set it to one I don't know which kernel Grub will list first.
When your system boots you should be able to choose which kernel you want to boot with your arrow keys-
I don't know why the older kernel is loading and I find that odd becuase the output clearly shows you installed a new one.
At one point I had 5 kernels in my Grub Menu so I change the limit to =2 by editing the
/etc/yum.conf file.
If you set it to one I don't know which kernel Grub will list first.
When your system boots you should be able to choose which kernel you want to boot with your arrow keys-
Hi, it's a remote server, at this moment I have no way to use KVM or so.
Very strange. I manage several CentOS machines, it's the first time I have this kind of issue.
It could be that another distro has "control" of the bootloader (ie the last system to `grub-install` will determine which distro's grub.cfg is parsed).
If you post the content of /boot/grub/grub.cfg (rather than grub.conf) we could be sure.
I don't use CentOS, however -- did you run `update-grub` (or `grub-mkconfig -o /boot/grub/grub.cfg`)?
From grub.conf:
Quote:
If you change this file, run 'update-grub' afterwards to update /boot/grub/grub.cfg.
few days ago I installed new kernel with yum (official CentOS repo):
A question?
What was the exact command you used?
the normal command would not do that
Code:
su -
yum update
or
did you try REPLACING the default kernel with a different one ?
if you did that
you would need to also replace the headers and the source
then rebuild the bootimage ( cent6 uses "dracut" )
It could be that another distro has "control" of the bootloader (ie the last system to `grub-install` will determine which distro's grub.cfg is parsed).
Hi, it's a server, no multi-boot.
Quote:
Originally Posted by Head_on_a_Stick
If you post the content of /boot/grub/grub.cfg (rather than grub.conf) we could be sure.
I went to housing provider (luckily it is in the city where I live and rebooted the machine.
At grub prompt, I have JUST ONLY entry (2.6.32-71.el6.x86_64).
This is my complete 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/mapper/vg_tokyo-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/ddf1_4c53492020202020808627c3000000004711471100000a28
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title CentOS (2.6.32-504.1.3.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-504.1.3.el6.x86_64 ro root=/dev/mapper/vg_tokyo-lv_root rd_DM_UUID=ddf1_4c53492020202020808627c3000000004711471100000a28 rd_LVM_LV=vg_tokyo/lv_root rd_LVM_LV=vg_tokyo/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=it crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-504.1.3.el6.x86_64.img
title CentOS (2.6.32-504.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-504.el6.x86_64 ro root=/dev/mapper/vg_tokyo-lv_root rd_DM_UUID=ddf1_4c53492020202020808627c3000000004711471100000a28 rd_LVM_LV=vg_tokyo/lv_root rd_LVM_LV=vg_tokyo/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=it crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-504.el6.x86_64.img
title CentOS (2.6.32-431.29.2.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-431.29.2.el6.x86_64 ro root=/dev/mapper/vg_tokyo-lv_root rd_DM_UUID=ddf1_4c53492020202020808627c3000000004711471100000a28 rd_LVM_LV=vg_tokyo/lv_root rd_LVM_LV=vg_tokyo/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=it crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-431.29.2.el6.x86_64.img
title CentOS (2.6.32-431.23.3.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-431.23.3.el6.x86_64 ro root=/dev/mapper/vg_tokyo-lv_root rd_DM_UUID=ddf1_4c53492020202020808627c3000000004711471100000a28 rd_LVM_LV=vg_tokyo/lv_root rd_LVM_LV=vg_tokyo/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=it crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-431.23.3.el6.x86_64.img
title CentOS (2.6.32-71.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=/dev/mapper/vg_tokyo-lv_root rd_DM_UUID=ddf1_4c53492020202020808627c3000000004711471100000a28 rd_LVM_LV=vg_tokyo/lv_root rd_LVM_LV=vg_tokyo/lv_swap rd_NO_LUKS rd_NO_MD LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=it crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-71.el6.x86_64.img
This is the output of mount command:
Code:
# mount
/dev/mapper/vg_tokyo-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
I suspect that grub configuration is updated every time only on /dev/sda, not on /dev/sdb.
This server has "hardware" sata raid.
What do you think?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.