ninjabucket

Figured it out by manually moving clumps of files around on the command line. Ended up being a couple of directories with odd characters that were throwing unRAID off like: Dir². Now to figure out why rsync trashed the file name when copying it over, but copying the same file via SMB works just fine.

Tried that - all it found was a couple update checks that aren't enabled. Any other ideas?

I have a user share with files on 3 disks. I could see all of the files via SMB. I did a copy from the command line on the unRAID server using rsync: rsync -avz remote_host /mnt/user/Media/ After doing that if I open Media via SMB from a remote client, it only shows some of the files (those on Disk1). Interestingly if I manually put in the full path of a directory I know should be there, it loads fine via SMB. From the unRAID server via SSH I can ls /mnt/user/Media and it shows all of the files/dirs. I tried chmod -R 777 /mnt/user/Media and restarted but that did not help. Anyone encounter this situation?

Unrelated, but how did you setup your cache? I have a similar build, and when I enable cache on a share that I am copying multiple TB's of data to, the cache fills up and things go wonky. It seems like the Mover process gets stuck and never finishes, then things bog down. For now I have cache disabled. I have the same LSI and am only getting 30MB/s in - but my drives are not as good.

I fixed it. The last directory being written was trashed on drive 2 - permissions were: d???. I started the array in maintenance mode, then ran "xfs_repair /dev/md2", restarted the array, and magic.

I'm new to unRAID, and doing some testing. I have 5 drive array (4 data, 1 parity). In the middle of copying data, I simulated a power loss by turning the unit off to see how it would handle recovery. After booting back up, I can see the data on the individual drives, but the the user share shows empty and gives a permission denied when attempting to write to it. unRAID is currently running a parity check. Is this normal behavior? Once the parity check finishes will the data re-appear on the share? Again I can look on the individual disks and see the data just fine.

I'm thinking of putting unRAID on a system I have with 192GB of RAM. Is a cache drive needed with large amounts of RAM, or will the RAM take care of most of the writes?