From: Phil Turmel <philip@turmel.org>
To: Andreas Boman <aboman@midgaard.us>
Cc: Ole Tange <tange@binf.ku.dk>, linux-raid@vger.kernel.org
Subject: Re: Failed during rebuild (raid5)
Date: Sun, 05 May 2013 23:21:49 -0400 [thread overview]
Message-ID: <518721CD.2040108@turmel.org> (raw)
In-Reply-To: <518693EF.6090802@midgaard.us>
Hi Andreas,
On 05/05/2013 01:16 PM, Andreas Boman wrote:
[trim /]
> Turns out the superblocks are there. I ran --examine on the disk instead
> of partition. OOps.
Please share the "--examine" reports for your array, and "smartctl -x"
for each disk, and anything from dmesg/syslog that relates to your array
or errors on its members. (Your original post did say you would be able
to get log info.)
> I still have the problem with ddrescue being very slow, it is running at
> 512 B/s pretty much no matter what options I use. The ddrescued disk
> does NOT have a md superblock. I tried to ddrescue -i to skip and grab
> the last 3MB or so of the disk, that seemed to work, but I still don't
> have the superblock.
>
> How do I find/recover the superblock from the original disk?
Superblocks are either at/near the beginning of the block device (v1.1 &
v1.2) or near the end (v0.90 and v1.0). If you've already recovered
beginning and end, and it's still not there, then you won't find it.
It may have to be reconstructed as part of "--create --assume-clean",
but that is a dangerous operation. You haven't yet shared enough
information to get good advice.
> After that is done I'll try to get the array up with 4 disks, then add
> the spare and have it rebuild. After that I'll add a disk to go to raid 6.
It may be wiser to get it running degraded and take a backup, but that
remains to be seen. You haven't shown that you know why the first
rebuild failed. Until that is understood and addressed, you probably
won't succeed in rebuilding onto a spare.
Phil
next prev parent reply other threads:[~2013-05-06 3:21 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
2013-05-05 17:16 ` Andreas Boman
2013-05-06 1:10 ` Sam Bingner
2013-05-06 3:21 ` Phil Turmel [this message]
[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=518721CD.2040108@turmel.org \
--to=philip@turmel.org \
--cc=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 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.