On Wed, 2009-09-23 at 18:25 +0100, Stewart Williams wrote:
> <snip>
> From those results, it doesn't look like your problem is a power issue.
> _Unless_ the drive itself has a fault. But that doesn't sound like the
> case, as it's fine on your other box.
>
> Maybe a problem with your USB port that you are plugging it into? Try
> another drive or USB device (e.g. USB flash drive) in the same port to
> see if you get any errors.
I tried the same drive on another port (different header on MB). Same
results. I *think* I tried the other drive two (I've got two identical),
but I'm unsure now. I'll fire it up and and try with the other drive
this week.
My first suspicion was old drive firmware (confirmed by the sdparm
results?) or old 4.7 driver code since 5.3 didn't do it. My second
suspicion is a flaw in the KT-440 chipset, since it didn't do it on the
KT-800 chipset.
Never got aggravating enough to google and if the OP hadn't raised the
issue I wouldn't have posted. I was just hoping a clue might be if we
had similar chipsets or driver versions involved.
> <snip sig stuff>
BTW, thanks for jumping in - I learned a bit from this.
--
Bill
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
