From: Carlos Maziero <carlos.maziero@gmail.com>
To: Leslie Rhorer <lesrhorer@att.net>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recover from crash in RAID6 due to hardware failure
Date: Tue, 15 Jun 2021 08:28:06 -0300 [thread overview]
Message-ID: <de1f0636-c194-4cf3-c464-589b78186fa0@gmail.com> (raw)
In-Reply-To: <f07a1c5e-b2ed-cff6-e4e3-1f4956a68c3d@att.net>
Hi Leslie,
thanks for your suggestion! I succeeded to do it, although the path was
a bit longer:
a) remove logical volume (synology creates one, it prevents stopping the
array):
# ll /dev/mapper/
crw------- 1 root root 10, 59 Sep 5 2020 control
brw------- 1 root root 253, 0 Jun 10 11:57 vol1-origin
# dmsetup remove vol1-origin
b) stop the array:
# mdadm --stop /dev/md2
mdadm: stopped /dev/md2
c) recreate the array with the original layout:
# mdadm --verbose --create /dev/md2 --chunk=64 --level=6
--raid-devices=5 --metadata=1.2 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
/dev/sde3
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sda3 appears to be part of a raid array:
level=raid6 devices=5 ctime=Sat Sep 5 12:46:57 2020
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdb3 appears to be part of a raid array:
level=raid6 devices=5 ctime=Sat Sep 5 12:46:57 2020
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdc3 appears to be part of a raid array:
level=raid6 devices=5 ctime=Sat Sep 5 12:46:57 2020
mdadm: layout defaults to left-symmetric
mdadm: /dev/sdd3 appears to be part of a raid array:
level=raid6 devices=5 ctime=Sat Sep 5 12:46:57 2020
mdadm: layout defaults to left-symmetric
mdadm: /dev/sde3 appears to be part of a raid array:
level=raid6 devices=5 ctime=Sat Sep 5 12:46:57 2020
mdadm: size set to 2925544256K
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md2 started.
d) checking it:
# cat /proc/mdstat
Personalities : [raid1] [linear] [raid0] [raid10] [raid6] [raid5] [raid4]
md2 : active raid6 sde3[4] sdd3[3] sdc3[2] sdb3[1] sda3[0]
8776632768 blocks super 1.2 level 6, 64k chunk, algorithm 2 [5/5]
[UUUUU]
[=>...................] resync = 6.8% (199953972/2925544256)
finish=2440.4min speed=18613K/sec
md1 : active raid1 sda2[1] sdb2[2] sdc2[3] sdd2[0] sde2[4]
2097088 blocks [5/5] [UUUUU]
md0 : active raid1 sdc1[3] sdd1[0] sde1[4]
2490176 blocks [5/3] [U__UU]
unused devices: <none>
After that, I fsck'ed and mounted it read-only, and now I'm happy
recovering my data... :-)
Thanks again!
Carlos
Em 14/06/2021 22:36, Leslie Rhorer escreveu:
> Oops! 'Sorry. That should be:
>
> mdadm -S /dev/md2
> mdadm -C -f -e 1.2 -n 5 -c 64K --level=6 -p left-symmetric /dev/md2
> /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3
>
>
> You only have five disks, not six.
>
prev parent reply other threads:[~2021-06-15 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 3:07 Recover from crash in RAID6 due to hardware failure Carlos Maziero
[not found] ` <4745ddd9-291b-00c7-8678-cac14905c188@att.net>
[not found] ` <ed21aa89-e6a1-651d-cc23-9f4c72cf63e0@gmail.com>
2021-06-15 1:33 ` Leslie Rhorer
2021-06-15 1:36 ` Leslie Rhorer
2021-06-15 7:46 ` Roman Mamedov
2021-06-15 11:28 ` Carlos Maziero [this message]
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=de1f0636-c194-4cf3-c464-589b78186fa0@gmail.com \
--to=carlos.maziero@gmail.com \
--cc=lesrhorer@att.net \
--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