The fix is to cut the overhead by sending more than 4 frames per interrupt. Unfortunately that required buying a new adapter with a different chip.
So it certainly seems possible to have an additional device in the signal path.
I think I'd have accepted having two cables from the get-go. And if I observed this problem, the first diagnostic I would do is to plug the Ethernet directly into the laptop.
Fewer technical pieces in a puzzle sometimes trumps ease of use.
I understand that not everybody likes this, because it can feel like a trick, or patronizing, or lying. But in my experience, it works very well for people.
Now I feel as though my time was wasted by a dishonest author trying to get me to believe that their story was interesting when it was not.
In the grand scheme of things, it’s not a very big deal, but I feel quite annoyed since I was baited into expecting a fun read.
To pick a not-RAID example, I've got an old (2012-vintage) 180GB SATA SSD, from Intel, on my desk. It gets used as scratch space for big-ish file operations, where it gets hammered hard periodically, usually in bursts. It's plugged into a cheap SATA <> USB 3 adapter, and is otherwise-unadorned. It is bus-powered.
It's usually connected to the back of the PC, but it's been plugged into different USB ports (with different controller types) and also external hubs.
I don't recall what its exact status was when I starting doing that with it after pulling it out of a gently-used Thinkpad T530 about 5 years ago, but I do recall thinking that it had lots of life left.
Here's where it is today:
- 10.6 years powered on
- 81TB written (of 36.5TB promised); ~222% over spec
- Zero reallocated sectors
- One singular hardware-reported error (corrected)
- Zero sector reallocations
And the pièce de résistance: - Zero reported errors according to ZFS checksums
That last one is important because in this application, ZFS automatically and continuously provides end-to-end verification, and it's been doing...perfectly fine.The other USB storage devices here that are used 24/7 are similar in this way. It's not hellish at all. It's quite lovely.
I'm inclined to further extrapolate that it would not have better data integrity when connected directly to a SATA port on the motherboard, or in a disk shelf attached via iSCSI or SAS or some other more-stodgy thing. It's hard get results that exceed beyond perfection.
(But in this example, I'm not chasing down minute bus timing issues with multi-gig networks. That's a very different kind of discussion.)
Your assertion doesn't seem to align with the article itself.
Need more proof?