From: Phil Turmel <philip@turmel.org>
To: tyranastrasz@gmx.de, antlists <antlists@youngman.org.uk>,
linux-raid@vger.kernel.org, NeilBrown <neilb@suse.com>
Subject: Re: Restoring a raid0 for data rescue
Date: Sun, 2 Aug 2020 22:55:37 -0400 [thread overview]
Message-ID: <811f84cf-62e1-f8e0-b120-60f7369e3774@turmel.org> (raw)
In-Reply-To: <84492bfd-8a1b-6109-fb3f-a32ce25e740d@gmx.de>
On 8/2/20 8:46 PM, tyranastrasz@gmx.de wrote:
> On 02.08.20 22:50, antlists wrote:
>>>> No, I have the disks in my pc.
>>>> The server can't boot the disks because Intel Storage says the raid has
>>>> a failure, because one of the disks has no raid information. But as I
>>>> read them both yesterday they had, now (see the last attachment) one of
>>>> them has none.
>>>> It makes no sense... I need the files
>>>>
>>>> Intel means "yeah make a new raid, with data loss" that's no option.
>>>>
>>>> Nara
>>>
>>>
>>> I tried something what was told here
>>> https://askubuntu.com/questions/69086/mdadm-superblock-recovery
>>>
>>> root@Nibler:~# mdadm --create /dev/md0 -v -f -l 0 -c 128 -n 2 /dev/sdd
>>> /dev/sdb
>>
>> OH SHIT !!!
>>
>> You didn't try booting with a rescue disk? That mistake could well cost
>> you the array :-( I'm out of my depth ...
>>
>> https://raid.wiki.kernel.org/index.php/Linux_Raid
>> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
>>
>> I've called in the heavy cavalry, and fortunately with 1.2 the damage
>> might not be too bad.
>>
>> Here's hoping,
>> Wol
>
> What do you mean with 1.2?
>
> Should I do?
> https://raid.wiki.kernel.org/index.php/Recovering_a_damaged_RAID
>
> I wait for an answer so I do it not more complicated :/
> But is it not possible to merge both disks together into a virtual one,
> block by block?
> Our put the old superblock back?
>
> I dunno what's the best solution.
>
> Thanks
> Nara
Oy. I don't mind being called a "big gun", but I've zero experience
with IMSM / software raid combinations. Not even a sparkler for you, sorry.
I avoid any form of "fakeraid" as too dangerous to play with. I
understand it is necessary if you wish to dual boot windows and linux on
the same raid, but I don't do the former at all any more (no bare metal
windows in my life for over a decade, now).
):
Phil
next prev parent reply other threads:[~2020-08-03 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1726630AbgHBR6v/20200802175851Z+2001@vger.kernel.org>
2020-08-02 18:09 ` Restoring a raid0 for data rescue tyranastrasz
2020-08-02 19:01 ` antlists
2020-08-02 19:24 ` tyranastrasz
2020-08-02 20:38 ` tyranastrasz
2020-08-02 20:50 ` antlists
2020-08-03 0:46 ` tyranastrasz
2020-08-03 2:55 ` Phil Turmel [this message]
2020-08-03 4:37 ` NeilBrown
2020-08-04 0:51 ` tyranastrasz
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=811f84cf-62e1-f8e0-b120-60f7369e3774@turmel.org \
--to=philip@turmel.org \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=tyranastrasz@gmx.de \
/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.