External smb share disappearing in sabnzbd

Operating System
1

Hi, looking for some help/ advice.

Just spent a few hours installing configuring and then reinstalling and configuring as I was experiencing issues when trying to setup the Arr stack in ZimaOS.

Everything is now working as I would like and I have taken backups from within the Arr stack applications so that if I have to reinstall again, its simple to get back to where I was.

The issue I have is Sabnzbd seems to lose connection to my synology NAS share after a reboot of the system, it cant find the folder to create and move the downloaded file.

If I go back into the Sabnzbd settings and refresh the mount point for the synology nas it works again!

Is there an ID for the mount points that changes after a reboot? I am guessing there must be something that changes in ZimaOS as the share on the Nas has not changed and refrshing the mount point in the app seems to connect it again.

Thanks For any advice

2

This isn’t a changing mount ID.

On ZimaOS, external SMB shares mount at the system level, and Docker containers (like SABnzbd) often start before that mount is fully ready after a reboot.

Result:
SAB starts > SMB share not mounted yet > path looks missing/empty > errors.
You refresh the mount > SMB is now ready > it works immediately.

This is a boot timing issue, not a Synology problem.

Clean fix:
Don’t point SAB directly at the dynamic /media/... path.
Create a stable path like /DATA/downloads, bind the SMB share to that, and map that fixed path into the container. That way the container always sees the same location, even if the SMB mount reconnects underneath.

Quick workaround:
After reboot, wait 1–2 minutes and restart only the SAB container instead of refreshing inside the app.

Very common with remote mounts + Docker on lightweight NAS OSes.