From: Chandra Shekhar Sah <edu4madh@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: port multiplier problem
Date: Tue, 02 Feb 2010 09:17:01 -0500 [thread overview]
Message-ID: <4B6833DD.1020001@gmail.com> (raw)
In-Reply-To: <4B679EA9.6030203@kernel.org>
Hi Tejun,
Thanks a lot for reply.
The disk array was connected to suse 10.3 before accident and was
working fine. After accident, I saw problems, so I switched to Fedora 12
because it has up-to-date sil24 driver for sata host controller sil3124.
Now, I am using Fedora 12 (kernel 2.6.31.12). The backplane card
(NORCO-LIB1220) on the disk array has 12 sata conectors, 5-5-1-1. i.e.
there are two port multiplier (sil3726, 5 sata ports in each PMP) and
two are without port multiplier, I mentioned it as "direct sata" (may be
not appropriate word).
I thought PMP is damaged so I purchased a new NORCO-LIB1220 backplane
card but same problem. The disks connected to PMP are not being
recognized. However, disk connected to "direct sata" (no disks on PMP)
is fine.
I greatly appreciate your help.
CN
On 2/1/10 10:40 PM, Tejun Heo wrote:
> Hello,
>
> On 01/22/2010 01:51 AM, Chandra Nepali wrote:
>
>> I have a disk array of 12 disks. The interface card has two sil3726 port
>> multiplier for 10 disks (5 disks in each port multiplier) and 2 direct
>> sata connectors. The host controller is sil3124. It was connected to
>> suse 10.4 and working fine.
>>
> Wasn't 10.3 the last of 10 series? After that it was 11.0. What's
> the version of the kernel?
>
>
>> There was a high voltage accident (high voltage to disk array only, not
>> computer) and because of that we replaced the power supply of this disk
>> array. Now, we are getting some problem, disks are not being
>> recognized,.
>>
> Ouch...
>
>
>> So, I connected it to Fedora 12 (To correct if it is
>> because of some bugs) with driver sil24. Here are few things that I have
>> tested.
>>
>> 1) If I connect only one disk to direct sata connector, it works fine.
>> 2) If I connect two disks to both direct sata connectors, it won't work.
>> 3) If I connect one disk to one direct sata and one disk directly to
>> host controller, it works.
>>
> What do you mean by 'direct sata'? How is it different from 'directly
> to host controller'?
>
>
>> 3) If I connect one or more disk to PM, it won't work.
>> 4) If I connect one disk to direct sata and one to PM, it won't work.
>>
> Maybe the PMP is fried?
>
> Thanks.
>
>
next prev parent reply other threads:[~2010-02-02 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:51 port multiplier problem Chandra Nepali
2010-02-02 3:40 ` Tejun Heo
2010-02-02 14:17 ` Chandra Shekhar Sah [this message]
2010-02-02 14:24 ` Tejun Heo
2010-02-02 14:59 ` Chandra Shekhar Sah
2010-02-02 16:44 ` Grant Grundler
[not found] ` <4B686B2B.2080406@gmail.com>
2010-02-02 19:04 ` Grant Grundler
[not found] ` <4B687B7C.2070406@gmail.com>
2010-02-04 2:37 ` Grant Grundler
2010-02-04 3:24 ` Tejun Heo
2010-02-04 17:59 ` Grant Grundler
2010-02-05 2:44 ` Tejun Heo
2010-02-11 20:22 ` Chandra Shekhar Sah
2010-02-04 16:39 ` Chandra Shekhar Sah
2010-02-04 3:21 ` Tejun Heo
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=4B6833DD.1020001@gmail.com \
--to=edu4madh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).