Bug 1618535 - Anaconda crashes on startup due to raid: gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_eebfbibac'
Summary: Anaconda crashes on startup due to raid: gi.overrides.BlockDev.DMError: Faile...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Blivet Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-16 21:29 UTC by Maximilian Haye
Modified: 2019-05-28 22:09 UTC (History)
12 users (show)

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


Attachments (Terms of Use)
storage.log (13.91 KB, text/plain)
2018-08-16 21:31 UTC, Maximilian Haye
no flags Details
anaconda.log (9.28 KB, text/plain)
2018-08-16 21:32 UTC, Maximilian Haye
no flags Details
dbus.log (3.10 KB, text/plain)
2018-08-16 21:32 UTC, Maximilian Haye
no flags Details
ifcfg.log (1.83 KB, text/plain)
2018-08-16 21:33 UTC, Maximilian Haye
no flags Details
program.log (6.63 KB, text/plain)
2018-08-16 21:33 UTC, Maximilian Haye
no flags Details
sensitive-info.log (not really all that sensitive) (105 bytes, text/plain)
2018-08-16 21:34 UTC, Maximilian Haye
no flags Details
Screenshot for the sake of completeness - don't mind the German (192.95 KB, image/png)
2018-08-16 21:37 UTC, Maximilian Haye
no flags Details

Description Maximilian Haye 2018-08-16 21:29:09 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build Identifier: 

When attempting to start Anaconda on the Fedora 28 Workstation Live CD, it immediately crashes with the following stacktrace (plus some extra bits above and below it):
```
[liveuser@localhost-live ~]$ liveinst
RAID set "pdc_eebfbibac" already active
RAID set "pdc_eebfbibac" was not activated
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 798, in wrapped
    ret = orig_obj(*args, **kwargs)
GLib.Error: g-bd-dm-error-quark: Failed to activate the RAID set 'pdc_eebfbibac' (3)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/anaconda-cleanup", line 82, in <module>
    devicetree.populate(cleanup_only=True)
  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/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 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 303, in handle_format
    helper_class(self, info, device).run()
  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/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 824, in wrapped
    raise transform[1](msg)
gi.overrides.BlockDev.DMError: Failed to activate the RAID set 'pdc_eebfbibac'
Starting installer, one moment...
anaconda 28.22.11-1.fc28 for Fedora 28 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * when reporting a bug add logs from /tmp as separate text/plain attachments
RAID set "pdc_eebfbibac" already active
RAID set "pdc_eebfbibac" was not activated

(anaconda:4364): PkGtkModule-WARNING **: 18:32:01.177: Error connecting to PK session instance: Connection is closed
```
This happend with the version that came with it (I don't recall which) as well as after upgrading to 28.22.11-1.fc28 via `dnf upgrade anaconda`.

Some info on the relevant parts of my system:
* Motherboard: GA-78LMT-USB3 (BIOS, no UEFI if that makes a difference)
* RAID Controller integrated in MB: Give me a minute to find out and add a comment.
* RAID Setup: 2 WD Blue 1TB HDDs in RAID0, one lonely 250GB Hitachi HDD
* CPU: AMD Phenom II X4 965


Reproducible: Always

Steps to Reproduce:
1. Grab and burn / flash a Fedora 28 Live CD
2. Run it on a machine with, I'm guessing, some certain RAID controller 
3. Start Anaconda
Actual Results:  
The program hangs for a few seconds, before two "An unkown error has occured"-boxes pop up.

Expected Results:  
No crash.

Comment 1 Maximilian Haye 2018-08-16 21:31:31 UTC
Created attachment 1476519 [details]
storage.log

Comment 2 Maximilian Haye 2018-08-16 21:32:15 UTC
Created attachment 1476520 [details]
anaconda.log

Comment 3 Maximilian Haye 2018-08-16 21:32:34 UTC
Created attachment 1476521 [details]
dbus.log

Comment 4 Maximilian Haye 2018-08-16 21:33:02 UTC
Created attachment 1476522 [details]
ifcfg.log

Comment 5 Maximilian Haye 2018-08-16 21:33:55 UTC
Created attachment 1476523 [details]
program.log

Comment 6 Maximilian Haye 2018-08-16 21:34:45 UTC
Created attachment 1476524 [details]
sensitive-info.log (not really all that sensitive)

Comment 7 Maximilian Haye 2018-08-16 21:37:23 UTC
Created attachment 1476526 [details]
Screenshot for the sake of completeness - don't mind the German

Comment 8 Maximilian Haye 2018-08-16 21:46:49 UTC
So the RAID controller seems to be from AMD (or maybe ATI?). A SATA controller by one of these names: SB7x0/SB8x0/SB9x0. It's PCI ID is 1002:4392. https://pci-ids.ucw.cz/read/PC/1002/4392.

Comment 9 Maximilian Haye 2018-08-17 06:37:37 UTC
If there's something missing from this report - or for any other reason, I'm hanging around in Freenode as MHajoha, where you should be able to get in touch with me. Timezone UTC+2.

Comment 10 Jiri Konecny 2018-08-17 06:47:45 UTC
This is storage related issue. I'm switching this to blivet - our storage library.

Comment 11 Ben Cotton 2019-05-02 21:05:11 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 12 Ben Cotton 2019-05-28 22:09:57 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.