Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

blitzvergnugen

Members
  • Joined

  • Last visited

Solutions

  1. blitzvergnugen's post in Import error Sonarr/Radarr was marked as the answer   
    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.
  2. blitzvergnugen's post in Replace cache drive that has gone read-only was marked as the answer   
    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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.