All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: Arve Knudsen <aknuds-1@broadpark.no>, linux-ide@vger.kernel.org
Subject: Re: Recommended SATA controller?
Date: Sun, 07 Mar 2004 22:32:48 +0100	[thread overview]
Message-ID: <404B9500.9060706@stesmi.com> (raw)
In-Reply-To: <404B93D9.5090402@stesmi.com>

Stefan Smietanowski wrote:

> Arve Knudsen wrote:
> 
>> Hi
>>
>> As it seems the Silicon Image driver won't be radically improved 
>> anytime soon(?), I'm thinking of purchasing a dedicated SATA 
>> controller. Can anyone recommend me a fairly cheap 2-port controller 
>> that's known to work well with Linux (2.6-series)? Stability is 
>> imperative, I just had a solid freeze and I'm afraid it might have to 
>> do with disk activity (playing MP3s while compiling). Might Promise 
>> (Ultra 150) or Adaptect (1210 SA) be worth considering?
> 
> 
> I sent a list the other day about my harddrives dieing on me and after
> following up my search I came across that there is some kind of either
> driver or hardware error on the VIA 8237 controller's SATA part, but
> ONLY if you run it in "DISK" mode. It works fine in "RAID" mode.
> 
> I can't give you specifics on what works or doesn't as I've only tried
> 2.4 so far but the promise one seems to work fine for me in 2.4 right
> now.
> 
> So stay away from the 8237 in case you decide to get a motherboard with
> SATA on instead (not much more expensive really than getting a seperate
> SATA PCI card.

Specifically three identical hard drives died on me in case you missed
the email, all in the same way. Low level formatting them cured two
but not the third. It is being RMA'd as we speak.

The problem is not only with Maxtor harddrives (as it was with me) but
with all brands. Drives that have died that I have read about are
WD, Maxtor and Seagate. I can't remember if Hitachi was on the list or
not but I wouldn't touch Hitachi (ex-IBM) with a 10 foot pole so that's
why I don't remember. Many people have seen the same problem as I did.
Some could use powermax to lowlevel the drive and some couldn't.
Using a different controller with the lowlevel formatted drive seems
to work for others as it does for me.

// Stefan

  reply	other threads:[~2004-03-07 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07 20:16 Recommended SATA controller? Arve Knudsen
2004-03-07 21:27 ` Stefan Smietanowski
2004-03-07 21:32   ` Stefan Smietanowski [this message]
2004-03-08  9:26     ` Arve Knudsen
2004-03-07 23:24 ` James Courtier-Dutton
2004-03-08  0:18   ` Bartlomiej Zolnierkiewicz
2004-03-08  9:11     ` Arve Knudsen

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=404B9500.9060706@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=aknuds-1@broadpark.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.