From: Tejun Heo <htejun@gmail.com>
To: Tony Mugan <tony@mugan.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: SIlicon Image Controller 3512A or Seagate Barracuda ST3160827AS Issue
Date: Mon, 21 Jan 2008 17:31:39 +0900 [thread overview]
Message-ID: <4794586B.7050706@gmail.com> (raw)
In-Reply-To: <4764b0290801192151h15405acahda1769621ba3b4cd@mail.gmail.com>
Tony Mugan wrote:
> Hello Jeff,
>
> I've tried a few recent Kernels (incl 2.6.23.14) attempting to have my
> SATA Raid configuration detected to no avail. My SATA drives are not
> on your blacklist in sata_sil.c so I decided to contact you to see if
> I am missing something or can offer a testbed to get this resolved.
>
> I have found a kernel forum posting from you back in 2004 relating to
> an issue with a slightly different Sil controller but the same drives.
> http://www.ussg.iu.edu/hypermail/linux/kernel/0412.0/0535.html
> You refer to updates in firmware resolving Raid-related issues but I
> cannot find any updates beyond my current v3.42 for these drives. Nor
> were there an newer Mobo firmwares beyond "FK" which I have installed.
>
> I'd be grateful for any pointers and would be very interested in
> assisting where I can in providing information if possible.
>
> I have attached some general information regarding my setup.
Please read the following page.
http://linux-ata.org/faq-sata-raid.html
BIOS RAIDs are supported via device mapper. I dunno which format the
sil controller uses and whether dm supports it tho. Unless you have to
use it for another OS, BIOS raids are usually worthless marketing crap.
Just use software RAID (md).
Thanks.
--
tejun
prev parent reply other threads:[~2008-01-21 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 5:51 SIlicon Image Controller 3512A or Seagate Barracuda ST3160827AS Issue Tony Mugan
2008-01-21 8:31 ` 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=4794586B.7050706@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=tony@mugan.com \
/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).