linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arthur Britto <ahbritto@iat.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help: Re-assemble raid-5 with inconsistent events.
Date: Sat, 22 Mar 2008 13:14:20 -0700	[thread overview]
Message-ID: <1206216860.10786.12.camel@loss.redstem.com> (raw)
In-Reply-To: <47E54234.3040407@tmr.com>

On Sat, 2008-03-22 at 13:30 -0400, Bill Davidsen wrote: 
> Might I suggest that you
> - back up your mdadm.conf file
> - replace the list of components in the ARRAY description with the UUID 
> of the array
> - change configure to use PARTITIONS and try them all
> - try the assemble with mdadm figuring out what goes where
> 
> Your chances of getting something drastically wrong are lower. You may 
> have to use --force to get the assembly, and should run fsck *with the 
> -n option* first to see what you have.

I was using UUID :)

As you suggested, I changed DEVICES to 'partitions' as that was my
original intent.

Rather than just hope, I looked at the source for mdadm.  A thousand
cheers for open source! =D

And discovered:
-v Would show how partitions were assigned.
    mdadm -v -A /dev/md5 showed all was good.
--force updates the events first thing when assembling.
   Solving my exact issue.

My array is now operational.  And the rest is up to reiserfsck. :/

Thank you so much,

-Arthur



      reply	other threads:[~2008-03-22 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22  2:40 Help: Re-assemble raid-5 with inconsistent events Arthur Britto
2008-03-22 17:30 ` Bill Davidsen
2008-03-22 20:14   ` Arthur Britto [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=1206216860.10786.12.camel@loss.redstem.com \
    --to=ahbritto@iat.com \
    --cc=davidsen@tmr.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).