Description of problem: I just booted netinst Everything to anaconda. I destroyed RAID on disks before I booted (there is a intel FW RAID on this machine). Version-Release number of selected component: anaconda-25.20.8-1 The following was filed automatically by anaconda: anaconda 25.20.8-1 exception report Traceback (most recent call first): File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 148, in _add_device raise ValueError("device is already in tree") File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/populator/helpers/partition.py", line 111, in run self._devicetree._add_device(device) File "/usr/lib/python3.5/site-packages/blivet/populator/populator.py", line 306, in handle_device device = helper_class(self, info).run() File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/populator/populator.py", line 518, in _populate self.handle_device(dev) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/populator/populator.py", line 451, in populate self._populate() File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 271, in reset self.devicetree.populate(cleanup_only=cleanup_only) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 1175, in storage_initialize storage.reset() File "/usr/lib64/python3.5/threading.py", line 862, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self, *args, **kwargs) ValueError: device is already in tree Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-25 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 25
Created attachment 1218932 [details] File: anaconda-tb
Created attachment 1218933 [details] File: anaconda.log
Created attachment 1218934 [details] File: dnf.librepo.log
Created attachment 1218935 [details] File: environ
Created attachment 1218936 [details] File: hawkey.log
Created attachment 1218937 [details] File: lsblk_output
Created attachment 1218938 [details] File: nmcli_dev_list
Created attachment 1218939 [details] File: os_info
Created attachment 1218940 [details] File: storage.log
Created attachment 1218941 [details] File: syslog
Created attachment 1218942 [details] File: ifcfg.log
Created attachment 1218943 [details] File: packaging.log
Created attachment 1218944 [details] File: program.log
Similar problem has been detected: Can't install Fedora25 to SuperMicro SuperWorkstation 7048A-T with either Xfce live spin (USB or DVD) or server DVD edition. Machine has SW raid 5 array of eight 8TB spinning disks, and an LVM array of three 4TB PCIe SSDs. With the server DVD install, I can see that the raid monitoring service fails to start, and that a subsequent e2fsck (of the LVM?) takes a _long_time_ (~one minute of CPU time, with a considerable portion running at .3% load). After this, the Anaconda screen shows that an "unknown error" has occured. Apparently all of this happens in the background - I was watching "top" in ctl-alt-F2, and had intentionally not yet specified the language. I previously submitted bug 1410216, which your automated system automatically declared to be a duplicate of 1400318 (which may, or may not, be true). At this point, I may have no way to install Fedora25 on a machine that is running Fedora24 and has run Fedora23. Or do I? If so, how? As far as I am concerned, this is a SEVERE BUG. Please advise me on how to circumvent this! addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-25 rd.live.check quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 package: anaconda-25.20.8-1 product: Fedora reason: ValueError: device is already in tree release: Cannot get release name. version: 25
*** Bug 1430155 has been marked as a duplicate of this bug. ***
The partition UUIDs on your former-RAID drives are not unique, which is fatal problem that we are not equipped to walk you through addressing in the installer. You will have to clear the partitions yourself and retry the installation.
*** Bug 1476950 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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 this bug is closed as described in the policy above. 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.