From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Steven Haigh <netwiz@crc.id.au>, linux-raid@vger.kernel.org
Subject: Re: Recommended pci-e 1x SATA cards.
Date: Fri, 15 Apr 2011 16:31:08 -0500 [thread overview]
Message-ID: <4DA8B91C.8050005@hardwarefreak.com> (raw)
In-Reply-To: <20110415105846.1c4ec630@natsu>
Roman Mamedov put forth on 4/14/2011 11:58 PM:
> On Thu, 14 Apr 2011 14:55:40 -0500
> Stan Hoeppner <stan@hardwarefreak.com> wrote:
>
>> Steven Haigh put forth on 4/14/2011 8:16 AM:
>>
>>> That is a very nice writeup... I searched for the HighPoint Rocket 620 -
>>> listed as $24.99 on NewEgg - but Australian suppliers seem to have it
>>> above $100AUD. The cheapest price I found was $54AUD - and they were out
>>> of stock.
>>
>> This is the card you should get:
>> http://www.sybausa.com/productInfo.php?iid=536
>> http://www.newegg.com/Product/Product.aspx?Item=N82E16815124027
>>
>> It's the same Syba Sil3132 based card BackBlaze uses in their 45 drive
>> mdadm managed pods.
>>
>
> Did you read the second link you posted, specifically the Feedback section?
> That's one more confirmation of corruption issue we discussed in this thread.
The overall Newegg rating for the Syba card you deride is 4/5 eggs
across 109 reviews. If the card was as horrible as you make it out to
be, the rating would be 1/5 not 4/5, and people would stop buying it.
Note that the user who posted the read corruption issue referred to a
single application in Windows 7 where this error occurred, TeraCopy.
It's far more likely he was up against an application or driver issue
than a hardware issue with the Syba card. He did not state whether a
Windows Explorer copy would also cause the problem, nor xcopy, nor
Robocopy, etc.
BTW, did you even read the BackBlaze blog I posted? They run hundreds
of this exact Syba 3132 card, with Linux, with mdraid, and have reported
zero problems. And they're using a 5:1 PMP on each 3132 port. If these
cards, or the 3132 were junk, as you state, surely BackBlaze would have
run into problems in 2+ years of full production, no?
Again, you're taking isolated incidents and assuming they are the norm,
when they most certainly are not.
--
Stan
next prev parent reply other threads:[~2011-04-15 21:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 10:31 Recommended pci-e 1x SATA cards Steven Haigh
2011-04-14 10:54 ` Roman Mamedov
2011-04-14 11:05 ` Tapani Tarvainen
2011-04-14 11:25 ` Roman Mamedov
2011-04-14 11:41 ` Tapani Tarvainen
2011-04-14 12:02 ` Roman Mamedov
2011-04-14 11:14 ` Steven Haigh
2011-04-14 19:37 ` Stan Hoeppner
2011-04-15 1:54 ` Brad Campbell
2011-04-15 5:03 ` Roman Mamedov
2011-04-14 12:53 ` Roman Mamedov
2011-04-14 13:16 ` Steven Haigh
2011-04-14 19:55 ` Stan Hoeppner
2011-04-14 23:50 ` Steven Haigh
2011-04-15 4:06 ` Stan Hoeppner
2011-04-15 4:35 ` Steven Haigh
2011-04-15 4:56 ` Stan Hoeppner
2011-04-15 4:58 ` Roman Mamedov
2011-04-15 21:31 ` Stan Hoeppner [this message]
2011-04-16 5:15 ` Roman Mamedov
2011-04-16 8:57 ` Brad Campbell
2011-04-16 20:40 ` Stan Hoeppner
2011-04-17 5:44 ` Brad Campbell
2011-04-17 18:36 ` Stan Hoeppner
2011-04-17 18:45 ` Mikael Abrahamsson
2011-04-17 20:26 ` Stan Hoeppner
2011-04-17 21:18 ` Sven Eschenberg
2011-04-17 21:25 ` Guy Watkins
2011-04-17 23:29 ` Brad Campbell
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=4DA8B91C.8050005@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=netwiz@crc.id.au \
--cc=rm@romanrm.ru \
/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).