Just updated another machine to 5.3, everything fine, but grub.conf wasn't updated to the 128 kernel. It got a new modified date and the kernel is there, but the content wasn't changed. /etc/sysconfig/kernel contains the correct UPDATEDEFAULT=yes No errors in logs or during the update. No problem to boot with this kernel once added. This is the first time I ever see this happen. Any clues? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
On Mon, 2009-04-06 at 18:35 +0200, Kai Schaetzl wrote:> Just updated another machine to 5.3, everything fine, but grub.conf wasn't > updated to the 128 kernel. It got a new modified date and the kernel is > there, but the content wasn't changed. /etc/sysconfig/kernel contains the > correct UPDATEDEFAULT=yes > No errors in logs or during the update. No problem to boot with this > kernel once added. > This is the first time I ever see this happen. > Any clues? > > Kai >This happened to me the other day when that kernel came out. "init" would not reload on the kernel update and yum stalled. I had reboot into the old kernel rpm -e the 128 kernel and yum update kernel again and all was fine. I do have to say this machine was memory limited and swapping on update bad. johnStanley
I just updated kernel manually last evening: that is, directly using rpm and it did update the grub.conf. Well, you can always manually edit the grub.conf file, right? BTW: I managed to install 5.3 on the very first generation MAC PRO (xeon 2.66, XT1900) last weekend with old kernel: I took a detour in order to install it directly from CD iso. The system Hung several times and the DVD rom was NOT recognized. However, after updated to the newest kernel last evening, the DVD ram recognized and it did NOT hang any more: at least for about 6 hours. Cheers! Lincong --- On Tue, 4/7/09, JohnS <jses27 at gmail.com> wrote:> From: JohnS <jses27 at gmail.com> > Subject: Re: [CentOS] kernel update doesn't update grub.conf > To: "CentOS mailing list" <centos at centos.org> > Date: Tuesday, April 7, 2009, 11:17 AM > > On Mon, 2009-04-06 at 18:35 +0200, Kai Schaetzl wrote: > > Just updated another machine to 5.3, everything fine, > but grub.conf wasn't > > updated to the 128 kernel. It got a new modified date > and the kernel is > > there, but the content wasn't changed. > /etc/sysconfig/kernel contains the > > correct UPDATEDEFAULT=yes > > No errors in logs or during the update. No problem to > boot with this > > kernel once added. > > This is the first time I ever see this happen. > > Any clues? > > > > Kai > > > > This happened to me the other day when that kernel came > out. "init" > would not reload on the kernel update and yum stalled. > > I had reboot into the old kernel rpm -e the 128 kernel and > yum update > kernel again and all was fine. I do have to say this > machine was memory > limited and swapping on update bad. > > johnStanley > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >
[I saw this thread in the mailing list archives, but wasn't subscribed at the time, so sorry it's not a proper follow-up.] The symptoms you describe could be a side effect of being previously hit by <http://bugs.centos.org/view.php?id=2914> and <https://bugzilla.redhat.com/show_bug.cgi?id=447841>. Those bug items describe workarounds. After you get mkinitrd upgraded to that in 5.3 the problem should go away, although you may have to manually fix up the results of the bad kernel install. Devin -- You live and learn. Or you don't live long. - Robert Heinlein