From: den RDC <denrdc@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID 5 - All superblocks gone due to MBR/GPT mishap - how do i figure out chunk size?
Date: Thu, 16 May 2013 21:24:12 +0200 [thread overview]
Message-ID: <CAMtEPUOF_jAWwxgJt=GjL+9RMTo-j8_WgPDXAWNNDTHn=4uAkA@mail.gmail.com> (raw)
Hello
Due to a nasty (human) error, 4 2tb disks in raid5 have lost their
1st megabyte of data ( including superblock ). In an attempt to get
the array to a state usable enough to at least attempt data recovery,
I have been trying to re-enable the array using various chunk size and
partition start offsets, but i cant seem to get it anywhere near a
consistent state ( recovery tools only return files or pieces of files
smaller then the chunk size, indicating alignment/chunk size
inconsistencies ).
The data I do have is :
- the order of the disks
- the pretty solid assumption that all data, even parity should be
fine for most of the disk except the very beginning.
- the exact size of the MD device before it got corrupted.
Is there any way, however adventurous, to glean the missing data (
chunk size, chunk alignment/offset ) from analysis of the existing
data ?
Kind regards
den_RDC
reply other threads:[~2013-05-16 19:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMtEPUOF_jAWwxgJt=GjL+9RMTo-j8_WgPDXAWNNDTHn=4uAkA@mail.gmail.com' \
--to=denrdc@gmail.com \
--cc=linux-raid@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).