From: Phil Turmel <philip@turmel.org>
To: "Wesley W. Terpstra" <wesley@terpstra.ca>, linux-raid@vger.kernel.org
Subject: Re: kernel refuses devices mdadm -E accepts
Date: Tue, 20 Jan 2015 13:28:23 -0500 [thread overview]
Message-ID: <54BE9E47.9030706@turmel.org> (raw)
In-Reply-To: <CAA-O0XjoD3fQaMpYYmy4kpBSxD+K9TKX_QGr9mcNVuye43XWHg@mail.gmail.com>
Hi Wesley,
On 01/19/2015 06:01 PM, Wesley W. Terpstra wrote:
> I was in the middle of a reshape of this 4-disk raid5 when something
> rebooted the computer. The system seems otherwise fine, and I suspect
> someone in the house.
>
> What is the correct next step? Should I try --run ? I would obviously
> prefer not to lose the data on this array. I expect that the reshape
> was NOT complete, so just recreating the array will probably corrupt
> its contents.
>
> Kernel version 3.17.8 and mdadm version 3.3.2.
There have been many bug fixes to mdadm since that kernel was retired.
You should temporarily boot a current liveCD (my favorite is
systemrescuecd) and do "mdadm -Afv /dev/mdX /dev/sdX ..."
Show us the output of that if it doesn't work (it should resume your
reshape).
When it is done reshaping/recovering, consider upgrading your kernel.
> Thanks for any help. If I lose this array, I am going to face a lot of grief...
I shouldn't have to say this, but RAID is for availability, not for data
security. You still need a backup system for any important data.
Phil
next prev parent reply other threads:[~2015-01-20 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
2015-01-19 23:52 ` Roger Heflin
2015-01-20 18:28 ` Phil Turmel [this message]
2015-01-20 18:32 ` Phil Turmel
2015-01-20 18:43 ` Wesley W. Terpstra
[not found] ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
2015-01-21 12:37 ` Wesley W. Terpstra
2015-01-20 18:32 ` Wesley W. Terpstra
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=54BE9E47.9030706@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=wesley@terpstra.ca \
/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.