From: Fabian Knittel <fabian.knittel@avona.com>
To: linux-ide@vger.kernel.org
Subject: Re: Problems with Promise SATAII TX4
Date: Tue, 23 Aug 2005 14:58:06 +0200 [thread overview]
Message-ID: <430B1D5E.9070201@avona.com> (raw)
In-Reply-To: <430404A5.7060000@avona.com>
Hi,
I wrote:
> I'm experiencing problems with my Promise SATAII TX4 controller, quite
> similar to what Kim reported a few months ago.
>
> Using a fresh linux-2.6.12.5 upstream kernel to boot into a rescue shell
> (so there's no distribution specific stuff going on, nothing else
> loaded, etc.), I can access my three connected Maxtor 120GB drives just
> fine, as long as I do so individually.
[...]
>>Attached devices:
>>Host: scsi0 Channel: 00 Id: 00 Lun: 00
>> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
>> Type: Direct-Access ANSI SCSI revision: 05
>>Host: scsi1 Channel: 00 Id: 00 Lun: 00
>> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
>> Type: Direct-Access ANSI SCSI revision: 05
>>Host: scsi3 Channel: 00 Id: 00 Lun: 00
>> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
>> Type: Direct-Access ANSI SCSI revision: 05
OK, apparently it's somewhat hardware related after all. I've added a
Seagate drive (Model: ST3120827AS, Rev: 3.42) and reading from this
drive together with two of the Maxtor drives (any two of the three)
currently works without problems (for now).
Switching ports and cables doesn't change anything, so it's not related
to that.
But how can that be? The individual drives don't reveal any problems and
(as reported in my previous mail) the drives worked seamlessly for a few
weeks ...
I'll have to do some more testing and this is probably off-topic by now,
so I'll stop with the noise now.
Fabian
next prev parent reply other threads:[~2005-08-23 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 0:10 Problems with Promise SATAII TX4 Kim Roland Rasmussen
2005-03-31 20:34 ` Joe Harvell
2005-08-18 3:46 ` Fabian Knittel
2005-08-23 12:58 ` Fabian Knittel [this message]
2005-10-08 13:12 ` Fabian Knittel
2005-10-08 17:06 ` Mark Hahn
2005-10-10 10:29 ` Erik Slagter
2005-10-10 10:23 ` Erik Slagter
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=430B1D5E.9070201@avona.com \
--to=fabian.knittel@avona.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).