worldspawn

Having the same issue since last night, Plex crashed during a library scan, followed the same basic steps, ran DBRepair, wiped the Preferences.xml and perms.txt files after errors showed up that indicated these files may be corrupted, uninstalled and nuked the appdata directory, reinstalled, still stuck with "A problem has been detected with a core component of Plex Media Server." Logs have not been particularly useful. Not running CA backup, and currently have approximately 278GB of free ram (yes, that's gigabytes). 2025-08-03 08:50:18.246750 [info] Host is running unRAID 2025-08-03 08:50:18.314530 [info] System information: Linux servname 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux 2025-08-03 08:50:18.380519 [info] Image tags: BASE_RELEASE_TAG=2025071502,IMAGE_RELEASE_TAG=1.42.0.9975-1-01 2025-08-03 08:50:18.455477 [info] PUID defined as '99' 2025-08-03 08:50:18.535544 [info] PGID defined as '100' 2025-08-03 08:50:18.621301 [info] UMASK defined as '000' 2025-08-03 08:50:18.696313 [info] Permissions already set for '/config' 2025-08-03 08:50:18.774209 [info] Deleting files in /tmp (non recursive)... 2025-08-03 08:50:18.855319 [info] TRANS_DIR defined as '/tmp/PlexRamScratch' 2025-08-03 08:50:18.936674 [info] Starting Supervisor... 2025-08-03 08:50:19,402 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2025-08-03 08:50:19,403 INFO Set uid to user 0 succeeded 2025-08-03 08:50:19,418 INFO RPC interface 'supervisor' initialized 2025-08-03 08:50:19,418 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2025-08-03 08:50:19,419 INFO supervisord started with pid 19 2025-08-03 08:50:20,424 INFO spawned: 'plexmediaserver' with pid 71 2025-08-03 08:50:20,425 INFO reaped unknown pid 20 (exit status 0) 2025-08-03 08:50:21,427 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-08-03 08:50:34,246 DEBG 'plexmediaserver' stdout output: Critical: libusb_init failed Logs.zip

I have a Lenovo SA120 enclosure which I had been controlling the fans on using the sg3_utils that was part of the Nerdpack plugin, it's not present in the nerdtools now that nerdpack has been removed with the update. I can see that sg_ses is present on my system, I've also tried downloading and installing the most recent version of sg3_utils manually, but I still can't get the system to recognize the 'python fancontrol.py 1' command (no such file or directory error). How do I get my fan control back? This box is incredibly loud without that control script I was running in unraid 6.11.

Yeah, seeing the exact same numbers for container/writable size, it's 2x as big as any other docker I have running. Seems way too big for a docker that shouldn't be storing any large data (media or large files). You might want to check your log settings, 340MB worth of logs is a TON of logs, lol. Mine is <30MB

Having just had a USB drive be corrupted on reboot (safe shutdown, don't know what the issue was), the lack of capacity for a redundant boot is very frustrating. For a system built on redundancy, depending on the integrity of a single flash media device seems like a pretty big oversight. Particularly since it's quite a hassle to set up and register a new device. It's easier to swap a failed hard drive or motherboard than it is to swap a thumb drive, and that's not right.

Hey, that's it. Been looking for that command for a month+ . Size updated as soon as the command was run. Attached diagnostics are after reboot. diagnostics-20230104-1939.zip

clear is complete, updated diagnostic attached diagnostics-20230104-1142.zip

That's because that drive is mid-clear, it's 18TB, so it takes over a day. The Cache drives are sdb and sdc, sdd is not involved.

Diagnostics file attached. Thanks. diagnostics-20230104-0824.zip

I have a pair of 800GB SSD drives installed for my cache, the system is reading the pool size as 650GB, and the used/free capacity only adds up to 500GB, how do I get Unraid to use the full 800GB?

The card is working NOW, as in, it is outputting video and displaying the console, just not being detected correctly in Nvidia-driver. Regarding the Above 4G decoding and Resizable BAR support, I'm not sure where those are, but the previous card Quadro P4000 was operating without any issue before the update. It's not a riser cable, Servers use risers for rotating the cards 90 deg so they fit into the case, it's an HP factory riser, and riser is known good, and was working before the server update.

Just upgraded my server to 6.11 and I can't get my card to show up. Followed the instructions provided to 'fix' the updated drivers, no change. Removed and reinstalled the entire plugin, no change. The card shows up in System Devices, but not in Nvidia-Driver. Screenshots from Nvidia-Driver and System Devices, along with diagnostics attached here. Quadro RTX 4000 in an HP DL380 Gen7 with dual Xeon L5630, 144GB DDR3 ECC RAM, using an x16 riser for the card. diagnostics-20221011-1500.zip

I installed the docker just now, but when I open the webUI, it's just a blank page that says 'Netdata, realtime monitoring done right' in the background. Is there something I'm missing here?

Thanks for the help and insight, FYI, after I got the web interface going, my downloads weren't connecting, turning off the proxy in the deluge preferences fixed that though. Proxy should be redundant anyway going through VPN, right?

Hey! That was it, when did that change? The last several versions I've used required the generated password set.

Yeah, been through that document already, if it were something that simple, I wouldn't be posting here. Your subscription has run out - double check this on the vpn providers website. -nope, logged into the site today, I have over a year left You have not typed in your username and/or password - do not copy and paste, type it in manually to prevent whitespace issues. -nope, copy/pasted, manually entered, regenerated credentials, and retried several times, this is not the issue You are using the wrong credentials - ensure the credentials are for openvpn/wireguard, NOT proxy servers etc. -this is the only 'maybe' here, I can't tell if PIA uses different credentials for wireguard, and if so, I can't find them, but I was getting the error for openvpn as well as wireguard, so either way this isn't the issue for at least one of my attempts and both are having the same issue. Your password contains a character which may cause issues - please ensure it only contains letters a-z (upper case or lower case) and numbers 0-9. -nope, using credentials generated by PIA, no unusual characters Out of date openvpn config file (ovpn extension) - ensure you download the latest ovpn file from your vpn provider. -nope, fresh download, files are dated 8-11-20, from the next-gen zip file The vpn provider you have signed up with is having authentication issues - try another endpoint, failing that contact the vpn provider and explain you are having authenticaiton issues when using native openvpn/wireguard clients with AUTH_FAILED shown. -maybe, but I'd expect a company as big as PIA to have that somewhere public if their connections have been down for days... Tried about 5 different endpoints, all give the same issue.