From: William Colls <william.colls@rogers.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid Problem - Unknown File System Type
Date: Wed, 09 Nov 2011 12:12:28 -0500 [thread overview]
Message-ID: <4EBAB47C.5070002@rogers.com> (raw)
In-Reply-To: <20111109163933.GA26630@cthulhu.home.robinhill.me.uk>
On 11/09/2011 11:39 AM, Robin Hill wrote:
> On Wed Nov 09, 2011 at 11:12:59AM -0500, William Colls wrote:
>
>>
>> Environment
>>
>> Kubuntu Linux 10.04.3 LTS
>> mdadm 2.6.7.1-1ubuntu15
>>
>> I have two identical disks that were in a raid configuration in another
>> machine (also running 10.04). I removed them from the old machine,
>> mounted them in a new machine, booted up, and at a terminal prompt as
>> root issued
>>
>> mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb /dev/sdc
>>
> You should have just assembled them. You've now created a new array
> instead of just assembling the old one.
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).
>
>> The configuration in the old machine was raid 1.
>>
>> I checked the contents of /proc/mdstat and it confirmed that md0 was
>> indeed running, with 2 devices, as expected. But it also said it was
>> resyncing the disks, which I didn't expect.
>>
>> When the reync completed, I was unable to mount /dev/md0p1. Specifying
>> -t ext3 in the mount command gives the error message "wrong fs, bad
>> option, bad superblock on /dev/md0p1". Trying mount with no -t gives the
>> error "unknown file type linux_raid_member". Looking at the disks with
>> Gparted, confims that the system sees the disks, but the filesystem
>> shows as unknown.
>>
> It would look like the old array was either created with an older mdadm
> version (with different defaults) or used some non-default parameter
> values.
>
>> The output from mdamd --detail /dev/sdb
>>
>> /dev/sdb:
>> Magic : a92b4efc
>> Version : 00.90.00
>> UUID : 1443e74d:f63f16ab:d527ef8c:7225e0b0
>> Creation Time : Tue Nov 8 13:14:48 2011
>> Raid Level : raid1
>> Used Dev Size : 732574464 (698.64 GiB 750.16 GB)
>> Array Size : 732574464 (698.64 GiB 750.16 GB)
>> Raid Devices : 2
>> Total Devices : 2
>> Preferred Minor : 0
>>
>> Update Time : Tue Nov 8 16:05:42 2011
>> State : clean
>> Active Devices : 2
>> Working Devices : 2
>> Failed Devices : 0
>> Spare Devices : 0
>> Checksum : c4195c85 - correct
>> Events : 34
>>
>>
>> Number Major Minor RaidDevice State
>> this 0 8 16 0 active sync /dev/sdb
>>
>> 0 0 8 16 0 active sync /dev/sdb
>> 1 1 8 32 1 active sync /dev/sdc
>>
>> --- end of output
>>
>> Output from mdadm --examine /dev/sdc
>>
>> /dev/sdc:
>> Magic : a92b4efc
>> Version : 00.90.00
>> UUID : 1443e74d:f63f16ab:d527ef8c:7225e0b0
>> Creation Time : Tue Nov 8 13:14:48 2011
>> Raid Level : raid1
>> Used Dev Size : 732574464 (698.64 GiB 750.16 GB)
>> Array Size : 732574464 (698.64 GiB 750.16 GB)
>> Raid Devices : 2
>> Total Devices : 2
>> Preferred Minor : 0
>>
>> Update Time : Tue Nov 8 16:05:42 2011
>> State : clean
>> Active Devices : 2
>> Working Devices : 2
>> Failed Devices : 0
>> Spare Devices : 0
>> Checksum : c4195c97 - correct
>> Events : 34
>>
>>
>> Number Major Minor RaidDevice State
>> this 1 8 32 1 active sync /dev/sdc
>>
>> 0 0 8 16 0 active sync /dev/sdb
>> 1 1 8 32 1 active sync /dev/sdc
>>
>> ---- end of output
>>
>> So - am I truly up the creek without a paddle? Is there any way to
>> recover this array? I have backups of most of it, but it will take a
>> while to find and restore. And for sure something will be lost.
>>
>
> Certainly most of the data should be there still. I don't suppose you
> have a copy of the mdadm --examine output from the old system at all?
No output from the original setup.
>
> Cheers,
> Robin
--
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 17:12 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 [this message]
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
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=4EBAB47C.5070002@rogers.com \
--to=william.colls@rogers.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).