So I booted into TrueNAS, imported the FreeNAS pools, crated childdataset on both, sambamapped them and set up access before trying to move a little data for a test then edit it.
The test went well but I wanna hear opinions about this.
I am using rsync to move the data from the rootdataset (the one created in freeNAS) to the new childdataset while crcchecking every file and deleting it if crccheck is ok. this way I save space.
I have 2 commands, one to move everything and one to move in batches:
rsync -rlptDvh --no-perms --no-owner --no-group --checksum --ignore-errors --remove-source-files --progress --exclude=âSourceDataSetâ â/mnt/SourceDataSet/â â/mnt/SourceDataSet/TargetDataset/â
rsync -rlptDvh --no-perms --no-owner --no-group --checksum --ignore-errors --remove-source-files --progress â/mnt/SourceDataSet/Folder/â â/mnt/SourceDataSet/ChildDataSet/Folder/â
As I understand this is gonna generate a lot of heat, moving all data, besides my Intel(R) Core⢠i3-4150 CPU @ 3.50GHz will be working a lot doign crc checks.
Except for making sure its doesnt get too hot inside the case. Am I missing something? can this be done in an simpler safer or faster way? do the commands lack anything ?
The bigger pool contains 45TB
@HoneyBadger Do you have any feedback on the process of getting root dataset SMB shares fixed to the newer child dataset model and fixing permissions, etc?
I was waiting to see if any other users posted.
While doing my test, I tried to edit one of the files from the FreeNAS root dataset that was rsynced to the TrueNAS childdataset and that went fine. However I dont take it granted that it will work with all files. My issues are the permissions and I really want make sure as much as possible that they are not gonna be a problem once i start rsycing files and deleting them rfom FreeNAS (where the permissions are no problem at all) Back and running on FreeNAS while waiting for some good posts here 
May I suggest reinstalling your TrueNAS installation? You wrote that you executed several LLM suggestions on your system before. I would not consider such an installation trustworthy now. And re-installing TrueNAS now without any data having been transferred might save you some headaches or random errors later.
Well, I a not sure about this. But I see a little point in what you suggest.
Most commands I executed have been to fix the permissions on the imported pools and I donât thing they have messed up the pools. Why? Because I have been rebooting more than once into FreeNAS and using the data there without any issues at all.
I wasnât even done with configuring the basics in TrueNAS like tests and scrubs as this a new installation when I detected the permissionsissues.
But I could bet that reinstalling will not fix this, the problem probably lays in:
1 All my data in the imported were created in FreeNAS (FreeBSD) with different permissionpolicy and live in the rootdataset. TrueNAS want the data in a a childdataset
2 FreeNAS, FreeBSD, permissions differ from TrueNAS, Linux, permissions
3 The test I did proved that it worked once I moved the data with rsync (see previous post), however it worked on the files I moved and it doesnât gurantee it works on the rest of the files
So for now I am gonna wait for more suggestions before doing anything at all. Also the machine is busy, running lots of tests on all disks in FreeNAS while waiting for more potential solutions 
Any more suggestions on how to move on with this ?
is Upgrading from FreeNAS (FreeNAS-11.0-U4 (54848d13b)) - #23 by arameen the only way to fix it? and are these commands good or am I missing something ?
It has been a month since your last post, so perhaps youâve got everything sorted outâŚ
For what itâs worth at this time:
I chose to do a new install of Scale 25.04.2.6 rather than running the migration from Core to Scale. Of course, I had to go through the TrueNAS set up again but since I couldnât migrate my old jails to the new system anyway, I didnât see this as much extra trouble.
After changing from Core to Scale, I had two issues that had to be addressed
- I had lots of data files that were owned by root
- On the Core system I had created SMB shares on root data sets (which Scale doesnât like)
Following the instructions/recommendations in the documentation, after setting up Scale I created my own admin user and general user. Then, I logged in with my own admin user and mounted the disks from my Core system, created new data sets on the disks, then moved all my data files to the new data sets. Once the data was moved, I reset ownership and permissions as needed using âchownâ and âchmodâ commands from the shell (to get rid of the previous root ownership). I did everything one step at a time⌠that way I didnât get lost and my data was never at risk. When it came time to set up the shares, I followed directions in the documentation.
yeah, I never got any message on how to go on with this when it comes to the permissions.
When it comes to the upgrad itself, as I wrote earlier in the thread the plan was to do a clean install for TrueNAS and just import the pools, That is exactly what I did. I never did upgrad x versions up, never saw a point in that but more issues and risks.