d3rby

@Captain Roque 1. i "left" them on the old pool. but i use now a dedicated NVME Drive only for jail / app stuff and install them clean after install hexOS 2. i created the user in HexOS GUI but because my dataset (NASSHARE) was not there in the HexOS GUI. So i made my SMB Share over Truenas GUI

I moved my old TrueNAS setup to HexOS last night for New Year’s. I even managed to cleanly import my old pool, which is great! 🙂 A lot of configurations had to be manually adjusted due to “legacy settings” in the TrueNAS GUI (e.g., Bond, GPU acceleration for Plex, a second pool with an NVMe drive for apps), but overall, things are running quite well! Unfortunately, HexOS seems to be struggling a bit with the second apps storage. At the moment, it’s not recognizing any pools (though it did detect them during the pool RAID import). I hope this gets fixed with future updates! Here’s a quick technical overview: Case: Very old 4U case from the 2000s Motherboard: ASUS P10S-E CPU: Intel Xeon E3-1230V5 RAM: 4x 8GB DDR4 2133 MHz ECC HDDs: 4x 4TB WD Red NVMEs: 1x 256GB NVMe cache drive, 1x 250GB NVMe SSDs: 1x WD Blue 500GB boot drive Pools: RAID5 with NVMe cache drive, “stripe” pool with NVMe for apps GPU: NVIDIA P400 for Plex I’ve now recreated all the shares except for my Time Machine backup share and am happily testing everything out! 😊 Simply installing HexOS and importing an existing pool isn’t possible just yet. I had to disconnect my pool and attach an empty drive because HexOS forces you to create a pool during the setup process. Unfortunately, there’s no option to skip this step at the moment. After completing the setup, I deleted the "new" pool on the empty drive, powered down the system, reconnected my original pools, and imported them via the TrueNAS GUI. 🙂