From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: mdraid <linux-raid@vger.kernel.org>
Subject: Re: [SOLVED] Re: Raid1 where Event Count off my 1 cannot assemble --force
Date: Mon, 09 Dec 2013 15:28:54 -0600 [thread overview]
Message-ID: <52A63616.10909@suddenlinkmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312090839360.24602@uplift.swm.pp.se>
On 12/09/2013 01:40 AM, Mikael Abrahamsson wrote:
>> But yes, it doesn't hurt to add it to a wiki page somewhere.
>
> I added this text to the wiki:
>
> "There are bugs in older versions of mdadm, and a lot of "stable" operating
> system releases ship with really old mdadm versions. Recent versions are 3.2.x
> and 3.3.x. It's advisable if you run into problems assembling your raid to
> upgrade to the latest git version of mdadm. If you can get the raid to
> successfully assemble and recover with the git version, then it's fine to use
> your old mdadm version again for normal system operation. Newer mdadm doesn't
> make any changes to the array that isn't backwards compatible."
That ought to help the dummies out...
As follow-up and confirmation of the help statement. I can confirm that after
repairing my arrays under mdadm 3.3.2, I was able to reboot and have the arrays
assemble and run with mdadm 2.6.4 without any issue. (good thing since the
problem was on the / partitions...)
Now I just have to back-port mdadm-master to build and run on openSuSE 11.0
when the closest thing I can find is an 11.1 src.rpm. (should be close enough)
Thank you again Neil and Mikael for all the help.
--
David C. Rankin, J.D.,P.E.
prev parent reply other threads:[~2013-12-09 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 10:18 Raid1 where Event Count off my 1 cannot assemble --force David C. Rankin
2013-12-08 10:57 ` Mikael Abrahamsson
2013-12-08 17:57 ` David C. Rankin
2013-12-09 0:38 ` David C. Rankin
2013-12-09 0:52 ` Adam Goryachev
2013-12-09 2:38 ` David C. Rankin
2013-12-09 3:12 ` Adam Goryachev
2013-12-09 3:40 ` David C. Rankin
2013-12-09 1:00 ` NeilBrown
2013-12-09 4:28 ` David C. Rankin
2013-12-09 4:46 ` NeilBrown
2013-12-09 5:20 ` [SOLVED] " David C. Rankin
2013-12-09 5:40 ` NeilBrown
2013-12-09 7:40 ` Mikael Abrahamsson
2013-12-09 21:28 ` David C. Rankin [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=52A63616.10909@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.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.