From: Alli Quaknaa <alquaknaa@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Restoring BTRFS partition
Date: Tue, 20 Apr 2010 16:56:29 +0200 [thread overview]
Message-ID: <w2y8c113a261004200756ucfa2eeabk617da0fc90d6ed8a@mail.gmail.com> (raw)
Hello,
Yesterday I have messed up my partition table and lost the information
of my BTRFS partition. Luckily I was able to find it's beginning, or
at least I think so. This is what I did:
- created a blank 300M file, formated with btrfs, examined with
hexedit. After 65536 zeros (at the position 0x10000) a sequence "1F 55
A8 7C" comes and at a position 0x10040 an ASCII sequence _BHRfS_M_ is
found.
- I found the same sequence ("_BHRfS_M_") in the raw image of my drive
and I've made another image to make my original look more like the
300M file - so in the beginning 65k of zeros and the sequence
_BHRfS_M_ is at the same position (basically I just deleted whatever
was before this sequence and prepended those zeros).
I don't think I have done anything that could have damaged the
filesystem itself and when viewing with hexedit I still see ELF data,
include files and so on, but I can't get the new image to mount or
btrfsck, it is simply not recognized as a btrfs image. Could anyone
please help me fix this? I have very little actual C/Linux knowledge
(from the programmers point of view) so I'd rather not go reading the
code.
Of course I can send whatever more information you need, just as a
starter - I have no idea what the sequence at 0x10000 is, but it is
different than the one of my blank 300M file - in my partition it says
"CB EE AE 02".
Thanks in advance,
al-Quaknaa
next reply other threads:[~2010-04-20 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 14:56 Alli Quaknaa [this message]
2010-04-20 15:55 ` Restoring BTRFS partition Wengang Wang
2010-04-20 16:50 ` Sean Bartell
2010-04-20 17:14 ` Alli Quaknaa
2010-04-20 18:13 ` Alli Quaknaa
2010-04-20 20:30 ` Sean Bartell
2010-04-20 22:25 ` Alli Quaknaa
2010-04-21 0:32 ` Sean Bartell
2010-04-21 7:45 ` Alli Quaknaa
2010-04-21 2:49 ` Wengang Wang
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=w2y8c113a261004200756ucfa2eeabk617da0fc90d6ed8a@mail.gmail.com \
--to=alquaknaa@gmail.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).