From: Jeff Johnson <jeff.johnson@aeoncomputing.com>
To: linux-raid@vger.kernel.org
Subject: Re: 20 drive raid-10, CentOS5.5, after reboot assemble fails - all drives "non-fresh"
Date: Sun, 07 Aug 2011 22:55:21 -0700 [thread overview]
Message-ID: <4E3F7A49.9000803@aeoncomputing.com> (raw)
In-Reply-To: <4E3F6E4D.1010502@gmail.com>
Joe / et-al,
The '--assemble --update=uuid' appears to have done the trick. It is
weird because the uuid in the config file matched the uuid of the raid
volume shown with 'mdadm -D /dev/md3' and the uuid on each of the drives
shown with 'mdadm -E /dev/sdc1'
The '--update=summaries' did not work. Assigning a new random uuid
appears to have repaired whatever bit in the superblock was mucked up.
Strange...
Joe, thanks for your help. Find me at SC11, I'm buying you beers.
--Jeff
On 8/7/11 10:04 PM, Joe Landman wrote:
>> Maybe '--update=uuid' ??
>
>
> It looks like it correctly finds /dev/sd[c-z]1 as elements of /dev/md3
>
> Which mdadm are you using?
>
> mdadm -V
>
> and which kernel?
>
> Try the UUID update, and let us know if it helps. Also if your mdadm
> is old (2.6.x), try updating to 3.1.x.
>
> FWIW: we've found problems in the past with Centos 5.4 to 5.5 kernels
> with MD arrays. Often times our only real solution would be to update
> the full OS on the boot drives. This is for distro specific kernels.
> For our kernels, we don't run into this issue.
>
>
--
------------------------------
Jeff Johnson
Manager
Aeon Computing
jeff.johnson "at" aeoncomputing.com
www.aeoncomputing.com
t: 858-412-3810 x101 f: 858-412-3845
4905 Morena Boulevard, Suite 1313 - San Diego, CA 92117
next prev parent reply other threads:[~2011-08-08 5:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 2:37 20 drive raid-10, CentOS5.5, after reboot assemble fails - all drives "non-fresh" Jeff Johnson
2011-08-08 2:56 ` NeilBrown
2011-08-08 4:32 ` Jeff Johnson
2011-08-08 4:40 ` Joe Landman
2011-08-08 4:54 ` Jeff Johnson
2011-08-08 5:04 ` Joe Landman
2011-08-08 5:55 ` Jeff Johnson [this message]
2011-08-08 16:17 ` Joe Landman
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=4E3F7A49.9000803@aeoncomputing.com \
--to=jeff.johnson@aeoncomputing.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 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.