From: Phil Turmel <philip@turmel.org>
To: Andrew Wilkins <andrew.m.wilkins@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Help Reassembling a raid5 array
Date: Mon, 7 Dec 2015 22:40:25 -0500 [thread overview]
Message-ID: <56665129.6050404@turmel.org> (raw)
In-Reply-To: <CAJGWEk93QAmCdik4_rxGPcq7dm=2tXX1U19Zkn5OwcAog0Z-RA@mail.gmail.com>
Hi Andrew,
On 12/07/2015 08:26 PM, Andrew Wilkins wrote:
> Hi, please can someone help me with a raid array which as gone wrong
> On Friday a backup server was rebooted, but failed to boot, possibly
> with an unrelated issue
>
>
> On Monday someone booted from a usb disk to try and recover it
> they were originally able to assemble the array but now they are not,
> 2 out of the 5 drives are showing out of date.
> Device 1 is showing
> Bad Block Log : 512 entries available at offset 72 sectors
> Array State : AAAAA
> and is showing 256 less a events
> last updated 2 hours before the others
>
> Device 4 is showing
> Array State : A.AAA
> and 2 less events
> last update 1 hour before the others
>
> The rest all show
> Array State : A.AA.
>
> I've tried manually assembling without device 1, but even with --force
> it refused to assemble, force seems to do nothing at all, i am
> assuming this maybe because the array state has been updated to say
> missing for 2 devices.
> The example here
> https://raid.wiki.kernel.org/index.php/RAID_Recovery
> seems to suggest that in my situation recreating might be my only option
Possibly. Let's try all other options first.
> Are there any better options before i go ahead and do this?
At least one anomaly below.
> /dev/sdb1:
> Array UUID : 7847e506:deaf87e5:7c6cd502:abb20cf1
> /dev/sdc1:
> Array UUID : xxxxxxxx:xxxxxxxx:xxxxxxxx:abb20cf1
How did this happen ? ^^^^^^^^^^^^^^^^^^^^^^
> /dev/sdd1:
> Array UUID : 7847e506:deaf87e5:7c6cd502:abb20cf1
> /dev/sde1:
> Array UUID : 7847e506:deaf87e5:7c6cd502:abb20cf1
> /dev/sdf1:
> Array UUID : 7847e506:deaf87e5:7c6cd502:abb20cf1
Try forcing re-assembly with sdb1, sdd1, sde1, and sdf1.
If that doesn't work with your current environment, try again with new
kernel and mdadm from booting a rescue environment. I usually recommend
the LiveCD from sysrescuecd.org.
If that succeeds (in either case), add sdc1 and let it rebuild before
doing anything else.
Phil
next prev parent reply other threads:[~2015-12-08 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 1:26 Help Reassembling a raid5 array Andrew Wilkins
2015-12-08 3:40 ` Phil Turmel [this message]
2015-12-08 5:02 ` Andrew Wilkins
[not found] ` <CAJGWEk-UovYPJcyCOhUNO4XahraB_9E5QriObJe+S6uVT_Rs1g@mail.gmail.com>
2015-12-08 19:48 ` Phil Turmel
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=56665129.6050404@turmel.org \
--to=philip@turmel.org \
--cc=andrew.m.wilkins@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).