Travisw

I have been using Plex with Plex pass for several months. I pass through a GTX760 using nvidia driver 470.141.03. It worked up until I did the more resent Unraid update and required a reinstall of the drivers due to some issue in the release. This solved the problem and allowed Plex to run again. I also verified the was transcoding using watch nvidia-smi. Everything was good. Today I noticed my CPU was really working so I checked watch nvidia-smi and nothing was working. Using Tautulli I can see Plex is transcoding using (HW) but for some reason its not using my GPU. I shut plex down and checked my container to ensure it still had all the stuff needed for passing the GPU then restarted. Still not working. If anyone has any idea I would appreciate it.

USB Flash Device GUID: 154B-00EE-0700-03320XXXXXX Attached Devices: 7 Good afternoon, I was hoping someone would be able to help me figure out what I did wrong. I am completely new to Unraid so go easy on me. My main goal for this system is to replace my 10Tb QNAP NAS. So far I have 4 10Tb drives installed so I can get 30Tb of storage. Below is what I have done so far. I purchased this license back in November of 2021 and finally made time to get my server up and going. I install the server without issues and click "Redeem Activation Code" Copy and paste the key I recieved in November "XXXXXTF49N" into the box and everything seems to work. I then received in my email containing a Unraid Pro license URL:https://keys.lime-technology.com/unraid/XXXXXXXXXXXXX/Pro.key Back on my newly installed server I navigate to Tools/Registration and paste my pro license URL into the Key file URL window followed by clicking "install key" This is the message I received back. Downloading https://keys.lime-technology.com/unraid/XXXXXX/Pro.key ... ERROR (5). I must have made a mistake somewhere along the line, but it still says i'm unregistered and that my server has been up and running for 6years 1 month 13hours 9 minutes. which is not correct. Model: Custom M/B: ASRock X99 Extreme3 Version - s/n: E80-49016200199 BIOS: American Megatrends Inc. Version P1.40. Dated: 09/04/2014 CPU: Intel® Core™ i7-5820K CPU @ 3.30GHz HVM: Enabled IOMMU: Enabled Cache: 384 KiB, 1536 KiB, 15 MB Memory: 16 GiB Other (max. installable capacity 256 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.15.46-Unraid x86_64 OpenSSL: 1.1.1o Uptime: My Log: ul 25 23:26:15 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:16 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:17 Tower nginx: 2016/07/25 23:26:17 [error] 1459#1459: *17492 open() "/usr/local/emhttp/webGui/images/feedback_'+url_parts[4]+'.jpg" failed (2: No such file or directory) while sending to client, client: 192.168.0.159, server: , request: "GET /webGui/images/feedback_'+url_parts[4]+'.jpg HTTP/1.1", host: "192.168.0.131", referrer: "http://192.168.0.131/webGui/include/Feedback.php?done=Done" Jul 25 23:26:17 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:18 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:19 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:20 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:21 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:22 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:23 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:24 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:25 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:26 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:27 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:28 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:29 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:30 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:31 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:32 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:33 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:34 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:35 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:36 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:37 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:38 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:39 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key Jul 25 23:26:40 Tower emhttpd: error: get_key_info, 560: Invalid argument (22): fread: /boot/config/Pro.key