CentOS 5 :: How To Prevent Kernel Upgrade On Reboot After Yum Update Kernel*
May 29, 2010
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
I need to prevent that the latest kernel update removes the only kernel that still works in my computer. how can i do this? Currently I have 3 linux kernels versions:
But only the oldest works. With the new update there is a new kernel version (2.6.32-24) that possibly will not boot (like previous 2.6.32-* kernels) and also I expect that, as in previous updates, the oldest kernel will become inaccessible, thus rendering my ubuntu unbootable.
PS: unsolved threads on the underlaying problem: Can't boot default kernel after upgrading from 9.xx to 10.04 lucid Upgrade to 10.04 freezes on the Ubuntu screen
I've upgraded kernel 2.6.27.48-0.2-default to 2.6.27.54-0.1.1 on openSUSE 11.1. Before I tried to upgrade to 2.6.27.48-0.3-default where I encountered the same issue. After reboot it can not find the modules for 2.6.27.48-0.2-default which puzzled me to no end. Now I have found that the /boot which is on separate partition of ext2 type is not mounted. The mount command does not recognize ext2 and xfs anymore.
Clearly the initrd does not have the right modules. Since this is standard zypper up process I would expect this to work without issues since it has worked until the 2.6.27.48-0.2-default kernel without issues. Has something changed with the last 2 kernel versions that requires some extra actions from me and if so what do I have to do.
Here's what to do right after applying the latest kernel security patch (2.6.34.7-0.4) to get the ATI driver back to work. Do not reboot yet make sure the update installed the headers and sources for kernel 2.6.34.7-0.4: rpm -qa | grep 2.6.34.7-0.4 should print the files in red on a 64bit system:
I updated to the latest available kernel for Kubuntu 10.04 today (2.6.32-24). When the system rebooted, it refused to connect to my wireless network. So far I have been unsuccessful in persuading it to connect. ifconfig shows the existence of the ethernet connection as eth0, and Network Manager also seems to accept the existence of the ethernet port - so why has it suddenly chosen now to stop connecting to the wired network?
I updated wubi kernel(ubuntu 10.04) After restart, i selected ubuntu then my system reboots. Then i select ubuntu then my system reboots. I dont know what to do now,
I have a new acer machine which runs fine on 10.10 mythbuntu desktop livecd. Install seemed fine.
Then I ran an update and on reboot I get a kernel panic error. Research on this reveals it as a very deep subject which can consume many hours, so I opted to reinstall.
This time with ubuntu 10.10. I've tried different CDs, liveusb. Same errors.
So, the question is this - where do I concentrate my efforts - somewhere ubuntu doesn't like this machine, or grub. Does a reinstall overwrite the grub install too? Or do I have a bogus grub install I need to purge before I will get anywhere.
I'm noticing that maybe twice a month the Update Manager is asking me to upgrade my kernel. Currently it's asking me to move to 2.6.32.24.25. Is this the smart thing to do? Are these primarily securtiy updates to the kernel?
Yesterday i was prompted by my update manager to update some packages. I really don't remember which but i updated.
After reboot the box now kernel panics. I don't believe i get a ubuntu splash screen, and at this point i can't figure out how to get to my grub, in case a kernel was upgraded and it's possible to boot to different kernel.
i noticed some words like 'mantis', 'oops' and 'dvb_core' was a part of the text i get on the screen.
Can this be because of a dvb* upgrade that breaks something important ?
If needed, i should be able to boot via liveCD, or i could take a picture of the errors.
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Is there a way to get the matching Linux kernel headers automatic on a regular kernel update via the Ubuntu packed manager? Every time I get a new kernel I must do an aptitude install linux-headers-`uname -r`
A recent kernel update seems to have misplaced the Kernel Headers. VMWare needs these headers and cannot find them. Attempting to run VMWARE gets the message: Kernel headers for version 2.6.31.12-0.2-desktop were not found.
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
At the moment I am using kernel 2.6.31-14-generic. I'm not one of those people who needs to have the latest and greatest kernel to be happy, I just rely on the update manager. I swore that I saw an update for a new kernel, but my kernel version hasn't changed. I'm just curious if there was a new kernel that was released or if that was just an update to the kernel listed above.
vmware virtual machine, the system is centos 5.4 want to upgrade the kernel 2.6.32. make menuconfig is based on the default. make; make modules_install; make install no problem, reboot the system to choose a new kernel, new kernel can not boot, the following is vastly map, right in the / boot directory, there is no 2.6.32 of the config files, do not know how the matter , in the compilation before I put / boot directory of the original system config files to the source directory cp The following is the contents of the screenshot
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2 2 logical groups in VolGroup00 now active mount: error mounting /dev/root on /sysroot as ex3t: No such device setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
i'm currently running centos 5 with kernel version 2.6.18-92.1.22.el5 is there any way to update to kernel version >= 2.6.27 via yum ? if not via yum is it advisable to compile from source?
From F12 to F13. Is there anything I should remove before updating? I have few programs isntalled from source/binary installers in /usr for example. Would it cause problems?
And is there any chance to be able to switch from a 32 bit kernel to 64 bit kernel during the update? The hardware is capable of this.
9.04 this morning updated my kernel to I believe it is 2.6.28.18 and upon the reboot I had no desktop. It booted wanting to go into low graphics.
So I drop to shell and stop the gdm and try to run the latest nvidia run file I have and it hangs saying I have a x server running.
Otherwise I am needing assistance with getting my desktop back! I can boot into an older kernel and if need be I would like to roll back that latest update this morning, but once again I am forgetting the command line for that.
I try to update my kernel to 2.6.18.128.4.1.el5 using # yum update
After # yum update # rpm -qa kernel*|sort gives the following: kernel-2.6.18-128.1.14.el5 kernel-2.6.18-128.1.16.el5.centos.plus kernel-2.6.18-128.4.1.el5.centos.plus kernel-2.6.18-92.1.18.el5 kernel-2.6.18-92.el5 kernel-devel-2.6.18-128.1.14.el5 .....
This my grub.conf: # 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/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=1 timeout=5.....
yum update installed: CentOS (2.6.18-128.4.1.el5.centos.plusxen) and CentOS (2.6.18-128.4.1.el5.centos.plus)
both are not working. I have to run the system using: 2.6.18-128.1.14.el5. Upon trying again #yum update it says that no packages are marked for update. Can I manually install the desired kernel? Do you know a reason why yum update is not automatically installing the proper kernel?
I had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
