Bug 1631228 - gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bjifjcag'
Summary: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bjifjcag'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2d1c36b945af1a14824cb7bef5b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-20 09:12 UTC by dtdraganov
Modified: 2019-05-28 22:53 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:53:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (981.48 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: anaconda.log (28.06 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: dbus.log (9.30 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: environ (734 bytes, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: journalctl (765.01 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: lsblk_output (1.92 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: nmcli_dev_list (1.60 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: os_info (623 bytes, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: program.log (38.21 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: storage.log (123.68 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details
File: ifcfg.log (5.83 KB, text/plain)
2018-09-20 09:12 UTC, dtdraganov
no flags Details

Description dtdraganov 2018-09-20 09:12:28 UTC
Description of problem:
I tried to install Fedora 28 from live image (from USB), and it constantly gives me this error at the very beginning of the install screen (where I have to choose what language to use diring the installation), so I am unable to continue the install process.

Version-Release number of selected component:
anaconda-core-28.22.10-1.fc28.i686

The following was filed automatically by anaconda:
anaconda 28.22.10 exception report
Traceback (most recent call first):
  File "/usr/lib/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 303, in handle_format
    helper_class(self, info, device).run()
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 275, in handle_device
    self.handle_format(info, device)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 462, in _populate
    self.handle_device(dev)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/populator/populator.py", line 412, in populate
    self._populate()
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 161, in reset
    self.devicetree.populate(cleanup_only=cleanup_only)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pyanaconda/storage/osinstall.py", line 1670, in reset
    super().reset(cleanup_only=cleanup_only)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/pyanaconda/storage/osinstall.py", line 2193, in storage_initialize
    storage.reset()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.6/site-packages/pyanaconda/threading.py", line 291, in run
    threading.Thread.run(self)
gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_bjifjcag'

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-28-1-1 rd.live.image quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.16.3-301.fc28.i686
other involved packages: python3-libs-3.6.5-1.fc28.i686, python3-blivet-3.0.0-0.6.1.b1.fc28.noarch, python3-blockdev-2.16-2.fc28.i686
product:        Fedora
release:        Fedora release 28 (Twenty Eight)
type:           anaconda
version:        28

Comment 1 dtdraganov 2018-09-20 09:12:36 UTC
Created attachment 1485069 [details]
File: anaconda-tb

Comment 2 dtdraganov 2018-09-20 09:12:38 UTC
Created attachment 1485070 [details]
File: anaconda.log

Comment 3 dtdraganov 2018-09-20 09:12:40 UTC
Created attachment 1485071 [details]
File: dbus.log

Comment 4 dtdraganov 2018-09-20 09:12:41 UTC
Created attachment 1485072 [details]
File: environ

Comment 5 dtdraganov 2018-09-20 09:12:45 UTC
Created attachment 1485073 [details]
File: journalctl

Comment 6 dtdraganov 2018-09-20 09:12:47 UTC
Created attachment 1485074 [details]
File: lsblk_output

Comment 7 dtdraganov 2018-09-20 09:12:48 UTC
Created attachment 1485075 [details]
File: nmcli_dev_list

Comment 8 dtdraganov 2018-09-20 09:12:50 UTC
Created attachment 1485076 [details]
File: os_info

Comment 9 dtdraganov 2018-09-20 09:12:52 UTC
Created attachment 1485077 [details]
File: program.log

Comment 10 dtdraganov 2018-09-20 09:12:54 UTC
Created attachment 1485078 [details]
File: storage.log

Comment 11 dtdraganov 2018-09-20 09:12:56 UTC
Created attachment 1485079 [details]
File: ifcfg.log

Comment 12 Bill 2018-10-13 19:07:04 UTC
Similar problem has been detected:

From Fedora 28 Live, install Fedora 28 to hard drive. Problem occurs after selecting language and clicking continue.

Motherboard: MSI 890FXA-GD70 (MS-7640) with latest BIOS

SATA set to RAID in BIOS. I have two SSDs set to RAID 0 - Windows 10 is installed here

I have two other non-RAID drives in system. I was going to install Fedora to one of these.

I had to disable IOMMU in BIOS in order to get Fedora Live to load.

addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-28-1-1 rd.live.image rd.live.check quiet
hashmarkername: anaconda
kernel:         4.16.3-301.fc28.x86_64
other involved packages: python3-blivet-3.0.0-0.6.1.b1.fc28.noarch, python3-libs-3.6.5-1.fc28.x86_64, python3-blockdev-2.16-2.fc28.x86_64
package:        anaconda-core-28.22.10-1.fc28.x86_64
packaging.log:  
product:        Fedora
reason:         gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_cagheaajje'
release:        Fedora release 28 (Twenty Eight)
version:        28

Comment 13 Ben Cotton 2019-05-02 19:23:50 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 14 Ben Cotton 2019-05-02 20:40:03 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.

Comment 15 Ben Cotton 2019-05-28 22:53:14 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.


Note You need to log in before you can comment on or make changes to this bug.