Tommyka

I also found another fix. Going back to version 6.11.5 also fixed it. This also seamed to fix the problem that smb did not work

Thanks will try that

I'm trying to setup zero tier to my unraid nas. I can ping the ip, and also access jellyfin running on the box. But if I try to access the gui it do not respond, and I can access the smb shares through the ip either. I read somewhere that I should add the interface to the "Include listening interfaces" but to no avail. ztjlhtns77 matches the ip-range of my zero tier ip. Is there something else I need to set?

@K1LLA_KING_KING Have you tried if you can access any of the other services you have? I have a similar problem running zero tier. I can access jellyfin but not the unraid ui and not able to connect to my smb share

I tried with different thread count to test if that made a difference. I tried looking around to find what file it was getting stuck on, but it just stopped after finishing a specific folder, but was not able to find any folders that was missing files. This is a big image archive, and I noticed that I had a old Lightroom archive in the folder that was not needed. And after deleting that it would complete the copy, or now it would just confirm that all the files where there. So I have now managed to copy over everything I needed. But it seams that it stumbled in all the small preview files of the Lightroom archive.

This is my first try using unraid. Im migrating from qnap nas to unraid. My plan was to run unraid on the qnap nas box, got it up and running fine. I have a brand new Toshiba n300 16 tb disk in it now. I have not added the second disk yet to create parity because i read it was recomended for a fresh install to move the data over first, and then create the parity. But when I began to migrate the data the transfers allways get stuck on the same file. Im using robocopy to copy over the files. I have tried and move the disk and unraid to another mashine, to see if it was the hardware, but it got stuck on the same file. I have run a smart self-test on the disk, and it came back as ok. I have added 2 diagnostics from 2 seperate attempts and the smart data. blokka-diagnostics-20230809-2321.zip blokka-smart-20230809-1309.zip blokka-diagnostics-20230808-2100.zip