Hi Peter, Thanks for the clarification - as you said:
pmokover wrote:A little misunderstanding here.
Indeed, I misunderstood.

When you said:
pmokover wrote:I finally got a USB3-SATA adapter and connected an old drive and it seems to be working OK.
... I had interpreted that "old drive" to be one of the "old" LaCie drives (which you must therefore have taken out of its case, since you were using it with a different USB-SATA bridge).
The picture is a little clearer now, but I doubt that I'll get to root cause without having the drives here.

There are many possible troubleshooting approaches I can see, depending on available time, money & equipment. I'll suggest some thoughts that I have below, but as I said, the limitations of remote diagnosis along with the lack of info about the USB or SATA I/O during the "stall", are a problem IMHO.
As I suggested before, looking at what the system is doing during the (up to 1min) "stall" when using the "problem" drives, would quickly point in the direction of the problem - i.e. what is actually causing that "stall". I realise that another piece of unclear info is whether that "stall" occurs for
every access to a "problem" drive; or just the
first access after the "problem" drive is
attached; or just the
first access to a "problem" drive which needs the drive to
spin-up; or something else. You mentioned that the "stall" occurs with
writes - what about
reads? Does the "stall" occur when a "problem" drive is the
first one attached to a PC after a power-on, and
not following from the "good" drive being attached? The timing of when you're attaching "good" and "problem" drives during the testing, wasn't clear to me from your earlier comments. All these answers may also tell you something, about when the "stall" is, and is not, triggered.
Techniques for examining what is happening during the "stall", would include using a USB or SATA protocol analyser - but hardware protocol analysers are expensive; software-based USB protocol analysers exist, but then you've still got to spend time looking at what gets captured, and interpreting it. Earlier I also suggested looking at the Windows system event log, to see if that gave you any clues.
Another piece of unclear info, is whether this is a USB-powered drive, or an externally-powered drive - I saw LaCie 1TB USB3 drives of both types advertised. Although USB3 increased the power which can be drawn from a port, if yours is a USB-powered drive, could a change in power requirements between the "good" and "problem" drives, be involved in the behaviour that you see?
As I understand the results of your recent test, due to the limitation that you don't want to open the LaCie enclosure, the only conclusive test result is that you
don't have a generic USB3-related issue on your PCs, due to the different USB3-SATA bridge working OK; but we knew that already, since your "good" USB3 drive works, didn't we?
I was wondering whether the other slightly unusual part of your config, could be related i.e. you're connecting multiple identical drives (individually) to the same system. Most buyers of these drives won't be doing that, will they? Therefore I'm thinking that you could be affected by something which other users (and also LaCie support) may be unaware of. Are these different drives being correctly recognised as different drives - are they reporting different USB h/w serial numbers? At one stage, when I had more Windows driver involvement than I do now, I think it was a requirement that all mass-storage devices did have unique USB serial numbers, if you were going to connect more than one to a system (or to swap between them).
What opportunities do you have for trying the "problem" drives (NOT the "good" one!) on other PCs, even just on a USB2 port? If you can find
any other PC where the "stall" does not occur (doing whatever test causes that "stall" on your normal PCs), then that would be an important result.
So those are the types of areas I would investigate, if I was in your situation, with the drives in front of me (except I'd also be using a protocol analyser to look at what happens during the "stall"). Hope that gives you some ideas.