linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Frotscher <infomails@tronserver.dyndns.org>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 not being reassembled correctly after device swap
Date: Tue, 3 Jul 2007 21:20:25 +0200	[thread overview]
Message-ID: <200707032120.25080.infomails@tronserver.dyndns.org> (raw)
In-Reply-To: <468A98D5.9090206@dgreaves.com>

Hi David,

> Do you have a mdman.conf file that specifies/limits partitions to search?

Just the usual "DEVICE partitons" followed by the ARRAY-lines. However, I 
don't think it's the mdadm.conf, rather the superblocks. Right now my main 
worry is my array which holds the root filesystem. The others I was able to 
resurrect (disks at their original ide ports) using the --update-option when 
assembling. As I cannot do that with the root array (didn't work when I 
booted off a CD), I'm a bit stuck.

When the system starts, it does not even bother to look for a third array 
component but starts the array degraded. I can then "mdadm -a" the third disk 
back into the array, it synchronizes and everything looks good. The same 
thing at the next boot.

Isn't there an option which updates all superblocks on an assembled array 
saying: you partitions are an array and stay an array until your superblock 
is erased or hell freezes over, whichever happens first. Amen.
-- 
YT,
Michael

  reply	other threads:[~2007-07-03 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 21:21 RAID5 not being reassembled correctly after device swap Michael Frotscher
2007-07-01 22:12 ` Neil Brown
2007-07-02  6:35   ` Michael Frotscher
2007-07-02  6:50     ` Michael Frotscher
2007-07-03 17:16 ` Michael Frotscher
2007-07-03 17:22   ` Patrik Jonsson
2007-07-03 18:43   ` David Greaves
2007-07-03 19:20     ` Michael Frotscher [this message]
2007-07-03 19:29     ` Michael Frotscher
2007-07-04  8:45       ` David Greaves
2007-07-04 16:31         ` Michael Frotscher
2007-07-04 13:35       ` Bill Davidsen

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=200707032120.25080.infomails@tronserver.dyndns.org \
    --to=infomails@tronserver.dyndns.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).