Trying to repair/access Pool and access SMB pool

Now that I have replaced all the hardware (minus the 8 hard drives), I am going to open this new topic. Here is a link to my first, but I will give a brief synopsis here.

My last server pretty much overheated and killed some hardware. I had a friend come over while I was out of town to swap hard drives (who I thought new TrueNAS) before I knew it was overheating. He messed it up and my Pool (MainNAS) disappeared from SMB and I couldn’t do much to recover it though it said it was there. Then I was getting checksum errors and a bunch of people told me to get new hardware.

TrueNAS Scale 25.04.2.5
RAM: 64GB
8 x 12TB Hard drives (all CMR, Seagate, Toshiba, WD NAS Drives) (RaidZ2)
1 256GN NVME (boot) (will mirror it when I get everything else running)
MSI Pro Z790-A MAX (12th Gen i9-12900K)
LSI SAS3008 9300-8I IT-Mode HBA JBOD PCI-E 3.0
Case: Fractal 7xl
PSU: Focus GX-850 power supply
ProART LC420 for cooling

That is my new setup. I had to use a new boot drive (TrueNAS Scale 24.10.2.4) as the other one had way too many errors, but also means my configuration was lost (ok as wasn’t much besides 4 users and 1 app).
I turned it on and imported the pool (MainNAS). It still has my ZFS Health as unhealthy and Red X on the GUI. Since as stated above, I had no configuration, there was no SMB setup. I created 1 new user so I can setup a SMB share and gave them builtin_Admin group.

In Windows I now see the folder and can log into it. I then see the 9 folders I had before, but when trying to access them I get “Windows cannot access. You do not have permission to access.”
What have I missed or am I doing wrong so I can open the folders and access the files?
Also what do I have to do to get ZFS Health back?

Thank you in advance for any help.

Also wanted to add this was originally a CORE, so maybe somewhere in the upgrades and the problems the permissions are screwed up, but I have made the 1 user I created with full access.

I think I found my problem. My UID was different while the permissions and names were the same. I will update if it worked later.

Filesystems not know about these username / groupname things. They only know uids / gids in MacOS / Linux, or SIDs in Windows.