Bug 130107 - mkinitrd & nash
Summary: mkinitrd & nash
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mkinitrd
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-17 07:19 UTC by facs
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-18 16:00:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description facs 2004-08-17 07:19:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)

Description of problem:
I have downloaded the source code of mkinitrd, I have applied the 
patch:
--- mkinitrd-3.5.13/mkinitrd.BAD        2004-05-11 
22:12:55.918825872 -0500+++ mkinitrd-3.5.13/mkinitrd    2004-05-11 
22:14:46.579002968 -0500@@ -399,6 +399,10 @@            findmodule 
linear            startraid=1            ;;+       multipath)
+           findmodule multipath+           
startraid=1+           ;;        raid[0145])            findmodule 
$level            startraid=1
and i have created the new rpm and I have installed it on my system.
After this operations, mkinitrd insert on file linuxrc the commands:
raidautorun /dev/md0
raidautorun /dev/md1
raidautorun /dev/md2
raidautorun /dev/md3
on boot the shell nash run the commands raidautorun but the meta 
devices doesn't start.
Can anyone help me?
Thanks a lot

Version-Release number of selected component (if applicable):
mkinitrd-3.5.13-1a [mkinitrd-3.5.13-1 + patch]

How reproducible:
Always

Steps to Reproduce:
1.boot server
2.
3.
    

Actual Results:  the meta devices /dev/md0 /dev/md1 /dev/md2 /dev/md3 
doesn't start

Additional info:

Comment 1 Jeremy Katz 2004-08-18 16:00:46 UTC
It's possible the kernel doen't know how to autostart multipath
devices.  mkinitrd doesn't do these as such by default, though and
it's not something I can really support.


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