* RAID md-personality
@ 2003-07-11 6:46 Mikael Chambon
2003-07-11 13:31 ` Paul Clements
0 siblings, 1 reply; 2+ messages in thread
From: Mikael Chambon @ 2003-07-11 6:46 UTC (permalink / raw)
To: linux-raid
Hi All,
I am quite new to RAID (please forgive if my questions are stupid) and
I tried to read almost all papers (HOW-TO) that I was able to find on
tldp.org
but I still have some questions, I will split them in different emails.
I would really appreciate if someone could answer my questions or if someone
could
give me a good link. For this setup I am using a RH 7.3 with a 2.4.20-18.7
kernel.
1) During boot time, when md is trying to autodetect a RAID array before the
root
filesystem is mounted, I get the following error when kmod
is trying to load md-personality (someone know what this module is for ?).
=========
Jul 9 15:28:29 mekare kernel: md: md driver 0.90.0 MAX_MD_DEVS=256,
MD_SB_DISKS=27
Jul 9 15:28:29 mekare kernel: md: Autodetecting RAID arrays.
Jul 9 15:28:29 mekare kernel: [events: 00000004]
Jul 9 15:28:29 mekare kernel: [events: 00000004]
Jul 9 15:28:29 mekare kernel: md: autorun ...
Jul 9 15:28:29 mekare kernel: md: considering hdc1 ...
Jul 9 15:28:29 mekare kernel: md: adding hdc1 ...
Jul 9 15:28:29 mekare kernel: md: adding hda8 ...
Jul 9 15:28:29 mekare kernel: md: created md0
Jul 9 15:28:29 mekare kernel: md: bind<hda8,1>
Jul 9 15:28:29 mekare kernel: md: bind<hdc1,2>
Jul 9 15:28:29 mekare kernel: md: running: <hdc1><hda8>
Jul 9 15:28:29 mekare kernel: md: hdc1's event counter: 00000004
Jul 9 15:28:29 mekare kernel: md: hda8's event counter: 00000004
Jul 9 15:28:29 mekare kernel: md: md0: raid array is not clean -- starting
background reconstruction
Jul 9 15:28:29 mekare kernel: md: RAID level 1 does not need chunksize!
Continuing anyway.
Jul 9 15:28:29 mekare kernel: kmod: failed to exec /sbin/modprobe -s -k
md-personality-3, errno = 2
Jul 9 15:28:29 mekare kernel: md: personality 3 is not loaded!
==========
- I can' find this module anywhere.
- I have tried to include the raid1 module in the RAMDISK using mkinitrd
but I still have the same error.
- When the root filesystem is mounted, I don't have this error anymore as
you
can see:
=========
Jul 9 15:28:29 mekare kernel: VFS: Mounted root (ext2 filesystem).
Jul 9 15:28:29 mekare kernel: md: raid1 personality registered as nr 3
Jul 9 15:28:29 mekare kernel: Journalled Block Device driver loaded
Jul 9 15:28:29 mekare kernel: md: Autodetecting RAID arrays.
Jul 9 15:28:29 mekare kernel: [events: 00000004]
Jul 9 15:28:29 mekare kernel: [events: 00000004]
Jul 9 15:28:29 mekare kernel: md: autorun ...
Jul 9 15:28:29 mekare kernel: md: considering hda8 ...
Jul 9 15:28:29 mekare kernel: md: adding hda8 ...
Jul 9 15:28:29 mekare kernel: md: adding hdc1 ...
Jul 9 15:28:29 mekare kernel: md: created md0
Jul 9 15:28:29 mekare kernel: md: bind<hdc1,1>
Jul 9 15:28:29 mekare kernel: md: bind<hda8,2>
Jul 9 15:28:29 mekare kernel: md: running: <hda8><hdc1>
Jul 9 15:28:29 mekare kernel: md: hda8's event counter: 00000004
Jul 9 15:28:29 mekare kernel: md: hdc1's event counter: 00000004
Jul 9 15:28:29 mekare kernel: md: md0: raid array is not clean -- starting
background reconstruction
Jul 9 15:28:29 mekare kernel: md: RAID level 1 does not need chunksize!
Continuing anyway.
Jul 9 15:28:29 mekare kernel: md0: max total readahead window set to 508k
Jul 9 15:28:29 mekare kernel: md0: 1 data-disks, max readahead per
data-disk: 508k
Jul 9 15:28:29 mekare kernel: raid1: device hda8 operational as mirror 0
===========
If someone could help me a little.
Thanks.
--
Mikael Chambon
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: RAID md-personality
2003-07-11 6:46 RAID md-personality Mikael Chambon
@ 2003-07-11 13:31 ` Paul Clements
0 siblings, 0 replies; 2+ messages in thread
From: Paul Clements @ 2003-07-11 13:31 UTC (permalink / raw)
To: Mikael Chambon; +Cc: linux-raid
Mikael Chambon wrote:
> 1) During boot time, when md is trying to autodetect a RAID array before the
> root
> filesystem is mounted, I get the following error when kmod
> is trying to load md-personality (someone know what this module is for ?).
This first autorun attempt occurs at md initialization time, before the
initrd is loaded, so there are no modules available. That's why the
failure occurs. This is actually expected behavior for Red Hat and SuSE
installations...more below...
> =========
> Jul 9 15:28:29 mekare kernel: md: md driver 0.90.0 MAX_MD_DEVS=256,
> MD_SB_DISKS=27
> Jul 9 15:28:29 mekare kernel: md: Autodetecting RAID arrays.
> Jul 9 15:28:29 mekare kernel: [events: 00000004]
> Jul 9 15:28:29 mekare kernel: [events: 00000004]
> Jul 9 15:28:29 mekare kernel: md: autorun ...
> Jul 9 15:28:29 mekare kernel: md: considering hdc1 ...
> Jul 9 15:28:29 mekare kernel: md: adding hdc1 ...
> Jul 9 15:28:29 mekare kernel: md: adding hda8 ...
> Jul 9 15:28:29 mekare kernel: md: created md0
> Jul 9 15:28:29 mekare kernel: md: bind<hda8,1>
> Jul 9 15:28:29 mekare kernel: md: bind<hdc1,2>
> Jul 9 15:28:29 mekare kernel: md: running: <hdc1><hda8>
> Jul 9 15:28:29 mekare kernel: md: hdc1's event counter: 00000004
> Jul 9 15:28:29 mekare kernel: md: hda8's event counter: 00000004
> Jul 9 15:28:29 mekare kernel: md: md0: raid array is not clean -- starting
> background reconstruction
> Jul 9 15:28:29 mekare kernel: md: RAID level 1 does not need chunksize!
> Continuing anyway.
> Jul 9 15:28:29 mekare kernel: kmod: failed to exec /sbin/modprobe -s -k
> md-personality-3, errno = 2
> Jul 9 15:28:29 mekare kernel: md: personality 3 is not loaded!
> ==========
> - I can' find this module anywhere.
Look in /etc/modules.conf for an "alias md-personality ..." line.
> - I have tried to include the raid1 module in the RAMDISK using mkinitrd
> but I still have the same error.
Yes, I would expect that.
> - When the root filesystem is mounted, I don't have this error anymore as
> you can see:
>
> =========
> Jul 9 15:28:29 mekare kernel: VFS: Mounted root (ext2 filesystem).
> Jul 9 15:28:29 mekare kernel: md: raid1 personality registered as nr 3
> Jul 9 15:28:29 mekare kernel: Journalled Block Device driver loaded
> Jul 9 15:28:29 mekare kernel: md: Autodetecting RAID arrays.
> Jul 9 15:28:29 mekare kernel: [events: 00000004]
> Jul 9 15:28:29 mekare kernel: [events: 00000004]
> Jul 9 15:28:29 mekare kernel: md: autorun ...
> Jul 9 15:28:29 mekare kernel: md: considering hda8 ...
> Jul 9 15:28:29 mekare kernel: md: adding hda8 ...
> Jul 9 15:28:29 mekare kernel: md: adding hdc1 ...
> Jul 9 15:28:29 mekare kernel: md: created md0
> Jul 9 15:28:29 mekare kernel: md: bind<hdc1,1>
> Jul 9 15:28:29 mekare kernel: md: bind<hda8,2>
> Jul 9 15:28:29 mekare kernel: md: running: <hda8><hdc1>
> Jul 9 15:28:29 mekare kernel: md: hda8's event counter: 00000004
> Jul 9 15:28:29 mekare kernel: md: hdc1's event counter: 00000004
> Jul 9 15:28:29 mekare kernel: md: md0: raid array is not clean -- starting
> background reconstruction
> Jul 9 15:28:29 mekare kernel: md: RAID level 1 does not need chunksize!
> Continuing anyway.
> Jul 9 15:28:29 mekare kernel: md0: max total readahead window set to 508k
> Jul 9 15:28:29 mekare kernel: md0: 1 data-disks, max readahead per
> data-disk: 508k
> Jul 9 15:28:29 mekare kernel: raid1: device hda8 operational as mirror 0
> ===========
The way that distros (at least Red Hat and SuSE) do this is to let the
initial autorun attempt fail and then, inside the initrd, they load the
necessary raid personality modules, as well as the necessary storage
drivers (in your case IDE is built-in) and then they manually call the
RAID_AUTORUN ioctl of md, to trigger a second autorun. It's sort of
convoluted...
--
Paul
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-07-11 13:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-11 6:46 RAID md-personality Mikael Chambon
2003-07-11 13:31 ` Paul Clements
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.