From: Charles Polisher <cpolish@surewest.net>
To: Dan Williams <djbw@fb.com>
Cc: chris <tknchris@gmail.com>,
"Dorau, Lukasz" <lukasz.dorau@intel.com>,
Neil Brown <neilb@suse.de>, "Jiang, Dave" <dave.jiang@intel.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recovery/Access of imsm raid via mdadm?
Date: Thu, 17 Jan 2013 07:12:17 -0800 [thread overview]
Message-ID: <20130117151217.GB29871@kevin> (raw)
In-Reply-To: <CAA9_cmfYRoRrF_Q=VkNctyte3UMfbDiyJ7DgaryMnaFD-NV4ew@mail.gmail.com>
Dan Williams wrote:
> chris <tknchris@gmail.com> wrote:
> > any idea why it wont assemble? I thought even if data was corrupt I
> > should be able to force it to assemble and look at it to determine if
> > it is corrupt or in tact
>
> A bug in mdadm was introduced shortly after the "missing" support was
> added. Looks like you need 3.2.6.
Probably unrelated, but in case you were unaware, ICHxR chipsets
have snared me in the past with bugs that were later corrected
by firmware updates from Intel. If I remember correctly from
upthread, you were at one point attempting to / running this
array with such hardware. If this is still an option, you might
check your firmware version and the release notes for any more
recent release. This won't fix software RAID but it could
conceivably coax the ICH10R into assembling the array.
--
Charles
next prev parent reply other threads:[~2013-01-17 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:23 Recovery/Access of imsm raid via mdadm? chris
2013-01-10 17:09 ` Dave Jiang
2013-01-10 20:19 ` chris
2013-01-11 1:42 ` Dan Williams
2013-01-11 17:53 ` chris
2013-01-13 19:00 ` chris
2013-01-13 21:05 ` Dan Williams
2013-01-14 0:56 ` chris
2013-01-14 12:36 ` Dorau, Lukasz
2013-01-14 14:10 ` Dorau, Lukasz
2013-01-14 14:24 ` Dorau, Lukasz
2013-01-14 15:25 ` chris
2013-01-15 10:25 ` Dorau, Lukasz
2013-01-16 16:49 ` chris
2013-01-16 16:53 ` chris
2013-01-16 22:47 ` Dan Williams
2013-01-17 15:12 ` Charles Polisher [this message]
2013-01-17 16:07 ` chris
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=20130117151217.GB29871@kevin \
--to=cpolish@surewest.net \
--cc=dave.jiang@intel.com \
--cc=djbw@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=neilb@suse.de \
--cc=tknchris@gmail.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 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).