All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Semyon Enskiy <semyon.enskiy@yandex.ru>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Recovering RAID5 with 2, actually 1, faulty disks.
Date: Wed, 25 Nov 2015 08:22:55 -0500	[thread overview]
Message-ID: <5655B62F.2070806@turmel.org> (raw)
In-Reply-To: <3822301448453563@web17m.yandex.ru>

On 11/25/2015 07:12 AM, Semyon Enskiy wrote:
> Hi Phil.
> 
> Thanks for your suggestions, I have followed them, but RAID5 at md3 not
> recovered at yet, maybe you will find time to suggest anything else.
> 
> Exactly, power and data connections of SATA disks was not reliable, fixed
> this and after boot get no errors in kernel logs.
> md3 was replaced with "<ingore>" in mdadm.conf and commented in fstab before
> poweroff, things returned back after boot.
> 
>     # mdadm --assemble --update=revert-reshape /dev/md3

This ^^^ is a mistake.  It did nothing because you didn't list all of
the component partitions.  Stop md3 and try this part again.  If it
still doesn't work, add --force.

>     # mdadm --assemble --scan -vv

> Note the difference in --display and --examine outputs (see below) about
> total and delta device numbers, 10 in detail and 11 in examine.

--display is pretty much useless on an inactive array.  The --examine
reports are the ones that matter.

> Also note, that sda3 is marked as "spare" device, I am wrote before in first
> message, that some useless commands was executed.

This is from the --add operation you should not have done.

>     # mdadm --add /dev/md3 --re-add /dev/sda3

Augh!  Don't guess at what to do!  And even if the right thing, the
syntax is wrong (never put --add and --re-add together).

> mdadm: Cannot get array info for /dev/md3
> # This is because array is not started?

Yes.

[trim /]

>     # mdadm --examine /dev/sd?3

[trim /]

Very good, you have device roles 0-7 & 9, plus one spare, matching the
array state.  Put these devices in the --assemble --update command.

>     # for x in /dev/sd[a-z] ; do echo $x ; smartctl -i -A $x ; done

[trim /]

Your drives are entirely healthy.  No apparent lasting effects from the
problem cables/power.

For reference, your drive name to serial numbers to roles:

/dev/sda3 ==> WD-WCC4E1657399 ==> spare
/dev/sdb3 ==> WD-WCC4E1643332 ==> role 6
/dev/sdc3 ==> WD-WCC4E1649141 ==> role 7
/dev/sdd3 ==> WD-WCC4E0340253 ==> role 4
/dev/sde3 ==> WD-WCC4E1658818 ==> role 5
/dev/sdf3 ==> WD-WCC4E1349511 ==> role 0
/dev/sdg3 ==> WD-WCC4E1265787 ==> role 3
/dev/sdh3 ==> WD-WCC4E1639809 ==> role 2
/dev/sdi3 ==> WD-WCC4E1639009 ==> role 1
/dev/sdj3 ==> WD-WCC4E1228884 ==> role 9

Your next operations are:

mdadm --stop /dev/md3

mdadm -v --assemble --update=revert-reshape /dev/md3 /dev/sd[a-i]3

If successful, it should begin rebuilding onto /dev/sda3 (role 8).

If the above fails, repeat with --force.  If that fails show the output
and do nothing else.

Phil

  reply	other threads:[~2015-11-25 13:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 15:28 Recovering RAID5 with 2, actually 1, faulty disks Semyon Enskiy
2015-11-23 15:35 ` Semyon Enskiy
2015-11-23 15:47   ` Wols Lists
2015-11-23 15:57     ` Semyon Enskiy
2015-11-23 16:08       ` Wols Lists
2015-11-23 18:24 ` Phil Turmel
2015-11-25 12:12   ` Semyon Enskiy
2015-11-25 13:22     ` Phil Turmel [this message]
2015-11-25 14:48       ` Semyon Enskiy
2015-11-25 14:55         ` Semyon Enskiy
2015-11-25 15:44           ` Phil Turmel
2015-11-25 16:29             ` Semyon Enskiy
2015-11-25 16:58               ` Phil Turmel
2015-11-25 17:32                 ` Semyon Enskiy
2015-11-25 17:49                   ` Phil Turmel
2015-11-26 13:21                     ` Semyon Enskiy
  -- strict thread matches above, loose matches on Subject: below --
2015-12-02 13:35 Semyon Enskiy

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=5655B62F.2070806@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=semyon.enskiy@yandex.ru \
    /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.