linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: peter pilsl <pilsl@goldfisch.at>
To: linux-raid@vger.kernel.org
Subject: how does autoraid work ?
Date: Tue, 28 Nov 2006 19:59:36 +0100	[thread overview]
Message-ID: <456C8718.2040406@goldfisch.at> (raw)


I've currently a new server (first ubuntu I set up) and I've a problem 
with a raiddevice. While the system itself (/ and /boot) do not use 
raid, a /data-partition is setup as raid1 /dev/md0

Now I'v the problem that md0 is not started during boot, but only late 
when the scripts in rc.d/ are processed for my runlevel. There is a 
script mdadm-raid that actually assemlnbles the raid based on a 
copnfig-file. This is not what I want/need.

On my other servers the raids are autodetected much earlier by the 
kernel or a module much earlier without need of a configfile.

The partitions of my raid are all labeld als linux-autoraid and I can 
manually assemble my raid with mdadm -A -a yes -m 0 /dev/md0, so 
everthing should be fine for the kernel to autostart my raid.

When exactely are the raids supposed to be assembled during boot. Which 
module/script is actually responsible for doing this?  And are there any 
  shots in the dark, why my ubuntu/debian is not doing so?

The raid is on hde and hdf - can this be the problem? that the 
raidmodule/script/whatever does not scan beyond the first two ide-buses?

I tried  raid=autodetect on the bootline but this didnt help either.

I hope I made my self a bit clear and any help is greatly appretiated...

thnx
peter





                 reply	other threads:[~2006-11-28 18:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=456C8718.2040406@goldfisch.at \
    --to=pilsl@goldfisch.at \
    --cc=linux-raid@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).