Bug 83921

Summary: grubby segmentation fault leaves upgrade unbootable
Product: [Retired] Red Hat Linux Reporter: Chris Ricker <chris.ricker>
Component: mkinitrdAssignee: Erik Troan <ewt>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: high    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 79578, 84358    
Attachments:
Description Flags
grub.conf that grubby segfaulted on none

Description Chris Ricker 2003-02-10 03:34:52 UTC 
I just tried upgrading to pre-beta5 (mkinitrd 3.4.39-1)

After the upgrade, the system failed to boot. The upgrade had replaced the old
kernel with the new one, but left the old grub.conf in place. Looking through
grub.conf, it appears that the old grub.conf is because grubby segfaulted when
the kernel was upgraded.

Upgrading kernel-2.4.20-2.33.
/sbin/new-kernel-pkg: line 260:   534 Segmentation fault      /sbin/grubby --add
-kernel=$bootPrefix/vmlinuz-$version $INITRD --copy-default --title "$title" --a
rgs="root=$rootdevice" --remove-kernel="TITLE=$title"
/sbin/new-kernel-pkg: line 260:   545 Segmentation fault      /sbin/grubby --rem
ove-kernel=$bootPrefix/vmlinuz-$version
Comment 1 Jeremy Katz 2003-02-10 06:52:56 UTC 
Could you attach the grub.conf?
Comment 2 Chris Ricker 2003-02-10 15:14:00 UTC 
Created attachment 89970 [details]
grub.conf that grubby segfaulted on

This is the grub.conf on the system already which grubby didn't upgrade....
Comment 3 Jeremy Katz 2003-02-18 17:25:19 UTC 
I don't see anything at all wrong with the grub.conf, but it sounds suspiciously
like bug 84128

*** This bug has been marked as a duplicate of 84128 ***
Comment 4 Red Hat Bugzilla 2006-02-21 18:51:41 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.