* Broken raid 5
@ 2014-05-21 22:05 L. M. J
2014-05-22 11:16 ` Benjamin ESTRABAUD
0 siblings, 1 reply; 3+ messages in thread
From: L. M. J @ 2014-05-21 22:05 UTC (permalink / raw)
To: linux-raid
Hi,
Very short story : I've created an array on top of another one, 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?
Thabks
--
May the open source be with you my young padawan.
Envoyé de mon téléphone, excusez la brièveté.
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Broken raid 5
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>
0 siblings, 1 reply; 3+ messages in thread
From: Benjamin ESTRABAUD @ 2014-05-22 11:16 UTC (permalink / raw)
To: L. M. J, linux-raid
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.
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Broken raid 5
[not found] ` <01734799-2b9f-4ab5-8be2-9f6dc928379f@email.android.com>
@ 2014-05-23 9:50 ` Benjamin ESTRABAUD
0 siblings, 0 replies; 3+ messages in thread
From: Benjamin ESTRABAUD @ 2014-05-23 9:50 UTC (permalink / raw)
To: L. M. J, Linux-RAID
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-23 9:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.