All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin ESTRABAUD <be@mpstor.com>
To: "L. M. J" <linuxmasterjedi@free.fr>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Broken raid 5
Date: Fri, 23 May 2014 10:50:02 +0100	[thread overview]
Message-ID: <537F19CA.30704@mpstor.com> (raw)
In-Reply-To: <01734799-2b9f-4ab5-8be2-9f6dc928379f@email.android.com>

On 22/05/14 19:49, L. M. J wrote:
> On 22 mai 2014 13:16:20 CEST, Benjamin ESTRABAUD <be@mpstor.com> wrote:
>> On 21/05/14 23:05, L. M. J wrote:
>>> Hi,
>>>
>>>    Very short story : I've created an array on top of another one,
>> I presume that you actually mean that you created an array ontop of the
>>
>> disks from another array.
>>
>>   so I lost my array and my data.
>>>
>>>    Is there à way to recover RAID 5 meta data on each disk to be able
>> to rebuilt the previous raid 5?
>>>
>> Well, if you used the same metadata version (like 1.2 for instance),
>> the
>> "old" metadata would have been overwritten by your new RAID metadata
>> (assuming you built the RAID on the same drives/partitions) so that
>> would be gone as well.
>>
>> Even if you were able to rebuild the "previous" RAID (also assuming it
>> was a RAID5), if your current RAID build has completed the data would
>> have been thoroughly destroyed by the build process and recovery would
>> be insanely hard.
>>
>>> Thabks
>>>
>>
>> Regards,
>> Ben.
>
> Strange, answer 1 seems different speech, have a look : http://serverfault.com/questions/499051/mdadm-mdadm-cannot-open-dev-sda1-device-or-resource-busy
>
Hi,

I'm not sure this SO question (how to create a RAID10 with the contents 
from one drive) relates to your problem. The first answer is about 
creating a RAID10 with a device missing (the device that currently holds 
the data), formatting the RAID so that the data from the "missing" RAID 
device can first be copied, and then adding the data to the RAID. This 
is to avoid having to copy any data to an intermediate drive when 
reusing a drive (with valid data) to create a RAID.

Regards,
Ben.

> Thanks
>

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-05-23  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 22:05 Broken raid 5 L. M. J
2014-05-22 11:16 ` Benjamin ESTRABAUD
     [not found]   ` <01734799-2b9f-4ab5-8be2-9f6dc928379f@email.android.com>
2014-05-23  9:50     ` Benjamin ESTRABAUD [this message]

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=537F19CA.30704@mpstor.com \
    --to=be@mpstor.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=linuxmasterjedi@free.fr \
    /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.