From: Evgeny Koryanov <evgeny.koryanov@maris.no>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Raid recovery. Help wanted!
Date: Sun, 21 Apr 2013 20:16:54 +0400 [thread overview]
Message-ID: <517410F6.8050605@maris.no> (raw)
Hello everybody!
Yesterday I met a problem with one of raid5 arrays build by mdadm on
three (sd[bcd]) 1.5T devices.
I found array in degraded state with sdd fail. Drive becomes fail state
after power jump.
Server supplied by UPS but this seems was not good enough - server was
not rebooted but one drive as I said becomes fail state.
I simply reattaches it and array started rebuilding but fails after
couple of %'s passed with sdc becomes fail!!!
I assemble array again with sd[bc] and tried to attach sdd again:
picture repeated rebuild fails.
So I have sdb in sync state, sdc - failed and sdd spare. I checked
SMARTs of drives to understand reason of such behavior and
found it clean on all devices. Than I tried to dd if=/dev/sd[bcd]
of=/dev/null and found that dd also fails with IO error.
After dd bad blocks started appears in SMART :)
Finally I have:
sdb - sync
sdc - fail
sdd - spare
states and a number of bads on each hdd in random places...
Could any one suggest how can I assemble this array now in read-only
mode to try to copy data?!
Theoretically data on sdd should not be rewritten and it still should be
possible to try recover data (meaning that bads appears in quite
different places)...
May be you know utility which helps recover data or the way how to start
array in read-only mode preventing becomes it to degraded state
and force md device to try recover data using readable places from each
devise???
Or any other ideas appreciated! Thanks, any way...
Best regards,
Evgeny.
next reply other threads:[~2013-04-21 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 16:16 Evgeny Koryanov [this message]
2013-04-21 16:40 ` Raid recovery. Help wanted! Mathias Burén
2013-04-21 17:27 ` Evgeny Koryanov
2013-04-21 23:37 ` Sam Bingner
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=517410F6.8050605@maris.no \
--to=evgeny.koryanov@maris.no \
--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