Sonvolt99

Bit of a rant , but on future releases can we have a bit of reality/honesty/transparancy on announcements for coming RC's or releases. September 2021 digest quote "6.10 stable coming soon tm" (don't think the TM addition is remotely humerous) December digest quote "new RC in coming days" , January "new RC in coming days" , Febuary downgraded to "coming soon" This to me is either Misinformation , BS , Incompetence , lack of /testing due diligence on product and does not give me any confidence to even consider trying the RC just released. End of rant @limetech @SpencerJ

I occasionally get this and only resolution is hard rewboot , attached diagnostics , appreciate any ideas and what I should be looking for in diagnostic file so I can identify issue if possible. nas-diagnostics-20211114-0856.zip

Yes excuding *.log from RSYNC has resolved this.

Think I may have the answer , I recently set up the syslog server on the array , suspect its waiting for that , will need to exclude it from RSYNC will try later to see if this resolves.

Laptop just invoking the script via Webui

Hi, I'm a relativly new UNRAID/Linux user and have a problem recently with Rsync from my unraid server to my backup NAS Netgear NAS duo , the rsync script hangs when copying the VMBACKUP folder syslog shows a upsteam timeout to 192.168.1.66 which is my laptop that initiated the RSYNC script to be run in background and connectivity messages re the backup server. Can access both server data files and no loss of connectivity from my laptop (wireless connected) The CPU's show 100% and I can generally avoid a reboot/parity check recovery by using HTOP from terminal to kill the RSYNC processes Attached diagnostic log (could only gather diagnostic after killing RSYNC processes), any guidance on what the issue is and how to can resovle appreiated. nas-diagnostics-20210722-2110.zip