From: Andreas Boman <aboman@midgaard.us>
To: Ole Tange <tange@binf.ku.dk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Failed during rebuild (raid5)
Date: Sun, 05 May 2013 10:00:34 -0400 [thread overview]
Message-ID: <51866602.8000704@midgaard.us> (raw)
In-Reply-To: <CANU9nTneT2CRWJhdN=d87Hb7W9M+apQH+fRE-S+sieZ-W6+hjg@mail.gmail.com>
On 05/03/2013 08:26 AM, Ole Tange wrote:
> On Fri, May 3, 2013 at 1:23 PM, Andreas Boman<aboman@midgaard.us> wrote:
>
>> This morning I came up to see the array degraded with two missing drives,
>> another failed during the rebuild.
> I just started this page for dealing with situations like yours:
> https://raid.wiki.kernel.org/index.php/Recovering_a_failed_software_RAID
>
>
> /Ole
After having ddrescue running all night, it dropped to copying at a rate
of 512B/s. I interrupted it and restarted, it stays at that speed. shows
no errors:
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued: 557052 MB, errsize: 0 B, errors: 0
Current status
rescued: 1493 GB, errsize: 0 B, current rate: 512 B/s
ipos: 937316 MB, errors: 0, average rate: 16431 kB/s
opos: 937316 MB, time from last successful read: 0 s
Copying non-tried blocks...
However that is much too slow...
Then, I decided to take a look at the superblocks and to my horror
discovered this:
# mdadm --examine /dev/sd[b-g] >>raid.status
mdadm: No md superblock detected on /dev/sdb.
mdadm: No md superblock detected on /dev/sdc.
mdadm: No md superblock detected on /dev/sdd.
mdadm: No md superblock detected on /dev/sde.
mdadm: No md superblock detected on /dev/sdf.
mdadm: No md superblock detected on /dev/sdg.
Can I recover still? What is going on here?
Thanks,
Andreas
next prev parent reply other threads:[~2013-05-05 14:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 11:23 Failed during rebuild (raid5) Andreas Boman
2013-05-03 11:38 ` Benjamin ESTRABAUD
2013-05-03 12:40 ` Robin Hill
2013-05-03 13:52 ` John Stoffel
2013-05-03 14:51 ` Phil Turmel
2013-05-03 16:23 ` John Stoffel
2013-05-03 16:32 ` Roman Mamedov
2013-05-04 14:48 ` maurice
2013-05-03 16:29 ` Mikael Abrahamsson
2013-05-03 19:29 ` John Stoffel
2013-05-04 4:14 ` Mikael Abrahamsson
2013-05-03 12:26 ` Ole Tange
2013-05-04 11:29 ` Andreas Boman
2013-05-05 14:00 ` Andreas Boman [this message]
2013-05-05 17:16 ` Andreas Boman
2013-05-06 1:10 ` Sam Bingner
2013-05-06 3:21 ` Phil Turmel
[not found] ` <51878BD0.9010809@midgaard.us>
2013-05-06 12:36 ` Phil Turmel
[not found] ` <5188189D.1060806@midgaard.us>
2013-05-07 0:39 ` Phil Turmel
2013-05-07 1:14 ` Andreas Boman
2013-05-07 1:46 ` Phil Turmel
2013-05-07 2:08 ` Andreas Boman
2013-05-07 2:16 ` Phil Turmel
2013-05-07 2:21 ` Andreas Boman
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=51866602.8000704@midgaard.us \
--to=aboman@midgaard.us \
--cc=linux-raid@vger.kernel.org \
--cc=tange@binf.ku.dk \
/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).