linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: PairOfTwins <PairOfTwins@mindspring.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Accessing 3.4 TB RAID Drive
Date: Tue, 28 Oct 2008 11:01:39 +0900	[thread overview]
Message-ID: <49067283.7040306@kernel.org> (raw)
In-Reply-To: <4901CDDB.8000409@mindspring.com>

PairOfTwins wrote:
> Folks (I was referred here by my local Linux group):
> 
> I'm replacing RHEL 3.2 with something newer, and need to access an
> external eSATA RAID array (Venus T5, Sil4726 chipset) about 3.4 TB.
> 
> Using a RIP (Recovery Is Possible) Live CD, I was able to read the GPT
> partition table and attempt to mount the device (though it was flagged
> dirty), on one test system.
> However, after installing Ubuntu Server 8.04 and 8.10 beta on a
> production box, I'm getting lots of errors.  One big difference, though,
> is the RIP test was using PCI eSATA card (Silicon Image Sil3124), and
> the production box has PCI-E eSATA card (Sil3132).
> 
> With Ubuntu Server 8.04 fully updated, kernel 2.6.24-21-server, driver
> sata_sil24, syslog says:
...
> Any hints appreciated, like what software needs updating, or shall I
> replace PCI-E card with PCI ?

That's because sata_sil24 supports PMP and 4726 is a (weird) PMP device.
 If you use PMP reset protocol, it reveals more about itself and when
the device is configured in hardware raid mode, it presents pseudo
devices on PMP links which doesn't behave in accordance with the ATA
spec and doesn't like libata's init sequence.  Just put 4726 into JBOD
mode and sil24 will happily see all the individual disks.

Thanks.

-- 
tejun

      reply	other threads:[~2008-10-28  2:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 13:30 Accessing 3.4 TB RAID Drive PairOfTwins
2008-10-28  2:01 ` Tejun Heo [this message]

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=49067283.7040306@kernel.org \
    --to=tj@kernel.org \
    --cc=PairOfTwins@mindspring.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).