Bug 810572 - DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves
DeviceTreeError: MD RAID device md127 not in devicetree after scanning all sl...
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: David Lehman
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-06 15:11 EDT by Thomas Davis
Modified: 2013-02-13 09:02 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 09:02:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: anaconda-tb-ff8woi (396.25 KB, text/plain)
2012-04-06 15:11 EDT, Thomas Davis
no flags Details

  None (edit)
Description Thomas Davis 2012-04-06 15:11:29 EDT
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-7.fc16.x86_64
product:        Fedora
reason:         DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves
time:           Fri Apr  6 19:06:31 2012
version:        16

anaconda-tb-ff8woi: Text file, 405756 bytes

:The following was filed automatically by anaconda:
:anaconda 16.25 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 753, in addUdevMDDevice
:    "scanning all slaves" % name)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 999, in addUdevDevice
:    device = self.addUdevMDDevice(info)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 732, in addUdevMDDevice
:    self.addUdevDevice(new_info)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 999, in addUdevDevice
:    device = self.addUdevMDDevice(info)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1866, in _populate
:    self.addUdevDevice(dev)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1823, in populate
:    self._populate(progressWindow)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 476, in reset
:    cleanupOnly=cleanupOnly)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 104, in storageInitialize
:    storage.reset()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1273, in doKickstart
:    storage.storageInitialize(anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 88, in return_false
:    func(*args, **kwargs)
:DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves
Comment 1 Thomas Davis 2012-04-06 15:11:32 EDT
Created attachment 575817 [details]
File: anaconda-tb-ff8woi
Comment 2 Jesse Keating 2012-07-18 17:27:29 EDT
Nothing really obvious in the logs.  Were you able to get past this, or reproduce this in F17?
Comment 3 Thomas Davis 2012-07-18 17:39:01 EDT
I dumped the setup.  It still died in the release version; the problem is based on creating a raid10 setup using a two raid1 arrays of different sizes.  One array was 1TB, the other was 2TB.  Using kernel raid10 would give 2TB total space, using raid0 + raid1 gives 3TB space.

So you would have 3 raid devices - a raid1 of 1TB, a raid1 of 2TB, and a raid0 using the 2 raid1 devices.
Comment 4 Fedora End Of Life 2013-01-16 08:18:04 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 5 Fedora End Of Life 2013-02-13 09:02:05 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.