Bug 450479
| Summary: | Anaconda unable to recognise grub, "replace" crashes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scott Schmit <i.grok> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | low | ||||||
| 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: | 2008-09-23 14:49:55 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: | |||||||
| Attachments: |
|
||||||
Created attachment 308665 [details]
Traceback generated by anaconda
I do believe I've fixed up the problem with not identifying the existing bootloader configuration for F10 Beta. |
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 11.4.0.82, according to the traceback. How reproducible: It happened every time until I told anaconda to skip instead (at least 2 or 3 times). 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 will. 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 /dev/mapper/VolGroup00-LogVol00 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.