Zonediver

Hi Frank1940 and thanks for your reply. Fist of all: My Problem has nothing to do with this prob described in your Link. I try to explain what really happens (difficult): I use mapped network addresses for my shares \\10.10.10.250\Movies \\10.10.10.250\TV-Serien \\10.10.10.250\Cache Win 10 starts the copy-process (Window comes up with this green graph), copies ~100MB or more to the share and then drops to Zero(!) No Error, no nothing - the window with the green graph is still on the screen but nothing happens any more - like it hangs. Only a reboot fix this error. After the reboot all is working fine as there was never a problem... (lol). I think its def. a Win 10 problem and has nothing to do with unraid (i think). And now the most strangest thing: When i use the network environment (not the mapped addresses!), sometimes all is working fine, and sometimes it fails like i described... so there must be a ghost or a goblin in my machine When i use the mapped addresses, it "always" fails at the first attempt - reboot - working... MS sucks! My test-machine (also Win10 1909) with only one NIC can copy to all shares without a problem. Maybe Win10 has a problem with 2 NICs like in my case or it is really a driver problem of the Asus XG-C100C... i don't know... But the most annoing problem still persist: I cant copy files to the root folders of my shares "Movie, TV-Serien and Cache" - what the hell is this??? Attached is a screen of a copy process (20GB) in German (sorry ;-)) Win10 copied 32% (~7GB) and then stopped (0 Bytes/s)...

Ok - command back - this problem is still there... also with the Asus-driver... ☹️

Found the culprit... the Aquantia driver of the 10GB network card. I'm now using an old Asus driver that works with everything - crazy stuff. Apparently the Aquantia driver for Windows 10 x64 has some quirks...

What i can say is this: I changed the security on unraid from private to public, but i cant copy files to the root-share (Movies and TV-Shows) as i could under win 7. So there must be def. some changes on SMB...

Interesting... i downloaded Win10 Pro directly from the MS-Webpage and they offer 1909. My TestPC got the 1909-update a week ago and on the machine of my son MS offered the update directly over the WindowsUpdate. So it's available (here in Austria at least).

I used Win 7 and the support end is near - so whats the problem with 1909? And by the way - who is a Guinea Pig?

Hi folks, have a fresh install of Win 10 PRO (1909) on my Machine and now i can't copy files to unraid. I read something about SMB-Versions but i am not an expert... Strange Thing: I can copy files FROM unraid to Windows 10 - lol? I have tested this over both NICs and both can copy files FROM unraid to Windows 10 BUT NOT TO unraid...

Yes - same network The source is my workstation (Win 7)

I am on the way 😉👍 EDIT: Diags included now unraid-diagnostics-20191206-1936.zip

The material (~10GB) was copied to the SSD, the stream came from Disk10...

The "slowdown-bug" is back in rc8! Copied some material to my server during a stream over plex... what shall i say? Stream runs with 1-2 FPS untill the material was copied to the ssd! lol... i am not amused...

My Flash is 7 years old and still working. There must be an other problem like USB-port or Mainboard...

Installed rc8 and got this: What does "rpmC" mean? 🤨

Strange thing happened right now... i was not able to start the mover > server-reboot, working... weird... 🤨

Can't answer this question because i use non of this things... But i would say no. When i copy from my PC to unraid over the 10GBit-Link using SMB, i reach up to 560MB/s - the maximum what the SSDs can provide. The link itself is faster of corse - up to 1200MB/s.

The only fast way would be a 10GBit-Link between both machines... Another question would be: How fast are your HDDs? They normaly max out at ~180MB/s But in your case it seems Resilio-Sync is the limiting factor...

No... what i meant was an "example of a script" which can make this possible... this is the script-plugin everyone knows...

Example?

Yep - sounds good - let me know if it helps 👍

Its always on cause it doesn't need much RAM. Next time (if it fails again) i make a screenshot and restart the docker again 😉

Will do that but this was the first time i saw this error since i use your docker. The sys has 24GB RAM and 2-4GB used - rest is cache.

Thanks for your reply - i did what you said but there was something wrong - i got a Java-Error... I restarted the docker and now its working again 👍

I have also a weird problem here... Using unraid v6.8.0-rc6 and got this (see picture) when i check my 8TB-Parity drive... The red marked number increases slowly but nothing else happens...

Updated right now - all is working fine so far 😉👍