Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Would be nice if it supported PoE
  3. Today
  4. Look what finally showed up at my door this morning. Ah yeah, Im one of the cool kids now lol
  5. Thank you for this guide! @Dylan, can we add this one to the guides page?
  6. Hello everyone! I wanted to setup a secondary server - one for testing to break things and one for a more stable NAS environment that I will wait for HexOS to support updates and etc. To do this I needed to get some things off of my test server - primarily my VMs that I had created. Here is how I setup replication and moved the VMs. Hope you find this useful! 1. Find the VM you would like to move. 2. TrueNAS should be able to make the connection to the other server but it sometimes (frequently) fails to do so, so I will dive into how to do it manually. 3. Setup the backup credentials on the server you are transferring from. In my case this is my 01 server. 1. Navigate to Credentials > Backup credentials on the left side: 2. In SSH Keypairs section click the Add button 3. Give your keypair a name and click the Generate Keypair button: 4. Copy your Public Key. You will need this on your new server. 4. Setup the keypair on your new server. 1. Navigate to your new server and Credentials > Users 2. Select the user you will be using to do your ZFS replication task and click Edit 3. In the Authentication section of the edit dialog for the user you should see "Authorized Keys". This is where you will paste your public key that you generated. 4. Scroll down and check the box that says "Allow all sudo commands" and "Allow all sudo commands with no password". 5. Time to setup the SSH link on your primary server. Navigate back to it. 5. On the primary server navigate back to Credentials > Backup Credentials and click Add on SSH Connections 6. In the new dialog give it a name, change the Setup Method to Manual, and fill out the rest of this information (including selecting the Private Key you generated): 7. Once you select your Private Key you can click the Discover Remote Host Key button. 8. Click Save. Now it is time to generate a replication task. 9. Navigate to Data Protection on the left side and click Add on Replication Task: 10. Fill out this information and click Next: 11. When you select your SSH credentials this dialog opens. Select "Use Sudo for ZFS Commands" or check the box with the arrow above. 12. If you have snapshots for VMs you can select "Recursive" to copy those snapshots over. 13. Keep your name that TrueNAS generates for you or rename it to something else and click Next. 14. In the When section I selected "Run Once". 15. Save it and the replication will start. If on the same network it is incredibly fast - Moved two VMs roughly 120 GB in less than 5 minutes. 16. Verify on your new server the zVOL disks you copied over are present and recreate your virtual machines as you would setting up a new VM, linking the VirtIO disks you just replicated.
  7. Nice!, glad you have found the solution. I had a same kind of error with Proxmox and it took me several hours to solve the issue. Always nerve breaking 😀
  8. Found the Solution my MB had two different SecureBoot options had to disable both for it to work!
  9. I have this issue, I'm on version 25.04.0, so that's likely my issue.
  10. I just ordered a Zimaboard to experiment with and I was wondering if anyone has some insight on running HexOS onboard a Zimaboard 232. I also ordered the Zimaboard 2 from kickstarter whenever those ship, but I wanted to learn a bit more earlier so I went ahead and got this. All I am wanting to do is run a 100% uptime Plex Server with some media storage. I have some spare SSDs laying around that can handle that storage part. Ideally, if someone has some experience I would love to just hop in a discord call to get some help setting this thing up.
  11. I believe it'll be on Amazon within the next few weeks. But kickstarter is over.
  12. Sonic

    Can it replace DSM?

    The thing is, DSM really holds up well in terms of functionality, stability, and ease of use. When it comes to hardware, Synology is lagging behind, and it’s clearly moving toward a more closed ecosystem. But no other player has quite managed to match Synology’s level when it comes to software. TrueNAS and Unraid are both very solid, but neither is as user-friendly as DSM. HexOS is still in beta, and even after the 1.0 release, it will take time before it reaches feature parity with DSM. This video mentions a few alternatives, but if QNAP is off the table for you, things start getting tricky. https://www.youtube.com/watch?v=HSkO1bdXLyg Ultimately, what you should do really depends on how much effort you're willing to put into switching systems. If you’re not up for that, there’s nothing wrong with paying the "Synology tax" and accepting that you're tied to Synology drives. In return, you get a DSM system that’ll likely serve you well for years. I’ve had a Synology running in my network for over 15 years, and it just does what it’s supposed to. My most important data still lives on it. Let me be clear: I’m definitely not happy with their recent direction. I think they’ve abandoned part of their user base with flimsy arguments—no 10GbE, Synology-only drives, EOL hardware. That criticism is everywhere on YouTube right now. But on the flip side, no one’s forcing you to buy Synology. If you want the DSM appliance experience and you're okay with Synology’s quirks, it can still be a solid choice. Personally, I’m very disappointed with Synology’s 2025 releases. I was hoping for a lot more. But if I’m being honest, I wouldn’t rule out buying another Synology in the future. That would be strictly for NAS and backup functionality. I haven’t used DSM for anything else in a long time. I’m really into the vision behind HexOS. It’s a super promising project. But for now, it’s still a system in development, and it’s not yet a replacement for DSM when it comes to storing my most critical data. At the end of the day, it’s about figuring out what matters most to you. In short: make your own call.
  13. For the most part it is safe to teak things using the truenas interface. Some things however are not supported even if tweaked in truenas such as single drive pools
  14. I'm in a similar situation and I'm curious about this as well. For me it's not as much about the when but more the what.
  15. No only the Truenas Installations nothing else on there
  16. Quick question — if there's a setting I want to change but it's not available in the HexOS interface, is it safe to switch over to the regular TrueNAS UI to tweak it? For example, if I deploy an app using HexOS but there's a setting related to that app or its container that I want to adjust, can I use the TrueNAS interface to make that change? Or would that risk breaking something in HexOS?
  17. Your email address is tied to your account. Contact support@hexos.com to follow up.
  18. I've found it confusing on whether or not kickstarter is still accepting orders or if I should just wait for retail?
  19. Yesterday
  20. That fixed it, didn’t even think to do that. Thanks!
  21. Did you already did a reboot via the TrueNas interface. I have seen another forum post with describing the same issue. A simple reboot fixed this issue. If not, you can try the steps @Mobius recommend.
  22. It's a no questions refund as long as you send the request email within the 30 days. There is no other trial. License follows the user and there is no limit swapping hardware. You can easily disconnect the license and connect it to a different server yourself.
  23. Do you have another OS in dual boot on this server? If so, perhaps this Reddit thread can help you in the right direction: https://www.reddit.com/r/linuxquestions/comments/vf3fdw/no_shim_lock_protocol_load_kernel_first_error/
  24. Is their a trial or intent to have a trial soon? I understand that there is a 30-day refund policy but I wasn't sure if that was no questions asked kind of thing. It sounds like the license follows the user and not the hardware. So if I want to switch to another server with HexOS, how simple is it to switch? Is it an online manual service thing or do I need to email a support line?
  25. Tried this already, unfortunatetly I'm still getting the same error.
  26. You have to disable secure boot in the BIOS. I think that will solve your problem.
  27. Check, you are right. The splitter is the problem. Bad luck 😕
  28. I did this test as well, w/o splitter with USB-C PD the JetKVM turns on, with the splitter it doesn't.
  1. Load more activity
×
×
  • Create New...