linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc L. de Bruin" <marc@debruin.org>
To: dean gaudet <dean@arctic.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: md/mdadm fails to properly run on 2.6.15 after upgrading from 2.6.11
Date: Mon, 10 Apr 2006 20:03:08 +0200	[thread overview]
Message-ID: <443A9DDC.10601@debruin.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604100843370.29514@twinlark.arctic.org>

dean gaudet wrote:
> On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
> 
>> dean gaudet wrote:
>>
>>> initramfs-tools generates an "mdrun /dev" which starts all the raids it can
>>> find... but does not include the mdadm.conf in the initrd so i'm not sure it
>>> will necessarily start them in the right minor devices.  try doing an "mdadm
>>> --examine /dev/xxx" on some of your partitions to see if the "preferred
>>> minor" is what you expect it to be...
>>>  
>> blah@frodo:~# sudo mdadm --examine /dev/md[01234]
> 
> try running it on /dev/sda1 or whatever the component devices are for your 
> array... not on the array devices.
> 
> -dean

Briljant, that turned out to work.

However, all "preferred minor"s are correct, meaning that the output is in 
sync with what I expected it to be from /etc/mdadm/mdadm.conf.

Any other ideas? Just adding /etc/mdadm/mdadm.conf to the initrd does not 
seem to work, since mdrun seems to ignore it?!

Marc.

  reply	other threads:[~2006-04-10 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 12:35 md/mdadm fails to properly run on 2.6.15 after upgrading from 2.6.11 Marc L. de Bruin
2006-04-09 14:46 ` Luca Berra
2006-04-09 14:47 ` dean gaudet
2006-04-10  7:54   ` Marc L. de Bruin
2006-04-10 15:44     ` dean gaudet
2006-04-10 18:03       ` Marc L. de Bruin [this message]
2006-04-10 18:35         ` dean gaudet
2006-04-10 21:05           ` Marc L. de Bruin
2006-04-11 21:13             ` dean gaudet

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=443A9DDC.10601@debruin.org \
    --to=marc@debruin.org \
    --cc=dean@arctic.org \
    --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).