DjJoakim

It didn't finish, but when i rebooted the server, disk nr 7 came up as "emulated" "Unmountable: Wrong or no file system" again, and then unraid started doing a data-rebuild, so i will se what will happend when the rebuild is done..

Hey! After last upgrade 6.11.3, Plex isn't reachable to network Anyone having the same issues, or know where to start searching for what's wrong?

Sorry, my bad.. From memcheck i get, ** Pass complete, no errors, press Esc to exit **

So, when i try to do a memtest, it says "Loading memtest" - OK and then my server restarts... Dosen't sound so good!

Yeah sorry for my fast reply, a quick google showed me the same.. I will try to do an memtest and get back with the resoults for you. Thanks so much.

How do i run memtest, and is it possible during a parity check? Thanks!

Hello! (First of all, i apologize for my bad english and grammar) So, long story short.. For 2 days ago, i upgraded unraid to 6.11.3, everything seemed to work fine, but when the array starded - i saw that one of my HDD was showing error "Unable to mount to array" or something like that, i saw that alot of people here had have this problem before, so i solved it using on of the guides here, i started the array in maintence mode and did an xfs_repair, using first the flag -v and then the flag -L (it gave me an error and told me to use it..) So, after that - i did a restart and the HDD was added to the array, and everything seemed to work fine! Awesome, well - short happines. Here comes the big problems... when i starded to run my dockers, first of all i saw that Plex didn't start, so i check the logs - currupted "malformed" database... hmhmhm... Soooo, i searched the internet and found a solution for it, i did some "VACUUM" mode in "PLEX SQLite" etc etc... and it gave me an "ok" on the DB file. So, now Plex started - but can't be found anywhere (but that's another problem i won't take here..) So then the problem also came to Sonarr, same here.. curropted database "malformed", i haven't got it working yet since all my backups seems to be corrupted aswell.. (but that's also another problem, i won't take here, since i feel like the problem is bigger and in unraid/array itself) So - last night when i got to bed, i started an pairty check, and now it's at 32% and i have 7005 errors??? WTDH? I haven't had more then 1 errors before, that was gone after doing a new pairty check.. I have searched over the wild internet but i can't find anything in my logs etc to determine what's wrong? Can someone please help me check the diagnostic to see what the hell has happend, is there some disk that's starting to crash? If so, what can i do? Thanks so much for taking you'r time! slave-diagnostics-20221112-1326.zip

Won’t work for me

Did you find à solution for this?

Works like a sharm... Thank you! Yes, i know it won't support h265, and i know it's not an optimal card since it's a bit old, but i had this laying around and i will start using this and then get me another card, maybe a newer quattro card, and i will replace it with that Thank you alot for you´r help! Nice to see it working fine.

Well, i don't know if you misspelled that, but it's a K600 and not K400. They way i found what driver i should have was going to this webpage https://www.nvidia.com/en-us/drivers/unix/ and then under Latest Legacy GPU version (390.xx series): 390.147, i found my Quadro K600 was supported, but it's not under the 2 first ones. Thanks!

Hey! I have a Quadro K600 in my unraid and i would like to use this plugin for it, but i found out that it's only supported under 390.147 version, and i can't find that in the list.. Is my card not compatible or is there some solution for it? As for now - it dosen't show up under nvidia driver page. Thanks!

Hey! Waking up an old thread here, but i have tried to get my UPS to work for days now... i have the same UPS you have, with the same problem - when i try use NUT plugin, it just won't start.. How did you get it working? Thanks

Is it possible to get the previous version of nginx? Mine stopped working after the last update.. and i can't get it to work again.. edit: So i found a solution on my problem, since the last update, at the botton there is a new port called "API" port, 3000. That wasn't there before, so if anyone else gets the same problem as i had, remove that port using advanced view, and then add the port in VPN docker, and it should work. Mine is working now again!

Yeah no other docker uses this ports.. i have the ports lined up in the vpn docker since it's "running through" the docker, and then i remove the ports from the nginx docker, but since the update today i get this error message.. When using the command "--net=container:openvpnpublic" it works, but if i change it to "custom container:openvpnpublic" network, i get this error message..

Hello, this docker has been working fine for the last months, but since i updated it today it has now crashed, and i get this message when trying to create it again.. Error response from daemon: conflicting options: port publishing and the container type network mode I am running it through a VPN Docker, and this has been working fine before, but from today it won't anymore.. There are no ports in the config, they are in the VPN docker, as they should. Please help

Thanks! I will look into that, do you know how to install two instances?

Hey! I have a setup that looks like this; VPN Docker 1 Docker 1 (runs under vpn docker 1) Docker 2 (runs under vpn docker 1) VPN Docker 2 Docker 3 (runs under vpn docker 2) Docker 4 (runs under vpn docker 2) When my network disconnect, vpn dockers activates their killswitch, witch is good - but bad for me.. bc then i have to manually restart every docker including the vpn dockers.. Is there someway to make a script that maybe detects when network is lost and shuts down the dockers, and then when network is up and running again, starts both vpn dockers at the same time, and 30 sec later starts the other dockers (so the vpn is connected) I was checking if there was something that could be done by using this script, but i can't really get the detection part figured out... since this activates when unraid is restarted. Thanks!

Hello, i have a problem using this docker. I use stable-torless-amd64 on unraid 6.8.3 but the problem is, after some time running it, the docker crashes, and it's never the same time, sometime it last 24h, sometime 6h, sometime 2 days... but after it crashes i always have this in my log. [info] Setting up OpenVPN tunnel [info] Create tunnel device [info] Allow DnS-over-TLS for openvpn to lookup VPN server [info] Connecting to VPN on port 1194 with proto udp... [info] Connection in progress, wait 10s... [info] Your VPN public IP is (my vpn ip) [info] Block DnS-over-TLS to force traffic through tunnel [info] Change DNS servers to 127.2.2.2 [info] Adding 127.2.2.2 to /etc/resolv.conf [info] Allowing DNS lookups (tcp, udp port 53) to server '127.2.2.2' [info] Done [info] Run danted in background on port 9118 [info] Run tinyproxy in background with no log on port 8118 WARNING: logging deactivated (can't log to stdout when daemonized) [info] Torless build detected. Skip running torsocks + privoxy configs. [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) [info] Your VPN public IP is (my vpn ip) Also, when the docker is running, it says like this in Unraid "Uptime 13 hours (unhealthy) Help..