linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Justin Stephenson <justin@evensteveninc.com>, linux-raid@vger.kernel.org
Subject: Re: Reassemble Raid 6
Date: Mon, 10 Feb 2014 18:02:54 -0500	[thread overview]
Message-ID: <52F95A9E.2060805@turmel.org> (raw)
In-Reply-To: <ema2a9c249-212d-4d96-a89b-b8e4a5d9f827@bigg>

On 02/10/2014 07:13 PM, Justin Stephenson wrote:
> Hello Phil,
> 
> You are 100% correct. Thanks for your email. I had 2 separate ARRAY
> entries in my mdadm.config file. When I added the spare, I added the new
> information to the config file but did not remove the old entry. Total
> newbie mistake.
> 
> - I commented out all the previous entries in the mdadm.config file (it
> had a devices lists instead of the UUID information)
> 
> - I successfully assembled the array (mdadm --assemble /dev/md0 
> /dev/sdb1 etc...)
> 
> - I  updated the config file using the information from mdadm -Esc
> partitions | grep UUID and deleted the old entries.
> 
> - I uncommented the fstab entry for the array and rebooted.
> 
> 
> Everything is working perfectly now.
> 
> 
> I remember reading somewhere that mdadm can run without the config file
> by using the RAID uuid and the information in the superblocks. Would
> this be more reliable?
> 
> Thanks Again

You're welcome.

I suggest you trim the mdadm.conf file even further--I only specify name
and uuid, so device changes don't interfere with assembly.  Like so
(slightly edited):

MAILFROM mdadm@example.com
MAILADDR philip@example.com

DEVICE /dev/sd[a-z][1-9]

# Mirrored Boot partitions
ARRAY /dev/md1 UUID=75c011c6:caeb06ea:ec7e3370:aa4f3320

# Far mirror (Raid10) core operations
ARRAY /dev/md2 UUID=6b4858da:f24e2567:34e73fe5:b8f2c118

# Bulk redundant (Raid6) storage
ARRAY /dev/md3 UUID=04f3706c:79a3cd73:8a558eee:93ec1879


HTH,

Phil

ps. Don't forget to update your initramfs after any changes to mdadm.conf!


      reply	other threads:[~2014-02-10 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 16:48 Reassemble Raid 6 Justin Stephenson
2014-02-10 20:53 ` Phil Turmel
2014-02-11  0:13   ` Re[2]: " Justin Stephenson
2014-02-10 23:02     ` Phil Turmel [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=52F95A9E.2060805@turmel.org \
    --to=philip@turmel.org \
    --cc=justin@evensteveninc.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).