Bug 202596

Summary: mkinitrd not loading raid456 module for raid5 devices
Product: [Fedora] Fedora Reporter: Clyde E. Kunkel <clydekunkel7734>
Component: mkinitrdAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: davej, jturner, notting
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-17 18:33:57 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:
Bug Depends On:    
Bug Blocks: 150224, 202996    
Attachments:
Description Flags
mkinitrd -f -v without specifying any modules to load
none
mkinitrd -f -v --with=raid456 none

Description Clyde E. Kunkel 2006-08-15 13:15:16 UTC 
Description of problem:
mkinitrd detecting need for raid5 personality, but does not load raid456 module
and thus the resulting initrd fails with kernel panic, not syncing since /
cannot be found.

Version-Release number of selected component (if applicable):
mkinitrd-5.1.6-1

How reproducible:
Every time.

Steps to Reproduce:
1. yum update
2. reboot
3. kernel panic.  Msg that raid5 personality not loaded is seen during initrd boot
  
Actual results:
kernel panic since / can't be found

Expected results:
Normal boot

Additional info:

This system has the root filesystem on LVM over software raid5.  The problem has
been around awhile, but only discovered when updating system from rawhide after
not updating for over two months.  

Running mkinitrd -f -v without specifying raid456 module results is same bad img
file as when using yum.  File attached showing results.  Note that need for
raid5 is detected, but module raid456 is not loaded.  Running mkinitrd -f -v
--with=raid456 results in good img file that boots properly.  File attached
showing results.  Previous version of mkinitrd also failed.  Did not go back
farther to see where the problem started.
Comment 1 Clyde E. Kunkel 2006-08-15 13:15:16 UTC 
Created attachment 134209 [details]
mkinitrd -f -v without specifying any modules to load
Comment 2 Clyde E. Kunkel 2006-08-15 13:16:32 UTC 
Created attachment 134210 [details]
mkinitrd -f -v --with=raid456
Comment 4 Bill Nottingham 2006-08-15 15:53:53 UTC 
The patch in bug 202559 fixes this as a side effect.
Comment 5 Jay Turner 2006-08-18 01:19:04 UTC 
What in the world happened with this bug.  It was a RHEL5 bug with a beta
blocker status requested, but now it's a FC bug which has been closed out.  Is
this still an issue with RHEL5?  More importantly, is this an issue which needs
to be resolved for beta?  If so, we really need a RHEL version of the bug to
track things.
Comment 6 Jay Turner 2006-08-18 01:20:55 UTC 
OK, ignore comment 5.  I see this was cloned to another bug for RHEL.
Comment 7 Clyde E. Kunkel 2006-10-17 21:21:06 UTC 
I am seeing this bug for mkinitrd-5.0.32-2 when updating FC5 to kernel
2.6.18-1.2200.fc5smp.  Reruning mkinitrd under an older FC5 kernel and using
--with=raid456 solves the problem.

Should this bug be reopened or a new bug entered?
Comment 8 Bill Nottingham 2006-10-17 21:25:23 UTC 
Open a new one, please.
Comment 9 Clyde E. Kunkel 2006-10-17 23:27:11 UTC 
found one already opened:  bug 211030.