UNPAID

Just wanted to say I fixed the duplicate issue by simply deleting that file off the share (using explorer) and then copying it over again and running mover. This time it went straight on to one of the disks.

So can this be because I tried writing directly to the array before? It copied more than just one file before I cancelled it so it's stage it's just the one file. How would I manually delete it off the cache?

Finally got all the data off the cache drive but for one file...it's still listed as being on the cache drive but going into the share, it's listed as being on the cache drive and disk 1. Surely it can't be on both disks at once? Mover refuses to move it regardless.

Thank you! It's moving off the cache on to another disk now.🙏 I set the levels up as per a video when I was fist setting up (I don't really understand what they all mean tbh) but that's what was suggested... So is it okay just to use that split level for all shares and does it matter if the data is scattered around various disks? I assume you can at any point move all the data of a share onto a single bigger disk. As for the minimum free space, I tried setting it to 0 as some of my other shares (grayed out 0) but it keeps spitting out 458GB anyway. Does it really matter what it's set to? I just want it to not interfere with copying data over.

I finally got around to trying this again. Thought I'd try writing direct to the array but after a short time it was obvious it would take forever. So I upped my cache to 5TB SSD (raid 0) and also threw in an extra 10TB HDD while I was at it, and was able to copy everything I needed over to the cache. I ran mover to get all this data off the cache to the array as I have another 3TB+ to copy but after some time the mover stopped and some of the data would not come off the cache, even though this share is set up to use All disks...so I manually selected all 4 disks to be used and still the mover won't move. It looks like my Disk 1 is absolutely full and none of the other disks are being used at all. Settings attached.

Why do files beginning with "._" refuse to copy over? If I rename the file (take out or change the _ to something else) it will copy over okay but renaming it back results in "Item Not Found" error. Is this a Linux thing and is there any work around?

Long story short, I wanted to copy a folder that was just over 3TB to my Unraid server and I used robocopy to copy it over. I watched it for a little bit and left it to copy as it was all going fine. But when I returned some time later, I found that it only copied just under 500GB. Trying to copy anything else to that share now showed that there was "not enough space". I have an array of 3 usable disks with around 14TB of free space and a 500GB cache SSD. So it seems the cache got filled up possible? But why does it not write directly to the array instead? Should I just disable the cache drive completely if moving such large files at once? The mover is now active and moving all these partial files over to the array but all those files will have to be copied over again... My shares are setup as per some videos I saw. I did some copying in the past and it was okay but it wasn't so much data at once.

This is way over my head but I think I understand. I only ever use /COPYALL for flags but I tried /copy:DAT and I got 0 errors and no fails! And of course, "S=Security=NTFS ACLs". Thank you for your help. Even though it wasn't stopping it from copying it's good to know what was causing this error.

I got a large local disk on my Windows 10 that I wanna back up to my Unraid Server. I love using robocopy as it gives me less hassle than using explorer when copying large amounts of data and avoiding the character limits. So I wanted to use robocopy to do the same over Network. Initially I was denied access, the usual but after messing around and making the Share Public, it allows the test file to copy over. But I'm still getting this error: ERROR 1314 (0x00000522) Copying NTFS Security to Destination File X:\TEST\TEST.txt A required privilege is not held by the client. While the test file copies over okay I wanna make sure this won't cause me issues once I start copying TBs of data and if there is something I'm missing. Is this error got something to do with the XFS FS? I'm still new to Unraid, I set it up almost a year ago but not really used it until recently but I love how easy it is to work it using the web interface.