I cannot be certain (not having used a T6-423 myself) but I have been pretty happy with my F5-221 which has far less CPU power.
You will need the 32GB upgrade - memory is probably more important for TrueNAS than CPU.
The key thing about TerraMaster units is that they come with an internal USB socket / Flash drive that has a special install O/S to allow you to install their NAS over a network onto a SATA drive in one of the bays. This is not needed (and should be removed) if you are going to run TrueNAS.
You then need to decide whether you are going to use one of your SATA ports/bays for a boot drive or (do as I did and) break an iX support rule and use a USB SSD (NOTE: not a USB flash drive - a proper SSD) for your boot drive.
Thanks, so I could use a m.2 ssd for truenas, think I would need the smallest possibly which is 500gb.
Memory wise the Terramaster memory is extortionate, they say you can upgrade to 32gb if you use Terramasters own but the main board only shows (on intel) as supporting 16gb. I am sure if I am using Truenas I can use whichever brand possible and might be work a try.
On the note of m.2 ssd and memory upgrades, would you recommend any particular brands or are they a bit of a muchness or any I should avoid?
Thanks
Ah - I didn’t realise it has an M.2 slot. So yes, use that for boot - and smallest possible drive.
You then need to decide whether you want to break another support rule and use only part (say 32GB) for the boot-pool and use the rest for e.g. an apps-pool. Unless you have a second M.2 slot, you won’t be able to mirror it without using a SATA port, but you can replicate it to your HDD-pool as a backup.
Alternatively, you will need to dedicate the full 500GB for the boot pool, 95% of which will never be used.
For memory, if the MB supports ECC then definitely buy ECC - otherwise I would personally use a reputable brand such as Crucial or Kingston bought from a reputable (i.e. non-fake) source. (This is not an area to save a handful of $$ on.)
Thanks it does have a second m.2 slot so if this is the case, what is the best way to set this up from the start, are you suggesting I would have one m.2 ssd for boot and a second for apps pool and would I only need two two small m.2?
Seems a bit of a waste of two m.2 slots but if this is the correct way to do it then so be it.
Great, im starting to get the picture now. So if I get one ssd that is 256GB for the operating system, what size would you suggest for the apps pool, maybe the same or 1tb?
I do have another question in preparation for it arriving.
As I only have apple MacBooks can you suggest how to create bootable ssd, I have read about Rufus but its not available on Mac and im nervous just downloading some random software. I was thinking that I might need a NVMe enclosure as well or if you can suggest another way.
Thanks again for your help, I really appreciate it.
P.S. If you want to run VMs, then replication is not a good solution because the virtual disks will not replicate nicely. You will really need a mirrored pool for VMs.
The apps-pool is probably mis-named - perhaps better called an ssd-pool (by comparison to the hdd-pool) because you will want to store on it all the apps data as well (which for Plex / Jellyfin will be all the metadata they build to index the videos you store). But so long as TrueNAS can see each file individually (and they are not hidden in virtual disks), then it should replicate for backup ok.
The size of you ssd-pool disk will depend on what you need to do with it, but I suspect that a 256GB or 512GB drive should be quite adequate in many cases.
(And sorry, I cannot advise on how to create a bootable flash drive for TrueNAS install on a Mac as I haven’t used one of those for c. 35 years.)
In my experience Zvols for VM disks, incremental snapshots, and replication work very well together. The destination will consume as much ZFS space as the source.
Or I am missing something different that you are hinting at?
The new F4-424 etc… models have NVMe internally haven’t tried booting from one but I bet they would. In which case you could go back to a supported boot method on those models.