linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johny Ågotnes" <johny@agotnes.com>
To: Ryan Bourgeois <rgb005@latech.edu>
Cc: Danny Cox <Danny.Cox@ECWeb.com>,
	Linux IDE List <linux-ide@vger.kernel.org>
Subject: Re: Which SATA Combos To Consider?
Date: Fri, 18 Feb 2005 10:44:57 +1000	[thread overview]
Message-ID: <42153A89.2090909@agotnes.com> (raw)
In-Reply-To: <421535F6.80609@latech.edu>

Just a quick note on the SX4 Card - I have seen data corruption on 
hard-drives too in the simplest possible setup, so I'd stay clear of 
that card until further notice.

Mine is sitting in a cupboard right now, awaiting 'someone' (me, if I 
get some time to learn low-level kernel drivers) debugging the issue.

Basically, accessing two drives via this card causes corruption, I had 
it working ok when I only accessed 1 drive, which is kinda pointless...

:)J



Ryan Bourgeois wrote:
> Danny Cox wrote:
> 
>>     I've been mostly lurking here for awhile now, just seeing how things
>> are going.  I've seen various drives on a blacklist, and various
>> controllers that do this or that well, but have problems doing foo.
>> There also seem to have been a Strange Interaction as well, but that's a
>> fuzzy memory at best.
>>
>>     So, my question is: if YOU were to purchase an SATA setup brand new,
>> what would you specify?  Which drives, motherboards, and PCI cards would
>> you recommend that just work?
>>
>>     I don't even mean "work like a Mercedes", by which I mean almost
>> perfection.  I mean like a Chevy.  I don't mind a little tinkering to
>> get it right, but I want my disk subsystem to be solid thereafter!  I've
>> got important stuff here!  Like my wife's backup; NEVER lose your wife's
>> backup (shudder)!
>>
>>     If SATA isn't ready for consumerdom, I'd like to know that too.  This
>> just isn't for Jeff and Bart either.  I'd like to hear success stories
>> from those whose systems just hum along all the time!
>>
>>     Thanks in advance!
>>
>>  
>>
> On my file server I run the Highpoint RocketRAID 1640.  It's a software 
> RAID five card.  Basically it's just a PCI card with two HPT374 chips 
> each with two SATA plugs (a total of four plugs).  So it's a no frills 
> PATA card with SATA converters onboard.  I run three Western Digital 
> 120gb SATA drives on it with a Linux Software RAID 5 array on them.  
> Aside from the fact that it's a PATA card at heart (so it doesn't use 
> libata), my only complaint is that it's slow.  It's stable as a rock, 
> though, I've had no problems with the card or drives.
> 
> I have a Promise SX4 that I tried.  I had those same three drives 
> connected to it, but I was having some problems with the array when I 
> was using it.  It had a tendency to corrupt the filesystem, for some 
> reason.  I was having other problems at the time, though, so it could be 
> unrelated to the card I was using.  If I get time and money I may try 
> and set up an array on the card for testing.
> 
> Anyways, out of personal preference, I go with Western Digital hard 
> drives.  For SATA cards, the Promise TX cards seem pretty reliable.  I 
> have an onboard TX2 on my main machine running a WD Raptor.  I've had 
> absolutely no problems with it and libata.  Or in Windows, for that matter.
> 
> I haven't used any other cards or drives, so I cannot offer anything in 
> that direction.
> 
> -Ryan Bourgeois
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2005-02-18  0:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  4:28 libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-16 11:01 ` Brad Campbell
2005-02-16 17:25   ` Jeff Garzik
2005-02-16 20:54     ` Brad Campbell
2005-02-16 21:40       ` Andy Warner
2005-02-16 22:47         ` Jeff Garzik
2005-02-16 23:49           ` Andy Warner
2005-02-16 23:58             ` Jeff Garzik
2005-02-17  0:20               ` Andy Warner
2005-02-17  5:08                 ` Jeff Garzik
2005-02-17 14:59                   ` Andy Warner
2005-02-17 19:13                     ` Jeff Garzik
2005-02-17 19:25                       ` Andy Warner
2005-02-17 22:36                         ` Jeff Garzik
2005-02-17 19:42                       ` Which SATA Combos To Consider? Danny Cox
2005-02-17 20:55                         ` Jeff Garzik
2005-02-18  0:25                         ` Ryan Bourgeois
2005-02-18  0:44                           ` Johny Ågotnes [this message]
2005-02-18  0:52                             ` Jeff Garzik
2005-02-21 23:50                               ` Johny Ågotnes
2005-02-21 23:50                               ` Johny Ågotnes
2005-02-22  1:55                                 ` Johny Ågotnes
2005-02-18  6:13         ` libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-19  4:14           ` Brad Campbell
2005-02-21  4:27             ` Brad Campbell
2005-02-22 10:09               ` Brad Campbell
  -- strict thread matches above, loose matches on Subject: below --
2005-02-21  9:25 Which SATA Combos To Consider? linux

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=42153A89.2090909@agotnes.com \
    --to=johny@agotnes.com \
    --cc=Danny.Cox@ECWeb.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rgb005@latech.edu \
    /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).