From: David Greaves <david@dgreaves.com>
To: linux-raid@vger.kernel.org
Subject: Re: SATA chipset recomendations
Date: Wed, 09 Jun 2004 11:56:46 +0100 [thread overview]
Message-ID: <40C6ECEE.8090706@dgreaves.com> (raw)
In-Reply-To: <1086777225.40c6e789ade9f@www.tastycake.net>
Nick Maynard wrote:
>Måns Rullgård wrote:
>
>
>>I'm using a Highpoint RocketRAID 1540 without any problems. There
>>have been reports on this list from others having strange problems
>>with Rocket 1540 (no fakeraid) cards. <snip>
>>
>>
>Yup - that was me. The basic Rocket (not RocketRAID) 1540 card gave me /very/
>serious problems with Linux. Really - don't play with it. I managed to get
>mine RMA'd, but... blech.
>
>The Promise TX4 SATA150, on the other hand, has been nothing but a pleasure to
>work with. It's been recommended by many on this list in the past, and I will
>now recommend it to you. Yes, it's more expensive, but you get what you pay
>for.
>
>
I have one too - fairly happy (just having some raid5 resync issues but
I'm doing some diagnostics and I doubt it's the card) :)
I have wondered whether I'd have been better off with 2x Promise TX2s?
I don't know where the bottleneck is with 4xSATA disks on a single
Promise/PCI slot
Or is it a single pci bus in which case the TX4 is fine?
David
>Cheers,
>
>--
>
>Nick Maynard
>nick.maynard@alumni.doc.ic.ac.uk
>
>
You too :)
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-06-09 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 1:12 SATA chipset recomendations chris
2004-06-09 4:41 ` John Lange
2004-06-09 7:59 ` David Greaves
2004-06-09 7:08 ` Måns Rullgård
2004-06-09 10:33 ` Nick Maynard
2004-06-09 10:56 ` David Greaves [this message]
2004-06-09 11:36 ` Måns Rullgård
2004-06-09 15:37 ` Marc Bevand
2004-06-09 13:51 ` Lars Gaarden
2004-06-09 8:44 ` 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=40C6ECEE.8090706@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@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).