Leaderboard

Thanks for your Answer, i was unaware of the ZFS 80% 90%, 94% Rules.

I made a post about the same issue, they are looking into it:

AnyRaid is not released yet. When it gets released by the ZFS people it has to be adopted first into TrueNas. So just a guess is that it probably won't be here till next year. There won't be a way to convert to it. You have to start from scratch so you'd have to copy off all the data from your existing system to something and then format the drives as AnyRaid. Then copy the data back over. Thanks

fast answer: no you don't, full answer: from what i know zfs (the filesystem of truenas, underlying os of HexOS) have different stage of speed: under 80% the storage is fast en responsive, this is the base mode: the performance mode over 80% the file system is going from a performance mode to a more slow mode (zfs is attentively looking for freespace on disk to store files) so after you hit the 80% trigger the warning is on and you shouldn't ignore it it you are really near the full capacity (99%+)

Hey, just click back on the top left and then skip.

We are extremely close to releasing HexOS Local, our solution for accessing/managing your HexOS servers through a locally installed application on your server. Before we roll this out to all current users, we are looking for a handful that are able/willing to help us test the migration process. The requirements are pretty simple: 1) Users that agree to enroll in this early access test will have ALL of their servers migrated (we cannot apply the test to just a single server, so if you have multiple, it's all or nothing). 2) Users must have a discord account as those accepted will be invited to our new discord server for the purposes of bug reporting and support needs. If you are interested in helping us test this, please drop a DM to @mill3000 with the subject "HexOS Local Early Access" and be sure to include your Discord username in the message. Any questions, post them here! Thanks everyone!!

I'm having the exact same issue on 25.10.2.1 — so the update alone doesn't fix it. I dug into it and found the actual root cause: The ix-vendor.service runs /usr/bin/start_vendor_service on boot, which calls vendor_service.py. This script starts a transient systemd unit called websocat.service (the websocket bridge between your local middleware and deck.hexos.com). The problem is that the script doesn't check whether websocat is already running before calling systemd-run --unit=websocat. If websocat is already active, the call fails with "Unit websocat.service was already loaded", but the script always exits with code 0 (it has a finally: sys.exit(0) block). Something then re-triggers ix-vendor, it fails again, and you get a rapid restart loop. Each loop iteration spawns a Python process that opens Docker sockets, and since the middlewared service only has a soft file descriptor limit of 1024, the FDs get exhausted quickly — hence the "Too many open files" error. Here's the fix that worked for me in truenas shell — a systemd override that adds a simple check before running the script: sudo mkdir -p /etc/systemd/system/ix-vendor.service.d/ sudo tee /etc/systemd/system/ix-vendor.service.d/no-loop.conf << 'EOF' [Service] ExecStart= ExecStart=/bin/bash -c 'if systemctl is-active --quiet websocat.service; then echo "websocat already running, skipping"; exit 0; fi; /usr/bin/start_vendor_service' EOF sudo systemctl daemon-reload sudo systemctl restart ix-vendor.service After this, ix-vendor shows active (exited) with status 0, websocat keeps running, and deck.hexos.com works fine. No more loop, no more FD exhaustion. I also raised the middleware FD limit as an extra safety net: sudo mkdir -p /etc/systemd/system/middlewared.service.d/ sudo tee /etc/systemd/system/middlewared.service.d/fd-limit.conf << 'EOF' [Service] LimitNOFILE=65536 EOF sudo systemctl daemon-reload sudo systemctl restart middlewared Both overrides live in /etc/systemd/system/ which - as far as I understand it "so far" - survives reboots. After a HexOS update you may want to verify they're still in place. Hopefully the HexOS team can add the is-active check to vendor_service.py itself so this gets fixed upstream.

I'm having this issue too. Looks like there is a fix on GitHub posted below, but I can't figure out how to access the app configuration files for a curated app..... really hoping I don't need to nuke my install and back up all of my photos again...... If I do I think I'll give up on the curated apps and start installing this in a docker container now that I've managed to teach myself that process. Before I do though - did anyone find a way to fix this on HexOS? https://github.com/truenas/apps/issues/4628#issuecomment-4098018533

After the 1.0 update not all my apps are showing on deck/local. I believe its only custom/docker compose apps. Before the update they where showing. Is there a way to fix this?

When I had local UI installed I had to log in just like the very first time I setup HexOS. It took a little while. Just long enough to make me think I was doing something wrong but the dashboard came up When I logged in I saw picture. I clicked on the word local and saw this. I am guessing it's not exactly the word that is the trigger. That just happens to be where the mouse pointer was when I clicked. I clicked on Switch to Hosted and went to the online dashboard so I started on local. Now to switch back I click the Return to Local button on the top banner. If you don't start that way I am guessing the down arrow next to your server name will allow you to go back and forth.

Hi there! I would love to have a way to have access to the server via my own domain. The way Yunohost its doing is fairly simple but breakes at lieased for me from time to time. Maybe there is a better way to have a self protecting login page reachable via a domain. I know that there are other ways like reverseproxy or tailscale but you have to manage security and update everything in the rightway or you have to pay for a service and teach the elder how to use tailscale ( sometimes twice a month ;D ). Love to have a solution thats easy to use, secure, stable, and inexpensive. Thanks for your thoughts on this!! ❤️

No one things thats good? Am I missing something?

You can join the official discord and request help in there, this should get sorted out rather quickly. https://discord.gg/fCW2htvYdz

Follow up, @shpligthe updated driver's removed support for non-RTX cards as I understood so 10xx series and below no longer work with containers/apps but should still work with virtual machines because you install the drivers in the virtual machine and just have to make sure the card is passed through. @CosmoI am hoping the TrueNAS 26.1 update will address my specific card compatibility. A thread on the TrueNAS forum seems to suggest that NVidia driver 570. 172.08 is what shipped with Goldeye 25.10 and comparing that against the earliest Linux driver for the 5060 Ti on the NVidia website shows a driver version of 570.211.01. Long story short, I think this card just missed the boat on support but according to a recent TrueNAS blog post 26.1 adds NVidia driver 590.48 which means it'll definitely be supported on the next major HexOS release

I followed the instructions and it solved the problem for me. Can confirm an instant CPU usage drop. Thanks!

Hey, The Team believes there is a bug in Truenas itself related to the vendor service which triggers the command deck connection. This is currently under investigation.

Luxembourg!

You can still run VMs in Hexos, but you need to go to the Truenas Gui. VMs will only be supported in the future in the Hexos GUI. But Proxmox is likely the better OS for your purposes and just put Hexos in a VM. 🙂 If you run Hexos as the OS, the 64GB SSD is more then enough. If you want to run Proxmox then get a bigger SSD (512GB or more) and make sure it's not connected to the same controller ass your HDDs. (Best is getting a NVME SSD anyway for Proxmox and the VMs). If you use Hexos as OS, you need 3 SSDs (1 for the boot drive, at least 2 for a mirrored pool for apps and VMs) while you only need 1 SSD if you use Proxmox as the OS, since you can install everything on the boot drive. Check this video to get a good overview of all the WD drives: But you can also go for Seagate and their IronWolf (Pro) or Exos Range. Unless you go for 10gbps networking, the speed difference in the drives is not going to be really noticable/worth the extra cost for most users. I'm using Intertech rack-mounted server cases. They are big, offer a lot of space and airflow and are ugly as hell and are ment to be mounted into a 19'' rack. 🙂 So yeah, unfortunately I cannot give you any none rack mounted recommendations. 🙂 You can use some PowerLAN adapters in the meantime if needed. 🙂 Yes, the rest can run over wifi, just the server absolutely needs to be connected via cable. Fan noise and HDD noise are a real thing and can be annoying. You don't need to have it good looking but noisy in the living room you can also put it noisy and ugly in the garage or cellar 🙂 Haha, no, my country is a lot smaller, but has the same flag, just with lighter blue and alternate is also available here =D 😉 If you have any more questions don't be afraid to ask them 🙂 Also, once you have your server speced out make sure to post it here as well so that we can take a look to avoid common pitfalls before buying 🙂

First, a huge thank you to @lnkd for posting the actual steps to do this. All I did was follow everything they said and take pictures, so really all credit goes to them. Original post here: Prepare TrueNAS for reinstall: 1. Login to TrueNAS web interface – go to deck.hexos.com and click Settings: Then click the TrueNAS icon: 2. Once logged into TrueNAS, go to System > General Settings > Manage Configuration > Download File: 3. Read the note presented when you click Download File: 4. Click Save: 5. If you have encrypted datasets, go to Datasets > select the encrypted dataset > Export Key: 6. Now it is time to shutdown the server. In the top right of the TrueNAS web UI click the power icon and click shutdown: 7. Make your changes to the hardware that you would like – for me I added a 10 GB network card to run off fiber. 8. Prepare the HexOS installation drive by following these steps: https://hub.hexos.com/topic/103-illustrated-installation-guide-start-here/ 9. In your router settings, give the new hardware the same IP as your old one, then restart TrueNAS to grab the correct IP. 10. Once rebooted you can confirm on the server the IP address is correct: 11. Login to the TrueNAS web interface with the username and password you set during install (username should be truenas_admin). 12. Confirm your version on the dashboard – if needed, apply the update to the server: a. To confirm what version you need check the filename of the .tar file you downloaded from your configuration. It will have the version number on the end of it. b. Select the same version from the upgrade screen and confirm you want to switch to that upgrade train. c. Apply the pending updates and the system will reboot. 13. Go to Storage > Import Pool > find your zpool: 14. I have two pools so I will import them both. 15. Go into System > General Settings > Manage Configuration > Upload file: 16. The server will reboot after the configuration is applied. Log back into the TrueNAS server once the reboot is finalized. 17. If, like me, you replaced the network cards you will need to login directly to the server and adjust the IP settings: 18. Setup your new interface with the primary IP in CIDR notation, then you can log back into the TrueNAS server. 19. To setup apps, you need to go to Apps > Configuration > Unset Pool: 20. Restart your TrueNAS server then go back into Apps > Configuration > Choose Pool: 21. Once the pool is set you will see your apps again and be able to start them. 22. Navigate to the HexOS Interface (http://deck.hexos.com), unclaim your old server and claim your new one: 23. I ran into an issue where no matter what password I input it would not take it: 24. Currently troubleshooting that to be able to claim my HexOS server in the deck. All of my apps and storage are up and running so I will report back here when I fix this issue.

Hey, the local GUI access is currently being rolled out to everyone in accordance to the purchase order and should be available to everyone in the next couple of days.

No, the warning went away on its own.

Likely unpopular opinion, but thank you!

Hello all! We are excited to announce HexOS Local, powering the new local UI/UX for HexOS and capable of so much more. Read more about it on the Blogpost - Introducing HexOS Local

Hello, It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following. Login to TrueNAS interface. Left side select "system". Then after screen refreshes select "shell" from the list. Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting. sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.

Great question! Because I have limited needs, just a storage device with basic streaming capabilities, I use HexOS on the daily - mainly Plex. However, this is just part of my larger effort to build out a home solution that will eventually replace paid-for services that have increasingly risen is price and are more inclusive of advertisements (I LOATH ads with a perfect hatred). I am attempting to time my efforts with HexOS maturation. Which is to say as HexOS gains in features, I look to increase my DIY replacement of paid-for services. I know not everyone has the same timeline, level of effort, risk tolerance etc.. as I do, but that's why I jumped in early. I keep backups, try to contribute to this community and help where I can to see where this is going.

UPDATE: As of 11/8, we have updated the ISO installer to run on version 25.04.2.6 of TrueNAS SCALE. Existing users should NOT reinstall to get this version. You can update from within the Activity card on the Dashboard (or the Notification). Hello and thank you for joining the HexOS beta program! You are an elite and vital part of this project and your participation is greatly appreciated. This post contains all the information you will need to get started with HexOS and how to communicate with our team during your beta experience. Disclaimer Beta Products, Software, and any related Services are still in development, and therefore, you are advised to safeguard important data, to use caution, and not to rely in any way on the correct functioning or performance of the products, software, or any related services. Beta Products and Services are provided to you “AS IS”, without any warranty whatsoever. Expectations During your participation in the beta, we expect you to do the obvious: use and test the software. But we also expect you to communicate with us when things don’t go right or if you’re having trouble. Please post feedback and let us know about your experiences, good and bad. That being said, please remember that this is beta software and early access. HexOS has a long and healthy roadmap ahead. Quickstart Guide For those that just want to get started, here’s the TLDR: Download the ISO here: https://downloads.hexos.com/TrueNAS-SCALE-25.04.2.6-HexOS.iso or https://hexos-downloads.sfo3.cdn.digitaloceanspaces.com/TrueNAS-SCALE-25.04.2.6-HexOS.iso (SHA256 Checksum: e8ed99a322affe0969b82b866161a9f6acbc1561e3cc7b2efb2bf120ffe2e856) Use a tool such as Balena Etcher to image a USB flash device with the ISO. Boot your server from the flash device and install the OS to preferably an SSD. When given the option, opt to create the admin password in the installer (do not select the option to "Configure using WebUI"). Remove the flash device and reboot your server when the install is complete. From another device (mobile, tablet, desktop) that is on the same LAN as your server, login to https://deck.hexos.com using your HexOS credentials. Follow the instructions to complete your server configuration. NOTE: As of the 24.10.2.2 build of this ISO, configuring the admin password via the webUI option has been removed from the installer. However, if you select to create an admin password, but then attempt to "cancel" that process, the ISO will proceed with an installation with no admin password set. This is a known bug and the TrueNAS team will be addressing this in a future update to the ISO. Just don't cancel out of creating the admin password in the installer ;-). Hardware Requirements Booting HexOS is designed to support a wide variety of x86 hardware (Intel or AMD). The minimum requirements are a 2-core 64-bit CPU, 8GB of memory, and a 16GB or larger SSD boot device. However, depending on your needs for performance and applications, more resources may be required. Storage Pools Pools are made up of storage devices based on size and type (HDDs vs. SSDs). Storage devices in each pool need to be roughly the same size*. The OS boot device cannot be a part of a pool. Expandable pools require a minimum of 3 devices and can be grown one device at a time. Non-expandable pools can be created with 2 devices. Initial pool width should not exceed 8 devices. Maximum expanded pool width should not exceed 12 devices. At least one storage pool must be created to use HexOS. *In the event of slight variations (e.g. 240GB and 256GB), devices can be grouped, but total capacity for the pool will sacrifice the larger device’s excess storage. Build Recommendations HexOS has been designed so that a relatively modern PC can be easily transformed into a very viable home server. This means using standard HDDs/SSDs and using onboard controllers for storage/networking. However, since we’re based on TrueNAS, our hardware support is actually rather vast. For more detailed hardware recommendations for advanced builds, please refer to the TrueNAS SCALE Hardware Guide. Installing in a VM As HexOS is based on TrueNAS SCALE, it can be installed as a virtual machine as well. While the process should be fairly self-explanatory, please see the TrueNAS SCALE documentation for additional instructions on VM installation. Setup and Configuration Once the OS has been installed and rebooted, you will use a web browser on the same network as your server to register your system and complete the setup process. This can be a PC, tablet, or mobile device. Using a capable browser, login to https://deck.hexos.com. Beta 1 Features Our first release is focused on providing a streamlined user experience for setup and configuration and laying the framework for what’s to come. The main features of Beta 1 include: Setup and configuration wizard Configure your home server in minutes with ease. Analyze system health, with warnings for SMR HDDs. Auto-configure storage pools to safeguard against device failures. Securely manage your server remotely via Command Deck. Storage device management Detect error states and conditions and report through the dashboard Highlight individual storage devices and their respective faults Replace devices from storage pools due to failure or preventative maintenance Expand pools as little as one device at a time Folders and users Create and share folders over your local network. Easily manage permissions for secure access. Apps One-click deploy Immich as a personal photo library app. One-click deploy Plex as a home media server. Automatic folder creation for app storage. Dashboard / UI Access key statistics like CPU, memory, network, and storage usage at a glance. Monitor storage health and see alerts for errors or degraded pools. Manage multiple servers from a single, unified interface. Enjoy mobile-responsive design for effortless navigation on any device.