All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Mike Garey <random51k@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Can't mount /dev/md0 after stopping a synchronization
Date: Wed, 05 Apr 2006 13:24:44 -0400	[thread overview]
Message-ID: <4433FD5C.1050109@steeleye.com> (raw)
In-Reply-To: <c79e949d0604050839k2287fefdm53f6abb08dfcae89@mail.gmail.com>

Mike Garey wrote:

> I seem to be getting closer.. If I try booting from a kernel without
> raid1 and md support, but using an initrd with raid1/md modules, then
> I get the "ALERT! /dev/md0 does not exist.  Dropping to a shell!"
> message.  I can't understand why there would be any difference between
> using a kernel with raid1/md support, or using an initrd image with
> raid1/md support, but apparently there is.  If anyone else has any

Autodetection doesn't occur unless md is built into the kernel -- one of 
the reasons why using autodetection is becoming less and less popular. 
You're probably better off assembling the array from your initrd with 
some invocation of mdadm.

--
Paul

  parent reply	other threads:[~2006-04-05 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  3:45 Can't mount /dev/md0 after stopping a synchronization Mike Garey
2006-04-05 15:21 ` Troels Bang Jensen
2006-04-05 15:39   ` Mike Garey
2006-04-05 16:20     ` Tuomas Leikola
2006-04-05 16:59       ` Mike Garey
2006-04-07 13:17         ` Tuomas Leikola
2006-04-08 15:45           ` Mike Garey
2006-04-09 20:48             ` Tuomas Leikola
2006-04-05 17:24     ` Paul Clements [this message]
2006-04-06  4:32       ` Mike Garey
  -- strict thread matches above, loose matches on Subject: below --
2006-04-04 19:25 Mike Garey

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=4433FD5C.1050109@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=random51k@gmail.com \
    /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 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.