Red Hat Bugzilla – Bug 218192
dmraid needs the raid45 kernel module from Heinz Mauelshagen
Last modified: 2010-07-01 03:59:09 EDT
Description of problem:
I attempted to install FC6 on a new Intel Core 2 Duo E6300 CPU on an Asus
P5N32-E SLI motherboard (nVidia chipset) with RAID 5 configured for the 3 SATA
drives (all 3 are 320GB drives). After clicking "Next" when selecting the
keyboard type, the exception pops up.
The dump is attached (will be revised, as this one seems to be truncated).
NOTE: the only hard drives in the system are part of the RAID.
Install attempt was from DVD.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install system
Exception after clicking "next" when selecting keyboard
Ability to create partitions and mountpoints
Created attachment 142671 [details]
Created attachment 142686 [details]
Created attachment 142689 [details]
Does booting with 'linux nodmraid' help?
I'll try it, but I'm trying to set up the RAID5 cluster as the bootable
drive/partition, etc. Results to follow after I get home from work... :)
It works, but it brings up the 3 SATA drives as individual ones instead of a
single RAID 5 device.
That defeats the purpose of what I'm trying to do.
The probem here is a missing kernel module needed by dmraid, and the problem
exists in Fedora 7 as well as FC6.
Heinz Mauelshagen has been working on one, and while it may be in alpha format,
it would be useful if it were compiled as a separate package that it can be
Can't install Fedora8, Fedora9a on software raid5 (P5E motherboard) because of
this bug. It says something like
device-mapper target type "raid45" not in kernel.
and lsmod shows that raid456 module loaded instead raid45.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.
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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug is still valid for Fedora 8. I haven't tried Fedora 9 yet, as it was
This bug is still valid for Fedora 9 (and CentOS 5.2 too).
I'm sorry, but developers should feel ashamed.
If the problem is "device-mapper target type "raid45" not in kernel" I think that this bug only requires rename the module "raid456" to "raid45" (maybe an alias is valid too).
Do you need 2 years to fix it? How many versions of Fedora are affected?
It is not a bug in dmraid, it is only a module naming convention.
You can change kernel module name or you can change dmraid to require the same module name that you are using.
Other Linux distributions had this bug, but they solved it in weeks.
So please fix it.
Sorry for my anger.
changing version to 9
I filed a similar bug and added external bug for Ubuntu (solved, btw) for reference. My bug number is 473007 (may well be a duplicate of this one) and Ubuntu Launchpad bug is 220493
The device-mapper RAID45 module is in Alasdair's <firstname.lastname@example.org> upstream queue.
Once it goes mainline, Fedora will pick it up from there.
*** Bug 473007 has been marked as a duplicate of this bug. ***
Still present in Fedora 11 (Preview).
Any news as to when it will be fixed?
Instead of waiting for upstream kernel to include, can it be added to the fedora kernel?
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:
This problem is still here in installing Fedora 13 Beta LiveCD. I get to the anaconda installer to install to hard drive and when I get to start selecting what storage i'm going to be using then select next. It gives me an error, trace attached. I check the modules loaded with lsmod and get:
raid10 19948 0
raid456 62980 0
async_raid6_recov 5762 1 raid456
async_pq 4605 2 raid456,async_raid6_recov
raid6_pq 78519 2 async_raid6_recov,async_pq
async_xor 3503 3 raid456,async_raid6_recov,async_pq
xor 4528 1 async_xor
async_memcpy 2045 2 raid456,async_raid6_recov
async_tx 2626 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
raid1 20281 0
raid0 6006 0
Then I checked if my raid is active:
[root@localhost liveuser]# dmraid -ay
ERROR: device-mapper target type "raid45" is not in the kernel
RAID set "isw_dgchhijicb_MADHAT" was not activated
ERROR: device "isw_dgchhijicb_MADHAT" could not be found
I found this weird, is it trying to access an out dated kernel module or is there another problem.
This is what I'm trying to do. Just bought a new computer and got 6x1TB hard drives for a large RAID5 setup. I read somewhere that linux (as well thought Fedora), would support Intel FakeRAID technology. Set up the the RAID in BIOS and tried to install Fedora. And ran into the problem above. Got rid of the RAID and still ran into the problem above but I think that is part of another bug 533703.
Asus P7P55D-E Deleuxe
6x1TB WD Black 32MB Cashe (so 512B Sectors)
Created attachment 408986 [details]
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:
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.
This bug is still valid for Fedora 13.
We already have another bug for tracking this issue, esp. see:
Note that AFAIK work is (slowly) progressing upstream to abstract the raid4/5 code from mdraid so that it can be used by other subsystems (such as device mapper) too.
*** This bug has been marked as a duplicate of bug 533703 ***