Description of problem: I am trying to install Fedora in a new logical volume in an existing volume group. The existing volume group has two physical volumes - a RAID-0 device, and an SSD. Both physical are LUKS formatted. After I decrypt both devices a new option group shows up in the list of devices called "unknown linux install". When I click on this to expand it I get the crash. The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/mdraid.py", line 92, in raidLevel raise MDRaidError("invalid raid level descriptor %s" % descriptor) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1410, in _get_raid_disabled_features level = mdraid.raidLevel(feature_raid_levels[feature]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1462, in _populate_raid disabled = self._get_raid_disabled_features(raid_level) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1718, in _populate_right_side self._populate_raid(raid_level, device.size) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2199, in on_selector_clicked self._populate_right_side(selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1936, in _show_first_mountpoint self.on_selector_clicked(page._members[0]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2222, in on_page_clicked self._show_first_mountpoint(page=page) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 119, in _onExpanded cb(obj.get_child()) MDRaidError: invalid raid level descriptor raid1 Additional info: cmdline: /usr/bin/python /usr/sbin/anaconda cmdline_file: initrd=initrd0.img root=live:UUID=B030-176C rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /usr/sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.11-1.fc18.x86_64 product: Fedora release: Fedora release 18 (Spherical Cow) type: libreport version: 18
Created attachment 704606 [details] File: anaconda-tb
Created attachment 704607 [details] File: anaconda.log
Created attachment 704608 [details] File: environ
Created attachment 704609 [details] File: ifcfg.log
Created attachment 704610 [details] File: packaging.log
Created attachment 704611 [details] File: program.log
Created attachment 704612 [details] File: storage.log
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.