[Poor file transfer performance over WireGuard]

On 3/7/2023 at 5:30 AM, thymon said:

Hello,

 

Same here
Test iperf3 unraid --> unraid-backup

(30Mbits) 

root@Unraid-Backup:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 10.253.0.1, port 54148
[  5] local 10.253.0.2 port 5201 connected to 10.253.0.1 port 54162
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  2.26 MBytes  19.0 Mbits/sec                  
[  5]   1.00-2.00   sec  2.63 MBytes  22.1 Mbits/sec                  
[  5]   2.00-3.00   sec  2.75 MBytes  23.1 Mbits/sec                  
[  5]   3.00-4.00   sec  3.00 MBytes  25.2 Mbits/sec                  
[  5]   4.00-5.00   sec  3.09 MBytes  25.9 Mbits/sec                  
[  5]   5.00-6.00   sec  3.00 MBytes  25.1 Mbits/sec                  
[  5]   6.00-7.00   sec  2.96 MBytes  24.8 Mbits/sec                  
[  5]   7.00-8.00   sec  2.81 MBytes  23.5 Mbits/sec                  
[  5]   8.00-9.00   sec  2.81 MBytes  23.6 Mbits/sec                  
[  5]   9.00-10.00  sec  2.26 MBytes  19.0 Mbits/sec                  
[  5]  10.00-10.09  sec   224 KBytes  21.5 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.09  sec  27.8 MBytes  23.1 Mbits/sec                  receiver

 

root@Unraid:~# iperf3 -c 10.253.0.2
Connecting to host 10.253.0.2, port 5201
[  5] local 10.253.0.1 port 54162 connected to 10.253.0.2 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  3.91 MBytes  32.8 Mbits/sec    0    337 KBytes       
[  5]   1.00-2.00   sec  2.64 MBytes  22.1 Mbits/sec    0    350 KBytes       
[  5]   2.00-3.00   sec  2.76 MBytes  23.1 Mbits/sec    0    337 KBytes       
[  5]   3.00-4.00   sec  3.13 MBytes  26.2 Mbits/sec    0    369 KBytes       
[  5]   4.00-5.00   sec  3.19 MBytes  26.7 Mbits/sec    0    326 KBytes       
[  5]   5.00-6.00   sec  3.19 MBytes  26.7 Mbits/sec    0    315 KBytes       
[  5]   6.00-7.00   sec  2.39 MBytes  20.1 Mbits/sec    0    310 KBytes       
[  5]   7.00-8.00   sec  3.19 MBytes  26.8 Mbits/sec    0    313 KBytes       
[  5]   8.00-9.00   sec  2.39 MBytes  20.1 Mbits/sec    0    297 KBytes       
[  5]   9.00-10.00  sec  2.39 MBytes  20.1 Mbits/sec    0    307 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  29.2 MBytes  24.5 Mbits/sec    0             sender
[  5]   0.00-10.09  sec  27.8 MBytes  23.1 Mbits/sec                  receiver

 

 

rsync with 1Go "testfile" over Wireguard VPN at 3Mbits.... (I tested all possible options for rsync and SSH without improvement)...
 

root@Unraid:~# rsync -az --progress testfile 10.253.0.2:/mnt/cache([email protected])
testfile
     50,987,008   4%    3.04MB/s    0:05:20  

 

 

So, what other solution do you use to backup to another remote Unraid server?

Mbits/sec does not equal MB/s...

1MB is 8Mbs (8 bits to a byte)

 

Therefore your rsync transfer speed was 24.32 Mbits/s (pretty much spot on your iperf3 test)

 

Mbits/s is often also written as Mb/s. The uppercase vs lowercase B is an important differentiation .

[Execution error Image can not be deleted, in use by other container(s)]

I just experienced this issue with several containers (Nextcloud, Swag, Sonarr, Radarr, Plex, and a few more) and was able to fix it so I thought I would share what I did in case anyone came looking in the future. I was having issues with steps 4-7 causing my server to hang and the GUI to become unresponsive so here's what I tried that ultimately worked for me:

 

1. Try steps 4-7. If they don't work or cause a server hang, comeback and start at 2.
2. Shutdown Unraid (force it if you have to and are comfortable with the risk)
3. Once restarted, stop any running containers (not sure if necessary  but I did it as a precaution)
4. Delete orphaned images via the bottom of the Docker tab in Advanced mode.
5. While still in Advanced mode, force update any containers that were failing to start with the error listed by OP.
6. Disable and re-enable the docker service via Settings > Docker (not sure if required, did this as a shortcut to get containers to auto-start rather than manually starting each).
7. Check your docker tab and attempt to start anything that hasn't auto-started, they should all start as expected.

[Can't stop array (BTRFS operation is running)]

On 10/18/2022 at 3:36 PM, lepis0 said:

I'm backing up data now.

How can I reformat the pool?

 

 

edit. I managed to reformat pool.

 

Thank you JorgeB for help

 Can you share how you managed to reformat the pool if you were unable to stop the array? I'm having the same issue right now and it's looking like a reformat is my only option.