mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID autodetection not working when booting with initramfs
Date: Mon, 30 Jan 2006 18:11:03 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601301808180.24345@tassadar.physics.auth.gr> (raw)
In-Reply-To: <17373.20667.838469.977966@cse.unsw.edu.au>


> 	/*
> 	 * check if there is an early userspace init.  If yes, let it do all
> 	 * the work
> 	 */
>
> So yes, it is by design.  Assembling arrays with mdadm gives you a
> lot more control than the kernel-autodetect so as you have an
> initramfs, it is a good idea to make use of it.
>
> If you *really* want to use the autodetect functionality, you can look
> around for a program called 'raidautorun'.  It does triggers the
> autodetect function from userspace.
>

 	Thank you , raidautorun did the trick. I am trying to build an 
initramfs as much generic as possible to be used with hundreds of systems, 
so doing a custom image for every possible raid combination is really not 
an options compared to autodetection.

 	Thnx again,

--
============================================================================

Dimitris Zilaskos

Department of Physics @ Aristotle University of Thessaloniki , Greece
PGP key : http://tassadar.physics.auth.gr/~dzila/pgp_public_key.asc
 	  http://egnatia.ee.auth.gr/~dzila/pgp_public_key.asc
MD5sum  : de2bd8f73d545f0e4caf3096894ad83f  pgp_public_key.asc
============================================================================

      reply	other threads:[~2006-01-30 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 23:13 Dimitris Zilaskos
2006-01-29 23:33 ` Neil Brown
2006-01-30 16:11   ` Dimitris Zilaskos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0601301808180.24345@tassadar.physics.auth.gr \
    --to=dzila@tassadar.physics.auth.gr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®