sacherjj

Helps quite a bit. The part I was missing is seeing the pull down that gives the rmsrc commands to help easily clean up. Still not sure why permissions are causing this, but working through that as I get to understand unraid better. Thanks for the education.

Versions Unraid 6.6.7, unBalance v2019.02.12b I get the same results with scatter or gather. All rsyncs use the same flags as this: rsync -avPR -X "Joe/Software" "/mnt/disk3/" It explicitly says skipping deletion, but I don't know if that is for source or target. W: 2019/03/20 11:58:33 core.go:763: command:end:error(exit status 13) I: 2019/03/20 11:58:33 core.go:767: command:retcode(0):exitcode(13) I: 2019/03/20 11:58:33 core.go:1028: Command Finished I: 2019/03/20 11:58:33 core.go:1041: Current progress: 100.00% done ~ 0s left (141003.94 MB/s) W: 2019/03/20 11:58:33 core.go:960: skipping:deletion:(rsync command was flagged):(/mnt/disk3/Joe/NeedsOrganizing) I: 2019/03/20 11:58:33 core.go:710: Command Started: (src: /mnt/disk4) rsync -avPR -X "Joe/Software" "/mnt/disk3/" W: 2019/03/20 11:58:33 shell.go:51: flag:(rsync: failed to set times on "/mnt/disk3/Joe": Operation not permitted (1) Seeing permissions of drwxrwxrwx nobody users for all directories and drw-rw-rw- nobody users for files.

I don't know if I have something misconfigured. I've been running unbalance and it copies data to drive I indicate, but the rsync is not removing data from the source. I'm having to go in an manually delete this data with mc. I've run the Docker Safe Permissions run. Any ideas on how to fix this?

It seems like syslog is blown away after a hang or reboot. I have been trying to figure out if this is a system error or configuration problem. I was doing a transfer to cache and Unbalance to empty a drive for replacement. And a pre-clean. Web interface hung and it looked like the system rebooted. Then it didn't come up and I had to reset after a few minutes. Each time it does a parity check, which is probably good as I don't know if anything was inflight during this hang. Any tips for persistent logging that I can track down the cause of this? I was all ready to jump into unraid, and not I'm trying to get it stable. Is syslog on the USB? Can I pull that if I see a hang and keep it from getting over written?