From: Kevin the Drummer on
Grant Edwards <invalid(a)invalid.invalid> wrote:
> On 2010-04-10, Kevin the Drummer <nobody(a)cosgroves.us> wrote:
> > Grant Edwards <invalid(a)invalid.invalid> wrote:
> >
> >> > This may have no impact in this case, but I can't think of any other
> >> > reason why the use of usb to access the drive would fail, while the
> >> > same drive works fine when internally connected, other then a problem
> >> > with the enclosure.
> >>
> >> I think you've hit the nail on the head: the USB<->IDE chip in the
> >> enclosure is buggy.
> >
> > Is there a USB<->IDE chip in my enclosure if it supports SATA
> > drives and not ATA (IDE) drives?
>
> No, then it's a USB<->SATA chip, and it's probably buggy.

I should have tried to note the chip number/vendor. But, I boxed
it all up for the RMA. Does Linux support work around buggy
chips at times? I wish I could have reported this, or at least
looked at the kernel mailing list to see if the chip showed up
their.

I wonder if enclosure vendors change such things as often as
wireless ethernet vendors change the chips they use in their
designs.

Thanks for the assist folks!

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.
From: Grant Edwards on
On 2010-04-12, Kevin the Drummer <nobody(a)cosgroves.us> wrote:
> Grant Edwards <invalid(a)invalid.invalid> wrote:
>> On 2010-04-10, Kevin the Drummer <nobody(a)cosgroves.us> wrote:
>> > Grant Edwards <invalid(a)invalid.invalid> wrote:
>> >
>> >> > This may have no impact in this case, but I can't think of any other
>> >> > reason why the use of usb to access the drive would fail, while the
>> >> > same drive works fine when internally connected, other then a problem
>> >> > with the enclosure.
>> >>
>> >> I think you've hit the nail on the head: the USB<->IDE chip in the
>> >> enclosure is buggy.
>> >
>> > Is there a USB<->IDE chip in my enclosure if it supports SATA
>> > drives and not ATA (IDE) drives?
>>
>> No, then it's a USB<->SATA chip, and it's probably buggy.
>
> I should have tried to note the chip number/vendor. But, I boxed it
> all up for the RMA. Does Linux support work around buggy chips at
> times?

I'm not aware of anything like that. Your best bet is to check to see
if there's a a firmware update for the enclosure. That fixed problems
I had with one particular case.

> I wish I could have reported this, or at least looked at the kernel
> mailing list to see if the chip showed up their.
>
> I wonder if enclosure vendors change such things as often as wireless
> ethernet vendors change the chips they use in their designs.

Unfortunately, Yes.

--
Grant Edwards grant.b.edwards Yow! Either CONFESS now or
at we go to "PEOPLE'S COURT"!!
gmail.com
From: Jerry Peters on
Kevin the Drummer <nobody(a)cosgroves.us> wrote:
> Jerry Peters <jerry(a)example.invalid> wrote:
>
>> I'm assuming you meant 2TB.
>
> Yes. It'll take me a while to type a T instead of a G, like when it
> took a while to get over the M or change the year when I write checks
> (what are those?).
>
>> Should be fine from the adressing standpoint. I'd still guess
>> bad SATA to USB bridge chip, or poorly designed enclosure
>> (marginal power supply, poor pcb layout, etc). A lot of these
>> enclosures are just plain junk.
>
> I'm thinking I've either got bad gear, or incompatible gear. The
> enclosures have an RMA and I'll be sending them back, trying NexStar
> next.
>
> Thanks....
>
I did see one post to lkml recently about a SATA drive (WD I think)
that needed to have ajumper set to a slower transfer rate because it
would negotiate the slower rate, but then use a faster rate. You could
be experiencing an incompatability of this type.

Jerry
From: Kevin the Drummer on
Yesterday my new USB2 NexStar enclosure arrived by UPS. Within
10 minutes I had the unit installed. It works perfectly, and
data transfers are very fast. I sort of wish that I would have
bought an eSATA card for my computer and the eSATA capable
NexStar enclosure. But, maybe I'll do that next time. The USB2
NexStar enclosure is just fine.

FYI...

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.