From: evan d <forumscollective@gmail.com>
To: quwenruo.btrfs@gmx.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem
Date: Sun, 7 Oct 2018 10:09:21 +0200 [thread overview]
Message-ID: <CAG__1a75dV6zVzMQFrnN-6u0iPXQRgvKebTkM1kxoiKgm3bcwg@mail.gmail.com> (raw)
In-Reply-To: <2122b08c-0fa9-b774-cbad-67b71f5084d4@gmx.com>
> If first 128M doesn't hit, I highly doubt something more strange happened.
Not sure I follow, do you mean if it doesn't hit then it's likely
something else went wrong?
> I'm considering something like encryption.
> Maybe the disk is already encrypted by hardware?
The drives were never encrypted, none of my drives are
> Windows is just a black box, I have no idea what a Windows could do to a
> disk.
>
> But it doesn't explain why the 2nd super block can't be located, unless
> Windows is wipe more data than the first 128M.
I'm thinking Windows may have tried to convert them to Dynamic disk on
detecting them and assuming they're empty.
>
> If the disk is larger than 256G, would you please try to locate the last
> possible super at 256G?
They're both 6TB drives
>
> # dd if=/dev/sdb bs=1M of=last_chance.raw count=128 skip=256M
> # grep -obUaP "\x5F\x42\x48\x52\x66\x53\x5F\x4D" last_chance.raw
dd returns:
dd: /dev/sdb: cannot skip: Invalid argument
next prev parent reply other threads:[~2018-10-07 8:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 23:23 Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem evan d
2018-10-07 0:32 ` Remi Gauvin
2018-10-07 6:08 ` evan d
2018-10-07 0:41 ` Qu Wenruo
2018-10-07 6:10 ` evan d
2018-10-07 6:26 ` Qu Wenruo
2018-10-07 6:47 ` evan d
2018-10-07 7:39 ` Qu Wenruo
2018-10-07 8:09 ` evan d [this message]
2018-10-07 8:19 ` Qu Wenruo
2018-10-07 8:28 ` evan d
2018-10-07 9:47 ` Qu Wenruo
2018-10-07 10:39 ` evan d
2018-10-07 10:51 ` Qu Wenruo
2018-10-07 12:25 ` evan d
2018-10-07 12:26 ` evan d
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=CAG__1a75dV6zVzMQFrnN-6u0iPXQRgvKebTkM1kxoiKgm3bcwg@mail.gmail.com \
--to=forumscollective@gmail.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 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.