Red Hat Bugzilla – Bug 200806
No way to switch from plain filesystem to RAID
Last modified: 2008-05-06 12:11:06 EDT
Description of problem:
Switching from a plain filesystem to a RAID configuration doesn't work in
mkinitrd. I was eventually forced to edit /init inside the mkinitrd
configuration manually in order to get it to add the commands to autodetect the
root md device.
Version-Release number of selected component (if applicable):
Switch from a plain system to a RAID-1 system.
Steps to Reproduce:
1. Create normal system
2. Add a disk to the system and set the partitions up as partial RAID-1
3. Remove initial disk and try to get Fedora to boot from the RAID-1 system
This sounds like you just need to make a new initrd in between steps 2 and 3.
Have you done that and left it out here? If not, can you try doing so?
/sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install "current
always works for me when I add md in a system that didn't had any.
Are there any drawbacks to always adding the md modules to the initrd even if
the system doesn't use md atthe moment of the initrd creation?
I did build a new mkinitrd. Even with --with=raid1, mkinitrd would include the
RAID modules, but would not add the autodetect command to the init start script.
I had to do that manually.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.