Moose_Flunky

Sorry. I was able to get the driver installed. For some reason, it appears that the download would time out while pulling the latest Nvidia driver. I was able to follow the download and it eventually pulled and installed correctly. Again, sorry to have bothered you and thank you for the support

Greetings. I'm having problems with the Nvidia-Driver plugin. I initially uninstalled it because I was having erratic behavior on my Tesla P4, with the intent to reinstall to see if it fixed the problem. However, now I cannot reinstall the plugin. I get the following failure: --------------Can't download Nvidia Driver Package v580.82.09----------------- Removing package: nvidia-driver-2026.01.16 plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installedI'm currently running Unraid 7.1.4, and just replaced my Boot USB thinking that might be the problem. Any ideas?

Could you please tell me where that is shown in either the diagnostics or the SMART results? I'd really like to know what to look for going forward.

I recently added the (refurbed) 10 TB drive in question to replace a smaller 4 TB drive. I'm starting to get errors, but I'm not knowledgeable enough to understand the smart report. The extended smart test aborts after roughly 10% saying Read:Failure, but the drive is still be shown as Healthy I've attached the last Extended Smart Test as well as the general system diagnostics (the drive in question is sdh). I believe that I have already changed the SAS cable for this bank of drives. flunkyland-smart-20251010-1222 (1).zip flunkyland-diagnostics-20251010-1240.zip

Thank you for that bit of information. That really helped. This morning I was able to put drive 20 in another slot and another open SATA port on the board and test it. In both cases it appears to be dead. So, I plugged a new drive into drive 20's slot, selected the new drive ID for drive 20, and Unraid immediately began rebuilding the drive. However, parity2 started throwing errors immediately, so as soon as drive 20 finishes rebuilding, I'm going to replace parity2. Thank you for all of your assistance. After everything is rebuilt, I post a final diagnostic to close the loop

A cable swap is not easy since this is a 4U chasis with a SATA backplane. All the drives are hot swap and all slots are currently in use. I don't know how I can move the drive without displacing another drive (which would corrupt the parity, correct?)

I shut down, checked the cables and reseated the failed drive 20. After I restarted, drive 20 now says Unassigned and the existing hard drive in that slot does not show as an option. New diagnostics here. flunkyland-diagnostics-20250408-1806.zip

Can you tell me how you can determine how Parity2 is failing? Is it in the SMART, or part of the larger diagnostics? I'll shut down a bit later and see if I can get disc 20 back on line. If I can, then I'll replace the parity drive (how?}

I just received this message this morning. In addition, I have a parity drive throwing read errors, but apparently not critical (yet). I did try changing the cables to the parity drives, with some spotty results. I've got 4 new (to me) 10 TB hard drives precleared and tested ready to drop in. But, I'm not certain what my steps should be. flunkyland-diagnostics-20250407-1227.zip flunkyland-smart-20250407-1226.zip

Once you switched it back to binhex/arch-sonarr in the repository, did you force an update? That was step 2 in Binhex's instructions. Try that and see if it pulls down a clean install. Other than that, I put you back in the gentle hands of Binhex.

Number 1 fixed the issue. My repository had "binhex/arch-sonarr:v3". Removing the :v3 let it update and it now is working again. Thank you!

Could this be related in some fashion to those of us still on Unraid 6.11 and not having the new Community Applications plugin? I ask because my Sonarr still shows as latest on the docker tab, even though it seems to be an older version than you just posted.

The information I posted was directly from the System Tab in Sonarr

Not using Cloudflare. Okay. Simply going to "Series", "Add New". Type Black Sails (or anything, actually) in the search box and the error pops up immediately. It's even been failing on the first letter "B". Failed to load search results, please try again. Search for 'B' failed. Invalid response received from SkyHook. I couldn't find a Force Update option anywhere on the page. My Unraid shows that the docker is up to date. Version 3.0.4.1126 Package Version 3.0.4.1126-1 by sonarr-phantom Mono Version 6.12.0

Here's what my log file is showing for this. It is the first thing on top of my log and pertains to the mono error. [v3.0.4.1126] System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.): 'https://skyhook.sonarr.tv/v1/tvdb/shows/en/420659' ---> System.Net.WebException: Error: TrustFailure (Authentication failed, see inner exception.) ---> System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> Mono.Btls.MonoBtlsException: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED at /build/mono/src/mono/external/boringssl/ssl/handshake_client.c:1132 at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x00057] in /build/mono/src/mono/mcs/class/System/Mono.Btls/MonoBtlsContext.cs:226 at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncOperationStatus status, System.Boolean renegotiate) [0x000da] in /build/mono/src/mono/mcs/class/System/Mono.Net.Security/MobileAuthenticatedStream.cs:715 at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake(Mono.Net.Security.AsyncOperationStatus,bool) at Mono.Net.Security.AsyncHandshakeRequest.Run (Mono.Net.Security.AsyncOperationStatus status) [0x00000] in /build/mono/src/mono/mcs/class/System/Mono.Net.Security/AsyncProtocolRequest.cs:289 at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (System.Threading.CancellationToken cancellationToken) [0x000fc] in /build/mono/src/mono/mcs/class/System/Mono.Net.Security/AsyncProtocolRequest.cs:223