Red Hat Bugzilla – Bug 507255
F10 to F11 Upgrade, GRUB, then Exception
Last modified: 2010-06-28 09:12:09 EDT
The following was filed automatically by anaconda:
anaconda 184.108.40.206 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/booty/util.py", line 4, in getDiskPart
path = storage.devicetree.getDeviceByName(dev).path[5:]
File "/usr/lib/anaconda/booty/x86.py", line 374, in grubbyPartitionName
(name, partNum) = getDiskPart(dev, self.storage)
File "/usr/lib/anaconda/booty/x86.py", line 480, in upgradeGrub
grubbyStage1Dev = self.grubbyPartitionName(stage1Dev)
File "/usr/lib/anaconda/booty/x86.py", line 526, in write
chainList, defaultDev, justConfig)
File "/usr/lib/anaconda/bootloader.py", line 204, in writeBootloader
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext
File "/usr/lib/anaconda/text.py", line 712, in run
File "/usr/bin/anaconda", line 965, in <module>
AttributeError: 'NoneType' object has no attribute 'path'
Created attachment 348834 [details]
Attached traceback automatically from anaconda.
I did a fresh Fedora 10 LVM install on a BIOS RAID which is shared with a Win XP Pro x64 ntfs partition and a Win 7 ntfs partition. Rather than initializing the F10 install, I booted off of the Fedora 11 x86_64 DVD and chose to upgrade and to update the boot loader configuration. Note that the graphical installation (i.e. X server) failed. The package installation seemed to work fine. The boot loader update seemed to be very quick. After the boot loader update, an exception report was generated. I chose to save the report. The Finding Devices | Finding Storage Devices window generated an "Error processing drive sde". I chose to "Ignore" the drive and this bug report was then submitted.
Upon system restart, the x server fails. No error is shown. The GUI just doesn't appear. The graphics set up includes two ATI 3870 PCIE cards.
The storage is configured as a six-drive stripped BIOS RAID.
I had no such trouble with Fedora 10.
This bug may be related to 506807 which I contributed to earlier today.
-Sorry about the "Mid-Air Collision".
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.