PsychoWards

Hey, yes this is not that difficult to do, I have done this in the past with various different NAS constellations. With Hexos you have 2 options: If you want to backup to another Hexos or Truenas you should use ZFS replication. (this is not your usecase) If you want to backup to a NAS which is not using ZFS you should do the backups using rsync. For rsync you need to configure both your Synology NAS as a server and your Hexos as a client (this needs to be setup in Truenas, Hexos doesn't offer this yet).

Mounting using fstab would have been my next advice, but I couldn't edit my post anymore so I was waiting for your feedback first. Keep us posted if it helps 😃

Hey, The problem with the high memory requirements is not directly Hexos or Truenas for that matter but ZFS itself. For example as a rule of thumb you need 1GB or memory for ever TB of storage, in your case that's already 7GB of memory. Then you also need 1/2-1GB for the write cache and additional memory for parity data calculation. So with your config you easily need 8-10GB of memory just for ZFS, add 1GB for Hexos and you see why the minimum required memory is so high and why you are facing issues with only 2GB of memory. Supporting low memory systems would require a lot of changes to ZFS which might result in suboptimal or bad performance. You can check this link for memory information: https://web.archive.org/web/20140818042550/http://hardforum.com/showpost.php?s=8d31305e57c1dd2853eb817124ff18d9&p=1036865233&postcount=3

Not yet, but the MMU3 support will come 🙂

Check out the new Prusa Core One with the MMU3. Checks all our boxes and it offers unparalleled upgradeablity. Prusa does offer an upgrade Path to the latest printer each time and this way to can easily upgrade and don't need to buy a new printer each time a new model is released.

Do you have the possibility to set the smb version? Can you force to use V3?

What distro are you using and can you share your fstab entry for the smb mount? (or however you are mounting your samba share)

Hey, you can use this raidz calculator, set number of disk groups to 1 and fill in all other numbers. If yoh have 3 or more disks hexos will create a raidz1, so you set this as raidz type and you get your usable storage in TB. (Don't forget to convert this to TiB) https://www.raidz-calculator.com/

In that case, use any gpu which you have at home for the initial setup or try do borrow one from a friend and check if the motherboard starts headless (without gpu) after the installation and if Hexos is accessible. If it is working fine without gpu after the setup you don't need to buy an extra gpu just for the server.

Hey @NaZzAtAzEr, What do you plan to do with your Hexos? Do you need the GPU only for video output or do you want to do some video transcoding with Plex/JellyFin? If you only need it for video out for the installation you can use any GPU and if you don't have one maybe you can borrow you from a friend. If you plan to do more with it, we need to know before we can give a proper recommendation.

I'm using a RaidZ2 without any issues, but I'm also not using any of the apps, since I'm running an Ubuntu VM with docker for all my apps. I didn't follow all the discussions but it seems that destroying the first pool created results in apps become unusable until some paths/settings are fixed in TrueNas, but don't quote me on that, maybe someone else has more information about this. To add to @Mobius explanations about the Vdevs: Once you loose all the drives from 1 vdev you loose everything. Meaning with 3x2 drive vdevs you can only loose 1 drive per vdev (but 3 drives in total if they are all from different vdevs) and with 2x3 drive vdevs you can loose 2 drives per vdev without loosing any data. @L-Pif you have 10 gbit/s networking, you might want to look into adding an nvme cache drive as an L2ARC. ARC is a read only cache, which is keeping the files which you might need next in a cache in memory for quick access. You can extend this with an L2ARC cache which, stores additional files on a dedicated drive. If this drive is an SSD it's gonna ready and serve those files significantly faster then if Hexos needed to read them from the slow HDDs. This might make sense in your case if you have 10gbit/s networking, everything below and the speed benefits are likely to be marginal at best. And no there is no write cache in Hexos only a read cache. 🙂

Exactly and depending on your usecase it might be hit or miss, if the ARC is caching the wrong files. For most user's it's not really useful except if you absolutely need the faster read speed of an m.2 SSD or your are doing a lot of video/image editing. If you just use your NAS as a backup, media storage solution, the L2ARC is very likely not needed. It's possible that you were transfering a lot of small files earlier, which could explain the 30MB/s you saw earlier. The connection is always taking the shortest path, if your PC and Server are connected to the same switch, they will not pass through the router.

That does look like a proper setup =D Is everything connected to your UPS? Concerning your copying speed, can you try copying from and to another device, to see which system might be the issue? If you're not finding a conclusive answer, you can create another topic in the support forum to get some more help on this matter. There is no write cache in Truenas/Hexos there is only L2ARC. This is an extension of the ARC which is running in memory. The ARC is buffering files which truenas thinks you might use next, to have them ready in memory and not needing to ready it from the drives. The L2ARC is an extension and it's keeping more files on the cache drive. It is a read only cache.

There are SFP modules with an RJ45 connector with up to 10Gbit/s, you don't need to go to fibre yet. If you can't or don't want to use the SFP card, it might be worth to consider getting a 2.5 Gbit/s card instead of a 1Gb card, they are not that much more expensive and it avoids you the need to upgrade the NIC afterwards, especially since 2.5Gbit/s switches are no longer expensive.

Can you give os more details on your SFP Network cards? You might be able to reuse them and just get an SFP Module

Onboard SATA Ports should be the least of your concerns when choosing a Motherboard, since you can easily add more SATA ports with HBA PCIe cards. I agree with @Dylan use your current machine, add some RAM and get a feeling for everything and for your needs (especially VM and Docker stuff). Maybe you get into Machine Learning (face recognition in Immich, AI OCR in paperlessngx etc...) and you need a potent dedicated GPU or you are only running lightweight apps and you can continue using your current server for the years to come.

Can you even reinstall an already installed app? Does Hexos allow you to do this? Do you mean if an app was installed via Truenas and it becomes a Hexos curated App that it is prefilling all the fields based on the current installation or if the App was installed via Hexos and you want to reinstall or both?

The Synology NAS is going to life at my parents house once the initial backup was made, so even if the entire building burns down, I'll have a backup. (So yes, indeed planning for the worst case) I'm only backing up the important things, for the rest, snapshots need to be enough.

Once you figured out the best/optimal settings for your use case(s), could you possibly release a recommended/curated settings guide, I would be very interested in this. It probably will not be the optimal configuration for every single usecase but probably already a good baseline for most cases, especially since most Youtube videos concerning setting up Truenas recommend outdated and suboptimal settings.

I'm running an Ubuntu VM which is hosting all of my docker containers, it's running Hexos to do NAS things and I will migrate my Windows Server over to proxmox as well, the windows VM will only run when I need to do windows thingy things. (Mainly Gameservers)

I cannot exactly answer you what you can do in Truenas concerning Apps/VM, however there are 2 approaches which would likely fit your bill if you want to have 1 server running all your stuff. If NAS is your main purpose and you only need some Apps (Plex, Immich, Home Assistant, Bitwarden etc.) and don't need to run different VMs (some Linux Distro, Windows etc.) Hexos on bare metal should be your way to go. However if you want to have different VMs running (Ubuntu for Docker, a Windows Server for Minecraft, Opnsense and Hexos) in that case you should use Proxmox as your OS and install Hexos in a VM, because Hexos is mainly a NAS with hypervisor capabilities, if however you need to run multiple VMs Proxmox is your better choice as the OS.

So you would need at least the 8GB RasPi5 (85€), with a powersupply (10€). The RasplPi5 doesn't have SATA ports, so you already need a hat to get the sata ports, (60€). You really shouldn't run Truenas off of the microSD card, so you already need 1 SATA port for your boot drive(likely esata), which leaves you with 4 more ports for your data drives. But depending on your hat you are limited to 2.5'' drives With the costs for the Pi and Hat you are already at 155€ which puts you in the price range of N100 NAS boards, which gives you x86_64 support and more bang for your back and more features. Sure a RasPi5/ARM Nas is possible but I just don't see the use case if you can get better suited HW for around the same price. Rewriting Truenas/Hexos for ARM would cost a loooooot of money.

This is impossible to do with software alone, you need a dedicated meter, measuring what the server is pulling from the plug:

It sounds very much like your systems are just freezing up, can you confirm this by trying to interact with the server directly? Is the server still responding to keyboard inputs and is the display still showing anything? If the server is no longer responsive I would suggest to read through the suggestions in following topic and to post your specs and additional infos there. A lot of people are using Hexos/Truenas and very few have stability issues, this makes me believe that the issue is likely on the HW side rather then on OS side. Even if your PC/Server was running without freezes for years with another OS, doesn't necessarily mean that the system is 100% stabil, it might just never have reached the conditions where it freezes. Hexos using almost all of the Memory is likely a scenario which didn't occur before at least not for a prolonged amount of time. Are you using your XMP or DOCP profiles? Have you done any overclocking/volting? Are you using the latest BIOS version? Have you disable automatic overclocking which a lot of consumer grade boards are doing? Those are common culprits for instabilities in those kind of situations.

Hey @Luminous, What would be the intended HW which you would like to use and what would be your use case? Seeing how little interest/support/opportunity there is currently for an ARM based NAS I doubt this will be implemented in the foreseeable future unless there is some major shift in the PC HW space.