Bug 253677 - mdadm does not find raid at boot-time
Summary: mdadm does not find raid at boot-time
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd   
(Show other bugs)
Version: 7
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-21 06:52 UTC by Tobias Bradtke
Modified: 2008-06-17 02:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 02:12:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tobias Bradtke 2007-08-21 06:52:28 UTC
Description of problem:

mdadm does not find raid at boot-time.

I created a raid-5-array with anaconda, added later other devices and all worked

Version-Release number of selected component:

# mdadm --version
mdadm - v2.6.2 - 21st May 2007

Actual results:

After a reboot mdadm gives an error:

> Red Hat nash 6.0.9 starting
> insmod: error inserting '/lib/raid456.ko': -1 File exists
> mdadm: no devices found for /dev/md1
>    Reading all physical volumes. This may take a while...
>    No volume groups found
>    Volume group "vg_raid" not found
> Unable to access resume device (/dev/vg_raid/lv_fedora_root)
> ...

Expected results:

No Problem.

Additional info:

Booting form the rescue-disc works without any problem, the raid is accessible.


The solution to this is to remove the kernel and re-install.
I found it here:

Comment 1 Doug Ledford 2007-08-24 16:13:39 UTC
Removing and reinstalling the kernel isn't the real fix.  It's just that
removing and reinstalling the kernel forces a rebuild of the initrd, and it's
the rebuilding of the initrd that solves the problem.  My guess is that during
installation a broken initrd image is built, probably due to package ordering or
something like that.  I'm reassigning this to the anaconda component.

Comment 2 Bug Zapper 2008-05-14 14:03:54 UTC
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

Comment 3 Bug Zapper 2008-06-17 02:12:23 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.