Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Sep 2003 02:45:28 -0500
From:      Derek Ragona <derek@computinginnovations.com>
To:        Will Andrews <will@csociety.org>, Soren Schmidt <sos@spider.deepcore.dk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
Message-ID:  <5.2.1.1.2.20030930022717.012dd740@www.computinginnovations.com>
In-Reply-To: <20030929193808.GT72999@procyon.firepipe.net>
References:  <200309291913.h8TJDmCI013173@spider.deepcore.dk> <61180692781.20030929202947@buz.ch> <200309291913.h8TJDmCI013173@spider.deepcore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
My troublesome system uses an Adaptec Serial ATA RAID 1210SA which has the 
SiI3112 RAID chip.  I have only one drive connected, so no RAID functionality.

Here is my verbose dmesg using the 9/28/03 snapshot:
http://www.computinginnovations.com/dmesg.html

         -Derek



At 12:38 PM 9/29/2003 -0700, Will Andrews wrote:
>On Mon, Sep 29, 2003 at 09:13:48PM +0200, Soren Schmidt wrote:
> > First off, there is ONLY support for Promise and HPT "soft RAID"
> > in the ATA driver, other vendors products are *not* supported (yet).
> >
> > Second, there seem to be a problem with some sil3112 setups where
> > timeouts and what not ruins the lunch, but so far I've not been
> > able to reproduce..
>
>I am still unable to use my SATA drive, it's probed incorrectly
>as I posted earlier.  Reverting to the August 10th 00:00 UTC
>kernel fixes this problem, so I concluded that ATAng broke this.
>
>If it makes any difference, my model is a SiI3112 RAID
>controller, but I only have one drive and it probes as ad4... the
>situation doesn't improve any if I add "ataraid".  But maybe
>ATAng doesn't take into account the difference between a "normal"
>and a "RAID" SiI 3112, if any?
>
>Here are my dmesg's again (Sep 18th, Aug 10th kernels):
>http://csociety.org/~will/dmesg.badATAng
>http://csociety.org/~will/dmesg.Aug10.preATAng
>
>The problem shown in the first dmesg still showed itself when I
>tried a new kernel on Sep 25th.
>
>Regards,
>--
>wca
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.1.1.2.20030930022717.012dd740>