Oh no.
Unfortunately I have a lot of experience with this: attaching permanent array members via USB is a bad idea. OP, if it's not too late, and assuming you haven't already and decided to double down on yolo, I'd recommend reading about the downsides of this approach. It is easy to find relevant discussions (and catastrophes) in r/zfs.
Thunderbolt enclosures are a bit more expensive, but they won't periodically fuck up your shit just because.
Thanks for the warning ⚠️🙏
This isn't my first rodeo with ZFS on USB. I've been running USB for a few years now. Recently I ran this particular box through a battery of tests and I'm reasonably confident that with my particular set of hardware it'll be fine. It passed everything I threw at it, once connected to a good port on my machine. But you're generally right and as you can see I discussed that in the testing thread, and I encountered some issues that I managed to solve. If you think I've missed something specific - let me know! 😊
Is it because USB doesn't expose proper UUIDs or something?
Bus issues usually. Having a disk (or 4) drop out of a ZFS filesystem regularly isn't a good time.
If you can find a combination of enclosure, driver/firmware and USB port that provides you with a reliable connection to the drive then USB is just another storage bus. It's generally not recommended because that combination (enclosure, chipset, firmware, driver, port) is so variable from situation to situation but if you know how to address the pitfalls it can usually work fine.
Been on USB enclosures using Linux software raid for 20 years and never lost a bit so far.
Didn't go cheap with USB jbod, and i have no idea if zfs is more sensitive to USB... But I don't use zfs either so don't know.
But again I have been using two jbods over USB:
- 4 SSDS split on two RAID1s on USB3
- 2 HDDs on RAID1 on USBC
All three raid are managed by Linux software raid stack.
The original one I think I started in the 2000's, then upgraded disks many times and slowly moving to ssds to lower heat production and power usage.
Keep them COOL that's important.
I've been on the USB train since 2019.
You're exactly right, you gotta get devices with good USB-to-SATA chipsets, and you gotta keep them cool.
I've been using a mix of WD Elements, WD MyBook and StarTech/Vantec enclosures (ASM1351). I've had to cool all the chipsets on WD because they like bolt the PCBs straight to the drive so it heats up from it.
From all my testing I've discovered that:
- ASM1351 and ASM235CM are generally problem-free, but the former needs passive cooling if close to a disk. A small heatsink adhered with standard double-sided heat conductive tape is good enough.
- Host controllers matter too. Intel is generally problem-free. So is VIA. AMD has some issues on the CPU side on some models which are still not fully solved.
I like this box in particular because it uses a very straightforward design. It's got 4x ASM235CM with cooling connected to a VIA hub. It's got a built-in power supply, fan, it even comes with good cables. It fixes a lot of the system variables to known good values. You're left with connecting it to a good USB host controller.
WD PCB on disk
I imagine if someone had to do it this way for whatever reason, Thunderbolt would be more reliable? Assuming it’s true Thunderbolt using a SATA bridge?
Yes - and unless you treat each enclosure as its own failure domain, it will still be a compromise, but it's a lot better.
What are you putting in them?
- 8x 8TB in a set of 2, some shucked WDs, some IronWolfs
- 5x 16TB in a set of 2, "recertified" WDs from serverpartdeals.com
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters More Letters PCIe Peripheral Component Interconnect Express SATA Serial AT Attachment interface for mass storage ZFS Solaris/Linux filesystem focusing on data integrity
3 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #668 for this sub, first seen 9th Apr 2024, 13:55] [FAQ] [Full list] [Contact] [Source code]
