maximushugus

Still no news for an official fix (on future release) ?

The command above is in two lines. You have to stop docker before modifying the file et restart after

I upgraded yesterday from unraid 6.11.5 to 6.12.4 (so I cannot say from when 6.12 version this problem starts), and I'm also impacted by this bug. I managed to fix it by : 1) Stopping docker service 2) Modifying /usr/locale/etc/rc.d/rc.docker file : at line 350 from : IPV6=$(min6 $(max6 $(wipe $(ip -br -6 addr show $NETWORK scope global|awk '{$2="";print;exit}'))|sort|head -1)) to IPV6=$(ip -6 addr show $NETWORK mngtmpaddr|awk '/^ +inet6 /{print $2;exit}') [[ -z $IPV6 ]] && IPV6=$(ip -6 addr show $NETWORK scope global permanent|awk '/^ +inet6 /{print $2;exit}' 3) Restarting the docker service But I hope there will be a fix from unraid in future version !

Hello ! I updated from unraid 6.11.5 to 6.12.4 today My server is running with a bridge interface (of 2 SFP port). I'm using macvlan for my docker with IPV4 and IPV6. After upgading, I cannot use IPV6 for my containers. I have the same issue as here, for my custom br0 network : If I choose another custom bridge network (for example br0.50 on a VLAN), I can assign IPV6. As said here, for my docker network for my bridge, "EnableIPV6" is set to false : I tried to apply this patch at the end of this conversation but it doesn't resolve my problem : Does someone know what is happening ? Thanks unraid-diagnostics-20230913-1831.zip

I was also able to make plex running again by restoring a save of the plex folder in appdata from a week ago I made with duplicati. No way of repairing without doing a restoration.

I'm facing the same problem after a reboot of unraid without error. I tried reparing DB but no error No error on log files I tried reinstalling the docker container Without success. I cannot access the webUI for http://localIP:32400/web If someone has a solution it would be awesome

I'm getting an nvme SSD in cache for system and appdata shares. Do you believe I should use btrfs for my main array of SATA SSD ? As far as I know, btrfs has build in support for trim. Is unraid compatible with this ?

Do you have an idea why have this IOWait problem only recently (since a few days) ? Because of performance degradation ?

Thanks for your answer. What is weired is that I didn't have this problem before. The IOWait completely locks docker. Trim (with the plugin) isn't supported on the array ?

Hello everyone, I'm writing here because I have a problem I'm not able to solve alone. First here is my Unraid server configuration : - CPU : Intel 8400T - 16 GB of RAM - Array composed of 2 SATA SSD (with 1 of those 2 drive being the parity drive) Because I only have SSD in my server, I don't have a cache drive. - 20 docker container, a lot of them have dedicated IPv4 and IPv6 on custom interface (not host not bridge to be accessible directly on my network). Docker is configured with a docker.img in BTRFS. - 2 VM : my pfSense firewall with PCIe passthrough for my NIC, and my HomeAssistant VM Description of the problem : Since a few days, I found my Unraid server very unresponsive. A lot of time, I cannot access my dockers (Plex, Nextcloud etc) web interfaces. I also cannot access Unraid Docker tab (or with a lot of pain), and every docker command (docker container stop for example) is painfully slow (in minutes) On the other hand, my VM were working as expected, with normal speed. So I tried to search what caused this behavior. Searching the cause of the problem : First I found that the load average (with htop) was very high, above 20. But CPU utilization with HTOP was low (5-10%). So I suspected IOWait. By running iotop I can see multiple command using a lot of IO : "unraidd1", "docker ..." etc. The IOWait was also confirmed by Netdata (here is an example but IOWait can go above 90%) : So first I tried to see if this high IOWait was because of a particular docker container. But even shutting down all container, the IOWait keeps being high for a few minutes before coming back to normal value (<3%), so it looks as it was not because of a container but with docker itself. When IOWait come back to low value, the docker tab/docker commands become responsive again. I also saw in Netdata that during high IOWait, the disk usage was at 100% on the parity drive but not on other drive. A temporary solution : So after a lot of searching I tried to disable parity (by stoping array and removing parity disk) in Unraid, and I do not have the high IOWait problem anymore. I need help : Does someone have an explanation and a solution for this problem ? I didn't have this problem a few weeks ago... IOWait is so high that I'm not able to sync parity again : if docker is enabled and my containers started, the problem happens immediately and parity sync is painfully slow : about 2MB/s on SSD, and every docker is not responsive ... Do you think this is a hardware failure ? I changed a few months ago the parity SSD Drive, so it's almost new. You can find my Unraid diagnostic below. Thanks a lot

Thanks fo the very precise answer. If I manage to make SSL preread to work I'll do a follow up here

Hello and thanks for the container. I have a question I'm not able to answer. Actually I have my NPM container working as expected with multiple proxy hosts. NPM is listening on port 443 et 80 (redirected from my router) I'm trying to configure a stream to my OpenVPN server (on TCP port 1194) : if I configure the stream on NPM with forward host as my openvpn server, with forward port 1194 and with incoming port different than 443 or 80, it works. But as soon as I put 443 as incoming port it doesn't work anymore. I want to do this because I need my OpenVPN server to be on TCP 443 from an external of my network point of view to bypass firewall where I use my VPN. Is there a solution for this ? Is it possible ? Many thanks

Maybe this question should be moved to the hardware section ?

Hello everyone, I'm new to unraid so sorry if my questions seem stupid. I recently build an unraid server. I plan to virtualize Pfsense on this server. To do this I want to buy a network card. As I'm eligible to multigigabit internet throught FTTH and as I have an SSD array, I want to buy a 10 Gb/s card. I already have a 10G switch with RJ45 and SFP+. So I would like to buy the Silicom PE310G4SPI9L wich is a 4 SFP+ 10Gb/s NIC. I can see it's based on 2 X Intel 82599ES, wich seem to have linux driver So here are my questions : Can someone confirm this card would be compatible with unraid ? Do you know if this is plug and play or how am I supposed to install those driver ? Trhough CLI ? As this card is based on 2 Intel 82599ES, does someone know if I can passthrought only some of the SFP+ ports to a VM ? I would like to pass 2 ports to my Pfsense VM and keep the 2 other SFP+ ports for Unraid, using IOMMU. Thanks a lot fot your answer