From: Phil Turmel <philip@turmel.org>
To: William Colls <william.colls@rogers.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid Problem - Unknown File System Type
Date: Thu, 10 Nov 2011 10:48:59 -0500 [thread overview]
Message-ID: <4EBBF26B.1090309@turmel.org> (raw)
In-Reply-To: <4EBBEC80.9040709@rogers.com>
On 11/10/2011 10:23 AM, William Colls wrote:
[...]
> the array was mounted as follows
>
> mount -t ext3 /dev/md0p1 /opt/share
>
> LVM was not installed on the old system, nor is it installed on the new machine
OK.
>> Please show a hexdump of the first 8k of /dev/md0p1. That should give us a signature to hunt down.
>
> 00000000 fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 |................|
> 00000010 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 |...|.........!..|
> 00000020 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 |....8.u........u|
> 00000030 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74 01 8b |.........|...t..|
> 00000040 4c 02 cd 13 ea 00 7c 00 00 eb fe 00 00 00 00 00 |L.....|.........|
> 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 000001b0 00 00 00 00 00 00 00 00 17 29 06 00 00 00 00 01 |.........)......|
> 000001c0 01 00 83 fe ff ff 3f 00 00 00 01 14 54 57 00 00 |......?.....TW..|
> 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
> 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> *
> 00002000
The signature is definitely not there for superblock 0, and it doesn't look like any other structure I'm familiar with.
Since you are confident it was ext3, try:
dumpe2fs |grep superblock
or:
dumpe2fs -f |grep superblock
That might find a backup superblock that can then be used with fsck. See e2fsck(8), option "-b".
I would run e2fsck in read-only mode for each backup superblock attempted, to see how bad the situation is. If its mostly clean, then it would be safe to proceed with the actual repair.
If none of this works, I'm out of ideas. You'd probably want to ask for more help on the linux-ext4 mailing list.
Phil
next prev parent reply other threads:[~2011-11-10 15:48 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
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 [this message]
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=4EBBF26B.1090309@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=william.colls@rogers.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.