tooviral

Lately have noticed something using my gpus when looking at the gpu plugin. When I hover over the icon its named Xorg The gpus are mapped to my plex docker for transcoding, if I have the A380 set in plex, the transcode video stutters every 5 secs. The A310 works fine when used in Plex. I can't find what is using these gpus. Is there another way to find what process is using them? *edit added diagnostics Thx tower-diagnostics-20260108-1415.zip

works fine by direct ip. Doesn't work when I use a fqdn locally with swag reverse proxy, ie (unraid.fqdn.com)

Im still on 7.1.2 and same happens here...

Had an issue where dashboard was not loading, tracked it down to gpustatistics plugin. Remove and Reinstall got dashboard showing again although it is very sluggish. Other tabs work fine. /boot/config/plugins/gpustat/gpustat.cfg nvidia-smi -q -x -i 0 cd /usr/local/emhttp/plugins/gpustat/ && php ./gpustatus.php

I followed this guide and have the reg radarr sync to the 4k radarr, works well https://trash-guides.info/Radarr/Tips/Sync-2-radarr-sonarr/

So, I ended up moving all files to the array, then deleting the cache pool and setting up a new raidz1 pool. then moved the files back over

Its currently btrfs filesystem.

Been running unraid now for 10+ years, upgraded hard drives as I go. At the moment I am running a single 2TB nvme cache drive on the mobo with 24 drives in main array. Cache drive hosts mostly *arr programs for media, and various other programs such as swag to facilitate the server use. I've got a hold of 4, 2 TB server grade nvmes and have attached them to a u.2 2.5" carrier mounted on to a pcie riser card. My question is do I run all 4 in a raidz1 zfs pool, and how do I go about migrating from the 2TB Nvme? Thx

thx Jorge

Have a cache pool of 4 devices in raid 0 I believe and will be upgrading board and cpu soon. I have a 2tb nvme that id like to replace those 4 drives with. Do I change it to raid 1 and then add the 2tb and let it balance, then remove one by one and rebalance between each pull? Just not sure best way to go about it.

Had a disk report some errors. Parity returned no errors as it scheduled run started just after these errors popped up. I've ran an extended self test and it completed without error. Don't think its cables as this is in a supermicro 24 bay system and hasn't moved Will prob order a replacement soon. HGST_HDN721010ALE604_1DGR5LUZ-20220829-1428.txt

Hello, Tryin to repair the database and not sure how to stop plexmediaserver in the docker img. Tried "service plexmediaserver stop" doesn't work Any ideas?

Its reported as closed still. Noticed another container variable "ADDITIONAL_PORTS" in logs and tried adding the incoming port and still no joy. Latest start logs attached. rtorrent.txt

Ive done that in rtorrent.rc and added the variable -e 'VPN_INCOMING_PORT'='12528' and it still shows a closed in rutorrent and https://portchecker.co/

So I've noticed in the logs this 2020-09-26 08:02:04,415 DEBG 'start-script' stdout output: [info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment It looks like its not setting the port forward. Could this be my problem?

Seems it may have been a fluke as I am now getting the red exclamation mark too. My docker start command is as follows Am I doing something wrong?

didnt make any changes to the files, added user/pass to docker variable and put these files in the openvpn folder

All I did was 1. Set up the port forward on Mullvad. 2. Edited the .torrent.rc file and specified the port like this: network.port_range.set = xxxx-xxxx where xxxx is the port number and set "network.port_random.set = no" and worked

It may take some time for it to show open, took a day or two for me.

its 'STRICT_PORT_FORWARD' for the variable wasnt working and was using this reference instead of the faq you have Always refer to the faq lol

Tring to install on a new machine and getting xml error

So it seems a Hikvision surveillance camera that is on the same network was somehow hijacking the portforwad. Removed from network and the container is now running as it was. Thanks to @CHBMB for troubleshooting with me.

I thought so too, but latest version do it automatically

Yes, was working fine before. Upgraded to 6.4 and noticed shortly thereafter it wasn't working. Had it running on 81 and 444 before. Changed it to its own ip with 80 and 443 and nada. Not sure why the reg nginx works, but not letsencrypt.

port forwarding, like i said its working fine on port 80 with nginx alone