Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Jorge Nunes <jorgebnunes@gmail.com>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: RAID 1 to RAID 5 failure
Date: Wed, 6 Apr 2022 20:57:10 +0100	[thread overview]
Message-ID: <b9f58b50-3f79-4a81-2f47-0f23a6958e10@youngman.org.uk> (raw)
In-Reply-To: <CANDfL1YiKq9aeUsrmdZyLb5Fy98Tifjcr_zZJY6a+LxyqKYKkA@mail.gmail.com>

On 05/04/2022 11:50, Jorge Nunes wrote:
> Hi roy.
> 
> Thank you for your time.
> 
> Now, I'm doing a photorec on /dev/sda and /dev/sdd and I get better
> results on (some) of the data recovered if I do it on top of /dev/md0.
> I don't care anymore about recovering the filesystem, I just want to
> maximize the quality of data recovered with photorec.

Once you've recovered everything you can, if no-one else has chimed in, 
do try shrinking it back to a 2-disk raid-5. It SHOULD restore your 
original filesystem. You've then just got to find out where it starts - 
what filesystem was it?

If it's an ext4 there's probably a signature which will tell you where 
it starts. Then somebody should be able to tell you how to mount it and 
back it up properly ...

I'm sure there will be clues to other file systems, ask on your distro 
list for more information - the more people who see a request for help, 
the more likely you are to get some.

Cheers,
Wol

  parent reply	other threads:[~2022-04-06 21:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 15:19 RAID 1 to RAID 5 failure Jorge Nunes
2022-04-04 16:42 ` Wols Lists
2022-04-04 17:17   ` Jorge Nunes
2022-04-05  0:29 ` Roy Sigurd Karlsbakk
2022-04-05  9:17   ` Roy Sigurd Karlsbakk
2022-04-05 10:50     ` Jorge Nunes
2022-04-05 11:30       ` Roy Sigurd Karlsbakk
2022-04-06  6:57         ` Jorge Nunes
2022-04-06 19:57       ` Wols Lists [this message]
2022-04-06 20:46         ` Jorge Nunes
2022-04-06 21:02           ` Roy Sigurd Karlsbakk

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=b9f58b50-3f79-4a81-2f47-0f23a6958e10@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=jorgebnunes@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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