tmchow

I have a few questions about having a drive sitting as a warm standby for when there is a drive failure. 1. Can the replacement drive be smaller than the one it's replacing provided it can fit the data that was on the failed drive? I have 6TB drives mostly, but have a few good 3TB drives sitting around. Plan was to use these as a warm standby in case the 6TB ever fail. 2. What is the proper procedure for prepping the drives so I can get back up running as fast as possible when there is a drive failure? I flirted with the idea of using these drives mounted outside the array, but changed my mind. I have already used the preclear plugin to do a 2 pass preclear on them. Wondering what I need to really do to get these drives ready? 3. Where can I find a list of the proper procedure to execute a drive replacement once there is a failure?

FYI, after a bit of wrestling, I got SSH working in the Snoopy Ubuntu docker. I had to: 1. Generate SSH keys with: sudo ssh-keygen -t rsa1 -f /etc/ssh/ssh_host_rsa_key sudo ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key 3. (Optional) Edited /etc/ssh/sshd_config to change my port from 22 to another port number (I used 1111) so it didn't interfere with the other SSH servers I have behind my router. Don't forget to forward port 22 (or whatever custom port you choose) in your router config.

Only ubuntu container I can find is from Snoopy's but it seems to only have remote desktop and not sure how to enable SSH straight into it. I've confines Openssh-server is installed and configured the port to be 2222. Configured the docker to use tcp 2222 along with port forwarding setup on my router. I can't even ssh using local host. Any ideas? ssh ubuntu@localhost -p 2222 https://lime-technology.com/forum/index.php?topic=43610.0

Thanks I'll check it out.

I need to give someone access to my system for a short period of time (a few days), and only want to give access to a specific set of shares and nothing else. What's the simplest way to do this? I was thinking that an easy way would be a docker container with some standard debian jessie install restricted only to a given share. After the access is not needed, just kill the container. Thoughts?

I have a 250GB SSD as a cache drive. It's too small to also be my torrent seed share. I can either have the torrents in the array or on an HD I mount outside the array. I initially thought having it inside the array was a bad idea due to parity checks but someone recent replies correcting me that it's only impacting parity on writes, but reads.

For my education, what is the reason to put the docker.img on the drive mounted outside the array? I'm not following the "won't start until it is mounted" part. Right now docker.img is on cache drive only.

It's not cost effective to buy a cache drive of several TB in size. My seeding on my desktop PC (which I'm migrating to unraid) is nearly 2TB in size.

Super odd. This got resolved. How? I rebooted. No idea how that fixed things, but it did. My drive access is quick and all file operations are fast now too. I had to reboot to physically relocate my server as well as install a few more HDs I had lying around that I wanted to add to the array. Rebooted and presto. Accesses to the shares are now lightning quick and as fast as my previous Windows Server.

What is the most common use case for using this plugin? I've seen references of running dockers and VMs from it, but given how relatively cheap SSDs are for cache drives, it seems far easier to just use cache-only shares for that. Is it for cases where you don't want to involve perf hit from using the array or involving the parity drive such as seeding torrents? Since torrent seeds could be huge, I can see why someone wouldn't want to put those files on the cache drive (and the speed of an SSD isn't as important for seeding torrents). Would love to hear about people's use cases for this.

I have my torrents seeding from /mnt/disk3/torrents/seeds/ but realized that this will still spin the parity disk. I know I could go directly to a cache-only share, but my cache drive is 250GB and I know my torrents will far exceed that in the near future. Is the best option to copy finished torrents to a disk mounted outside the array (using the unassigned devices plugin)? This would then be: - Deluge downloads torrents to cache-only share (/mnt/cache/downloads/torrents/) - On completion, it moves them to <disk mounted outside array> so it can seed from there - Sonarr and Couch Potato monitor the <disk mounted outside array> and copy what it needs to back to the array into my media share (which is then protected by parity and redundancy).

Found a solution... i just had to reboot the server and magically dashboard works fine with no delays. Odd.

I have Ghostery, the chrome extension, for ad blocking but it's whitelisted the web UI. Only other antivirus software I have is what's built into Windows 10. Nothing has changed on that front since this problem started. I wonder if one of the plugins is causing this?

thanks all!

I'm wondering if there is any problem with my router being the SMB Local Master Browser on my network vs my unraid box? I didn't even know my router was acting as one, until i installed the Dynamix Local Master plugin which told me my router was. My router is running the Merlin firmware, which advertises as one of it's features that it can act as a local master browser. Are there any consequences to having my router be the local master browser vs the unraid box?

For some reason, my Web UI "Dashboard" is hanging after an initial loading, before info is filled in. Here is what it looks like when I hit it, notice no values for most of the tables: It'll just sit and sit there. Browser will recognize a click on other navigation and the page will sit there with the chrome spinner in the tab going. Eventually it'll navigate to that second page. It didn't always do this.. how can i debug?

the Powerdown button (and Reboot button) shows on the Main Tab if the array is stopped, but not if it is started There is the Dynamix System Buttons plugin available for adding it as an option at the top level of the GUI. Thank you!!

Using the above, I got my backup script working. Initially had a problem restarting docker containers and it was a typo in the variable name in my script I'm only backing up appdata, as I can easily re-setup docker.img. #!/bin/bash #Logfile location LOG_FILE=/var/log/cache_backup.log BACKUP_ROOT=/mnt/disk3/backups/unraid/appdata echo `date` "Starting cache drive appdata backup to " ${BACKUP_ROOT} >> $LOG_FILE #Stop plugin services located in /etc/rc.d/ # enter in plugins to stop here, if any #stop dockers # find running docker containers declare -a Containers=(`docker ps -q`) # stop running containers for CONT in "${Containers[@]}" do echo `date` " Stopping Container: " $CONT >> $LOG_FILE docker stop $CONT >> $LOG_FILE done #Backup cache via rsync to the latest folder /usr/bin/rsync -avrtH --delete /mnt/cache/appdata/ ${BACKUP_ROOT} >> $LOG_FILE #Make a compressed archive into the archive folder so we can rotate #tar -czvf ${BACKUP_ROOT}/archive/cache-appdata_$(date +%y%m%d).tar.gz ${BACKUP_ROOT}/latest/ >> $LOG_FILE #Start plugin services # enter in plugins to start here, if any #start dockers previousy stopped for CONT in "${Containers[@]}" do echo `date` " Starting Container: " $CONT >> $LOG_FILE docker start $CONT >> $LOG_FILE done #notify about backup /usr/local/emhttp/plugins/dynamix/scripts/notify -i normal -s "Cache Drive AppData Backup Completed" -d "Cache Drive AppData Backup completed at `date`" The notification is slick because it shows the notification in the Web UI. Great confirmation it ran, and since it's weekly it's not a big deal. I initially was messing with rotating compressed tars, but ended up ditching it because I realized I have crashplan running in a docker backing up this directory and it handles all that automatically as seen in this config screenshot: To kick the script off, I'm using the tip earlier in the thread about using cron, by creating /boot/config/plugins/cache_backup/cache_backup.cron: # Weekly cache backup 0 0 5,12,19,26 * * /boot/scripts/cache_backup.sh &> /dev/null Backups every at midnight on the 5th, 12th, 19th and 26th of every month.

I recall there being an option in the Web UI to power down or reboot. I can't seem to find them anywhere and don't want to resort to just using the command line.

I was experimenting with trying to get jumbo frames to work on my network but realized it wasn't going to help me much since my main desktop PC that I connect to my Unraid server with is communicating over 802.11ac wifi. So I reverted the MTU changes. One thing I noticed today was that the network interfaces for the docker containers (at least that's what I think they are) show an MTU of 9014, but eth0 is back at 1500. Not sure if this is because docker was enabled when I had the MTU changed to 9014 I'm assuming that they should all match. Is it just a matter of restarting the docker daemon or something else? here is output from ifconfig. Notice eth0 is MTU=1500, and most everything else is MTU=9014. root@Tower:/boot/config# ifconfig as0t0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.224.1 netmask 255.255.255.0 destination 172.27.224.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t1: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.225.1 netmask 255.255.255.0 destination 172.27.225.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t2: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.226.1 netmask 255.255.255.0 destination 172.27.226.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t3: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.227.1 netmask 255.255.255.0 destination 172.27.227.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t4: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.228.1 netmask 255.255.255.0 destination 172.27.228.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t5: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.229.1 netmask 255.255.255.0 destination 172.27.229.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t6: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.230.1 netmask 255.255.255.0 destination 172.27.230.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t7: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.231.1 netmask 255.255.255.0 destination 172.27.231.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t8: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.232.1 netmask 255.255.255.0 destination 172.27.232.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t9: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.233.1 netmask 255.255.255.0 destination 172.27.233.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t10: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.234.1 netmask 255.255.255.0 destination 172.27.234.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t11: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.235.1 netmask 255.255.255.0 destination 172.27.235.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t12: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.236.1 netmask 255.255.255.0 destination 172.27.236.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t13: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.237.1 netmask 255.255.255.0 destination 172.27.237.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t14: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.238.1 netmask 255.255.255.0 destination 172.27.238.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t15: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.239.1 netmask 255.255.255.0 destination 172.27.239.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 06:8b:76:b7:f5:0d txqueuelen 0 (Ethernet) RX packets 32463330 bytes 4724517316 (4.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 42074423 bytes 150142060462 (139.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.161 netmask 255.255.255.0 broadcast 192.168.1.255 ether d0:50:99:6f:f8:dc txqueuelen 1000 (Ethernet) RX packets 3737745349 bytes 5543995151653 (5.0 TiB) RX errors 0 dropped 47225 overruns 1 frame 0 TX packets 457213270 bytes 89063610077 (82.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf7400000-f747ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 3029127 bytes 1572045339 (1.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3029127 bytes 1572045339 (1.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth3cc4ce6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether c6:9b:37:c4:da:b5 txqueuelen 0 (Ethernet) RX packets 22111 bytes 13578262 (12.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 312458 bytes 49262154 (46.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4570d1e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 06:8b:76:b7:f5:0d txqueuelen 0 (Ethernet) RX packets 3843 bytes 264600 (258.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 190471 bytes 47993673 (45.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4ee1280: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether e6:11:7b:bf:1f:12 txqueuelen 0 (Ethernet) RX packets 12633206 bytes 3284798965 (3.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 17592166 bytes 40794143395 (37.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethd0c48d5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether ba:6e:7b:b5:70:e6 txqueuelen 0 (Ethernet) RX packets 390846 bytes 153011784 (145.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 674410 bytes 302327780 (288.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethdf28aad: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 7a:cf:b8:35:d9:bc txqueuelen 0 (Ethernet) RX packets 19346524 bytes 1682816930 (1.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24152100 bytes 108135357168 (100.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetheff27f9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 9e:f7:e6:5c:0f:fd txqueuelen 0 (Ethernet) RX packets 2519 bytes 560959 (547.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 167224 bytes 36699419 (34.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I was experimenting with trying to get jumbo frames to work on my network but realized it wasn't going to help me much since my main desktop PC that I connect to my Unraid server with is communicating over 802.11ac wifi. So I reverted the MTU changes. One thing I noticed today was that the network interfaces for the docker containers (at least that's what I think they are) show an MTU of 9014, but eth0 is back at 1500. Not sure if this is because docker was enabled when I had the MTU changed to 9014 I'm assuming that they should all match. Is it just a matter of restarting the docker daemon or something else? here is output from ifconfig. Notice eth0 is MTU=1500, and most everything else is MTU=9014. root@Tower:/boot/config# ifconfig as0t0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.224.1 netmask 255.255.255.0 destination 172.27.224.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t1: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.225.1 netmask 255.255.255.0 destination 172.27.225.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t2: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.226.1 netmask 255.255.255.0 destination 172.27.226.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t3: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.227.1 netmask 255.255.255.0 destination 172.27.227.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t4: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.228.1 netmask 255.255.255.0 destination 172.27.228.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t5: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.229.1 netmask 255.255.255.0 destination 172.27.229.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t6: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.230.1 netmask 255.255.255.0 destination 172.27.230.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t7: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.231.1 netmask 255.255.255.0 destination 172.27.231.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t8: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.232.1 netmask 255.255.255.0 destination 172.27.232.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t9: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.233.1 netmask 255.255.255.0 destination 172.27.233.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t10: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.234.1 netmask 255.255.255.0 destination 172.27.234.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t11: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.235.1 netmask 255.255.255.0 destination 172.27.235.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t12: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.236.1 netmask 255.255.255.0 destination 172.27.236.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t13: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.237.1 netmask 255.255.255.0 destination 172.27.237.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t14: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.238.1 netmask 255.255.255.0 destination 172.27.238.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 as0t15: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 172.27.239.1 netmask 255.255.255.0 destination 172.27.239.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 200 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 06:8b:76:b7:f5:0d txqueuelen 0 (Ethernet) RX packets 32463330 bytes 4724517316 (4.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 42074423 bytes 150142060462 (139.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.161 netmask 255.255.255.0 broadcast 192.168.1.255 ether d0:50:99:6f:f8:dc txqueuelen 1000 (Ethernet) RX packets 3737745349 bytes 5543995151653 (5.0 TiB) RX errors 0 dropped 47225 overruns 1 frame 0 TX packets 457213270 bytes 89063610077 (82.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf7400000-f747ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 3029127 bytes 1572045339 (1.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3029127 bytes 1572045339 (1.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth3cc4ce6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether c6:9b:37:c4:da:b5 txqueuelen 0 (Ethernet) RX packets 22111 bytes 13578262 (12.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 312458 bytes 49262154 (46.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4570d1e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 06:8b:76:b7:f5:0d txqueuelen 0 (Ethernet) RX packets 3843 bytes 264600 (258.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 190471 bytes 47993673 (45.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth4ee1280: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether e6:11:7b:bf:1f:12 txqueuelen 0 (Ethernet) RX packets 12633206 bytes 3284798965 (3.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 17592166 bytes 40794143395 (37.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethd0c48d5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether ba:6e:7b:b5:70:e6 txqueuelen 0 (Ethernet) RX packets 390846 bytes 153011784 (145.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 674410 bytes 302327780 (288.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethdf28aad: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 7a:cf:b8:35:d9:bc txqueuelen 0 (Ethernet) RX packets 19346524 bytes 1682816930 (1.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24152100 bytes 108135357168 (100.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetheff27f9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9014 ether 9e:f7:e6:5c:0f:fd txqueuelen 0 (Ethernet) RX packets 2519 bytes 560959 (547.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 167224 bytes 36699419 (34.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Update on more investigation on this and things I tried: Teracopy Both Windows file copy and Teracopy are slow. Teracopy seems to hang as long as built-in standard file copy. Trying SCP Over SCP, the file transfer DOES work and start transfer immediately. Here is a screenshot of the status screen from WinSCP as soon as I initiated the copy it started immediately (although transfer speed is pretty slow): Disabling Remote Differential Compression I tried turning off Remote Differential Compression, as that was suggested in one of the threads that @betaman posted. No impact, same delays. (Note: Although no *nix specific, this technet blog also goes into debunking the myth that turning off this setting makes anything faster.) Investigated low disk space Multiple threads talked about suspicion of low disk space being the culprit. Whether that's the cause for other people, it's not the cause here because I don't have low disk space yet encounter the slow file operations. See this screenshot of free disk space in my array: Syslog errors/warnings I increased the verbosity of the logging by adding "log level = 2" and "syslog = 2" to /boot/config/smb-extra.conf and see these 2 lines repeatedly in the syslog. Not sure if it's relevant Apr 1 18:30:04 Tower smbd[6995]: idmap range not specified for domain '*' WARNING: The "null passwords" option is deprecated

I just tried this but on the unraid side with this line in /boot/config/smb-extra.conf in the [global] section: max protocol = SMB2 Didn't have any effect.

Ugh, I hadn't seen those before doing this huge migration from Windows Server to Unraid. But this isn't limited to only windows. My Macbook also has this problem in finder. I normally don't use it at home since I have a windows desktop but I opened it to just try connecting and it times out like crazy. It can see //tower and the shares, but when I click on one to view contents in Finder, it timeouts repeatedly and just hangs.

Also just noticed that even doing things like mapping drives is slow. However, once they are mapped the drives open fine. It's as if something is interfering with the initial communication/handshaking between my PC and Unraid. Is no one else experiencing this?