All Activity

I'm running into a similar issue on a system. I have: Disk ST14000Naa11 ZHZ48MVX is FAULTED Say I don't want to replace the drive. Instead I would like to just let another drive be the backup. There are 6 14TB drives for a total of 66.96 TB. But I'm only using 2TB so far of the space. Disk 3 has faulted, and I would be okay with only having 5 14TB drives. How do I do this?

Hello. Thanks for writing us. We currently don't have a student program but please reach out next year and we hopefully will have a program in place. Try to save your allowance up as it's going to be more than $5 but a lot less than the $299 it will be at that time. Good luck with your studies. HexOS Team

Hi, I am in 7th grade and am currently running TrueNAS on my server. However, I love the UI of HexOS, but cannot afford a license. Does hexOS offer giveaways for students? My budget would be $5.

I would love to have visibility into the app curation roadmap, even without timelines, to get a list of the next apps to be curated.

I see many updates on the website. Mostly in the Hex.OS DECK interface and these go of coarse automattically but what about updating the local TrueNAS engine without breaking things? Today I saw in the command deck a message that my TrueNas can be updated, but I was afraid to do so. Can someone tell me how it happens or how it is supposed to work to keep the 2 updates in sync ? Maybe in release 1.0 there will be a update knob that installs a script to update TrueNas for the version to be in sync? It would be very clear for NEWBIES when there's a warning in the deck when to run this script and a warning not to do updates via TrueNas.

Hi @GabeL This typically means one of three conditions has been met: A drive has failed A connection issue There are read/write errors. If the drive has failed, it should be replaced. If somehow a drive experienced a connection failure, reset connections and restart. Read/write errors are indicative of a drive ABOUT to fail and that drive should either be repaired or replaced.

Hopefully this is the right place for this. We have been running our HexOS server about a year and just recently one drive has a degraded status. Just wondering what this means/what I should do. Disk 7 ST18000NM003D-3DL103 Capacity 18 TB Type Hard disk drive Healthy Yes Serial ZVTGGZES Device sdh Status DEGRADED Temperature 33° C

I tried that before I commented here. It did nothing. This morning I got up to watch something on jellyfin, and it wouldnt connect. Now, not only am I unable to access the hexos dashboard, but I can't access anything via 192.168.x.x either. I have a friend that uses truenas, so I called him. He told me to pull up the the truenas console and he talked me through rolling back to an eariler version of truenas that way hoping to fix it. It did temporarily fix the problem. temporairly meaning for about 3 mins. I'm going to try unplugging all my drives and reinstaling hexos now. I don't know what other options I have

@Sweet-foe Did you ever manage to get it working? I've tried a few times now, and honestly I just can't seem to get it figured out...

That looks like a very capable NAS you are building! I am running an Intel Arc A380 myself and it is working great for transcoding! It usually transcodes at around 500fps for me. And with this post you are now part of the community, so welcome 👋😄

I signed up as an early adopter last November, but have not yet installed it (running TrueNAS on an IXSystems Mini 3.0X+ w/a 5x8TB RAIDZ1) I'm building a custom NAS (probably overkill, this is all homelab stuff) now (parts slowly arriving) CPU: Intel 14500 I5 RAM: 128GB DDR4 (ouch!!!!) Mobo: ASUS B760M-A D4-CSM Supermicro 2U chassis 7x12TB (will be a RAIDZ2) with an HBA card and SAS extender in case I want to add more than the 8 drives the chassis supports 1TB Samsung 990 Pro NVME (boot drive, and planning on putting my VMs there, or at least the fast ones I need, w/backup to the big vdev) Intel A380 (hoping it'll work) for transcoding dual 10GBps NIC for connecting to my backbone I'll be reading a ton in the next week here 🙂 ~Horist

Creating the config dataset when using the defauult HexOs app install was the fix for me also, Thanks for this wkwebster

can you try doing this

I also have this problem. Trying to get more comments on this thread so it gets attention.

I actually didn't manage to rename the pools (it worked, but I screwed up and borked everything ahahah), thankfully I was still trying stuff on a new server. Why can't we choose the name of a new pool either? SSDs, HDDs, SSDs-1, HDDs-1, etc isn't very intuitive for multiple pool setup.

+1 on paperless-ngx

I've managed to rename pools with CLI and Truenas GUI. But it wasn't great for someone without any Linux skills. That seems like a "basic" thing we should be able to do. And I'm sorry if that sounds ungrateful considering all the work you've already put into this project. Thanks

there is a kiwix serve docker app in the truenas app catalog so it can be installed on HexOS right now. There just is no timeline for if or when the app will be curated by the HexOS team.

Update: I think I was able to get to the bottom of it. A while ago, after upgrading the server, I set a bunch of power efficiency options in BIOS to minimise the hardware impact on the power bill. However, it seems these settings may impact the system stability at high loads, which is what I've been experiencing. I also played around with the EXPO profile a little bit since I've seen system instability with some stock profiles in the past.

Any plans to implement Kiwix serve? Being able to host Wikipedia locally (through .zim file) would be great. https://wiki.kiwix.org/wiki/Kiwix-serve It’s the only feature left that would remove my barrier to switching my current setup to hexos.

I just did this with the direction of a moderator/admin. I had to make a Linux distro on a usb drive then start it in demo. Once that was done I deleted all the partitions using gpart I think. Once all partitions were gone the use you created should load after you do the standard messing around to boot from USB drive. Since I needed that to boot to linux, it was all pretty straight forward. My issue was with the pool so I needed to rebuild everything including the pool itself. As stated above, you may not need to mess with the drives. Ive never been that lucky though.

I am not able to check it myself at the moment. But I would recommend you to attach a display and a keyboard to your server, also your USB with the OS. When you restart the server it should tell you a way to stop the boot sequence and enter your BIOS. From the BIOS you can set the USB as your boot device and then restart the server again. Now it should boot into the HexOS install sequence where it will reinstall everything from scratch, and you can decide whether or not you want to wipe your HDD/SSD pools. I recommend you to get the newest HexOS ISO file and put that on your USB before you go through this process 🙂

Hello, I am sorry if this is a silly topic but I have been having issues with my installation for a bit now and after messing about a bit I think a made things worse. I now want to try and perform a clean install of HexOS but I am not sure how to do that. I have a usb with the OS on it from when I first installed it but I don't know how to to a clean install and start all over. If anyone can help I would really appeciate it, thank you.

Just got this warning in alerts today. Something I need to worry about? Certificate 'truenas_default' is expiring within 6 days.

Yes, I have configured TrueNAS Scale itself, but not TrueCloud. I'll run some further diagnostics a little later today and share findings. I apologize if my original message came across as accusatory—that wasn't my intent. I was genuinely concerned about unexpected high-bandwidth activity I couldn't easily explain or control, and I wanted to raise it as a potential bug report or documentation gap. My claims were mostly descriptions of my experience and feelings at the time (confusion, concern about what was happening). At no point did I claim HexOS was intentionally exfiltrating data or acting maliciously. My main concern was whether the cloud connection could have been compromised in some way, or if there was a misconfiguration I wasn't aware of. I appreciate the clarification about TrueCloud and the wsocat tunnel being legitimate management traffic. I'm still learning the system and genuinely want to understand what happened. Thank you for your patience, and I'll follow up with more details once I've investigated further. As per our DM, feel free to delete this topic and I'll raise it when I have more info.