Description of problem: the guest (btrfs-3) has many disks, i choose all 400mb ones. in manual partitioning i deleted all partitions. 1. Created a 400mb /boot 2. Created a 4.2gb / partittion type raid0 for the other 400mb disks for / Note over 2.: I could not do it directly (from the mount point dialog), since anaconda does not permit such setup. So i created a 1mb / partition which later i set it to 4.2gb type raid0. The following was filed automatically by anaconda: anaconda 18.37.8 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 1632, in __init__ self.size = int(size / len(devices)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1984, in setContainerMembers size_set = factory.set_class(members, container_size) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2167, in newDevice members=members, device=device) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 885, in _replace_device self.__storage.newDevice(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1106, in _save_right_side selector=selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2481, in on_apply_clicked self._save_right_side(self._current_selector) ZeroDivisionError: float division by zero Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet nokill BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.8 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 671625 [details] File: anaconda.log
Created attachment 671626 [details] File: environ
Created attachment 671627 [details] File: ifcfg.log
Created attachment 671628 [details] File: packaging.log
Created attachment 671629 [details] File: program.log
Created attachment 671630 [details] File: storage.log
Created attachment 671631 [details] File: syslog
Created attachment 671632 [details] File: anaconda-tb
*** Bug 892609 has been marked as a duplicate of this bug. ***
Tried to create 2 disk RAID0 stripe containing XFS mount for /home Package: anaconda-18.37.11 OS Release: Fedora release 18
Trying to configure /boot as raid device. Package: anaconda-18.37.11 OS Release: Fedora release 18
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.