linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wesley W. Terpstra" <wesley@terpstra.ca>
To: linux-raid@vger.kernel.org
Subject: kernel refuses devices mdadm -E accepts
Date: Tue, 20 Jan 2015 00:01:14 +0100	[thread overview]
Message-ID: <CAA-O0XjoD3fQaMpYYmy4kpBSxD+K9TKX_QGr9mcNVuye43XWHg@mail.gmail.com> (raw)

I have a raid5 array for which every disk, when examined with "mdadm
-E /dev/sd[abcd]4" shows a Version: 1.2 superblock with a valid
checksum.

However, when I try:
mdadm -A /dev/md/backing /dev/sd[abcd]4
mdadm says:
mdadm: failed to add /dev/sdc4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sdb4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sda4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sdd4 to /dev/md/backing: Invalid argument
mdadm: /dev/md/backing assembled from 0 drives - need all 4 to start
it (use --run to insist)
The kernel says:
md: sdc4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdb4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sda4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdd4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22

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.

Thanks for any help. If I lose this array, I am going to face a lot of grief...

             reply	other threads:[~2015-01-19 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:01 Wesley W. Terpstra [this message]
2015-01-19 23:52 ` kernel refuses devices mdadm -E accepts Roger Heflin
2015-01-20 18:28 ` Phil Turmel
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=CAA-O0XjoD3fQaMpYYmy4kpBSxD+K9TKX_QGr9mcNVuye43XWHg@mail.gmail.com \
    --to=wesley@terpstra.ca \
    --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).