rmp5s

Tried a system reboot which led to Docker not wanting to start at ALL, so I had to go in and delete docker.img from /mnt/user/system/docker/, turned Docker off and back on again, then reinstalled all the containers as outlined here. (Community Applications really is an absolute GODSEND!!) Now everything appears to be back to normal. No idea what caused all that but wasn't too big of a deal to fix...so...whatever, I guess. 👍

Got it sorted, everyone.  Anyone else getting a similar error, don't click the "contact support" link in the error...go here and create a ticket.  Always been impressed with Lime's support.  Fantastic as usual.

Thanks, everyone.

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.  👍