From: Erik Slagter <erik@slagter.name>
To: David Greaves <david@dgreaves.com>
Cc: Brad Campbell <brad@wasp.net.au>,
linux-raid@vger.kernel.org, IDE Linux <linux-ide@vger.kernel.org>
Subject: Re: Problems with multiple Promise SATA150 TX4 cards
Date: Wed, 25 Jan 2006 11:04:45 +0100 [thread overview]
Message-ID: <1138183485.27604.49.camel@localhost.localdomain> (raw)
In-Reply-To: <43D66681.708@dgreaves.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Tue, 2006-01-24 at 17:40 +0000, David Greaves wrote:
> >> sounds like a spinup time on marginal power to me.
> > No, it's a limitation of the Promise BIOS on the cards, it will only
> > detect a maximum of 8 drives. I had a quick convo with tech support
> > from Promise over this and they told me they don't support more than
> > one card in a machine in any case. (Which is odd given they advertise
> > the ability to RAID-5 across 2 cards!)
> > <snipped the rest about power issues>
I'd really consider the PSU. I had all sorts of weird problems with my
promise SATA150 TX2plus until I replaced the PSU. Apparently it doesn't
suffice to supply _enough_ power.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]
next prev parent reply other threads:[~2006-01-25 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 2:01 Problems with multiple Promise SATA150 TX4 cards Christopher Smith
2006-01-24 6:39 ` Mark Hahn
2006-01-24 6:58 ` Christopher Smith
2006-01-24 9:11 ` Brad Campbell
2006-01-24 13:27 ` Christopher Smith
2006-01-25 0:15 ` Christopher Smith
2006-01-25 5:33 ` Mattias Wadenstein
2006-01-24 17:40 ` David Greaves
2006-01-25 10:04 ` Erik Slagter [this message]
2006-01-26 0:26 ` Christopher Smith
2006-01-26 11:35 ` Erik Slagter
2006-01-26 14:22 ` David Greaves
2006-01-26 14:44 ` Hans Kristian Rosbach
2006-01-27 6:00 ` Mitchell Laks
2006-01-27 13:21 ` berk walker
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=1138183485.27604.49.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=brad@wasp.net.au \
--cc=david@dgreaves.com \
--cc=linux-ide@vger.kernel.org \
--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).