UnKwicks

Members
  • Posts

    22
  • Joined

  • Last visited

Everything posted by UnKwicks

  1. What tells you that in my case its the network? It seems like we are all in the same boat here.
  2. As you can see in my previous posts we already did several tests with iperf.
  3. I never found a solution for that. I did a lot of research but never found out where this really comes from. i hope you have more luck. Thanks for letting me know 👍
  4. Hey Thanks! Did the update and the dashboard is working again. Also it fixed that my Dashboard was not able to show CPU load bars. Now this is working as well.
  5. I have a problem that my folders do not appear on the Dashboard. It worked for a short time some weeks ago and then it stopped working. Is there any setting I am missing that disables the folders on the Dashboard? I reinstalled Docker Folders to check if this helps but it did not.
  6. did you find a solution? Syncthing is causing high CPU usage on shfs process for me as well.
  7. Thanks. Seems like the update enabled the disk share for the cache drive. I found the disk share scrolling down at shares and set it to private again.
  8. Hi I updated from 6.8.3 to 6.9.0-beta29 the other day. Today I connected via macOS to my unraid system (Finder -> Connect with server) and can see that my whole cache drive is exported and public read/writeable. I only configured two shares to be public available but beneath these two shares the whole cache drive shows up (see image attached). What can I do to solve this? If this is relevant: I followed the steps to solve the excessive ssd writes and moved all data from cache to array, erased and formatted my cache and moved all data back from array to ssd.
  9. I have the same issue. Started some weeks ago. I can not tell what happend. Before CPU usage was shown correctly
  10. Ok, I guess my issue is not SMB related as I thought before. I did some more iperf testing. Let me add the following before I post the results: Using LAN read and write speed is good Issue seems only to appear using wifi on client but then only with unraid. So I did iperf having my MacBook connected via Wifi and Unraid as well as QNAP via LAN. QNAP (LAN) iperf client --> MacBook (Wifi) iperf server: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 556 MBytes 466 Mbits/sec 0 sender [ 5] 0.00-10.00 sec 555 MBytes 466 Mbits/sec receiver Unraid (LAN iperf client --> MacBook (Wifi) iperf server: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 125 MBytes 104 Mbits/sec 0 sender [ 5] 0.00-10.00 sec 123 MBytes 103 Mbits/sec receiver MacBook (Wifi) iperf client --> QNAP (LAN) iperf server: [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 518 MBytes 434 Mbits/sec sender [ 4] 0.00-10.00 sec 517 MBytes 433 Mbits/sec receiver MacBook (Wifi) iperf client --> Unraid (LAN) iperf server: [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 493 MBytes 413 Mbits/sec sender [ 4] 0.00-10.00 sec 492 MBytes 412 Mbits/sec receiver So only sending from Unraid to my MacBook is slow! MTU on all devices is 1500. I attached my diagnostics zip if this helps. TOWER-diagnostics-20200920-1654 2.zip
  11. Thanks a lot for you help. MTU is set to default 1500. Yes the Mac is on Wifi but for my connection to the QNAP NAS as well. Reading from unraid is about 3x slower in this scenario than reading from QNAP. I use macOS 10.15.5. SMB signing is disabled by default on 10.13.4 and higher. I read through each post in this forum I found and googled for several hours. Sadly most posts are 2 years old or older and describe slow speeds in general. I have slow speeds only for reading. As stated in my first post I set "Enhanced macOS interoperability = yes" and this helped a lot. But still having this bad reading speed for a file transfer (dir listing speed is ok now) Is there a special tweak or thread you are talking about?
  12. I did another measure: Activity Monitor in Mac OS shows me a max. of: 14 MB / sec when reading a file from my unraid SMB share. 130 MB / sec when writing a file to my unraid SMB share. Any idea why reading is so slow is appreciated. It seems not to be an issue with my Mac because reading and writing to my QNAP NAS is fast (see first post) Edit: I did some more tests with iperf. Mac as client --> Unraid as server [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 597 MBytes 501 Mbits/sec sender [ 4] 0.00-10.00 sec 596 MBytes 500 Mbits/sec receiver Unraid as client --> Mac as server [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 164 MBytes 137 Mbits/sec 0 sender [ 5] 0.00-10.00 sec 162 MBytes 136 Mbits/sec receiver
  13. Hi guys I read a lot topics here about slow read/write performance with SMB but I did not find something like mine or any solution there helped me. So I start this thread. I switched recently from QNAP to my new unraid build. and I am testing performance right now. First some facts: - I use macOS 10.15.5 as client OS - I have a 12 TB Parity and a 12 TB Array Disk (WD red) - I have SSD cache but not enabled for this share / this test - I use unraid 6.8.3 - I test to copy a 2.5 GB image file. - QNAP NAS and unraid server are connected with a 1 GB ethernet. - My SMB config: veto files = /._*/.DS_Store/ #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end #disable SMB1 for security reasons [global] min protocol = SMB2 Write speed: UNRAID: Copying the file to my unraid Server takes about 55 seconds QNAP: Copying the file to my QNAP NAS takes about 65 seconds So no problems here. Read speed: First I had poor performance for directory listing when browsing the share. so I set "Enhanced macOS interoperability = yes" and this helped a lot. UNRAID: Reading the file from my unraid server takes 2 min 48 sec. QNAP: Reading the file from my QNAP NAS takes 58 sec So reading performance from my unraid server is pretty poor in comparison to my old QNAP. What am I missing here? Some ideas why reading is so slow while writing is fast? Thanks!
  14. Thanks for that info. No idea where the terminal window was but I rebooted and the messages are gone. Thanks!
  15. Hi I have installed several docker containers. (16 in summary) Now I realized that my syslog is flodded with error messages referencing two of my docker containers ("linuxserver/nextcloud" and "zabbix/zabbix-agent2"). Here a short example: Sep 12 22:55:57 MyServer nginx: 2020/09/12 22:55:57 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/" Sep 12 22:56:00 MyServer nginx: 2020/09/12 22:56:00 [error] 11912#11912: *829201 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local" Sep 12 22:56:02 MyServer nginx: 2020/09/12 22:56:02 [error] 11912#11912: *829210 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local" Sep 12 22:56:10 MyServer nginx: 2020/09/12 22:56:10 [error] 11912#11912: *824237 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/token HTTP/2.0", upstream: "http://unix:/var/tmp/nextcloud.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/nextcloud/" Sep 12 22:56:12 MyServer nginx: 2020/09/12 22:56:12 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/" Sep 12 22:56:13 MyServer nginx: 2020/09/12 22:56:13 [error] 11912#11912: *829249 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local" Sep 12 22:56:14 MyServer nginx: 2020/09/12 22:56:14 [error] 11912#11912: *829260 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local" The mentioned client IP is the IP of my local client. Where do these messages come from and how could I solve this problem? Thanks!
  16. thanks for your reply. I am aware of the go file. My question is more how to safely do it. I tried manually to add the location part to the emhttp-server.conf of nginx but my customization does not even survive a nginx reload. So I need to solve this problem first, how to add this part to the server block of the nginx conf. Next step would then be to keep the change to persist on unraid reboot via go file.
  17. Hi for my Monitoring with zabbix I want to call the stub_status of nginx. I saw that the stub_status module is already installed but no location is set. Therefore I have to add this location to the nginx config. #nginx_status location /nginx_status { stub_status; allow 10.0.0.111; deny all; } Does anyone know a way how to do this safely and persists after reboot? Thanks for any idea
  18. Default spin down delay is set to "never" in my case.
  19. I noticed the same. I am new to unraid and set up my server last week. I use 2x12TB WD red. I have the exect same behavior. No read or write but noticeable HDD noise every few seconds. So since I have it with WD and others with Seagate I assume its not related to a specific drive or manufacturer.