From: Drew <drew.kay@gmail.com>
To: Khurram Hassan <kfhassan@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Rocketraid 640 raid 5 disabled
Date: Wed, 27 Feb 2013 19:52:55 -0800 [thread overview]
Message-ID: <CACJz6QvecsLtH+uPzZrbniv1z_UAqha6xOwSiR8RcK851Aoscw@mail.gmail.com> (raw)
In-Reply-To: <CACJz6Qvd1QEC3bQFiZLAS4A+wNMNL5fW-G_Gmf2mydem=0mroQ@mail.gmail.com>
On Wed, Feb 27, 2013 at 7:28 PM, Drew <drew.kay@gmail.com> wrote:
>> I would like to use mdadm to re-write the array's metadata so that the
>> disks are accessible again. I have done it previously also but with an
>> intel array and loads of help from Neil Brown. I am hoping he can work
>> his magic again :)
>
> You probably won't be able to. The Intel RAID controllers were
> possible because developers from Intel frequent this list and have
> assisted in the efforts to get IMSM RAID supported by mdadm. The RAID
> metadata from other controllers like Adaptec or LSI are usually
> proprietary and afaik, are not supported by mdadm.
Looking at the linux source closer for the hpt driver, I'm thinking
it's proprietary. There are several pre-compiled object files that
appear to contain the driver code for the various RAID related
functions. That also suggests the controller is a fakeraid controller,
a HPT trademark, especially given the price point locally.
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
"This started out as a hobby and spun horribly out of control."
-Unknown
prev parent reply other threads:[~2013-02-28 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 3:11 Rocketraid 640 raid 5 disabled Khurram Hassan
2013-02-27 6:39 ` Stan Hoeppner
2013-02-27 15:55 ` Khurram Hassan
2013-02-28 3:28 ` Drew
2013-02-28 3:52 ` Drew [this message]
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=CACJz6QvecsLtH+uPzZrbniv1z_UAqha6xOwSiR8RcK851Aoscw@mail.gmail.com \
--to=drew.kay@gmail.com \
--cc=kfhassan@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 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.