All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nouts <nouts@protonmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: Troubleshoot help needed - RAID1 not mounting : failed to read block groups
Date: Sat, 02 May 2020 15:51:37 +0000	[thread overview]
Message-ID: <DQCllnVeUApb40W6_xKaNlAxRJlhCTeYnZEP5r3dZvF0AZejwemvJK-CWfNtV56zb5-LZaPuH-4WgD_-SxDeE2b_TYCRDeTo-2aN4atItbY=@protonmail.com> (raw)
In-Reply-To: <ZL8K9EyQa7EnOmd3WjfSsNFy8hYbikAq4lO6CTK1vc-HoXoqpY9CKKcYd2xFCwEDvry2aLuZvbwK91-2_J-Zu6tDL6sovvr4jRIATnhmyMQ=@protonmail.com>

Well, I changed my mind. I'll wait a few more days, for the beginning of the next week, if you have any magical command left :)
I'm not sure to understand it but can a "restore" command dump all of the data in a new readable disc ?




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, May 2, 2020 4:55 PM, Nouts <nouts@protonmail.com> wrote:

> For the record, I ran check and check --repair with the new btrfs-progs. Both returned this error :
>
> Opening filesystem to check...
> ERROR: child eb corrupted: parent bytenr=5923702292480 item=2 parent level=2 child level=0
> ERROR: failed to read block groups: Input/output error
> ERROR: cannot open file system
>
> I'm gonna wipe the drive and restore a backup as I've lost hope recovering and can't wait any longer.
> Thanks a lot for your help !
>
> Nouts
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, April 30, 2020 9:18 PM, Chris Murphy lists@colorremedies.com wrote:
>
> > On Thu, Apr 30, 2020 at 1:05 PM Nouts nouts@protonmail.com wrote:
> >
> > > Here is the dump --follow : https://pastebin.com/yx13mDfB
> > > Sadly, none of "mount" worked.
> >
> > Yep. I can't tell from the check error or the dump output, whether
> > it's worth trying chunk recover again with the latest progs, or check
> > with --repair. But either of those makes changes to the file system,
> > so best to get advice from a developer first and in the meantime
> > refresh backups.
> > I don't know that a newer kernel will help in this case, because even
> > the latest progs complains. And the output from check doesn't give
> > enough information to know what to try next or if it's hopeless.
> >
> > Chris Murphy



  reply	other threads:[~2020-05-02 15:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EvtqVyP9SQGLLtX4spGcgzbLaK45gh3h00n6u9QU19nuQi6g13oqfZf6dmGm-N8Rdd2ZCFl7zOeEBXRc_Whom2KYJA1eDUSQxgZPZgmI7Dc=@protonmail.com>
2020-04-30 11:41 ` Troubleshoot help needed - RAID1 not mounting : failed to read block groups Nouts
2020-04-30 13:46   ` Hugo Mills
2020-04-30 14:04     ` Nouts
2020-04-30 14:49       ` Nouts
2020-04-30 17:38   ` Chris Murphy
2020-04-30 18:40     ` Nouts
2020-04-30 18:46       ` Chris Murphy
2020-04-30 19:05         ` Nouts
2020-04-30 19:18           ` Chris Murphy
2020-05-02 14:55             ` Nouts
2020-05-02 15:51               ` Nouts [this message]
2020-05-02 17:53                 ` Chris Murphy
2020-05-06 19:31                   ` Nouts
2020-05-07 12:55                     ` Nouts

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='DQCllnVeUApb40W6_xKaNlAxRJlhCTeYnZEP5r3dZvF0AZejwemvJK-CWfNtV56zb5-LZaPuH-4WgD_-SxDeE2b_TYCRDeTo-2aN4atItbY=@protonmail.com' \
    --to=nouts@protonmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.com \
    /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.