linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Asdo <asdo@shiftmail.org>
To: aragonx@dcsnow.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Several steps to death
Date: Tue, 26 Jan 2010 10:28:29 +0100	[thread overview]
Message-ID: <4B5EB5BD.7070406@shiftmail.org> (raw)
In-Reply-To: <55f050077e86adeb1f4acca87cace12b.squirrel@www.dcsnow.com>

aragonx@dcsnow.com wrote:
> If I try to mount it now, with the correct configuration I get the
> following error:
>
> mdadm --create /dev/md0 --level=5 --spare-devices=0 --raid-devices=5
> /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
>
> ...
>   

I think this is the point where you destroyed your data. Probably the 
devices were not specified in the exact order as before: in this command 
you specified the array with increasing letters order but if you changed 
the mainboard, drives won't be detected in the same order as with the 
old mainboard.

Previously when you thought it was detected as 4 disks + 1 spare, I 
believe instead it was just doing a resync because the array was stale, 
probably the old mainboard broke when it was writing something. Hadn't 
you entered the above --create command, your data would presumably still 
be there. You didn't try mounting it, did you?

At the current state of things, I'm not sure if you can get your data 
out of there.

In theory if you stop the current resync, try to recreate it in all 
possible permutations of 5 drives using --assume-clean during creation 
so to prevent any resyncs (and just mount readonly!) then try mounting 
it or try fsck -n to see if data makes sense, you might be able to get 
data out of it. I have never tried this technique, I read it from a post 
by Neil Brown in this ML, date 12/04/2009 10:12 PM, subject "Re: RAID5 
demise or coma? after re-creating with a spare" try looking for it in 
the archives

  parent reply	other threads:[~2010-01-26  9:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 21:21 Several steps to death aragonx
2010-01-26  1:35 ` Michael Evans
2010-01-26  9:28 ` Asdo [this message]
2010-01-26 13:17   ` aragonx
2010-01-26 13:36     ` Asdo
2010-01-26 14:36       ` aragonx
2010-01-26 14:56         ` Michał Sawicz
2010-01-26 15:07           ` Asdo
2010-01-26 17:48           ` aragonx
2010-01-26 18:12             ` Michał Sawicz
2010-01-26 14:45     ` Kristleifur Daðason

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=4B5EB5BD.7070406@shiftmail.org \
    --to=asdo@shiftmail.org \
    --cc=aragonx@dcsnow.com \
    --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).