Yes agreed, all that is true. Regardless of the reason, Unraid takes a different approach and has different tradeoffs which enable partial recovery in the SHTF scenario. I prefer the Unraid approach - plus it is more intuitive and feels simpler for me.
Sure, if you’re using ZFS’ RAID1 and lose 2 drives, it all goes. Or RAID2 and lose 3 drives, it all goes. Because the data is allocated across many drives, there is not a fundamental “one file one drive” scenario if SHTF.
Whereas with Unraid, one file on one drive, with a parity check (or two) if you need to recreate.
As someone who went the other way - proxmox and TrueNas -> Unraid, I would caution you to think twice against going that way. You’ve admitted having issues with Unraid configuration, and TrueNas is significantly more complex (especially if you layer in proxmox). You’ll just be throwing away all the knowledge you have about Unraid and jumping into another setup where configuration is important. Except, in this case, if you screw up the ZFS setup you risk losing ALL YOUR DATA.
Something doesn’t quite add up. How are you downloading 3TB a day and expecting it to fit into your existing drive setup? I would really recommend just biting the bullet and getting 2x4TB cache drives that you could fill up and then let the slow writes to array take over. If you’re telling me that you do 3TB every day, then what is your plan for 30 days from now when you’re out of array space?
Something doesn’t quite add up - I’m not doubting you, but I think your frustration is pushing you to make a change, even if that change might not be the best for you in the long run.
All that is to say, please don’t jump to TrueNAS with prod data for your first experience.
That’s quite a lot, I have a brand new tower I just built that pulls 53w when idle. 10 core intel gen13 with 3 nvme, 2 ssd, and 2 spinning drives.