Bug 450479 - Anaconda unable to recognise grub, "replace" crashes
Anaconda unable to recognise grub, "replace" crashes
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-06-08 20:34 EDT by Scott Schmit
Modified: 2008-09-23 10:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-23 10:49:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Traceback generated by anaconda (70.61 KB, text/plain)
2008-06-08 20:34 EDT, Scott Schmit
no flags Details

  None (edit)
Description Scott Schmit 2008-06-08 20:34:49 EDT
Description of problem:
Anaconda was (apparently) unable to find/recognize my grub bootloader and/or
/boot partition. As a result, it treated it as if the system had a third-party
boot loader and refused to update the config. I had an option to replace the
boot loader or skip config altogether. I selected replace, causing a traceback
and crash, which is attached.

Version-Release number of selected component (if applicable):
Anaconda, according to the traceback.

How reproducible:
It happened every time until I told anaconda to skip instead (at least 2 or 3

Steps to Reproduce:
1. Somehow get into a state where anaconda doesn't recognize a perfectly valid
/boot (?)
2. Upgrade the installation.
Actual results:
3. See that anaconda doesn't recognize /boot, but you can replace or skip
4. Select replace, click next
5. Watch the installer crash and offer to save the traceback/debug information.

Expected results:
3. Anaconda gives you the option to update, replace, or skip
4. Selecting any of the provided options doesn't crash, but does what it says it

Barring that, anaconda should never crash, ever (especially not for options it
gives me). I'm just glad it hadn't modified my disk yet.

Additional info:
This occurred when I updated my gateway machine (which has my DNS, & DHCP
server, hence the manual/IP setup) from Fedora 7 to Fedora 9. The partitioning
of the drive is from the default (or near-default) partitioning of an earlier
install, so I don't know of anything that would cause the installer to act like
it did.

Postinstall info:
$ df -h
Filesystem            Size  Used Avail Use% Mounted on
                       72G  9.6G   59G  15% /
/dev/sda1              99M   19M   76M  20% /boot
tmpfs                 124M     0  124M   0% /dev/shm

# fdisk -l

Disk /dev/sda: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd0f4738c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        9726    78019672+  8e  Linux LVM

Hope this helps.
Comment 1 Scott Schmit 2008-06-08 20:34:50 EDT
Created attachment 308665 [details]
Traceback generated by anaconda
Comment 2 Chris Lumens 2008-09-23 10:49:55 EDT
I do believe I've fixed up the problem with not identifying the existing bootloader configuration for F10 Beta.

Note You need to log in before you can comment on or make changes to this bug.