blitzvergnugen

Ok, managed to figure it out. sabnzbd was placing things in the wrong location. Apparently I had gone non-standard in my old configuration and that did not transfer over from my last configuration. A careful reading of https://trash-guides.info/Radarr/Radarr-remote-path-mapping/ helped me find the issue. It was confusing as the the settings were only off by a couple characters. In sabnzbd>Folders Setting Good Bad "Temporary Download Folder" /downloads/incomplete Downloads/incomplete "Completed Download Folder" /downloads/complete Downloads/complete Insidiously close. One thing I did learn is that this was easier to verify from Radarr. It gives a warning in the Radarr>System>Health Check if the completed downloads folder does not exist. I was able to play around and run the Radarr>Tasks>Health Check to see if it had resolved. Once I finally got that, the whole pipeline started working properly. Unfortunately, I was unable to get things through the remaining steps of the Sonarr pipeline. Sonarr had initiated the download and cached the message from sabnzbd (with the incorrect download placement location). I had to manually move things over and the Sonarr was able to detect and rename them. Did lose "quality" metadata by doing it that way. Hope this helps someone in the future.

One thing to mention: I recently had some issues with my cache drive and I believe this may be some effects that I'm just now noticing. For reference: https://forums.unraid.net/topic/143240-replace-cache-drive-that-has-gone-read-only/ Could it be a hardlink got corrupted or missing when I replaced that?

My issue is like this thread (whose guidance I've followed) https://forums.unraid.net/topic/125875-import-error-in-sonarrradarr/, I'm having import errors in Sonarr/Radarr. This feels like a mapping error, but not quite... I do believe my mappings to be correct, but the error logs look like something is going wrong in Sonarr/Radarr. I'm using all linuxserver docker containers. Mappings: App Name Container Volume Host Volume radarr /downloads /mnt/user/downloads/ /movies /mnt/user/Movies/ /config /mnt/user/appdata/radarr sabnzbd /downloads /mnt/user/downloads/ /incomplete-downloads /mnt/user/downloads/incomplete/ /config /mnt/user/appdata/sabnzbd sonarr /dev/rtc /dev/rtc /tv /mnt/user/TV/ /downloads /mnt/user/downloads/ /config /mnt/user/appdata/sonarr Sonarr error: 2023-09-15 02:11:24.8|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /config/Downloads/complete/tv/my-show-here. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder Radarr error: Remote download client sabnzbd+ places downloads in /config/Downloads/complete/movies but this directory does not appear to exist. Likely missing or incorrect remote path mapping. From other error logs, I find it very odd that log has /config/ prior to the /downloads container volume. I'm not seeing this in other "import error" help requests, so I believe it to be my root cause.

Well, I messed something up as the configs to my docker apps did not come back. I was able to pull the old cache drive out and put it in an enclosure, then use the Unassigned Devices plugin to retrieve and restore them. I think what could have been better would be to set my appdata share to Yes: Cache and invoking the mover (as mentioned above). Then set appdata to No: Cache and install one of the appdata backup apps/plugins. Either way, that's my next step is to install an appdata backup apps. Hope this is useful to anyone who encounters this situation in the future.

Following my instinct to migrate the data off the cache pool, I have followed steps 1-5 of this help article https://docs.unraid.net/unraid-os/manual/storage-management#reformatting-a-cache-drive Changing the Cache settings of my Shares to all be "No" or "Yes: Cache" allowed the Mover to do...something. diff'ing the shares/appdata.cfg from my earlier diagnostics and the one in this post makes me think I've successfully migrated the data as a disk was added to the list of where data resides. Unfortunately, since my Cache drive is read-only, nothing gets changed on it. So.. I think I have all the data off of the drive, but it's technically in some limbo/duplicated state. This seems like a place for "fun" edge cases. I think my next step is to essentially add a step between 6 (stop array) and 7 (start array) in the "Reformatting a cache drive" article (linked above) where I physically add the drive to the box. Then remove the old cache drive from the array configuration and replace it with the new drive. I may get impatient and give it a go, but it'd be nice to have some confirmation for a confidence booster. Thanks for any and all help. unnasty-diagnostics-20230806-1547.zip

I believe my SSD cache drive has "died" and entered a read-only state. I would like to replace it, but am not sure the best way to go about that. I've looked up a few guides on replacing cache drives, but most make use of CA apps to assist with the migration process. I don't think I can do that as Docker fails to start due to appdata (Only: Cache) and system (Prefer: Cache) being on the dead/dying cache drive. I've got hardware to replace the cache drive, just don't know what's the best way to go about it. Would it be easier to add the new drive to the cache pool, then manually migrate the data over? Open to options. Thanks for any and all help. unnasty-diagnostics-20230806-1053.zip