The following was filed automatically by anaconda: anaconda 15.20.1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 732, in addUdevMDDevice "devicetree as %s" % (name, device.name)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 979, in addUdevDevice device = self.addUdevMDDevice(info) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1764, in _populate self.addUdevDevice(dev) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1722, in populate self._populate() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 434, in reset self.devicetree.populate() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 103, in storageInitialize storage.reset() File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked self.anaconda.dispatch.gotoNext() DeviceTreeError: MD RAID device md127 already in devicetree as md0
Created attachment 480825 [details] Attached traceback automatically from anaconda.
Installation on Intel BIOS RAID with LiveCD (alpha RC1 / KDE) not possible, DVD not checked. This breaks the following test case: http://fedoraproject.org/wiki/QA:Testcase_Install_to_BIOS_RAID ...as this expected result is not fulfilled: "All installable BIOS RAID devices are successfully detected by installer and are available for partitioning" According to http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#General_Tests ...that's a beta criterion. Therefore I'm going to propose this as a beta blocker.
Created attachment 481472 [details] Attached traceback automatically from anaconda.
like Sandro, I hit this after applying the patch for 678877.
Created attachment 481913 [details] Patch to improve handling of active fwraid during devicetree populate This is related to the fact that dracut has started activating fwraid arrays automatically on livecd startup.
Created attachment 481914 [details] Patch to improve handling of active fwraid during devicetree populate
I can confirm that patch to fix this issue. I then hit bug 681608, though.
it's RAID whack-a-mole, hooray. dlehman: do we want to stop dracut doing that, for the live boot?
Patches that (attempt to) fix all known firmware RAID issues for F15 are available in bug 681608 for those doing live installs. For those doing non-live installs, just ask and I'll be happy to provide an updates image for you to test with. As for dracut assembling the fwraid... it was considered a bug when they were not auto-assembled, so we should probably leave it be now.
Last patch had a problem. It did not take into account the fact that mdadm will append an underscore and some number of digits to the name of an array it assembles if the system hostname at the time of assembly does not match the hostname in the array metadata. Good stuff. New patch: http://dlehman.fedorapeople.org/fwraid-f15.4.patch New updates: http://dlehman.fedorapeople.org/updates-fwraid-f15.4.img Please test and let me know the results.
*** Bug 660258 has been marked as a duplicate of this bug. ***
Fixed for Fedora 15 in anaconda-15.22-1.
anaconda-15.22-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/anaconda-15.22-1.fc15
Discussed at 2011-03-11 blocker review meeting. This issue is fixed and available for testing in anaconda-15.22-1. The issue has been accepted as a beta blocker.
anaconda-15.22-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.