Just a guess, but do you need an alias for md-personality-3 in your
/etc/conf.modules?
I do know that RedHat screwed up /etc/rc.d/rc.sysinit in 6.0 - they left in
the old raid startup methods (what was it raidadd or something?). You might
need to modify that file also...
fwr
----- Original Message -----
From: Rlas Kotowski <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 28, 1999 5:31 PM
Subject: Raid-1 Red Hat 6.0 problem at boot
> Hi,
>
> I just installed Raid Level-1, it seems to run fine, I can start it, mount
> it, transfer files, etc..
>
> however, the riad gets autodetected, started and the STOPPED at boot time,
> after the entire boot process is over and I'm logged in I can start and
> mount it manually, but for whatever I try it won't be mounted at boot
> time, here is the the log of the message:
>
> ay 28 14:44:41 narixa kernel: autorun ...
> May 28 14:44:41 narixa kernel: considering sdb3 ...
> May 28 14:44:41 narixa kernel: adding sdb3 ...
> May 28 14:44:41 narixa kernel: adding sda3 ...
> May 28 14:44:41 narixa kernel: created md0
> May 28 14:44:41 narixa kernel: bind<sda3,1>
> May 28 14:44:41 narixa kernel: bind<sdb3,2>
> May 28 14:44:41 narixa kernel: running: <sdb3><sda3>
> May 28 14:44:41 narixa kernel: now!
> May 28 14:44:41 narixa kernel: sdb3's event counter: 00000002
> May 28 14:44:41 narixa kernel: sda3's event counter: 00000002
> May 28 14:44:41 narixa kernel: kmod: failed to exec /sbin/modprobe -s -k
> md-personality-3, errno = 2
> May 28 14:44:41 narixa kernel: do_md_run() returned -22
> May 28 14:44:41 narixa kernel: unbind<sdb3,1>
> May 28 14:44:41 narixa kernel: export_rdev(sdb3)
> May 28 14:44:41 narixa kernel: unbind<sda3,0>
> May 28 14:44:41 narixa kernel: export_rdev(sda3)
> May 28 14:44:41 narixa kernel: md0 stopped.
> May 28 14:44:41 narixa kernel: ... autorun DONE.
>
>
> I'm very frustrated since I can't figure this out, any help would be
> apreciated, thank you very much in advance.
>
> Ralf R. Kotowski
>
>
>
