From: John Yates <jyates65@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Advice recovering from interrupted grow on RAID5 array
Date: Wed, 16 Oct 2013 09:02:52 -0400 [thread overview]
Message-ID: <CA+90J_9vLnEVPhAkQmZ5VS=gTw0fjf107wf=2riLn+=RstJMSQ@mail.gmail.com> (raw)
In-Reply-To: <20131016162625.628c5558@notabene.brown>
On Wed, Oct 16, 2013 at 1:26 AM, NeilBrown <neilb@suse.de> wrote:
> 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
Yes I did, thanks. Not much change though. It accepts the timestamp,
but then appears not to use it.
mdadm --assemble /dev/md127 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
/dev/sdf1 /dev/sdg1 --verbose
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb1 is identified as a member of /dev/md127, slot 4.
mdadm: /dev/sdc1 is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdd1 is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sde1 is identified as a member of /dev/md127, slot 0.
mdadm: /dev/sdf1 is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdg1 is identified as a member of /dev/md127, slot 5.
mdadm: :/dev/md127 has an active reshape - checking if critical
section needs to be restored
mdadm: accepting backup with timestamp 1381360844 for array with
timestamp 1381729948
mdadm: backup-metadata found on device-5 but is not needed
mdadm: added /dev/sdf1 to /dev/md127 as 1
mdadm: added /dev/sdd1 to /dev/md127 as 2
mdadm: added /dev/sdc1 to /dev/md127 as 3
mdadm: added /dev/sdb1 to /dev/md127 as 4 (possibly out of date)
mdadm: added /dev/sdg1 to /dev/md127 as 5 (possibly out of date)
mdadm: added /dev/sde1 to /dev/md127 as 0
mdadm: /dev/md127 assembled from 4 drives - not enough to start the array.
next prev parent reply other threads:[~2013-10-16 13:02 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
2013-10-16 13:02 ` John Yates [this message]
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='CA+90J_9vLnEVPhAkQmZ5VS=gTw0fjf107wf=2riLn+=RstJMSQ@mail.gmail.com' \
--to=jyates65@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).