From: Drew <drew.kay@gmail.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Nvidia Raid5 Failure
Date: Sun, 13 Apr 2014 09:42:19 -0700 [thread overview]
Message-ID: <CACJz6QtoddN1nOcfzeJeV-09j+t9fhT=E2a17Ppxq4gXpZDcVA@mail.gmail.com> (raw)
In-Reply-To: <CAK_KU4ZHZik=_=2=fMPW1c_y-xc0DW_9=ucsYQXU2e=eSOtYQg@mail.gmail.com>
On Thu, Apr 10, 2014 at 7:36 AM, Scott D'Vileskis <sdvileskis@gmail.com> wrote:
> <snip> I
> would also advise against what is known as 'fake raid' controllers
> like your NVIDIA hardware likely is, (or Promise, highpoint, Intel,
> etc) because it can be difficult to recover data if you have a
> controller/mobo failure without exact hardware.
Agree on the staying away from fake-RAID. One thing I will point out
for reference tho, is that not *all* Intel RAID is fakeraid. The
onboard RAID built into Intel's ICH family certainly is. However Intel
does make a line of RAID controller daughter cards which are rebadged
LSI RAID controllers and are in fact true H/W RAID. Easiest way to
know is to see if the card supports SAS. If it does, chances are it's
a H/W RAID card.
--
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
next prev parent reply other threads:[~2014-04-13 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 5:00 Nvidia Raid5 Failure peter davidson
2014-04-10 8:46 ` David Brown
2014-04-10 14:36 ` Scott D'Vileskis
2014-04-11 4:15 ` Scott D'Vileskis
2014-04-11 7:45 ` David Brown
2014-04-13 16:42 ` Drew [this message]
2014-04-14 6:14 ` Stan Hoeppner
2014-04-14 9:50 ` NeilBrown
2014-04-14 10:55 ` Stan Hoeppner
[not found] ` <CAK_KU4aRbK-sD6h7xqieW_D9FhBYBAy799wZHXq222DAMLjRng@mail.gmail.com>
2014-04-15 3:18 ` Stan Hoeppner
2014-04-10 11:13 peter davidson
2014-04-13 10:59 peter davidson
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='CACJz6QtoddN1nOcfzeJeV-09j+t9fhT=E2a17Ppxq4gXpZDcVA@mail.gmail.com' \
--to=drew.kay@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.