jebusfreek666

Just noticed that for the past 2 weeks or so, Sonarr and Radarr are no longer doing anything. I had errors connecting to deluge and jackett in both of them. Jackett seems to be on the way out so I switched to prowlarr. I am fairly sure that is set up correctly and I have it loaded in both Sonarr and Radarr. But nothing has changed with deluge. I can open the webui, but it will not connect to sonarr or radarr. Has something changed recently? Update: Actually, Deluge is messed up somehow. I can open the webui, but all the settings are blank and it keeps timing out. I can not add or edit anything. Update 2: Never mind. A server reset seems to have fixed it.

It sounds to me like this is more or less a scaled down version of unBalance, but from within the webUI. Is that correct? It is obviously missing some of the functionality of unBalance, like gather, but the way it works essentially seems the same. Edit: actually, this might have more functionality than unBalance. I don't remember, but I don't believe that had share to share moves?

@Squid Just a heads up, the script linked in the OP for spinning up all disks at a certian time is no longer valid. Might want to remove it so it doesn't send others to incorrect info. I read another post about another script to do this, but I am not sure how it panned out.

I figured, but wanted to make sure Also, I know it is not built into this plugin, but I was wondering if it is possible to have turbo write invoked anytime writes go to certain shares or come in from a certain user (for a windows PC). I have a few shares that are set to not use the cache as the files are sensitive and I would prefer they get written to the encrypted array ASAP.

Does invoking turbo write spin all the drives up itself? What I mean is, if I have it set to invoke turbo write when 4 drives are spinning (6 spun down of 10 total), will it automatically spin all the drives up even if no writes are happening? So If I have 4 people streaming plex, and all 4 people happened to pic media that is on 4 different drives causing them to spin up I know this will change it to turbo write. I just want to make sure that it wont also spin up all the drives until one of them is actually writing. I read through the explanation of turbo write, and this entire post but didn't see this specifically called out.

If you wanted to enable/disable Auto mode would it be write method 2? Edit: Did a little more digging and found out auto is not what I thought it was, so the question is kind of meaningless now. 🤷‍♂️

Not really. I am pretty sure this can be handled with a user script, though I am not an expert by any means. In my case, I am starting to think I will just use dedicated unassigned disks or possibly a cache pool instead. Depending on the number of cameras I end up with and the quality of the video, this could be a rather large amount of data. And expecting mover to handle that much every day might be asking a bit much.

I am trying to keep my disks spun down as much as possible, and narrowed down the biggest offender to be bazarr. It is downloading subs and spinning up the disks very frequently. I do not see a way to adjust how often it searches or downloads. If someone know how to do this it would be great. Or, better yet, if someone knows a way to make it download to cache instead (still same path though, ie. mnt/user/media/movies but on the cache) then it would never spin up the drives and instead the subs would be accessible right away and get moved over with mover.

Logs are completely filled with this: Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: Discover page displays nothing. Searches return only TV shows, movie posters look like they are trying to load but never do.

I have been having an issue in Ombi for a while now. It doesn't seem to mark things as available after they are added to plex. All requests go through fine to sonarr/radarr. I went to settings to test the connection to plex and it connects successfully. Not sure where the issue is.

Where is the setting in Sonarr/Radarr to have it make plex update its library?

I have been thinking about setting my disks to spin down after a certain amount of time. I realize that I will have to turn off periodic checks in plex as this will keep the disks spinning. My question is, I had read that plex will kick out errors if the disk that the media is on has to spin up. I don't know if this is an old issue or something that has been resolved some way in recent builds. Is this still the case? I have like 10 data disks and my media is spread across all of them as this is primarily a plex server. I will probably have to skip doing spin downs if my plex users are going to get errors all the time.

Yes, that is correct. I was wondering because in your previous response you said: Which I took to mean writing to a dedicated disk in the array.

If you set it up to one of your array disks wont you just be right back in the situation of constant writes to the array? That's why I wanted to do a raid 1 cache pool, for redundancy. Depending on how much space 30 days worth of video used, I could just leave it on the HDDs I guess. But I only have a few spare 6Tb drives, and think it is going to be a lot more data than that. What do you mean it might not be viable to move to the array every night? Do you mean there would be too much data to transfer in that time span? As for the total size used by my cams, I do not have this info yet. It will take a while before it is up and running. It is still sort of in the planning phase.

I guess pool size and redundancy would be the most important. I am not sure how important write speed is really in this instance, since NVRs routinely have used HDD. I am not sure on the exact size of drive I will need, but rough estimates have put it well over the 2Tb range daily unless I am doing this wrong. I could have it just write directly to the array, but I feel like this would be a waste as it would be writing not only the data but also dual parity 24/7. I thought it would be nice to have mirrored copies as a cache pool and then set it to move the files over while I slept.