Bug 708289 - Installation fails as it encounters a RAID5 mdadm volume
Summary: Installation fails as it encounters a RAID5 mdadm volume
Keywords:
Status: CLOSED DUPLICATE of bug 646157
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-27 07:23 UTC by dvandenbroeck
Modified: 2011-05-27 19:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-27 19:34:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda bug report (278.54 KB, text/xml)
2011-05-27 07:23 UTC, dvandenbroeck
no flags Details
Current disk state (771 bytes, text/plain)
2011-05-27 07:26 UTC, dvandenbroeck
no flags Details
blkid command result (1.21 KB, text/plain)
2011-05-27 07:27 UTC, dvandenbroeck
no flags Details

Description dvandenbroeck 2011-05-27 07:23:40 UTC
Created attachment 501259 [details]
Anaconda bug report

Good morning everybody,

I'm currently running Fedora 13 and trying to switch to F15, as I was not able to upgrade to F14 because of the same reasons.

I've downloaded and burned the DVD image of Fedora 15 for x86_64 platforms (which seems to work fine) and Anaconda fails after selecting the device type class (just after choosing the language and the keyboard type), while scanning existing the partitions. The top error message is:

  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/mdraid.py", line 81, in raidLevel
    raise ValueError, "invalid raid level descriptor %s" % descriptor

I use a box with three 500GB SATA disks. I installed Fedora 13 from scratch on the first one, then created later two RAID5 volumes with mdadm on it. Both these volumes use three identical partitions numbered sd{a,b,c}7 and sd{a,b,c}8. The first one contains my /home, is 92Go wide and 3/4 full.

As said before, the problem already occured with the previous release (14) and probably before, whether I try to upgrade from a running system with PackageKit or reinstall it from scratch with a DVD. 

I'd like the system just to ignore these partitions and let me re-set them up manually as the system is reinstalled, but I can't get the installer to do that. 

I tried to pass the options "nodmraid" and "nompath" but it didn't help. Whatever I do, it always crashes at the same stage.

Attached the bug report and some disk information

Comment 1 dvandenbroeck 2011-05-27 07:26:00 UTC
Created attachment 501260 [details]
Current disk state

Comment 2 dvandenbroeck 2011-05-27 07:27:15 UTC
Created attachment 501261 [details]
blkid command result

Comment 3 Chris Lumens 2011-05-27 19:34:00 UTC

*** This bug has been marked as a duplicate of bug 646157 ***


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