Date: Sun, 30 Nov 2003 02:13:03 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Will Andrews <will@csociety.org> Cc: current@freebsd.org Subject: Re: Western Digital WD360GD SATA disk on -CURRENT Message-ID: <1070176383.68747.176.camel@shumai.marcuscom.com> In-Reply-To: <20031130070051.GN431@sirius.firepipe.net> References: <20031130045604.GM431@sirius.firepipe.net> <1070174954.68747.162.camel@shumai.marcuscom.com> <20031130070051.GN431@sirius.firepipe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sun, 2003-11-30 at 02:00, Will Andrews wrote: > On Sun, Nov 30, 2003 at 01:49:14AM -0500, Joe Marcus Clarke wrote: > > I have a host controller with the same chipset. I was having frequent > > data corruption problems, so I asked about it on current@ a few days > > ago. so@ offered a patch (which has now been comitted), but it didn't > > help. Bottom line, he said to get a Promise SATA card. Since I don't > > want to mess around with this anymore, I went to Amazon, and ordered > > one. In looking at this output, I doubt the patch would even affect you > > since you're using the new hardware revision. > > > > For more details, check the archives for current@ for a thread with the > > subject, "Recent ATA drivers giving problems with SATA." > > Yeah, that's what I figured. When I looked at the change, the > fix only appears to affect rev 0x00, but my SiI3112A is 0x02. :( > > Well, I can tell you that people aren't gonna be happy when their > brand new motherboard that comes with SiI SATA builtin doesn't > work with their SATA disks (or well, just this one?). Since > SiI's are so cheap (and fairly common), I'd consider this a > showstopper as far as SATA goes. I agree. I really needed to be up and running ASAP, so I opted for the new controller. Søren, if you're listening, and need an SiI controller for testing, you're free to have mine. Else, I can keep it and test it as needed (I can put a test drive on it). > > This thing used to work, it should be fixed. Besides, I simply > don't have the money to spend on another SATA controller for my > main workstation just so it can run up-to-date -CURRENT. :( I have a basic time line. Everything worked fine until I upgraded on November 18 at 02:23 UTC. I had a 160 GB Seagate SATA drive running on the same chipset for about a month before that. As soon as I rebooted on the new kernel, everything went south. Until Søren told me about the buggy chipset, I was going to back my ATA drivers back to November 11, 2003 00:00 UTC, and see if that helped. That was right before a big change went into the driver. Joe > > Regards, -- PGP Key : http://www.marcuscom.com/pgp.asc [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/yZh/b2iPiv4Uz4cRAgacAJ9gQ6rzQbeefvIRt+bYJhx6lcbtxQCfRv+X b3IzfNiRx64f5d23z7PcDQo= =XVYr -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1070176383.68747.176.camel>