linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: antlists <antlists@youngman.org.uk>,
	Daniel Sanabria <sanabria.d@gmail.com>,
	Roman Mamedov <rm@romanrm.net>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: do i need to give up on this setup
Date: Thu, 8 Oct 2020 21:00:11 -0400	[thread overview]
Message-ID: <24447.46619.550227.607747@quad.stoffel.home> (raw)
In-Reply-To: <CAAMCDefj4koi_+g-vdzWpfSB21KLgRq2kJ9sCZK04iX85b_qfw@mail.gmail.com>

>>>>> "Roger" == Roger Heflin <rogerheflin@gmail.com> writes:

Roger> The controller is crap, and is expected to have serious issues no
Roger> matter what drives are on the controller.

I can't say enough good things about the LSI SATA RAID controllers.
You can usually get them pretty cheap on eBay, and just flash them
with the JBOD firmware and they do great.

  LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT S)

It's been a while, but I think it was an IBM branded card at the
time.  8 ports, easy setup, works well.  And looking on ebay, they're
cheap now, around $50 though you might have to pay for the 1-to-4
cables to goto SATA drives.  9211, 9341, stuff like that.  Here's an
eBay listing with cables:

https://www.ebay.com/p/1404809612?iid=133501363959&_trkparms=aid%3D555018%26algo%3DPL.SIM%26ao%3D1%26asc%3D20170810093926%26meid%3De20ed20fb9634e328a31bca5c9e2063c%26pid%3D100854%26rk%3D1%26rkt%3D1%26itm%3D133501363959%26pmt%3D1%26noa%3D0%26pg%3D2322090%26algv%3DSimplAMLSeedlessV2&_trksid=p2322090.c100854.m4779

In my mind, the other advantage of these cards is that you can get two
of them, and split your data across two controllers.  But it also gets
your data disks off the internal controllers, which means you don't
run into nearly as many problems where the system tries to boot off
your data drives, or you have to put boot blocks on them, etc.  

This controller would be more tolerant of your existing drives, since
you have the 850w power supply, it's almost certainly not power
problems either.

John

  reply	other threads:[~2020-10-09  1:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 13:10 do i need to give up on this setup Daniel Sanabria
2020-10-05 13:17 ` Reindl Harald
2020-10-05 13:44 ` Roman Mamedov
     [not found]   ` <CAHscji0pNezf6xCpjWto5-21ayoCeLWm34GTYh5TSgxkOw90mw@mail.gmail.com>
2020-10-05 14:04     ` Roman Mamedov
2020-10-05 14:10       ` Reindl Harald
2020-10-05 14:28       ` Daniel Sanabria
2020-10-05 15:58         ` Roger Heflin
2020-10-06  7:56           ` Daniel Sanabria
2020-10-06  8:24             ` Reindl Harald
2020-10-06 10:53             ` Roger Heflin
2020-10-06 11:29               ` antlists
2020-10-06 14:59                 ` Roger Heflin
2020-10-09  1:00                   ` John Stoffel [this message]
2020-10-06 15:03               ` Tim Small
2020-10-06 16:01                 ` Daniel Sanabria
2020-10-07  7:26                   ` Tim Small

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=24447.46619.550227.607747@quad.stoffel.home \
    --to=john@stoffel.org \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.net \
    --cc=rogerheflin@gmail.com \
    --cc=sanabria.d@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).