Bug 144650
| Summary: | mkinitrd fails to recognize that raid1 is compiled into the kernel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Fat Rat Bastard <fat_rat_bastard> |
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-01-17 16:39:11 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: | |||
We don't really support using kernels that we don't ship, or at the very least aren't at all built like ours. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Description of problem: I configured a 2.6.10 kernel with raid1 statically-linked (not a module). When running mkinitrd I get the message: No module raid1 found for kernel 2.6.10c, aborting. There is no reference to raid1 in /etc/modprobe.conf. If I execute mkinitrd with the --builtin=raid1 directive, I get an initial ram disk that boots and mounts my raid 1 /, swap, and /boot partitions. Version-Release number of selected component (if applicable): mkinitrd 4.1.18 How reproducible: Always Steps to Reproduce: 1. Configure/compile 2.6.10 kernel with raid1 statically linked. 2. Use mkinitrd 4.1.18 to make the initial ram disk 3. Actual Results: I get message: No module raid1 found for kernel 2.6.10c, aborting. Expected Results: Completes the process of making an initial ram disk with modules, etc. Additional info: