Way back when i started with 24.04 i created a custom app config. Which didn’t work and also didn’t let itself be deleted. Now fast forward to me running 25.04.6 i gave removing it another go. Messed up the config file, which stopped the Apps Dashboard from loading with an error message.
I then thought to myself, why don’t you give Unraid a try (that’s when i shoot myself in the foot for real. I used a different pool name than in Truenas, which stuck). Unraid didn’t work for me so i went back to TrueNAS and installed 25.10, which went smoothly but now the Dataset gets imported with the following mount point: /mnt/mnt/unraidpoolname/dataset
That results in TrueNAS not recognizing it as a mount point. I can reset the Mountpoint using the CLI but that doesn’t persist reboots and also creates other problems.
Can i salvage this somehow? What additional information do you need?
Thanks in advance to anyone who read my rant/ cry for help.
You should be able to export the pool through the webUI (don’t check off “delete data” of course!) and then re-import it. That should then import it as /mnt/unraidpoolname/dataset which will let you map it correctly.
Try correcting the mountpoint and canmount properties directly in the datasets, and then export or import the pool correctly. Once the properties match TrueNAS expectations, the UI should recognize them normally.
I tried the commands again, with a bit more time at hand and this command: zfs set mountpoint=/mnt/poolname poolname fixes all paths, but when I export and the reimport via the cli all mountpoints get reset to /mnt/mnt/poolname/dataset, but uses the correct pool name and not to the one I set in Unraid. So i just need to make the change persistent and everything is back to working order.
Except i just tried rebooting to see if the change persists a reboot and now the command doesn’t seem to be working anymore. sigh
I’m already working on a way to safely store the data away, to just burn the whole pool down to rebuild, but i want to keep that as a last resort.
