giveitago

Looks like you are getting consistent 10g in both directions on the network. However this is different from OP. Are you still getting different speeds when you run it as you did originally?

On the PC run the following iperf commands which runs the test for 60 secs and link to the results on pastebin. iperf3 -c <server IP> -P 4 -O 3 -t 60 > iperf_results_client_send.txt iperf3 -c <server IP> -P 4 -O 3 -t 60 -R > iperf_results_server_send.txt Might show up something

Wonder if others are using Wireguard and can connect to Docker containers hosted on UnRaid where they have unique IP addresses? Can you show me you Wireguard config to see where I'm going wrong? Thanks

I've got UnRaid 6.11.5 installed and been working well for many months. For most Docker containers I set network type to "Custom: br0" and I set a fixed unique IP address for each container. I can ping the containers IP address and connect to the applications in the containers from any devices in the local LAN (192.168.88.X) Recently, I set up Wireguard in UnRaid (Settings -> VPN Manager) to connect to an external hub. From a Wireguard client I can ping & connect to UnRaid host (192.168.88.230) and any other IP address in the local subnet (192.168.88.X) except any IP address assign to a Docker container on UnRaid. How can I connect to Docker container from a Wireguard device? Thanks

The first log lines where docker is creating and bringing down network interfaces in quick succession looks like a badly configured docker instance to me with auto-start. In those logs I would interpret avahi-daemon is normally responding to the creation of removal of network interfaces. If you want to diagnose I would disable autostart on all your docker containers, reboot the box, then go through one at a time and start a container and monitor logs for 3 - 4 mins. Then you can see which is the dodgy docker container

Thanks @Arbadacarba @MAM59 I will try that out

On my unraid box netdata detected occasional FIFO errors with my I350 network card - https://community.netdata.cloud/t/10min-fifo-errors/1814 I increased the RX buffer through the Terminal screen and it has been running with no errors for a number of days... until I rebooted today and the error came back again! How can I persist the change so the command is run on startup? The command is: ethtool -G eth0 rx 4096

Today I did a memory upgrade on my Unraid box and couldn't run the Memtest program on the boot menu. It hung at the point of stating "Loading /memtest". From the Memtest website I downloaded the latest binaries - https://www.memtest.org/download/v6.10/mt86plus_6.10.binaries.zip I extracted memtest64.efi file and put in the /boot directory of the Unraid USB stick. I then modified /boot/syslinux/syslinux.cfg and added the following lines: label Memtest86+ (UEFI) kernel /memtest64.efi On reboot, the UEFI version ran successfully. I guess it was because the BIOS is UEFI the original did not work. My recommendation would be to keep the old and add a UEFI one. It only adds 145kB to the USB drive.

Marvellous! Many thanks both! The Docker image files were not moving even though the Containers were stopped. I realised I had to disable the Docker and VM in the Settings first then tried Mover again. All transferred to the NVMe pool now.

Hi, I have one HDD drive and one NVMe drive. I've gone through the manual and searched previous posts however I'm still a bit confused how to store docker images and containers data on an NVMe drive. From what I read the recommendation is not to add NVMe drive to array but to create a pool for the NVMe drive. On creating Unraid I've created a array device with single 8TB HDD. I've then loaded a couple of experimental Docker instances. This has created appdata, domains, isos and system shares on the 8TB HDD. I've now created a pool using single NVMe drive. However, when i click on any of the above shares, I thought I would see the pool drive in the "Included disks" but it only shows HDD. I'm not looking to use the NVMe as a cache drive. I want to use it as a permanent drive for Docker et al. What is the right way to host Docker and related files on the NVMe? Thanks