From: William Colls <william.colls@rogers.com>
To: Phil Turmel <philip@turmel.org>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid Problem - Unknown File System Type
Date: Wed, 09 Nov 2011 14:57:18 -0500 [thread overview]
Message-ID: <4EBADB1E.1070700@rogers.com> (raw)
In-Reply-To: <4EBACC88.8070403@turmel.org>
On 11/09/2011 01:55 PM, Phil Turmel wrote:
> Hi William,
>
> On 11/09/2011 12:12 PM, William Colls wrote:
> [...]
>
>> I thought, at the time, that I needed to do the create so that the /dev/md0 device would be created properly (new machine had no raid before).
>
> That's the "--auto" option, which has sane defaults.
>
> [...]
>
>> No output from the original setup.
>
>> From what you've described so far, a likely possibility is that the original raid 1 was using metadata version 1.1 or 1.2, which put the superblock near the beginning of the disks. The default "--create" metadata in that old version of mdadm is 0.9, as you can see in your reports.
>
> If so, you've likely only lost a tiny bit of data at the end of the volumes where the 0.90 superblock has been written. (I'm also going to assume that the two disks were in-sync in old box before you moved them, so the re-sync wouldn't do any harm.)
>
> A dump of the first 8K of your drives might be helpful here.
>
> dd if=/dev/sdb count=16 2>/dev/null |hexdump -C
>
> dd if=/dev/sdc count=16 2>/dev/null |hexdump -C
>
> Regards,
>
> Phil
>
Did the dumps to text files. diff shows no difference between the files.
Should I be looking for anything particular? There are sections which
seem to have data, and several blocks that are all zeros, but I don't
see any particular patterns, and only a very few obvious text strings.
Thanks for your interest and help.
--
I know you believe that you understand what you think I said, but I am
not sure that you realize that what you heard was not what I ment.
next prev parent reply other threads:[~2011-11-09 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 16:12 Raid Problem - Unknown File System Type William Colls
2011-11-09 16:39 ` Robin Hill
2011-11-09 17:12 ` William Colls
2011-11-09 18:55 ` Phil Turmel
2011-11-09 19:57 ` William Colls [this message]
2011-11-09 20:05 ` Phil Turmel
[not found] ` <4EBAE90F.2030104@rogers.com>
2011-11-09 21:45 ` Phil Turmel
2011-11-10 3:36 ` William Colls
2011-11-10 3:57 ` Phil Turmel
2011-11-10 15:23 ` William Colls
2011-11-10 15:48 ` Phil Turmel
2011-11-10 16:12 ` John Robinson
2011-11-10 16:32 ` Phil Turmel
2011-11-14 15:01 ` William Colls
2011-11-10 8:53 ` Robin Hill
2011-11-09 17:07 ` Gordon Henderson
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=4EBADB1E.1070700@rogers.com \
--to=william.colls@rogers.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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).