March 9, 20215 yr Samba loses connectivity during long file transfer, e.g. backup or rsync and requires restart of rsync to regain connectivity and Veeam requiring a restart - during this, the Samba share in File Explorer does not respond. During this time, I can connect to the WebGUI with no issues. This happens at any time, no matter if the disks are spun down, spun up, during parity check, not at a specific time during transfer etc. There seems to be no consistency in the faults, however I can consistently trigger it fairly frequent during a long transfer - maybe approx every 100-200GB. This happens both on Linux and Windows, while my other Samba FreeNAS array does not lose connectivity. Rebooting does not help. The WebGUI does not show any faults. Server: R720, 2x 2690v1, 64GB (4x16GB), 4x4TB Seagate constellation, H310 mini mono (IT) and a random Intel 120GB SSD as cache. Running unRAID 6.9 Plugins:Community applications (2021.03.02), Dynamix Active Streams (2020.06.17), Dynamix Cache Directories (2020.08.03), Dynamix File Integrity (2020.06.21), Dynamix System Statistic (2020.06.21), Nerd Tools (2021.01.08), Recycle Bin (2021.02.14a), Spin Down SAS Drives (0.85). Docker containers: kamermans/docker-openmanage. VMs: None. tower-diagnostics-20210309-1830.zip
May 6, 20215 yr Hi, I have same problem.... Do you find where problem is? When i use cash pool - works fine, but i need/must use array. Slowly speed is not big problem for me. When i do backup from my windows server 2k19 on UNRAID array - i can send 15-30 Gb and sending data stoped. Windows say: lost connection or somthing like that. Undraid nothing say Sorry 4 my english. Regards Przemek
May 11, 20215 yr Author On 5/6/2021 at 3:41 PM, krzemo said: Hi, I have same problem.... Do you find where problem is? When i use cash pool - works fine, but i need/must use array. Slowly speed is not big problem for me. When i do backup from my windows server 2k19 on UNRAID array - i can send 15-30 Gb and sending data stoped. Windows say: lost connection or somthing like that. Undraid nothing say Sorry 4 my english. Regards Przemek Yes I did. It was unfortunately intermittent connectivity issues with a few disks I bought second hand. They would randomly time out and in the disk log, a read error would present. SMART were fine. I've removed them and added some new disks, and it all works fine. Check the disk log, by clicking on the icon next to the name in the "main" tab.
Archived
This topic is now archived and is closed to further replies.