From: NeilBrown <neilb@suse.de>
To: John Yates <jyates65@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Advice recovering from interrupted grow on RAID5 array
Date: Wed, 16 Oct 2013 16:26:25 +1100 [thread overview]
Message-ID: <20131016162625.628c5558@notabene.brown> (raw)
In-Reply-To: <CA+90J__=u_m9RW7c9KHGMRr+6ZOSVQUN6yXm61YM_yir-7LE7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Mon, 14 Oct 2013 21:59:45 -0400 John Yates <jyates65@gmail.com> wrote:
> Midway through a RAID5 grow operation from 5 to 6 USB connected
> drives, system logs show that the kernel lost communication with some
> of the drive ports which has left my array in a state that I have not
> been able to reassemble. After reseating the cable connections and
> rebooting, all of the drives appear to be functioning normally, so
> hopefully the data is still intact. I need advice on recovery steps
> for the array.
>
> It appears that each drive failed in quick succession with /dev/sdc1
> being the last standing and having the others marked as missing in its
> superblock. The superblocks of the other drives show all drives as
> available. (--examine output below)
>
> >mdadm --assemble /dev/md127 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1
> mdadm: too-old timestamp on backup-metadata on device-5
> mdadm: If you think it is should be safe, try 'export MDADM_GROW_ALLOW_OLD=1'
> mdadm: /dev/md127 assembled from 1 drives - not enough to start the array.
Did you try following the suggestion and run
export MDADM_GROW_ALLOW_OLD=1
and the try the --asssemble again?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-10-16 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 1:59 Advice recovering from interrupted grow on RAID5 array John Yates
2013-10-16 5:26 ` NeilBrown [this message]
2013-10-16 13:02 ` John Yates
2013-10-17 0:07 ` NeilBrown
2013-10-17 5:36 ` John Yates
2013-10-21 1:09 ` NeilBrown
2013-10-21 16:29 ` John Yates
2013-10-21 20:06 ` John Yates
2013-10-21 22:51 ` NeilBrown
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=20131016162625.628c5558@notabene.brown \
--to=neilb@suse.de \
--cc=jyates65@gmail.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).