 |
 |
 |
 |
| Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum. |

12th September 2008, 11:00 AM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
kernel-2.6.26.3-29.fc9.i686 upgrade did not modify my grub.conf
I got the update notification to update to the latest kernel-2.6.26.3-29.fc9.i686.
After doing the upgrade, I noticed that /boot has all the new kernel files but my grub.conf was not modified.
I need to understand why the kernel upgrade is not modifying grub.conf
Thanks.
--Daniel
|

12th September 2008, 11:12 AM
|
 |
Registered User
|
|
Join Date: Sep 2007
Location: Cambodia
Posts: 108

|
|
Did you checked /boot/grub/menu.lst?
That's where it's happening actually, not in grub.conf
do as root less /boot/grub/menu.lst to check your available kernels.
Is the new kernel available upon boot?
Look here for some introductory info:
http://forums.fedoraforum.org/showthread.php?t=198953
http://www.redhat.com/docs/manuals/l...e/ch-grub.html
Cheers
__________________
Hamlet - O, from this time forth, my thoughts be bloody, or be nothing worth !
Shakespeare "Halmet" Act IV, Scene 4 Registered Linux user number 418565
Last edited by Peacepunk; 12th September 2008 at 11:21 AM.
|

12th September 2008, 11:32 AM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
I did the "less /boot/grub/menu.lst" and the new kernel is not available on reboot.
Both grub.conf and menu.lst have not not been touched since 2008-08-08
|

12th September 2008, 11:48 AM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
Ok, I took yumex, made sure to uninstall the new kernel-2.6.26.3-29.fc9.i686
and then selected to update the kernel.
Here is the output -- seems the kernel update died towards the end even though
it claims to have successfully installed. Sure, /boot shows the new kernel files
but grub.conf did not get updated.
Here is my /boot/grub/menu.lst:# 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,4)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda5
default=0
timeout=5
howmany=all
splashimage=(hd0,4)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.25.14-108.fc9.i686)
root (hd0,4)
kernel /vmlinuz-2.6.25.14-108.fc9.i686 ro root=UUID=4452d6c5-6d2a-4742-8324-4af887d41199
initrd /initrd-2.6.25.14-108.fc9.i686.img
title Other
rootnoverify (hd0,1)
chainloader +1
-----
06:41:52 : Downloading Packages:
06:42:37 : Checking GPG Signatures:
06:42:37 : Running Transaction Test
06:42:41 : Finished Transaction Test
06:42:41 : Transaction Test Succeeded
06:42:41 : --> Populating transaction set with selected packages. Please wait.
06:42:42 : ---> Package kernel-devel.i686 0:2.6.26.3-29.fc9 set to be installed
06:42:42 : ---> Package kernel.i686 0:2.6.26.3-29.fc9 set to be installed
06:42:42 : Running Transaction
*** glibc detected *** /sbin/nash: malloc(): memory corruption: 0x0906b250 ***
======= Backtrace: =========
/lib/libc.so.6[0xa25596]
/lib/libc.so.6(__libc_malloc+0x95)[0xa26ce5]
/lib/libc.so.6(__strdup+0x30)[0xa2a480]
/usr/lib/libnash.so.6.0.52[0x7c6159]
/usr/lib/libbdevid.so.6.0.52[0x795253]
/lib/libglib-2.0.so.0(g_ptr_array_foreach+0x45)[0xbbc2f5]
/usr/lib/libbdevid.so.6.0.52[0x79534d]
....
00-b7e00000 ---p b7d21000 00:00 0
b7eeb000-b7ef1000 rw-p b7eeb000 00:00 0
bf7fc000-bf811000 rw-p bffeb000 00:00 0 [stack]
/sbin/new-kernel-pkg: line 104: 8440 Aborted $grubby --add-kernel=$bootPrefix/$kernelName-$version $INITRD --copy-default $makedefault --title"$title" ${mbkernel:+--add-multiboot="$mbkernel"} ${mbargs:+--mbargs="$mbargs"}--args="root=$rootdevice $kernargs" --remove-kernel="TITLE=$title"
06:44:07 : Installed:
06:44:07 : --> kernel-2.6.26.3-29.fc9.i686
06:44:07 : --> kernel-devel-2.6.26.3-29.fc9.i686
[root@gateway grub]#
|

12th September 2008, 11:53 AM
|
 |
Administrator
|
|
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289

|
|
Well, there it is:
Code:
/sbin/new-kernel-pkg: line 104: 8440 Aborted $grubby --add-kernel=$bootPrefix/$kernelName-$version $INITRD --copy-default $makedefault --title"$title" ${mbkernel:+--add-multiboot="$mbkernel"} ${mbargs:+--mbargs="$mbargs"}--args="root=$rootdevice $kernargs" --remove-kernel="TITLE=$title"
Looks like maybe the %postinstall script failed? No idea why though.
V
|

12th September 2008, 12:32 PM
|
 |
Registered User
|
|
Join Date: Sep 2007
Location: Cambodia
Posts: 108

|
|
|
Life Sucks.
Could you try with just yum update (as root)?
__________________
Hamlet - O, from this time forth, my thoughts be bloody, or be nothing worth !
Shakespeare "Halmet" Act IV, Scene 4 Registered Linux user number 418565
|

12th September 2008, 01:04 PM
|
|
Registered User
|
|
Join Date: Nov 2005
Location: Iceland
Age: 30
Posts: 2

|
|
|
Had this same behaviour with kernel 2.6.26.5-32.fc9.i686 upgrade yesterday.
The install went without error. But I rebooted into old kernel so
I checked grub.conf and no entry for the new install, checked /boot and it was missing the initrd-x.img file.
I yum removed the new kernel and installed it again, all is well now, initrd-x file and grub entry all set.
"some thing just can't be explained"
|

12th September 2008, 01:45 PM
|
|
Registered User
|
|
Join Date: Jan 2007
Posts: 194

|
|
|
Strange, I don't get any kernel update recently after new key.
|

12th September 2008, 11:29 PM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
Hi PeacePunk and Link,
Thanks for taking the time to give me some help. Unfortunately none of the suggestions brought
the desired result of grub.conf getting updated to allow the new kernel to boot.
Any real Fedora experts out there to help?
287 yum remove kernel-2.6.26.3-29.fc9.i686
288 yum update
yum update results in the same error - the post install is still failing....
Running Transaction
Installing : kernel [1/1]
*** glibc detected *** /sbin/nash: malloc(): memory corruption: 0x09101250 ***
======= Backtrace: =========
/lib/libc.so.6[0xa25596]
/lib/libc.so.6(__libc_malloc+0x95)[0xa26ce5]
/lib/libc.so.6(__strdup+0x30)[0xa2a480]
.
.
.
/sbin/new-kernel-pkg: line 104: 11984 Aborted $grubby --add-kernel=$bootPrefix/$kernelName-$version $INITRD --copy-default $makedefault --title "$title" ${mbkernel:+--add-multiboot="$mbkernel"} ${mbargs:+--mbargs="$mbargs"} --args="root=$rootdevice $kernargs" --remove-kernel="TITLE=$title"
Installed: kernel.i686 0:2.6.26.3-29.fc9
Complete!
|

12th September 2008, 11:31 PM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
Hi Link,
In my case here is a listing of /boot - the init-* was created fine. The update of the grub.conf is
what is failing.
-rw-r--r-- 1 root root 86472 2008-08-04 14:16 config-2.6.25.14-108.fc9.i686
-rw-r--r-- 1 root root 88852 2008-09-03 03:50 config-2.6.26.3-29.fc9.i686
drwxr-xr-x 3 root root 1024 2008-08-07 23:16 efi
drwxr-xr-x 2 root root 1024 2008-09-12 18:19 grub
-rw------- 1 root root 3313634 2008-08-14 18:57 initrd-2.6.25.14-108.fc9.i686.img
-rw------- 1 root root 2560876 2008-09-12 18:23 initrd-2.6.26.3-29.fc9.i686.img
drwx------ 2 root root 12288 2008-08-07 23:00 lost+found
-rw-r--r-- 1 root root 889202 2008-08-04 14:16 System.map-2.6.25.14-108.fc9.i686
-rw-r--r-- 1 root root 916077 2008-09-03 03:50 System.map-2.6.26.3-29.fc9.i686
-rwxr-xr-x 1 root root 2075392 2008-08-04 14:16 vmlinuz-2.6.25.14-108.fc9.i686
-rwxr-xr-x 1 root root 2125184 2008-09-03 03:50 vmlinuz-2.6.26.3-29.fc9.i686
|

12th September 2008, 11:38 PM
|
 |
Administrator
|
|
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289

|
|
|
What's the size of your /boot partition? Are the HDDs and/or partitions nearing full capacity? How about RAM? Run memtest86+? Also try:
su -
yum install yum-utils
package-cleanup --problems
V
|

12th September 2008, 11:45 PM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
Here is disk space utilization below. None of the HDs are nearing full capacity. I have 2G of RAM.
Running Transaction
Installing : kernel-headers [1/2]
Installing : glibc-headers [2/2]
Installed: glibc-headers.i386 0:2.8-8
Dependency Installed: kernel-headers.i386 0:2.6.26.3-29.fc9
Complete!
[root@gateway grub]# package-cleanup --problems
Setting up yum
Reading local RPM database
Processing all local requires
No problems found
[root@gateway grub]# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
83956256 18369124 61322380 24% /
/dev/sda5 202219 18270 173509 10% /boot
tmpfs 971832 820 971012 1% /dev/shm
/dev/sdc1 488264736 191036096 297228640 40% /media/My Book
|

12th September 2008, 11:52 PM
|
 |
Administrator
|
|
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289

|
|
|
That looks odd: why are glibc-headers being updated after the new kernel was installed? Or is that part of the same transaction?
Try the kernel update again now that glibc-headers and kernel-headers are updated.... ?
V
|

13th September 2008, 02:10 AM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
Unfortunately, the yum update failed again. I am equally stumped.
Here is the history:
301 yum install yum-utils
302 package-cleanup --problems
303 yum install glibc-headers
304 package-cleanup --problems
305 yum install glibc-headers remove
306 history | grep remove
307 yum remove kernel-2.6.26.3-29.fc9.i686
308 ll /boot
309 yum update
|

14th September 2008, 03:24 PM
|
|
Registered User
|
|
Join Date: Apr 2006
Posts: 15

|
|
|
The yum update successfully downloads the kernel and dies during installation with the following
error:
Downloading Packages:
kernel-2.6.26.3-29.fc9.i686.rpm | 18 MB 00:12
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : kernel [1/1]
*** glibc detected *** /sbin/nash: malloc(): memory corruption: 0x08d60a40 ***
======= Backtrace: =========
/lib/libc.so.6[0xa25596]
/lib/libc.so.6(__libc_malloc+0x95)[0xa26ce5]
/lib/libc.so.6(__strdup+0x30)[0xa2a480]
/usr/lib/libnash.so.6.0.52[0x7c6159]
/usr/lib/libbdevid.so.6.0.52[0x795253]
.
.
.
00de9000-00df2000 rw-p 00de9000 00:00 0
08048000-08051000 r-xp 00000000 fd:00 106721 /sbin/grubby
08051000-08052000 rw-p 00009000 fd:00 106721 /sbin/grubby
09d94000-09db5000 rw-p 09d94000 00:00 0 [heap]
b7e00000-b7e21000 rw-p b7e00000 00:00 0
b7e21000-b7f00000 ---p b7e21000 00:00 0
b7fb6000-b7fbc000 rw-p b7fb6000 00:00 0
bfac6000-bfadb000 rw-p bffeb000 00:00 0 [stack]
/sbin/new-kernel-pkg: line 104: 14862 Aborted $grubby --add-kernel=$bootPrefix/$kernelName-$version $INITRD --copy-default $makedefault --title"$title" ${mbkernel:+--add-multiboot="$mbkernel"} ${mbargs:+--mbargs="$mbargs"}--args="root=$rootdevice $kernargs" --remove-kernel="TITLE=$title"
Installed: kernel.i686 0:2.6.26.3-29.fc9
Complete!
----
memtest did not find any RAM errors. The code reports installation complete but grub.conf
was not modified so the new kernel cannot boot.
Something is broken with regard to the Fedora kernel update. I have tested this on two other
Fedora 9 systems and the upgrade worked fine. The difference in the grub.conf is shown
below:
FAILED UPGRADE (machine under investigation):
kernel /vmlinuz-2.6.25.14-108.fc9.i686 ro root=UUID=4452d6c5-6d2a-4742-8324-4af887d41199
SUCCESSFUL UPGRADE (different machine):
kernel /vmlinuz-2.6.26.3-29.fc9.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 13:36 (Friday, 24-05-2013)
|
|
 |
 |
 |
 |
|
|