From: kind.moon1862@fastmail.com
To: "Qu Wenruo" <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Help requested: btrfs can't read superblock
Date: Tue, 19 Mar 2024 13:44:14 -0700 [thread overview]
Message-ID: <6f97071f-2c47-46f7-89f1-b0a80530ad38@app.fastmail.com> (raw)
In-Reply-To: <1cfe630d-ddb4-42fc-ac42-54fa53cab747@gmx.com>
On Mon, Mar 18, 2024, at 17:53, Qu Wenruo wrote:
> And still, please run memtest before doing any rescue.
> As faulty hardware can always lead to weird problems no matter what.
memtest86+ found bad RAM. I will replace that before proceeding. Thanks again.
next prev parent reply other threads:[~2024-03-19 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 21:22 Help requested: btrfs can't read superblock kind.moon1862
2024-03-19 0:06 ` Qu Wenruo
2024-03-19 0:33 ` kind.moon1862
2024-03-19 0:53 ` Qu Wenruo
2024-03-19 20:44 ` kind.moon1862 [this message]
2024-03-19 20:45 ` Qu Wenruo
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=6f97071f-2c47-46f7-89f1-b0a80530ad38@app.fastmail.com \
--to=kind.moon1862@fastmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox