From: sylvain.depuille@laposte.net
To: linux-raid@vger.kernel.org
Subject: Big trouble during reassemble a Raid5
Date: Sun, 28 Dec 2014 13:16:21 +0100 (CET) [thread overview]
Message-ID: <938521225.11264152.1419768981146.JavaMail.zimbra@laposte.net> (raw)
In-Reply-To: <2105542796.11263344.1419768937013.JavaMail.zimbra@laposte.net>
Hello,
i'm sorry to ask this questions but the raid 5 with 4 disk is in big trouble during re-assemble. 2 disks are out of order.
I have change a disk of the raid 5 (sde) to growing the raid.
But a second disk (sdc) have too many bad sector during the re-assemble, and shutdown the re-assemble.
"mdadm --assemble --force /dev/md2 /dev/sd[bcde]1"
I have try to correct bad sectors with badblocks, but it's finished by no more spare sectors and the disk still have some bad sector.
badblocks -b 512 -o badblocks-sdc.txt -v -n /dev/sdc 1140170000 1140169336
1140169400
1140169401
1140169402
1140169403
1140169404
1140169405
1140169406
1140169407
1140169416
1140169417
1140169418
1140169419
1140169420
1140169421
1140169422
1140169423
For information the mdadm examine return :
cat mdadm-exam.txt
/dev/sdb:
MBR Magic : aa55
Partition[0] : 1953523120 sectors at 2048 (type fd)
/dev/sdc:
MBR Magic : aa55
Partition[0] : 1953520002 sectors at 63 (type fd)
/dev/sdd:
MBR Magic : aa55
Partition[0] : 1953520002 sectors at 63 (type fd)
/dev/sde:
MBR Magic : aa55
Partition[0] : 4294965247 sectors at 2048 (type fd)
I have 2 way to solve the issue.
The first, is to have special command to pass bad sector during re-assemble as "mdadm --assemble --force /dev/md2 /dev/sd[bcde]1"
The second is change the disk sde with the old good one, but some datas have been changed on the raid since i have remove it. But these datas are not important. It's only logs and history activity.
What can i do to recover a maximum datas without too many risk?
Thank's in advance
Best Regards
----------------------------------
Sylvain Depuille (in trouble)
sylvain.depuille@laposte.net
next parent reply other threads:[~2014-12-28 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2105542796.11263344.1419768937013.JavaMail.zimbra@laposte.net>
2014-12-28 12:16 ` sylvain.depuille [this message]
2014-12-29 18:32 ` Big trouble during reassemble a Raid5 John Stoffel
[not found] ` <164935924.13594562.1419881845418.JavaMail.zimbra@laposte.net>
2014-12-29 20:36 ` Re : " John Stoffel
2014-12-30 9:37 ` sylvain.depuille
2014-12-30 21:06 ` John Stoffel
2014-12-30 12:44 ` sylvain.depuille
[not found] ` <84D72604-6572-40D9-8861-19B28BBF91B6@laposte.net>
[not found] ` <21667.5112.568800.563410@quad.stoffel.home>
[not found] ` <367813595.16604641.1420034830100.JavaMail.zimbra@laposte.net>
[not found] ` <21668.1236.130012.995660@quad.stoffel.home>
2014-12-31 14:51 ` sylvain.depuille
2014-12-31 16:08 ` John Stoffel
[not found] ` <A6F7476D-8314-480D-B6B5-F84FF1F0960B@laposte.net>
[not found] ` <21668.12775.212408.482021@quad.stoffel.home>
2014-12-31 17:59 ` sylvain.depuille
2014-12-31 19:11 ` John Stoffel
2015-01-01 18:21 ` sylvain.depuille
2015-01-02 4:07 ` John Stoffel
2015-01-02 7:59 ` Can Jeuleers
2015-01-04 18:19 ` sylvain.depuille
2015-01-04 18:16 ` sylvain.depuille
2015-01-01 21:06 ` sylvain.depuille
2015-01-02 4:01 ` John Stoffel
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=938521225.11264152.1419768981146.JavaMail.zimbra@laposte.net \
--to=sylvain.depuille@laposte.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;
as well as URLs for NNTP newsgroup(s).