From: tyranastrasz@gmx.de
To: antlists <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: Re: Restoring a raid0 for data rescue
Date: Sun, 2 Aug 2020 21:24:18 +0200 [thread overview]
Message-ID: <d8f9d16d-b6a2-77ba-bff2-a56c62dac5df@gmx.de> (raw)
In-Reply-To: <7437ab4d-9cd1-fe53-a17a-fc9e966ccd92@youngman.org.uk>
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
next prev parent reply other threads:[~2020-08-02 19:24 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 [this message]
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
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=d8f9d16d-b6a2-77ba-bff2-a56c62dac5df@gmx.de \
--to=tyranastrasz@gmx.de \
--cc=antlists@youngman.org.uk \
--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