gooner_47

Thank you, I will do that. Should I stop the parity check that is currently running, or let it complete? Also can I replace disk 3 with a larger capacity disk, or should it match the 6TB that it is currently?

Hi, I've been away from home for 6 weeks, things were fine before I left - the array was up, all disks were mounted, parity had been run successfully. There was a power cut while I was away, after booting up the server again, Disk 3 in the array is showing as "Unmountable: not mounted". Parity check is currently running on its normal schedule (and has been for nearly 11 days). Diagnostics are attached. I'd appreciate advice on the correct way to resolve this. There are a huge number of errors popping up for the disk in question, so i'm expecting to need to replace this as part of the process. nebula-diagnostics-20221012-0805.zip

I have Sonarr and NZBGet set up in binhex Docker containers. For the most part, Sonarr and NZBGet are working in harmony. The connection to NZBGet tests successfully, and the majority of the time Sonarr is able to send reports to NZBGet. However, on checking the logs, Sonarr is regularly receiving the following error when trying to connect to NZBGet: Unable to retrieve queue and history items from NZBGet: Unable to connect to NZBGet. Error getting response stream (GetResponse): ServerProtocolViolation: 'http://192.168.178.39:6789/jsonrpc' 1:05am Any idea why this would happen sometimes but be fine the rest of the time? Here's the full set of logs where this happened last night, and because of the error Radarr I think got confused and added 2 downloads for each movie (so you can see that despite the error the two apps can actually communicate):