While that's the ARC, I would be surprised if they blocked you from building vdevs with SSDs.

Looking at the specs: https://store.ui.com/us/en/category/network-storage/products...

Hard Drive Capacity

(16) 2.5/3.5" HDD / SSD support

(2) M.2 NVMe SSD support

(2) Expansion ports support

I think you're right we only get two SSDs on NVME as the cache, but it looks like we can run the rest (16) as SATA SSDs, which is often fine if you primarily care about random IOPS and capacity over pure throughput.

Would you consider that a dealbreaker?

▲

kube-system 2 hours ago | parent [-]

No I think it's perfectly fine, if I'm accessing files over a network I don't expect them to be blazing fast anyway.

▲

bhouston an hour ago | parent [-]

FYI: you should upgrade to 10gbe if your network is slow. It isn't that expensive these days: https://ben3d.ca/blog/home-network-lessons

▲

avtar 31 minutes ago | parent | next [-]

Not sure if you've looked into this but you can ditch Bell's router with one of these:

https://store.10gtek.com/1-25g-media-converter-sfp-slot-with...

Or a non-copper equivalent in your case. You just need to use the VLAN IDs that Bell expects, see https://www.reddit.com/r/bell/s/uUltTdyqFC

	▲	bhouston 15 minutes ago \| parent [-]
		I did end up ditching the modem since I wrote the article. I ended up using a TP-Link 8411 router though. Having everything TP-Link has its benefits for observability and maintenance.

▲

kube-system 22 minutes ago | parent | prev [-]

That's still only 1/3rd of a single U.2 or a 6th or single U.3 drive... and the IOPS over SMB/NFS is significantly lower than a local drive, even with a big ethernet pipe.