Bug 498486 - formatting error
formatting error
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-30 13:27 EDT by ENDOH takanao
Modified: 2014-11-19 04:36 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 08:17:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
djmchl: needinfo-

Attachments (Terms of Use)
Attached traceback automatically from anaconda. (280.19 KB, text/plain)
2009-04-30 13:27 EDT, ENDOH takanao
no flags Details

  None (edit)
Description ENDOH takanao 2009-04-30 13:27:44 EDT
The following was filed automatically by anaconda:
anaconda exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devicelibs/mdraid.py", line 187, in mdactivate
    raise MDRaidError("mdactivate failed for %s" % device)
  File "/usr/lib/anaconda/storage/devices.py", line 2364, in setup
  File "/usr/lib/anaconda/storage/devices.py", line 263, in setupParents
  File "/usr/lib/anaconda/storage/devices.py", line 1675, in setup
  File "/usr/lib/anaconda/storage/devices.py", line 263, in setupParents
  File "/usr/lib/anaconda/storage/devices.py", line 2031, in create
  File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute
  File "/usr/lib/anaconda/storage/devicetree.py", line 659, in processActions
  File "/usr/lib/anaconda/storage/__init__.py", line 234, in doIt
  File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems
MDRaidError: mdactivate failed for /dev/md2
Comment 1 ENDOH takanao 2009-04-30 13:27:51 EDT
Created attachment 341967 [details]
Attached traceback automatically from anaconda.
Comment 2 Bug Zapper 2009-06-09 10:54:16 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 3 Martin Gracik 2009-12-09 04:35:15 EST
Could you please provide the information about your disk setup, and steps you did during the installation, when you encountered this traceback, so we can reproduce the error?
Comment 4 Bug Zapper 2010-04-27 10:02:07 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 Bug Zapper 2010-06-28 08:17:46 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.