Re: Western Digital WD360GD SATA disk on -CURRENT

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_at_ a few days
> > ago.  so_at_ 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_at_ 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