Bug 24989 - RAID boot with 2.4 kernel
Summary: RAID boot with 2.4 kernel
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-25 23:46 UTC by Thomas Dodd
Modified: 2015-01-04 22:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-26 02:33:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Thomas Dodd 2001-01-25 23:46:12 UTC
The 2.4.0-0.43.12 kernel will not boot with / on a RAID volume.
2.4.0-0.99.5 looks to have the same problems.

The kernel config options were moved so CONFIG_MD_BOOT
is not selectable when RAID is a module (raid0.o, raid1.o).

RAID autodetect doesn't work when IDE is modular, since th
md driver runs autodetect prior to the IDE modules loading
and detecting the devices.

I changed linux/drivers/md/Config.in to move the autodetect
option to no require built-in raid, but the IDE issue hits.

Building IDE, MD, and RAIDx into rthe kernel works.

I'm testing 2.4.0-0.99.5 now, but the configfile still has
the autodetect option depending on builtin RAID drivers.

Comment 1 Dave Jones 2004-10-26 02:33:49 UTC
going through old unclosed bugs..
Did this ever get resolved? Does this problem still exist
in our current Fedora/RHEL products ?

Please reopen if this is still a problem.

Thanks.

Comment 2 Thomas Dodd 2004-10-26 13:43:51 UTC
I'd forgotten this. It was working throughmost of the 2.4 based
releases. RHL9 worked fine. I nolonger have SW RAID so I cannot say more.


Note You need to log in before you can comment on or make changes to this bug.