linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Low cost PCI-E unRAID - Supermicro AOC-SASLP-MV8 Driver/LBA questions for HW owners/users
Date: Fri, 21 Jan 2011 13:04:21 -0600	[thread overview]
Message-ID: <4D39D8B5.1090901@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTimp7xxQTv419oL7x6L-sbrhv1ZcEqLq+CfY6gs5@mail.gmail.com>

Michael Evans put forth on 1/21/2011 10:00 AM:
> The SUPERMICRO AOC-SASLP-MV8 PCI Express x4 Low Profile SAS SAS RAID
> Controller seems to fit my needs and budget except for one glaring
> omission on Supermicro's product page, and every other site that
> blindly copies it.
> 
> Has anyone tested this hardware with a 48-bit LBA required drive (EG
> one of the 3TB drives that still exposes 512k sectors)?

NewEgg has an excellent return policy:
http://www.newegg.com/Product/Product.aspx?Item=N82E16816101358

But, BTW, if you can afford over $1000 of 3TB drives, why are you demanding to
go so cheap with the HBA?  There are plenty of much better LSI based dual
SFF8087 HBAs available with no LBA or driver issues.  For instance:
http://www.newegg.com/Product/Product.aspx?Item=N82E16816117157

$155 Quality/compatible LSI SAS1068E chip+driver vs
$109 Marvell 88SE6480 less than quality chip+driver

If you can afford 5+ 3TB drives you can certainly afford an extra ~$50 for a
decent quality known to work SAS/SATA HBA.  I say 5+ because you're obviously
starting out with 5 or you'd be looking at cards with a single SFF8087, or
simply 4 individual SATA connectors.

I can't imagine an easier decision to make:  $50 for guaranteed piece of mind,
performance, compatibility.

-- 
Stan

  reply	other threads:[~2011-01-21 19:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 16:00 Low cost PCI-E unRAID - Supermicro AOC-SASLP-MV8 Driver/LBA questions for HW owners/users Michael Evans
2011-01-21 19:04 ` Stan Hoeppner [this message]
2011-01-22  5:50   ` Michael Evans
2011-01-22 16:04     ` Stan Hoeppner
2011-01-22 20:36       ` Michael Evans
2011-01-22 22:42         ` Matt Garman
2011-01-22 23:40         ` Spelic
2011-01-23  2:44           ` Andre Tomt
2011-01-23  3:19             ` Michael Evans
2011-01-23  4:00             ` Spelic
2011-01-24 11:45               ` Sven Eschenberg
2011-01-23  0:49         ` Stan Hoeppner
     [not found]           ` <4D3C64CB.2080002@harddata.com>
     [not found]             ` <4D3C9C94.8090607@hardwarefreak.com>
     [not found]               ` <4D3CB72E.3050000@harddata.com>
2011-01-24  1:52                 ` Stan Hoeppner
2011-01-24  3:28                   ` John Robinson
2011-01-24 11:27                     ` Mark Knecht
2011-01-24 11:56                       ` John Robinson
2011-01-24 23:09                         ` Leslie Rhorer
2011-01-24 22:06                     ` Leslie Rhorer
2011-01-25 18:30                       ` Maurice Hilarius
2011-01-25 20:00                         ` Stan Hoeppner
2011-01-24 21:58           ` Leslie Rhorer

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=4D39D8B5.1090901@hardwarefreak.com \
    --to=stan@hardwarefreak.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 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).