rbjap

It looks like replacing the disk has solved the parity check/rebuild issue as well. Thanks to you both for your help.

That seems to have solved the mover problem, thank you! Any ideas as to why the parity check is dragging on forever? Could that be related to the drive with read errors, or is it something else?

Completed as instructed. I tried to take a look at the syslog in the diags after enabling the logging, and it looked like it just said that it was starting then immediately said it was finishing. Hopefully there's somewhere else that you know of that has more information. Just for additional information, Fix Common Problems is also telling me that I have Machine Check Events. I don't know if that's related to the read errors on the one disk that I know about, or if it's something else that could be contributing to the problem. tower-diagnostics-20250414-0742.zip

I've checked the share names, there's no issue there as far as I can tell. It's files in the p------a share that should be moved off the cache and into the array.

I've removed the mover plugin and the mover function still won't engage. I can press the button to force a move, the screen refreshes, however it still doesn't move anything. I had removed the old instance of the plugin previously and had found a new one in the app store, so it was the newer, supported version that I had installed. Now neither of them are.

I'm having an issue with the mover and parity check functions on my system. I used to have a mover tuning plugin from the store, but I removed it since it was showing up as not supported and was recommended to be removed before the upgrade to 7.0.1 (the version that I'm currently on). For the mover, it's just not moving anything automatically at all anymore. I have to manually go in and move files off my cache drive and onto the field drives.tower-diagnostics-20250412-1128.zip For the parity check, I have it scheduled to kick off on the first of the month and run during the overnight hours. Typically with my array, it will complete within 3+ days of processing time. We're now almost halfway into the month and it's only gone 3.5% of the way through. When I try to resume it manually, it will run for a few seconds and then stop. I know that I have one of my drives that is showing errors and that has been shut down. I plan on replacing it, but I'm afraid if I do, it won't actually rebuild the array with my other issues going on. Do I need to replace the drive, and then my other issues will resolve themselves, or do I need to figure out these issues and get them resolved prior to replacing the drive? I've attached diagnostics from my system and very much appreciate any assistance the community can provide to help me figure out and fix my system.

I'm using the latest docker version of the template for each instance.

I'm trying to use radarrsync. I set it up yesterday and it synced part of the entries between the two instances, then it threw this error message and hasn't done anything since: File "/RadarrSync.py", line 86, in <module> searchid.append(int(r.json()['id'])) TypeError: list indices must be integers or slices, not str Can anyone shed any light as to what is causing this issue and how it can be resolved? Thanks in advance