Leaderboard

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.

For this, the fix was to in HexOS go into Settings > Reset > Unclaim System. Then reclaim the server and it should be fine. From what I can tell it gets like that because when you reclaim the server before restoring the config backup in TrueNAS the API key is different than what HexOS has so when you reclaim the server it checks and see the API key in TrueNAS and uses that. Sidenote if you are importing your config file back into TrueNAS for the apps if they are gone and nothing happens after you set the pool, try unsetting (unset pool) then select the pool again it and then it takes a bit to run through the HDDs and bam it comes back.

Are there plans to add other MFA possibilities than Google Authenticator? I'd really rather not have to use that app.

Hi there :). I'm upgrading from a hdd enclosure that I had connected to a mini-pc to this. I'll have 48tb of usable space and plan on upgrading with another 5hdd's at some point and then another 5hdd's even further down the line. I'll eventually add a GPU as well. Looking at the Nvidia Quadro p5000. Named the server Leela 🙂 CPU - Intel Core i9-12900K Mobo - ASUS Z790 Prime Gaming Mem - 64gb DDR5 (16x4) Boot Storage - 1tb nvme Teamgroup Mass Storage - WD Red 12tb NAS HDD's x5 SAS - SVNXINGTII SAS9305-16i PSU - NZXT C1000 ATX 3.1 Case - RackOwl 4U Server Chassis

I'll just answer myself. It is. I had previosly updated TrueNas to Fangtooth which is not supported and I messed up the boot pool so I wanted to reinstall but was worried about it (I was thinking on just dropping HexOS and use TrueNas directly with the latest version). I was able to reinstall everything following these steps (I had a recent copy of the truenas config): Follow steps 1 to 6 Update TrueNas from the UI to Fangtooth Reimport TrueNas config profit This was easier than I though and I didn't lose any data.