clevoir

Thanks for the reply, I've got some new 8TB hard drives being delivered today I'll swap them out with failed ones, then do some testing on the old ones. ,

Please find attached diagnostics tower-diagnostics-20260509-1148.zip

The array won't let me run any self-tests, if I click on either sefl-test nothing happens?

I've bitten the bullet and bought 2 8TB new hard drives as I could do with some more capacity I see that the hard drives failed after a power failure, I've seen this before and then bought a UPS with AVR, so disappointed a power failure has caused drives to fail?

I have woke this morning and have found that 2 disks have failed in my array, Disk7 and 8 I'm running 7.2.4, what is my best course of action? Where 1 disk has failed before, I've restarted the array with out it, rebuilt the array, then added it back in and then rebuilt array again. I guess I could do this one disk at a time but I am worried as I I'll have no parity protection See attached syslog tower-syslog-20260509-0831.zip

With the latest image I can now connect to AirVPN using OpenVPN and download at normal speeds again. Thank you!

I spoke too soon I can search in Sonarr / Radarr and download, but speeds are terrible, I am using AirVPN and can only download at 800kbs at most? I've tried other locations but all have the same effect'?

I found out that my issues were down to Privoxy, I have set PRIVOXY to no and have set all containers not to use Privoxy too. Now I can download using SabNZBVPN OK and Sonarr / Radarr / Lidarr can all search too. If I turn PIVOXY on again, Sonarr / Radarr / Lidarr can't search for files?

Please can someone help with my query

I can establish a VPN connection using AirVPN, but Sabnzbvpn can't connect to any usenet servers? I have set NAMES SERVERS to 8.8.8.8 and 1.1.1.1 Sonaar & Radarr can't download search items either. I am seeing this in the log file INFO::[_cplogging:213] [12/Oct/2025:11:57:36] ENGINE Client ('127.0.0.1', 34844) lost — peer dropped the TLS connection suddenly, during handshake: (8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1032)') I've tried 4 different VPN servers with the same effect Please see attached files, I have read the Q&A's but can't see any that can help me. If I turn off the VPN connection, sabnzbvpn works OK I'd be grateful for some assistance sabnzbd.txt supervisord.txt AirVPN_Netherlands_TCP-443-Entry3.ovpn

I am new user to Jellyfin, I have set up the server app and installed media player in a client PC. I am finding both the server app and the media player very slow to populate the main page, sometimes taking 5 mins. I have also seen CPU usage spike to 100% whilst this happens. This is after the media libraries have been 100% populated. Is this related to lack to server resources, I am running Intel® Xeon® CPU E3-1230 V2 @ 3.30GHz and 16GB RAM? However I am able to view most of my media inc 4K films without transcoding.

If I disable the VPN connection, I can access SABnzbVPN again?

I can't access SABnzbVPN, but it works fine in Lidarr? I get this when I try and test Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [503:ServiceUnavailable] [GET] at [http://192.168.1.10:8080/api?mode=get_config&apikey=d13a732039250f1d334faa02338c95ed&output=json] I get the same result in Radarr too?

Thank you, I have now deleted these 2 duplicate files from my cache drive I'll monitor how I get on.

Please find attached diagnostics Shares - Donwloads, FLAC Music and Hi Def should be moved tower-diagnostics-20250212-1751.zip

I have deleted the mover plugin and enabled mover logging. However I can't start the mover, if I press "Move Now" I don't receive the normal message that the mover is running & files don't not move from my cache drive After a deleted the plugin I have not yet rebooted the server, would this be a good idea?

I have just tried that and it had no effect.

I am running Unraid 7.0 and today I have found that the mover has stopped working. It's configured to run every hour, but instead my Cache disk is filling up. I've tried to manually start it, but after clicking start I don't any notification that it is running Please find attached diagnostic file tower-diagnostics-20250211-1536.zip

I have now rebuilt parity, the progress page worked correctly and kept updating until the end. I am also able to stop the array OK and restart it. I'm concerned that it did not try to unmount disks last time though. Please find attached latest diagnostics tower-diagnostics-20230804-1029.zip

I have shut down the array and replaced disk 12, I am now waiting for parity to rebuild However when shutting down, I set the shutdown timer to 420 seconds as recommended in another post, an unclean shutdown was detected? It noted that a driver couldn't be stopped, the text on an attached monitor was moving too fast for me to take note of which driver Please find attached diagnostics file that the the array took on shutdown, I thought 6.12.3 was supposed to have fixed this issue? tower-diagnostics-20230803-1628.zip

I am running 6.12.3 and a parity check was run today. It appears that this has been completed as there are no disk activity or disk reads going on However the array reports that the parity check is still in progress, but these figures have been frozen for hours and do not update if you refresh the page? Please find attached diagnostics - I know that Disk 12 has failed tower-diagnostics-20230801-1759.zip

I have just updated to 6.12.3, so far without problems Had to stop dockers using umount /var/lib/docker, but all dockers have come back up and working OK

I anm running 6.12.2 and I am getting the following fault on the log file, and Sonaar just hangs at one series Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. See attached log file, Big Bang Theory seems to be problem 2023_07_10 Sonaar Log.txt

Because of the problems that I have been experiencing I thought I'd revert back to 6.11.5. So copied all the BZ files and Changes log to the flash drive, where I previously had 6.12.0 installed Immediately lost access to the server and had to do a hard reboot. 6.11.5 boots up with unclean shutdown detected and kicks off the parity check (great!), but I can't start any dockers with "Server Error" being reported I then restored 6.12.0 back to the flash drive and reboot, boots OK but unclean shutdown detected again. So decide to update to 6.12.2, this reboots OK without unclean shutdown detected and all dockers start OK Not sure what to do now, I guess stick on 6.12.2 and see what happens?

I have seen this behavior too since upgrading to 6.12.0, it was never an issue using 6.11.5 I haven't found the reason and am sorely tempted to go back to 6.11.5. Because as this issue am rebooting the server instead of stopping it, but this causes problems with unclean shutdowns. Again this was never a problem before 6.12.0