linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arshavir Grigorian <ag@m-cam.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0+1
Date: Wed, 16 Mar 2005 15:31:09 -0500	[thread overview]
Message-ID: <4238978D.5090809@m-cam.com> (raw)
In-Reply-To: <4238879D.7040608@m-cam.com>

Arshavir Grigorian wrote:
> Hi,
> 
> I have a RAID1+0 array. During boot time, RAID1 arrays get correctly 
> detected and activated. But RAID0 fails to come up. I am guessing the 
> reason the RAID0 cannot be autodetected is that it's built on other md 
> devices and not a physical disk. Anyone knows how to get around this?
> 
> I am using Debian Sarge with mdadm -v1.9.0 running a custom compiled 
> 2.4.27 kernel.

Fixed. The RAID1 devices need to be listed in mdadm.conf as DEVICES in 
addition to the physical disks/partitions.

      reply	other threads:[~2005-03-16 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 19:23 RAID0+1 Arshavir Grigorian
2005-03-16 20:31 ` Arshavir Grigorian [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=4238978D.5090809@m-cam.com \
    --to=ag@m-cam.com \
    --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).