SCIENTIFIC-LINUX-USERS Archives

July 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Andras Horvath <[log in to unmask]>
Reply To:
Andras Horvath <[log in to unmask]>
Date:
Wed, 2 Jul 2014 17:41:53 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
On Wed, 2 Jul 2014 10:17:32 -0400
Lamar Owen <[log in to unmask]> wrote:

> On 07/02/2014 03:14 AM, Andras Horvath wrote:
> > Anyway I tried to raise those values high again and it seemed to have 
> > enter that hanging state at once. Interesting. I also checked the SATA 
> > possibility and it's working just fine if no USB is involved in the 
> > story. Since I have no more idea, I'll stick with the SATA version. 
> > Thanks. Andras 
> 
> That's good to hear that the SATA connection works for you; that tends 
> to eliminate the drive itself as being the source of the issues, and 
> narrows it down to the USB stack and all of the hardware involved.
> 
> If you are still interested in troubleshooting why the USB stack is 
> causing this issue, it might be instructive to compare the USB to SATA 
> bridge chips used by your enclosures.  Likewise the cables.

Also, the data throughput was ok too on SATA setup (varying around 120 MB/s).

ATOM RSS1 RSS2