yum update produces /sbin/grubby error

dedanna1029 · #1 14th July 2010, 09:48 PM

I got this upon installation of the new kernel:

Code:

Installing     : kernel-2.6.33.6-147.fc13.i686                                                                                                      81/245 
grubby recieved SIGSEGV!  Backtrace (6):
/sbin/grubby[0x804f898]
[0xc09400]
/sbin/grubby[0x804a174]
/sbin/grubby[0x804f441]
/lib/libc.so.6(__libc_start_main+0xe6)[0x234cc6]
/sbin/grubby[0x80490a1]

And then, on the Cleanup phase:

Code:

  Cleanup        : kernel-2.6.33.4-95.fc13.i686                                                                                                      242/245
grubby recieved SIGSEGV!  Backtrace (6):
/sbin/grubby[0x804f898]
[0xf0a400]
/sbin/grubby[0x804a174]
/sbin/grubby[0x804f441]
/lib/libc.so.6(__libc_start_main+0xe6)[0x3d4cc6]
/sbin/grubby[0x80490a1]

My question is, am I going to have issues on reboot, and if so, is there anything I can do to prevent them? I'm a bit loose on what, specifically, grubby does other than what yum info tells me:

Code:

# yum info grubby
Loaded plugins: presto, refresh-packagekit
Installed Packages
Name       : grubby
Arch       : i686
Version    : 7.0.13
Release    : 1.fc13
Size       : 77 k
Repo       : installed
From repo  : anaconda-InstallationRepo-201005130056.i386
Summary    : Command line tool for updating bootloader configs
URL        : http://git.fedorahosted.org/git/grubby.git
License    : GPLv2+
Description: grubby  is  a command line tool for updating and displaying information about
           : the configuration files for the grub, lilo, elilo (ia64),  yaboot (powerpc)
           : and zipl (s390) boot loaders. It is primarily designed to be used from scripts
           : which install new kernels and need to find information about the current boot
           : environment.

Thanks a bunch.

***glennzo*** · #2 14th July 2010, 10:42 PM

I would go over /boot/grub/grub.conf with a "fine toothed comb" as it were. In other words, I'd have a good close look at the whole file and see if anything looks amiss before attempting a reboot. I suspect that, if anything, the stanza for the new kernel could be wrong.

dedanna1029 · #3 14th July 2010, 11:14 PM

Thank you for the reply.

Here is what I have in /boot/grub/menu.lst:

Code:

# cat /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,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_dedanna-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sdb
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz

#title Fedora (2.6.33.5-124.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-124.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-124.fc13.i686.PAE.img
title Fedora (2.6.33.5-124.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-124.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-124.fc13.i686.img
#title Fedora (2.6.33.5-112.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-112.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-112.fc13.i686.PAE.img
title Fedora (2.6.33.5-112.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-112.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-112.fc13.i686.img
title Fedora 13 (2.6.33.4-95.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.4-95.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.4-95.fc13.i686.img

#title Fedora 13 PAE (2.6.33.4-95.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.4-95.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.4-95.fc13.i686.PAE.img

The thing is, the PAE kernel never works for me, so I've been installing just the "normal" kernel, and commenting out the PAE kernels. I can't be sure if anything is wrong here. Any help is appreciated.

I'm on a P4 IntelPro chip, 2.4GHz, with 1Gb RAM, and an Nvidia 7300 GT card. I have an Audigy2 card installed, but it's not in use right now. I'm using the onboard sound.

Thanks again!

---------- Post added at 04:14 PM CDT ---------- Previous post was at 04:11 PM CDT ----------

Oh, and here is /boot/grub/grub.conf (pretty much the same as menu.lst):

Code:

# 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/mapper/vg_dedanna-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sdb
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz

#title Fedora (2.6.33.5-124.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-124.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-124.fc13.i686.PAE.img
title Fedora (2.6.33.5-124.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-124.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-124.fc13.i686.img
#title Fedora (2.6.33.5-112.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-112.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-112.fc13.i686.PAE.img
title Fedora (2.6.33.5-112.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.5-112.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.5-112.fc13.i686.img
title Fedora 13 (2.6.33.4-95.fc13.i686)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.4-95.fc13.i686 ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.4-95.fc13.i686.img

#title Fedora 13 PAE (2.6.33.4-95.fc13.i686.PAE)
	root (hd0,0)
	kernel /vmlinuz-2.6.33.4-95.fc13.i686.PAE ro root=/dev/mapper/vg_dedanna-lv_root rd_LVM_LV=vg_dedanna/lv_root rd_LVM_LV=vg_dedanna/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
	initrd /initramfs-2.6.33.4-95.fc13.i686.PAE.img

stoat · #4 15th July 2010, 01:30 AM

Quote:

Originally Posted by dedanna1029

Oh, and here is /boot/grub/grub.conf (pretty much the same as menu.lst)

In Fedora, /boot/grub/menu.lst is a symlink to /boot/grub/grub.conf. So is /etc/grub.conf. So opening any of those opens /boot/grub/grub.conf.

Next, I recommend that you not comment out kernels in grub.conf like that. The kernels are still installed. They still will be updated. And yum will still want to remove the old versions when the limit is reached. It also will want to edit grub.conf to remove the entries of the removed kernels. But you've commented them out. I don't know what that will do to all of that.

If you don't want a particular kernel, then reboot into another kernel and remove the unwanted kernel with rpm -e or yum remove. That will remove the kernel, remove its modules, and edit the grub.conf. Probably a cleaner way to deal with an unwanted kernel.

simpfeld · #5 20th July 2010, 06:59 PM

This looks like the error I'm seeing (and others) when a system has been upgraded from F12 to F13. I have one system I have that didn't display this behaviour and one that does. It's possibly because the one displaying this problem isn't a simple disk device, it's an md device (or an LVM from other people seeing this).

No one has suggested a solution yet or how it might be debugged.

Bugzilla for this is here:

https://bugzilla.redhat.com/show_bug.cgi?id=596829

dedanna1029 · #6 20th July 2010, 10:49 PM

I didn't upgrade though. I fresh clean-installed.

And, I just had to do it again because of this.

When I got that kernel upgrade, it had uninstalled all of the other kernels that I had installed that worked for me at the time, so I couldn't get back in no matter what I did.

When I went for the reboot after going back over yet again, grub.conf with a fine-tooth comb, it stuck at the point of Starting atd(?) I think it was. It would just freeze right there, no error messages or anything.

I just wish it would stop installing the PAE kernels on me by default, even in upgrades. If I have a regular kernel installed, I would think that's what it would upgrade, rather than install the next-up PAE kernel. I've been going round and round with the kernels on this thing ever since I initially installed F13 when it came out.

Next kernel upgrade I don't think I'll trust so readily.

---------- Post added at 03:49 PM CDT ---------- Previous post was at 03:44 PM CDT ----------

One more addition, then I'm done. Look at how updates went that day, quite differently from normal.

diamond_ramsey · #7 20th July 2010, 11:38 PM

dedanna, thank you for your posts.

Quote:

Originally Posted by dedanna1029

...[/COLOR]One more addition, then I'm done. Look at how updates went that day, quite differently from normal.

Interesting indeed.

Could you post the output from the following two commands, "yum repolist all" as well as "uname -r" to this this thread?

====================================
The following is my example:

[root@localhost ~]# yum repolist all
Loaded plugins: refresh-packagekit
repo id repo name status
fedora...
repolist: 22,240

[root@localhost ~]# uname -r
2.6.35-0.31.rc4.git4.fc14.i686.PAE
====================================
This may provide some clarity or more questions. Hope this helps.

stoat · #8 21st July 2010, 02:52 AM

Install the kernel you want. Reboot into it. If you like it, then list all of the installed kernels.

Code:

rpm -qa | grep kernel | sort

Then use yum to remove the kernels that you don't want.

Code:

su
yum remove kernel-PAE-2.6.xx.x-xxx.fc13.i686 kernel-PAE-2.6.xx.x-xxx.fc13.i686 kernel-PAE-2.6.xx.x-xxx.fc13.i686

Quote:

Originally Posted by dedanna1029

Look at how updates went that day, quite differently from normal.

Updating with delta rpms is enabled by a yum plugin (Presto). If you don't like that, you can disable it or uninstall it.

dedanna1029 · #9 21st July 2010, 04:37 PM

Quote:

Originally Posted by diamond_ramsey

dedanna, thank you for your posts.

You're welcome.

Quote:

Originally Posted by diamond_ramsey

Could you post the output from the following two commands, "yum repolist all" as well as "uname -r" to this this thread?

I could, but am not sure if it would do any good, as I've just said I've done a reinstall day before yesterday, and things are working okay for now.

---------- Post added at 09:37 AM CDT ---------- Previous post was at 09:36 AM CDT ----------

Quote:

Originally Posted by stoat

Install the kernel you want. Reboot into it. If you like it, then list all of the installed kernels.

Code:

rpm -qa | grep kernel | sort

Then use yum to remove the kernels that you don't want.

Code:

su
yum remove kernel-PAE-2.6.xx.x-xxx.fc13.i686 kernel-PAE-2.6.xx.x-xxx.fc13.i686 kernel-PAE-2.6.xx.x-xxx.fc13.i686

Updating with delta rpms is enabled by a yum plugin (Presto). If you don't like that, you can disable it or uninstall it.

Yes, I got all this already thanks. It was just unusual, as it had never done it before, and just happened to be on the update that totally hosed me and made me have to reinstall.

lexonight · #10 9th April 2012, 07:12 PM

after the grubby error on a kernel download, seeing as i have grub2 i run this

Quote:

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

that seams to work for me