exdox77

OMG you are a godsend!!! I was panicking for a minute!!!!!

I accidentally selected the wrong preserve settings and lost my array config. I did not back up manually since I am connected to Unraid Connect. Is there a way to go back in Connect to get a config from a previous day? Is there a way to restore the previous settings for the array? I have an image of the array prior to this happening, but it says all data will be lost if the array is started.

Thank you everyone for your support. I purchased new memory yesterday, went with Corsair with the same advertised specs. Ensure the MB was configured correctly and did one last memtest last night. Everything passed with flying colors and Unraid seems to be running great.

No OC on this board. It runs stock config. Memory test failed out because of too many errors.

No OC settings have ever been enabled. The system has been running for years without issues with no changes to the BIOS. The memtest failed out because of too many errors. Running memtest on the new memory now.

@trurl initial results do not look good. Looks like I will be ordering some memory.

I have not. If the USB drive is failing, could this cause these issues?

Yesterday I spent most of the recovering from my cache drive filesystem becoming read only. I recovered and created a new pool with another brand new drive. Moved everything over and everything was working fine. This morning I woke up to the filesystem in the brand drive read only. I am at a loss to why this keeps happening, this is the third time this past couple of months this has happened. I have attached the diagnostics. I do want to mentioned that if I reboot Unraid and restart the array, things work fine for awhile. hive-diagnostics-20221202-0713.zip

I figured it out, it was a config in one of the plugins that I needed to tell it to use the GPU. Working pretty well now.

Everything seems to look correct from configuration, unless I am missing something. Extra Parameters = --runtime=nvidia Variable NVIDIA_VISIBLE_DEVICES = GPU UUID Variable NVIDIA_DRIVER_CAPABILITIES = all Also note that Tdar is currently transcoding with the GPU selected and there is no GPU activity using nvidia-smi.

I have noticed recently that GPU transcoding isn't work in Plex. I also tried GPU transcoding in Tdarr and Tdarr was using a lot of CPU. I have been using GPU on Plex for months now with no issues. I am on Unraid 6.9.2 with Nvidia driver 460.80. I am not sure when GPU transcoding stopped working. I tried removed the variables from the template and adding them. I tried rebooting Unraid and downloading new versions. I cannot seem to get Plex or any container to use GPU.

I am migrating from docker compose to unraid and I had originally had command line arguments in my docker compose file and I am not sure how to get those into an unraid image. This is an example: command: # CLI arguments - --global.checkNewVersion=true - --global.sendAnonymousUsage=true - --entryPoints.http.address=:80 - --entryPoints.https.address=:443 command: # CLI arguments - --global.checkNewVersion=true - --global.sendAnonymousUsage=true - --entryPoints.http.address=:80 - --entryPoints.https.address=:443

Thanks for the info, wish I would have saw this earlier lol.

Changed Status to Open Changed Priority to Other

Not sure if anyone else is having this issue but my 4th core has been 100% since reboot.

Nope, others kept telling me to add a route on the host but couldn't figure out how to do it and no one really wanted to help. Then work got a little busy. I moved it to the docker network again but the unifi devices didn't like that it couldn't see the controller so i moved it back to the main network. So not sure what is up.

Interesting, I have my netdata container on the t2_proxy using Traefik routes and it works just fine. I think i am going to try to move the container back to t2_proxy and reconfigure traefik.

I originally had it on t2_proxy and then all my unifi devices lost access to the controller. So i moved it back to br0 and the devices connected again. Very strange behavior. I recently moved it back thinking that now I was done reconfiguring everything that it would be fine in t2_proxy. But l traefik still couldn't connect, but gave a 404 error this time and with no log data.

this is weird. i access the containers shell and ping a few ip's on br0 and they come back just fine. go to ping the ip configured for the unifi container and all packets are lost. no matter if i change the ip to different ip or not.

yes and traefik chokes and doesnt start back up. I have to disconnect the network from traefik for it work again. I maybe remove all these network i dont use anymore since i moved everything into docker. Ideally i would have 192.168.0.0/16 and then the docker networks and that would be it.

The problem container is traefik, which is connected to t2_proxy network with all the other containers, except for unifi. The unifi container needs to be on the main network br0. From what I can tell from the logs, traefik is trying to route requests to my unifi container but there are no routes.

I have been toying around with Docker and Docker Compose lately and I finally got Traefik setup to reverse proxy all my containers to their own docker network. However, I have one container I was not able to put into the docker container network and sits outside of the docker network. It looks like I can still use Traefik to forward traffic to this container but when the request comes in the traefik container logs state "no route to host". I assume this is because the internal docker networks do not see other networks and are isolated. My questions is, how do it expose the docker networks to other non-docker networks?

Update. After digging through the logs and trying to make sense of it, it concluded that it may just need a reboot. I did a reboot of the server and it allowed me to format the drive and now I can use.

Thanks for the help, still learning the ways. tower-diagnostics-20200214-1934.zip