mikechy

Correct!

Correct. I was using the Unassigned Devices app to mount it outside of the array. It was clipping along at about 60-70 meg a sec. that's awesome if that works as I spent two days moving the first 6 TB over the network, lol. Thanks for the reply.

I am in the process of rebuilding the old unraid system, going from 18 drives to 3. After getting the new setup up and running, I was mounting the old drives one at a time in my Ubuntu box and literally copying the content over the network. This was taking forever as you can imagine. Then I got the bright idea to mount the drive in the new UnRaid server and use the file manager to copy the content right to disk1/media/Blu. Of course it flies. After the first 2 TB moved in it struck me, that writing that fast it has to be circumventing parity, right? If so, can I just re-run parity and have everything made right? And is the correct way to write to user0/share instead? Or is this not possible... TIA.

I think I figured it out. I had that share set to cache only for a few days and then I added a new sharedrive, set the cache to THAT drive before moving the old cache to array. I think I created orphaned files that never moved until I forced it. I assume I can manually just move them to where I want them to go one of the array drives and then just run parity with fix and be all good? thanks for the reply.

Looking at the logs while the mover is working, there is endless scrolling of the mover being unable to move files to a non-existent folder in user0. I opened the file manager and sure enough, the folder it's trying to move to is not there. It's in user but not user0. I connect to the share and see the folder and files there. But am I looking at the files in the cache and not really on the array? I did change the way the cache moves a few days ago but never noticed any file loss or anything. Should I be concerned?

Fresh Install 6.12.14. Right out of the gate I get the blank screen. refresh 1 to 20 times and it will pop back up. very frustrating. This happens on two different servers and multiple clients. Mac and Windows. clearly this is a code issue and not a client issue.