All Activity

yes Kinda sorta. adding a m.2 ssd as L2ARC will automatically cache. the most used files and speed up the performance when reading them. A special VDEV will also speed up the entire ssd to a certain degree especially when you have thousands of folders with thousands of files in them like what i'd expect from database workloads. However its not actually tiered behavior

Same Issue here

Thanks for the heads-up. From what I understand, unlike a typical Synology setup, TrueNAS doesn’t use SSDs for caching by default — instead, it relies entirely on RAM. So, if I want better performance, especially for read/write speeds, I should focus on adding more RAM. Is that correct? One of my intended use cases is running Docker containers with databases. If I install M.2 SSDs, would it be possible to combine them with my existing CMR HDDs in a way that prioritizes SSDs for high-performance data, like database workloads? Ideally, I'm hoping this can be handled automatically — does HexOS support that kind of tiered storage behavior?

Did this ever get resolved, I am having the same issue.

Great write up. I'd do it the same way Steps 1-6 is all that's needed (at this time) to reclaim a disconnected server using the same boot drive for anyone with that problem

I ran into the issue that my boot drive was corrupted and I had to restore my HexOS install from scratch. I found posts that said basically just reinstall it but nothing that explained the process. I had several issues, when I reinstalled HexOS it wanted to wipe my raid, once i disconnected the raid and went through the initial setup, I had no shares. So I wanted to document this so that others with this issue find a solution instead trying to rename and recreate shares and move data between datasets. This was done after I figured out a process for doing this so sorry if I missed any steps. Step 1. Remove the bad boot drive. Step 2: Disconnect the Raid drives. Step 3: Install your new boot drive and usb HexOS install media. Step 4: Follow the standard install process, including setting your admin account and claiming your server. When you finish the setup you will not have any disks so you will name your server and just continue. Step 5: Shutdown the system. Step 6: Reconnect your raid drives and boot up. Step 7: Log in to the TrueNAS gui by going to the IP address of your server in the browser and using the credentials you set up during install Username: truenas_admin Password: <whatever you entered at install>. Step 8: Go to Storage Tab and select Import Pool. 9: Select your pool from the drop down it should be named 'HDDs' and select Import. It will take a few minutes to import and complete. At this point the storage should be detected in HexOS and you should be able to start creating shares, but your existing folders and shares will not have returned. To get your shares back you must recreate them by renaming your datasets and naming them back as follows: Step 1: Under Datasets you can find all of your existing data on the RAID. Find the Dataset you want to restore in HEXOS and note the name. Step 2: Back in HexOS go to the Folder tab and select 'New Folder' Note: you may want to recreate your old users manually or create your folders with public access and recreate the users and add permissions later. Step 3: Create a new folder with the same name as the Dataset but add a 1 (In this case 'Plex1'). Make sure to keep the array the same 'HDDs; and give it the permissions you want (this can be adjusted later). Step 4: Back in TrueNAS go to Shares and select the edit button on the 'Plex1' share, depending on screen resolution you may need to scroll the horizontal scroll bar to the right. Step 5: In the side bar remove the '1' from the Path or use the drop down to select the original shared folder, then click into the Name field which should auto update and remove the 1. Step 6 Scroll down and click 'Save' and you will be prompted to restart the SMB service, do this and your share should be updated. Step 7: Navigate to the dataset tab select the 'Plex1' dataset and click delete on the right side. It will make you confirm by typing the whole dataset path. Step 8: When this is done you should be able to refresh the folders tab on the HexOS page and see the updated folder name (it took a minute to refresh for me). Redo this for each share that you wish to recreate. Once I did this and set up the users and permissions correctly, other servers I used to connect to my shares started working seamlessly. I didn't experience this but I can imagine you may run into some permissions issues since the new users in HexOS could have different IDs than before. Unfortunately you would need to manually adjust permissions on the files and folders. P.S. I imagine minutes after posting this someone will tell me I am dumb and should have done it this way, or someone else posted better over here. If that's the case let me know and Ill point to a better example, but when I needed help I couldn't find it.

Correct, but it is the only way currently until they push an update for HexOS that supports single drive pools. But good job pointing out the obvious.

Hey @freid What do you want to do with the cache drive? Please check this post from @Sonic for more information about cache in Hexos:

Exciting update! My AOOSTAR WTR MAX, which I ordered on April 2, 2025, has finally shipped as of May 29, 2025. I'm planning to re-use some existing hard drives, but for RAM and cache, I'm considering the following: RAM: Kingston Fury Impact 64GB (2x32GB) DDR5-5600 (Spec Sheet) Cache SSD: Crucial P3 Plus 1TB PCIe Gen4 NVMe SSD (Product Page) What do you all think? Are these solid picks, or would you recommend something better?

Noob here. Am i correct in saying that when I install hex os, i can also install AMP without installing a virtual machine to run/host games as a server like valheim and satisfactory?

I have the same problem

I think the core of your question is whether or not we have any type of revenue sharing agreement with iXsystems on lifetime licenses and the simple answer to that question is no, we do not.

Hi there and thanks for the questions! Long story short, we are not fundamentally changing the base of TrueNAS at this time which means that we are not offering a newer kernel version or different VM capabilities. With VMs in particular, can you walk me through what you are trying to do that isn’t currently possible with TrueNAS?

It's not recommended to run TrueNas updtaes since it can break HexOs.

Is it safe at this point to update or stay on 24.10?

in most cases its not but its also not making money like mining theoretically is.

Hexos vm support will be based on the the new truenas 25.04 incus for vm deployment system. I'm not sure if the specifics of what hexos will add to that system has been revealed yet to us. I imagine if hexos does modify it, it will just be for streamlining the process if it is required. Hexos vm support had not been implemented yet because the Hexos team was waiting for the new truenas system to release so they can build off it. At this time changing the kernel is not supported and I imagine its not going to be a supported feature but i can ask the team when i get a chance, if they ever plan on it.

Hey all, I know HexOS is built on/partnership with TrueNAS, but I have some questions that would determine if I grab HexOS for my servers at home. - Is the VM features any more meaningful VM features compared to TrueNAS? One of my servers in the cluster is on Proxmox and I don't need all of it, I do need more then what TrueNAS currently provides. - More importantly, is HexOS able to be on a newer Kernel, unlike TrueNas' choice to stay on 6.12 LTS? Proxmox recently started offering the ability to go to 6.14+. I'd love to see HexOS move to something newer then TrueNAS to support newer hardware, that will make this an almost instant purchase for several of my servers.

I just stopped mining the past month... the power draw cant be worse than my 3090 (pulling about 365w 24x7)

That's not really an answer though. "Yeah you can do it manually using the thing that HexOS is trying to abstract away, and it breaks HexOS, you know the thing you installed because you didn't feel like dealing with the thing it abstracts away in the first place".

The Zimma Board 2 will be my first foray into homelabbing. We'll see how it goes. I can hardly wait for it to arrive. I ordered the 8GB memory version but might look into getting the 16GB variant aslo.

my truenas was connected immediately after installing and was diconnected form HexOS. now when I log into hexos it says claim server with the ip of the truenas. I created a new API key and associated it with the truenas_admin account but when I try to claim the server in hexos it says Invalid Password and fails

I updated my Wifi network and therefore, all of my IP addresses changed. HexOS no longer sees my server. I have been able to locate the IP address for my TrueNas install but HexOS has failed to find the server. I have also entered the IP address manually with no luck.

I wanna drop my name to the mix, I have a bunch of files on my DropBox subscription that I would like to sync locally. So DropBox app please!

Hey, yes this is possible, someone already mentioned it in this forum however I don't have any details and it might not be as easily setup as Synology Drive Client. First of all, if it should be reachable over the Internet you either need to setup a VPN or a reversed proxy with a domain. This however is true for every service which you want to reach from the Internet and not limited to the drive replacement. But once you have this setup it's easily configured for Immich and your media player if needed. Immich is great, it's a free self hosted replacement for Google Photos. Concerning Buddy Backup it's foreseen to come this year, but you need a second (Hexos) server (and hexos licenses if you want to run it yourself) to backup to. But even without Buddy Backup, local backups to another Hexos/Truenas server is easily done using the replication tasks. You run do everything on the same server, this saves you the costs of having to run 2 servers and you only need to maintain 1 server. It's best to use Jellyfin or Plex (although Plex is alienating a lot of users recently which are switching to Jellyfin) on your server with an iGPU or dedicated GPU. As long as you have a decent GPU and not a lot of people streaming at the same time, performance impact is not an issue. Stay away from Realtek NICs (they are not supported and a lot of problems reported in this forum regarding connectivity or speed were solved by replacing the realtek NIC). If you need to get a new NIC, go for an Intel 2.5 or 10 Gbit/s NIC depending on your future network upgrade plans. Intel iGPUs are great for media streaming/transcoding and you don't need a dedicated GPU just for this. Immich does leverage a dedicated GPU for Machine Learning stuff but doesn't warrant a dedicated GPU just for this purpose. You need at least 2 data drives and 1 small boot drive. The boot drive can't be used for anything else then the OS so don't use a 1TB drive for this, a 16GB SSD is enough. With 2 data drives, Hexos is creating a mirrored pool which is not expandable in size, therefore you need to create a pool with at least 3 data drives to be able to expand in the future. Stay away from SMR drives (Desktop drives or WD RED (non plus, non pro)) make sure to only go for CMR drives. If you want to get new HW or reuse your existing server, you can post the components in here and you will get help to match the parts as best as possible and avoid certain pitfalls.