Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Darko Luketic <darko@luketic.de>
To: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: RAID10 with 2 drives auto-assembled as RAID1
Date: Mon, 7 Nov 2016 18:13:57 +0100	[thread overview]
Message-ID: <27046c36-09a3-821f-059b-acaa578972b9@luketic.de> (raw)
In-Reply-To: <c2c0659b-9dd6-1f5f-9309-8a47ea3400f4@turmel.org>

On 11/07/2016 02:49 PM, Phil Turmel wrote:
> Good morning,
>
Good morning Phil

> On 11/07/2016 08:36 AM, Darko Luketic wrote:
>> On 11/05/2016 11:54 PM, Phil Turmel wrote:
>>>  Assuming you had an ext2/3/4 filesystem in the array, try this
>>> one-liner:
>>>
>>> for x in /dev/sd[ef]1; do echo -e "\nDevice $x"; dd if=$x bs=1M
>>> count=16k |hexdump -C |egrep '^[0-9a-f]+30  .+  53 ef'; done
>
>> There are many lines of output.
>> Meanwhile I went the commercial route. Managed so save all important
>> stuff but the software (rdata product version 6 for Windows) didn't do
>> it properly.
>> I'll have to start a new restore.
>> I also used a free product for gnu/linux called R-Linux which is able to
>> find most dirs and files but hangs at 1.03TB and is unable to find the
>> most important .thunderbird dir .
>> Also tried sleuthkit with autopsy2 without success.
>
> Ok.
>
>> For now I can cope with the 128GB ssd as a temporary solution, but life
>> must go on and in the long run I need more space and to use the drives.
>>
>> What was I searching for with this chain of commands?
>
> Magic number for an ext2/3/4 filesystem at a suitable offset within a
> sector.
>
>> Device /dev/sde1
>> 07f00430  b5 9b 1c 58 7a 02 ff ff  53 ef 01 00 01 00 00 00
>> |...Xz...S.......|
>
> This is a candidate, with a last write timestamp of Fri, 04 Nov 2016
> 14:31:17 GMT.
>
>
>> 0ff00030  c4 36 78 52 00 00 ff ff  53 ef 00 00 01 00 00 00
>> |.6xR....S.......|
>
> And another candidate with a last write @ Tue, 05 Nov 2013 00:07:32 GMT.
>
>> 1ff00030  c4 36 78 52 00 00 ff ff  53 ef 00 00 01 00 00 00
>> |.6xR....S.......|
>
> And this one appears to be a backup superblock for the 2013 filesystem.
> The spacing between these two make me wonder if they are both backups
> for a superblock that's been overwritten.
>
> I'd suggest sharing these emails with the Ext4 mailing list to see if
> you can get some more specific recovery help.  I'd say the odds are fair
> to good.
>
> Phil

Yes (probably) the array was created in 2013.

Thank you so much for your help Phil.

Darko

      reply	other threads:[~2016-11-07 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 14:10 RAID10 with 2 drives auto-assembled as RAID1 Darko Luketic
2016-11-05 20:20 ` Phil Turmel
2016-11-05 21:10   ` Darko Luketic
2016-11-05 22:54     ` Phil Turmel
     [not found]       ` <904643ba-b712-0c8a-249d-a78e7fc68876@luketic.de>
2016-11-07 13:49         ` Phil Turmel
2016-11-07 17:13           ` Darko Luketic [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=27046c36-09a3-821f-059b-acaa578972b9@luketic.de \
    --to=darko@luketic.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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