Description of problem: Error popped up during installation Version-Release number of selected component: anaconda-27.20.4-1 The following was filed automatically by anaconda: anaconda 27.20.4-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 824, in wrapped raise transform[1](msg) File "/usr/lib/python3.6/site-packages/blivet/populator/helpers/dmraid.py", line 69, in run blockdev.dm.activate_raid_set(rs_name) File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 345, in handle_format helper_class(self, info, device).run() File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 318, in handle_device self.handle_format(info, device) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 519, in _populate self.handle_device(dev) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 454, in populate self._populate() File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 272, in reset self.devicetree.populate(cleanup_only=cleanup_only) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/osinstall.py", line 1175, in storage_initialize storage.reset() File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 252, in run threading.Thread.run(self) gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'nvidia_bdahgace' Additional info: addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-dvd-x86_64-27 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.13.9-300.fc27.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 27
Created attachment 1368504 [details] File: anaconda-tb
Created attachment 1368505 [details] File: anaconda.log
Created attachment 1368506 [details] File: dnf.librepo.log
Created attachment 1368507 [details] File: environ
Created attachment 1368508 [details] File: lorax-packages.log
Created attachment 1368509 [details] File: lsblk_output
Created attachment 1368510 [details] File: nmcli_dev_list
Created attachment 1368511 [details] File: os_info
Created attachment 1368512 [details] File: program.log
Created attachment 1368513 [details] File: storage.log
Created attachment 1368514 [details] File: syslog
Created attachment 1368515 [details] File: ifcfg.log
Created attachment 1368516 [details] File: packaging.log
It looks like a storage related issue. Changing components. Could be related to bug 1476513.
When I read look into bug 1476513 the cases look very similar. This case also happened on a system containing a nForce 790i chipset with a couple of WD drives in RAID. The error popped up during installation (using a Fedora netinstall disk). When the installer opens for the language and keyboard selections, a popup comes up with the message "unknown error" occured. Only after reporting the bug into bugzilla the header of the window contained info "Failed to activate the RAID set 'nvidia_bdahgace'". If more info is required, or something has to be tried, pls give me a sign.
*** Bug 1529499 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I just tried to install Fedora. When it reaches to the point of choosing language and keyboard for the instalation, the installer crashes. The install is from USB drive.The computer is with Pentium IV CPU, and I am trying to install 32 bit version of Fedora 27. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-dvd-i386-27 quiet hashmarkername: anaconda kernel: 4.13.9-300.fc27.i686 package: anaconda-27.20.4-1 product: Fedora reason: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bjifjcag' release: Cannot get release name. version: 27
Similar problem has been detected: Appeard immediately on presentation of the installer addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-27 rd.live.check quiet hashmarkername: anaconda kernel: 4.13.9-300.fc27.x86_64 package: anaconda-27.20.4-1 product: Fedora reason: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_djgjgehdjc' release: Cannot get release name. version: 27
Motherboard: P5QL-E Chipset: Intel® P43 ICH10R RAID controller: On-board Southbridge Intel Matrix Storage Technology RAID Configuration: 2 x 120GB disks in RAID 0
Disks: Western Digital WD1200JD-00GBB0
Similar problem has been detected: I switched the storage configuration in the BIOS to AHCI (formerly RAID). The RAID controller doesn't seem to be in use (I don't see the usual RAID controll configuration/POST screen on boot) but still it fails with the same error as beforee. The two RAID0 disks are NTFS formatted, with Windows 7 Pro installed. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-27 quiet hashmarkername: anaconda kernel: 4.13.9-300.fc27.x86_64 package: anaconda-27.20.4-1 product: Fedora reason: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_djgjgehdjc' release: Cannot get release name. version: 27
Still ongoing in Fedora 28. I still only have the storage controller set to AHCI (not RAID) in the BIOS settings.
I noticed it was erroring-out against what seemed to be a md device (/dev/mapper/pdc-blablabla). Sorry I didn't capture the exact message. However couldn't figure out where this device was mapped. I tried "mdamd --zero-superblock <device>" on all disks but it didn't identify any of them as "md" devices. Tried "lvm pvremove /dev/mapper/pdc-..." (sorry I didn't cap the exact text) I went into the BIOS and switched the SATA storage controller from AHCI to IDE, and then the error went away on next boot. So I switched it back to AHCI, and disabled all disks. Error still gone. Then I switched from IDE to RAID. I selected the option to remove all arrays, but it didn't find any. So I created a new RAID 0 array on the two disks that used to have the array, and now when I boot the installer i works! It also sees the BIOS RAID array when selecting disks. In hindsight the installer wasn't seeing all of the disks, and I guess there was some kind of RAID array still written to the disk that was "corrupt" as far as the OS could tell? But still, it'd be good if it didn't fail the whole installer even when this does occur. But an edge case I guess. I'm guessing that's the link between the original report and this, as opposed to the chipset or disk brand/model.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.