BrttClne22

Members
  • Posts

    24
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BrttClne22's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Appreciate the response. Can you expand on what you did to manually restore? Did you just drop your old config back into appdata?
  2. I've stayed at 4.3.9 for a while after the 4.4.0 debacle and am finally considering moving to 4.4.5. I'm assuming it will try to reset my settings again as I see others are still facing this issue in the last few pages. Is there any simple way to combat the settings reset or am I stuck setting everything back up from scratch? I assume my old qbit config will be overwritten each time I place it in the config folder and start the container since that's what happened last time. Is the only option to rebuild it via the UI following the upgrade?
  3. TBH, I can't remember the complete context of this. What I do know: 1. My -arrs are now using the network of my VPN container so their traffic is routed through the same VPN tunnel. 2. I added this really odd feeling firewall rule and disabled "Drop Invalid": Preface: I'm far from a network guru, hobbyist at best. Looking back on it... The VPN containers probably use a internal private network. Whenever the application inside the docker container communicates to your LAN it's technically communicating from the network inside of the container and needs to be routed, thus hitting the firewall. The router has no idea about that network inside the container so it gets marked as invalid? I'd still love to know the definitive answer if anyone has one.
  4. I'm trying to move from OVPN to WireGuard and I'm running into a roadblock. Based on my logs I believe everything is starting properly, however, I cannot reach the webui. If I change 'wireguard' to 'openvpn' in the configuration I can reach the UI as expected. Any ideas? docker run -d --name='binhex-delugevpn' --net='br0.10' --ip='192.168.10.15' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8112'='8112' -e 'TCP_PORT_58846'='58846' -e 'TCP_PORT_58946'='58946' -e 'UDP_PORT_58946'='58946' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxxxxxxxx' -e 'VPN_PASS'='xxxxxxxxxx' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='192.168.10.1/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'ADDITIONAL_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/disks/unassigned/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2020-10-15 23:56:08.672244 [info] System information Linux 843aa7a70558 5.7.8-Unraid #1 SMP Thu Jul 9 11:10:03 PDT 2020 x86_64 GNU/Linux 2020-10-15 23:56:08.707765 [info] OS_ARCH defined as 'x86-64' 2020-10-15 23:56:08.755273 [info] PUID defined as '99' 2020-10-15 23:56:09.103466 [info] PGID defined as '100' 2020-10-15 23:56:09.722302 [info] UMASK defined as '000' 2020-10-15 23:56:09.741216 [info] Permissions already set for volume mappings 2020-10-15 23:56:09.841045 [info] Deleting files in /tmp (non recursive)... 2020-10-15 23:56:09.884032 [info] VPN_ENABLED defined as 'yes' 2020-10-15 23:56:09.906021 [info] VPN_CLIENT defined as 'wireguard' 2020-10-15 23:56:09.925092 [info] VPN_PROV defined as 'pia' 2020-10-15 23:56:14.841527 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf 2020-10-15 23:56:14.875796 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network' 2020-10-15 23:56:14.934189 [info] VPN_REMOTE_PORT defined as '1337' 2020-10-15 23:56:14.953274 [info] VPN_DEVICE_TYPE defined as 'wg0' 2020-10-15 23:56:14.971720 [info] VPN_REMOTE_PROTOCOL defined as 'udp' 2020-10-15 23:56:14.995647 [info] LAN_NETWORK defined as '192.168.10.1/24' 2020-10-15 23:56:15.019885 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' 2020-10-15 23:56:15.039629 [info] VPN_USER defined as 'xxxxxxxx' 2020-10-15 23:56:15.063950 [info] VPN_PASS defined as 'xxxxxxxx' 2020-10-15 23:56:15.088321 [info] STRICT_PORT_FORWARD defined as 'yes' 2020-10-15 23:56:15.108386 [info] ENABLE_PRIVOXY defined as 'no' 2020-10-15 23:56:15.127681 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports 2020-10-15 23:56:15.153110 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-10-15 23:56:15.174085 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2020-10-15 23:56:15.199612 [info] Starting Supervisor... 2020-10-15 23:56:17,177 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2020-10-15 23:56:17,177 INFO Set uid to user 0 succeeded 2020-10-15 23:56:17,207 INFO supervisord started with pid 6 2020-10-15 23:56:18,209 INFO spawned: 'start-script' with pid 157 2020-10-15 23:56:18,210 INFO spawned: 'watchdog-script' with pid 158 2020-10-15 23:56:18,210 INFO reaped unknown pid 7 (exit status 0) 2020-10-15 23:56:18,226 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2020-10-15 23:56:18,227 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-10-15 23:56:18,227 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-10-15 23:56:18,229 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2020-10-15 23:56:18,231 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2020-10-15 23:56:18,234 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2020-10-15 23:56:18,237 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2020-10-15 23:56:18,239 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2020-10-15 23:56:18,242 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2020-10-15 23:56:18,245 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2020-10-15 23:56:18,247 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2020-10-15 23:56:19,487 DEBG 'start-script' stderr output: parse error: Invalid numeric literal at line 4, column 0 2020-10-15 23:56:20,125 DEBG 'start-script' stdout output: [info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'... 2020-10-15 23:56:20,642 DEBG 'start-script' stdout output: [info] Default route for container is 192.168.10.1 2020-10-15 23:56:20,654 DEBG 'start-script' stdout output: [info] Docker network defined as 192.168.10.0/24 2020-10-15 23:56:20,657 DEBG 'start-script' stdout output: [info] Adding 192.168.10.1/24 as route via docker eth0 2020-10-15 23:56:20,657 DEBG 'start-script' stderr output: Error: Invalid prefix for given prefix length. 2020-10-15 23:56:20,658 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2020-10-15 23:56:20,658 DEBG 'start-script' stdout output: default via 192.168.10.1 dev eth0 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.15 2020-10-15 23:56:20,658 DEBG 'start-script' stdout output: -------------------- 2020-10-15 23:56:20,661 DEBG 'start-script' stdout output: iptable_mangle 16384 2 ip_tables 28672 8 iptable_filter,iptable_raw,iptable_nat,iptable_mangle 2020-10-15 23:56:20,661 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2020-10-15 23:56:20,749 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2020-10-15 23:56:20,750 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 192.168.10.0/24 -d 192.168.10.0/24 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1337 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.10.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i wg0 -j ACCEPT -A OUTPUT -s 192.168.10.0/24 -d 192.168.10.0/24 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1337 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.10.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT 2020-10-15 23:56:20,751 DEBG 'start-script' stdout output: -------------------- 2020-10-15 23:56:20,753 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2020-10-15 23:56:20,793 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2020-10-15 23:56:20,798 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2020-10-15 23:56:20,799 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2020-10-15 23:56:20,807 DEBG 'start-script' stderr output: [#] ip -4 address add 10.25.245.109/32 dev wg0 2020-10-15 23:56:20,812 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2020-10-15 23:56:20,838 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2020-10-15 23:56:20,838 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2020-10-15 23:56:20,839 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2020-10-15 23:56:20,840 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2020-10-15 23:56:20,842 DEBG 'start-script' stderr output: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1 2020-10-15 23:56:20,851 DEBG 'start-script' stderr output: [#] iptables-restore -n 2020-10-15 23:56:20,871 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2020-10-15 23:56:22,128 DEBG 'start-script' stdout output: [info] Attempting to get external IP using Name Server 'ns1.google.com'... 2020-10-15 23:56:37,514 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 212.102.34.182 2020-10-15 23:56:37,515 DEBG 'start-script' stdout output: [info] WireGuard interface 'up' 2020-10-15 23:56:37,515 DEBG 'start-script' stdout output: [info] Script started to assign incoming port 2020-10-15 23:56:37,516 DEBG 'start-script' stdout output: [info] Port forwarding is enabled [info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled... 2020-10-15 23:56:39,111 DEBG 'start-script' stdout output: [info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding 2020-10-15 23:56:39,111 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2020-10-15 23:56:39,112 DEBG 'start-script' stdout output: [info] al.privacy.network [info] ad.privacy.network [info] austria.privacy.network [info] brussels.privacy.network [info] ba.privacy.network [info] sofia.privacy.network [info] czech.privacy.network [info] denmark.privacy.network [info] ee.privacy.network [info] fi.privacy.network [info] france.privacy.network [info] de-frankfurt.privacy.network [info] de-berlin.privacy.network [info] gr.privacy.network [info] hungary.privacy.network 2020-10-15 23:56:39,112 DEBG 'start-script' stdout output: [info] is.privacy.network [info] ireland.privacy.network [info] man.privacy.network [info] italy.privacy.network [info] lv.privacy.network [info] liechtenstein.privacy.network [info] lt.privacy.network [info] lu.privacy.network [info] mk.privacy.network [info] malta.privacy.network [info] md.privacy.network [info] monaco.privacy.network [info] montenegro.privacy.network [info] nl-amsterdam.privacy.network [info] no.privacy.network [info] poland.privacy.network [info] pt.privacy.network [info] ro.privacy.network [info] rs.privacy.network [info] sk.privacy.network [info] spain.privacy.network [info] sweden.privacy.network [info] swiss.privacy.network [info] ua.privacy.network [info] uk-manchester.privacy.network [info] uk-london.privacy.network [info] uk-southampton.privacy.network [info] bahamas.privacy.network [info] ca-vancouver.privacy.network [info] ca-ontario.privacy.network [info] ca-montreal.privacy.network [info] ca-toronto.privacy.network [info] greenland.privacy.network [info] mexico.privacy.network [info] panama.privacy.network [info] ar.privacy.network [info] br.privacy.network [info] venezuela.privacy.network [info] yerevan.privacy.network [info] cambodia.privacy.network [info] china.privacy.network [info] cyprus.privacy.network [info] georgia.privacy.network [info] hk.privacy.network [info] in.privacy.network [info] iran.privacy.network 2020-10-15 23:56:39,112 DEBG 'start-script' stdout output: [info] israel.privacy.network [info] japan.privacy.network [info] kazakhstan.privacy.network [info] philippines.privacy.network [info] qatar.privacy.network [info] saudiarabia.privacy.network [info] sg.privacy.network [info] srilanka.privacy.network [info] taiwan.privacy.network [info] tr.privacy.network [info] ae.privacy.network [info] vietnam.privacy.network [info] aus-perth.privacy.network [info] au-sydney.privacy.network [info] aus-melbourne.privacy.network [info] nz.privacy.network [info] dz.privacy.network [info] egypt.privacy.network [info] morocco.privacy.network [info] nigeria.privacy.network [info] za.privacy.network 2020-10-15 23:56:41,732 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '47146' 2020-10-15 23:56:42,196 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.25.245.109 different, marking for reconfigure 2020-10-15 23:56:42,261 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2020-10-15 23:56:42,263 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2020-10-15 23:56:42,263 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 47146 different, marking for reconfigure 2020-10-15 23:56:42,270 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2020-10-15 23:56:44,217 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.26.129.208' [info] Deluge key 'listen_interface' will have a new value '10.25.245.109' [info] Writing changes to Deluge config file '/config/core.conf'... 2020-10-15 23:56:44,374 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'wg0' [info] Deluge key 'outgoing_interface' will have a new value 'wg0' [info] Writing changes to Deluge config file '/config/core.conf'... 2020-10-15 23:56:44,501 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of '9b89b378e26b43ed89a18c7b060d30de' [info] Deluge key 'default_daemon' will have a new value '9b89b378e26b43ed89a18c7b060d30de' [info] Writing changes to Deluge config file '/config/web.conf'... 2020-10-15 23:56:44,950 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2020-10-15 23:56:45,411 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2020-10-15 23:56:47,515 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2020-10-15 23:56:49,315 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (47146, 47146) Configuration value successfully updated. 2020-10-15 23:56:51,151 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-10-15 23:56:51,152 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2020-10-15 23:56:51,152 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started
  5. I'm no pro, but have you tried to enable MSI in regedit? https://wiki.unraid.net/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support
  6. I was trying to decide whether this was more of a Ubiquiti, Unraid or Docker question, but I figured you all would have a more well-rounded knowledge of the situation in it's entirety. So here goes: The Issue My sonarr (192.168.10.3) and radarr (192.168.10.4) dockers cannot communicate with my rtorrent (192.168.10.6) docker, but they can talk to sabnzbd (192.168.10.7). All stated dockers are assigned IP addresses via br0.10 with a gateway/mask of 192.168.10.1/24. I can see the traffic is being dropped by my firewall rules (see below), but my understanding is the packets should not hit the firewall because they're in the same VLAN/subnet (?). Related Network Equipment Unifi Cloud Key Unifi USG Unifi 16 port Switch w/ 1GB LAG to Unraid Server Problem Dockers linuxserver/sonarr:preview (br0.10, 192.168.10.3) linuxserver/radarr:latest (br0.10, 192.168.10.4) binhex-rtorrentvpn:latest (br0.10, 192.168.10.6) I can connect to this one fine from sonarr/radarr on the other hand: binhex-sabnzbdvpn:latest (br0.10, 192.168.10.7) Network INTERFACE GATEWAY/MASK br0.10 192.168.10.1/24 Relevant Firewall Rules (LAN IN) RULE DESCRIPTION ACTION PROTOCOLS SOURCE DESTINATION 2000 Allow Established/Related Accept All Protocols 2001 Drop Invalid Drop All Protocols (Pretty specific rules unrelated to dockers here. All are action=Allow) 2009 Disable Intervlan Routing Drop All Protocols Groups: RFC1918 Groups: RFC1918 According to Firewall Logging (why would these hit the firewall to begin with?) The packets from sonarr/radarr to rtorrent are dropped at rule 2001 when it is enabled. The packets are dropped at rule 2009 when 2001 is disabled. The connection is successful when both 2001 and 2009 are turned off. Example Firewall Logs (I believe the connection is initiated from sonarr/radarr so I believe this is the response being dropped?) With '2001 - Drop Invalid' enabled [LAN_IN-2001-D]IN=eth1.10 OUT=eth1.10 MAC=78:8a:20:40:bd:e8:02:42:c0:a8:0a:06:08:00:45:00:00:3c SRC=192.168.10.6 DST=192.168.10.4 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=TCP SPT=9443 DPT=51068 WINDOW=43440 RES=0x00 ACK SYN URGP=0 With '2009 - Disable Intervlan Routing' enabled (2001 disabled) [LAN_IN-2009-D]IN=eth1.10 OUT=eth1.10 MAC=78:8a:20:40:bd:e8:02:42:c0:a8:0a:06:08:00:45:00:00:3c SRC=192.168.10.6 DST=192.168.10.4 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=0 DF PROTO=TCP SPT=9443 DPT=52090 WINDOW=43440 RES=0x00 ACK SYN URGP=0 Not in logs, but connection is successful in sonarr/radarr when both rules are disabled. Any thoughts, ideas are much appreciated!
  7. I can confirm this worked for me although I did end up doing a blanket auth on the proxy. Thanks again!
  8. I'll give this a shot when I get home. Just out of curiosity, in your setup, did you disable auth in the container and just use auth on the proxy? That seems like a good blanket fix. You're the man binhex! Thanks for looking into it so quickly. Beer will definitely be coming your way.
  9. For reference... (And in NZB360, the upload/download speed update every 5 seconds so it's definitely making a full connection)
  10. Interesting. When I go to the :9443/ in a browser I get the default browser authentication popup and I log in with the username/password I created with the script inside the container. I can definitely verify that Sonarr/Radarr/NZB360 don't require authentication to the :9443/rpc2 endpoint currently. Maybe I should delete my container/appdata and start from scratch?
  11. I admittedly don't have a deep understanding of rTorrent/ruTorrent but based on the little I know, port 5000 would be rTorrent (the backend) and 9080/9443 would be ruTorrent (the frontend, which is what I'd like to reverse proxy). This RPC2 endpoint seems to live on the front end (9080/9443). Within my network, I've currently got NZB360 (an android app) pointed at https://192.168.1.4:9443/RPC2 (ports are all default) and it's working with no username or password.
  12. I was considering using a reverse proxy to make rutorrent accessible from the web (mainly for NZB360), however, I was doing some research before I did so and it seems that RPC2 doesn't require auth (I think it used to?). To test, I removed my username/password from Sonarr, Radarr and NZB360, all three seem to connect without any username/password. Are others seeing this? I don't think I've modified any configuration that would effect this. I've been using this container for a while but I think the deepest thing I've done configuration wise is add my own username/password and delete the default using the scripts.
  13. Thanks for pointing that out, very interesting thread. After reading it, I did a write test of a 25 GB file from my Windows 10 VM (running on a separate NVME drive) to the media share (Samsung Pro SSD) and speeds were VERY similar to the /mnt/cache test. That puts my mind a little more at ease.
  14. Hoping one of you smart souls can shed some light on an issue I've found today. I've done a lot of Googling, but no dice. I had been experiencing some iowait lockups when radarr/sonarr moved a file from an unassigned disk to my 'media' share with the cache setting to 'Yes'. I confirmed that turning the cache setting to 'Off', mitigated the iowait issues but I would prefer it be written to the cache first. Using a write speed test script posted by @johnnie.black, I ran two separate tests against my cache drive. When formatted as BTRFS (sorry, I don't have the exact results for these): /mnt/cache/test.dat 450 MBps /mnt/user/media/test.dat 60 MBps I ditched BTRFS, thinking that may be the problem. I didn't really have a use case for it anyways as I only have a single cache drive atm. Here are the same tests with XFS writing 10240000000 bytes to: /mnt/cache/test.dat 3681144+0 records in 3681144+0 records out 3769491456 bytes (3.8 GB, 3.5 GiB) copied, 5.00031 s, 754 MB/s 6741953+0 records in 6741953+0 records out 6903759872 bytes (6.9 GB, 6.4 GiB) copied, 10.0016 s, 690 MB/s 9420809+0 records in 9420809+0 records out 9646908416 bytes (9.6 GB, 9.0 GiB) copied, 15.0049 s, 643 MB/s 10000000+0 records in 10000000+0 records out 10240000000 bytes (10 GB, 9.5 GiB) copied, 16.1416 s, 634 MB/s write complete, syncing removed '/mnt/cache/test.dat' writing 10240000000 bytes to: /mnt/user/media/test.dat 327258+0 records in 327258+0 records out 335112192 bytes (335 MB, 320 MiB) copied, 5.00024 s, 67.0 MB/s 664063+0 records in 664063+0 records out 680000512 bytes (680 MB, 648 MiB) copied, 10.0015 s, 68.0 MB/s 993568+0 records in 993568+0 records out 1017413632 bytes (1.0 GB, 970 MiB) copied, 15.0029 s, 67.8 MB/s 1321207+0 records in 1321207+0 records out 1352915968 bytes (1.4 GB, 1.3 GiB) copied, 20.0045 s, 67.6 MB/s 1652369+0 records in 1652369+0 records out 1692025856 bytes (1.7 GB, 1.6 GiB) copied, 25.0059 s, 67.7 MB/s 1988734+0 records in 1988734+0 records out 2036463616 bytes (2.0 GB, 1.9 GiB) copied, 30.0073 s, 67.9 MB/s 2316253+0 records in 2316253+0 records out 2371843072 bytes (2.4 GB, 2.2 GiB) copied, 35.0089 s, 67.7 MB/s 2649459+0 records in 2649459+0 records out 2713046016 bytes (2.7 GB, 2.5 GiB) copied, 40.0102 s, 67.8 MB/s 2984946+0 records in 2984946+0 records out 3056584704 bytes (3.1 GB, 2.8 GiB) copied, 45.0115 s, 67.9 MB/s 3321507+0 records in 3321507+0 records out 3401223168 bytes (3.4 GB, 3.2 GiB) copied, 50.0129 s, 68.0 MB/s 3651156+0 records in 3651156+0 records out 3738783744 bytes (3.7 GB, 3.5 GiB) copied, 55.0142 s, 68.0 MB/s 3980471+0 records in 3980471+0 records out 4076002304 bytes (4.1 GB, 3.8 GiB) copied, 60.0157 s, 67.9 MB/s 4314105+0 records in 4314105+0 records out 4417643520 bytes (4.4 GB, 4.1 GiB) copied, 65.0171 s, 67.9 MB/s 4647805+0 records in 4647805+0 records out 4759352320 bytes (4.8 GB, 4.4 GiB) copied, 70.0184 s, 68.0 MB/s 4981473+0 records in 4981473+0 records out 5101028352 bytes (5.1 GB, 4.8 GiB) copied, 75.02 s, 68.0 MB/s 5315667+0 records in 5315667+0 records out 5443243008 bytes (5.4 GB, 5.1 GiB) copied, 80.0215 s, 68.0 MB/s 5645479+0 records in 5645479+0 records out 5780970496 bytes (5.8 GB, 5.4 GiB) copied, 85.0229 s, 68.0 MB/s 5974952+0 records in 5974952+0 records out 6118350848 bytes (6.1 GB, 5.7 GiB) copied, 90.0242 s, 68.0 MB/s 6310587+0 records in 6310587+0 records out 6462041088 bytes (6.5 GB, 6.0 GiB) copied, 95.0256 s, 68.0 MB/s 6638667+0 records in 6638667+0 records out 6797995008 bytes (6.8 GB, 6.3 GiB) copied, 100.027 s, 68.0 MB/s 6965658+0 records in 6965658+0 records out 7132833792 bytes (7.1 GB, 6.6 GiB) copied, 105.029 s, 67.9 MB/s 7297553+0 records in 7297553+0 records out 7472694272 bytes (7.5 GB, 7.0 GiB) copied, 110.03 s, 67.9 MB/s 7625676+0 records in 7625676+0 records out 7808692224 bytes (7.8 GB, 7.3 GiB) copied, 115.033 s, 67.9 MB/s 7953216+0 records in 7953216+0 records out 8144093184 bytes (8.1 GB, 7.6 GiB) copied, 120.035 s, 67.8 MB/s 8282188+0 records in 8282188+0 records out 8480960512 bytes (8.5 GB, 7.9 GiB) copied, 125.037 s, 67.8 MB/s 8613901+0 records in 8613901+0 records out 8820634624 bytes (8.8 GB, 8.2 GiB) copied, 130.04 s, 67.8 MB/s Just to prove that it is in fact set to use the cache drive (I also double checked the file system of /mnt/cache/media as it was writing): Diagnostics attached. Thanks for your help! zeus-diagnostics-20180515-2039.zip
  15. I've been piddling around with this and I think it has resolved itself.