Red Hat Bugzilla – Bug 592860
ValueError: Trying to pick boot devices but do not have a sane root partition. Aborting install.
Last modified: 2014-09-30 19:39:06 EDT
The following was filed automatically by anaconda: anaconda 14.5 exception report Traceback (most recent call first): File "/tmp/updates/pyanaconda/booty/bootloaderInfo.py", line 304, in availableBootDevices raise ValueError, ("Trying to pick boot devices but do not have a " File "/tmp/updates/bootloader.py", line 239, in hasWindows for (dev, type) in bl.images.availableBootDevices(bl.storage): File "/tmp/updates/iw/timezone_gui.py", line 108, in getScreen self.utcCheckbox.set_active(not hasWindows(anaconda.bootloader)) File "/tmp/updates/pyanaconda/gui.py", line 1422, in setScreen new_screen = self.currentWindow.getScreen(anaconda) File "/tmp/updates/pyanaconda/gui.py", line 1343, in nextClicked self.setScreen () ValueError: Trying to pick boot devices but do not have a sane root partition. Aborting install.
Created attachment 414820 [details] Attached traceback automatically from anaconda.
I see this on rawhide, in vmware, during the 'finding storage devices step'. It's not the vmware though, rhel6 passes there no problem.
Created attachment 415034 [details] Attached traceback automatically from anaconda.
Created attachment 417776 [details] Attached traceback automatically from anaconda.
Same here, but with KVM virt. I built a boot.iso for rawhide using mock. On boot isolinux flashes something that disappears too fast to read and goes directly to a boot: prompt. I updated it with a new updates.img from today, passing it: vmlinuz initrd=initrd.img stage2=hd:LABEL="Fedora" updates=http://proxy.home/updates/14.7.img And it has the same boot devices error (my traceback is from this attempt).
Created attachment 418731 [details] Attached traceback automatically from anaconda.
(In reply to comment #6) > Created an attachment (id=418731) [details] > Attached traceback automatically from anaconda. My attempted (hard drive) install was for the x86-64 version of Fedora 14 (Rawhide), downloaded as a nightly build yesterday.
*** Bug 596585 has been marked as a duplicate of this bug. ***
I think this is broken because of 0317f7cb17aed20bbbf7918488e9d7b2858aa0b2, without a kickstart this tries to take a look at the root device before the storage gets initialized. With kickstart this somehow doesn't appear (even though storage init still happens after the incriminated code is called..). Will investigate more later. Workaround for now: give it a kickstart.
Fixed by commit a1b11e33179f6f88752773ee7567342f5579df38 in anaconda-14.8. It was more related to 90fd1d4263bc823e90f025344789f9dc93492852. 0317f7cb17aed20bbbf7918488e9d7b2858aa0b2 is not the problem here.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping