Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Andrew Lyon" <andrew.lyon@gmail.com>
To: James Andrewartha <jamesa@daa.com.au>
Cc: linux-ide@vger.kernel.org, jim@jtan.com
Subject: Re: Recommended PCI Express or PCI-X SATA (Raid) Controller?
Date: Wed, 17 Sep 2008 15:36:50 +0100	[thread overview]
Message-ID: <f4527be0809170736w4cf59a71j38588aea78d3f10a@mail.gmail.com> (raw)
In-Reply-To: <1221595291.23098.8.camel@zarvora>

On Tue, Sep 16, 2008 at 9:01 PM, James Andrewartha <jamesa@daa.com.au> wrote:
> On Sat, 2008-09-13 at 10:00 +0100, Andrew Lyon wrote:
>> I want to add a PCI Express or PCI-X SATA Controller to my system for
>> an additional 2 or 4 sata ports, however I am running Xen so I am
>> stuck with a older kernel version, gentoo xen 2.6.21 has proved to be
>> fairly stable on my hardware but I may attempt to upgrade to 2.6.25 if
>> necessary, can anybody recommend a pci-x or pci express sata
>> controller with 2 or 4 ports that has been well supported since at
>> least 2.6.21?
>>
>> I assumed that any real hardware raid device would be beyond my budget
>> but I might just be able to afford a Areca ICAe1210, has anybody used
>> Areca cards with older kernels?
>
> The Sil 3132 is a good 2-port PCIe controller, or the 3124 is 4 ports on
> PCI-X. Going up a bit, the supermicro AOC-USAS-S8i is an 8-port PCIe SAS
> controller based on the LSISAS1068E which has had a Linux driver for a
> while, but I don't know what the support for SATA drives on it in Linux
> is like.
>
> The Areca cards are good and have drivers for older kernels (2.6.18 if
> not earlier).
>
> James Andrewartha
>


Thanks for the info, I borrowed a PCIe Sil 3132 and also found a PCI
3112 in our spares, the 3112 was not detected by sata_sil when running
2.6.18-xen but I've since made my own Xen kernel based on
gentoo-sources-2.6.25-gentoo-r8 (2.6.25.15) and the Xen patches from
Opensuse 2.6.25, with a newer kernel both cards are detected and work
well, I may replace them with a single 3124 PCI-X in the near future.

I have noticed one very minor problem, I am using a Supermicro
SC743TQ-865-SQ case with CSE-SAS-743TQ SATA/SAS hotswap backplane and
X7DWA-N motherboard, 6 of the drives are connected to the onboard
SATA, 2 to the 3132 and the 3112 is used for SATA DVDROM+DVDRW, the
hot swap bays have two led's for each drive, activity and failure,
when the onboard SATA is initialized and the drives are detected the
led's in each bay flash red, they flash again when smartd is loaded
and then flash green for activity, the led's in the bays connected to
the 3132 do not flash at all.

The backplane http://www.supermicro.com/manuals/other/BPN-SAS-743TQ.pdf
can use I2C or SGPIO mode, I've left it on I2C (default) as the
motherboard only came with one SGPIO cable, although it does have two
ports.

What exactly is I2C/SGPIO used for with a hot swap backplane like this?

Perhaps the LED's only work when all 8 ports are connected to the same
controller?

Andy

      reply	other threads:[~2008-09-17 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  9:00 Recommended PCI Express or PCI-X SATA (Raid) Controller? Andrew Lyon
2008-09-16 20:01 ` James Andrewartha
2008-09-17 14:36   ` Andrew Lyon [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=f4527be0809170736w4cf59a71j38588aea78d3f10a@mail.gmail.com \
    --to=andrew.lyon@gmail.com \
    --cc=jamesa@daa.com.au \
    --cc=jim@jtan.com \
    --cc=linux-ide@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