Bug 1139206

Summary: MDRaidError: mdactivate failed for /dev/md/2: running mdadm --assemble /dev/md/2 --uuid=d4b6c747:e7f2546c:7797ff7a:c975c701 --run /dev/sda3 /dev/sdb3 /dev/sdc3 failed
Product: [Fedora] Fedora Reporter: spital <spital>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0b4119385ea1f8590d5b0bff96466ce8635f511fe93e07f216ebd0740429ac64
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:26:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description spital 2014-09-08 11:50:14 UTC
Description of problem:
I created raid devices with MDADM and tried to install Fedora 20 x64.

* On the first graphical BFO scren (lang selection) I pressed ALT+SHIFT+F2
* using mdadm created 3 raids for /boot, / and swap
* continued with graphical install
* everything looked fine, but alas- error

Version-Release number of selected component:
anaconda-20.25.15-1

The following was filed automatically by anaconda:
anaconda 20.25.15-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/mdraid.py", line 214, in mdactivate
    raise MDRaidError("mdactivate failed for %s: %s" % (device, msg))
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 3372, in _setup
    uuid=self.uuid)
  File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 716, in setup
    self._setup(orig=orig)
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 534, in execute
    self.device.setup(orig=True)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 239, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 308, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 167, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 142, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run
    threading.Thread.run(self, *args, **kwargs)
MDRaidError: mdactivate failed for /dev/md/2: running mdadm --assemble /dev/md/2 --uuid=d4b6c747:e7f2546c:7797ff7a:c975c701 --run /dev/sda3 /dev/sdb3 /dev/sdc3 failed

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   repo=http://download.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/ initrd=http://download.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img BOOT_IMAGE=http://download.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.10-301.fc20.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        20

Potential duplicate: bug 985207

Comment 1 spital 2014-09-08 11:50:20 UTC
Created attachment 935309 [details]
File: anaconda-tb

Comment 2 spital 2014-09-08 11:50:21 UTC
Created attachment 935310 [details]
File: anaconda.log

Comment 3 spital 2014-09-08 11:50:22 UTC
Created attachment 935311 [details]
File: environ

Comment 4 spital 2014-09-08 11:50:23 UTC
Created attachment 935312 [details]
File: lsblk_output

Comment 5 spital 2014-09-08 11:50:25 UTC
Created attachment 935313 [details]
File: nmcli_dev_list

Comment 6 spital 2014-09-08 11:50:26 UTC
Created attachment 935314 [details]
File: os_info

Comment 7 spital 2014-09-08 11:50:28 UTC
Created attachment 935315 [details]
File: program.log

Comment 8 spital 2014-09-08 11:50:30 UTC
Created attachment 935316 [details]
File: storage.log

Comment 9 spital 2014-09-08 11:50:32 UTC
Created attachment 935317 [details]
File: syslog

Comment 10 spital 2014-09-08 11:50:33 UTC
Created attachment 935318 [details]
File: ifcfg.log

Comment 11 spital 2014-09-08 11:50:36 UTC
Created attachment 935319 [details]
File: packaging.log

Comment 12 Fedora End Of Life 2015-05-29 12:49:25 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 13 Fedora End Of Life 2015-06-29 22:26:12 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.