linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: Mitchell Laks <mlaks@verizon.net>, linux-raid@vger.kernel.org
Subject: Re: multiple Sata SATAII 150, TX4  - how to tell which drive is which? headaches galore!
Date: Mon, 23 Jan 2006 13:20:59 +0100	[thread overview]
Message-ID: <op.s3ty89rfcigqcu@apollo13> (raw)
In-Reply-To: <200601230336.55220.mlaks@verizon.net>

On Mon, 23 Jan 2006 09:36:54 +0100, Mitchell Laks <mlaks@verizon.net>  
wrote:

> Dear Experts,
>
> I wanted to ask for any experience with running raid with SATA drives and
> controllers here under linux.
>

	Well, here's mine :

	Maxtor SATA drives series 6V (those with 16 MB cache) are incompatible  
with nforce 3-4 SATA controllers. Maxtor acknowledges this. Symptom is a  
slow death of the drive, ending with command timeouts. When reverting the  
drive to SATA 1.5Gbps with the jumper, it works perfectly again (for a few  
days...). nvidia doesn't care. This is on windows and linux. In windows,  
you have to use fucking PIO mode or you get corruptions. nforce4 sata also  
has problems with plextor sata burners, and possibly others.

	The Maxtor 6L series (with 8 MB cache) work flawlessly.

	I currently have these SATA drives, on a nforce3 MSI mobo :

# hdparm -I /dev/sd? |grep "Model Numb"

         Model Number:       Maxtor 6L200M0
         Model Number:       Maxtor 6L250S0
         Model Number:       ST3250823AS
         Model Number:       ST3250823AS

	All work. I RMA'd the 6V250 drive and exchanged it against a good, old,  
IDE drive, which works perfect.

	It took me a month, 3 maxtor drives, and nights of googling to figure  
this out...

	My gut feeling is that SATA isn't that ready for prime-time after all...

  reply	other threads:[~2006-01-23 12:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  8:36 multiple Sata SATAII 150, TX4 - how to tell which drive is which? headaches galore! Mitchell Laks
2006-01-23 12:20 ` PFC [this message]
2006-01-23 20:22   ` John Hendrikx
2006-01-23 20:44     ` Shawn Usry
2006-01-23 20:49       ` Jeff Garzik
2006-01-23 20:53       ` John Hendrikx
2006-01-24  9:54     ` PFC
2006-01-24 14:40       ` Jeff Garzik
2006-01-23 16:27 ` Shawn Usry
2006-01-23 17:41 ` Shawn Usry
2006-01-24  2:46   ` multiple Sata SATAII 150, TX4 - how to tell which drive is which?headaches galore! Shawn Usry
  -- strict thread matches above, loose matches on Subject: below --
2006-01-24  6:30 Mitchell Laks
2006-01-24 12:53 ` David Greaves
2006-01-24 16:10   ` Shawn Usry
2006-01-24 17:02     ` David Greaves
2006-01-24 17:12     ` Francois Barre
2006-01-24 17:18       ` Gordon Henderson
2006-01-24 17:21         ` Francois Barre
2006-01-24 17:32           ` Gordon Henderson
2006-01-24 22:56       ` John Hendrikx
2006-01-25  5:51       ` Mattias Wadenstein
2006-01-25  8:33       ` Hans Kristian Rosbach

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=op.s3ty89rfcigqcu@apollo13 \
    --to=lists@peufeu.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mlaks@verizon.net \
    /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).