July 27, 20241 yr I have no idea why, but Radarr decided to stop working a few days ago. In the "System" tab, this is in there: No idea why that changed all of a sudden, but ok fine...when I try to go add a new root folder, I get this: This makes no sense. Nothing that I know of has changed, all the permissions and everything for all the folders are the same ("nobody users" when I ls -l it), I've Googled everything I can think of and it's such a generic error that I can't really find anything useful. I've tried chmod-ing the directory -R 777 too. No change. Anyone have any idea what it's looking for?...what would make it happy? Thank you!!
July 27, 20241 yr Best to post in the specific thread for the container you are using, click on the icon in the Unraid GUI and select support.
July 28, 20241 yr Author Solution I actually figured it out. I noticed that it wasn't just Radarr having a problem...it was Sonarr and even NZBGet, all broken, all of a sudden. That in and of itself made me go "hmmm". I looked in the messages on NZBGet and saw it kept saying it couldn't write a file over and over and over again. One error said the disk may be full. I was like, "no way...I have almost 8TB of free space still..." Then I thought, "wait. Maybe I didn't tell that share to use the new disk when I added it." And I sure didn't. The share it was all writing to couldn't write to the new disk and that new disk was the only disk with any space available. Told the share to use the new disk as well, Bob's your auntie, all is right with the world. 👍
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.