Bug 211030 (raid456)
| Summary: | mkinitrd fails to include raid5 module with kernel 2.6.18->panic | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dieter Stolte <dstolte> | ||||
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5 | CC: | andrew, arequipeno, bugzilla, bugzilla, ctm, dale, davej, gilboad, gresko, jburgess777, mozdiav, mw-redhat, nospam, steve, tom, triage, tschan+redhat.com | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-06 16:29:18 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dieter Stolte
2006-10-16 20:48:06 UTC
Until this is fixed, does anyone know how to create an initrd that will boot from a RAID-5 root? Ian Pilcher: Try this: # mv initrd-2.6.18-1.2200.fc5.img initrd-2.6.18-1.2200.fc5.img.bak # mkinitrd --with=raid456 /boot/initrd-2.6.18-1.2200.fc5.img 2.6.18-1.2200.fc5 *** Bug 211358 has been marked as a duplicate of this bug. *** *** Bug 208382 has been marked as a duplicate of this bug. *** *** Bug 211060 has been marked as a duplicate of this bug. *** still failing to install raid456.ko Have to: mkinitrd -v -f --with=raid456 /boot/initrd-2.6.18-1.2224.fc5smp.img 2.6.18-1.2224.fc5smp which results in: .... Adding module scsi_mod Adding module sd_mod Adding module libata Adding module sata_promise Adding module ata_piix Adding module jbd Adding module ext3 Adding module dm-mod Adding module dm-mirror Adding module dm-zero Adding module dm-snapshot Adding module xor Adding module raid456 ... which leads to a good .img file. *** Bug 214157 has been marked as a duplicate of this bug. *** still failing to install raid456 switching from kernel kernel-smp-2.6.17-1.2187_FC5 to kernel-smp-2.6.18-1.2239.fc5 with mkinitrd-5.0.32-2 Threw me I kickstarted a box with raid5 as the underlying device for LVM, rebooted okay the first time, yet after installing new kernel, failed to mount root. Come on, DaveJ, lots of people are hitting this bug! Shall I work on a patch or are you working on it already? Could the patch in: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=134188 be used? *** Bug 214937 has been marked as a duplicate of this bug. *** Still a problem with 2.6.18-1.2257.fc5 x86_64 quad proc. ... Same here. Dual Opteron 248, 2GB, RAID5/SATA. Sigh. - Gilboa mkinitrd is broken in rawhide also as far as software raid is concerned. I understand the engineers are aware of the problme and it is on a to-do list. No response to comment #9 AFAICT. Looking for action after the New Year... Created attachment 144383 [details]
mkinitrd raid fix
This patch tries to fix the initrd problem. Unfortunately it is not backward
compatible (yet).
Same problem with raid6.ko, I bet you knew that! My / is raid6. kernel-smp-2.6.18-1.2257.fc5 mkinitrd-5.0.32-2 *** Bug 220269 has been marked as a duplicate of this bug. *** The latest kernel for fc5, kernel-2.6.19-1.2288.2.4.fc5, still has the bug. How about the kernels for fc6? I really wish someone would apply my attached patch. It works well for me and could close this bug. The missing backward compatibility for kernels < 2.6.18 should not be a problem as noone with a new fixed mkinitrd will install such old kernels, imho. FC5 is not longer supported. Haven't seen this bug in F7/8. Unless I'm wrong, this bug can be closed. This was fixed shortly after reported. Don't know why it wasn't closed. 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. http://fedoraproject.org/wiki/LifeCycle/EOL 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 the change. 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: http://fedoraproject.org/wiki/BugZappers/F9CleanUp 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. |