Re: Restoring a raid0 for data rescue

[antlists <antlists@youngman.org.uk>]

On 02/08/2020 21:38, tyranastrasz@gmx.de wrote:
> On 02.08.20 21:24, tyranastrasz@gmx.de wrote:
>> On 02.08.20 21:01, antlists wrote:
>>> On 02/08/2020 19:09, tyranastrasz@gmx.de wrote:
>>>> Hello
>>>>
>>>> I've a problem with my raid0.
>>>> The probelmatic disks (2x 1TB wdred) were in usage in my server, now
>>>> they got replaced with 3x 4TB seagate in a raid5.
>>>>
>>>> Before I turned them off, I made a backup on an external drive (normal
>>>> hdd via USB) via rsync -avx /source /mnt/external/
>>>>
>>>> Whatever happens in the night, the backup isn't complete and I miss
>>>> files.
>>>> So I put the old raid again into the server and wanted to start, but 
>>>> the
>>>> Intel Raid Controller said that one of the disks are no member of a
>>>> raid.
>>>>
>>>> My server mainboard is from Gigabyte a MX11-PC0.
>>>>
>>>> Well I made some mdadm examines, smartctl, mdstat, lsdrv logfiles and
>>>> attached them to the mail.
>>>>
>>> Ow...
>>>
>>> This is still the same linux on the server? Because mdstat says no raid
>>> personalities are installed. Either linux has changed or you've got
>>> hardware raid. in which case you'll need to read up on the motherboard
>>> manual.
>>>
>>> I'm not sure what they're called, but try "insmod raid1x" I think it is.
>>> Could be raid0x. If that loads the raid0 driver, cat /proc/mdstat should
>>> list raid0 as a personality. Once that's there, mdadm may be able to
>>> start the array.
>>>
>>> Until you've got a working raid driver in the kernel, I certainly can't
>>> help any further. But hopefully reading the mobo manual might help. The
>>> other thing to try is an up-to-date rescue disk and see if that can read
>>> the array.
>>>
>>> Cheers,
>>> Wol
>>
>> 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