linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Danny Cox <Danny.Cox@ECWeb.com>
To: Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Linux IDE List <linux-ide@vger.kernel.org>
Subject: Which SATA Combos To Consider?
Date: Thu, 17 Feb 2005 14:42:44 -0500	[thread overview]
Message-ID: <1108669364.3604.80.camel@vom> (raw)
In-Reply-To: <4214ECE9.7070502@pobox.com>

	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!

-- 
Daniel S. Cox
Internet Commerce Corporation


  parent reply	other threads:[~2005-02-17 19:43 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                       ` Danny Cox [this message]
2005-02-17 20:55                         ` Which SATA Combos To Consider? Jeff Garzik
2005-02-18  0:25                         ` Ryan Bourgeois
2005-02-18  0:44                           ` Johny Ågotnes
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=1108669364.3604.80.camel@vom \
    --to=danny.cox@ecweb.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).